Configuring Optional Parameters Common To An Nqa Test Group - 3Com MSR 50 Series Configuration Manual

3com msr 30-16: software guide
Hide thumbs Also See for MSR 50 Series:
Table of Contents

Advertisement

2028
C
109: NQA O
HAPTER
Configuring Optional
Parameters Common
to an NQA Test Group
VERVIEW
Configuration prerequisites
Before configuring trap delivery, you need to configure the destination address of
the trap message with the snmp-agent target-host command to create an NQA
test group and related parameters. For the configuration of the snmp-agent
target-host command, refer to "SNMP Configuration" on page 2085.
Configuring trap delivery
Follow these steps to configure trap delivery:
To do...
Enter system view
Enter NQA test group view
Enter test type view of the test
group
Configure to send traps to
network management server
under specified conditions
Optional parameters common to an NQA test group are valid only for tests in this
test group.
Unless otherwise specified, the following parameters are applicable to all test
types and they can be configured according to the actual conditions.
Follow these steps to configure optional parameters common to an NQA test
group:
To do...
Enter system view
Enter NQA test group view
Configure the descriptive
string for a test group
Configure the interval
between two consecutive
tests for a test group
Use the command...
system-view
nqa entry admin-name
operation-tag
type { dhcp | dlsw | ftp |
http | icmp-echo | snmp |
tcp | udp-echo | udp-jitter }
reaction trap {
probe-failure
consecutive-probe-failures |
test-complete | test-failure
cumulate-probe-failures }
Use the command...
system-view
nqa entry admin-name
operation-tag
description text
frequency interval
Remarks
-
-
-
Optional
No traps are sent to the
network management server
by default.
Remarks
-
-
Optional
By default, no descriptive
string is available for a test
group.
Optional
By default, the interval
between two consecutive
tests for a test group is 0
milliseconds, that is, only one
test is performed.
If the last test is not
completed when the interval
specified by the frequency
command is reached, a new
test is not started.

Hide quick links:

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents