5000 Series Layer 2/3 Managed Data Center Switch CLI Reference Guide
1112
Prefixes Current
The number of prefixes currently advertised to or received from this
neighbor. For inbound prefixes, this count only includes prefixes that
passed inbound policy.
Prefixes Accepted
The number of prefixes from this neighborthat are eligible to become
active in the local RIB. Received prefixes are ineligible if their BGP Next
Hop is not resolvable or if the AS-PATH contains a loop. A prefix is only
considered accepted if it passes inbound policy.
Prefixes Rejected
The number of prefixes currently received from this neighbor that fail
inbound policy.
Max NLRI per Update
The maximum number of prefixes included in a single UPDATE
message, to and from this neighbor.
Min NLRI per Update
The minimum number of prefixes included in a single UPDATE
message, to and from this neighbor.
If the router receives an UPDATE message with an invalid path attribute, the router will in most cases
send a NOTIFICATION message and reset the adjacency. BGP maintains a per-neighbor counter for
each type of path attribute error. This show command ts each non-zero counter, just after the
LastSubError. The counters that may be listed are as follows:
Path with duplicate
attribute
The peer sent an UPDATE message containing the same path attribute
more than once.
Path with weII-
known/optionaI conflict
A received path attribute was flagged as both well-known and optional
or neither well-known nor optional.
Transitive f gt set on
transitive attr
A received path attribute is known to be transitive, but the transitive flag
is not set.
Manda attribute non-
transitive or partial
A mandatory path attribute was received with either the transitive or
partial flag set.
Optional attribute non-
transitive and partial
An optional path attribute has the transitive flag clear and the partial flag
set.
Path attribute too long
A received path attribute was longer than the expected length.
Path attribute length error
A received path attribute has a length value that exceeds the remaining
length of the path attributes field.
Invalid ORIGIN code
A received UPDATE message included an invalid ORIGIN code.
Unexpected first ASN in AS
path
The AS-PATH attribute from an external peer did not include the peer’s
AS number as the first AS.
Invalid AS path segment
type
The AS-PATH includes a segment with an invalid segment type.
Invalid BGP NEXT HOP
The BGP NEXT HOP is not a valid unicast address.
Bad BGP NEXT HOP
The BGP NEXT HOP was either the receiver's IP address or an IP
address outside the subnet to the peer.
Invalid AGGREGATOR
attribute
The AGGREGATOR attribute was invalid.
Unrecognized well-known
path attribute
An UPDATE message contained a path attribute with the Optional flag
clear, but this router does not recognize the attribute.