Trap Logging Configuration Form

The name is used to identify the logging configuration and must be unique. Use a name that will help you to remember the purpose or kind of SNMP trap for which you are configuring this log information.

Valid characters include alphanumeric, dash (-), slash (/), colon (:), and underscore(_).

Specify the Object Identifier of the trap you want to log.

You can obtain the OID value from the trap.log or trap.csv log file.

Click here for more information about determining a trap OID for an undefined trap.

1. Export the trap.csv file to an Excel spreadsheet.

2. Search for NO TRAP LOGGING CONFIGURATION FMT FOR.

   Tip This text should appear in the Formatted Message column.

3. Look for the trap OID value that follows this message.

   Tip You can also navigate to the OID column to identify the OID for this trap.

When using the wildcard (*) character in the Trap Object ID (OID) attribute, note the following:

• The OID must be unique.
• Only one wildcard character is permitted within the Trap Object ID (OID) attribute.
• The wildcard must appear at the end of an OID. For example .1.3.6.1.4.1.* is valid; however, .1.3.6.1.4.*.2 is NOT valid.
• NNMi permits wildcards only in OIDs beginning with .1.3.6.1.4 (private MIBs).
• The wildcard character is not valid for an SNMPv1 generic trap because these traps do not begin with .1.3.6.1.4.
• When checking whether an SNMP Trap Incident Configuration exists, NNMi’s TrapFilter uses only implicit matching when checking generic SNMPv1 traps OIDs. See About the Trap Service Stages for more information about TrapFilter.

• NNMi matches the OID value using the longest match. Specific OID matches take precedence over an OID that is matched using the wildcard character. Click here for an example:

  The following table provides an example of precedence between a specific OID and one that includes a wildcard. This example also illustrates how NNMi uses the longest match.

  Example of Matching Incoming SNMP Traps Using Specific and Longest Match Criteria

  SNMP OID Attribute Configuration	Incoming SNMP Trap	Match Criteria
  .1.3.6.1.4.1.2.3	.1.3.6.1.4.1.2.3	Specific OID takes precedence over the wildcard OID configuration.
  .1.3.6.1.4.1.*	.1.3.6.1.4.1.2	The wildcard OID takes precedence because it is the longest match.
  .1.3.6.1.4.*	Using the specific OID and longest match criteria, this configuration is not the best match for these incoming traps.	See above.

• NNMi handles each OID as if it contains an implicit wildcard. For example, when NNMi receives a trap whose OID is .1.3.6.1.6.3.1.1.5.4.100, NNMi logs the trap as SnmpLinkUp (.1.3.6.1.6.3.1.1.5.4) and generates an SNMPLinkUp incident.
• If a trap's OID matches both an implicit and explicit wildcard, the longer one is used. If the length is the same, NNMi uses the implicit OID. Click here for an example:

  The following table provides an example of precedence between implicit and explicit wildcards.

  Example of Matching Incoming SNMP Traps Using Implicit and Explicit Wildcard Criteria

  SNMP OID Attribute Configuration	Incoming SNMP Trap	Match Criteria
  .1.3.6.1.4.1.2.3.*	.1.3.6.1.4.1.2.3.4	The longest OID takes precedence.
  .1.3.6.1.4.1.2	.1.3.6.1.4.1.2.3	The implicit OID takes precedence.
  .1.3.6.1.4.1.*	Using the length and implicit criteria, this configuration is not the best match for these incoming traps.	See above.

If the Enabled options is selected, NNMi logs this SNMP Trap to the trap.log and trap.csv log files for the nodes in the specified Node Group.

If the Disabled option is selected, NNMi does not log the specified SNMP Trap configuration to the trap.log and trap.csv log files in the specified Node Group.

Specify the information you want NNMi to include in the SNMP Trap's Message attribute value. You can use any combination of valid parameter strings and Custom Incident attributes to configure the Message.

For more information, see:

Valid Parameters for Trap Logging Messages

Include varbinds in Your Log Message Format

Specifies that you want the values from the associated SNMP Trap Incident Configuration to be used for the following attributes:

• Severity
• Category
• Family
• Incident Message Format

If selected , you are not able to provide values for the attributes listed

The Severity represents the seriousness calculated for the SNMP trap. Use the Severity attribute to specify the Severity that should be assigned to the SNMP trap when it appears in the trap.log and trap.csv log files.

Possible values are described in the following table.

See Monitor Incidents for Problems for more information about these severity values.

The Category attribute helps you organize your SNMP Traps. Select the category that you want to be associated with this SNMP Trap when it appears in the trap.log and trap.csv log files.

Each of the possible Category values is described in the following table.

You can use Family values to further categorize the types of SNMP Traps that might be generated. Select the Family that you want to be associated with this SNMP Trap when it appears in the trap.log and trap.csv log files.

Each of the possible Family values are described in the following table.

See Author form for important information.

Click the  Lookup icon and select Show Analysis to display details about the currently selected Author, select  Quick Find to access the list of existing Author values, or click  New to create one.