Administer > Configure Incidents > Configure Trap Logging > Include Custom Incident Attributes in Your Log Message Format

Include varbinds in Your Log Message Format

You can use varbinds in your message format to extend the amount of information presented. SNMP trap varbinds are identified by the Abstract Syntax Notation value (ASN.1).

To include a varbind in your Trap Logging Configuration message format, type the dollar-sign character ($)plus any of the following

  • Varbind position number or asterisk (*) to include all varbind values
  • Object identifier (oid) of the varbind (useful when the varbind position number is not consistent among vendors)

The following table presents some example formats with the subsequent output.

Example Incident Message Formats
Example Message Format Output in Incident View
Possible trouble with $3 Possible trouble with <varbind 3>
Possible trouble with $11 Possible trouble with <varbind 11>

Possible trouble with $77 (where the varbind position 77 does not exist)

Possible trouble with <Invalid or unknown varbind> 77
Possible trouble with $3x Possible trouble with <varbind 3>x
Possible trouble with $1.2.3.4.5 Possible trouble with <value of the varbind with oid of 1.2.3.4.5>

Tip NNMi provides an error message when a varbind cannot be found. For example, if you enter an unavailable varbind position, name, or object identifier (oid), NNMi returns an "Invalid or unknown varbind" error message.