Manage Devices, Device Groups, and Network Groups
Use the appropriate Configuration pages from the left-navigation menu to manage devices, device groups, and network groups. Paragon Insights (formerly HealthBot) supports both Junos devices by default and third party vendor devices with the required license installed. You must add a device to one or more device groups or create a network group before you can apply Paragon Insights rules and playbooks to a device. Network groups allow you to correlate health status data between multiple devices across the network. For example, you can create a network group that monitors the ping times between two or more devices and notifies you if the ping times are too high.
Adding a Device
To add a device:
- Click the Configuration > Device option in the left-nav bar.
- Click the add device button (+).
- Enter the necessary values in the text boxes and select
the appropriate options for the device.
The following table describes the attributes in the Add a Device window:
Attributes
Description
Name
Name of the device. Default is hostname. (Required)
Hostname / IP Address / Range
Hostname or IP address of a single device. If you are providing a range of IP addresses, enter the IP address for the device that marks the start and end of the address range. (Required)
System ID to use for JTI
Unique system identifier required for JTI native sensors. Junos devices use the following format: <host_name>:<jti_ip_address>
When a device has dual routing engines (REs), it might send different system IDs depending on which RE is primary. You can use a regular expression to match both system IDs.
Flow/IFA Source IPs
Enter the IP address(es) that this device uses to send NetFlow data to Paragon Insights.
The IP address or addresses are used to send probe packets for flow monitoring using Inband Flow Analyzer (IFA).
If there are more than one IP address, separate them with a comma.
OpenConfig Port Number
Port number required for JTI OpenConfig sensors. The default value is 32767.
iAgent Port Number
Port number required for iAgent. The default value is 830.
Vendor
Lists the vendor or supplier of the device you are using.
The operating system you can select from the OS drop-down list depends on the vendor you select from the Vendor drop-down list.
The following are the list of options you can choose from.
Select Juniper from the vendor drop-down list to select either Junos or Junos Evolved operating systems from the OS drop-down list.
Select CISCO from the Vendor drop-down list to select either IOSXR or NXOS operating systems from the OS drop-down list.
With Paragon Insights Release 4.0.0, NXOS OS is also supported.
Note:If you plan to use Cisco IOS XR devices, you must first configure the telemetry. For more information, see Paragon Insights Installation Requirements
Select Arista from the Vendor drop-down list to select EOS operating system from the OS drop-down list.
Select Paloalto from the Vendor drop-down list to select PANOS operating system from the OS drop-down list.
Select Linux from the Vendor drop-down list and you can enter the name of the operating system in the OS field.
If you select Other Vendor, the Vendor Name and OS Name fields are enabled. You can enter the name of the vendor of your choice in the Vendor Name field and the corresponding operating system for the vendor in the OS field.
Consider the following example. If the operating system of a vendor (listed in the Vendor drop-down list) is not listed (in the OS drop-down list), you can select the Other Vendor option to enter name of the vendor and operating system of your choice.
Starting with Paragon Insights Release 4.0.0, Paragon Insights supports Arista Networks, Paloalto Networks, and Linux vendors.
Timezone
Timezone for this device, specified as + or -hh:mm. For example, +07:00
Syslog Source IPs
List of IP addresses for the device sending syslog messages to Paragon Insights. For example,
10.10.10.23,192.168.10.100.Syslog Hostnames
List of hostnames for the device sending syslog messages to Paragon Insights. For example, router1.example.com.
SNMP
SNMP Port Number
Port number required for SNMP. The port number is set to the standard value of 161.
SNMP Version
Select either v2c or v3 in the drop-down menu.
SNMP Community
This field appears if you selected v2c in SNMP Version field.
Enter an SNMP Community string if you configure SNMPv2c for traps and ingest.
In SNMPv2c, Community string is used to verify the authenticity of the trap message issued by the SNMP agent (devices such as routers, switches, servers, and so on).
Authentication None
This field appears if you selected v3 in SNMP Version field.
Enable this option on if you want to set SNMPv3 authentication to None.
Protocol None
This field appears if you selected v3 in SNMP Version field.
Enable this option on if you want to set SNMPv3 protocol to None.
SNMPv3 Username
This field appears if you selected v3 in SNMP Version field.
Enter a username for trap notifications. The username you enter here is checked against the SNMPv3 users configured in Paragon Insights.
If there is a match, the trap message is further processed else, the message is dropped.
Context Engine ID
This field appears if you selected v3 in SNMP Version field.
Enter the Engine ID of the device (SNMP agent) that sends the trap notification.
For inform notifications, the Engine ID must be set to that of Paragon Insights.
SNMPv3 Authentication Protocol
This field appears if you selected v3 in SNMP Version field and disabled Authentication None.
Select an authentication protocol from the drop-down menu.
SNMP authentication protocol hashes the SNMP username with the passphrase you enter. The hashed output is sent along with the trap notification message. Paragon Insights again hashes the username with the passphrase you entered for authentication. If the output matches, the trap notification is further processed.
SNMPv3 Authentication Passphrase
This field appears if you selected v3 in SNMP Version field and disabled Privacy None.
Enter a passphrase for SNMPv3 authentication.
SNMPv3 Privacy Protocol
Select a privacy protocol from the drop-down menu.
Privacy algorithm encrypts the trap notification message with the protocol passphrase so that the message cannot be read by an unauthorized application in the network.
SNMPv3 Privacy Passphrase
This field appears if you selected v3 in SNMP Version field and disabled Privacy None.
Enter a passphrase to encrypt the trap notification.
Source IP Address
This field appears if you selected v3 in SNMP Version field.
Enter the source IP address of the device.
If you use NAT or an SNMP Proxy, the Context Engine ID cannot be used to identify the device that send trap notifications. In such cases, the source IP address of the device is used to verify the source of trap notifications.
Authentication (Required either here or at Device Group level)
Password
Username Authentication username.
Password Authentication password.
SSL
Server Common Name Server name protected by the SSL certificate.
CA Profile* Choose the applicable CA profile(s) from the drop-down list.
Local Certificate* Choose the applicable local certificate profile(s) from the drop-down list.
SSH
SSH Key Profile* Choose the applicable SSH key profile(s) from the drop-down list.
Username Authentication username.
Outbound SSH
Reset
The reset option is set by default. If you disabled outbound SSH for this device, you can enable it back by selecting Reset in the dropdown menu.
Disable
You can disable outbound SSH connections for a device by selecting Disable from the dropdown menu.
*To edit or view details about saved security profiles, go to the Security page under the Settings menu in the left-navigation bar.
- Click Save to save the configuration or click Save and Deploy to save and deploy the configuration. For information on how to use the Devices table, see Monitor Device and Network Health.
Editing a Device
To edit a device:
- Click the Configuration > Device option in the left-nav bar.
- Click anywhere on the line that contains the device name
in the table under DEVICES.
You can search and filter the device names in the table.
- Click the Pencil (Edit Device) icon.
- Modify the attributes, as needed.
See Adding a Device for a description of each attribute.
- Click Save to save the configuration or click Save and Deploy to save and deploy the configuration. For information on how to use the Devices table, see Monitor Device and Network Health.
- (Optional) A device can be deleted by clicking the Trash Can (Delete Device) icon with the device selected.
Adding a Device Group
To add a device group:
- Click the Configuration > Device Group option in the left-nav bar.
- Click the add group button (+).
The Add Device Group page appears.
- Configure the device group with the details described in Table 1.
- Do one of the
following:
Click Save—Paragon Insights saves the configuration but does not initiate operations based on the saved configuration.
You can use this option to save make multiple changes in Paragon Insights configurations and commit the changes in bulk or to roll back the changes. See Commit or Roll Back Configuration Changes in Paragon Insights for more information.
Click Save & Deploy—Paragon Insights saves and deploys the configuration.
The configuration changes are applied to the IFA ingest service in Paragon Insights.
Table 1: Fields in Device Group Configuration Attributes
Description
Name
Name of the device group. (Required)
Description
Description for the device group.
Devices
Add devices to the device group from the drop-down list. (Required)
Starting in Paragon Insights Release 4.0.0, you can add more than 50 devices per device group. However, the actual scale of the number of devices you can add depends on the available system resources.
For example, consider that you want to create a device group of 120 devices. In releases earlier than release 4.0.0, it is recommended that you create three device groups of 50, 50, and 20 devices respectively. With Paragon Insights Release 4.0.0, you just create one device group.
Native Ports
(Native GPB sensors only) List the port numbers on which the Junos Telemetry Interface (JTI) native protocol buffers connections are established.
Flow Ports
(NetFlow sensors only) List the port numbers on which the NetFlow data is received by Paragon Insights. The port numbers must be unique across the entire Paragon Insights installation.
Syslog Ports
Specify the UDP port(s) on which syslog messages are received by Paragon Insights.
Retention Policy
Select a retention policy from the drop-down list for time series data used by root cause anaylsis (RCA). By default, the retention policy is 7 days.
Disable Trigger Action Scheduler (for a particular device group)
By default, this field is marked False because the option to add a UDA scheduler in Trigger Action page is enabled.
You can set this field to True if you want to disable UDA scheduler settings in Trigger Action page.
Reports
In the Reports field, select one or more health report profile names from the drop-down list to generate reports fo the device group. Reports include alarm statistics, device health data, as well as device-specific information (such as hardware and software specifications).
To edit or view details about saved health report profiles, go to the System page under the Settings menu in the left-nav bar. The report profiles are listed under Report Settings.
For more information, see Alerts and Notifications.
SNMP
SNMP Port Number
Port number required for SNMP. The port number is set to the standard value of 161.
SNMP Version
Select either v2c or v3 in the drop-down menu.
If you select v2c, the SNMP Community name field appears. The string used in v2c authentication is set to public by default. It is recommended that users change the community string.
If you select v3, you are given an option to set username, authentication and privacy methods, and authentication and privacy secrets.
Notification Ports
Enter notification ports separated by comma.
Paragon Insights listens on these notification ports for trap notification messages.
SNMP Community
This field appears if you selected v2c in SNMP Version field.
Enter an SNMP Community string if you configure SNMPv2c for traps and ingest.
In SNMPv2c, Community string is used to verify the authenticity of the trap message issued by the SNMP agent.
Authentication None
This field appears if you selected v3 in SNMP Version field.
Enable this option on if you want to set SNMPv3 authentication to None.
Protocol None
This field appears if you selected v3 in SNMP Version field.
Enable this option on if you want to set SNMPv3 protocol to None.
SNMPv3 Username
This field appears if you selected v3 in SNMP Version field.
Enter a username for trap notifications. The username you enter here is checked against the SNMPv3 users configured in Paragon Insights.
If there is a match, the trap message is further processed else, the message is dropped.
SNMPv3 Authentication Protocol
This field appears if you selected v3 in SNMP Version field and disabled Authentication None.
Select an authentication protocol from the drop-down menu.
SNMP authentication protocol hashes the SNMP username with the passphrase you enter. The hashed output is sent along with the trap notification message. Paragon Insights again hashes the username with the passphrase you entered for authentication. If the output matches, the trap notification is further processed.
SNMPv3 Authentication Passphrase
This field appears if you selected v3 in SNMP Version field and disabled Privacy None.
Enter a passphrase for SNMPv3 authentication.
SNMPv3 Privacy Protocol
Select a privacy protocol from the drop-down menu.
Privacy algorithm encrypts the trap notification message with the protocol passphrase so that the message cannot be read by an unauthorized application in the network.
SNMPv3 Privacy Passphrase
This field appears if you selected v3 in SNMP Version field and disabled Privacy None.
Enter a passphrase to encrypt the trap notification.
Summarization
To improve the performance and disk space utilization of the Paragon Insights time series database, you can configure data summarization methods to summarize the raw data collected by Paragon Insights. Use these fields to configure data summarization:
Time Span The time span (in minutes) for which you want to group the data points for data summarization.
Summarization Profiles Choose the data summarization profiles from the drop-down list for which you want to apply to the ingest data. To edit or view details about saved data summarization profiles, go to the Data Summarization Profiles page under the Settings menu in the left-nav bar.
For more information, see Configure Data Summarization.
Ingest Frequency
Select existing Ingest Frequency Profiles to override rule or sensor frequency settings.
Authentication(Required here or at Device level)
Password
Username Authentication user name.
Password Authentication password.
SSL
Server Common Name Server name protected by the SSL certificate.
CA Profile* Choose the applicable CA profile(s) from the drop-down list.
Local Certificate* Choose the applicable local certificate profile(s) from the drop-down list.
SSH
SSH Key Profile* Choose the applicable SSH key profile(s) from the drop-down list.
Username Authentication username.
Notifications
You can use the Alarm Manager feature to organize, track, and manage KPI event alarm notifications received from Paragon Insights devices.
To receive Paragon Insights alarm notifications for KPI events that have occurred on your devices, you must first configure the notification delivery method for each KPI event severity level (Major, Minor, and Normal). Select the delivery method from the drop-down lists.
To edit or view details about saved delivery method profiles, go to the System page under the Settings menu in the left-nav bar. The delivery method profiles are listed under Notification Settings.
For more information, see Alerts and Notifications.
Logging Configuration
You can collect different severity levels of logs for the running Paragon Insights services of a device group. Paragon Insights Release 4.0.0 supports collecting log data for SNMP notification.
Use these fields to configure which log levels to collect:
Global Log Level From the drop-down list, select the level of the log messages that you want to collect for every running Paragon Insights service for the device group. The level is set to error by default.
Log Level for specific services Select the log level from the drop-down list for any specific service that you want to configure differently from the Global Log Level setting. The log level that you select for a specific service takes precedence over the Global Log Level setting.
For more information, see Logs for Paragon Insights Services.
Publish
You can configure Paragon Insights to publish sensor and field data for a specific device group:
Destinations Select the publishing profiles that define the notification type requirements (such as authentication parameters) for publishing the data.
To edit or view details about saved publishing profiles, go to the System page under the Settings menu in the left-nav bar. The publishing profiles are listed under Notification Settings.
Field Select the Paragon Insights rule topic and rule name pairs that contain the field data you want to publish.
Sensor (Device group only) Select the sensor paths or YAML tables that contain the sensor data you want to publish. No sensor data is published by default.
Outbound SSH
Ports
Enter one or more port numbers for outbound SSH connections for this device group.
IFA Deploy Nodes
Enter IP address of the node where the IFA ingest must be deployed in Paragon Insights.
IFA Ports
Enter the UDP port number on which Paragon Insights receives IFA sensor data.
Range: 1 to 65,535.
Root Cause Analysis
RCA Support
RCA is enabled by default. Disable RCA if you do not want the device group to be a part of root cause analysis.
Exclude Resources
Exclude Resources field allows you to select device resources that must be excluded from resource and dependency formation.
Editing a Device Group
To edit a device group:
Click the Configuration > Device Group option in the left-nav bar.
Click on the device group name under DEVICE GROUPS.
Click on the Pencil (Edit Device Group) icon.
Modify the attributes, as needed.
See Adding a Device Group for a description of each attribute.
Click Save to save the configuration or click Save and Deploy to save and deploy the configuration. For information on how to use the device group cards, see Monitor Device and Network Health.
(Optional) A device group can be deleted by clicking the Trash Can (Delete Device Group) icon with the device group selected.
Configuring a Retention Policy for the Time Series Database
To configure a retention policy for the time series data used for root cause analysis (RCA):
- Click the Settings > System option in the left-nav bar.
- Select Retention Policy Settings.
- Click the + Retention Policy button.
- Enter the necessary values in the text boxes for the retention
policy.
The following table describes the attributes in the Add a Retention Policy window:
Attributes
Description
Name
Name of the retention policy.
Duration
Amount of time the root cause analysis (RCA) data is retained in the Paragon Insights RCA database. By default, data is retained for 7 days.
The data must be entered in hours or days. For example, 1 day is entered as 1d or 24h.
- Click Save to save the configuration or click Save and Deploy to save and deploy the configuration.
You can now apply the retention policy to a device group. For information on how to apply a retention policy to a device group, see Adding a Device Group.
Adding a Network Group
To add a network group:
- Click the Configuration > Network option in the left-nav bar.
- Click the + (Add Network) button.
- Enter the necessary values in the text boxes and select
the appropriate options for the network group.
The following table describes the attributes in the Add a Network Group window:
Attributes
Description
Name
Name of the network group. (Required)
Description
Description for the network group.
Reports
In the Reports field, select one or more health report profile names from the drop-down list to generate reports fo the network group. Reports include alarm statistics, device health data, as well as device-specific information (such as hardware and software specifications).
To edit or view details about saved health report profiles, go to the System page under the Settings menu in the left-nav bar. The report profiles are listed under Report Settings.
For more information, see Alerts and Notifications.
Disable Trigger Action Scheduler (for a particular network group)
By default, this field is marked False because the option to add a UDA scheduler in Trigger Action page is enabled.
You can set this field to True if you want to disable UDA scheduler settings in Trigger Action page.
Notifications
You can use the Alarm Manager feature to organize, track, and manage KPI alarm notifications received from Paragon Insights devices.
To receive Paragon Insights alarm notifications for KPI events that have occurred on your devices, you must first configure the notification delivery method for each KPI event severity level (Major, Minor, and Normal). Select the delivery method from the drop-down lists.
To edit or view details about saved delivery method profiles, go to the System page under the Settings menu in the left-nav bar. The delivery method profiles are listed under Notification Settings.
For more information, see Alerts and Notifications.
Ingest Frequency
Select existing Ingest Frequency Profiles to override rule or sensor frequency settings.
Logging Configuration
You can collect different severity levels of logs for the running Paragon Insights services of a network group. Paragon Insights Release 4.0.0 supports collecting log data for SNMP notification.
Use these fields to configure which log levels to collect:
Global Log Level From the drop-down list, select the level of the log messages that you want to collect for every running Paragon Insights service for the network group. The level is set to error by default.
Log Level for specific services Select the log level from the drop-down list for any specific service that you want to configure differently from the Global Log Level setting. The log level that you select for a specific service takes precedence over the Global Log Level setting.
For more information, see Logs for Paragon Insights Services.
Publish
You can configure Paragon Insights to publish Paragon Insights sensor and field data for a specific network group:
Destinations Select the publishing profiles that define the notification type requirements (such as authentication parameters) for publishing the data.
To edit or view details about saved publishing profiles, go to the System page under the Settings menu in the left-nav bar. The publishing profiles are listed under Notification Settings.
Field Select the Paragon Insights rule topic and rule name pairs that contain the field data you want to publish.
Root Cause Analysis
RCA Support
RCA is enabled by default. Disable RCA if you do not want the network group to be a part of root cause analysis.
Exclude Resources
Exclude Resources field allows you to select network resources that must be excluded from resource and dependency formation.
- Click Save to save the configuration or click Save and Deploy to save and deploy the configuration. For information on how to use the network, see Monitor Device and Network Health.
Editing a Network Group
To edit a network group:
- Click the Configuration > Network option in the left-nav bar.
- Click anywhere on the line that contains the group name in the table under NETWORK LIST.
- Click on the Edit Network (Pencil) icon.
- Modify the attributes, as needed.
See Adding a Network Group for a description of each attribute.
- Click Save to save the configuration or click Save and Deploy to save and deploy the configuration. For information on how to use the network group cards, see Monitor Device and Network Health.
- (Optional) A network can be deleted by clicking the Delete Network (Trash Can) icon.
Related Documentation
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.