Manage CLI Configuration Changes

Configuration Guidelines

The CLI Configuration feature is supported on routers that are managed by Juniper Routing Assurance only and the routers must be running supported Junos or Junos EVO operating systems. CLI Configuration operates strictly within the Juniper Routing Assurance managed configuration group named Routing Assurance.

Follow these guidelines when using the CLI Configuration feature to ensure configurations are applied safely and correctly:

• CLI Configuration supports Junos set commands only. Enter each configuration command as a standard Junos OS or Junos OS Evolved set command, with one command per line. Following is a sample configuration to set a login banner/message, define a prefix list with a specific IP address and a BGP community for use in routing policies:

• Router configuration changes are controlled using the Configuration Management flag, which administrators can enable or disable to allow or deny Juniper Routing Assurance permission to manage router configurations. When Configuration Management is disabled, configuration changes are stored but not applied to the router. When enabled, the saved configuration is immediately pushed to the router. See Enable or Disable Router Configuration Management to allow or deny configure permissions for Juniper Routing Assurance to manage router configuration.

• Juniper Routing Assurance does not perform syntax validation when the configuration is entered or saved in the Additional CLI Commands text box. Validation occurs only when the configuration is pushed to the router and a commit operation is attempted.

• If you include an invalid or unsupported command, the configuration push fails during the commit phase on the router. In such cases, the configuration is not committed and no partial configuration is applied.

  This behavior ensures that erroneous configuration does not impact the running configuration.

• Users cannot create custom configuration groups, or use apply-groups to apply the configuration groups. Juniper Routing Assurance can detect such configurations. When detected, Juniper Routing Assurance prevents the configuration from being saved, ensuring that only supported inputs are applied.

• When you add or update set commands, Juniper Routing Assurance applies those commands to the targeted routers as a single transaction. Updating the configuration replaces the previously applied configuration while preserving settings defined at the template, site, or device level. This ensures that only the intended changes are applied.

  If any part of the change fails validation, Juniper Routing Assurance performs a rollback of the configuration rather than leaving the router in a partially configured state. This ensures consistency across routers and protects against incomplete or inconsistent configuration deployment.

• To remove a configuration, delete the corresponding set commands from the CLI input. Explicit delete commands are not required and are not supported.

View Events in Router Insights Page

When you perform a configuration change, related events appear in the Router Insights page under Router Events section.

• Configuration Success─When configuration is successfully committed on the router, a Config Changed by User event is recorded as a Good event, confirming that the changes were applied as intended.

• Configuration Failure─When a commit failure occurs due to a syntax error or invalid input, Juniper Routing Assurance generates a Config Failed event. This event is recorded as a Bad event under the Router Events section and is visible on the Router Insights page. The router event details clearly indicate that the commit failed and include the reported syntax error, allowing users to identify and correct the issue.