Monitoring Your Network - Understanding NerveCenter - Role in Network Management Strategy - Using Multiple NerveCenter Servers -
Previous: Standalone Operation     Next: Integration with Network Management Platforms

Using Multiple NerveCenter Servers

Because one NerveCenter server can inform another NerveCenter server or management platform of a network condition, it's possible to set up NerveCenter servers at remote sites that notify a centrally located NerveCenter server or management platform of the noteworthy network conditions at those remote sites.

Distributed NerveCenter Servers

This is a reliable solution because the remote NerveCenter servers use TCP/IP to notify the centrally located NerveCenter server of network conditions and retransmit messages as necessary to ensure their delivery.

There are a couple of advantages to this type of setup:

• Only a small amount of data is transmitted over the WAN. Any bandwidth intensive monitoring is conducted on a LAN and is managed by a remote NerveCenter server.
• The remote NerveCenter servers can be run in lights-out mode. Being able to run NerveCenter lights-out means that:
  • NerveCenter runs as a Windows NT service or as a UNIX daemon
  • You can monitor and configure NerveCenter from a remote location
  • You can modify all NerveCenter parameters without shutting NerveCenter down
  • No display or operators are required at a site
• The central NerveCenter can further correlate and filter conditions across remote NerveCenter Server domains