HP 5820X Switch, 5800 Switch Configuration Manual

HP 5820X & 5800 Switch Series Network Management and Monitoring

Configuration Guide

Abstract

This document describes the software features for the HP 5820X & 5800 Series products and guides you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.

This documentation is intended for network planners, field technical support and servicing engineers, and network administrators working with the HP 5820X & 5800 Series products.

Part number: 5998-1636 Software version: Release 1211 Document version: 6W101-20121123

Legal and notice information

No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice.

HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

System maintenance and debugging ························································································································· 1

Configuring ping·······························································································································································1

Configuring ping example ······································································································································1

Tracert ················································································································································································3

Configuring tracert ···················································································································································4

System debugging ····························································································································································5

Configuring system debugging·······························································································································6

Configuring ping and tracert example ···························································································································7

Configuring NQA························································································································································ 9

NQA benefits····························································································································································9 Basic NQA concepts ············································································································································ 11

NQA probe operation procedure ······················································································································· 12 NQA configuration task list ·········································································································································· 12 Configuring the NQA server ········································································································································ 13 Enabling the NQA client··············································································································································· 14 Creating an NQA test group········································································································································ 14 Configuring an NQA test group ·································································································································· 14

Configuring ICMP echo tests································································································································ 14

Configuring DHCP tests ········································································································································ 15

Configuring DNS tests ·········································································································································· 16

Configuring FTP tests············································································································································· 17

Configuring HTTP tests·········································································································································· 18

Configuring UDP jitter tests ·································································································································· 19

Configuring SNMP tests ······································································································································· 21

Configuring TCP tests············································································································································ 22

Configuring UDP echo tests·································································································································· 23

Configuring voice tests ········································································································································· 24

Configuring DLSw tests ········································································································································· 26 Configuring the collaboration function ························································································································ 27 Configuring threshold monitoring ································································································································ 28 Configuring the NQA statistics collection function····································································································· 29 Configuring the history records saving function ········································································································· 30 Configuring optional parameters for an NQA test group························································································· 31 Scheduling an NQA test group···································································································································· 32 Displaying and maintaining NQA ······························································································································· 33 Configuring NQA examples········································································································································· 33

Configuring ICMP echo test example ················································································································· 33

Configuring DHCP test example·························································································································· 35

Configuring DNS test example ···························································································································· 36

Configuring FTP test example ······························································································································ 37

iii

Configuring HTTP test example···························································································································· 38

Configuring UDP jitter test example ···················································································································· 40

Configuring SNMP test example ························································································································· 43

Configuring TCP test example······························································································································ 44

Configuring UDP echo test example ··················································································································· 45

Configuring voice test example ··························································································································· 47

Configuring DLSw test example··························································································································· 50

Configuring NQA collaboration example·········································································································· 51

Configuring NTP ························································································································································54

NTP applications ··················································································································································· 54

NTP advantages ···················································································································································· 54

How NTP works····················································································································································· 55

NTP message format············································································································································· 56

NTP operation modes ··········································································································································· 57

Multiple instances of NTP····································································································································· 59 NTP configuration task list············································································································································· 60 Configuring the operation modes of NTP ··················································································································· 60

Configuring NTP client/server mode ·················································································································· 60

Configuring the NTP symmetric peers mode ······································································································ 61

Configuring NTP broadcast mode ······················································································································ 62

Configuring NTP multicast mode ························································································································· 63 Configuring optional parameters of NTP ···················································································································· 63

Specifying the source interface for NTP messages···························································································· 63

Disabling an interface from receiving NTP messages······················································································· 64

Configuring the maximum number of dynamic sessions allowed···································································· 64 Configuring access-control rights ································································································································· 65

Configuration prerequisites ·································································································································· 65

Configuring NTP client/server mode example ·································································································· 68

Configuring the NTP symmetric mode example································································································· 69

Configuring NTP broadcast mode example······································································································· 71

Configuring NTP multicast mode example ········································································································· 72

Configuring NTP client/server mode with authentication example································································· 75

Configuring NTP broadcast mode with authentication example ····································································· 76

Configuring MPLS VPN time synchronization in client/server mode example··············································· 78

Configuring MPLS VPN time synchronization in symmetric peers mode example ········································ 80

Configuring IPC··························································································································································82

Enabling IPC performance statistics ····························································································································· 83 Displaying and maintaining IPC··································································································································· 84

Configuring PoE·························································································································································85

Protocol specification ············································································································································ 86 PoE configuration task list ············································································································································· 86 Enabling PoE ·································································································································································· 87

Enabling PoE for a PoE interface························································································································· 87 Detecting PDs·································································································································································· 88

Enabling the PSE to detect nonstandard PDs ····································································································· 88

Configuring a PD disconnection detection mode ······························································································ 88 Configuring the PoE power··········································································································································· 89

Configuring the maximum PoE interface power ································································································ 89 Configuring PoE power management·························································································································· 89

Configuring PoE interface power management ································································································· 89 Configuring the PoE monitoring function····················································································································· 90

Configuring PSE power monitoring····················································································································· 90

Monitoring PD························································································································································ 90 Configuring PoE interface through PoE profile ··········································································································· 91

Configuring PoE profile ········································································································································ 91

Applying PoE profile ············································································································································· 91 Upgrading PSE processing software in service ·········································································································· 92 Displaying and maintaining PoE ·································································································································· 93 Configuring PoE example ············································································································································· 93 Troubleshooting PoE ······················································································································································ 94

Configuring SNMP·····················································································································································96

SNMP mechanism ················································································································································· 96

SNMP protocol version········································································································································· 96

MIB overview························································································································································· 97 Configuring SNMP ························································································································································ 97 Configuring network management-specific interface index ····················································································100

