- 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 Link
To add a link in the topology map:
Field | Description |
---|---|
Properties | |
Name | Enter a name for the link. |
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 the name of the egress (destination) node from the list. |
IP A | Enter the IPv4 address of Node A. |
IP Z | Enter the IPv4 address of Node Z. |
IPv6 A | Enter the IPv6 address of Node A. |
IPv6 Z | Enter the IPv6 address of Node Z. |
Bandwidth AZ and ZA | Enter the bandwidth (in bps) for each direction (Node A to Z and from Z to A). You must enter a number immediately followed by K (Kbps), M (Mbps), or G (Gbps). For example, 10M signifying 10 Megabits per second. Note: If you enter a value without units, bps is applied. |
ISIS Off/On | Toggle the button to enable or disable IS-IS protocol.
|
RSVP Off/On | Toggle the button to enable or disable the RSVP protocol. Enter the RSVP bandwidth for each direction AZ (Node A to Z) and ZA (from Z to A). |
Constraints | |
Admin Group AZ and ZA | Select the bit-level link coloring from the list for A to Z and Z to A links. |
Delay AZ and ZA | Enter the delay metric for each direction in milliseconds for A to Z and Z to A links. This field is used only if the routing method is set to Delay Metric. When the program performs path placement and is trying to find the best route for a call, delay metrics are examined to determine the desirability/undesirability of a link. Two delay metrics are supported, one for each direction of the trunk. If the hardware does not support asymmetric delay metrics, the second delay is marked as '-'. If a delay metric is not defined for a trunk, a default delay is calculated based on propagation delay and serialization delay. |
Admin Weight AZ and ZA | Enter the admin weight (number) for links between Node A and Z. Range: 1-2^31 (1 through 2147483648). |
Util Reroute Threshold AZ and ZA | Enter the link utilization threshold (in percentage) for A to Z and Z to A links. When the link utilization exceeds the specified threshold, the controller reroutes the LSPs to reduce the link utilization within the threshold value. |
Packet Loss Threshold | Enter the packet loss threshold in percentage for A to Z and Z to A links. When packet loss on a link exceeds this threshold, the link is considered unstable and rerouting of traffic to avoid the link is triggered. To achieve this, a maintenance event is created for each link, temporarily making the link unavailable for traffic. |
Advanced | |
Description | Enter a text description for the link. |
Type | Click the Type field and select the type of link you want to create from the list. |
Slices | Enter one or more numbers (positive integers) which represents the topology slice IDs. Range is 1 through 18446744073709551615. |
Protected Link | Toggle this button to enable protected link status for this link. By default, link protection is disabled. PCE supports preferred protected links routing constraint for packet LSPs. When this constraint is selected, PCE computes the path that maximizes the number of protected links, and therefore offers the best overall protection. |
Custom Attributes Node A and Node Z | 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:
|