he parser or not. Once a matching trap parser found, an event will be generated by applying the trap parser and no other trap parsers will subsequently be applied to that trap. Users can enable or disable any particular parser. 12 Fault Management AdventNet Trap Parser Configuration Configured Trap Parser List coldStart coldStart Match Criteria warmStart Nodes egpNeighborLoss Groups authenticationF ailure Enterprise 1.3.6.1.2.1.11 Generic Type Specific Type Click he to configure for Severity Major Message Click Message Failure Object $Agent Domain Category $Community Network $Source Source $Agent Group Name Help URL $GenericType-$SpecificType.ht Add Trap Parser Modify Trap Parser Delete Trap Parser Update Close Load From MIB Load From File Save To File Cancel Figure 12.4 Trap parser configuration. Table 12.1 Trap parser input fields. Parameter Description Nodes Nodes to which a trap parser is to be applied are specified by the Agents' IP addresses Groups If managed objects can be grouped, then it makes sense to allow specification of groups to which a trap parser is to be applied Enterprise This field is used to specify the enterprise OID of the SNMP v1 trap. The parser will be applied only if the trap enterprise field starts with the value specified Generic Type Each SNMPv1 trap has a Generic Type number. Users can specify the Generic Type number in this field so that the trap parsers will be applied only to corresponding traps Specific Type Each SNMPv1 trap has a Specific Type number and this can be used as a match criterion for incoming traps Trap OID Trap OID is an identification number which comes along with the Trap PDU. This is used only for SNMPv2c and v3 traps OSS for Telecom Networks 12.7.2 Trap API Trap parsers can be configured using the trap API. A set of APIs is provided to handle dynamically the features of trap filters and parsers. Using API methods, it is possible to automate the addition and deletion of parsers and filters and also automate how their properties are set. Trap API methods are publ