Example for Using the Upper-Layer NMS to Monitor and Display Network-wide Resources

Procedure

1. Add lower-layer NMSs.
   1. Log in to the server on which a lower-layer NMS is installed, double-click the control console, and choose Tools > Hierarchical Management.
       NOTE:

      If a lower-layer NMS is installed in a local two-node cluster, log in using the floating IP address.

      

       NOTE:

      For a lower-layer NMS running the Linux operating system, firstly, stop the eSight process and then run the following commands as the ossuser user:

      If a lower-layer NMS is installed in a local high availability system, take the resource NMSServer offline on the hosts, run the following tool, and take NMSServer online. For details, see Bringing a Resource Online and Taking a Resource Offline in the eSight Product Documentation.

      cd eSight installation directory/mttools/tools

      ./connect-cluster.sh

      If the lower-layer NMS contains the LogCenter component in the hierarchical networking scenario, pay attention to the following points:

      • If you want to add the lower-layer NMS to the upper-layer NMS, run the LogCenter hierarchical NMS configuration tool on the LogCenter server. For details, see the LogCenter Product Documentation.

      • If the IP address of the upper-layer NMS changes, repeat steps 1.a and 1.b to configure connection parameters between the upper-layer and lower-layer NMSs.

        If the IP address of a lower-layer NMS changes, remove the lower-layer NMS from the upper-layer NMS and add it again.

        . You also need to run the LogCenter hierarchical NMS configuration tool on the LogCenter server. For details, see the LogCenter Product Documentation.

   2. Set parameters and click Config.

      

      f the lower-layer NMS is installed on the Linux operating system, Automatic start and stop eSight is unavailable. Start the lower-layer NMS manually. For details, see the eSight Product Documentation.

      Automatic start and stop eSight must be selected. Restart the lower-layer NMS to make the configuration take effect.

       NOTE:

      When you create a lower-layer NMS on the upper-layer NMS, set User Name and Password to the values specified here.

      After a lower-layer NMS is connected to the upper-layer NMS, you can click Rollback to terminate the connection between them and restore them as independent NMSs.

   3. Repeat steps 1.a to 1.b to configure the connection parameters for all the lower-layer NMSs.
   4. Log in to the upper-layer NMS and choose System > System Settings > Lower-Layer NMS.

      

   5. Click Create, enter basic information about the lower-layer NMSs, and click OK.

      

      

      View the online status of lower-layer NMSs in the lower-layer NMS list.

   6. Repeat step 1.e to add all the lower-layer NMSs to the upper-layer NMS.
   7. Click the name of a target lower-layer NMS to check whether you can normally access the lower-layer NMS.

      If you cannot access the lower-layer NMS, check the IP address, User name and Password of the lower-layer NMS and whether the lower-layer NMS is started.

2. Monitor network-wide alarms.
   1. Set an alarm monitoring rule.
      1. Choose Monitor > Fault Management > Alarm Settings and click Monitor Rule in the navigation tree.

         

          NOTE:

         The upper-layer NMS can display alarms reported by lower-layer NMSs only after an alarm monitoring rule is configured.
      2. Click Create, set basic alarm monitoring rule information, and click OK.

         

         

   2. View alarm details.

      Choose Monitor > Fault Management > Current Alarms.

      

      Click the name of a target alarm on the Current Alarms page.

   3. Manually acknowledge alarms.

      Select one or more alarms on the Current Alarms page, and click Acknowledge.

      

   4. You need to manually clear alarms if the alarms fail to be cleared automatically and no NE or NMS reports the alarms.

      Select one or more alarms on the Current Alarms page, and click Clear.

      

      After an alarm is cleared, it will be moved to the historical alarm list if it has been acknowledged, or displayed in the current alarm list in green if it has not been acknowledged.

3. Monitor network-wide topologies.
   1. Choose Monitor > Topology > Topology Management.

      

   2. View network-wide topology views of lower-layer NMSs.

      

   3. Synchronize topology information about lower-layer NMSs in real time.

      Select a lower-layer NMS whose topology information is to be synchronized in real time, right-click the blank area in the topology view and choose Synchronize topological layout of the lower-layer NMS.

      

4. Create user-defined device groups.
   1. Choose Resource > Resources Group > Group Management.

      

   2. Click  next to Custom Group under Device Group in the navigation tree to create a device group.

      

   3. Click Preview Members.

      

   4. Click Confirm. A user-defined device group is created.

      

5. Create lower-layer NMS Portlets.
   1. Choose Monitor > Monitoring Tools > Lower-layer NMS Mangement and click .

      

   2. In the Customize View dialog box, set Portlets to be displayed on the upper-layer NMS, and click  of the target Portlets.

      

   3. Set Portlets to be displayed on the lower-layer NMSs and click  of the target Portlets.

      

   4. Click Close. Portlets to be displayed on the upper-layer NMS and lower-layer NMSs are customized.

      

6. Customize the home page.
   1. Choose Home and click .

      

   2. In the Customize Homepage dialog box, set Portlets to be displayed, and click  of the target Portlets.

      

   3. Click Close. Alarm and topology information is aggregated on the home page.