5.9.2 Example of creating a general monitoring object (CPU monitoring by JP1/Cm2/SSO)
If you want to monitor items that are not supported by the automatic generation of monitoring trees (for example, you want to use JP1/Cm2/SSO version 8 or earlier to monitor CPUs), you need to create a monitoring object manually.
- Organization of this subsection
(1) What you need to know before creating the object
If you want to use JP1/IM to monitor products that output SNMP traps, such as JP1/Cm2/SSO version 8 or earlier, you need to convert SNMP traps to JP1 events first. This is necessary because Central Scope uses the attribute names and attribute values of JP1 events as keys for monitoring objects.
You can use JP1/Base SNMP trap conversion to convert SNMP traps to JP1 events. With SNMP trap conversion, you can map the SNMP fields to the attributes of JP1 events.
The following table describes the correspondence between the attributes of a JP1 event that is converted from an SNMP trap and the fields of the SNMP trap.
JP1 event created as a result of conversion |
SNMP trap to be converted |
||
---|---|---|---|
Basic attribute |
Message |
PDU Type |
|
Extended attribute |
Common information |
SEVERITY |
specific trap |
-- |
-- |
||
Program-specific information |
SNMP_OID |
Enterprise |
|
SNMP_DATE |
Time stamp |
||
SNMP_SOURCE |
Agent address |
||
SNMP_SEVERITY |
Specific trap |
||
SNMP_URL |
-- |
||
SNMP_VARBIND_RESULT |
-- |
||
SNMP_VARBIND_NUM |
-- |
||
SNMP_VARBIND1 |
Value of Data 1 in the variable binding |
||
SNMP_VARBIND2 |
Value of Data 2 in the variable binding |
||
(Omitted) |
(Omitted) |
||
SNMP_VARBIND28 |
Value of Data 28 in the variable binding |
For details about SNMP trap conversion, see the JP1/Base User's Guide.
(2) Confirmation before creating a monitoring object
Confirm the following before you create a monitoring object for monitoring CPUs.
-
The setup of JP1/Cm2/SSO version 8 or earlier has been completed on the agents, and JP1 events are sent to the manager.
In Central Console, in the Event Console window, make sure that the events for monitoring CPUs by JP1/Cm2/SSO version 8 or earlier are displayed.
-
On agents on which JP1/Cm2/SSO version 8 or earlier monitors CPUs, the setup for linkage with Central Scope has been completed.
When you automatically generate a monitoring tree in Central Scope, make sure that an SSO Monitoring monitoring object is generated and that the status of the object changes when JP1 events are received.
(3) Creating a monitoring object (CPU monitoring)
To create a monitoring object:
-
In the Monitoring Tree (Editing) window, from the menu bar, choose Edit, and then Create New Monitoring Node.
The Create New Monitoring Node window appears.
-
Enter the node name, select the node type, and then click the OK button.
Table 5‒7: Settings in the Monitoring node name and Monitoring node type Item
Setting
Monitoring node name
Enter any name.
We recommend a name that is easily recognizable. In this example, enter Category Monitoring (SSO).
Monitoring node type
Click Monitoring object. From the drop-down list, select User Monitoring Object.
The monitoring object Category Monitoring (SSO) is added to the monitoring tree.
(4) Setting up the monitoring object (CPU monitoring)
To set up the monitoring object:
-
Select the created monitoring object (Category Monitoring (SSO)). From the menu bar, choose Edit, and then Properties.
The Properties window appears.
-
In the Properties window, choose the Status-Change Condition tab. On the Status-Change Condition page, click the Add button.
The Status-Change Condition Settings window appears.
-
In the Status-Change Condition Settings window, specify a common condition, individual conditions, and other items.
The status of the selected monitoring node changes when JP1/IM - Manager receives JP1 events. Specify the types of JP1 events that cause the monitoring node status to change.
Enter a status change condition and then click the OK button. (When you click the OK button, the Status-Change Condition page returns.) If you want to enter another status change condition, click the Add button again and enter a condition in the Status-Change Condition Settings window.
In the Status-Change Condition Settings window, enter or select values as described in the following tables.
Table 5‒8: Settings in the Status-Change Condition Settings Condition name (any)
Status
Common condition
CPU usage rate alert event (SSO)
Alert
Resource alert event (SSO)
CPU usage rate error event (SSO)
Error
Resource error event (SSO)
For each status change condition, specify individual conditions as follows. Click Add each time you add an individual condition.
Table 5‒9: Settings in the Status-Change Condition Settings (individual conditions section) Monitoring node attribute name
Attribute name
Attribute value (example)
Condition
Category name
E.SNMP_VARBIND2
SSO
Match
Group name
E.SNMP_VARBIND3
Computer
Match
Resource name
E.SNMP_VARBIND4
CPU usage rate#1
Match
Event-issuing host
E.SNMP_VARBIND11
mgr-svr1#2
Host name comparison
Host name
E.SNMP_VARBIND12
agt-srv1#3
Host name comparison
-
When you have finished the settings, on the Status-Change Condition page, click the OK button.
In the Monitoring Tree (Editing) window, from the menu bar, choose File, and then Update Server Tree. Check whether the monitoring node has been added to the monitoring object database of Central Scope.
You can also use a Category Monitoring (SSO) system-monitoring object to create the CPU Usage Rate Management (SSO) monitoring object for JP1/Cm2/SSO version 8 or earlier. After you create a Category Monitoring (SSO) system-monitoring object, add the required individual conditions to the status change condition.
- Important
-
For JP1/IM to monitor JP1/Cm2/SSO version 8 or earlier, all JP1/Cm2/SSO and JP1/Base on the agents must be version 7 or 8.
If JP1/Cm2/SSO and JP1/Base on the agents are version 6, JP1/IM can monitor them. However, JP1/IM cannot automatically collect information from JP1/Cm2/SSO or JP1/Base, which results in extensive manual work in addition to the above procedure. For this reason, we do not recommend monitoring of JP1/Cm2/SSO version 6.
Note that the product name of JP1/Cm2/SSO is JP1/PFM/SSO for version 7 and JP1/SSO for version 6.