H3C Technologies H3C SecBlade LB Cards - Manual (Page 131)

123
Configuring the collaboration function
Collaboration is implemented by associating a reaction entry of an NQA operation a track entry. The
reaction entry monitors the NQA operation. If the number of operation failures reaches the specified
threshold, the configured action is triggered.
To configure the collaboration function:
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. Specify an NQA operation
type and enter its view.
type { dhcp | dlsw | dns | ftp |
http | icmp-echo | snmp | tcp |
udp-echo }
The collaboration function is not
available for the UDP jitter and
voice operations.
4. Configure a reaction entry.
reaction item-number
checked-element probe-fail
threshold-type consecutive
consecutive-occurrences
action-type trigger-only
Not configured by default.
You cannot modify the content of
an existing reaction entry.
5. Exit to system view. quit N/A
6. Associate track with NQA. See "Configuring Track." N/A
7. Associate track with an
application module.
See"Configuring track." 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 may be triggered:
{
none—NQA displays results only on the terminal screen. It does not send traps to the NMS.