Define an event policy to be processed by the event process
(eventd) process.
|
- Click Add new entry next to Policy.
- In the Name box, enter the policy
name.
- In the Comment box, enter the comment
for the policy.
|
Execute the policy only if the attributes of two events
are correlated or if the attribute of one event matches a regular
expression.
|
- Click Add new entry next to Attributes
Match.
- In the From Event Attribute box,
enter the first attribute to compare.
- From the Condition list, select the
match condition for the attributes.
- In the To Event Attribute Value box,
enter another attribute.
- In the Comment box, enter the comment
for the attributes-match.
|
Create a list of events that trigger this policy. If
one or more of the listed events occurs, the policy is executed.
|
- Click Add new entry next to Events.
- In the New events dialog box, enter
the name of the event.
|
Define actions to take if an event occurs. For each policy,
you can configure multiple actions.
|
- Click Then next to policy.
- In the comment box, enter the comment.
- Select the Ignore check box to define
a policy that ignores particular events.
- Select the Raise Trap check box to
define a policy that raises a Simple Network Management Protocol (SNMP)
trap in response to an event.
|
Specify operational mode commands to be issued, the format
of the command output, and a name and destination for the output file.
|
- Expand Then and select Event Script.
- Click Add new entry next to Event
Script.
- In the Name box, enter the filename.
- In the comment box, enter the comment
for the event script.
- From the Username list, select the
user associated with an action in an event policy.
- In the Output Filename box, enter
the filename to which to write command or script output for the specified
commands or script.
- From the Output Format list, select
the format for the output of the specified commands.
|
Include command-line arguments to the script for JUNOS
op scripts and assign a location to which to upload command or script
output for the specified policy.
|
- Expand event-script.
- Click Arguments next to event-script.
- Click Add new entry next to Arguments.
- In the Name box, enter the arguments
to the script as name.
- In the comment box, enter the comment.
- In the Value box, enter the variables
in the argument values to allow data from the triggering event to
be automatically included in the argument.
- Click Destination next to event-script.
- From the Name list, select the location
to which to upload command or script output for the specified policy.
- In the Comment box, enter the comment.
- From the Transfer Delay list, select
the delay in seconds before transferring files.
- Expand Destinations and select Retry Count next to it.
- In the Comment box, enter the comment
for the retry count.
- From the Retry list, select the number
of retries.
- From the Retry Interval list, select
the length of time to wait between retries.
|
Specify operational mode commands to be issued, the format
of the command output, and a name and destination for the output file
on receipt of an event.
|
- Expand Execute Commands.
- Click Commands.
- In the Name box, enter the command.
- Click Destination next to Execute
Commands.
- See
|
Specify a file to be uploaded to a destination on receipt
of an event.
|
- Click Upload next to Event Script.
- In the Filename box, enter the name
of the file to be uploaded.
- From the Destination list, select
the name of a destination.
- From the User Name list, select the
username.
- From the transfer relay list, select
the delay before transferring files.
|
Create a list of events that must (or must not) occur
within a specified time interval for the policy to be triggered.
|
- Click Add new entry next to Within.
- Expand Within.
- From the Name list, select the interval
between events.
- Click Events next to within.
- Click Add new entry next to Events.
- In the New events dialog box, enter
the events that trigger this policy.
- Expand Not.
- Click Events next to Not.
- In the New events dialog box, enter
the events that trigger this policy.
- Click Trigger next to Not.
- In the Comment box, enter the comment.
- Select one of the following:
- until—if the policy is to be
executed each time a matching event is received and stops being executed
when the number of matching events received equals number.
- on—if the policy is executed
when the number of matching events received equals number.
- after—if the policy is executed
when the number of matching events received equals number + 1.
- From the Count list, select the number
of times an event or set of events should occur within a specified
time period.
|