Synchronizing with the MPLS Topology Server
MPLS Topology Server
The MPLS component servers of may be started in any order, meaning that the
MPLS Monitoring Server
and the MPLS Analysis Server
may be started before or after the MPLS Topology Server
performs its initial discovery.Whenever
the
MPLS Monitoring Server
and the MPLS Analysis Server
are started, the autoconfiguration
program, described in the , automatically adds the MPLS Topology Server
as a topology source to the MPLS
monitoring and analysis servers, and creates an InChargeDomain object (INCHARGE-MPLS-TOPOLOGY, for example) in their repositories.After the
MPLS Topology Server
is added as a topology source,
the MPLS Monitoring Server
and the MPLS Analysis Server
each start a synchronization program that probes the MPLS Topology Server
repository for network, MPLS, VPN, and BGP topology. The synchronization program probes for topology information immediately after the MPLS Topology Server
is added as a topology source, and then every time thereafter whenever:- TheMPLS Topology Servercompletes a discovery cycle.
- The connection to theMPLS Topology Serveris lost and then reestablished.If theMPLS Topology Serveris not running when theMPLS Monitoring Server/MPLS Analysis Serverstarts up, the synchronization program periodically attempts to probe for the topology. When theMPLS Topology Serverbecomes available, the probing succeeds.During the probing of topology, the MPLS monitoring and analysis servers also learn the names of their proxy (status) sources. TheMPLS Monitoring Serverlearns the names of theIP Availability Managers that are added as topology sources to theMPLS Topology Server, and theMPLS Analysis Serverlearns the name of theMPLS Monitoring Server.When MPLS-BGP cross-domain correlation is enabled, theMPLS Monitoring Serveralso learns the name of its proxy source from theMPLS Topology Server.