Job Management Partner 1/Performance Management User's Guide

[Contents][Glossary][Index][Back][Next]

11.4 Configuration of MIB objects

The following figure shows the configuration of MIB objects for SNMP traps in Performance Management.

Figure 11-4 MIB object configuration

[Figure]

The following table describes the contents of MIB objects in Performance Management.

Table 11-8 Contents of MIB objects

Object ID Contents
.1.3.6.1.4.1.116.5.17.12.2.1 PFM - Agent or PFM - RM instance numbers (ASCII codes of instance numbers)
.1.3.6.1.4.1.116.5.17.12.2.3 Report information specified at the definition of alarms
pfm-manager-host-name@report-id
.1.3.6.1.4.1.116.5.17.12.2.6 Names of the Performance Management categories and conditional expressions of alarms
.1.3.6.1.4.1.116.5.17.12.2.7 Alarm values#1
.1.3.6.1.4.1.116.5.17.12.2.8 Alarm conditions
  • NORMAL
  • WARNING
  • CRITICAL
.1.3.6.1.4.1.116.5.17.12.2.9 PFM - Agents or PFM - RM product-type identifiers
For example, for PFM - Agent for Platform (Windows), the value is Windows; for PFM - Agent for Oracle, the value is ORACLE.
.1.3.6.1.4.1.116.5.17.12.2.10 Management units#2 that cause alarms
.1.3.6.1.4.1.116.5.17.12.2.12
  • In PFM - Agent
    Instance names of PFM - Agents
  • In PFM-RM
    Device ID of the remote agent or group agent
.1.3.6.1.4.1.116.5.17.12.2.13 Contents of message texts specified at the definition of alarms#3
.1.3.6.1.4.1.116.5.17.12.2.14 Names of alarm tables
.1.3.6.1.4.1.116.5.17.12.2.15 Names of alarms
.1.3.6.1.4.1.116.5.17.12.2.16
  • In PFM - Agent
    Names of PFM - Agent hosts
  • In PFM-RM (remote agent)
    Monitored host name
  • In PFM-RM (group agent)
    Primary host name (PFM-RM host name)
.1.3.6.1.4.1.11.2.17.2.2.0
  • In PFM - Agent
    Names of PFM - Agent hosts
  • In PFM-RM (remote agent)
    Monitored host name
  • In PFM-RM (group agent)
    Primary host name (PFM-RM host name)

#1
Multi-instance records operate as follows:
  • When any value in the warning or abnormal condition is detected in target instances:
    User-defined messages specified when the alarm was defined are displayed in the message text (MIB object ID: 1.3.6.1.4.1.116.5.17.12.2.13). In this case, the data element value that causes event occurrence is the instance value in which an excess threshold value is first detected.
  • When conditions return to normal from abnormal or warning:
    Nothing is specified in the message text even though normal events are issued because all the instance values become normal and the value that causes event occurrence is not determined. In this case, <OK> is specified as a value of the data element that causes the event occurrence.

#2
Do not use this value during operations because Performance Management uses the value internally.

#3
Values displayed in message text are as follows:
  1. Alarm updated/deleted: An alarm definition has been updated or deleted.
  2. Alarm deactivated: An alarm has been deactivated.
  3. Alarm cleared: An alarm bind has been cleared.
  4. Alarm expired: Current time is out of the alarm evaluating hours.
  5. message-defined-by-user: An alarm condition has changed to abnormal or warning from normal, or an alarm condition has changed to normal from abnormal or warning in a single instance record.
  6. None: An alarm condition has changed to normal from abnormal or warning in a multi-instance record.
In the above messages 1 - 4, (N/A) is specified as a value of the data element that causes event occurrence.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.