Hitachi

JP1 Version 12 JP1/Performance Management Reference

H.2 Configuration of MIB objects in SNMP traps

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

Figure H‒1: MIB object configuration

[Figure]

The table below shows the detailed MIB objects under performanceManagementTrapMibs(2) that are used in Performance Management. These MIB objects are stored in order in the variable-bindings field of the SNMP trap.

Table H‒2: Contents of MIB objects under performanceManagementTrapMibs(2)

No.

Object ID

Object name

MIB object attributes in the SMIv1 OBJECT-TYPE macro

Contents

1

.1.3.6.1.4.1.116.5.17.12.2.1

instanceNumber

  • SYNTAX: INTEGER

  • MAX-ACCESS: read-only

  • STATUS: mandatory

PFM - Agent or PFM - RM instance numbers (ASCII codes of instance numbers)

2

.1.3.6.1.4.1.116.5.17.12.2.3

informationInReport

  • SYNTAX: OCTET STRING

  • MAX-ACCESS: read-only

  • STATUS: mandatory

Report information specified at the definition of alarms

pfm-manager-host-name@report-id

3

.1.3.6.1.4.1.116.5.17.12.2.6

categoryNameAndConditionalExpression

Names of the Performance Management categories and conditional expressions of alarms

4

.1.3.6.1.4.1.116.5.17.12.2.7

alarmValue

Alarm values#1

5

.1.3.6.1.4.1.116.5.17.12.2.8

alarmStatus

Alarm conditions

  • NORMAL

  • WARNING

  • CRITICAL

6

.1.3.6.1.4.1.116.5.17.12.2.9

productType

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.

7

.1.3.6.1.4.1.116.5.17.12.2.10

managementUnit

Management units#2 that cause alarms

8

.1.3.6.1.4.1.116.5.17.12.2.12

instanceName

  • In PFM - Agent

    Instance names of PFM - Agents

  • In PFM-RM

    Device ID of the remote agent or group agent

9

.1.3.6.1.4.1.116.5.17.12.2.13

alarmMessage

Contents of message texts specified at the definition of alarms#3

10

.1.3.6.1.4.1.116.5.17.12.2.14

alarmTableName

Names of alarm tables

11

.1.3.6.1.4.1.116.5.17.12.2.15

alarmName

Names of alarms

12

.1.3.6.1.4.1.116.5.17.12.2.16

hostName

  • 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:

    If the function for measurement value output at alarm recovery is enabled, the user-defined message set in the alarm definition is displayed as the message text. In this case, the current measurement value of the instance that caused the last abnormal or warning alarm to be issued is set as the value of the data element that triggered the event.

    If the function for measurement value output at alarm recovery is disabled, a normal event is issued. However, because all instance values are in the normal range and there is no specific value that causes the event to be generated, nothing is displayed in the message text. In this case, <OK> is specified as a value of the data element that causes the event occurrence.

    For details about the function for measurement value output at alarm recovery, see the description about setting the function for measurement value output at alarm recovery in the JP1/Performance Management User's Guide.

#2

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

#3

Values displayed in message text are as follows:

When the function for measurement value output at alarm recovery is enabled:

  • Alarm updated/deleted

  • Alarm deactivated

    The meaning of the above messages depends on the setting of the alarmCompatibleMode parameter in the initialization file (config.xml) that defines the operating environment for PFM - Web Console.

    For details about alarmCompatibleMode, see Initialization file (config.xml).

    If alarmCompatibleMode is not in the file:

    - Alarm updated/deleted: The alarm definition has been updated or deleted.

    - Alarm deactivated: The alarm is now inactive.

    If alarmCompatibleMode is true:

    - Alarm updated/deleted: The alarm definition has been deleted.

    - Alarm deactivated: The alarm has become inactive, or the alarm was updated and its previous status was reset.

    If alarmCompatibleMode is false:

    The meaning of the messages depends on the version of PFM - Manager, as follows:

    In PFM - Manager version 09-10-19 or later:

    - Alarm updated/deleted: The alarm definition has been updated or deleted.

    - Alarm deactivated: The alarm has become inactive, or the alarm was updated and its previous status was reset.

    In versions of PFM - Manager earlier than 09-10-19:

    - Alarm updated/deleted: The alarm definition has been deleted.

    - Alarm deactivated: The alarm has become inactive.

  • Alarm cleared: The alarm is unbound (including importing the alarm table where the alarm occurred from the GUI) or PFM - Agent or PFM - RM was stopped while PFM - Agent or PFM - RM is in an abnormal or warning status.

  • Alarm expired: Current time is out of the alarm evaluating hours.

  • User-defined message: The alarm status has changed.

When the function for measurement value output at alarm recovery is disabled:

  • Alarm updated/deleted

  • Alarm deactivated

  • The meaning of the above messages depends on the setting of the alarmCompatibleMode parameter in the initialization file (config.xml) that defines the operating environment for PFM - Web Console.

    For details about alarmCompatibleMode, see Initialization file (config.xml).

    If alarmCompatibleMode is not in the file:

    - Alarm updated/deleted: The alarm definition has been updated or deleted.

    - Alarm deactivated: The alarm is now inactive.

    If alarmCompatibleMode is true:

    - Alarm updated/deleted: The alarm definition has been deleted.

    - Alarm deactivated: The alarm has become inactive, or the alarm was updated and its previous status was reset.

    If alarmCompatibleMode is false:

    The meaning of the messages depends on the version of PFM - Manager, as follows:

    In PFM - Manager version 09-10-19 or later:

    - Alarm updated/deleted: The alarm definition has been deleted.

    - Alarm deactivated: The alarm has become inactive, or the alarm was updated and its previous status was reset.

    In versions of PFM - Manager earlier than 09-10-19:

    - Alarm updated/deleted: The alarm definition has been updated or deleted.

    - Alarm deactivated: The alarm is now inactive.

  • Alarm cleared: The alarm is unbound (including importing the alarm table where the alarm occurred from the GUI) or PFM - Agent or PFM - RM was stopped while PFM - Agent or PFM - RM is in an abnormal or warning status.

  • Alarm expired: Current time is out of the alarm evaluating hours.

  • User-defined message: The alarm status has changed in relation to a single-instance record, or has changed to abnormal or warning status in relation to a multi-instance record.

  • None: An alarm condition has changed to normal from abnormal or warning in a multi-instance record.

For the above four items, (N/A) is set as the value of the data element that caused the event to be issued.

To Page Top

Copyright (C) 2019, 2021, Hitachi, Ltd.

Copyright (C) 2019, 2021, Hitachi Solutions, Ltd.

(C)opyright 2000-2009, by Object Refinery Limited and Contributors.