User guide

Setting Up Fault Management Configuring Event Parsers
922
AlliedView NMS Administration Guide
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.
Save to File To reuse the configured event parsers and to save the event parser configuration as a backup. These
files can later be loaded in to the same or another event manager. This will enable sharing of the
event parser data by other users. When this option is chosen, a dialog window will be brought which
will prompt you to enter a filename (the default being event.parsers). Enter the name of the file and
choose Save option to save the trap parser.
Note: When saving these files, the AlliedView NMS sets as the default directory the <NMS
Home>/state
directory, so for example the file path:
../conf/event.parsers
is being saved in the
conf directory by going up one level from the state directory (..)
and then down to the
conf directory. If the user enters in the form only a file name,
that file is being saved in the default
state directory.
Load from
File
To load a set of event parsers previously saved with the Save To File option and add them to the
existing list of event parsers. This option brings up a dialog box to specify the filename on the server,
which contains the event parsers. Choosing the Load option will complete loading event parsers
from the specified file. The parsers with the same matching criteria as that of the existing ones will
be replaced with the new ones.
Update Update the modified Event Parser. The change will not take effect until the Apply to Server button is
selected.
Apply to
Server
Makes and changes permanent.
Cancel Cancels the update.
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