le Cancel Close Figure 12.29 Trap parser configuration. AdventNet - Load Trap Parsers From MIB Specify MIB File - Be sure to set Severities after Loading Parsers Load MIB Filename /mibs/ Create Parsers Close Figure 12.30 Loading trap parsers from an MIB is an easy way of configuring a trap parser. Groups: The managed objects can be grouped together and given as match cri- teria in this field. Trap OID: The trap type of each SNMP v2c and v3 trap could be uniquely identi- fied by using the trap OID that is provided with the trap PDU. This trap OID can be used to define the matching criteria. The trap parser would be applied only to traps whose trap OID starts with the given trap OID value. Event object attributes are defined by the values given in the trap parsers. If the user knows something of the event they are seeking, then selecting some values is useful in identifying the failure quickly. Fields include: Severity: Sets the state of the event, which determines the severity shown in the event browser. This severity determines how a fault/alert may be affected by this 12 Fault Management event. For a given failure object, the severity specified for the event will be respon- sible for the severity of the corresponding fault/alert. Message: Corresponds to the "text" field of the event object. The value specified here will be copied on to the "text" field of the event object created by this trap parser. Failure Object: The key of the event object. This field affects how the event is processed by the fault management system. Appropriate processing by the trap parser will ensure that the failure object reflects the exact problem as notified. This can be used for tracking down the problems quickly and identifying the objects involved, rather than simply reporting raw events. Domain: Used to specify the domain name for the event. This field may or may not be used depending upon the application. Category: Used to categorise events and alerts. Network: Used to specify the name of the network from which the event was rais