Help Docs

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 if 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.

The following steps will walk you through creating, editing, and deleting a Threshold and Availability Profile for a network device:

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.

  1. Click Admin > Configuration Profiles > Threshold and Availability.
  2. Click Add Threshold Profile in the Threshold and Availability screen, and in the drop-down, select Threshold Profile.
  3. 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.
  4. Mark the device as Trouble when an interface is Down or in a Trouble state: Toggle to Yes to receive an alert when any one of the interfaces in a device is Down or in a Trouble state.
  5. Alert when an individual switch in a switch stack is Down: Toggle to Yes to receive an alert when the stack switch is down.
  6. Alert when a hardware sensor in a switch stack is Down: Toggle to Yes to receive an alert when a stack sensor is down.
  7. 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.
  8. Click Save

How it works:
Poll counts are the default strategy to validate threshold breaches. You can validate 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.

Note

To make sure the condition applied in the Time duration (in minutes) strategy or the Average time (in minutes) strategy for threshold breach detection works as intended, you must ensure that you specify a time duration that is at least twice the applied check frequency for that monitor.

Note

Threshold profiles can also be configured for individual interfaces. Learn more about configuring thresholds for network interfaces and performance counters.

Edit a Threshold and Availability Profile for a network device

  1. Click the profile that you want to edit.
  2. Edit the parameters that need to be changed in the Edit Threshold and Availability window.
  3. Click Save.

Delete a Threshold and Availability Profile for a network device

  1. Click the profile in the Threshold and Availability screen that needs to be deleted.
  2. This will bring you to the Edit Threshold and Availability window.
  3. Click Delete.

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.


We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.


Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!