Root-cause problems for BGPProtocolEndpoint lists the root-cause problems that are diagnosed for BGPProtocolEndpoint.
| Problem 1 |
Description |
|---|---|
| 1**Problems prevent a session from forming on the affected endpoint. |
|
| Disabled |
This endpoint or its associated physical interface is administratively down (manually disabled), and the BGP session for this endpoint is reporting an improper state. |
| IBGPPeerMissing |
IBGP peer for this endpoint is not present in the topology, and the BGP session for this endpoint is reporting an improper state. Possibly, the peer IP, that is, the RemoteAddress for this endpoint, is misconfigured and is pointing to a nonexistent device. |
| RemoteAsMismatch |
Actual autonomous system number and locally configured autonomous system number of the remote device for this endpoint do not match, that is, ActualRemoteAS and RemoteAS for this endpoint do not match; and the BGP session for this endpoint is reporting an improper state. |
| RemoteSpeakerNotConfigured |
Remote device for this endpoint is not configured to speak BGP to the local device for this endpoint, and the BGP session for this endpoint is reporting an improper state. |
| RemoteSystemNotRunningBGP |
Remote device for this endpoint is not running BGP, and the BGP session for this endpoint is reporting an improper state. |
To prevent Network Protocol Manager for BGP from issuing Disabled root-cause problems, you set the AdminDownFlag parameter in the bgp.conf file. The VMware Smart Assurance Network Protocol Manager Configuration Guide provides directions on setting this parameter.
