- 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 Integration With Anuta ATOM
- 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 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 Configure Your Network
- play_arrow Topology
- play_arrow Network Information Table
- Network Information Table Overview
- About the Node Tab
- Add a Node
- Edit Node Parameters
- Delete a Node
- About the Link Tab
- Add a Link
- Edit Link Parameters
- Delete a Link
- About the Tunnel Tab
- Understand How Pathfinder Handles LSPs
- Reroute LSPs Overview
- Segment Routing Overview
- Add a Single Tunnel
- Add Diverse Tunnels
- Add Multiple Tunnels
- Edit and Delete Tunnels
- About the Demand Tab
- About the Interface Tab
- Container LSP Overview
- About the Container LSP Tab
- Add a Container LSP
- Edit Container LSP Parameters
- Maintenance Event Overview
- About the Maintenance Tab
- Add a Maintenance Event
- Edit a Maintenance Event
- Simulate a Maintenance Event
- Delete a Maintenance Event
- About the P2MP Groups Tab
- Add a P2MP Group
- Edit P2MP Group Parameters
- About the SRLG/Facility Tab
- Add an SRLG/Facility
- Edit SRLG/Facility Parameters
- About the Topology Group Tab
- Add Anycast Group Tunnels
- play_arrow Tunnels
- play_arrow Change Control Management
-
- 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
-
Configure Paragon Insights Notification for LSP Gray Failures
Paragon Insights can notify Paragon Pathfinder if there are gray failures in Label Switched Paths (LSPs) or nodes connecting the LSPs in an MPLS network. Gray failures or short-lived failures are mainly caused by interface-related issues such as link flaps, traffic exceeding bandwidth thresholds, link or interface errors, network delay, or packet loss and node-related issues such as routing daemon CPU utilization exceeding threshold, routing protocol issues, memory leaks, chassis temperature rising beyond a set threshold, or line card failures. When an LSP consists of a faulty link due to a gray failure, Paragon Insights can be configured to notify Paragon Pathfinder which marks the link or node for maintenance and removes the maintenance mode status when the cause of gray failure is resolved.
Before you begin to configure functions, you must have completed configuring the interface.statistics/check-interface-flaps rule. The interface.statistics/check-interface-flaps rule periodically collects link flap counts and notifies Paragon Pathfinder when the link flap counts exceeds a pre-defined threshold.
The following checklist ensures that you have configured the interface.statistics/check-interface-flaps rule in Rules page:
Selected sensor and configured sensor frequency in interface.statistics/check-interface-flaps rule in Sensor tab.
Added a field to take flap count from sensor in Fields tab.
Added a field to set flap threshold in Fields tab.
Added a field to capture interface name in Fields tab.
Added a Term to check if link flaps are increasing compared to threshold value for a given time range in Triggers tab.
Added a Term to check if link is stable in Triggers tab.
Paragon Insights has a number of pre-defined rules that collect interface statistics such as flap count, administrative state of the interface, neighbor interface states, and so on. Let us take the example of how you can configure a function in Paragon Insights that sends Paragon Pathfinder a maintenance mode alert when flap count increases consistently.
After you configure the interface.statistics/check-interface-flaps rule, you can configure functions to generate or remove link maintenance mode in the Functions tab of the rule. The Python function catalog notify_pathfinder.py has pre-defined functions for generating and removing maintenance modes. You can make a reference to these functions and set arguments (parameters).
To add a link maintenance function:
In the Triggers tab, you can call the function name you added and enter the value for the arguments (function parameters).
To call the generate maintenance mode function for link flaps in a trigger:
Click Triggers tab.
In the link_flaps trigger, click on the Term you configured to check if link flaps exceed the threshold limit in a given time.
Under the Then statement of the Term, click the Add Function button.
Select the function name you configured to generate maintenance link from the drop-down menu.
All the arguments (function parameters) you entered in the Functions tab appear here.
Enter $ followed by argument name in the value field for each argument. You can also select a suitable input from the drop-down menu. For example, $interface-name for the argument ifd_name, $mnt_time for argument mnt_time, and so on.
Click Save and Deploy.
You can follow the same instructions to add remove_link_maintenance function in Functions tab and define argument values for that function under the Term in Triggers tab that checks if an interface is stable.
The four main functions that enable Insights to trigger notifications are generate_link_maintenance and remove_link_maintenance for any interface related issues and generate_node_maintenance and remove_node_maintenance for any node related issues.
To check nodes or interfaces that are under maintenance, navigate to Network > Topology in the left navigation bar. Click ellipse (...) in the panel with node, link and tunnel tabs. Select Maintenance in the drop-down menu. The Maintenances page displays details of links and nodes kept under maintenance.