User guide

Setting Up Fault Management Configuring Event Parsers
927
AlliedView NMS Administration Guide
3. Click on the tic box, and then OK to add the type criteria.
4. The Event Parser Configuration Form is now the only form that is on the screen. Click on Update, Apply, and Close.
Now only AT-AR745's when disconnected will go critical and all the others will still be major.
9.4.5.6 Ensure the Event Parser is created
1. Select Edit -> Configure ->Event Parsers again.
2. The Event Parser Configuration Form will appear and will include the new Event Parser.
9.4.5.7 Test the New Event Parser
1. Delete existing alarms for the device.
2. Click on Update Status, and see the color change to red, as shown in Figure 9-11.
FIGURE 9-11 Testing the Changed Severity for the Event Parser (now Critical)
3. If it changed to green instead of red, either connectivity was re-established while you were creating the Event Parser,
or you accidentally selected Clear on the Severity Output-String where you meant to select Critical.
4. If it goes to Orange, you misspelled the Message text, you selected Major instead of Critical, or you misspelled the
type name.
Note: A critical event will also be generated for the network to which the failed device belongs.
9.4.5.8 Delete the Event Parser (if non-default behavior no longer needed)
To delete the new Event Parser (and return to the default behavior), go back to the Event Parser Configuration window,
select the parser you added, click on Delete Event Parser, Apply, and then Close.