BGP domain topology is missing multiple BGPProtocolEndpoints and BGPSessions; Configuration changes made to BGP domain topology are not seen after Smarts AM synchronization

Products

• VMware Smart Assurance

Issue/Introduction

BGP domain topology in Smarts NPM is missing multiple BGPProtocolEndpoints and BGPSessions
Configuration changes made to Smarts NPM BGP domain topology are not being picked up after Smarts AM domain synchronization

Environment

SMARTS 10.x / 2.x/24.x

Cause

Once a device is initially discovered in Smarts NPM/BGP, the discovered topology is monitored by Smarts AM. However, BGP configuration changes made after the initial discovery are not picked up when the topology is subsequently synchronized with the Smarts AM domain. On subsequent synchronizations with the Smarts AM domain, only newly discovered devices in Smarts AM which also have BGP attributes will get discovered in the BGP domain.

Resolution

To resolve this issue, you must run a Discover All command against the BGP domain. This will cause devices that are already discovered to be probed again and their BGP configuration to be rediscovered. The Discover All command can be run using the appropriate function in the Smarts application user interface or by executing the following dmctl command:

dmctl -s <bgp-domain> invoke ICF_TopologyManager::ICF-TopologyManager discoverAll

 

Restarting the BGP domain will also invoke a discover all