- 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
- 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 VPN Service Health Monitoring Data
- Physical Interfaces Health Check Results
- Logical Interfaces Health Check Results
- L2 Circuit Service Health Check Results
- Performance Graphs to View Service Health 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 host disk usage
- show paragon backup
- show paragon certificate expiry-date certificate-type
- show paragon cluster (o)
- show paragon cluster applications (o)
- show paragon cluster common-services ingress (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 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
- 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
- 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
-
Device Onboarding Overview
Device onboarding refers to the steps that you must perform to enable Paragon Automation to manage the devices in your network. Device onboarding involves different personas in an organization performing different tasks to onboard devices.
A network architect prepares to add devices to the network and decides the roles for each device in the network. Based on the device role, the network architect creates resource pools, device profiles, and interface profiles.
Resource pools include values for network resources [IP addresses, loopback addresses, BGP cluster IDs, segment identifiers (SIDs), autonomous system number, and so on] that Paragon Automation can assign to the devices when automatic configuration is specified for the resources. See the Add Network Resource Pools for more details.
The device profiles include configurations such as IP loopback address, router ID, the software image to be used, and some routing protocols (such as BGP). The interface profiles include the routing protocol (IS-IS, OSPF, RSVP, and LDP) configurations. The network architect can also specify compliance and connectivity checks to be performed during device onboarding. See Device and Interface Profiles Overview for more details.
A network planner uses these profiles to create a plan (referred to as network implementation plan) for onboarding devices. In the plan, the network planner assigns the device and interface profiles to the devices to be onboarded. The planner can also configure links between the devices included in the plan. See Network Implementation Plan Overview for more details.
The planner also adds information about the type of pluggables and cables to be used for each port on a device.
Paragon Automation commits configurations defined in the device and interface profiles, and the network implementation plan on the device during device onboarding. You can use the profiles and plan to also add configurations after a device is onboarded. For example, if a plan has an RSVP LSP configured from a device to all the provider edge (PE) devices, an LSP is configured from the device to all the PE devices that are present in the network during onboarding and also, to any PE device that might be added to the network after the device is onboarded.
After a device is onboarded and brought to production, you can use the network implementation plan to manage the devices. For example, if you want to upgrade software on all the devices in the plan, you specify the software version to be installed in the plan and push the updates on to the devices (known as publish). Paragon Automation updates the software that is installed on the devices to the version you specified in the plan.
Figure 1 shows the device onboarding workflow in Paragon Automation for a new device (greenfield).
Apart from the field technician, the superuser or network administrator can also onboard devices (both greenfield and brownfield devices) by committing the outbound SSH commands that Paragon Automation provides.
After the device connects with Paragon Automation, you can manage the device by using Paragon Automation. See Device Management Workflow.
Benefits
Paragon Automation facilitates faster deployment of devices to the network by committing device configurations and checking the health and connectivity of the devices during onboarding.
The network implementation plan provides an easy way to upgrade software or modify configurations on multiple devices at the same time.
