Events

Events detected by Network Protocol Manager for BGP lists the events that are detected by Network Protocol Manager for BGP and used as symptoms to diagnose root-cause problems. For each event, Table 8 identifies the managed object for the event, the condition that triggers the event, and whether the event is imported by the Global Manager.

Note:

Events detected by Network Protocol Manager for BGP lists the events that are generated for BGP-enabled devices in IPv4 network. The range of notification for Cisco BGP-enabled devices in IPv6 network is limited. Those IPv6 specific events for Cisco devices are indicated against them.

Table 1. Events detected by Network Protocol Manager for BGP

Managed object	Event (symptom)	Condition
1**Imported by the Global Manager.
BGPProtocolEndpoint	AdministrativelyDown	This BGP protocol endpoint or its associated physical interface is administratively down (manually disabled).
	IBGPPeerMissingEvent Note: Also detected for Cisco BGP-enabled devices in IPv6 network.	The IBGP peer for this endpoint is not present in the topology.
	RemoteAsMismatchEvent	The actual AS number and the locally configured AS number of the BGP peer for this endpoint do not match.
	RemoteSpeakerNotConfiguredEvent	The BGP peer for this endpoint is not configured to speak BGP to this endpoint.
	RemoteSystemNotRunningBGPEvent	The BGP peer for this endpoint does not run BGP.
BGPSession	Disconnected 1 Note: Also detected for Cisco BGP-enabled devices in IPv6 network.	The BGP session is not established.
	Flapping1	The BGP session is experiencing transient functional problems.
BGPSessionGroup	Impacted 1	A BGPSessionGroup consists of multiple BGPSessions. If one of the sessions is alarming, then BGPSessionGroup event it Impacted.
RedundancyGroup (described in “BGPSessionGroup” on page 48)	AllComponentsDown 1	None of the member objects in the BGP redundancy group are responsive or operational.
	AtRisk 1	Only one of the member objects in the BGP redundancy group is responsive or operational.
	ReducedRedundancy 1	Applies only to BGP redundancy groups that contain three or more member objects: At least one member object in the redundancy group is unresponsive or not operational, but the number of responsive or operational member objects is at least two.