close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- play_arrow Junos Automation Scripts Overview
- play_arrow Junos XML Management Protocol and Junos XML API Overview
play_arrow Automation Scripting Using XSLT
- play_arrow XSLT Overview
- play_arrow Standard XPath and XSLT Functions Used in Automation Scripts
- play_arrow Standard XSLT Elements and Attributes Used in Automation Scripts
play_arrow Automation Scripting Using SLAX
- play_arrow SLAX Overview
- play_arrow SLAX Statements
- play_arrow The libslax Distribution for Automation Scripting
play_arrow Automation Scripting Using Python
- play_arrow Python Overview
play_arrow Automation Script Input
- play_arrow Global Parameters in Automation Scripts
  - Global Parameters and Variables in Junos OS Automation Scripts
play_arrow Extension Functions and Named Templates for Automation Scripts
play_arrow Manage Automation Scripts
- play_arrow Store and Enable Scripts
- play_arrow Configure a Remote Source for Scripts
- play_arrow Configure the Session Protocol for Scripts
  - Understanding the Session Protocol in Automation Scripts
  - Example: Specify the Session Protocol for a Connection within Scripts
- play_arrow Control Execution of Scripts
- play_arrow Synchronize Scripts Between Routing Engines
- play_arrow Convert Scripts Between SLAX and XSLT
  - Convert Scripts Between SLAX and XSLT
play_arrow Commit Scripts
- play_arrow Commit Scripts Overview
  - Commit Script Overview
  - How Commit Scripts Work
- play_arrow Create and Execute Commit Scripts
- play_arrow Generate a Custom Warning, Error, or System Log Message Using Commit Scripts
- play_arrow Generate Persistent or Transient Configuration Changes Using Commit Scripts
- play_arrow Create Custom Configuration Syntax with Commit Script Macros
- play_arrow Commit Script Examples
- play_arrow Junos XML and XSLT Tag Elements Used in Commit Scripts
- play_arrow Troubleshoot Commit Scripts
play_arrow Op Scripts
- play_arrow Op Scripts Overview
  - Op Script Overview
  - How Op Scripts Work
- play_arrow Create and Execute Op Scripts
- play_arrow Op Script Examples
- play_arrow Provision Services Using Service Template Automation
  - Service Template Automation Overview
  - Example: Configure Service Template Automation
- play_arrow Troubleshoot Op Scripts
  - Trace Op Script Processing on Devices Running Junos OS
  - Trace Script Processing on Devices Running Junos OS Evolved
play_arrow Event Policies and Event Scripts
play_arrow SNMP Scripts
- play_arrow SNMP Scripts Overview
  - SNMP Scripts Overview
- play_arrow Create and Execute SNMP Scripts
- play_arrow SNMP Script Example
  - Example: Process Unsupported OIDs with an SNMP Script
- play_arrow Troubleshoot SNMP Scripts
  - Trace SNMP Script Processing on Devices Running Junos OS
  - Trace Script Processing on Devices Running Junos OS Evolved
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Junos Logger Utility

date_range 27-Aug-24

arrow_backward

arrow_forward

Use the Junos logger utility to record custom system log messages or generate event notifications for validating event policies in a test environment.

The Junos software includes a logger utility, which enables you to:

Record custom messages in the system log file
Simulate Junos event notifications

Junos Logger Overview

The Junos logger is a shell utility that you can use to log custom messages to the system log file and artificially generate event notifications. The logger enables you to successfully test event policies and event scripts even when the trigger event is difficult to reproduce.

You can configure event policies on Junos devices to execute specific actions in response to an event or series of events. It is important to test an event policy before deploying it in a production environment to ensure that the policy triggers as expected and performs the correct actions. In some cases, it is difficult to simulate the environment that generates the events required to trigger an event policy. In these cases, you can use the Junos logger utility to generate event notifications to trigger the policy.

Note:

The Junos event logger is an unsupported shell utility that should not be used on devices in a production environment. However, the utility is well suited for use in lab environments where you are developing and verifying event policies and event scripts.

The logger utility also enables you to record a message in the system log without triggering an event notification. Thus, you can log supplementary information about the system in addition to the messages and events that are automatically logged during normal device operations.

When you use the logger utility to generate event notifications or record custom log messages, the device uses a modified version of the base OS's logger utility. The modified utility accepts a specialized set of options that are designed for use with the Junos software.

Syntax (Junos OS)

content_copy zoom_out_map
logger -e EVENT_ID -a attribute=value -d process -l logical-system-name -p priority "message"

Syntax (Junos OS Evolved)

content_copy zoom_out_map
eventd_logger -e EVENT_ID -a attribute=value -d process -l logical-system-name -p priority "message"

Description

Generate an event notification and also log the event in the system log, provided that the device is configured to log events with the specified priority.

Options

Table 1 outlines the required and optional arguments for the Junos event logger utility.

Table 1: Logger Options (Generate an Event)
Option	Description	Example
`-a attribute=value`	(Optional) Attribute associated with the event. The attribute name must be lowercase. To specify multiple attributes, include the `-a` option for each attribute. For more information about the attributes associated with a particular Junos event, view the event's details in the System Log Explorer tool.	`-a username=admin` `-a command=commit`
`-d process`	(Optional) Junos process (daemon) to use as the event's source process. If you do not specify a process, Junos OS uses `logger` for the process, and Junos OS Evolved uses `EVENTD_LOGGER` for the process.	`-d mgd`
`-e EVENT_ID`	Event for which to generate the event notification. The event identifier must be uppercase.	`-e UI_COMMIT`
`-l logical-system-name`	(Optional) Generate and log an event notification in the log file for the specified logical system.	`-l ls-router1`
`-p priority`	(Optional) Log the event with the given priority, specified numerically or as a syslog `facility.severity` pair. The default priority is `user.notice`.	`-p external.notice`
`message`	(Optional) Message string to record in the system log. Quotes are not required, but they are recommended for clarity.	"This is a manually generated test event."

