Set SNMP rule conditions properties

• Rule Description: Type a description that will help you remember what this rule does. This description is visible in the rules list.
• Node: If you only want to match SNMP events from a specific node, type the FQDN, the primary node name, or the IP address. Give multiple entries with the OR operator (for example, celery.veg.com|broccoli.veg.com), or leave blank for all nodes. You can also use variable <$OPC_MGMTSV>.
• Event Information
  Select this option to change the way in which the event information appears. The option you choose determines what fields are visible in the window and what information you have to supply. If you want to match a specific event, select Event Object ID. If you want to match a range of events or specify a specific event in SNMPv1 Notation, select the SNMPv1Notation option.
  • Event object ID

    Type the complete Event Object Identifier for the SNMP event that you want to match.

    For example: .1.2.6.1.4.1.11.2.17.1.0.40000001

  • SNMPv1 Notation

    You can type the complete event object ID in SNMPv1 format or you can specify only part of the identifier. For example, by specifying only the Enterprise ID, you can match all events with a specific Enterprise ID.

  • Enterprise ID

    Type in the enterprise ID for incoming SNMP traps to be compared with this condition. The enterprise ID is a vendor-specific identifier for the trap. Standard HPOM pattern-matching syntax may not be used in this field; however, it is possible to match a range of objects by entering only a prefix. For instance, the pattern:

    .1.3.6.1.4.1.11.2.17

    would match:

    .1.3.6.1.4.1.11.2.17.1

    .1.2.6.1.4.1.11.2.17.2

    and so on.

  • Generic ID

    From the list, select the appropriate Generic Trap ID. Possible values are:

    • (0) ColdStart
    • (1)WarmStart
    • (2) LinkDown
    • (3) LinkUp
    • (4) Authentification
    • (5) EgpNeighborLoss
    • (6) EnterpriseSpecific
    • (7) don't care
    If you select (6) EnterpriseSpecific, you can type in the specific trap ID. Select don't care to intercept any kind of trap.
  • Specific ID

    Type in the specific trap ID if you have selected (6)EnterpriseSpecific in Generic Trap. Enterprise-specific SNMP traps can be implemented by vendors on their specific network devices. The specific trap ID is used to identify the source of the trap.

  NOTE:
  The SNMP syntax used by the editor requires that the trap string being with a point. If you forget to add the point at the beginning of the string, the program will add it for you when you save the policy.
• SNMP V2 Traps

  Follow these steps to specify that the Windows agent can receive SNMPV2 traps:

  1. Disable the Windows SNMP Service/SNMP Trap Service.
  2. Add the following line to opcinfo:

     SNMP_SESSION_MODE NNM_LIBS

  3. Restart the agent.
• Variable Bindings
  Select the variable bindings you want the policy to monitor, and write one or more match patterns for each binding. Standard HP Operations pattern-matching rules can be used when matching variable bindings.

  $1 represents the first variable binding in the event, $2 the second variable, and so on. Use the matching options button to set the case sensitivity and field separators for all variable bindings.

1. Right-click the policy and select All Tasks Edit...
2. Select Rules.
3. Select the rule for which you want to modify the conditions.
4. Select Modify.
5. Select Condition and type the conditions for this rule.

Related Topics:

• SNMP Variables
• Quick start: how to create a policy