User guide

Configuring Event Parsers Changing Severity of Default Events (i.e. Status Update Fail-
AlliedView NMS Administration Guide (Setting Up Fault Management)
9-14
FIGURE 9-5 Setting the Event Parser to Produce Alarms for SYSLOG
The usual scenario would be the device in the Physical Network view would show the device has a major alarm. Right clicking
Alarms/Events -> Alarms on the affected device would show Figure 9-6. (This would also show up in the Events view as a
network event.). The user could then double click the alarm row to further process the alarm, or Edit -> Clear to clear the
alarm.
FIGURE 9-6 Alarm Produced as a Result of Configuring Event Parser
9.4.5 Changing Severity of Default Events (i.e. Status Update Failure)
The default Event Parser Configuration Form allows the user to view and modify the events that are generated by the devices.
As explained in 9.4.1, these events have attributes (especially the alarm level) that should not be changed unless with consulta-
tion with Allied Telesis personnel.
For default events (such as status update failure), the severity of the event is already set, but can be changed by creating an
Event Parser that outputs a different Severity Alarm. Following is an overview of status update and the steps to change the
severity of a status node failure from Major to Critical.
9.4.5.1 Overview
The AlliedView NMS periodically tests connectivity to all managed devices by polling their interfaces. By default, the period
is 300 seconds, which can be modified with the Managed Object Properties dialogue (by changing the pollInterval parameter).
By default, when connectivity is lost a major event is created, which in turn generates a major alarm. This example shows how
to make the event critical instead of major.