Junos OS categorizes on-box automation scripts according to their execution trigger and operational scope. An event script is designed to run automatically in response to system events and syslog messages captured by the Junos event daemon (eventd). When an operational condition generates a specific system log entry (e.g., an interface transition or BGP peer flap), an event policy triggers the associated event script to execute corrective actions, collect targeted diagnostic telemetry, or notify administrators. In contrast, commit scripts run during the commit phase to enforce syntax standards and security policies; operation (op) scripts are executed manually by users from the CLI operational mode (op < script-name > ); and SNMP scripts are invoked in response to SNMP MIB requests. Therefore, scripts triggered automatically by log entries are event scripts.
[Reference: JNCIA-DevOps Study Guide — Junos On-Box Automation: Event Scripts and eventd Policy Triggers., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit