- 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 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 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
-
ON THIS PAGE
Understand Root Cause Analysis
Paragon Automation monitors network resources — such as devices, interfaces, protocols, and label switched paths — through rules deployed in the network. Rules capture specific metrics called key performance indicators (KPI) for the network resources. Paragon Automation generates separate alarms when different KPIs experience an anomaly or an error. These alarms do not establish a causal relationship between two error events.
To find the root cause of multiple errors, Paragon Automation must first link rules to their corresponding resource. For example, the rules that monitor temperature must be linked to the chassis resource or rules that monitor interface admin status must be linked to the interface resource. Users can link a rule to a resource when a they configure a new resource or clone a system-generated resource. Secondly, Paragon Automation must perform root cause analysis by checking if an error in one resource leads to an error in another. To enable Paragon Automation to perform root cause analysis, you must configure dependency for the resources.
When Paragon Automation finds the root cause of several error events, it combines the alarms generated for these events into a top-down hierarchy based on the causal relationship between the events. Such a combined set of alarms is called a smart alarm.
Terms
The following list has frequently used terms and concepts connected with resources:
Resource—A resource is a specific component that constitute the network.
For example, chassis, line card, protocols, system memory, interfaces, and so on.
Resource Instance—Resources such as an interface, Flexible PIC Concentrators (FPC), router ids, or virtual private networks can have many instances. An instance is a specific realization of the resource. For example, an interface includes instances such as ge-0/0/1, et-1/0/0, xe-2/0/1, and so on.
Property—Properties define unique characteristics of a resource. A property is comparable to fields in rules.
For example, neighbor-id and maximum transmission unit (MTU) are characteristics of routing-options resource and interface resource, respectively.
Neighbor id is a unique characteristic of protocol OSPF as a resource.
Key property in resource— A key property uniquely identifies all instances of a resource.
For example, <variable>interface-name</variable> property uniquely identifies interface resource instance with name ge-0/0/0 from other instances. MTU cannot be a unique property.
Resource Dependency—Defines the relationship between two resources.
Dependent resource—In a resource dependency, a dependent resource is the one that depends on another resource. In a single-level resource dependency, a dependent resource is a child resource of another resource.
Dependency resource—In a resource dependency, a dependency resource is the one that impacts another resource. In a single-level resource dependency, a dependent resource is a parent resource of another resource.
Resources
A resource can be part of a device or the network. Device resources can be an interface, Flexible PIC Concentrator (FPC), chassis, OSPF, etc. Network resources are resources that span multiple devices in a network, such as IPSec tunnels, VPN, etc.
As with rules, you configure resources under the topic hierarchy in Paragon Automation. The resource properties are derived from rules. When you configure interface as a resource, you can choose the specific interface rules from which Paragon Automation detects a particular interface resource property. The exact rules you select to identify a resource depend on your use case.
When you configure a resource property (such as interface name or MTU), you can refer multiple rules where the values configured for the property are different. A resource property aggregates instances from referenced rules.
Resource Dependencies
Resource dependency defines the relationship between a dependent resource (child resource) and a dependency resource (parent resource). While configuring dependency, you begin with a dependent resource and refer dependency resources that the child resource depends on. A dependency configuration also has terms that contain the logic to map dependency between two resources.
There are three types of dependency based on the type of resources involved, as described in Table 1. You can define dependencies between resources in the same device (Local Device and Network), between resources in different devices (Other Device), between a network resource to another network resource (Other Network), and a network resource to a device resource (Other Device).
| Local Device and Network | Other Device | Other Network Group |
|---|---|---|
| Interface → line card | Interface 1 (device 1) → interface 2 (device 2) | VPN → interface 1 (device 1) |
| Line card → chassis | OSPF (device 1) → OSPF (device 2) | VPN → IPSec tunnel |
You can configure multiple single-level dependencies for a resource. Consider the following chains of dependencies:
- VPN → LSP → interface → Line card
- VPN → interface → Line card
When you configure VPN as a resource, you can define VPN’s dependency on Label Switched Paths (LSPs) as one dependency and VPN’s dependency on interface as a second dependency. For LSP as a resource, you can define its dependency on interface. For interface as a resource, you can define its dependency on line card.
A dependency term logic can involve checking parts of a dependent (child) resource property with parts of dependency (parent) resource's property, checking all instances of the dependency (parent) resource, checking all devices that have dependency (parent) resource instances, checking all or specific device groups, and checking all or specific network groups. Paragon Automation supports matches-with and user-defined functions for dependency logic.
As dependency configurations can involve complex operations, Paragon Automation also allows you to execute such operations in a function. The function returns a Boolean value that can be used to check if a dependency exists between resources.
Use Cases
Resource and dependency configurations serve the following use cases:
Root cause analysis — You can understand the root cause of a failure in your network. Refer the resource dependencies and use the relationship between resources to diagnose alerts generated by triggers in rules.
Smart alarms — Through smart alarms, Paragon Automation links several resources that have a failure to another resource that is the cause of the failure.
