JP1 Version 11 Network Management: Getting Started

4.2 Troubleshooting mechanism

The Monitoring Manager manages the progress of incident handling as lifecycle states in the Incidents view. If multiple persons share the management, you can specify a person responsible for the operation other than you (by using Assigned To) to share the tasks on the GUI when starting the tasks to resolve a failure.

As shown in the following figure, if you assign a person responsible for handling an incident and change the lifecycle state, you can appropriately handle a failure that occurred:


After reporting an incident, the Monitoring Manager continues to monitor the state. If the Monitoring Manager detects a recovery, the state of the incident is automatically set to Closed. For example, when a node for which NodeDown was reported starts operation again, the state of the incident is automatically set to Closed.


As an exercise illustrating the operation, the following describes how to cause a dummy failure to occur in order to check the reported incident:

  1. Cause a failure to occur by disconnecting the LAN cable from a monitoring target node or stopping the node.

    Make sure the problem will not affect your business's work.

  2. After selecting the node in a map window, from the Actions menu, select Polling, and then select Status Poll.

    The state polling is performed, and then the failure is detected.