After the MPLS Topology Server adds an IP Availability Manager as a topology source, imports topology, and performs its own discovery, the MPLS Analysis 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 analysis purposes. It also imports the reference (INCHARGE-MPLS-MONITORING, for example) that identifies the name of the MPLS Monitoring Server.

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

    • The probe creates an InChargeDomain object (INCHARGE-MPLS-MONITORING, for example) that has the instance name of the MPLS Monitoring Server and adds the MPLS Monitoring Server as a proxy source to the MPLS Analysis Server.

      • To associate a network, MPLS, VPN, or BGP object in the repository of the MPLS Analysis Server with its proxy source, the object’s ServiceName attribute is set to the name of the MPLS Monitoring Server.

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

        Note that if the MPLS Analysis Server imports its initial topology before the MPLS Monitoring Server imports its initial topology, the MPLS Analysis Server will not be able to determine its MPLS Monitoring Server proxy source. However, as soon as the MPLS Monitoring Server import its topology, the MPLS Topology Server will send a proxy update message to the MPLS Analysis Server, and the MPLS Analysis Server will add the MPLS Monitoring Server as a proxy source.