Switching the format of an NM-specific ifindex·······························································································100 Configuring SNMP logging ········································································································································101

Enabling SNMP logging·····································································································································101 Configuring SNMP trap ··············································································································································102

Enabling the trap function ··································································································································102

Configuring trap parameters······························································································································103 Displaying and maintaining SNMP ···························································································································104 Configuring SNMPv1/SNMPv2c example ···············································································································105 Configuring SNMPv3 example ··································································································································106 Configuring SNMP logging example ························································································································107

Configuring RMON ················································································································································ 109

Working mechanism···········································································································································109

RMON groups·····················································································································································110 Configuring the RMON statistics function ·················································································································111

Configuring the RMON Ethernet statistics function·························································································· 113

Configuring the RMON history statistics function ····························································································113

Configuring the RMON alarm function ·····················································································································114

Configuration procedure ····································································································································114 Displaying and maintaining RMON ··························································································································115 Configuring Ethernet statistics group example·········································································································· 116 Configuring history group example ···························································································································117 Configuring alarm group example ····························································································································119

Configuring CWMP················································································································································ 121

CWMP network framework ·······························································································································121 CWMP basic functions ················································································································································122

Automatic configuration file deployment ··········································································································122

CPE system file management ·····························································································································122

CPE status and performance monitoring···········································································································122 CWMP mechanism ······················································································································································123

Auto-connection between the ACS and a CPE ································································································123

Configuration parameter deployment ···············································································································124

RPC methods························································································································································124

Active and standby ACS switchover ·················································································································125 CWMP configuration tasks ·········································································································································126

Configuring the DHCP server·····························································································································126

Configuring the DNS server·······························································································································127

Configuring the ACS server ······························································································································· 127

Configuring CPEs ················································································································································ 127 Enabling CWMP ··························································································································································128 Configuring the ACS server ········································································································································128

Configuring the ACS URL ···································································································································128

Configuring the ACS username and password ·······························································································128 Configuring CPE attributes··········································································································································129

Configuring the CPE username and password ································································································129

Configuring the CWMP connection interface ··································································································130

Sending Inform messages··································································································································· 130

Configuring the maximum number of attempts made to retry a connection················································· 131

Configuring the close-wait timer of the CPE ·····································································································131 Displaying and maintaining CWMP··························································································································132 Configuring CWMP example ·····································································································································132

Network requirements·········································································································································132

Configuring cluster management··························································································································· 141

Roles in a cluster··················································································································································141

How a cluster works············································································································································142 Cluster configuration task list ······································································································································145 Configuring the management device·························································································································147

Enabling NDP globally and for specific ports··································································································147

Configuring NDP parameters ····························································································································147

Enabling NTDP globally and for specific ports································································································148

Configuring NTDP parameters···························································································································148

Manually collecting topology information ········································································································149

Enabling the cluster function ······························································································································149

Establishing a cluster··········································································································································· 149

Enabling management VLAN auto-negotiation································································································150

Configuring communication between the management device and the member devices within a cluster151

Configuring cluster management protocol packets ·························································································151

Cluster member management ····························································································································152 Configuring the member devices ·······························································································································153

Enabling NDP ······················································································································································153

Enabling NTDP ····················································································································································153

Manually collecting topology information ········································································································153

Deleting a member device from a cluster ·········································································································153 Configuring access between the management device and its member devices···················································154 Adding a candidate device to a cluster ····················································································································155 Configuring advanced cluster functions ····················································································································155

Configuring topology management ··················································································································155

Configuring interaction for a cluster··················································································································156

SNMP configuration synchronization function································································································· 157

Configuring web user accounts in batches ······································································································158 Displaying and maintaining cluster management ····································································································158 Configuring cluster management example················································································································ 159

Configuring a sampler············································································································································ 163

Creating a sampler ······················································································································································163 Displaying and maintaining sampler ·························································································································163 Configuring sampler examples··································································································································· 164

Configuring port mirroring····································································································································· 165

Port mirroring types·············································································································································165

Implementing port mirroring······························································································································· 165 Configuring local port mirroring ································································································································168

Local port mirroring configuration task list ·······································································································168

Creating a local mirroring group ······················································································································ 168

Configuring mirroring ports for the local mirroring group·············································································· 169

Configuring mirroring CPUs for the local mirroring group·············································································169

Configuring the monitor port for the local mirroring group············································································170 Configuring layer 2 remote port mirroring················································································································170

Layer 2 remote port mirroring configuration task list ······················································································170

Configuring a remote source mirroring group (on the source device) ··························································172

Configuring a remote destination mirroring group (on the destination device) ··········································· 174

Using the remote probe VLAN to enable local mirroring to support multiple destination ports ················· 176 Configuring layer 3 remote port mirroring················································································································178

vii

Layer 3 remote port mirroring configuration task list ······················································································178

Configuring local mirroring groups···················································································································179

Configuring mirroring ports for a local mirroring group ················································································179

Configuring mirroring CPUs for a local mirroring group················································································180

Configuring the monitor port for a local mirroring group ··············································································180 Displaying and maintaining port mirroring···············································································································181 Configuring port mirroring examples ························································································································181

Configuring local port mirroring example········································································································181

Configuring Layer 2 remote port mirroring example ······················································································182

Configuring local port mirroring with multiple monitor ports example ·························································184

Configuring Layer 3 remote port mirroring example ······················································································186

Configuring traffic mirroring ·································································································································· 189

Mirroring traffic to an interface ·························································································································189

Mirroring traffic to the CPU································································································································190

Applying a QoS policy······································································································································· 191 Displaying and maintaining traffic mirroring············································································································ 192 Configuring traffic mirroring examples······················································································································192

