After the MPLS Topology Server adds an IP Availability Manager as a topology source, imports topology, and performs its own discovery, the MPLS Monitoring Server responds by performing the following tasks:

  1. Imports from the MPLS Topology Server and stores in its repository:

    • A subset of network, MPLS, VPN, and BGP topology (identified in “Imported topology subsets” on page 130), to be used for monitoring purposes.

      • An InChargeDomain object (INCHARGE-AM, for example) that represents the IP Availability Manager topology source.

  2. Starts a remote repository (proxy) accessor probe.

    • The probe adds the IP Availability Manager as a proxy source to the MPLS Monitoring Server.

      • To associate a network object in the repository of the MPLS Monitoring Server repository with its proxy source, the object’s ServiceName attribute is set to the name of the IP Availability Manager. For an object that is monitored by multiple proxy sources, the object’s ServiceName attribute is set to the name of the last added active IP Availability Manager.

  3. Starts another remote repository (proxy) accessor probe if MPLS-BGP cross-domain correlation is enabled.

    • The probe adds the Network Protocol Manager for BGP as a proxy source to the MPLS Monitoring Server.

      • To associate a BGP object in the repository of the MPLS Monitoring Server repository with its proxy source, the object’s ServiceName attribute is set to the name of the Network Protocol Manager for BGP.

        Thereafter, at startup or whenever the connection to the MPLS Topology Server is lost and then reestablished, the MPLS Monitoring Server re-imports topology from the MPLS Topology Server and re-runs the proxy probes.

        Also, whenever the MPLS Monitoring Server imports topology from the MPLS Topology Server, the MPLS Topology Server stores the name of the MPLS Monitoring Server (INCHARGE-MPLS-MONITORING, for example) as a reference for the MPLS Analysis Server.