Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

CLI Configuration

Juniper Routing Assurance preserves existing customer configurations while enabling centralized configuration management through the CLI Configuration.

To support this requirement, Juniper Routing Assurance follows a shared configuration ownership model:

  • Juniper Routing Assurance manages only the configuration applied through templates and remote shell under Utilities.
  • Existing customer-managed configurations remain unchanged and fully under customer control.

This approach ensures non-disruptive onboarding while maintaining the integrity of production configurations and enabling secure access for monitoring.

CLI Configuration

CLI Configuration enables centralized management of additional configuration for routers from Juniper Routing Assurance. Using the CLI Configuration widget, administrators can apply Junos OS or Junos OS Evolved configurations on multiple routers at the same time from Juniper Routing Assurance.

The CLI Configuration widget addresses common operational needs such as applying system banners, login messages, or consistent system settings across many routers. CLI Configuration enables centralized management of settings. It reduces manual effort, improves consistency, minimizes configuration drift, and supports site or device-level customization when required.

The key value of CLI Configuration lies in its ability to simplify large‑scale configuration management. Instead of logging in to individual devices or relying on external scripts, teams can manage configuration centrally and apply updates consistently. This approach improves operational efficiency and strengthens configuration governance.

Note: 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 permissions for Juniper Routing Assurance to manage router configuration.

How Configuration is Applied on Juniper Routers

Juniper Routing Assurance leverages Junos OS and Junos OS Evolved configuration groups to apply managed configuration.

A configuration group is a logical container for a set of configuration statements. Configuration groups help create modular and logically structured configuration files, making Juniper Networks devices easier to configure and maintain. All configuration applied by Juniper Routing Assurance resides in a single Junos OS or Junos OS Evolved configuration group named Routing Assurance.

Multiple configuration groups can be applied to a router, and the final running configuration is a merge of:

  • The base configuration.
  • Configuration groups managed by administrators.
  • The Routing Assurance configuration group.

This Routing Assurance configuration group is fully managed by Juniper Routing Assurance, and any out-of-band changes made to it are automatically detected and reverted.

Configuration Inheritance and Conflict Resolution

Routers associated with a site automatically inherit the configuration template assigned to that site. Configuration inheritance follows this hierarchy:

  • Template-level configuration─Templates define global settings that apply to all managed routers.
    Note: Template-level configurations do not apply to all routers by default. Template-level configurations are applied to all managed routers within a specific site only when the template is assigned to that site.
  • Site-level configuration─Applies site-specific settings to all routers at a given site. Site-level configurations can override template-level templates for routers within a specific site.
  • Device-level configuration─Allows customization for individual routers. Device-level configurations can further override both site-level and template-level settings for individual routers.

When configuration conflicts occur, the most specific (narrower) configuration takes precedence by overriding broader configurations.

Note: Site-level configurations can override the template-level configurations when the Override Configuration Template check box is enabled on the Router Configuration : Site Name page. For more information, see Override a Configuration Template for a Site.

Managing Router Configurations and Templates

The Router Configuration and Router Templates pages provide a centralized interface for managing configurations across sites and routers using configuration templates. These pages enable administrators to view configuration coverage, understand template usage, and efficiently manage the full life cycle of configuration templates, from creation to deployment.

Through these pages, you can review the templates assigned to specific sites, see the number of routers affected, and make updates either at the site level or template level. The UI supports both single and bulk actions, allowing you to assign, update, and standardize configurations at scale while maintaining visibility into deployment scope and impact.

In addition, the configuration template management view allows users to create new templates, import existing ones, customize templates by adding CLI commands, clone templates for reuse, export templates as JSON files, and safely delete unused templates. Together, these capabilities simplify router configuration management, improve consistency in configuration across the network, and reduce operational overhead through streamlined, template-driven work flows.

Related Documentation