- play_arrow Introduction
- play_arrow Overview
- About the Paragon Automation (Pathfinder, Planner, Insights) User Guide
- Paragon Automation Overview
- Paragon Pathfinder Overview
- Paragon Insights Overview
- Paragon Planner Overview
- Understand Differences between Paragon Pathfinder and Planner
- Paragon Automation GUI Overview
- Paragon Automation GUI Menu Overview
- play_arrow Access the Paragon Automation GUI
- play_arrow Access the Paragon Planner
- play_arrow Configure SMTP, LDAP, and Portal Settings
- play_arrow Manage Users
- play_arrow Manage Roles
- play_arrow Manage User Groups
- play_arrow Identity Providers
-
- play_arrow Workflows
- play_arrow Base Platform
- play_arrow Paragon Pathfinder
- play_arrow Paragon Planner
- play_arrow Paragon Insights
-
- play_arrow Manage Devices and Network
- play_arrow Devices
- play_arrow Device Groups
- play_arrow Device Images
- play_arrow Network
- play_arrow Network Groups
- play_arrow Topology Filter
-
- play_arrow Manage Device Templates and Configuration Templates
- play_arrow Configuration Templates
- Configuration Templates Overview
- Configuration Templates Workflow
- About the Configuration Templates Page
- Add Configuration Templates
- Preview and Render a Configuration Template
- Assign Configuration Templates to a Device Template
- Deploy a Configuration Template to a Device
- Edit, Clone, and Delete a Configuration Template
- play_arrow Device Templates
-
- play_arrow Manage Playbook, Rules, Resources, and Graphs
- play_arrow Playbooks
- play_arrow Rules
- Understand Paragon Insights Topics
- Rules Overview
- About the Rules Page
- Add a Predefined Rule
- Edit, Clone, Delete, and Download Rules
- Configure a Custom Rule in Paragon Automation GUI
- Configure Paragon Insights Notification for LSP Gray Failures
- Configure Multiple Sensors per Device
- Understand Sensor Precedence
- Configure Sensor Precedence
- play_arrow Resources
- Understand Root Cause Analysis
- About the Resources Page
- Add Resources for Root Cause Analysis
- Configure Dependency Between Resources
- Example Configuration: OSPF Resource Dependency
- Edit Resources and Dependencies
- Upload Resources
- Download Resources
- Clone Resources
- Delete User-Generated Resources and Dependencies
- Filter Resources
- play_arrow Graphs
- play_arrow Grafana
-
- play_arrow Manage Sensor Settings, Insights Settings, and Data Summarization Profiles
- play_arrow Sensor Settings
- Sensors Overview
- About the Ingest Settings Page
- Configure NetFlow Settings
- Configure a Rule Using Flow Sensor
- About the Frequency Profiles
- Manage Frequency Profiles
- Apply a Frequency Profile
- Configure Offset Time
- Configure a Rule Using Server Monitoring Sensor
- Configure Native GPB Ingest
- Configure sFlow Settings
- Configure SNMP Ingest
- Configure a Rule Using SNMP Scalar
- Configure SNMP Trap and Inform Notifications
- Configure Outbound SSH Port for iAgent
- Configure System Log Ingest
- System Log Optional Configurations
- Configure a Rule Using Syslog
- Understand Inband Flow Analyzer 2.0
- Configure Device Details for Inband Flow Analyzer Devices
- Delete an Inband Flow Analyzer Device
- Understand Bring Your Own Ingest
- Load BYOI Default Plug-ins
- Configure Bring Your Own Ingest Default Plug-in Instances
- Build and Load BYOI Custom Plug-in Images
- Configure Bring Your Own Ingest Custom Plug-in Instances
- Use Sample Rule and Playbook Configurations for BYOI Custom Plug-in Instances
- Configure Ingest Mapping for Default BYOI Plug-in Instances
- Delete a BYOI Plug-in
- About the Diagnostics Page
- Use the Self Test Tool
- Use the Reachability Test
- Use the Ingest Test Tool
- Use the No-Data Tool
- Paragon Insights Tagging Overview
- Types of Tagging
- Add a Tagging Profile
- Apply a Tagging Profile
- Delete a Tagging Profile
- Understand User-Defined Actions and Functions
- Modify User-Defined Action, Function, and Workflow Engines
- Enable UDA Scheduler in Trigger Action
- Understand kube-state-metrics Service
- play_arrow Insights Settings
- About the Insights Settings Page
- Add Alert Blackouts
- About Alert Notifications
- Use Exim4 for E-mails
- Configure the Exim4 Agent to Send E-mail
- Configure a Notification Profile
- Enable Alert Notifications for Device Groups and Network Groups
- Configure Report Settings
- Configure Scheduler Settings
- Configure a Retention Policy
- Configure Destination Settings
- Time Series Database (TSDB) Overview
- Manage Time Series Database Settings
- Backup and Restore the TSDB
- Time Series Database Replication Scenarios
- play_arrow Data Summarization Profiles
-
- play_arrow Monitoring
- play_arrow Monitor Network Health
- play_arrow Manage Alarms and Alerts
- play_arrow Monitor Jobs
- play_arrow Analytics
- play_arrow Monitor Workflows
-
- play_arrow Reports
- play_arrow Health Reports
- play_arrow Network Reports
- play_arrow Maintenance Reports
- play_arrow Inventory Reports
- play_arrow Demand Reports
-
- play_arrow Administration
- play_arrow Manage E-mail Templates
- play_arrow Manage Audit Logs
- play_arrow Configure External EMS
- play_arrow Manage Task Scheduler
- play_arrow Manage Security Settings
- play_arrow License Management
-
Understand LSP Delegation and Undelegation
In Paragon Pathfinder, the Path Computation Element (PCE) computes paths in the network and applies computational constraints.
You can delegate the management of Path Computation Client-controlled LSPs (PCC-controlled LSPs) to the PCE either by using the Paragon Automation GUI (from the Configure LSP Delegation page [Network > Tunnels > Configure LSP Delegation]) or the Junos OS CLI. After delegation, such LSPs are managed by the PCE and are classified as PCC-delegated LSPs.
When LSPs are managed by the PCE, you can reprovision LSPs (directly from the GUI) for which provisioning has failed or for which the path isn’t the expected path. In addition, you can also enable optimization to re-establish an optimal set of paths for the network. Pathfinder does not support reprovisioning and optimization for PCC-controlled LSPs.
You can also delegate the LSPs back to the PCC (also known as undelegating the LSPs from the PCE), after which the LSPs are managed by the PCC and are re-classified as PCC-controlled LSPs. This is useful if Pathfinder is down or if the LSPs are not working as expected.
For the procedure to delegate and undelegate LSPs from the Paragon Automation GUI, see Add and Remove LSP Delegation.
Understand the Behavior of Delegated and Undelegated LSPs
In both standalone (where the Paragon Automation components run on a single primary node) and high availability (HA) cluster configurations (where the Paragon Automation components run on multiple primary nodes), whenever a Path Computation Element Protocol (PCEP) session on a PCC goes down, all the LSPs that originated from that PCC are removed from the Pathfinder database, except those LSPs with parameters configured from the GUI.
For PCC-controlled LSPs, all the configuration changes made to the LSP attributes from the router (that is, the PCC) are stored only in the router’s configuration file. When you delegate such LSPs to the PCE and change the LSP attributes from the GUI, the changes are stored only in the Pathfinder database. The PCE communicates the changes to the PCC by using PCEP.
You can still make changes to the LSP attributes from the router and these changes are stored in the router’s configuration file, but the changes do not take effect as long as the LSPs remain delegated to the PCE.
The configuration changes made from the PCC take effect automatically only after the LSPs are undelegated from the PCE, which means that the control of the LSPs is returned to the PCC. After undelegation, the PCE obtains the LSP state from the PCEP report messages. If you change the LSP attributes from the router and the PCE isn’t available at this time, the PCE obtains the latest LSP state after it becomes available. Therefore, if you delegate such LSPs to the PCE, the LSPs carry the latest state.
If you perform the Undelegate operation on a delegated LSP, the Path Computation Server (PCS) uses the bandwidth reported by the device for the planned bandwidth instead of the user input value.