Mirroring traffic to an interface example ·········································································································192

Configuring NetStream··········································································································································· 194

NetStream basic concepts ··········································································································································194

What is a flow·····················································································································································194

How NetStream works········································································································································ 194 NetStream key technologies ·······································································································································195

Flow aging ···························································································································································195

NetStream data export ·······································································································································196

NetStream export formats ··································································································································197 Introduction to NetStream sampling and filtering·····································································································198

NetStream sampling ···········································································································································198

NetStream filtering ··············································································································································198 NetStream configuration task list································································································································ 198 Enabling NetStream·····················································································································································200

Enabling NetStream on an interface·················································································································200 Configuring NetStream filtering and sampling·········································································································200

Configuring NetStream filtering························································································································· 200

Configuring NetStream sampling ······················································································································ 202 Configuring NetStream data export ··························································································································202

Configuring NetStream traditional data export ·······························································································202

Configuring NetStream aggregation data export ···························································································203 Configuring attributes of NetStream export data ·····································································································204

Configuring NetStream export format ··············································································································204

Configuring refresh rate for NetStream version 9 templates ·········································································· 206 Configuring NetStream flow aging····························································································································207

viii

Flow aging approaches······································································································································207

Configuring NetStream flow aging ···················································································································207 Displaying and maintaining NetStream ····················································································································208 Configuring NetStream examples ······························································································································ 208

Configuring NetStream traditional data export example ··············································································· 208

Configuring NetStream aggregation data export example ···········································································209

Configuring IPv6 NetStream ·································································································································· 211

IPv6 NetStream basic concepts ··································································································································211

What is an IPv6 flow ··········································································································································211

How IPv6 NetStream works ······························································································································· 211 IPv6 NetStream key technologies·······························································································································212

IPv6 NetStream data export······························································································································· 212

IPv6 NetStream export format····························································································································213 IPv6 NetStream configuration task list ······················································································································· 213 Enabling NetStream·····················································································································································214

Enabling NetStream on an interface·················································································································214 Configuring IPv6 NetStream data export··················································································································214

Configuring IPv6 NetStream traditional data export·······················································································214

Configuring IPv6 NetStream aggregation data export···················································································215 Configuring attributes of IPv6 NetStream data export·····························································································217

Configuring IPv6 NetStream export format ······································································································217

Configuring refresh rate for IPv6 NetStream version 9 templates ·································································217 Displaying and maintaining IPv6 NetStream············································································································218 Configuring IPv6 NetStream examples······················································································································218

Configuring IPv6 NetStream traditional data export example·······································································218

Configuring IPv6 NetStream aggregation data export example ···································································219

Configuring sFlow··················································································································································· 221

sFlow operation ···················································································································································221 Configuring sFlow························································································································································222

Configuring the sFlow agent and sFlow collector···························································································· 222

Configuring flow sampling·································································································································223

Configuring counter sampling ···························································································································223 Displaying and maintaining sFlow·····························································································································223 Configuring sFlow example ········································································································································224 Troubleshooting sFlow configuration ·························································································································225

The remote sFlow collector cannot receive sFlow packets ·············································································· 225

Configuring information center······························································································································ 226

System information types····································································································································227

Eight levels of system information······················································································································227

Output destinations and channels of system information················································································227

Outputting system information by source module····························································································228

Default output rules of system information ········································································································228

System information format··································································································································229

Information center configuration task list ·········································································································· 232

Outputting system information to the console ··································································································233

Outputting system information to a monitor terminal ······················································································234

Outputting system information to a log host·····································································································235

Outputting system information to the trap buffer ·····························································································236

Outputting system information to the log buffer······························································································· 236

Outputting system information to the SNMP module······················································································· 237

Outputting system information to the web interface ························································································238

Saving system information to a log file·············································································································239

Saving security logs into the security log file····································································································240

Configuring synchronous information output ···································································································243

Disabling a port from generating link up/down logging information···························································243 Displaying and maintaining information center ·······································································································244 Configuring information center examples ················································································································· 245

Outputting log information to a Unix log host ·································································································245

Outputting log information to a Linux log host·································································································246

Outputting log information to the console ········································································································ 248

Saving security logs into the security log file····································································································249

Support and other resources·································································································································· 253

Contacting HP ······························································································································································253

Subscription service ············································································································································253 Related information······················································································································································253

Documents····························································································································································253

Websites ······························································································································································253 Conventions ··································································································································································254

Index ········································································································································································ 256

System maintenance and debugging

You can use the ping command and the tracert command to verify the current network connectivity, and use the debug command to enable debugging and to diagnose system faults based on the debugging information.

Configuring ping

The ping command allows you to verify whether a device with a specified address is reachable, and to examine network connectivity.

The ping function is implemented through the ICMP using the following workflow:

1. The source device sends an ICMP echo request to the destination device.

2. The source device determines whether the destination is reachable based on whether it receives an

ICMP echo reply; if the destination is reachable, the source device determines the link quality based on the numbers of ICMP echo requests sent and replies received, determines the distance between the source and destination based on the round trip time of ping packets.

To configure the ping function:

To do… Use the command… Remarks

Check whether a specified address in an IP network is reachable.

NOTE:

• For a low-speed network, set a larger value for the timeout timer—indicated by the -t parameter in

the command—when configuring the ping command.

• Only the directly connected se

the -i argument

• For more information about the ping lsp command, see MPLS basics commands

Command Reference

m interval | -n | -p pad | -q | -r | -s packet-size | -t timeout | -tos tos | -v | -

vpn-instance vpn-instance-name ] * host

ping ipv6 [ -a source-ipv6 | -c count | -m

interval | -s packet-size | -t timeout ] * host [ -i interface-type interface-number ]

