bgp

bgpIncomingDynamicPeerLimitReached

bgpIncomingDynamicPeerLimitReached:bgp

Table 1. bgpIncomingDynamicPeerLimitReached properties
Property name	Value
Application name	bgp
Event name	bgpIncomingDynamicPeerLimitReached
Default severity	notice
Message format string	In network-instance network-instance, an incoming BGP connection from peer-address was rejected because the limit for the maximum number of incoming dynamic peers, max-sessions, has been reached.
Cause	The configured limit on the number of incoming sessions associated with dynamic peers has been reached.
Effect	The incoming connection attempt is rejected.

bgpInstanceConvergenceStateTransition

bgpInstanceConvergenceStateTransition:bgp

Table 2. bgpInstanceConvergenceStateTransition properties
Property name	Value
Application name	bgp
Event name	bgpInstanceConvergenceStateTransition
Default severity	notice
Message format string	In network-instance network-instance, the BGP convergence state for the address-family address family transitioned from the previous-state state to the new-state state
Cause	This event is generated when the BGP convergence process is being tracked and a state transition occurs
Effect	Dependent on the new state

bgpLowMemory

bgpLowMemory:bgp

Table 3. bgpLowMemory properties
Property name	Value
Application name	bgp
Event name	bgpLowMemory
Default severity	critical
Message format string	In network-instance network-instance, the BGP session with peer-address was terminated immediately because BGP has out of memory.
Cause	BGP has run out of memory and this peer has been shutdown to reclaim some memory.
Effect	No routes can be exchanged with this peer.

bgpNeighborBackwardTransition

bgpNeighborBackwardTransition:bgp

Table 4. bgpNeighborBackwardTransition properties
Property name	Value
Application name	bgp
Event name	bgpNeighborBackwardTransition
Default severity	warning
Message format string	In network-instance network-instance, the BGP session with peer-address moved from higher state last-state to lower state session-state due to event last-event
Cause	This event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.
Effect	No routes can be exchanged with this peer.

bgpNeighborClosedTCPConn

bgpNeighborClosedTCPConn:bgp

Table 5. bgpNeighborClosedTCPConn properties
Property name	Value
Application name	bgp
Event name	bgpNeighborClosedTCPConn
Default severity	warning
Message format string	In network-instance network-instance, the BGP session with peer-address was closed because the neighbor closed the TCP connection.
Cause	The router received a TCP FIN message from its peer.
Effect	No routes can be exchanged with this peer.

bgpNeighborEstablished

bgpNeighborEstablished:bgp

Table 6. bgpNeighborEstablished properties
Property name	Value
Application name	bgp
Event name	bgpNeighborEstablished
Default severity	notice
Message format string	In network-instance network-instance, the BGP session with peer-address moved into the ESTABLISHED state
Cause	The BGP session entered the ESTABLISHED state.
Effect	Routes of negotiated address families can now be exchanged with this peer.

bgpNeighborGRHelpingStarted

bgpNeighborGRHelpingStarted:bgp

Table 7. bgpNeighborGRHelpingStarted properties
Property name	Value
Application name	bgp
Event name	bgpNeighborGRHelpingStarted
Default severity	notice
Message format string	In network-instance network-instance, the router has started providing GR helper service to the neighbor peer-address
Cause	GR helper is activated
Effect	Routes previously received from the peer, prior to its restart, are retained as stale until the stale-routes-time expires.

bgpNeighborGRHelpingStopped

bgpNeighborGRHelpingStopped:bgp

Table 8. bgpNeighborGRHelpingStopped properties
Property name	Value
Application name	bgp
Event name	bgpNeighborGRHelpingStopped
Default severity	notice
Message format string	In network-instance network-instance, the router has stopped providing GR helper service to the neighbor peer-address
Cause	GR helper is deactivated
Effect	Any remaining stale routes are immediately removed.

bgpNeighborHoldTimeExpired

bgpNeighborHoldTimeExpired:bgp

