I.1 Using the SNMP trap converter to convert SNMP traps into events

(1) SNMP trapping in a cluster system

The SNMP trap converter operates only on a physical host. Also, it operates by using the NNM function linked with the starting up and shutting down of NNM. It therefore operates independently of JP1/Base failovers.

By default, JP1 events are registered in the event service on the physical host. To register JP1 events in the event service on a logical host, specify the event server name of the logical hosts for the imevt_server parameter in the action definition file for converting SNMP traps. However, if NNM is used in a non-cluster system, and that system is configured to directly register converted JP1 events to the logical host, the standby node cannot monitor the SNMP traps it receives.

The following figure illustrates how to configure a cluster system (where NNM is used) to directly register JP1 events to a logical host.

To use NNM in a cluster system, set up NNM on both the primary and secondary nodes, referring to I.2 Setting the SNMP trap converter. Register NNM and JP1/Base in the same cluster group.

If you are using NNM in a cluster system and JP1/Base in a non-cluster system (that is, these programs are being used on the physical hosts only), you must start JP1/Base on the physical host at both the primary and secondary nodes.

To Page Top

(2) Criteria for converting SNMP traps

The following criteria apply to SNMP trap conversion:

• Maximum line length in the definition files

  The length of each line in the definition files (imevtgw.conf, snmpfilter.conf, and trapd.conf) must not exceed 1,023 bytes.

• Enterprise name

  The enterprise name defined in the trapd.conf file must not begin with a hash mark, exclamation mark, or plus sign.

• Event name

  The event name defined in the trapd.conf file must not begin with an asterisk.

• Object ID

  The object ID defined in the trapd.conf file must not include an asterisk. Only SNMP traps whose object IDs completely match those defined in the trapd.conf file will be converted into JP1 events.

• Source list

  If you specify particular sources (nodes) in NNM by selecting Only specified sources in the Sources page of the Modify Events dialog box, which opens from the Event Configuration window, only the SNMP traps generated by those sources will be converted into JP1 events.

  You can also specify a file containing source names. If you use a file, you cannot use the hash mark to enter comment lines. Each source (node) must not exceed 511 bytes in length. Sources (nodes) do not support regular expressions.

• Message

  If the message acquired from the trapd.conf file contains any special "$ variables", the SNMP trap converter expands the $ variables to present the information contained in the SNMP trap. The $ variables supported by the SNMP trap converter are listed below. All other variables are output without being expanded when an SNMP trap is converted.

  

  $ variables are not expanded if there are no variable-related parameters in the action definition for converting SNMP traps (imevtgw.conf). To expand the $ variables, set an action definition for converting SNMP traps (imevtgw.conf). For details on how to do this, see I.4(1) Action definition file for converting SNMP traps (imevtgw.conf).

  The KAVA2108-E message is output if an error occurs when information is expanded from a $ variable. If you want to detect errors as JP1 events, monitor such errors using the log file trap, and make the KAVA2108-E message (output to the integrated trace log) the SNMP trap condition.

  The output message after expansion of the $ variables might differ from the message output by NNM. You can check the output messages in either of the following ways:

  • In JP1/IM - View, from the Tool Launcher double-click Network Management to launch the NNM window.

  • In JP1/IM - View, open the Event Details window, click the Monitor button to launch the NNM window, and examine the NNM alarm browser.

• Generic traps

  Generic traps can be converted by the SNMP trap converter.

  If generic traps are defined for JP1 event conversion in the filter file for converting SNMP traps (snmpfilter.conf), enterprise-specific generic traps are also converted as generic traps. If both generic traps and enterprise-specific generic traps are defined in the trapd.conf file, enterprise-specific generic traps will be converted as such in NNM, but as generic traps by the SNMP trap converter. As a result, the information displayed in JP1/IM - View might sometimes differ from the information displayed in NNM. To avoid this problem, add a definition for enterprise-specific generic traps to the filter file for converting SNMP traps (snmpfilter.conf). Examples of a generic trap and of an enterprise-specific generic trap are shown below.

  Example: Generic trap

  Enterprise name: snmpTraps

  Event name: SNMP_Link_Down

  Object ID: .1.3.6.1.6.3.1.1.5.3

  Example: Enterprise-specific generic trap

  Enterprise ID: hitachi

  Event name: HI_Link_Down

  Object ID: .1.3.6.1.6.3.1.1.5.3.1.3.6.1.4.1.116

Note that the following SNMP traps used internally in NNM cannot be converted into JP1 events:

• OpenView.OV_Ack_Alarm

• OpenView.OV_Delete_Alarm

• OpenView.OV_Unack_Alarm

• OpenView.OV_ChgSev_Alarm

• OpenView.OV_ChgCat_Alarm

• Events generated by the ECS engine (OpenView.OV_Corr_Indic, and so on)

For details, see the NNM documentation.

To Page Top

(3) Note

• An error message is displayed and the event data is discarded if a connection to the event service fails when the SNMP trap converter attempts to convert an SNMP trap to a JP1 event.

To Page Top