Junos Logger Syntax (Log a Message)

Syntax (Junos OS)
Syntax (Junos OS Evolved)
Description
Options

Syntax (Junos OS)

content_copy zoom_out_map
logger -46Ais -f file -h host -p priority -t tag "message"

Syntax (Junos OS Evolved)

content_copy zoom_out_map
eventd_logger -is -f file -p priority -t tag "message"

Description

Log entries in the system log, provided that the device is configured to log messages with the specified priority.

Note:

On devices running Junos OS Evolved, you can also use the Linux logger utility in the system shell to record messages in the system log.

Options

When you use the Junos logger utility to record custom messages in the system log, the device calls the logger utility for the underlying base OS. Only a subset of the logger options are supported on Junos devices. Table 2 outlines the supported options.

Table 2: Logger Options (Log a Message)
Option	Description
`(-4 \| -6)`	(Optional) On Junos OS, use IPv4 or IPv6 addresses only.
`-A`	(Optional) On Junos OS, attempt to send the message to all addresses.
`-f file`	(Optional) Copy the contents of the specified file into the system log file.
`-h host`	(Optional) On Junos OS, send the message to the specified remote host instead of logging it locally.
`-i`	(Optional) Log the process ID of the logger process with each line.
`-p priority`	(Optional) Generate the event with the given priority, specified numerically or as a syslog `facility.severity` pair. The default priority is `user.notice`.
`-s`	(Optional) Log the message to standard error, in addition to the system log file.
`-t tag`	(Optional) Log the entry with the specified tag instead of the default tag, which is the current username.
`message`	(Optional) Message string to record in the system log. Quotes are not required, but they are recommended for clarity.

Use the Junos Logger to Generate Events

The Junos event logger is a shell utility. To use the utility, you must first start a system shell.

To generate an event notification and also log it in the system log file:

Start a system shell.
```
user@host> start shell
```
The shell prompt varies depending on the OS and whether the user is the root user. For example:
- In Junos OS:
  user@host> start shell %
- In Junos OS Evolved:
  user@host> start shell [vrf:none] user@host~$
Generate an event by calling the Junos logger utility and specifying the event ID in uppercase as well as any other optional arguments.
For example, the following commands simulate a UI_COMMIT event. The event is generated by the mgd process and has event priority external.notice.
- In Junos OS:
  % logger -e UI_COMMIT -d mgd -p external.notice -a username=admin -a command=commit "This is a test event."
- In Junos OS Evolved:
  [vrf:none] user@host~$ eventd_logger -e UI_COMMIT -d mgd -p external.notice -a username=admin -a command=commit "This is a test event."

The event notification is sent to the eventd process. The device also records the event information and specified message in the system log file, provided you have configured the device to log messages of the given facility and severity level.

content_copy zoom_out_map
user@host> show log messages | match UI_COMMIT
Nov 4 16:26:41 host mgd: UI_COMMIT: This is a test event.

You can use the Junos event logger utility to generate one or more event notifications to trigger and test an event policy when it is difficult to reproduce the events in a given lab environment. In the previous example, the device will execute any policies that trigger on the UI_COMMIT event.

Use the Junos Logger to Log Messages

The Junos logger is a shell utility. To use the utility, you must first start a system shell.

To log information in the system log file:

Start a system shell.
```
user@host> start shell
```
The shell prompt varies depending on the OS and whether the user is the root user. For example:
- In Junos OS:
  user@host> start shell %
- In Junos OS Evolved:
  user@host> start shell [vrf:none] user@host~$
Log a message to the system log by calling the Junos logger utility and specifying the information to log as well as any optional arguments.
For example, the following commands log the given message string with the CUSTOM_LOG tag and a priority of external.notice.
- In Junos OS:
  % logger -p external.notice -t CUSTOM_LOG "The server is up."
- In Junos OS Evolved:
  [vrf:none] user@host~$ eventd_logger -p external.notice -t CUSTOM_LOG "The server is up."

In this example, the message string is recorded in the system log with the CUSTOM_LOG tag, provided you have configured the device to log messages of the given facility and severity level.

content_copy zoom_out_map
user@host> show log messages | match CUSTOM_LOG
Nov 16 14:38:31  host CUSTOM_LOG[21905]: The server is up.

arrow_backward PREVIOUS Use Nonstandard System Log Messages to Trigger Event Policies

NEXT arrow_forward Configure an Event Policy to Execute Operational Mode Commands

Automation Scripting User Guide

ON THIS PAGE

Junos Logger Utility

Junos Logger Overview

Junos Logger Syntax (Generate an Event)

Syntax (Junos OS)

Syntax (Junos OS Evolved)

Description

Options

Junos Logger Syntax (Log a Message)

Syntax (Junos OS)

Syntax (Junos OS Evolved)

Description

Options

Use the Junos Logger to Generate Events

Use the Junos Logger to Log Messages

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry