CLI Guide

Layer 3 Routing Commands 1391
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 lists each non-zero counter, just after the
LastSubError. The counters that may be listed are as follows:
Time Elapsed Since Last
Update
How long since an UPDATE message has been received
from this neighbor.
Message Table The number of BGP messages sent to and received from
this neighbor
Prefixes Advertised A running count of the number of prefixes advertised to
or received from this neighbor
Prefixes Withdrawn A running count of the number of prefixes included in
the Withdrawn Routes portion of UPDATE messages,
to and from this neighbor
Prefixes Current The number of prefixes currently advertised to or
received from this neighbor
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
Counters Description
Path with duplicate
attribute
The peer sent an UPDATE message containing the
same path attribute more than once.
Path with well-
known/optional conflict
A received path attribute was flagged as both well-
known and optional or neither well-known nor optional.
Transitive flag not set on
transitive attr
A received path attribute is known to be transitive, but
the transitive flag is not set.
Mandatory 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.