Device and Interface Threshold Settings
DX NetOps Spectrumincludes several device and interface alarms configured with three variables to define the alarm and reset conditions:
- Threshold SettingSpecifies the threshold setting above which an alarm condition can exist.
- Reset LevelSpecifies the reset level below which an existing threshold alarm condition is automatically cleared.DX NetOps Spectrumdoes not generate subsequent alarms for the parameter until the value falls below the reset level.
- Allowed Threshold Violation DurationSpecifies how long the parameter can be greater than the threshold setting, in seconds, beforeDX NetOps Spectrumgenerates an alarm.
You can configure device thresholds so that an alarm is generated if a given threshold is exceeded for a certain duration.
To configure device and interface threshold alarm settings, the Device Threshold attribute on the
SpectroSERVERmust be enabled. You can turn off individual device or interface thresholds by setting the threshold and reset level variables equal to zero.
Device Threshold Settings
You can configure device thresholds so that an alarm is generated if a value is exceeded for a certain duration. No further alarms are generated for a threshold violation until its monitored value falls below the reset threshold. To disable a threshold from generating alarms, set the threshold value to zero.
The device threshold settings available are ‘% CPU Utilization’ and ‘% Memory Utilization’. You can access these OneClick settings in the following ways:
- The Thresholds and Watches subview in the Information tab for the selected device.
- The Attribute Editor, Thresholds, Device Thresholds grouping.When using the Attribute Editor to set the Device Threshold attributes, the Allowed Threshold Violation Duration attribute is not available, and the default value of 300 seconds (five minutes) is used.
You can view the source that is used to calculate the CPU and memory utilization for a device in the Thresholds and Watches, Thresholds subview in the Information tab of the Component Detail panel.
Example % CPU Utilization Default Settings
This example illustrates how the default % CPU Utilization Threshold settings work together to trigger an alarm. The example is illustrated in the following graphic. The default settings for this alarm setting are as follows:
- % CPU Utilization Threshold = 85%
- % CPU Utilization Reset = 70%
- Allow Threshold Violation Duration = 300 seconds
Using the default settings, when the device’s % CPU Utilization parameter exceeds the threshold setting of 85% at time Y,
DX NetOps Spectrumbegins the 300 second Allowed Threshold Duration timer.
The % CPU Utilization does not fall below the reset value of 70% for the duration of the timer.
At time = Y+5 minutes,
DX NetOps Spectrumtriggers a % CPU Utilization alarm for the device.
DX NetOps Spectrumwill not generate another % CPU Utilization alarm until this alarm is cleared manually or automatically.
At time = Y+12 minutes, the device’s % CPU Utilization falls below the reset value of 70%.
DX NetOps Spectrumclears the % CPU Utilization alarm for the device.
Illustration: % CPU Utilization Default Settings
Interface Threshold Settings
The following interface thresholds parameters are available:
- % Utilization ThresholdDefines the level of port capacity used that triggers an alarm condition for a port.
- Packet Rate Threshold (packets/sec)Defines the number of packets per second that triggers an alarm condition for a port.
- % Error Rate ThresholdDefines the error rate on a port that triggers an alarm condition.
- % Discarded ThresholdDefines the percentage of discarded packets on a port that triggers an alarm condition.
Each of these attributes has a reset value and Allowed Threshold Violation Duration timer attribute setting. You can access these OneClick settings in the following ways:
The Thresholds and Watches subview in the Information tab for the selected device interface.
- The Attribute Editor, Thresholds, Interface Thresholds grouping.
See Threshold Attributes for information about accessing Device Threshold settings using the Attribute Editor.