MIb Browser Trap Receivers

Trap Browser

Trap Browser is used for receiving the traps. Using this you can view the incoming traps to the specified port. The traps can be sent from any host. The port number and the community name has to be set in the Trap Browser. The trap originator should send the trap to the port no specified in the Trap Browser.

The Trap Browser displays the trap information in a table format.

The trap browser has the following four columns:

  • Class - displays the severity information of the received traps (eg - Info, critical, warning etc)
  • Source - source from which the trap originated
  • Date - the time stamp of the received trap (date and time)
  • Message - the received trap message

All the received traps are displayed in rows. Clicking on any of the column headings pops up a dialog box which contains more additional information on the received trap. Right-clicking on the any of the column headings pops up a menu "Delete the selected Rows", which can be used to delete any of the selected rows. Clicking on the ParserEditor opens up a TrapParser which is used to parse the trap events.

Trap Parser

The configuration of the Trap Parsers can be done by the below steps:

  • Create a empty file by the name trap.parser in the MibBrowser directory.
  • Load the file in the trap parser by clicking the browse button in the "Load Traps From file" field.
  • Configure the trap parser.
  • The new trap to be added should not be in the same name of traps already existing in the trap list.
  • If the MIB file loaded in the MibBrowser has traps specified in it, then the traps are loaded automatically in the trap list.

The trap parser is used to configure and parse the trap events. Since Traps typically contain cryptic information not easily understandable to the users, trap parsers are required to translate or parse traps into understandable information.

Trap Parsers files

Parsing traps is achieved by configuring a list of trap parser files. Only one trap parser file can be applied to a given trap. The match criteria in a parser determines whether a specific trap matches a trap parser. The search for matching trap parsers is done from the trap parsers list starting at the top. Once a matching trap parser is found, an event is generated and no other trap parsers will be used on that trap.

Match Criteria

The match criteria determines whether the trap will be parsed by the given trap parser. All fields must match for the trap parser to be applied to a trap. The three fields are:

Enterprise Field

The enterprise field is the SNMP enterprise identifier in the trap, which is used to uniquely identify traps for a particular application. If you specify this field, the parser will only be applied if the trap enterprise field starts with the enterprise field you specify. The only exception is when the enterprise field is left blank, in which case the trap will be allowed to be parsed.

Generic Type

Each trap should specify one among the following:

  • coldstart
  • warmstart
  • linkdown
  • llinkup
  • authenticationfailure
  • egpneighborloss
  • enterprisespecific

Specific Type

Each trap has a specific type number. This number must be specified for the trap parser, and only when this matches, the trap parser be applied to a trap. The only exception is when the specific field is left blank or filled with negative value , in which case the trap will be allowed to be parsed

Setting Trap Parser Parameters

The following are some important fields and information on how to configure them for a given trap.

  • name: The name of the parser
  • severity: This is used to specify the state of an event, which determines the severity shown in the ListTraps.This severity determines how a fault may be affected by this event. Any one of the following needs to be assigned.
    • All
    • Critical
    • Major
    • Minor
    • Warning
    • Clear
    • Info , by default info will be assigned.
  • textDefn: This is the message text seen for this event in the ListTraps and logs.
  • categoryDefn:This is a type of the trap that can be used to categorize trap events.
  • nodeDefn: This enables using a node value for the event .
  • networkDefn, domainDefn, sourceDefn: These are all typically the source system for a given event.
  • helpDefn: The associated document for this trap
  • ST: This is the specific type of the trap.
  • GT: This is the generic type of the trap.
  • enterprise: This is the enterprise oid of the trap.

Trap Parser Customization

In Trap Parser the match criteria can also be customized to parse based on an oid and value or the agent Address and port number. For example to parse the oid and value:

  • Enter the OID and value in the respective field.
  • Press Add of the OID lists.
  • Parse the agent address and port address by doing the following steps:
    • Enter the ip address and the port number in the respective fields.
    • Press Add to add to the agent list.
      Note : The agent port if zero, will accept all the ports.
  • Enter the generic -type and specific -type and enterprise oid if necessary.
  • If the above fields are not required to be matched then:
    • generic-type will be "-"
    • specific -type will be 0
    • enterprise oid field will be blank
  • Add the trap parser setting in to the Trap Parser list as above. After configuring the parser settings, store the configurations in a file, using the Save option.
  • Run the Trap Browser.