Configuration Pushed to Devices During Device Adoption

This topic lists the configuration pushed to the devices during device adoption.

When a device connects to Routing Director, specific commands are pushed to the device to enable management and telemetry collection. This topic lists those commands and provides a brief description of their purpose.

Configuration Applied During Adoption

Event Generation

The following commands are committed to:

  • Generate an event every 180 seconds to collect operational statistics from the device.

  • Generate an event daily to monitor the available disk space.

Link Event Policies

The following commands are committed to monitor change in the interface operational status.

Configuration Change Monitoring

The following commands configure an event policy that automatically runs the jcloud_acx_event_dispatcher.py script after a configuration is successfully committed on the device.

System Event Monitoring

The following commands configure an event policy within the jcloud-script configuration group to run a script jcloud_acx_event_dispatcher.py when any of the following events occur:

  • A commit confirm operation is not confirmed within a specified timeout period, causing Junos OS to roll back the configuration.

  • When the device or Routing Engine is restarted.

  • High availability (HA) events such as:

    • HA control link failure or the recovery of the HA control link.

    • HA node health falls below the configured threshold.

    • HA node health has recovers above configured threshold.

    • Change in the state of the HA node (for example from primary to secondary and secondary to primary).

    • A critical HA-related process or redundancy daemon fails.

  • Mismatch in Services Processing Unit (SPU) count between HA peers

  • Failure and recovery in Service Redundancy Group (SRG) health

  • Change in state of SRG (active to standby and standby to active)

  • Change in the state of redundancy group (primary to secondary and secondary to primary)

Statistics Aggregation Policy

The following commands are committed to generate an event to collect statistics every three minutes and execute the jcloud_acx_event_dispatcher.py script whenever statistics is collected.

Event Script Registration

The following commands register the Junos OS and Junos OS Evolved event scripts, specify the local user account that will run the scripts, and apply the jcloud-script group so that all the policies defined during adoption and script settings become active.

Dual-Routing Engine Devices

The following command is committed to apply the configuration groups global, re0, re1, and jcloud-script to the device's active configuration, causing all settings defined in those groups to take effect.

Virtual Chassis systems:

The following command is committed to apply the configuration groups global, member0, and jcloud-script to the device's active configuration, making all settings defined within those groups effective.

Enable Script Framework

Junos OS devices

The following commands are committed to enable Python scripting on the devices running Junos OS and Junos OS Evolved ensure that script files are automatically replicated across redundant Routing Engines.

Junos OS Evolved and newer EX and QFX devices

The following commands are committed to enable Python-3 based automation scripts on devices running Junos OS Evolved and newer EX and QFX devices to ensure that files are automatically replicated across redundant Routing Engines.

Dual-Routing Engine devices

The following command is committed to synchronize configuration changes on both the Routing Engines of a dual-Routing Engine device.

System Log Configuration

The following commands are committed to configure log files, define log rotation, and specify what events are recorded in the logs. Log files are rotated after reaching 2MB size and up to five log files are retained.

Additional Configuration on EX and QFX Devices

The following additional commands are committed on EX and QFX Series devices to configure the standard messages log file. This log file records all events related to authorization. For example, user login attempts, authentication successes or failures, privilege changes, SSH access, user account activities, and TACACS+ and RADIUS authorization events.

All severity levels are logged and the log file is rotated after reaching 2MB size. Up to five log files are archived.

Configuration for gNMI-over-TLS Connection

The following commands are committed to create a PKI Certificate Authority (CA) profile named jcloud_gnmi_ca and associate it with a CA certificate identified as jcloud_gnmi_ca for enabling a gNMI-over-TLS connection between Routing Director and the device.

Verification

The following commands are committed to view and list the configured event policies, event scripts, system scripts, configuration groups, and view contents of escript.log and op-script.log.

Telemetry and Monitoring RPCs Executed After Device Adoption

This section provides a list of the remote procedure calls (RPCs) executed on devices to gather operational statistics and monitor device health after device adoption.

Interface Statistics Collection

The following RPC is executed to retrieve the output of the show interfaces extensive command in a structured XML format.

Supported Platforms: ACX, MX, and PTX

Alarm Monitoring

The following RPCs are executed to retrieve the alarm information from the device.

Supported Platforms: ACX, MX, and PTX

Environment Monitoring

The following RPCs are executed to discover hardware inventory and verify device health.

Supported Platforms: ACX, MX, and PTX

Switched Virtual Interfaces (SVI) Discovery

The following RPCs are executed to retrieve routing information learned through the Local routing protocol and stored in the device.

Supported Platforms: ACX and MX