NerveCenterTM 3.8: An Overview
-
Contents - Multiple NerveCenters -
If your network is large or distributed over a wide area, you may need to have more than one NerveCenter to manage all your devices. You may want to manage certain subnets independent of one another, or you might configure NerveCenter so that all polling is accomplished on local area networks rather than across a wide area network. Using this capability, you can minimize bandwidth by limiting the type of information to be monitored for each subnet and the number of nodes to be polled. Another aspect of distributed management is fault tolerance -- your important resources are not all located in one place.
A distributed NerveCenter configuration can reduce network overhead while providing some form of centralized management. For example, say that your company consists of a central office and several small branch offices. Local NerveCenters could manage the branch offices and forward important information to a central NerveCenter and/or network management platform. Because the NerveCenter Servers can run as a daemon on UNIX systems or as a service on Windows, the branch NerveCenters could be managed remotely using the NerveCenter Client, the command line interface, or utilities like ImportUtil. Multiple NerveCenters illustrates centralized management of multiple NerveCenters.
As events for the local NerveCenters are detected and filtered, each NerveCenter sends inform messages to the central NerveCenter or network management platform.
| NerveCenter Integrated with a Network Management Platform | Starting With NerveCenter |
| 29 July 2003 |