Dell N3200-ON EMC Networking N-Series Switches CLI Reference Guide version 6.7 - Page 1418

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