Operational Defect Database
BugZero updated this defect 33 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 380813
Ionix/Smarts NPM: When is an Interface Down event reported as root cause for BGPSession Down events?
Last update date:
4/16/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
When is an Interface Down event reported as root cause for Ionix/Smarts NPM BGPSession Down events?
Resolution
For an Interface Down event to be an NPM BGPSession Down 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: Run the following command: <BASEDIR>/bin/dmctl -s <BGP-DOMAIN> exec dmdebug --dumpCodebook 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::IF-qa-gw4.smarts.com/3::Down> may cause:Event: <MSI_Element::IF-qa-gw4.smarts.com/3::DownInRemote> 1Event: <BGPSession::BGP-ADJ-qa-gw4.smarts.com/10.9.254.6<-->qa-gw6.smarts.com/10.9.254.4::Disconnected> 1Event: <BGPSession::BGP-ADJ-qa-NPMce3.lss.emc.com/10.9.254.4<-->qa-gw4.smarts.com/10.9.254.3::Disconnected> 1
