Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Step 2: Up and Running

Onboard Routers

You must first onboard the router to Juniper Mist Routing Assurance and assign it to a site. After the router is onboarded, Juniper Mist Routing Assurance starts providing information about the router's health and performance.

Before you onboard a router, ensure that;

  • The router can reach the gateway.

  • The router can connect to the Internet. You can verify this by pinging the IP address 8.8.8.8.

  • The firewall is configured to allow outbound access on TCP port 2200.

  • Take a backup of the existing Junos OS configuration on the router by running the following command on the router's CLI.

    Backup configuration is saved in the config directory.

To onboard a router:

  1. Log into Juniper Mist Routing Assurance.
  2. Navigate to Organization > Inventory.

    The Inventory page appears.

  3. On the Routers tab, click Adopt Routers.

    The Router Adoption page appears displaying the outbound SSH configuration that needs to be committed on the router to establish a connection with Juniper Mist Routing Assurance.

  4. Click Copy to Clipboard to copy the CLI commands to the clipboard.
  5. Log into the router's CLI using SSH and enter configuration mode.
  6. Paste the contents of the clipboard and commit the configuration on the router.
  7. In Juniper Mist Routing Assurance page close the Router Adoption page. Click Organization > Inventory > Routers tab.
    The Inventory page appears displaying the newly onboarded router in the Unassigned state.
    Note:

    After the outbound SSH configuration is committed from the router's CLI, it takes about three minutes for the router to be displayed on the Inventory page in Juniper Mist Routing Assurance.

Assign Routers to Sites

After the router is onboarded successfully, you must assign the router to a site.

To assign a router to a site:

  1. From the menu, click Organization > Inventory > Routers tab.
    The onboarded routers are displayed.
    The status of a router that is onboarded to Juniper Mist Routing Assurance, but is not assigned to a site appears as Unassigned.
  2. Select the router that you want to assign to a site and click the More drop-down list.
  3. Click Assign to Site.

    The Assign Routers pop-up appears.

  4. From the site drop-down list, select the site you want to assign the router to and click Assign to Site.
  5. Click Close to close the assign routers pop-up.

    After the router is assigned to a site, the status of the router changes to Connected, indicating that the router can be monitored from Juniper Mist Routing Assurance. The status of a router changes to Disconnected if your network stops allowing outbound SSH connection or if the outbound SSH configuration is removed from the router.

    Note:

    You can monitor a router only after it is assigned to a site.

View Router Insights

After a router is connected to Juniper Mist Routing Assurance, you can view information about the health of the routing platform and its components, the router's performance, and connectivity. Administrators can use this information to proactively respond to network events that impact network traffic. You can view router insights by clicking Router Insights from the Routers: Router name page.

Note: After a device is onboarded, the current device information is displayed first, along with by a time stamp in the top right corner of the table. Graphs are populated after the required aggregation interval of 10 minutes or 1 hour, depending on the requested time-range.
Note:

After an event occurs in the network, it takes up to three minutes for the events to be visible in the router insights dashboard in Juniper Mist Routing Assurance.

Information that Juniper Mist Routing Assurance provides includes the following:

  • Front panel, port list, and physical inventory information

  • Routing table information

  • BGP sessions and BGP peer information

  • OSPF summary information

  • Router interface queues

  • Router charts displaying CPU and memory utilization and port errors

  • Visualization in charts and graphs

  • Site-level aggregation of router events