Filter
Top Products
actions when specific events occur. These actions can either help you diagnose a
fault or take corrective action.
This section contains the following topics:
■ Event Policy Overview on page 95
■ Configuring Event Policies on page 95
Event Policy Overview
In response to events, event policies can execute the following actions:
■ Ignore the event—Do not generate a system log message for this event and do
not process any further policy instructions for this event.
■ Raise a trap—Initiate an SNMP trap to notify SNMP trap-based applications when
the event occurs.
■ Upload a file—Upload a file to a specified destination. You can specify a transfer
delay, so that, on receipt of an event, the upload process begins after the
configured transfer delay. For example, a transfer delay can ensure that a core
file has been completely generated before being uploaded.
■ Execute CLI operational mode commands—Execute commands when an event
occurs. The output of these commands is stored in a file, which is then uploaded
to a specified URL.
■ Execute operation scripts—Execute operation scripts when an event occurs. The
output of the operation scripts is stored in a file, which is then uploaded to a
specified URL. For information about operation scripts, see “Automating Network
Management and Troubleshooting with Operation Scripts” on page 92.
To view a list of the events that can be referenced in an event policy, issue the help
syslog ? command:
user@host> help syslog ?
Possible completions:
<syslog-tag> System log tag
ACCT_ACCOUNTING_FERROR Error occurred during file processing
ACCT_ACCOUNTING_FOPEN_ERROR Open operation failed on file
ACCT_ACCOUNTING_SMALL_FILE_SIZE Maximum file size is smaller than record size
...
For information about these events, see the JUNOS System Log Messages Reference.
Configuring Event Policies
To configure event policies:
1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI
configuration editor.
2. Perform the configuration tasks described in Table 45 on page 96.
3. If you are finished configuring the network, commit the configuration.
Running Self-Diagnostics with Event Policies ■ 95
Chapter 6: Automating Network Operations and Troubleshooting