12.10.3 Example of agent maintenance
The following describes an example of implementing maintenance on a specific agent.
When a problem needing urgent attention occurs on an agent, events related to the issue should be monitored, but events occurring after maintenance is underway will not be required. Before maintenance work starts, set common exclusion-conditions in an event acquisition filter that eliminate redundant events, so that JP1/IM - Manager can continue monitoring the other hosts. The figure below shows an example of implementing maintenance on a specific agent.
|
|
![[Figure]](GRAPHICS/CS071700.GIF)
The workflow is described below, following the numbers in the figure:
-
An error occurs on agent B being monitored by JP1/IM, and a JP1 event is issued.
-
The JP1 event is relayed through JP1/Base and through the event acquisition filter in JP1/IM - Manager on the manager, and is displayed in JP1/IM - View.
-
To carry out maintenance tasks on host B, enable the predefined common exclusion-conditions for host B maintenance (a set of common exclusion-conditions which exclude JP1 events issued from host B from acquisition by JP1/IM - Manager).
The common exclusion-conditions can be switched from the JP1/IM - View System Environment Settings window or Event Acquisition Conditions List window, or by using the jcochfilter command.
-
Because the common exclusion-conditions for host B maintenance are now in effect, JP1 events issued from host B are not acquired by JP1/IM - Manager (they do not appear in the JP1/IM - View windows).
-
Carry out host B maintenance.
-
After maintenance is completed, disable the common exclusion-conditions from the JP1/IM - View System Environment Settings window or Event Acquisition Conditions List window, or by using the jcochfilter command.
For the procedure for enabling or disabling common exclusion-conditions, see 5.8 Switching the event acquisition filter in the Job Management Partner 1/Integrated Management - Manager Administration Guide.