ment address can be pinged if the outgoing interface is specified with

Configuring ping example

Required.

Use either approach.

The ping command is applicable in an IPv4 network; the ping ipv6 command is applicable in an IPv6 network.

Available in any view.

in the

MPLS

Network requirements

As shown in Figure 1, check whether Device A and Device C can reach each other. If they can reach each other, get the detailed information of routes from Device A to Device C.

Figure 1 Ping network diagram

Configuration procedure

# Use the ping command to display whether Device A and Device C can reach each other.

<DeviceA> ping 1.1.2.2 PING 1.1.2.2: 56 data bytes, press CTRL_C to break Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=205 ms Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms

--- 1.1.2.2 ping statistics -- 5 packet(s) transmitted 5 packet(s) received

0.00% packet loss round-trip min/avg/max = 1/41/205 ms

# Get the detailed information of routes from Device A to Device C.

<DeviceA> ping -r 1.1.2.2 PING 1.1.2.2: 56 data bytes, press CTRL_C to break Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=53 ms Record Route:

1.1.2.1

1.1.2.2

1.1.1.2

1.1.1.1 Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms Record Route:

1.1.2.1

1.1.2.2

1.1.1.2

1.1.1.1 Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms Record Route:

1.1.2.1

1.1.2.2

1.1.1.2

1.1.1.1 Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms Record Route:

1.1.2.1

1.1.2.2

1.1.1.2

1.1.1.1 Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms Record Route:

1.1.2.1

1.1.2.2

1.1.1.2

1.1.1.1

--- 1.1.2.2 ping statistics -- 5 packet(s) transmitted 5 packet(s) received

0.00% packet loss round-trip min/avg/max = 1/11/53 ms

The principle of ping –r is as shown in Figure 1.

1. The source (Device A) sends an ICMP echo request with the RR option being empty to the

destination (Device C).

2. The intermediate device (Device B) adds the IP address (1.1.2.1) of its outbound interface to the RR

option of the ICMP echo request and forwards the packet.

3. Upon receiving the request, the destination device copies the RR option in the request and adds the

IP address (1.1.2.2) of its outbound interface to the RR option. Then the destination device sends an ICMP echo reply.

4. The intermediate device adds the IP address (1.1.1.2) of its outbound interface to the RR option in

the ICMP echo reply, and then forwards the reply.

5. Upon receiving the reply, the source device adds the IP address (1.1.1.1) of its inbound interface

to the RR option. Finally, get the detailed information of routes from Device A to Device C: 1.1.1.1 <-> {1.1.1.2; 1.1.2.1} <-> 1.1.2.2.

Tracert

By using the tracert command, you can trace the Layer 3 devices involved in delivering an IP packet from source to destination to check whether a network is available. This is useful for identification of failed nodes in the event of network failure.

Figure 2 Tracert diagram

The tracert function is implemented through ICMP, as shown in Figure 2:

1. The source (Device A) sends a packet with a TTL value of 1 to the destination (Device D). The UDP

port of the packet is a port number that will not be used by any application of the destination.

2. The first hop (Device B) (the Layer 3 device that first receives the packet) responds by sending a TTL-

expired ICMP error message to the source, with its IP address 1.1.1.2 encapsulated. In this way, the source device can get the address (1.1.1.2) of the first Layer 3 device.

3. The source device sends a packet with a TTL value of 2 to the destination device.

4. The second hop (Device C) responds with a TTL-expired ICMP error message, which gives the

source device the address (1.1.2.2) of the second Layer 3 device.

5. The process continues until the ultimate destination device is reached. No application of the

destination uses this UDP port. The destination replies a port unreachable ICMP error message with the destination IP address 1.1.3.2.

6. When the source device receives the port unreachable ICMP error message, it knows that the

packet has reached the destination, and it can get the addresses of all Layer 3 devices involved to get to the destination device (1.1.1.2, 1.1.2.2, 1.1.3.2).

Configuring tracert

Configuration prerequisites

Before you configure tracert, complete the following tasks:

• Enable sending of ICMP timeout packets on the intermediate device (the device between the source

and destination devices). If the intermediate device is an HP device, execute the ip ttl-expires enable command on the device. For more information about this command, see IP performance optimization commands in the Layer 3 - IP Services Command Reference.

• Enable sending of ICMP destination unreachable packets on the destination device. If the

destination device is an HP device, execute the ip unreachables enable command. For more information about this command, see IP performance optimization commands in the Layer 3 - IP Services Command Reference.

Tracert configuration

To configure tracert:

To do… Use the command… Remarks

1. Enter system view.

2. Display the routes from

source to destination.

NOTE:

For more information about the tracert lsp command, see MPLS basics commands

Command Reference

System debugging

The device provides various debugging functions. For the majority of protocols and features supported, the system provides debugging information to help users diagnose errors.

The following switches control the display of debugging information:

• Protocol debugging switch, which controls protocol-specific debugging information.

system-view —

timeout ] * host

tracert ipv6 [ -f first-ttl | -m max-ttl | -p port | -q packet-number | -w timeout ]

* host

Required.

Use either approach.

The tracert command is applicable in an IPv4 network; the tracert ipv6 command is applicable in an IPv6 network.

Available in any view.

in the

MPLS

• Screen output switch, which controls whether to display the debugging information on a certain

screen.

As Figure 3 illu

strates, assume the device can provide debugging for the three modules 1, 2, and 3. The debugging information can only be output on a terminal when both the protocol debugging switch and the screen output switch are turned on.

Figure 3 The relationship between the protocol and screen output switch

Configuring system debugging

