IT Operations Management (ITOM)

3 reasons to deploy the Global Network Management feature of NNMi

3 reasons to deploy the Global Network Management feature of NNMi



Guest post by Michael Procopio


The Global Network Management feature of HP Network Node Manager i (NNMi) allows for one copy of NNMi to consolidate from other NNMi servers and provide a single view of the network as well as perform casual analysis. Here are three scenarios that would cause you to use this feature of our network management software.


If you haven’t experienced HP Network Node Manager i for yourself, this is your opportunity to download it and experience what it can do for you.


Management structure

In this example, let’s say your organization requires local autonomy for network management. An example of this might be a manufacturing company with multiple manufacturing plants. Each plant needs to be self-sufficient—including network management capabilities. In addition, there is a global network team that is responsible for connectivity to all sites.


In this case, each plant has its own copy of NNMi managing all the elements in the plant and each reports up to the global NNMi instance as well.


Regional distribution

Your organization is geographically diverse, for example a global company. Even though you are under the limit of 25,000 nodes for a single NNMi server, because of the distance to your furthest managed node it makes more sense to have one server for the Americas, one for Asia and one for Europe. This is due to the need for polling, which is less meaningful at long distances and with delay times.


As with the example above, each regional server reports into the central server.



The last reason to deploy the Global Network Management feature is a very large network. A single NNMi server can handle 25,000 nodes. If you have more than that you need to split the load across multiple servers. This prevents overweighing the system.


Additional notes


You can filter the nodes that are sent to the central server. This means that the central server does not need to manage all of the nodes of the distributed servers. This can be important in scaling because the consolidation server has an upper limit of 65,000 nodes. There are likely access switches in a local site that don’t need to be managed by a global team. By not passing those upstream you allow for more total nodes in the network than the 65,000 limit for a consolidation server.


Cross border causal analysis can be done by the consolidation server. Take the case where Server A’s domain and Server B’s domain are connected, but the link is not under either domain’s control. The only thing that is managed at that level are the attached switches. The consolidation server can stitch together that connection from the information it gets from the ports on the connecting devices. This helps us reach the conclusion that the view from the consolidation server may differ from the distributed servers because it has a different view of the network.


Whether it is management structure, regional distribution or scale the Global Network Management feature provides a solution.


You can download HP Network Node Manager i here and experience it for yourself.

You can also learn more about HP Network Node Manager i and the Global Network Management feature at the product page here.

  • infrastructure management
0 Kudos
About the Author


This account is for guest bloggers. The blog post will identify the blogger.