H3C Technologies H3C MSR 50 - Manual (Page 135)

Step Command Remarks
361. Exit to system view. quit N/A
See High Availability
Configuration Guide.
362. Associate Track with NQA. N/A
363. Associate Track with an
application module.
See High Availability
Configuration Guide.
N/A
Configuring threshold monitoring
Introduction
1. Threshold types
An NQA operation supports the following threshold types:
{
average—If the average value for the monitored performance metric either exceeds the upper
threshold or goes below the lower threshold, a threshold violation occurs.
{
accumulate—If the total number of times that the monitored performance metric is out of the
specified value range reaches or exceeds the specified threshold, a threshold violation occurs.
{
consecutive—If the number of consecutive times that the monitored performance metric is out of
the specified value range reaches or exceeds the specified threshold, a threshold violation
occurs.
Threshold violations for the average or accumulate threshold type are determined on a per NQA
operation basis, and threshold violations for the consecutive type are determined from the time the
NQA operation starts.
2. Triggered actions
The following actions might be triggered:
{
none—NQA displays results only on the terminal screen. It does not send traps to the NMS.
{
trap-only—NQA displays results on the terminal screen, and meanwhile it sends traps to the
NMS.
The DNS operation does not support the action of sending trap messages.
3. Reaction entry
In a reaction entry, a monitored element, a threshold type, and an action to be triggered are
configured to implement threshold monitoring.
The state of a reaction entry can be invalid, over-threshold, or below-threshold.
{
Before an NQA operation starts, the reaction entry is in invalid state.
{
If the threshold is violated, the state of the entry is set to over-threshold. Otherwise, the state of
the entry is set to below-threshold.
If the action to be triggered is configured as trap-only for a reaction entry, when the state of the
entry changes, a trap message is generated and sent to the NMS.
Configuration prerequisites
Before you configure threshold monitoring, configure the destination address of the trap messages by
using the snmp-agent target-host command. For more information about the command, see Network
Management and Monitoring Command Reference.
122