Output of the debugging information may reduce system efficiency. Administrators usually use the debugging commands to diagnose network failure. After completing the debugging, disable the corresponding debugging function, or use the undo debugging all command to disable all debugging functions.

Output of debugging information depends on the configurations of the information center and the debugging commands of each protocol and functional module. Displaying the debugging information on a terminal—including console or VTY—is a common way to output debugging information. You can also output debugging information to other destinations. For more information, see Information center commands in the Network Management and Monitoring Command Reference. By default, you can output debugging information to a terminal by following these steps:

To do…

1. Enable the terminal

Use the command… Remarks

monitoring of system information.

terminal monitor

Optional.

The terminal monitoring on the console is enabled by default and that on the monitoring terminal is disabled by default.

Available in user view.

2. Enable the terminal display of

debugging information.

3. Enable debugging for a

specified module.

terminal debugging

debugging { all [ timeout time ] |

module-name [ option ] }

Required.

Disabled by default.

Available in user view.

Required.

Disabled by default.

Available in user view.

To do… Use the command… Remarks

display debugging [ interface

4. Display the enabled

debugging functions.

interface-type interface-number ] [ module-name ] [ | { begin |

exclude | include } regular- expression ]

Optional.

Available in any view.

NOTE:

To display the detailed debugging information on the terminal, configure the debugging, terminal

debugging and terminal monitor commands. For more information about the terminal debugging terminal monitor commands, see Information center commands

Monitoring Command Reference

in the

Network Management and

Configuring ping and tracert example

Network requirements

As shown in Figure 4, Device A failed to Telnet Device C. Determine whether Device A and Device C can reach each other. If they cannot reach each other, locate the failed nodes in the network.

Figure 4 Ping and tracert network diagram

and

Configuration procedure

# Use the ping command to display whether Device A and Device C can reach each other.

<DeviceA> ping 1.1.2.2 PING 1.1.2.2: 56 data bytes, press CTRL_C to break Request time out Request time out Request time out Request time out Request time out

--- 1.1.2.2 ping statistics -- 5 packet(s) transmitted 0 packet(s) received

100.00% packet loss

# Device A and Device C cannot reach each other. Use the tracert command to determine failed nodes.

<DeviceA> system-view [DeviceA] ip ttl-expires enable [DeviceA] ip unreachables enable [DeviceA] tracert 1.1.2.2 traceroute to 1.1.2.2(1.1.2.2) 30 hops max,40 bytes packet, press CTRL_C to bre ak 1 1.1.1.2 14 ms 10 ms 20 ms

2 * * * 3 * * * 4 * * * 5 <DeviceA>

The output shows that Device A and Device C cannot reach other, Device A and Device B can reach each other, and an error occurred on the connection between Device B and Device C. Use the debugging ip icmp command to enable ICMP debugging on Device A and Device C to check whether the devices send or receive the specified ICMP packets, or use the display ip routing-table command to display whether Device A and Device C can reach each other.

Configuring NQA

NQA can perform various types of tests and collect network performance and service quality parameters such as delay jitter, time for establishing a TCP connection, time for establishing an FTP connection, and file transfer rate.

With the NQA test results, you can diagnose and locate network faults, know network performance in time and take proper actions.

NQA benefits

Supporting multiple test types

Ping can only use the ICMP to test the reachability of the destination host and the round-trip time. As an enhancement to Ping, NQA provides more test types and functions.

NQA supports 11 test types: ICMP echo, DHCP, DNS, FTP, HTTP, UDP jitter, SNMP, TCP, UDP echo, voice and DLSw.

NQA enables the client to send probe packets of different test types to detect the protocol availability and response time of the peer. The test result helps you understand network performance.

Supporting the collaboration function

Collaboration is implemented by establishing reaction entries to monitor the detection results of NQA probes. If the number of consecutive probe failures reaches a limit, NQA informs the track module of the detection result, and the track module triggers other application modules to take predefined.

Figure 5 Implement collaboration

The collaboration comprises the following parts: the application modules, the track module, and the detection modules.

• A detection module monitors specific objects, such as the link status, and network performance, and

informs the track module of detection results.

• Upon the detection results, the track module changes the status of the track entry and informs the

associated application module. The track module works between the application modules and the detection modules. It hides the differences among detection modules from application modules.

• The application module takes actions when the tracked object changes its state.

The following describes how a static route is monitored through collaboration.

1. NQA monitors the reachability to 192.168.0.88.

2. When 192.168.0.88 becomes unreachable, NQA notifies it to the track module.

NOTE:

3. The track module notifies the state change to the static routing module

4. The static routing module sets the static route as invalid.

For more information about the collaboration and the track module, see

Configuration Guide

Supporting threshold monitoring

NQA supports threshold monitoring for performance parameters such as average delay jitter and packet round-trip time. The performance parameters to be monitored are monitored elements. NQA monitors threshold violations for a monitored element, and reacts to certain measurement conditions, for example, sending trap messages to the network management server. This helps network administrators understand the network service quality and network performance.

1. Monitored elements

Table 1 de

monitored.

Table 1 Monitored elements and NQA test types

Monitored elements

Probe duration

Count of probe failures

Packet round-trip time UDP jitter test and voice test

scribes the monitored elements and the NQA test types in which the elements can be

Test type supported

High Availability

Tests excluding UDP jitter test and voice test

Count of discarded packets UDP jitter test and voice test

One-way delay jitter (source-to-destination and destination-tosource)

One-way delay (source-to-destination and destination-to-source) UDP jitter test and voice test

ICPIF (see “Configuring voice tests”) Voice test

MOS (see “Configuring voice tests”) Voice test

2. Threshold types

UDP jitter test and voice test

The following threshold types are supported:

