Managing NerveCenter - Managing NerveCenter Port Settings - Troubleshooting: Managing NerveCenter Port Connections -
Previous: Specifying SNMP Ports for NerveCenter     Next: Managing Node Data

Troubleshooting: Managing NerveCenter Port Connections

The following list contains some common problems users have when managing the NerveCenter Server port connections.

The NerveCenter Server's communication port does not change when I selected Save in NerveCenter Administrator

Problem: NerveCenter must register the changes.

Solution: Stop and start the NerveCenter Server.

See Running the NerveCenter Server on UNIX or Running the NerveCenter Server on Windows NT.

A NerveCenter Server does not receive Informs sent by another NerveCenter Server

Problem: The inform packet is being sent to an incorrect port.

Solution: Make sure the receiving NerveCenter Server's inform port is the same as the port in the sending NerveCenter's inform configuration.

See Configuring NerveCenter to Receive Inform Actions.

The NerveCenter Server's inform port did not change when I selected Save in NerveCenter Administrator

Problem: NerveCenter must register the changes.

Solution: Stop and start the NerveCenter Server.

See Running the NerveCenter Server on UNIX or Running the NerveCenter Server on Windows NT.


Previous: Specifying SNMP Ports for NerveCenter Next: Managing Node Data
Please send comments or corrections to Information Development
This file was last updated on 10 October 2000