1.4.3 Error investigation

(a) Event details

First of all, check the details of the detected error event. If you register action methods and procedures in advance, the initial response will be smoother and faster.

Figure 1‒20: Troubleshooting advice (event guide information) provided in the Guide area

(b) Event search

For some problems, you might want to investigate not only the error-notification event but also related events leading up to the event in question, to see what was happening generally at the time the error occurred. In such cases, you can perform an event search.

(c) Event investigation

After verifying the general circumstances by checking the event details and conducting an event search, investigate each event.

From a displayed JP1 event, you can launch the appropriate management application and move by intuitive operation from the monitoring window to the investigation window to begin your diagnosis. You can also execute Windows and UNIX commands on an agent host directly from the Central Console. This makes it easy to perform simple checks or tests because you can execute commands without having to connect to the agent host by telnet or other means.

Figure 1‒21: Operations performed from JP1/IM - Manager

(a) Identifying the source and extent of an error

When an error occurs in the system, the icons representing the affected nodes change to error status in the Monitoring Tree window and Visual Monitoring window. From the upper level of the tree, check the monitoring nodes indicating error status, and identify which resources are likely to be affected by the error.

Figure 1‒22: Checking the affected resources

Guide information is a useful means of checking where a problem occurred. The guide function allows you to register operating know-how including troubleshooting procedures for specific problems, and examples of past situations in which certain errors have occurred. Although responding appropriately to whatever problems occur in a diverse range of resources is never easy, the guidance offered by the guide function goes some way toward reducing the system administrator's workload.

Important

Guide information must be registered before it can be viewed. For details about the guide function, see 5.8 Guide function in this manual and 6.6 Editing guide information in the JP1/Integrated Management 2 - Manager Configuration Guide.

Figure 1‒23: Troubleshooting advice provided by the guide function

(b) Identifying events that caused the error

After you have identified the node that is in error status, you can discover what event caused the problem.

Select the node that is in error status, and then click the Search Status-Change Events command. The Event Console window opens with the Search Events page displayed. This page lists the JP1 events that caused the node to change to error status.

Figure 1‒24: Identifying events that caused the error

(c) Investigating the error

After you have identified the node in which an error occurred, you can discover what event caused the problem. To locate the event, use the Central Console. By linking to the Central Console, you can investigate the nature of the error that triggered the JP1 event.