Alcatel-Lucent 060321-10, Rev. B Cli Reference Manual page 1147

Omniswitch series
Table of Contents

Advertisement

BGP Commands
output definitions (continued)
Last rcvd Notification reason
Time last msg was rcvd
# of msgs sent
# of Update msgs sent
# of Route Refresh msgs sent
# of Notification msgs sent
OmniSwitch CLI Reference Guide
NOTIFY messages include errors codes. These error codes are listed
in this field. They apply to the last NOTIFY message received from
this peer. The notification reasons are listed in two parts separated by a
dash (-). The following are possible notification reasons:
message header error - synchronization loss
message header error - bad length
message header error - bad type
open message error - unsupported version
open message error - bad peer autonomous system
open message error - bad peer bgp id
open message error - unsupported option
open message error - authentication failure
open message error - unacceptable hold time
open message error - unsupported capability
update message error - malformed attribute
update message error - unknown attribute
update message error - missing wellknown attribute
update message error - attribute flags error
update message error - attribute length error
update message error - invalid origin
update message error - as loop
update message error - invalid nexthop
update message error - optional attribute error
update message error - invalid network
update message error - malformed aspath
cease - maximum number of prefixes reached
cease - administrative shutdown
cease - peer de-configured
cease- administrative reset
cease- connection rejected
cease - other configuration change
cease - connection collision resolution
cease - out of resources
hold time out - none
fsm error - none
none - none
The duration since a message was received from this peer.
Total number of messages (UPDATE, NOTIFY, OPEN, KEEPALIVE)
sent to this peer.
The number of route UPDATE messages sent to this peer. UPDATE
messages contain route reachability information, BGP attributes, and
route feasibility information.
The number of route refresh requests this peer has sent. Route refresh
requests request all routes learned be a peer.
The number of NOTIFY messages sent to this peer. NOTIFY mes-
sages contain error information, such as unsupported parameters,
invalid attributes, and holdtime expirations.
March 2011
show ip bgp neighbors statistics
page 19-179

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Omniswitch 10k

Table of Contents