Threshold and Availability for Network Device
Add a network monitor and keep track of all the performance metrics of critical network devices to help network teams visualize, monitor, optimize, and manage the network devices and interfaces.
The Threshold and Availability Profile helps the alarms engine decide whether a specific network device or resource has to be declared as down or in a trouble state. Thresholds can also be configured for child attributes like network interfaces and performance counters.
Add a Threshold and Availability Profile 
The monitor’s status changes to Trouble or Critical when the condition applied to any of the below threshold strategies is met.
- Click Admin > Configuration Profiles > Threshold and Availability.
- Click Add Threshold Profile in the Threshold and Availability screen, and in the drop-down, select Threshold Profile.
- Specify the following details for adding threshold and availability for a network device:
- Monitor Type: Select Network Device from the drop-down list
- Display Name: Provide a label for identification purposes.
- Mark the device as Trouble when an interface is Down/Trouble: Toggle to Yes to receive an alert when any one of the interfaces in a device is Down or in a Trouble state.
- Alert when an individual switch in a switch stack is Down: Toggle to Yes to receive an alert when the stack switch is down.
- Alert when a hardware sensor in a switch stack is Down: Toggle to Yes to receive an alert when a stack sensor is down.
- Threshold Type: Select Static Threshold to set thresholds manually and Zia based Threshold to track abnormal spikes using anomaly detection and to set a dynamic threshold. From the drop-down menu, choose the desired metrics for which thresholds need to be configured. Enter a value specific to the unit in the Threshold field, set the threshold criteria (<, <=,=,>, or >=, !=) in the Condition field, select an appropriate Poll Strategy, and enter the Poll Value and the monitor state (Critical or Trouble) next to each metric. You'll receive alerts when these threshold conditions are violated.
- Device-level attributes: Response Time, Packet Loss, CPU Utilization, Memory Utilization, and System Uptime.
- Interface-level attributes: In Traffic, Out Traffic, Total Traffic, Rx Utilized (%), Errors (%), Tx Utilized (%), Discards (%), Rx Volume, Tx Volume, and Total Volume.
- Switch stack attributes: Hardware Sensor Value.
- Additional settings: For each of these threshold configurations, you can also select an Automation step and an Event reason template.
NoteYou can select configlets as an Automation step. However, the step will be executed only if the network device is also added as an NCM monitor.
- Advanced Threshold: Set complex alert conditions using logical operators across multiple attributes to accurately detect anomalies using advanced threshold settings.
- Click Save
How it works
Poll counts are the default strategy to validate threshold breaches. You can validate a threshold breach by applying multiple conditions (>, <,=,>=, <=, !=) to your specified threshold strategy. The monitor’s status changes to Trouble or Critical when the condition applied to any of the below threshold strategies is met:
- Poll Count: The monitor’s status changes to Trouble or Critical when the condition applied to the threshold value is continuously validated for the specified poll count.
- Poll Average: The monitor’s status changes to Trouble or Critical when the average of the attribute values for the number of polls configured continuously breaches the condition applied to the threshold value.
- Time duration (in minutes): When the specified condition applied to the threshold value is continuously validated for all the polls during the configured time duration, the monitor’s status changes to Trouble or Critical.
- Average time (in minutes): The monitor’s status changes to Trouble or Critical when the average of the attribute values for the average time configured continuously justifies the condition applied on the threshold value.
The multiple poll check strategy, mentioned in the poll average step, will not be applied by default. During the conditions where no strategy could be applied, the threshold breach will be validated for a single poll alone.
Edit a Threshold and Availability Profile for a network device
- Click the profile that you want to edit. Alternatively, you can navigate to Network > Network Devices > click a device. Click the hamburger icon
, then click Edit. Next, click the pencil icon
beside Threshold and Availability field in the Configuration Profiles section.
- Edit the parameters that need to be changed in the Edit Threshold and Availability window.
- Click Save.
Delete a Threshold and Availability Profile for a network device
- Click the profile in the Threshold and Availability screen that needs to be deleted.
- This will bring you to the Edit Threshold and Availability window.
- Click Delete.