• average—Monitors the average value of monitored data in a test. If the average value in a test

exceeds the upper threshold or goes below the lower threshold, a threshold violation occurs. For example, you can monitor the average probe duration in a test.

• accumulate—Monitors total number of times the monitored data violates the threshold in a test. If the

total number of times reaches or exceeds a specified value, a threshold violation occurs.

• consecutive—Monitors the number of consecutive times the monitored data violates the threshold

since the test group starts. If the monitored data violates the threshold consecutively for a specified number of times, a threshold violation occurs.

NOTE:

The counting for the average or accumulate threshold type is performed per test, but that for the consecutive type is performed since the test group is started.

3. Triggered actions

The following actions may be triggered:

• none—NQA only records events for terminal display; it does not send trap information to the

network management server.

• trap-only—NQA records events and sends trap messages to the network management server.

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.

4. Reaction entry

In a reaction entry, a monitored element, a threshold type, and the 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 test group starts, the reaction entry is in the state of invalid. After each test or probe, threshold violations are counted according to the threshold type and range configured in the entry. If the threshold is violated consecutively or accumulatively for a specified number of times, the state of the entry is set to overthreshold; 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 network management server.

Basic NQA concepts

Test group

An NQA test group specifies test parameters including the test type, destination address, and destination port. Each test group is uniquely identified by an administrator name and operation tag. You can configure and schedule multiple NQA test groups to test different objects.

Test and probe

After the NQA test group starts, tests are performed at a specified interval. During each test, a specified number of probe operations are performed. Both the test interval and the number of probe operations per test are configurable. But only one probe operation is performed during one voice test.

Probe operations vary with NQA test types.

• During a TCP or DLSw test, one probe operation means setting up one connection.

• During a UDP jitter or a voice test, one probe operation means continuously sending a specified

number of probe packets. The number of probe packets is configurable.

• During an FTP, HTTP, DHCP or DNS test, one probe operation means uploading or downloading a

file, obtaining a web page, obtaining an IP address through DHCP, or translating a domain name to an IP address.

• During an ICMP echo or UDP echo test, one probe operation means sending an ICMP echo request

or a UDP packet.

• During an SNMP test, one probe operation means sending one SNMPv1 packet, one SNMPv2C

packet, and one SNMPv3 packet.

NQA client and server

A device with NQA test groups configured is an NQA client and the NQA client initiates NQA tests. An NQA server makes responses to probe packets destined to the specified destination address and port number.

Figure 6 Relationship between the NQA client and NQA server

Not all test types require the NQA server. Only the TCP, UDP echo, UDP jitter, or voice test requires both the NQA client and server, as shown in Figure 6.

ou can create multiple TCP or UDP listening services on the NQA server. Each listens to a specific destination address and port number. Make sure the destination IP address and port number for a listening service on the server are the same as those configured for the test group on the NQA client. Each listening service must be unique on the NQA server.

NQA probe operation procedure

An NQA probe operation involves the following steps:

1. The NQA client constructs probe packets for the specified type of NQA test, and sends them to the

peer device.

2. Upon receiving the probe packets, the peer sends back responses with timestamps.

3. The NQA client computes the network performance and service quality parameters, such as the

packet loss rate and round-trip time based on the received responses.

NQA configuration task list

To enable the NQA server:

Task Remarks

Configuring the NQA server

To perform NQA tests successfully, make the following configurations on the NQA client:

1. Enable the NQA client.

2. Create a test group and configure test parameters. The test parameters may vary with test types.

3. Schedule the NQA test group.

Required for TCP, UDP echo, UDP jitter and voice tests

To configure NQA client:

Task Remarks

Enabling the NQA client Required

Creating an NQA test group Required

Task Remarks

Configuring ICMP echo tests

Configuring DHCP tests

Configuring DNS tests

Configuring FTP tests

Configuring HTTP tests

Configuring an NQA test group

Configuring the collaboration function Optional

Configuring threshold monitoring Optional

Configuring the NQA statistics collection function Optional

Configuring the history records saving function Optional

Configuring optional parameters for an NQA test group Optional

Scheduling an NQA test group Required

Configuring UDP jitter tests

Configuring SNMP tests

Configuring TCP tests

Configuring UDP echo tests

Configuring voice tests

Configuring DLSw tests

Configuring the NQA server

Required

Use any of the approac

hes

To perform TCP, UDP echo, UDP jitter, or voice tests, configure the NQA server on the peer device. The NQA server responses to the probe packets sent from the NQA client by listening to the specified destination address and port number.

To configure the NQA server:

To do… Use the command… Remarks

1. Enter system view.

2. Enable the NQA server.

3. Configure the listening

service.

system-view —

nqa server enable

nqa server { tcp-connect | udpecho } ip-address port-number

Required.

Disabled by default.

Required.

The destination IP address and port number must be the same as those configured on the NQA client. A listening service must be unique on the NQA server.

Enabling the NQA client

Configurations on the NQA client only take effect when the NQA client is enabled.

To enable the NQA client:

To do… Use the command… Remarks

1. Enter system view.

system-view —

2. Enable the NQA client.

nqa agent enable

Creating an NQA test group

Create an NQA test group before you configure NQA tests.

To do… Use the command… Remarks

1. Enter system view.

2. Create an NQA test group

and enter the NQA test group view.

system-view —

nqa entry admin-name operation- tag

Configuring an NQA test group

Optional.

Enabled by default.

Required.

In the NQA test group view, you can specify the test type.

You can use the nqa entry command to enter the test type view of an NQA test group with test type configured.

Configuring ICMP echo tests

