HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
120
Configuring threshold monitoring
Configuration prerequisites
Before you configure threshold monitoring, complete the following tasks:
• Configure the destination address of the trap message by using the snmp-agent target-host
command. For more information about the snmp-agent target-host command, see Network
Management and Monitoring Command Reference .
• Create an NQA test group and configure the related parameters.
Configuration guidelines
Follow these guidelines when you configure threshold monitoring:
• NQA DNS tests do not support the action of sending trap messages. The action to be triggered in
DNS tests can only be the default one, none.
• Only the test-complete keyword is supported for the reaction trap command in a voice test.
Configuration procedure
To configure threshold monitoring:
Step Command Remarks
1. Enter system
view. system-view
N/A
2. Enter NQA test
group view. nqa
entry admin-name operation-tag N/A
3. Enter test type
view of the test
group. type
{ dhcp | dlsw | dns | ftp | http | icmp-echo | snmp | tcp
| udp-echo | udp-jitter | voice } N/A
121
Step Command Remarks
4. Configure
threshold
monitoring.
• Enable sending traps to the netw ork management server
under specified conditions:
reaction trap { probe-failure consecutive-probe-failures |
test-complete | test-failure cumulate-probe-failures }
• Configure a reaction entry for monitoring the probe duration
of a test (not supported in UDP jitter and voice tests):
reaction item-number checked-element probe-duration
threshold-type { accumulate accumulate-occurrences |
average | consecutive consecutive-occurrences }
threshold-value upper-threshold lower-threshold
[ action-type { none | trap-only } ]
• Configure a reaction entry for monitoring the probe failure
times (not supported in UDP jitter and voice tests):
reaction item-number checked-element probe-fail
threshold-type { accumulate accumulate-occurrences |
consecutive consecutive-occurrences } [ action-type { none |
trap-only } ]
• Configure a reaction entry for monitoring packet round-trip
time (only supported in UDP jitter and voice tests):
reaction item-number checked-element rtt threshold-type
{ accumulate accumulate-occurrences | average }
threshold-value upper-threshold lower-threshold
[ action-type { none | trap-only } ]
• Configure a reaction entry for monitoring the packet loss in
each test (only supported in UDP jitter and voice tests):
reaction item-number checked-element packet-loss
threshold-type accumulate accumulate-occurrences
[ action-type { none | trap-only } ]
• Configure a reaction entry for monitoring one-way delay
jitter (only supported in UDP jitter and voice tests):
reaction item-number checked-element { jitter-ds | jitter-sd }
threshold-type { accumulate accumulate-occurrences |
average } threshold-value upper- threshold lower- threshold
[ action-type { none | trap-only } ]
• Configure a reaction entry for monitoring the one-way delay
(only supported in UDP jitter and voice tests):
reaction item-number checked-element { owd-ds | owd-sd }
threshold-value upper-threshold lower-threshold
• Configure a reaction entry for monitoring the ICPIF value
(only supported in voice tests):
reaction item-number checked-element icpif threshold-value
upper- threshold lower- threshold [ action-type { none |
trap-only } ]
• Configure a reaction entry for monitoring the MOS value
(only supported in voice tests):
reaction item-number checked-element mos threshold-value
upper- threshold lower- threshold [ action-type { none |
trap-only } ] Configure to send
traps.
No traps are sent
to the network
management
server by default.
122
Configuring the NQA statistics collection function
NQA groups tests completed in a time period for a test group, and calculates the test result statistics. The
statistics form a statistics group. To view information about the statistics groups, use the display nqa
statistics command. To set the interval for collecting statistics, use the statistics interval command.
When the number of statistics groups kept reaches the upper limit and a new statistics group is to be
saved, the oldest statistics group is deleted. To set the maximum number of statistics groups that can be
kept, use the statistics max-group command.
A statistics group is formed after the last test is co mpleted within the specified interval. Statistics groups
have an aging mechanism. A statistics group is delete d when its hold time expires. To set the hold time
of statistics groups for a test group, use the statistics hold-time command.
Follow these guidelines when you configure the NQA statistics collection function:
• The NQA statistics collection function is not supported in DHCP tests.
• If you use the frequency command to set the frequency between two consecutive tests to 0, only one
test is performed, and no statisti cs group information is collected.
To configure the NQA statistics collection function:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter NQA test group view.
nqa entry admin-name operation-tag N/A
3. Enter test type view of the test
group. type
{ dlsw | dns | ftp | http |
icmp-echo | snmp | tcp | udp-echo |
udp-jitter | voice } N/A
4. Configure the interval for
collecting the statistics of test
results. statistics interval
interval Optional.
60 minutes by default.
5.
Configure the maximum number
of statistics groups that can be
kept. statistics max-group
number Optional.
2 by default.
To disable collecting NQA
statistics, set the maximum
number to 0.
6.
Configure the hold time of
statistics groups. statistics hold-time
hold-time Optional.
120 minutes by default.
Configuring the history records saving function
The history records saving function enables the system
to save the history records of NQA tests. To view
the history records of a test group, use the display nqa history command.
The configuration task also allows you to configure the following elements:
• Lifetime of the history records —The records are removed when the lifetime is reached.
• The maximum number of history records that can be saved in a test group —If the number of history
records in a test group exceeds the maximum number, the earliest history records are removed.
To configure the history records saving function of an NQA test group:
123
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter NQA test group
view. nqa
entry admin-name
operation-tag N/A
3.
Enter NQA test type view. type
{ dhcp | dlsw | dns | ftp
| http | icmp-echo | snmp |
tcp | udp-echo | udp-jitter |
voice } N/A
4.
Enable the saving of the
history records of the
NQA test group. history-record enable
By default, history records of the NQA test
group are not saved.
5.
Set the lifetime of the
history records in an NQA
test group. history-record keep-time
keep-time
Optional.
By default, the history records in the NQA
test group are kept for 120 minutes.
6.
Configure the maximum
number of history records
that can be saved for a test
group. history-record number
number
Optional.
By default, the maximum number of records
that can be saved for a test group is 50.
Configuring optional parameters for an NQA test
group
Optional parameters for an NQA test group are valid only for tests in this test group.
Unless otherwise specified, the following optional
parameters are applicable to all test types.
To configure optional parameters for an NQA test group:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter NQA test group view. nqa
entry admin-name
operation-tag N/A
3. Enter test type view of a test
group. type
{ dhcp | dlsw | dns
| ftp | http | icmp-echo
| snmp | tcp | udp-echo
| udp-jitter | voice } N/A
4.
Configure the description for a
test group. description text
Optional.
By default, no description is available for a
test group.
124 Step Command Remarks 5. Configure the interval between two consecutive tests for a test group. frequency interval Optional. By default, the interval between two consecutive tests for a test group is 0 milliseconds. 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 does not start. 6. Configure the number of probe operations to be performed in one test. probe count times Optional. By default, one probe operation is performed in one test. Not available for voice tests, Only one probe operation can be performed in one voice test. 7. Configure the NQA probe timeout time. probe timeout timeout Optional. By default, the timeout time is 3000 milliseconds. Not available for UDP jitter tests. 8. Configure the maximum number of hops a probe packet traverses in the network. ttl value Optional. 20 by default. Not available for DHCP tests. 9. Configure the ToS field in an IP packet header in an NQA probe packet. tos value Optional. 0 by default. 10. Enable the routing table bypass function. route-option bypass-route Optional. Disabled by default. Not available for DHCP tests. Configuring a schedule for an NQA test group You can configure a schedule for an NQA test group by setting the start time and test duration for a test group. A test group performs tests between the scheduled star t time and the end time (the start time plus test duration). If the scheduled start time is ahead of the system time, the test group starts testing immediately. If both the scheduled start and end time are behind the system time, no test will start. To view the current system time, use the display clock command. Configuration prerequisites Before you configure a schedule for an NQA test group, complete the following tasks: • Configure test parameters required for the test type. • Configure the NQA server for tests that require cooperation with the NQA server.
125
Configuration guidelines
Follow these guidelines when you schedule an NQA test group:
• After an NQA test group is scheduled, you cannot enter the test group view or test type view.
• System adjustment does not affect st arted or completed test groups. It only affects test groups that
have not started.
Configuration procedure
To schedule an NQA test group:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Configure a schedule
for an NQA test
group. nqa schedule
admin-name
operation-tag start-time
{ hh:mm:ss [ yyyy/ mm/dd ]
| now } lifetime { lifetime |
forever } now
specifies the test group starts testing
immediately.
forever specifies that the tests do not stop unless
you use the undo nqa schedule command.
3. Configure the
maximum number of
tests that the NQA
client can
simultaneously
perform. nqa agent max-concurrent
number Optional.
By default, the maximum number of tests that the
NQA client can simultaneously perform is 2.
Displaying and maintaining NQA
Task Command Remarks
Display history records of NQA
test groups.
display
nqa history [ admin-name operation-tag ] [ |
{ begin | exclude | include } regular-expression ]
Available in any
view
Display the current monitoring
results of reaction entries. display nqa reaction counters
[ admin-name
operation-tag [ item-number ] ] [ | { begin | exclude |
include } regular-expression ]
Display the results of the last NQA
test. display
nqa result [ admin-name operation-tag ] [ |
{ begin | exclude | include } regular-expression ]
Display statistics of test results for
the specified or all test groups. display
nqa statistics [ admin-name operation-tag ] [ |
{ begin | exclude | include } regular-expression ]
Display NQA server status. display nqa server status
[ | { begin | exclude |
include } regular-expression ]
126 NQA configuration examples ICMP echo test configuration example Network requirements As shown in Figure 40, c onfigure NQA ICMP echo tests to test whether the NQA client (Device A) can send packets through a specific next hop to the spec ified destination (Device B) and test the round-trip time of the packets. Figure 40 Network diagram Configuration procedure Before you make the configuration, make sure the devices can reach each other. # Create an ICMP echo test group, and specify 10.2.2.2 as the destination IP address for ICMP echo requests to be sent. system-view [DeviceA] nqa entry admin test [DeviceA-nqa-admin-test] type icmp-echo [DeviceA-nqa-admin-test-icmp-echo] destination ip 10.2.2.2 # Configure 10.1.1.2 as the next hop IP address for ICMP echo requests. The ICMP echo requests are sent to Device C to Device B (the destination). [DeviceA-nqa-admin-test-icmp-echo] next-hop 10.1.1.2 # Configure the device to perform 10 probe operations per test, perform tests at an interval of 5000 milliseconds. Set the NQA probe ti meout time as 500 milliseconds. [DeviceA-nqa-admin-test-icmp-echo] probe count 10 [DeviceA-nqa-admin-test-icmp-echo] probe timeout 500 [DeviceA-nqa-admin-test-icmp-echo] frequency 5000
127
# Enable the saving of history records and configure the maximum number of history records that can be
saved for a test group.
[DeviceA-nqa-admin-test-icmp-echo] history-record enable
[DeviceA-nqa-admin-test-icmp-echo] history-record number 10
[DeviceA-nqa-admin-test-icmp-echo] quit
# Start ICMP echo tests.
[DeviceA] nqa schedule admin test start-time now lifetime forever
# Stop the ICMP echo tests after a period of time.
[DeviceA] undo nqa schedule admin test
# Display the results of the last ICMP echo test.
[DeviceA] display nqa result admin test
NQA entry (admin admin, tag test) test results:
Destination IP address: 10.2.2.2
Send operation times: 10 Receive response times: 10
Min/Max/Average round trip time: 2/5/3
Square-Sum of round trip time: 96
Last succeeded probe time: 2011-01-23 15:00:01.2
Extended results:
Packet loss in test: 0%
Failures due to timeout: 0
Failures due to disconnect: 0
Failures due to no connection: 0
Failures due to sequence error: 0
Failures due to internal error: 0
Failures due to other errors: 0
Packet(s) arrived late: 0
# Display the history of ICMP echo tests.
[DeviceA] display nqa history admin test
NQA entry (admin admin, tag test) history record(s):
Index Response Status Time
370 3 Succeeded 2011-01-23 15:00:01.2
369 3 Succeeded 2011-01-23 15:00:01.2
368 3 Succeeded 2011-01-23 15:00:01.2
367 5 Succeeded 2011-01-23 15:00:01.2
366 3 Succeeded 2011-01-23 15:00:01.2
365 3 Succeeded 2011-01-23 15:00:01.2
364 3 Succeeded 2011-01-23 15:00:01.1
363 2 Succeeded 2011-01-23 15:00:01.1
362 3 Succeeded 2011-01-23 15:00:01.1
361 2 Succeeded 2011-01-23 15:00:01.1
DHCP test configuration example
Network requirements
As shown in Figure 41, configure NQA DHCP tests to test the time required for Device A to obtain an IP
address from the DHCP server (Device B).
128
Figure 41 Network diagram
Configuration procedure
# Create a DHCP test group, and specify interfac e VLAN-interface 2 to perform NQA DHCP tests.
system-view
[DeviceA] nqa entry admin test
[DeviceA-nqa-admin-test] type dhcp
[DeviceA-nqa-admin-test-dhcp] operation interface vlan-interface 2
# Enable the saving of history records.
[DeviceA-nqa-admin-test-dhcp] history-record enable
[DeviceA-nqa-admin-test-dhcp] quit
# Start DHCP tests.
[DeviceA] nqa schedule admin test start-time now lifetime forever
# Stop DHCP tests after a period of time.
[DeviceA] undo nqa schedule admin test
# Display the result of the last DHCP test.
[DeviceA] display nqa result admin test
NQA entry (admin admin, tag test) test results:
Send operation times: 1 Receive response times: 1
Min/Max/Average round trip time: 624/624/624
Square-Sum of round trip time: 389376
Last succeeded probe time: 2011-01-22 09:56:03.2
Extended results:
Packet loss in test: 0%
Failures due to timeout: 0
Failures due to disconnect: 0
Failures due to no connection: 0
Failures due to sequence error: 0
Failures due to internal error: 0
Failures due to other errors: 0
Packet(s) arrived late: 0
# Display the history of DHCP tests.
[DeviceA] display nqa history admin test
NQA entry (admin admin, tag test) history record(s):
Index Response Status Time
1 624 Succeeded 2011-01-22 09:56:03.2
129
DNS test configuration example
Network requirements
As shown in Figure 42, c onfigure NQA DNS tests to test whether Device A can translate the domain
name host.com into an IP address through the DNS server and test the time required for resolution.
Figure 42 Network diagram
Configuration procedure
Before you make the configuration, make sure the devices can reach each other.
# Create a DNS test group.
system-view
[DeviceA] nqa entry admin test
[DeviceA-nqa-admin-test] type dns
# Specify the IP address of the DNS server 10.2.2.2 as the destination address for DNS tests, and specify
the domain name that needs to be translated as host.com.
[DeviceA-nqa-admin-test-dns] destination ip 10.2.2.2
[DeviceA-nqa-admin-test-dns] resolve-target host.com
# Enable the saving of history records.
[DeviceA-nqa-admin-test-dns] history-record enable
[DeviceA-nqa-admin-test-dns] quit
# Start DNS tests.
[DeviceA] nqa schedule admin test start-time now lifetime forever
# Stop the DNS tests after a period of time.
[DeviceA] undo nqa schedule admin test
# Display the results of the last DNS test.
[DeviceA] display nqa result admin test
NQA entry (admin admin, tag test) test results:
Destination IP address: 10.2.2.2
Send operation times: 1 Receive response times: 1
Min/Max/Average round trip time: 62/62/62
Square-Sum of round trip time: 3844
Last succeeded probe time: 2011-01-10 10:49:37.3
Extended results:
Packet loss in test: 0%
Failures due to timeout: 0
Failures due to disconnect: 0
Failures due to no connection: 0
Failures due to sequence error: 0
Failures due to internal error: 0
Failures due to other errors: 0