Clear araman Clear IF-araman Clear kernel-linux Clear IF-kernel-linux Major switch-rd3_Port1 Alarm count by severity Clear nms-build Clear IF-nms-build Clear IF-duplex1 Clear rajesh Clear IF-rajesh Clear fakirm fakir Clear IF-fakirm fakir Clear mahaluckshme Done. Figure 12.23 Test node. Traps contain cryptic information, which cannot easily be understood by users. Therefore, a trap parser is required to translate or parse these traps into under- standable information for easy identification. A trap parser converts information from any device into meaningful events, that is, identification of the affected element. For example, a "link down" message may have the router and the interface as the failure object. Using the trap parsers, this can be converted to a more understandable event where the failure object is uniquely identified. This is important because it allows the tracking of the fault or failure. Trap parsers option under the "Edit" menu helps in detailed parsing of the input data to identify fully the failure object of the event. The trap parser can be edited through an HTML interface. 12 Fault Management Add Tree Node User Defined Properties Any additional user defined properties for the node to be added can be specified here Property Key Property Value FRAME TITLE Frame Title Value FRAME TITLE Frame Title Modify Delete Click back to add default properties Next> Apply Cancel Figure 12.24 Adding a tree node. Tooks AdventNet Excultures MATTRES Trap Parser Configuration Configured Trap Parsers coldStart warmStart egpNeighborLoss authenticationFailure Modify Trop Persor Delete Trap Parser Add Trap Parser Figure 12.25 Trap parser configuration through HTML user interface. The HTML screen in Figure 12.25 shows all trap parsers that have been config- ured, with radio buttons for every trap parser. By default, four trap parsers are con- figured. A new trap parser can be added in the HTML form shown in Figure 12.26. Trap parser parameters are given in Table 12.4. Trap parsers can also be loaded from MIBs or from 