User guide

Relationship Between User Properties and Custom Views Configuring Event Parsers
9-13
AlliedView NMS Administration Guide (Setting Up Fault Management)
If the event object contains the trap pdu information, you can make use of the trap pdu information while defining the output
events. The methodology of using the properties of the trap using symbolic notations is similar as in Trap Parsers, except for
the following:.
• To access the values of the SNMP OID in the SNMP Variable bindings, the notation should start with % and not with $
as in trap parser.
• To access the SNMP OID in the SNMP Variable bindings, the notation should start with @ which is same as in trap
parser.
The values of the trap pdu can be used in any of the columns, except in Tokenizer in the parser defined.
Note: If the trap pdu symbolic notation, such as %Agent, is used in the property column (while configuring
Additional Criteria) when the value has also been tokenized by specifying a tokenizer string, then to refer
to a token of this field use the notation as $%Agent$N, where N specifies the count of the token to be
used.
9.4.3 Relationship Between User Properties and Custom Views
As explained in Table 9-4, user properties can be added using the Event Parser form and clicking the More button. (They can
also be added by Allied Telesis software extensions.) These can then be used in additional event event parsers or custom
views
Note: When defining properties for nodes, include the properties displayed on the last page of the Managed
Object Properties Form.
For Event Custom Views, refer to the NMS User Guide, Section 9.
For Alarm Custom Views, refer to the NMS User Guide, Section 9. Note that for custom alarm views only one user property,
sysLocation, is available. This is explained in the User Guide.
9.4.4 Setting up a SYSLOG Event to Create an Alarm
By using the Event Parser Configurator, the user can parse a SYSLOG event so that an alarm is produced. This can be useful
if certain events, such as a configuration change on the a device, need to be highlighted.
Figure 9-5 shows how a SYSLOG that includes the string “Configuration Updated” can be set. The user would bring up the
Event Parser Configuration window and Add Event Parser, in this case ConfigChangeSyslogParser. The Category is SYS-
LOG, and the Severity for the Output String is Major. (SYSLOG events have no severity level on the Match String and so the
Severity is set to All.)
Help Invokes this table.
Close Closes the form. If no changes were applied to the server, they are lost. If changes have been made,
there is a prompt on whether to apply the changes.
TABLE 9-4 Event Parser Configuration Form (Continued)
Option Description