Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Deploy a Configuration Template

Follow the steps described in this topic to deploy a configuration template to one or more sites or routers.

Deploy a Configuration Template to a Site

Note: Enable Configuration Management on all routers at the site to allow configurations to be pushed from Juniper Routing Assurance; see Enable Router Configuration Management for a Router.
Note: A configuration push applies settings to all routers currently in the Connected state. For routers in Disconnected state, the configuration changes apply when the routers come online. Whenever new routers are onboarded to a site, the appropriate organization-level and site-level template are automatically applied.

To deploy a configuration template to a site:

  1. Navigate to Organization > Router Templates.
    The Router Templates page appears, displaying the list of configuration templates that you have created.
  2. Select the desired template that you want to deploy on a site.
    The Router Templates > Template Name page appears.
  3. Click Assign to Sites.
    The Assign Template to Sites pop-up window appears, displaying the number of sites and the number of routers on which the selected template is currently deployed.
  4. Under Sites, click the Add (+) icon.
  5. Select one or more sites from the list of sites that is displayed, and then click Add.
    You are returned to the Assign Template to Sites pop-up window and the window displays the sites that you selected.
  6. Click Apply.
    The Confirm Apply Templates to Sites pop-up window appears.
  7. Click Confirm to confirm the action.
    The configuration is immediately pushed to all the routers at the selected sites and you are returned to the Router Templates > Template Name page.

To view the results of a site‑level configuration push, navigate to the Routers page. The Config Success widget shows the percentage of routers with successful configuration.

When configuration is successfully committed on the router, a Config Changed by User event is generated. View this event under Router Events on the Router Insights page. This event shows a UI_COMMIT_COMPLETED response. Click View Details to see the configuration difference.

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. The router event details indicate that the commit failed and include the reported syntax error, allowing users to identify and correct the issue.

Override a Configuration Template for a Site

Follow the steps described below to apply site‑level customizations to a configuration template.

Note: Enable Configuration Management on all routers at the site to allow configurations to be pushed from Juniper Routing Assurance; see Enable Router Configuration Management for a Router.

To apply site‑level customizations to a configuration template:

  1. Navigate to Organization > Router Configuration.
    The Router Configuration page appears, displaying the list of sites in the organization.
  2. Click the desired site to apply a configuration template.
    The Router Configuration : Site Name page appears, displaying the configuration template currently deployed at the site level.
  3. Enable the Override Configuration Template check box, under CLI Configuration.
    The text box in the Additional CLI Commands widget is editable, allowing you to enter CLI commands.
  4. Enter the Junos OS or Junos OS Evolved set commands to modify or override the site-level configuration settings, and then click Save.

    For guidelines on using the Additional CLI Commands, see Manage CLI Configuration Changes.

    The Confirm Changes pop-up appears, displaying the configuration that was entered in the previous step.
  5. Verify that the configuration is rendered correctly.

    • If the configuration is not rendered correctly, click the close (X) icon to go back to the Router Templates : Template Name page and make modifications as needed.

    • If the configuration is rendered correctly, click Save.

      You are returned to the Router Templates page.

    The new configuration is pushed to all the devices in the site.

When configuration is successfully committed on the router, a Config Changed by User event is generated. View this event under Router Events on the Router Insights page. This event shows a UI_COMMIT_COMPLETED response. Click View Details to see the configuration difference.

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. The router event details indicate that the commit has failed and include the reported syntax error, allowing users to identify and correct the issue.

Apply Device-Level Configuration

Follow the steps described below to:

  • Apply device‑level configurations to the router.

  • Override the configuration template currently applied to the router.

Note: Enable Configuration Management on the router to allow configurations to be pushed from Juniper Routing Assurance; see Enable Router Configuration Management for a Router.

To apply device‑level customizations:

  1. Click Routers from the main navigation menu.
    The Routers page appears, listing the routers managed by Juniper Routing Assurance.
  2. From the list of routers, select the router for which you want to push device-level configuration customizations.
    The Routers : Router Name page appears.
  3. Navigate to the Configuration tab.
    The Site/Template CLI Commands section list the Junos OS or Junos OS Evolved set commands applied to the device at the site or template level.
  4. Enter the Junos OS or Junos OS Evolved set commands in the Additional CLI Commands text box to modify or override the site or template level configuration settings, and then click Save.

    For guidelines on using the Additional CLI Commands, see Manage CLI Configuration Changes.

    The Confirm Changes pop-up appears, displaying the configuration that was entered in the previous step.
  5. Verify that the configuration is rendered correctly.

    • If the configuration is not rendered correctly, click the close (X) icon to go back to the Configuration tab and make modifications as needed.

    • If the configuration is rendered correctly, click Save.

      You are returned to the Configuration page.

    The new configuration is pushed to the router.

When configuration is successfully committed on the router, a Config Changed by User event is generated. View this event under Router Events on the Router Insights page. This event shows a UI_COMMIT_COMPLETED response. Click View Details to see the configuration difference.

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. The router event details indicate that the commit failed and include the reported syntax error, allowing users to identify and correct the issue.