Table 9. bgpNeighborHoldTimeExpired properties
Property name	Value
Application name	bgp
Event name	bgpNeighborHoldTimeExpired
Default severity	warning
Message format string	In network-instance network-instance, the BGP session with peer-address was terminated because a KEEPALIVE message was not received before the holdtime limit of negotiated-hold-time was reached.
Cause	BGP did not receive a KEEPALIVE message from the peer before the negotiated holdtime expired.
Effect	No routes can be exchanged with this peer.

bgpNeighborInvalidLocalIP

bgpNeighborInvalidLocalIP:bgp

Table 10. bgpNeighborInvalidLocalIP properties
Property name	Value
Application name	bgp
Event name	bgpNeighborInvalidLocalIP
Default severity	warning
Message format string	In network-instance network-instance, an incoming BGP connection from peer-address was rejected because the destination IP address does not match the allowed local-address, local-address.
Cause	BGP configuration does not allow an incoming BGP connection to this IP address.
Effect	No routes can be exchanged with this peer.

bgpNeighborNoOpenReceived

bgpNeighborNoOpenReceived:bgp

Table 11. bgpNeighborNoOpenReceived properties
Property name	Value
Application name	bgp
Event name	bgpNeighborNoOpenReceived
Default severity	warning
Message format string	In network-instance network-instance, the BGP session with peer-address was terminated because an OPEN message was not received before the configured holdtime limit was reached.
Cause	BGP did not receive an OPEN message from the peer before the configured holdtime expired.
Effect	No routes can be exchanged with this peer.

bgpNeighborPrefixLimitReached

bgpNeighborPrefixLimitReached:bgp

Table 12. bgpNeighborPrefixLimitReached properties
Property name	Value
Application name	bgp
Event name	bgpNeighborPrefixLimitReached
Default severity	notice
Message format string	In network-instance network-instance, the number of family routes received from the neighbor peer-address has exceeded the configured limit.
Cause	The number of received routes from the peer has exceeded the configured limit for the associated address family.
Effect	No effect. Routes above the limit are still received and processed.

bgpNeighborPrefixLimitThresholdReached

bgpNeighborPrefixLimitThresholdReached:bgp

Table 13. bgpNeighborPrefixLimitThresholdReached properties
Property name	Value
Application name	bgp
Event name	bgpNeighborPrefixLimitThresholdReached
Default severity	notice
Message format string	In network-instance network-instance, the number of family routes received from the neighbor peer-address has exceeded the configured threshold, which is warning-threshold-pct% of the limit.
Cause	The number of received routes from the peer has exceeded the configured threshold for the associated address family.
Effect	No effect. Routes above the threshold are still received and processed.

bgpNeighborUnknownRemoteIP

bgpNeighborUnknownRemoteIP:bgp

Table 14. bgpNeighborUnknownRemoteIP properties
Property name	Value
Application name	bgp
Event name	bgpNeighborUnknownRemoteIP
Default severity	warning
Message format string	In network-instance network-instance, an incoming BGP connection from peer-address was rejected because the source IP address does not match the address of any configured neighbor or any dynamic-neighbor block.
Cause	BGP configuration does not allow an incoming BGP connection from this IP address.
Effect	No routes can be exchanged with this peer.

bgpNLRIInvalid

bgpNLRIInvalid:bgp

Table 15. bgpNLRIInvalid properties
Property name	Value
Application name	bgp
Event name	bgpNLRIInvalid
Default severity	warning
Message format string	In network-instance network-instance, a route for NLRI nlri was received from neighbor peer-address and it was ignored because it is considered an invalid NLRI.
Cause	The router received an UPDATE with an invalid NLRI
Effect	The route associated with the NLRI is not added or removed from the BGP RIB.

bgpNotificationReceivedFromNeighbor

bgpNotificationReceivedFromNeighbor:bgp