ICMP echo tests of an NQA test group are used to test reachability of a destination host according to the ICMP echo response information. An ICMP echo test has the same function as the ping command but provides more output information. In addition, you can specify the next hop for ICMP echo tests. ICMP echo tests are used to locate connectivity problems in a network.

To configure ICMP echo tests:

To do… Use the command… Remarks

1. Enter system view.

2. Enter NQA test group view.

3. Configure the test type as

ICMP echo and enter test type view.

4. Configure the destination

address of ICMP echo requests.

system-view —

nqa entry admin-name operation- tag

type icmp-echo Required.

destination ip ip-address

—

Required.

By default, no destination IP address is configured.

To do… Use the command… Remarks

5. Configure the size of the data

field in each ICMP echo request.

data-size size

Optional.

100 bytes by default.

6. Configure the string to be

filled in the data field of each ICMP echo request.

7. Apply ICMP echo tests to the

specified VPN.

8. Configure the source interface

for ICMP echo requests. The requests take the IP address of the source interface as their source IP address when no source IP address is specified.

9. Configure the source IP

address of ICMP echo requests.

data-fill string

vpn-instance vpn-instance-name

source interface interface-type interface-number

source ip ip-address

Optional.

By default, the string is the hexadecimal number

00010203040506070809.

Optional.

By default, ICMP echo tests apply to the public network.

Optional.

By default, no source interface is configured for probe packets.

The specified source interface must be up; otherwise, no ICMP echo requests can be sent out.

Optional

By default, no source IP address is configured.

If you configure both the source ip command and the source interface command, the source ip command takes effect.

The source IP address must be the IP address of a local interface. The local interface must be up; otherwise, no ICMP echo requests can be sent out.

10. Configure the next hop IP

address of ICMP echo requests.

11. Configure optional

parameters.

next-hop ip-address

See “Configuring optional

parameters for an NQA test group”

NOTE:

NQA ICMP echo tests are not supported in IPv6 networks. To test the reachability of an IPv6 address, use the ping ipv6 command. For more information about the command, see “System maintenance and

debugging.”

Configuring DHCP tests

DHCP tests of an NQA test group are used to test if a DHCP server is on the network, and how long it takes for the DHCP server to respond to a client request and assign an IP address to the client.

Optional.

By default, no next hop IP address is configured.

Optional.

Configuration prerequisites

Before you start DHCP tests, configure the DHCP server. If the NQA (DHCP client) and the DHCP server are not in the same network segment, configure a DHCP relay. For the configuration of DHCP server and DHCP relay, see Layer 3

Configuring DHCP tests

To configure DHCP tests:

To do… Use the command… Remarks

1. Enter system view.

—

IP Services Configuration Guide.

system-view —

2. Enter NQA test group view.

3. Configure the test type as

DHCP and enter test type view.

4. Specify an interface to

perform DHCP tests.

5. Configure optional

parameters.

nqa entry admin-name operationtag

type dhcp Required.

operation interface interface-type

interface-number

See “Configuring optional

parameters for an NQA test group”

—

Required.

By default, no interface is configured to perform DHCP tests.

The specified interface must be up; otherwise, no probe packets can be sent out.

Optional.

NOTE:

• The interface that performs DHCP tests does not change its IP address. A DHCP test only simulates

address allocation in DHCP.

• When a DHCP test completes, the NQA client sends a DHCP-RELEASE packet to release the obtained

IP address.

Configuring DNS tests

DNS tests of an NQA test group are used to test whether the NQA client can translate a domain name into an IP address through a DNS server and test the time required for resolution.

Configuration prerequisites

Before you start DNS tests, configure the mapping between a domain name and an IP address on a DNS server.

Configuring DNS tests

To configure DNS tests:

To do… Use the command… Remarks

1. Enter system view.

2. Enter NQA test group view.

3. Configure the test type as

DNS and enter test type view.

system-view —

nqa entry admin-name operation-tag

type dns Required.

—

To do… Use the command… Remarks

4. Specify the IP address of the

DNS server as the destination address of DNS packets.

5. Configure the domain name

that needs to be translated.

6. Configure optional

parameters.

NOTE:

A DNS test simulates the domain name resolution. It does not save the mapping between the domain name and the IP address.

Configuring FTP tests

FTP tests of an NQA test group are used to test the connection between the NQA client and an FTP server and the time necessary for the FTP client to transfer a file to or download a file from the FTP server.

Configuration prerequisites

Before you start FTP tests, configure the FTP server. For example, configure the username and password that are used to log in to the FTP server. For more information about FTP server configuration, see Fundamentals Configuration Guide.

destination ip ip-address

resolve-target domain-name

See “Configuring optional

parameters for an NQA test group”

Required.

By default, no destination IP address is configured.

Required.

By default, no domain name is configured.

Optional.

Configuring FTP tests

To configure FTP tests:

To do… Use the command… Remarks

1. Enter system view.

2. Enter NQA test group view.

3. Configure the test type as FTP

and enter test type view.

4. Specify the IP address of the

FTP server as the destination address of FTP request packets.

5. Configure the source IP

address of FTP request packets.

system-view —

nqa entry admin-name operation- tag

type ftp Required.

destination ip ip-address

source ip ip-address

—

Required.

By default, no destination IP address is configured.

Required.

By default, no source IP address is specified.

The source IP address must be the IP address of a local interface. The local interface must be up; otherwise, no FTP requests can be sent out.

To do… Use the command… Remarks

Optional.

6. Configure the operation type.

7. Configure a login username.

8. Configure a login password.

9. Specify a file to be transferred

between the FTP server and the FTP client.

operation { get | put }

username name

password password

filename file-name

By default, the operation type for the FTP is get, which means obtaining files from the FTP server.

Required.

By default, no login username is configured.

Required.

