H3C Technologies H3C S6300 Series Switches - Manual (Page 143)

130
• 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.
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, 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 procedure
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.
To configure threshold monitoring:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an NQA
operation and
enter NQA
operation view.
nqa entry admin-name operation-tag
By default, no NQA operation
is created.
3. Enter NQA
operation view. type { dhcp | dlsw | dns | ftp | http | icmp-echo
| snmp | tcp | udp-echo | udp-jitter | voice } Path jitter does not support the
threshold monitoring function.
4. Enable sending
traps to the NMS
when specific
conditions are met.
reaction trap { probe-failure
consecutive-probe-failures | test-complete |
test-failure cumulate-probe-failures }
By default, no traps are sent to
the NMS.
The UDP jitter and voice
operations only support the
test-complete keyword.