- 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
-
Network Implementation Plan Overview
Paragon Automation uses a network implementation plan to commit configurations on the device during device onboarding, and update configurations after the 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 currently present in the network and also, to any PE device that might be added to the network after the device is onboarded.
Before you (a network planner) onboard a device, you must create a network implementation plan to define the device configurations to be committed, and health, connectivity, and compliance [with Center for Internet Security (CIS)] checks to be performed on the device.
Network implementation plans define which device profiles and interface profiles should be applied to a device or a group of devices during onboarding. The profiles define which interfaces to configure, with protocols to enable, with IP addresses to assign, and so on.
Paragon Automation maps the serial number of a device during onboarding with the serial number that is included in a particular network implementation plan and the corresponding device and interface profiles are then applied to the device.
A single network implementation plan can include one or more devices. If you want to onboard multiple devices, you can add all of them to a single implementation plan, and within the plan, reference a different device profile for each device or specify a default device profile that will be applied to all the devices.
Paragon Automation can manage up to 800 devices. You can onboard a maximum of three devices parallelly at a time.
Additionally, the implementation plan allows the user to provide any required information to build the configuration. For example, for a given interface, you can be referencing an interface profile that does not have automatic address assignment enabled. In the Network Implementation Plan, you will provide the IP address that you want to configure on that interface while creating the network implementation plan.
You create a plan by adding devices, assigning device and interface profiles to the devices, and defining links from the devices to neighboring devices. A device profile contains configurations associated with a device such as IP address, autonomous system (AS) the device is a part of, tunnels to be created on the device, and BGP groups. The interface profiles contain the protocol configuration (IS-IS, OSPF, BGP, and RSVP) for the interfaces. See Device and Interface Profiles Overview for more information.
Paragon Automation provides a wizard in the GUI that guides you to create the plan. To create a plan, navigate to Inventory > Device Onboarding > Network Implementation Plan.
In the plan, you:
Add one or more devices that you want to associate with the plan.
Assign one or more device profiles and interface profiles to the devices. You can also define default device or interface profiles that would be assigned to all the devices and their interfaces in the network implementation plan.
Enter instructions on the type of pluggables to insert and cables to use for connecting to the device ports.
A field technician can view these instructions on the field technician UI while installing the device. So, we recommend that you use terminologies with which a field technician is familiar. See Install and Onboard the Device (Day 0 Activities).
Add the number of hardware elements (pluggables, memory, PSU, and fans) in the device for collecting health data.
Configure links from the device to neighboring devices. You can configure links only between devices in the same network implementation plan.
You cannot onboard multiple devices in an Implementation plan at the same time.
Figure shows an example of a network implementation plan ISP1 created for onboarding an ACX7024 device with serial number 12345.
To onboard the ACX7024 device, Paragon Automation:
- Matches the serial number mentioned in the network implementation plan with the serial number of the ACX7024 device.
Tags the ACX 7024 device with the label PE-Router and configures:
PE-1 as the hostname
192.168.1.1 as the loopback interface IPv4 address
Configures iBGP on the ACX 7024 device based on the PE-Devices device profile and peers the device with other devices with the PE-Router label.
Configures Interface ge-0/0/0.0 to run OSPF with metric 25 and MTU 9200 based on the CE-FACING interface profile referenced for this interface.
Configures Interface ge-0/0/1.0 to run IS-IS level 2 with metric 20 and MTU 9200 based on the CORE-FACING interface profile referenced for this interface.
Benefits
A network architect can provide instructions on the type of pluggables and cables to be used for a port, to a field technician. This helps the field technician to install the correct pluggables and connect correct cables to ports.
By using a network implementation plan, you can define the configuration for multiple devices once and commit them when the devices are onboarded. To modify the committed configurations on the devices later, you can change the configuration in the plan and push the changes to the devices.
When you use a plan for onboarding a device, Paragon Automation executes the health and connectivity checks during device onboarding. The health and connectivity checks during onboarding help you to ensure that the device will function without issues after the device is onboarded and is ready for production soon after onboarding.
When you use a plan to onboard a device, based on the configurations in the plan, playbooks for collecting metrics are enabled automatically. You do not have to separately configure monitoring. For example, if you enable BGP, Paragon Automation collects metrics for BGP and displays the data on the Paragon Automation UI.
By defining the links between devices in the plan, the links are configured on the devices while the devices are onboarded, enabling quick deployment of your network.
