- play_arrow Introduction
- play_arrow Overview
- play_arrow Access and Manage Paragon Automation Account
-
- play_arrow Administration
- play_arrow Introduction
- play_arrow Organization Management
- play_arrow Site Management
- play_arrow User Management
- play_arrow Inventory Management
- play_arrow Audit Logs
- play_arrow Tags
-
- play_arrow Observability
- play_arrow Introduction
- play_arrow Health Dashboard
- play_arrow Troubleshoot Devices
- play_arrow View Network Topology
- Network Topology Visualization Overview
- Network Visualization Options
- View Network Topology Details
- Network Table Overview
- About the Device Tab
- About the Link Tab
- About the Site Tab
- About the Tunnels Tab
- Dynamic Topology Workflow
- Configure a PCE Server
- Configuring PCEP on a PE Router
- Configuring Topology Acquisition Using BGP-LS
-
- play_arrow Trust and Compliance
- play_arrow Introduction
- play_arrow Manage Trust Settings and Trust Scores
- Compliance Standards Overview
- About the Compliance Benchmarks Page
- About the Compliance Tailorings Page
- Example: Create a Tailoring Document for NTP Settings
- About the Compliance Checklist Page
- Add a Checklist Template
- Add Checklist for a Device
- Import Scans and Update Rule Results in a Checklist
- Trust Plans Overview
- About the Network Score Formula Page
- Trust Score Overview
- About the Network Score Page
- About the Snapshots Page
- Add a Snapshot for a Target
- play_arrow Manage Compliance Scans
- play_arrow Manage Vulnerabilities
- play_arrow Monitor Integrity
-
- play_arrow Service Orchestration
- play_arrow Introduction
- play_arrow View Service Design Catalog
- play_arrow Manage Customers
- play_arrow Add Resources for Network Services
- play_arrow Manage Service Instances
- Service Instance Overview
- About the Service Instances Page
- View Service Instance Details
- View Passive Assurance Monitoring Data
- View EVPN Passive Assurance Monitoring Results
- View L2 Circuit Passive Assurance Monitoring Data
- View L3VPN Passive Assurance Monitoring Results
- Physical Interfaces Health Check Results
- Logical Interfaces Health Check Results
- Performance Graphs to View Passive Assurance Monitoring Data
- play_arrow Provision VPN Services
- play_arrow Monitor Service Order Execution Workflows
-
- play_arrow Active Assurance
- play_arrow Introduction
- play_arrow Test Agents
- play_arrow Tests and Monitors
- play_arrow Test Templates
-
- play_arrow Paragon Shell CLI Reference
- play_arrow Introduction
- play_arrow Operational Mode Commands
- file copy
- monitor
- request paragon backup
- request paragon cluster pods reset
- request paragon cluster upgrade
- request paragon config
- request paragon deploy
- request paragon deploy cluster
- request paragon destroy cluster
- request paragon fix-permission
- request paragon load
- request paragon repair-node
- request paragon replace-node
- request paragon restore
- request paragon running-config
- request paragon ssh
- request paragon ssh-key
- request paragon storage cleanup
- request paragon super-user password reset
- request system decrypt password
- request system reboot
- show configuration paragon cluster
- show configuration paragon cluster applications (o)
- show configuration paragon cluster common-services (o)
- show host disk usage
- show paragon backup
- show paragon certificate expiry-date certificate-type
- show paragon cluster (o)
- show paragon cluster details
- show paragon cluster namespaces
- show paragon cluster nodes
- show paragon cluster pods
- show paragon cluster pods namespace healthbot sort
- show paragon images version
- show paragon images version namespace
- show paragon pvc details
- show paragon version
- play_arrow Configuration Mode Commands
- delete paragon cluster
- load set
- set paragon cluster applications
- set paragon cluster common-services ingress
- set paragon cluster insights victoria-metrics
- set paragon cluster install
- set paragon cluster kubernetes
- set paragon cluster mail-server
- set paragon cluster nodes
- set paragon cluster ntp
- set paragon cluster papi
- set paragon monitoring
- set system login
- show paragon cluster (c)
- show paragon cluster applications (c)
- show paragon cluster common-services ingress (c)
- play_arrow Troubleshooting Commands
- Troubleshoot Using the Paragon Shell CLI Commands
- request paragon support information
- request paragon troubleshooting information
- request paragon debug
- request paragon debug get-tsdb-data
- request paragon debug insights-kafka-data
- request paragon debug kafka
- request paragon debug logs
- request paragon debug logs namespace
- request paragon debug postgres
- request paragon debug redis
- play_arrow Service Orchestration
- About the Service Orchestration cMGD CLI
- set foghorn:core org-id
- set service design default version
- set dag state failed
- show service order status
- show service order as-json
- show service order as-yaml
- show service designs
- show device dependent configuration
- show insights configuration
- show configuration foghorn:customers
- show service instance lock status
- show service instance lock token
- show service projects
- show service order history
- show airflow dags
- show airflow dag-runs
- show paragon orgs
- request service project add
- request service order sync
- request network resources load
- request service order load
- request service order place
- request service order modify
- request service order delete
- request service order submit
- request service order provision
- request service design install
- request service design uninstall
- request create graphdb
- request service order set
- request service instance lock
- request service instance unlock
-
Install and Onboard the Device (Day 0 Activities)
A device can be installed and onboarded in one of the following two ways:
A field technician, a user assigned the Installer role, installs and onboards devices to Paragon Automation as part of the Day 0 activities.
A network administrator can onboard a device by using the adopt method after the field technician installs the device. See Add a Device to Paragon Automationfor details.
You must install and onboard the devices associated with a network implementation plan one at a time.
The field technician UI in Paragon Automation enables you to access the network implementation plan of a device and get guidance to perform the Day 0 tasks.
Before you start onboarding a device to Paragon Automation, ensure that you have:
A laptop that you can use to access the field technician UI.
Internet connectivity on the laptop.
The credentials to log in to Paragon Automation.
Names of the organization and the site at which the device must be installed and onboarded.
Unboxed the device and mounted it on the rack.
For details about installing a Juniper device, see the corresponding device Hardware Guide or Quick Start Guide at the Documentation site. To access the Hardware Guide or the Quick Start Guide of a device, on the homepage of the Documentation site, under DOCUMENTATION BY CATEGORY, click View More > Device-Model in the Routing section.
For details about installing a third-party vendor device, see documentation from the respective vendor.
You must also ensure that:
If a firewall exists between Paragon Automation and the device, the firewall is configured to allow outbound access on TCP ports 443, 636, 2200, 6800, 4189, and 32,767.
Destination URL for LDAP:ldap-server: 636
Destination URL for NETCONF: web-ui-ip-address: 2200.
Destination URL for gNMI: web-ui-ip-address: 32,767.
Destination URL for Paragon Active Assurance Test Agent: test-agent-virtual-IP-address: 6800.
Destination URL to access Paragon Automation from a laptop or a desktop: web-ui-ip-address: 443.
PCE server VIP address.
Where, ldap-server is the IP address of the LDAP server, web-ui-ip-address is the IP address of the Paragon Automation Web UI, test-agent-virtual-ip-address is the Paragon Active Assurance virtual IP address, and VIP-address is the VIP address of the PCE server.
Static routes are configured to reach the Internet.
content_copy zoom_out_mapuser@device#set routing-options static route 0.0.0.0/0 next-hop Gateway-IP-address
A DNS server is configured on the device to resolve domain names or the device is able to access an external DNS server (for example, 8.8.8.8).
To onboard a device to Paragon Automation:
After device onboarding is complete, the next step is to move the device to production. See Move a Device to Production (Day 1 and Day 2 Activities).
| Test | Result Description |
|---|---|
| Management connectivity | You can view whether the device has established an outbound SSH connection to Paragon Automation. If the connection is not established, you must adopt the device manually. See Add a Device to Paragon Automation to adopt the device. |
| Hardware health | You can view the health of fans, line cards, power supply modules (PSMs), CPU, and memory. |
| Interfaces | You can view the health of the interfaces. |
| Optics | You can view whether you have installed the correct pluggable in the port. The test result is displayed as follows:
|
| Chassis Alarm | You can view the severity of alarms present on the device. The following color code is used to display the chassis alarms present on the device:
|
| Trust Result | You can view whether the hardware is authentic and whether a valid software is installed on the device. |
| Neighbor Connectivity | You can view the result of the ping tests from the device port to neighboring devices. Note: You can view the results of the ping tests only for those ports for which the Active Assurance tests are enabled in the network implementation plan. |
| Remote Connectivity | You can view the results of the following connectivity tests from the device ports to the remote endpoints (edge devices, Internet endpoints, and cloud provider endpoints configured in the network implementation plan):
|
- Onboard a Device without a Serial Number
- Onboard a Device without a Network Implementation Plan
- What's Next
Onboard a Device without a Serial Number
A network implementation plan can include one or more devices without a serial number. This is because, it is possible that while planning for device onboarding, the device is not yet procured and therefore the serial number is unavailable.
If the serial number entered on the Onboard a Device is incorrect, the UI provides a pop-up with Adopt and Select options. You (field technician) can:
- Click Adopt to commit the outbound SSH configuration
for the device. To adopt the device:
Click Adopt to view the outbound SSH commands that you can commit on the device to connect with Paragon Automation.
The Select Site pop-up window appears.
Select the site (location) to install the device.
Click Adopt.
A pop-up window displays the SSH commands that you must copy and commit on the device.
Click Copy.
The commands are copied to clipboard and the pop-up window closes.
Access the device in the configuration mode and commit the commands.
The device connects with Paragon Automation. The device is listed on the Inventory page (Router tab) of the Paragon Automation UI with status as Connected.
The device can now be managed by using the element management functions in Paragon Automation. See Device Management Workflow.
Click Select to associate a serial number to the device.
A message appears for you to confirm whether you want to assign a serial number to the device. Do one of the following:
Use the Onboard a Device page to proceed:
On the Onboard a Device page, enter the serial number of the device in the Serial Number field.
Click OK.
The Device List page appears. The Device List page displays the list of devices without a serial number under the Onboard section.
Click a device without a serial number in the Device List to associate the device with a serial number that you entered. The device that you select must match the model of the device you want to onboard.
The Add a Device page appears.
Go to step 5 of the onboarding procedure to proceed from the Add a Device page.
Use the Device List page to proceed:
Click the Device List menu to open the Device List page.
The Device List page lists all devices to be onboarded along with their serial number. The page also displays a few devices without a serial number.
Click on a device that does not have a serial number and that matches with the model of the device you want to onboard.
You get a message asking to confirm whether you want to associate a serial number.
Click OK.
The Onboard a Device page appears.
Enter the device's serial number in the Serial Number field.
The Add a Device page appears.
Go to step 5 of the onboarding procedure to proceed from the Add a Device page.
Onboard a Device without a Network Implementation Plan
When a network implementation plan does not exist, you can:
- Adopt the device by committing the outbound SSH configuration.
Click Adopt to view the outbound SSH commands that you must commit on the device to connect with Paragon Automation.
The Select Site pop-up window appears.
Select the site (location) to install the device.
Click Adopt.
A pop-up window displays the SSH commands that you must copy and commit on the device.
Click Copy.
The commands are copied to clipboard and the pop-up window closes.
Access the device in the configuration mode and commit the commands.
The device connects with Paragon Automation. The device is listed on the Inventory page (Router tab) of the Paragon Automation UI with status as Connected.
The device can now be managed by using the element management functions in Paragon Automation. See Device Management Workflow.
Associate the serial number of the device with a device in a network implementation plan that does not have a serial number and use that plan for onboarding the device.
Click the Device List menu to open the Device List page.
The Device List page lists all the devices to be onboarded along with the serial number.
Click a device that does not have a serial number. The device you select must match the model of the device you want to onboard.
You get a message asking to confirm whether you want to associate a serial number.
Click OK.
The Onboard a Device page appears.
Enter the device's serial number in the Serial Number field.
Go to step 5 of the onboarding procedure to proceed from the Add a Device page.
What's Next
If the device is onboarded device by using the network implementation plan, a Super User or Network Admin can move the device to production and manage the device by using the network implementation plan. See Move a Device to Production (Day 1 and Day 2 Activities).
If the device does not use the network implementation plan to onboard a Super User or Network Admin can manage the device by using the element management functions in Paragon Automation. See Device Management Workflow.