Table 16. bgpNotificationReceivedFromNeighbor properties
Property name	Value
Application name	bgp
Event name	bgpNotificationReceivedFromNeighbor
Default severity	warning
Message format string	In network-instance network-instance, the BGP session with peer-address was closed because the neighbor sent a NOTIFICATION with code last-notification-error-code and subcode last-notification-error-subcode
Cause	The router received a NOTIFICATION message from its peer.
Effect	No routes can be exchanged with this peer.

bgpNotificationSentToNeighbor

bgpNotificationSentToNeighbor:bgp

Table 17. bgpNotificationSentToNeighbor properties
Property name	Value
Application name	bgp
Event name	bgpNotificationSentToNeighbor
Default severity	warning
Message format string	In network-instance network-instance, the BGP session with peer-address was closed because the router sent this neighbor a NOTIFICATION with code last-notification-error-code and subcode last-notification-error-subcode
Cause	The router sent a NOTIFICATION message to its peer.
Effect	No routes can be exchanged with this peer.

bgpOutgoingDynamicPeerLimitReached

bgpOutgoingDynamicPeerLimitReached:bgp

Table 18. bgpOutgoingDynamicPeerLimitReached properties
Property name	Value
Application name	bgp
Event name	bgpOutgoingDynamicPeerLimitReached
Default severity	notice
Message format string	In network-instance network-instance, no session was initiated towards the LLDP-discovered address peer-address because the limit for the maximum number of outgoing dynamic peers, max-sessions, has been reached.
Cause	The configured limit on the number of outgoing sessions associated with dynamic peers has been reached.
Effect	No connection attempt is made by the router.

bgpPathAttributeDiscarded

bgpPathAttributeDiscarded:bgp

Table 19. bgpPathAttributeDiscarded properties
Property name	Value
Application name	bgp
Event name	bgpPathAttributeDiscarded
Default severity	warning
Message format string	In network-instance network-instance, a path attribute of type attribute-type and length attribute-length was discarded in a route received from the neighbor peer-address.
Cause	The path attribute was malformed and the attribute-discard approach is used for this type of attribute.
Effect	The intended meaning of that path attribute is not applied but the UPDATE message is still processed for new reachabiity information.

bgpPathAttributeMalformed

bgpPathAttributeMalformed:bgp

Table 20. bgpPathAttributeMalformed properties
Property name	Value
Application name	bgp
Event name	bgpPathAttributeMalformed
Default severity	warning
Message format string	In network-instance network-instance, a path attribute of type attribute-type and length attribute-length that was received in a route from the neighbor peer-address was considered malformed.
Cause	The router considers a path attribute to be malformed, for example not the expected length. The UPDATE message can still be parsed though.
Effect	Dependent on the type of the malformed path attribute. Either the malformed attribute is discarded or else the entire UPDATE message is considered to have unreachable NLRI.

bgpRouteWithdrawnDueToError

bgpRouteWithdrawnDueToError:bgp

Table 21. bgpRouteWithdrawnDueToError properties
Property name	Value
Application name	bgp
Event name	bgpRouteWithdrawnDueToError
Default severity	warning
Message format string	In network-instance network-instance, a route for NLRI nlri was received from neighbor peer-address and it was considered withdrawn because of a recoverable error in the UPDATE message.
Cause	The router received a malformed UPDATE and the malformed path attribute(s) require as a treat-as-withdraw error handling behavior for the included set of routes.
Effect	There is no reachability for the NLRI in the malformed UPDATE message.

bgpUpdateInvalid

bgpUpdateInvalid:bgp

Table 22. bgpUpdateInvalid properties
Property name	Value
Application name	bgp
Event name	bgpUpdateInvalid
Default severity	warning
Message format string	In network-instance network-instance, an UPDATE message received from neighbor peer-address was considered invalid and caused the connection to be closed because the NLRI could not be parsed correctly.
Cause	The router received a malformed UPDATE which made it is impossible to identify all of the NLRI correctly.
Effect	The session is shutdown.

bgp