To reconfigure the Global Manager for configuration scenario 2:

  1. In the toolbar area of the Global Manager Administration Console, click the Reconfigure toolbar button.

  2. In the Server Reconfiguration confirmation dialog box, click Yes.

  3. In the Server Reconfiguration information dialog box, click Close.

    In response, the Global Manager:

    • Creates an InChargeDomainGroup object named ASIA-MPLS.

    • Creates an InChargeDomain object named ASIA-MPLS-TOPOLOGY and starts the appropriate topology drivers.

    • Creates an InChargeDomain object named ASIA-MPLS-MONITORING and starts the appropriate topology and event drivers.

    • Creates an InChargeDomain object named ASIA-MPLS-ANALYSIS and starts the appropriate event drivers.

    • Creates an InChargeDomain object named ASIA-AM1 and starts the appropriate topology and event drivers.

    • Creates an InChargeDomain object named ASIA-AM2 and starts the appropriate topology and event drivers.

    • Consults the Broker for the deployment and establishes connections to the ASIA-MPLS-TOPOLOGY, ASIA-MPLS-MONITORING, ASIA-MPLS-ANALYSIS, ASIA-AM1, and ASIA-AM2 domains.

    • Subscribes to and imports topology from the ASIA-MPLS-TOPOLOGY domain.

    • Subscribes to and imports remote ping events from the ASIA-MPLS-MONITORING domain.

    • Subscribes to and imports events from the ASIA-MPLS-ANALYSIS domain.

    • Subscribes to and imports topology and events from the ASIA-AM1 domain.

    • Subscribes to and imports topology and events from the ASIA-AM2 domain.

      The Global Manager will establish an additional connection to the ASIA-MPLS-MONITORING domain under any of the following circumstances:

    • To obtain the latest object attribute values for display in the Details tab of an MPLS Notification Properties dialog box.

    • To obtain the latest object attribute values for display in an MPLS Containment dialog box.

    • To re-execute a user-initiated remote ping on a remote ping object for which the ASIA-MPLS-MONITORING domain generated a remote ping Down or Impaired event.

      Note:

      As no IP Availability Manager application named INCHARGE-AM is running in configuration scenario 2, the administrator should disable the INCHARGE-AM domain for this scenario.