5.2.2 Removing hosts undergoing maintenance from the items to be monitored

Whenever you restart a server on a host that is undergoing maintenance, a large number of events not needed for system monitoring are issued and displayed in the event list, making it difficult to check necessary events.

To avoid displaying unnecessary events in the event list, in advance remove hosts undergoing maintenance from the items to be monitored. With common exclusion-conditions, you can prevent actions from being executed while you continue monitoring events.

[Figure]

Important

Note:

If you need to perform maintenance on an entire system that includes JP1/IM - Manager, perform the maintenance in the order of higher hosts to lower hosts. If you start maintenance from lower hosts, the events that can be viewed in JP1/IM - View before JP1/IM - Manager stopped might be different from those after JP1/IM - Manager starts.

Keywords:

item, filter, common exclusion-condition, specific, host

Tip:

To remove, from the items to be monitored, the events that are not predefined in common exclusion conditions but become unnecessary while the system is operating:: After system monitoring starts, events that are not predefined in common exclusion conditions but become unnecessary while the system is operating might be issued. Use additional common exclusion conditions in filters to remove, from the items to be monitored, events that become unnecessary while the system is operating. Additional common exclusion conditions are exclusion conditions that are defined by using monitored events while the system is operating. For details, see 4.2.7 (3) Additional common exclusion-conditions in the Overview and System Design Guide, and 6.5.4 Setting an additional common exclusion-condition to exclude a JP1 event from the monitoring target or action execution in the Administration Guide.

Organization of this subsection

(1) Using common exclusion conditions in a filter to temporarily stop hosts from being monitored
(2) Verifying that events from unmonitored hosts are not displayed

(1) Using common exclusion conditions in a filter to temporarily stop hosts from being monitored

To remove hosts undergoing maintenance from the items being monitored, you use common exclusion conditions in a filter. To set common exclusion conditions, you use the Common Exclusion-Condition Settings window of Central Console. You can also use common exclusion conditions to remove action-triggering events from the items being monitored.

Prerequisites

The JP1 user who wants to set common exclusion conditions in a filter must have JP1_Console_Admin permissions.

Procedure

In the Event Console window, select Options and then System Environment Settings. In the System Environment Settings window that appears, click the Editing list button to display the Event Acquisition Conditions List window.
In the Event Acquisition Conditions List, click the Add button in the Common exclusion-conditions groups area to display the Common Exclusion-Conditions Settings window.
Specify common exclusion conditions as described in the following figure:
Click the OK button in the Common Exclusion-Conditions Settings window.

The Event Acquisition Conditions List window appears.
Click the OK button in the Event Acquisition Conditions List window.

The System Environment Settings window appears.
On the General page, under Common exclusion-conditions groups in the Event acquisition conditions area, select the conditions you want to apply in the Apply column. Then, click the Apply button in the System Environment Settings window.

The specified conditions are defined.

Related topics

4.2.6 Defining filter conditions in the Overview and System Design Guide
14.9 Considerations for JP1/IM system-wide maintenance in the Overview and System Design Guide
5.2.4 Settings for event acquisition filters in the Configuration Guide
3.15 Common Exclusion-Conditions Settings window in the manual GUI Reference

To Page Top

(2) Verifying that events from unmonitored hosts are not displayed

After you have specified the common exclusion conditions for the filter, make sure that events from the unmonitored hosts are not displayed in the event list. This subsection describes how to verify that events issued on host 1 are displayed in the event list, and that events issued on hosts A and B are not displayed in the event list.

Prerequisites

The following conditions must be satisfied:

OS user mapping was configured according to 4.2.1 Configuring user mapping.
A basic configuration system was set up according to 4.1 What is IM Configuration Management?.

Procedure

In the Event Console window, click the Execute Command button. The Execute Command window appears.

Set the items in the Execute Command window as described below, and then click the Execute button.

Item	Setting
Command type	Select Command of managed host.
Event information to inherit	Clear the Inherit event information check box.
Target host	Enter the following: `hostA`
Command	Enter the following: In Windows: `"Base-path\bin\jevsend" -e SEVERITY=Warning -m Command executed from host A.` In Linux: `/opt/jp1base/bin/jevsend -e SEVERITY=Warning -m Command executed from host A.`

An event of severity level is Warning is issued on host A.

Repeat steps 1 and 2. Set the items in the Execute Command window as described below, and then click the Execute button.

Item	Setting
Command type	Select Command of managed host.
Event information to inherit	Clear the Inherit event information check box.
Target host	Enter the following: `hostB`
Command	Enter the following: In Windows: `"Base-path\bin\jevsend" -e SEVERITY=Warning -m Command executed from host B.` In Linux: `/opt/jp1base/bin/jevsend -e SEVERITY=Warning -m Command executed from host B.`

An event of severity level Warning is issued on host B.

Repeat steps 1 and 2. Set the items in the Execute Command window as described below, and then click the Execute button.

Item	Setting
Command type	Select Command of managed host.
Event information to inherit	Clear the Inherit event information check box.
Target host	Enter the following: `host1`
Command	Enter the following: In Windows: `"Base-path\bin\jevsend" -e SEVERITY=Warning -m Command executed from host 1.` In Linux: `/opt/jp1base/bin/jevsend -e SEVERITY=Warning -m Command executed from host 1.`

An event of severity level Warning is issued on host 1.

Verify that the event list contains the event issued on host 1, but does not contain the events issued on hosts A and B.

Related topics

3.1 Overview of the Event Console window in the manual GUI Reference
3.24.2 Event Attributes page in the manual GUI Reference
3.40 Execute Command window in the manual GUI Reference

To Page Top