Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Prerequisites

Prerequisites for Onboarding a Router

Before you onboard a router, ensure that:

  • The router can reach the gateway.

    Note:

    If a firewall exists between Juniper Routing Assurance and the router, configure the firewall to allow outbound access on TCP ports 2200 and 443, from the management port of the router.

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

  • You take a back up of the existing Junos OS configuration on the router by running the following command from the router's CLI:

    Backup configuration is saved in the config directory. You can view the backed-up configuration file by starting the Junos OS shell and running the following commands:

    Note: We recommend that you back up the existing Junos OS configuration on a router before onboarding it.
  • If routers use management VRF, you must configure outbound SSH to use the corresponding management routing instance to ensure successful onboarding. As Juniper Routing Assurance uses the inet.0 routing table for outbound SSH by default, a misconfiguration might prevent the router from establishing a connection during onboarding.

    To configure management routing instance, run the command set system outbound-ssh routing-instance mgmt_junos.

    Replace mgmt_junos with the routing-instance name configured in your environment.

Configure Ports

Table 1 lists the ports that should be enabled to allow the router to connect with the cloud.

Table 1: Ports Configuration

Service Type

Portal/Endpoint

Port Number

Admin Portal

routing.ai.juniper.net

TCP 443

Router to Juniper Cloud

oc-term.ai.juniper.net

TCP 2200

Receive Webhook Notifications for Router Events

api-ws.ai.juniper.net

TCP 2200

Router gNMI Telemetry to Juniper Cloud

gnmi-term.ai.juniper.net

TCP 32767

Note: The endpoints in Table 1 use dynamic IP addressing. To ensure continuous connectivity, configure firewall rules using Fully Qualified Domain Names (FQDNs) instead of static IP addresses.