- 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
-
Device Life-Cycle Management Overview
Device life-cycle management (LCM) in Paragon Automation is divided into various tasks that you perform as Day -2, Day -1, Day 0, Day 1, and Day 2 activities. The tasks are divided so that you follow a structured process to onboard, manage, and offboard devices. The activities for managing a device life cycle are divided as:
Day -2 activities in which a network architect plans the device role and device configuration for that device role. See Add Network Resource Pools and Profiles (Day -2 Activities).
- Day -1 activities in which a network planner prepares a plan for onboarding the device to Paragon Automation. See Prepare for Device Onboarding (Day -1 Activities).
- Day 0 activities in which a field technician installs the device. The field technician or a network administrator gets Paragon Automation to manage the device. See Install and Onboard the Device (Day 0 Activities).
- Day 1 and Day 2 activities in which a network administrator monitors the health and functioning of the device and moves the device to production. See Move a Device to Production (Day 1 and Day 2 Activities).
Onboard a Device
You can use Paragon Automation to onboard:
New devices that you procure for your network (greenfield devices).
You onboard greenfield devices by using a network implementation plan, which includes the management configurations (IP address, hostname, and so on) and infrastructure configurations (routing protocol configurations). Paragon Automation applies the following configurations on a device by using a network implementation plan:
Basic device-level configurations (for example, IP address configurations, hostname, and software image to be used) and routing protocols (for example, IS-IS, OSPF, BGP, RSVP, LDP, and PCEP).
Configuration for links with neighboring devices. The neighboring devices are devices that are a part of the same network implementation plan.
Configuration for performing health checks, connectivity checks, and running trust scans.
These configurations are applied when you onboard a device to Paragon Automation either through the field tech UI or by committing outbound SSH commands on the device.
Devices that exist in your network (brownfield devices).
You onboard brownfield devices by committing outbound SSH commands for connecting with Paragon Automation, on the device. Paragon Automation provides you the SSH commands that you can copy and commit on the device. The onboarding of a device by committing the outbound SSH commands is referred to as adopting a device.
Manage and Monitor a Device
After you onboard a device, you can manage a device's inventory, apply licenses, perform backup and restore of device configurations, upgrade software, reboot the device, and access the CLI of the device. See Device Onboarding Workflow.
While Paragon Automation provides automated solution for managing configurations, device monitoring, and periodic Trust scans for greenfield devices, Paragon Automation also provides the conventional device LCM solutions for brownfield devices.
For a greenfield device, to upgrade a software, you update the software version to be applied on the device in the device profile or the network implementation plan used to onboard the device. Similarly, links and basic configurations that were committed on a device by using the network implementation plan can be updated by editing the network implementation plan and profiles used to onboard the device. You can also use configuration templates to apply advanced configurations on the device.
After onboarding, you can upgrade the software on a greenfield device by using the Software Upgrade option (Observability > Health > Troubleshoot Devices > More > Upgrade) as well, without having to update the network implementation plan.
In addition, Paragon Automation executes a predetermined set of tasks (based on the configurations in the plan and profiles) for automatic monitoring and operations of the greenfield devices right from when the device is onboarded. For example, when you enable BGP or RSVP protocols in the profiles, Paragon Automation monitors the functioning of the BGP and RSVP protocols and displays any alerts or alarms related to the functioning of the protocols, right after the device is onboarded.
Paragon Automation GUI provides an integrated view of all the information about a device. On the Device-Name page (Inventory > Onboarding Dashboard > Device-Hostname), you can view general details, connectivity details, results of trust scans, and key performance indicators (KPIs), and assess the functioning of the device. You can also upgrade software and perform a backup of the device configurations from the same page.
For brownfield devices, Paragon Automation provides options for software upgrade, adding licenses, applying configurations by using configuration templates, and backing up configurations under the Observability > Health > Troubleshoot Devices menu.
Decommission a Device
When you want to decommission (offboard) a greenfield device, you can:
Use the network implementation plan that you are using to manage a device to decommission the device. See Offboard a Network Implementation Plan.
When you use a network implementation plan to offboard, device configurations are deleted, but the outbound SSH configuration is retained. You must delete the outbound SSH configuration for Paragon Automation to disconnect from the device. See Release a device.
Use the Release option to delete the outbound SSH configuration so that Paragon Automation disconnects from the device, See Release a device.
In this case, the other configurations committed on the device are retained. You must access the device CLI and manually delete the configurations.
To decommission a brownfield device, you simply use the Release option in Paragon Automation to delete the outbound SSH configuration on the device. See Release a device.
Benefits of Device Life Cycle Management
Provides an automated solution for managing the life cycle of new devices procured for a network.
The profiles and network implementation plan that are used to onboard and manage multiple devices considerably reduce the time and effort taken to onboard and manage the devices. For example, to upgrade software running on five devices, you can simply edit the software version in the network implementation plan used for onboarding the devices and publish the plan. Paragon Automation updates the software on the devices to the version you mention in the plan.