By default, no login password is configured.

Required.

By default, no file is specified.

10. Set the data transmission

mode for FTP tests.

11. Configure optional

parameters.

NOTE:

• When you execute the put command, a file

FTP server. When you execute the get command, the device does not save the files obtained from the FTP server.

• When you download a file that does not exist on the FTP server, FTP tests fail.

• When you execute the get command, use a file with a small size. A big file may result in test failure

due to timeout, or may affect other services for occupying too much network bandwidth.

Configuring HTTP tests

HTTP tests of an NQA test group are used to test the connection between the NQA client and an HTTP server and the time required to obtain data from the HTTP server. HTTP tests enable you to detect the connectivity and performance of the HTTP server.

Configuration prerequisites

mode { active | passive }

See “Configuring optional

parameters for an NQA test group”

file-name

with fixed size and content is created on the

Optional.

active by default.

Optional.

Before you start HTTP tests, configure the HTTP server.

Configuring HTTP tests

To configure HTTP tests:

To do… Use the command… Remarks

1. Enter system view.

2. Enter NQA test group view.

3. Configure the test type as

HTTP and enter test type view.

system-view —

nqa entry admin-name operation- tag

type http Required.

—

To do… Use the command… Remarks

4. Configure the IP address of

the HTTP server as the destination address of HTTP request packets.

5. Configure the source IP

address of request packets.

6. Configure the operation type.

7. Configure the website that an

HTTP test visits.

destination ip ip-address

source ip ip-address

operation { get | post }

url url Required.

Required.

By default, no destination IP address is configured.

Optional.

By default, no source IP address is specified.

The source IP address must be the IP address of a local interface. The local interface must be up; otherwise, no probe packets can be sent out.

Optional.

By default, the operation type for the HTTP is get, which means obtaining data from the HTTP server.

8. Configure the HTTP version

used in HTTP tests.

9. Configure optional

parameters.

http-version v1.0

See “Configuring optional

parameters for an NQA test group”

NOTE:

The TCP port must be port 80 on the HTTP server for NQA HTTP tests.

Configuring UDP jitter tests

Do not perform NQA UDP jitter tests on known ports, ports from 1 to 1023. Otherwise, UDP jitter tests might fail or the corresponding services of this port might be unavailable.

Real-time services such as voice and video have high requirements on delay jitters. UDP jitter tests of an NQA test group obtain uni/bi-directional delay jitters. The test results help you verify whether a network can carry real-time services.

A UDP jitter test takes the following procedure:

1. The source sends packets at regular intervals to the destination port.

2. The destination affixes a time stamp to each packet that it receives, and then sends it back to the

source.

Optional.

By default, HTTP 1.0 is used.

Optional.

3. Upon receiving the response, the source calculates the delay jitter, which reflects network

performance. Delay refers to the amount of time it takes a packet to be transmitted from source to destination or from destination to source. Delay jitter is the delay variation over time.

Configuration prerequisites

UDP jitter tests require cooperation between the NQA server and the NQA client. Before you start UDP jitter tests, configure UDP listening services on the NQA server. For more information about UDP listening service configuration, see “Configuring the NQA server.”

Configuring UDP jitter tests

To configure UDP jitter tests:

To do… Use the command… Remarks

1. Enter system view.

system-view —

2. Enter NQA test group view.

3. Configure the test type as UDP

jitter and enter test type view.

4. Configure the destination

address of UDP packets.

5. Configure the destination port

of UDP packets.

6. Specify the source port

number of UDP packets.

7. Configure the size of the data

field in each UDP packet.

nqa entry admin-name operationtag

type udp-jitter Required.

destination ip ip-address

destination port port-number

source port port-number

data-size size

—

Required.

By default, no destination IP address is configured.

The destination IP address must be the same as that of the listening service on the NQA server.

Required.

By default, no destination port number is configured.

The destination port must be the same as that of the listening service on the NQA server.

Optional.

By default, no source port number is specified.

Optional.

100 bytes by default.

8. Configure the string to be

filled in the data field of each probe packet.

9. Configure the number of

probe packets to be sent during each UDP jitter probe operation.

10. Configure the interval for

sending probe packets during each UDP jitter probe operation.

11. Configure the interval the

NQA client must wait for a response from the server before it regards the response is timed out.

data-fill string

probe packet-number

packet-number

probe packet-interval packet-

interval

probe packet-timeout packet- timeout

Optional.

By default, the string is the hexadecimal number

00010203040506070809.

Optional.

10 by default.

Optional.

20 milliseconds by default.

Optional.

3000 milliseconds by default.

+ 119 hidden pages

HP 5820X Switch, 5800 Switch Configuration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

System maintenance and debugging

Configuring ping

Configuring ping example

Network requirements

Configuration procedure

Tracert

Configuring tracert

Configuration prerequisites

Tracert configuration

System debugging

Configuring system debugging

Configuring ping and tracert example

Network requirements

Configuration procedure

Configuring NQA

NQA benefits

Supporting multiple test types

Supporting the collaboration function

Supporting threshold monitoring

Basic NQA concepts

Test group

Test and probe

NQA client and server

NQA probe operation procedure

NQA configuration task list

Configuring the NQA server

Enabling the NQA client

Creating an NQA test group

Configuring an NQA test group

Configuring ICMP echo tests

Configuring DHCP tests

Configuration prerequisites

Configuring DHCP tests

Configuring DNS tests

Configuration prerequisites

Configuring DNS tests

Configuring FTP tests

Configuration prerequisites

Configuring FTP tests

Configuring HTTP tests

Configuration prerequisites

Configuring HTTP tests

Configuring UDP jitter tests

Configuration prerequisites

Configuring UDP jitter tests