- play_arrow Introduction
- play_arrow 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
-
Add a Container LSP
To add a container LSP:
Field | Description |
---|---|
Properties | |
Provisioning Method | Only PCEP is available. |
Provision Type | Select RSVP or SR. |
Container Name | Enter name for the Container LSP. Only alphanumeric characters, hyphens, and underscores are allowed. Other special characters and spaces are not allowed. Note: The name you assign to the container LSP is used for automatic naming of the sub-LSPs that are created. |
Node A | Click the Node A list and select the name of the ingress (source) node from the list. |
Node Z | Click the Node Z list and select an egress (destination) node from the list. |
Merging Bandwidth | Enter merging bandwidth value. The container normalization task computes aggregated bandwidth for each container LSP and sends it to the Path Computation Server (PCS). Aggregate bandwidth thresholds are used to trigger merging of sub-LSPs during normalization. When the average bandwidth per sub-LSP (computed using aggregate bandwidth of container and current number of sub-LSPs) falls below the merging bandwidth (the lower threshold), sub-LSPs are reduced during normalization. Note: Aggregation is based on the selected percentile [80th, 90th, 95th, 99th (X percentile)], or Average, or Max. For more information, see Table 2. |
Splitting Bandwidth | Enter splitting bandwidth value. The container normalization task computes aggregated bandwidth for each container LSP and sends it to the Path Computation Server (PCS). Aggregate bandwidth thresholds are used to trigger splitting of sub-LSPs during normalization. When the average bandwidth per sub-LSP (computed using aggregate bandwidth of the container and current number of sub-LSPs) is above the splitting bandwidth (upper threshold), sub-LSPs are added during normalization. Note: Aggregation is based on the selected percentile [80th, 90th, 95th, 99th (X percentile)], or Average, or Max. For more information, see Table 2. |
Minimum and Maximum LSP Count | Enter the minimum and maximum number of sub-LSPs that can be created in the container LSP. Range is 1 through 32767. |
Minimum and Maximum LSP Bandwidth | Enter the minimum and maximum bandwidth that can be signaled for the sub-LSPs during normalization or initialization, immediately followed by units (no space in between). Valid units are:
For example, 50M, 1000b, 25g. If you enter a value without units, bps is applied. |
Planned Metric | Enter the metric value for static tunnel or use the up and down arrows to increment or decrement the value. For more information, see Basic LSP Configuration in MPLS Applications User Guide. |
Setup | Enter the RSVP setup priority for the tunnel traffic. Priority levels range from 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS LSP definition in Junos OS. |
Hold | Enter the RSVP hold priority for the tunnel traffic. Priority levels range from 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS LSP definition in Junos OS. |
Routing Method | Select a routing method from the following:
|
Bandwidth Sizing | Toggle the button to enable bandwidth sizing. By default, this option is disabled. Once enabled, configure the following parameters:
|
Constraints Enables you to configure administrative groups to bypass label-switched paths (LSPs). For more information, see Assign Names to Admin Group Bits. | |
Admin Group Include All | Specifies the administrative groups whose links the bypass LSP must traverse. Select one or more bit-level link coloring options from the list. |
Admin Group Include Any | Specifies the administrative groups whose links the bypass LSP can traverse. Select one or more bit-level link coloring options from the list. |
Admin Group Exclude | Specifies the administrative groups to exclude for a bypass LSP. Select one or more bit-level link coloring options from the list. |
Advanced | |
Description | Enter a description for the Container LSP. |
IP Z | IP address of Node Z. |
Custom Attributes | Simple name-value pairs which can be used to add any arbitrary customer-specific information. For example, to differentiate between properties for different vendor nodes. To add custom properties associated with the node:
Note:
|
Aggregation Statistic | Description |
---|---|
80th, 90th, 95th, 99th Percentile | Aggregation is based on the selected percentile. The ‘X’ percentile is the value at which ‘X’ percent of all the samples taken in the previous sampling period lie at or below the calculated value. |
Average | For each interval, the samples within that interval are averaged. If there are N samples for a particular interval, the result is the sum of all the sample values divided by N. |
Max | For each interval, the maximum of the sample values within that interval is used. |