Interface Down event reported as root cause for BGPSession Disconnected events

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:

Criteria for Interface Down event to be an NPM BGPSession Disconnected root cause

Environment

Smarts - 10.1.X

Resolution

For an Interface Down event to be an NPM BGPSession Disconnected root cause, all BGPSessions which have a relationship with that Interface must be disconnected. To ascertain which BGPSessions must be disconnected to see the RCA of Interface Down, do the following:

1. Run the following command:
   

   <BASEDIR>/bin/dmctl -s <BGP-DOMAIN> exec dmdebug --dumpCodebook

   
   
   
2. Check the BGP server log for the output and "grep" the server log file for the Interface.

The following is an example codebook output from the BGP domain log file. For an Interface Down to be generated, both BGPSessions must be disconnected as shown in the following example:

Event: <MSI_Element::<Interface name>/3::Down> may cause:
Event: <MSI_Element::<Interface name>/3::DownInRemote> 1
Event: <BGPSession::<BGP session instance>/<IP address><-->abc-abc.com/<IP address>::Disconnected> 1
Event: <BGPSession::<BGP session instance>/<IP address><-->abc-abc.com/<IP address>::Disconnected> 1