ewing trap filter details ordering trap filters saving configuration. OSS for Telecom Networks Trap Filter Configuration (trap.filters) The filters will be invoked in the same order as listed in the table. Drag and Drop to change the order of the filters. Use reload option to load TrapFilter classes again in the WebNMS server at runtime. Filter Name Class Name LinkDownSnmpV1 test.LinkUpDownTrapFilter LinkUpSnmpV2c st.LinkUpDownTrapFilter LinkDownSnmpV2c LinkUpDownTrapFilter LinkUpSnmpV1 (test.LinkUpDownTrapFilter Enabled Filters Disabled Filters Modify Delete Close Figure 12.3 Trap filter configuration. 12.7.1 Trap Parser Configuration If a trap filter returns a trap PDU, then the traps may be parsed to generate mean- ingful events. A tool is provided for configuring trap parsers. Options available with the Trap Parser Configuration are Add Trap Parser, Modify Trap Parser, Delete Trap Parser, Save To File, Load From MIB and Load From File. Rather than specifying the match criteria manually, an MIB with defined traps can be translated to trap parsers by loading from an MIB or from some other file. The Configuration of Trap Parser involves setting trap parser parameters and match criteria, defining the parameters for the output event object and configuring the trap parser list. Table 12.1 lists the trap parser configurable parameters. The output of the trap parser is an event object whose attributes are defined by the trap parsers. Selecting appropriate values for important attributes, such as failure object/affected entity, source and message text, allows quick identification of a failure. While specifying the output values for the event object generated, information present in the incoming trap PDU can be used. The information in the trap PDU can be accessed using the tokens which represent values of the fields in a trap. Incoming traps are parsed by configuring a list of trap parsers. Only one trap parser can be applied to a given trap. The match criteria in the parser determine whether a specific trap matches t