Configuring Threshold Monitoring - H3C SR6600-X Configuration Manual

Step
2. Create an NQA operation
and enter NQA operation
view.
3. Specify an NQA operation
type and enter its view.
4. Configure a reaction entry.
5. Exit to system view.
6. Associate Track with NQA.
7. Associate Track with an
application module.

Configuring threshold monitoring

This function allows you to monitor the NQA operation running status.
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. The threshold violations for the consecutive type are determined from the time the NQA
operation starts.
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.
•
• trigger-only—NQA displays results on the terminal screen, and meanwhile triggers other modules
for collaboration.
The DNS operation does not support the action of sending trap messages.
Reaction entry
In a reaction entry, configure a monitored element, a threshold type, and an action to be triggered to
implement threshold monitoring.
Command
nqa entry admin-name
operation-tag
type { dhcp | dlsw | dns | ftp |
http | icmp-echo | snmp | tcp |
udp-echo }
reaction item-number
checked-element probe-fail
threshold-type consecutive
consecutive-occurrences
action-type trigger-only
quit
See High Availability
Configuration Guide.
See High Availability
Configuration Guide.
27
Remarks
By default, no NQA operation is
created.
The collaboration function is not
available for the path jitter, UDP
tracert, UDP jitter, and voice
operations.
By default, no reaction entry is
configured.
You cannot modify the content of
an existing reaction entry.
N/A
N/A
N/A