For an MPLS Monitoring Server, the autoconfiguration program follows the TopologyProvides relationship in the mpls-tma.conf file to its source, the MPLS Topology Server, and then adds the MPLS Topology Server as a topology source to the MPLS Monitoring Server. The MPLS Monitoring Server responds by connecting to the MPLS Topology Server and importing a subset of topology for monitoring purposes.
The MPLS Monitoring Server creates an InChargeDomain object (INCHARGE-MPLS-TOPOLOGY, for example) in its repository for the MPLS Topology Server instance that is added as a topology source. This object represents the connection between the MPLS Monitoring Server and the MPLS Topology Server source.
After the MPLS Monitoring Server establishes a connection to the MPLS Topology Server and imports a subset of the topology, which includes the InChargeDomain objects that represent the IP Availability Managers, the MPLS Monitoring Server is able to determine its proxy sources by reading the names of the imported InChargeDomain objects. It then adds the IP Availability Managers as proxy sources, connects to them, and subscribes to MPLS-relevant statuses.
When MPLS-BGP cross-domain correlation is enabled, the MPLS Monitoring Server also fetches the name of the Network Protocol Manager for BGP from the MPLS Topology Server. It then adds the Network Protocol Manager for BGP as a proxy source, connects to it, and subscribes to BGP-relevant statuses.
Lastly, when the MPLS Monitoring Server establishes a connection to the MPLS Topology Server, the MPLS Topology Server creates an InChargeDomain object (INCHARGE-MPLS-MONITORING, for example) in its repository for the connected MPLS Monitoring Server. Among other things, this object serves as a reference for the MPLS Analysis Server.