H3C SR8800 User Manual

Network Management and Monitoring

Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com

Software version: SR8800-CMW520-R3347 Document version: 6W103-20120224

H3C SR8800 10G Core Routers

Configuration Guide

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Hangzhou H3C Technologies Co., Ltd.

Trademarks

H3C, , Aolynk, , H

Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL, SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd.

All other trademarks that may be mentioned in this manual are the property of their respective owners

Notice

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

G, VnG, PSPT,

Preface

The H3C SR8800 documentation set includes 13 configuration guides, which describe the software features for the H3C SR8800 10G Core Routers and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.

The Network Management and Monitoring Configuration Guide describes how to manage the network, view system information, collect traffic statistics, sample packets, analyze network quality, and use the ping, tracert, and debugging commands to examine and debug network connectivity.

This preface includes:

• Audience

• Conventions

• About the H3C SR8800 documentation set

• Obtaining documentation

• Technical support

• Documentation feedback

Audience

This documentation is intended for:

• Network planners

• Field technical support and servicing engineers

• Network administrators working with the SR8800 series

Conventions

This section describes the conventions used in this documentation set.

Command conventions

Convention Description

Boldface Bold text represents commands and keywords that you enter literally as shown.

Italic Italic text represents arguments that you replace with actual values.

[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.

{ x | y | ... }

[ x | y | ... ]

Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.

Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none.

{ x | y | ... } *

[ x | y | ... ] *

Asterisk marked braces enclose a set of required syntax choices separated by vertical bars, from which you select at least one.

Asterisk marked square brackets enclose optional syntax choices separated by vertical

Convention Description

gory

bars, from which you select one choice, multiple choices, or none.

&<1-n>

# A line that starts with a pound (#) sign is comments.

GUI conventions

Convention Description

Boldface

> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.

Symbols

Convention Description

WARNING

CAUTION

IMPORTANT

NOTE

The argument or keyword and argument combination before the ampersand (&) sign can be entered 1 to n times.

Window names, button names, field names, and menu items are in Boldface. For example, the New User window appears; click OK.

An alert that calls attention to important information that if not understood or followed can result in personal injury.

An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software.

An alert that calls attention to essential information.

An alert that contains additional or supplementary information.

TIP

An alert that provides helpful information.

Network topology icons

Represents a generic network device, such as a router, switch, or firewall.

Represents a routing-capable device, such as a router or Layer 3 switch.

Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

Port numbering in examples

The port numbers in this document are for illustration only and might be unavailable on your router.

About the H3C SR8800 documentation set

The H3C SR8800 documentation set includes:

Cate

Product description and specifications

Documents

Marketing brochures

Technology white papers

Purposes

Describe product specifications and benefits.

Provide an in-depth description of software features and technologies.

Category Documents

Card datasheets Describe card specifications, features, and standards.

Purposes

Hardware specifications and installation

Software configuration

Operations and maintenance

Compliance and safety manual

Installation guide

H3C N68 Cabinet Installation and Remodel Introduction

H3C Pluggable SFP [SFP+][XFP] Transceiver Modules Installation Guide

H3C High-End Network Products Hot-Swappable Module Manual

Configuration guides

Command references Provide a quick reference to all available commands.

Release notes

Provides regulatory information and the safety instructions that must be followed during installation.

Provides a complete guide to hardware installation and hardware specifications.

Guides you through installing and remodeling H3C N68 cabinets.

Guides you through installing SFP/SFP+/XFP transceiver modules.

Describes the hot-swappable modules available for the H3C high-end network products, their external views, and specifications.

Describe software features and configuration procedures.

Provide information about the product release, including the version history, hardware and software compatibility matrix, version upgrade information, technical support information, and software upgrading.

Obtaining documentation

You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com

Click the links on the top navigation bar to obtain different categories of product documentation:

[Technical Support & Documents > Technical Documents]

upgrading, and software feature configuration and maintenance documentation.

[Products & Solutions]

– Provides information about products and technologies, as well as solutions.

[Technical Support & Documents > Software Download]

software version.

Technical support

service@h3c.com

http://www.h3c.com

Documentation feedback

You can e-mail your comments about product documentation to info@h3c.com.

– Provides hardware installation, software

– Provides the documentation released with the

We appreciate your comments.

Using ping, tracert, and system debugging ··············································································································· 1

Ping ····················································································································································································· 1

Introduction ······························································································································································· 1 Configuring ping ······················································································································································ 1 Ping configuration example ···································································································································· 2

Tracert ················································································································································································ 3

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

Introduction to system debugging ··························································································································· 5 Configuring system debugging ······························································································································· 6

Ping and tracert configuration example ························································································································· 6

Configuring NQA ························································································································································ 8

NQA overview ·································································································································································· 8

NQA features ··························································································································································· 8 NQA concepts ······················································································································································· 10

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

Configuring ICMP echo tests ································································································································ 13

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

Configuring DNS tests ·········································································································································· 15

Configuring FTP tests ············································································································································· 16

Configuring HTTP tests ·········································································································································· 17

Configuring UDP jitter tests ··································································································································· 18

Configuring SNMP tests ······································································································································· 20

Configuring TCP tests ············································································································································ 21

Configuring UDP echo tests ·································································································································· 22

Configuring voice tests ········································································································································· 23

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

ICMP echo test configuration example ··············································································································· 32

DHCP test configuration example ························································································································ 34

DNS test configuration example ·························································································································· 35

FTP test configuration example ···························································································································· 36

HTTP test configuration example ·························································································································· 37

UDP jitter test configuration example ·················································································································· 39

SNMP test configuration example ······················································································································· 41

TCP test configuration example ··························································································································· 43

UDP echo test configuration example ················································································································· 44

Voice test configuration example ························································································································ 45

DLSw test configuration example ························································································································· 48

NQA collaboration configuration example········································································································ 49

Configuring NTP ························································································································································ 52

NTP overview ································································································································································· 52

NTP applications ··················································································································································· 52

How NTP works ····················································································································································· 52

NTP message format ············································································································································· 53

Operation modes of NTP ····································································································································· 55

NTP-supported MPLS L3VPN ································································································································ 57 NTP configuration task list ············································································································································· 57 Configuring the operation modes of NTP ··················································································································· 57

Configuring NTP client/server mode ·················································································································· 58

Configuring the NTP symmetric mode ················································································································ 59

Configuring NTP broadcast mode ······················································································································· 59

Configuring NTP multicast mode ························································································································· 60 Configuring the local clock as a reference source ····································································································· 61 Configuring optional parameters of NTP ···················································································································· 61

Specifying the source interface for NTP messages ···························································································· 61

Disabling an interface from receiving NTP messages ······················································································· 62

Configuring the maximum number of dynamic sessions allowed ···································································· 62 Configuring access-control rights ································································································································· 62

Configuration prerequisites ·································································································································· 63

Configuring NTP authentication in client/server mode ····················································································· 64

Configuring NTP authentication in symmetric peers mode ··············································································· 65

Configuring NTP authentication in broadcast mode ························································································· 66

Configuring NTP authentication in multicast mode ··························································································· 67 Displaying and maintaining NTP ································································································································· 68 NTP configuration examples ········································································································································· 69

Configuring NTP client/server mode ·················································································································· 69

Configuring the NTP symmetric mode ················································································································ 70

Configuring NTP broadcast mode ······················································································································· 72

Configuring NTP multicast mode ························································································································· 73

Configuring NTP client/server mode with authentication ················································································· 76

Configuring NTP broadcast mode with authentication ····················································································· 77

Configuring MPLS VPN time synchronization in client/server mode ······························································ 79

Configuring MPLS VPN time synchronization in symmetric peers mode ························································ 81

Configuring Clock monitoring ··································································································································· 83

Clock monitoring module overview ······························································································································ 83

Reference source level ·········································································································································· 83

Working mode of the clock monitoring module ································································································ 84

Working mode of the port clock ·························································································································· 84 Clock monitoring module configuration task list ········································································································· 85 Configuring working mode of the clock monitoring module of the SRPU ································································ 85 Configuring reference source priority ·························································································································· 86 Configuring SSM for reference sources ······················································································································· 86

Setting the ways of deriving SSM level ··············································································································· 86

Setting the bit position for transmitting bits clock source information ······························································ 86

Configuring SSM levels for the reference sources ····························································································· 87

Activating/deactivating SSM ······························································································································· 87 Setting the input port of the line clock (LPU port) ········································································································ 87 Displaying and maintaining the clock monitoring module ························································································ 88 Clock monitoring module configuration example ······································································································· 89

Configuring IPC ·························································································································································· 91

IPC overview ··································································································································································· 91

Node ······································································································································································· 91

Link ·········································································································································································· 91

Channel ·································································································································································· 91

Packet sending modes ·········································································································································· 92 Enabling IPC performance statistics ····························································································································· 92 Displaying and maintaining IPC ··································································································································· 93

Configuring SNMP ····················································································································································· 94

SNMP overview······························································································································································ 94

SNMP framework ·················································································································································· 94

SNMP operations ·················································································································································· 94

SNMP protocol versions ······································································································································· 94

MIB and view-based MIB access control ············································································································ 95 Configuring SNMP basic parameters ·························································································································· 95

Configuring SNMPv3 basic parameters ············································································································· 95

Configuring SNMPv1 or SNMPv2c basic parameters ······················································································ 96 Configuring SNMP logging ·········································································································································· 98

Introduction to SNMP logging ····························································································································· 98

Enabling SNMP logging ······································································································································· 98 Configuring SNMP traps ··············································································································································· 98

Enabling SNMP traps ··········································································································································· 99

Configuring the SNMP agent to send traps to a host ······················································································· 99 Displaying and maintaining SNMP ··························································································································· 100 SNMP configuration examples ··································································································································· 101

SNMPv1/SNMPv2c configuration example ···································································································· 101

SNMPv3 configuration example························································································································ 102

SNMP logging configuration example ············································································································· 103

Configuring MIB style ············································································································································· 106

Overview ······································································································································································· 106 Setting the MIB style ····················································································································································· 106 Displaying and maintaining MIB style ······················································································································· 106

Configuring RMON ················································································································································ 107

RMON overview ·························································································································································· 107

Working mechanism ··········································································································································· 107

RMON groups ····················································································································································· 108 Configuring the RMON statistics function ················································································································· 109

Configuring the RMON Ethernet statistics function ·························································································· 109

Configuring the RMON history statistics function ···························································································· 110 Configuring the RMON alarm function ····················································································································· 110

Configuration procedure ···································································································································· 111 Displaying and maintaining RMON ·························································································································· 111 RMON configuration examples ·································································································································· 112

Ethernet statistics group configuration example ······························································································· 112

History group configuration example ················································································································ 113

Alarm group configuration example ················································································································· 115

iii

Configuring a sampler ············································································································································ 117

Sampler overview ························································································································································ 117 Creating a sampler ······················································································································································ 117 Displaying and maintaining sampler ························································································································· 118 Sampler configuration examples ································································································································ 118

Using the sampler for NetStream ······················································································································ 118

Configuring port mirroring ····································································································································· 120

Terminologies of port mirroring ························································································································· 120

Port mirroring classification and implementation ····························································································· 121 Configuring local port mirroring ································································································································ 122 Configuring remote port mirroring ····························································································································· 123

Configuring a remote source mirroring group ································································································· 124

Configuring a remote destination mirroring group ·························································································· 125 Displaying and maintaining port mirroring ··············································································································· 125 Port mirroring configuration examples ······················································································································· 126

Local port mirroring configuration example (in source port mode) ······························································· 126

Layer 2 remote port mirroring configuration example (reflector port configurable) ···································· 127

Configuring traffic mirroring ·································································································································· 130

Traffic mirroring overview ··········································································································································· 130 Configuring traffic mirroring ······································································································································· 130 Displaying and maintaining traffic mirroring ············································································································ 131 Traffic mirroring configuration example ···················································································································· 131

Configuring NetStream ··········································································································································· 133

NetStream overview ···················································································································································· 133 NetStream basic concepts ·········································································································································· 133

Flow ······································································································································································ 133

NetStream operation ··········································································································································· 134 NetStream key technologies ······································································································································· 134

Flow aging ··························································································································································· 134

NetStream data export ······································································································································· 135

NetStream export formats ·································································································································· 137 NetStream sampling ···················································································································································· 138 NetStream configuration task list ································································································································ 138 Configuring NetStream ··············································································································································· 139

Configuring QoS-based NetStream ·················································································································· 139

Configuring NetStream on an SPC card ·········································································································· 140 Configuring NetStream sampling ······························································································································· 141

Configuring NetStream sampling ······················································································································ 141 Configuring attributes of NetStream export data ····································································································· 142

Configuring NetStream export format··············································································································· 142

Configuring refresh rate for NetStream version 9 templates ·········································································· 143

Configuring MPLS-aware NetStream ················································································································ 144 Configuring NetStream flow aging ···························································································································· 144 Configuring NetStream data export ·························································································································· 145

Configuring NetStream common data export ·································································································· 145

Configuring NetStream aggregation data export ··························································································· 146 Displaying and maintaining NetStream ···················································································································· 147 NetStream configuration examples ···························································································································· 147

QoS-based NetStream configuration example ································································································ 147

NetStream aggregation data export configuration example ········································································· 148

NetStream aggregation data export on an SPC card configuration example ············································· 150

Configuring IPv6 NetStream ·································································································································· 153

IPv6 NetStream overview ············································································································································ 153 IPv6 NetStream basic concepts ·································································································································· 153

IPv6 flow ······························································································································································· 153

IPv6 NetStream operation ·································································································································· 154 IPv6 NetStream key technologies ······························································································································· 154

IPv6 NetStream data export ······························································································································· 155

IPv6 NetStream export format ···························································································································· 156 IPv6 NetStream configuration task list ······················································································································· 156 Configuring IPv6 NetStream ······································································································································· 157

Configuring QoS-based IPv6 NetStream ·········································································································· 157

Configuring IPv6 NetStream on an SPC card ·································································································· 157 Configuring attributes of IPv6 NetStream data export ····························································································· 158

Configuring IPv6 NetStream export format ······································································································ 158

Configuring refresh rate for IPv6 NetStream version 9 templates ································································· 159

Configuring MPLS-aware NetStream ················································································································ 159 Configuring IPv6 NetStream flow aging ··················································································································· 160

Flow aging approaches ······································································································································ 160

Configuring IPv6 NetStream flow aging ··········································································································· 161 Configuring IPv6 NetStream data export ·················································································································· 161

Configuring IPv6 NetStream traditional data export ······················································································· 161

Configuring IPv6 NetStream aggregation data export ··················································································· 162 Displaying and maintaining IPv6 NetStream ············································································································ 163 IPv6 NetStream configuration examples ··················································································································· 163

IPv6 NetStream traditional data export configuration example ····································································· 163

IPv6 NetStream aggregation data export configuration example ································································· 165

Configuration example for IPv6 NetStream aggregation data export on an SPC card ······························ 167

Configuring protocol packet statistics ···················································································································· 170

Protocol packet statistics overview ····························································································································· 170 Displaying and maintaining protocol packet statistics ····························································································· 170

Configuring the information center ························································································································ 171

Information center overview ········································································································································ 171

Introduction to information center ······················································································································ 171

Classification of system information ·················································································································· 172

Eight levels of system information ······················································································································ 172

Eight output destinations and ten channels of system information ································································· 172

Outputting system information by source module ···························································································· 173

Default output rules of system information ········································································································ 173

System information format ·································································································································· 174 Configuring information center ··································································································································· 177

Information center configuration task list ·········································································································· 177

Outputting system information to the console ·································································································· 178

Outputting system information to a monitor terminal ······················································································ 179

Outputting system information to a log host ····································································································· 180

Outputting system information to the trap buffer······························································································ 180

Outputting system information to the log buffer ······························································································· 181

Outputting system information to the SNMP module ······················································································· 182

Outputting system information to the web interface ························································································ 183

Saving system information to a log file ············································································································· 184

Configuring synchronous information output ··································································································· 185

Disabling a port from generating link up/down logging information ··························································· 185 Displaying and maintaining information center ······································································································· 186

Information center configuration examples ··············································································································· 186

Outputting log information to a Unix log host·································································································· 186

Outputting log information to a Linux log host ································································································· 188

Outputting log information to the console ········································································································ 190

Flow logging configuration ···································································································································· 191

Flow logging overview ················································································································································ 191

Introduction to flow logging ······························································································································· 191

Flow logging versions ········································································································································· 191 Flow logging configuration task list ··························································································································· 192 Configuring flow logging version ······························································································································· 192 Configuring the source address for flow logging packets ······················································································· 193 Exporting flow logs ······················································································································································ 193

Exporting flow logs to log server ······················································································································· 193

Exporting flow logs to information center ········································································································· 194 Displaying and maintaining flow logging ················································································································· 194 Flow logging configuration example ························································································································· 195 Troubleshooting flow logging ····································································································································· 196

Index ········································································································································································ 197

Using ping, tracert, and system debugging

You can use the ping command to check the connectivity to a destination, use the tracert command to trace the path to a destination, and use the debug command to diagnose system faults based on the debugging information.

Ping

Introduction

Use the ping utility to check the reachability to a specific address.

Ping sends ICMP echo requests (ECHO-REQUEST) to the destination device. Upon receiving the requests, the destination device responds with ICMP echo replies (ECHO-REPLY) to the source device. The source device outputs statistics about the ping operation, including the number of packets sent, number of echo replies received, and the round-trip time. You can measure the network performance by analyzing these statistics.

Configuring ping

To configure the ping function:

Task Command

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

NOTE:

• For a low-speed network, H3C recommends that you 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.

Remarks

• For an IPv4 network:

ping [ ip ] [ -a source-ip | -c count | -f |

-h ttl | -i interface-type interface-number | -m interval | -n | -p pad | -q | -r | -s

packet-size | -t timeout | -tos tos | -v |

-vpn-instance vpn-instance-name ] * host

• For an IPv6 network:

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

-m interval | -s packet-size | -t timeout |

-vpn-instance vpn-instance-name ] *

host [ -i interface-type interface-number ]

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

Use either approach.

Available in any view.

• For more information about the ping lsp command, see

MPLS Command Reference

Ping configuration example

Network requirements

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

Figure 1 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 detailed information about 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 (Device A) sends an ICMP echo request with the RR option being empty to the

destination device (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, you can get detailed information about routes from Device A to Device C:

1.1.1.1 <-> {1.1.1.2; 1.1.2.1} <-> 1.1.2.2.

Tracert

Introduction

Traceroute enables you to get the IP addresses of Layer 3 devices in the path to a specific destination. You can use traceroute to check network connectivity and identify the failed nodes in the event of network failure.

Figure 2 Tracert operation

Traceroute uses received ICMP error messages to get the IP addresses of devices. As shown in Figure 2, traceroute works as follows:

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

(Device D). The destination UDP port is not used by any application on the destination device.

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

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

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 of the second Layer 3 device (1.1.2.2).

5. The above process continues until the packet sent by the source device reaches the ultimate

destination device. Since no application uses the destination port specified in the packet, the destination device responds with a port-unreachable ICMP message to the source device, with its IP address encapsulated. In this way, the source device gets the IP address of the destination device (1.1.3.2).

6. The source device thinks that the packet has reached the destination device after receiving the

port-unreachable ICMP message, and the path to the destination device is 1.1.1.2 to 1.1.2.2 to

1.1.3.2.

Configuring tracert

Configuration prerequisites

Enable sending of ICMP timeout packets on the intermediate device (the device between the source and destination devices). If the intermediate device is an H3C device, execute the ip ttl-expires enable command on the device. For more information about this command, see Layer 3—IP Services Command Reference.

Enable sending of ICMP destination unreachable packets on the destination device. If the destination device is an H3C device, execute the ip unreachables enable command. For more information about this command, see Layer 3—IP Services Command Reference.

Tracert configuration

To configure tracert:

Step Command

1. Enter system view. system-view N/A

• For an IPv4 network:

tracert [ -a source-ip | -f first-ttl | -m max-ttl | -p port | -q packet-number

| -vpn-instance vpn-instance-name |

2. Display the routes from

source to destination.

-w timeout ] * host

• For an IPv6 network:

tracert ipv6 [ -f first-ttl | -m max-ttl |

-p port | -q packet-number |

-vpn-instance vpn-instance-name |

-w timeout ] * host

NOTE:

For more information about the tracert lsp command, see

System debugging

Introduction to system debugging

Remarks

Use either approach.

Available in any view.

MPLS Command Reference

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

The following two switches control the display of debugging information:

• Protocol debugging switch—Controls protocol-specific debugging information.

• Screen output switch—Controls whether to display the debugging information on a certain screen.

As Figure 3 i

llustrates, assume the router can provide debugging for the three modules 1, 2, and 3. The debugging information is output on a terminal only 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 the 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 the chapter “Configuring the information center.”

To enable the output of debugging information to a terminal:

Step Command

1. Enable the terminal

monitoring of system information.

2. Enable the terminal

display of debugging information.

3. Enable debugging for a

specified module.

4. Display the enabled

debugging functions.

terminal monitor

terminal debugging

debugging { all [ timeout time ] |

module-name [ option ] }

display debugging [ interface

interface-type interface-number ] [ module-name ] [ | { begin | exclude | include } regular-expression ]

Remarks

Optional.

By default, the terminal monitoring on the console is enabled and that on the monitoring terminal is disabled.

Available in user view.

By default, terminal display of debugging information is disabled.

Available in user view.

By default, debugging for a specified module is disabled.

Available in user view

Optional.

Available in any view.

NOTE:

You must configure the debugging, terminal debugging and terminal monitor commands first to displa the detailed debugging information on the terminal. For more information about the terminal debuggin and terminal monitor commands, see

Network Management and Monitoring Command Reference

Ping and tracert configuration example

Network requirements

As shown in Figure 4, Device A failed to telnet Device C. Check 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 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 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. In this case, 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 overview

Network Quality Analyzer (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 features

Supporting multiple test types

Ping can use only the Internet Control Message Protocol (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 Implementing 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.

NOTE:

• 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.

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

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 desc

monitored.

Table 1 Monitored elements and NQA test types

Monitored elements Test t

Probe duration Tests excluding UDP jitter test and voice test

Count of probe failures Tests excluding UDP jitter test and voice test

Packet round-trip time UDP jitter test and voice test

Count of discarded packets UDP jitter test and voice test

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

High Availability Configuratio

e supported

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

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

Calculated Planning Impairment Factor (ICPIF) (see “Configuring

voice tests

Mean Opinion Scores (MOS) (see “Configuring voice tests”)

2. Threshold types

”

)

UDP jitter test and voice test

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 specific 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 specific 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 specific number of times, the state of the entry is set to over-threshold; otherwise, the state of the entry is set to below-threshold.

If the action to be triggered is configured as trap-only for a reaction entry, when the state of the entry changes, a trap message is generated and sent to the network management server.

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 specific interval. During each test, a specific 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 specific

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 I CMP echo or U DP echo test, one pro be 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

Complete the following task to enable the NQA server:

Task Remarks

Configuring the NQA server Required for TCP, UDP echo, UDP jitter and voice tests

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.

Complete these tasks 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:

Step Command

1. Enter system view.

2. Enable the NQA server.

3. Configure the listening

service.

system-view N/A

nqa server enable Disabled by default.

nqa server { tcp-connect | udp-echo } ip-address

port-number

Enabling the NQA client

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

Remarks

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.

To enable the NQA client:

Step Command

1. Enter system view.

2. Enable the NQA client.

system-view N/A

nqa agent enable

Creating an NQA test group

Create an NQA test group before you configure NQA tests.

To create an NQA test group:

Step Command

1. Enter system view.

2. Create an NQA test group

and enter the NQA test group view.

system-view N/A

nqa entry admin-name operation-tag

Remarks

Optional

Enabled by default

Remarks

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 an NQA test group

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:

Step 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.

5. Configure the size of the data

field in each ICMP echo request.

system-view N/A

nqa entry admin-name operation-tag

type icmp-echo N/A

destination ip ip-address

data-size size

N/A

By default, no destination IP address is configured.

Optional.

100 bytes by default.

Step Command Remarks

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.

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 requests take the IP address of the source interface as their source IP address when no source IP address is specified.

The specified source interface must be a Layer 2 Ethernet interface or a VLAN interface and the 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

Optional.

By default, no next hop IP address is configured.

Optional.

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

Monitoring Command Reference.

Network Management and

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.

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:

Step Command Remarks

—

IP Services Configuration Guide.

1. Enter 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.

system-view N/A

nqa entry admin-name operation-tag

type dhcp N/A

operation interface interface-type

interface-number

See “Configuring optional

parameters for an NQA test

”

group

N/A

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:

Step Command

1. Enter system view.

2. Enter NQA test group view.

3. Configure the test type as

DNS and enter test type view.

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:

DNS test simulates the domain name resolution. It does not save the mapping between the domain name

and the IP address.

Configuring FTP tests

Remarks

system-view N/A

nqa entry admin-name operation-tag

type dns N/A

destination ip ip-address

resolve-target domain-name

See “Configuring optional

parameters for an NQA test gr

oup

N/A

By default, no destination IP address is configured.

By default, no domain name is configured.

Optional.

”

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.

Configuring FTP tests

To configure FTP tests:

Step 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.

system-view N/A

nqa entry admin-name operation-tag

type ftp N/A

destination ip ip-address

N/A

By default, no destination IP address is configured.

Step Command Remarks

By default, no source IP address is specified.

5. Configure the source IP

address of FTP request packets.

6. Configure the operation type.

source ip ip-address

operation { get | put }

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.

Optional.

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

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.

10. Set the data transmission

mode for FTP tests.

11. Configure optional

parameters.

username name

password password

filename file-name By default, no file is specified.

mode { active | passive }

See “Configuring optional

parameters for an NQA test

”

group

NOTE:

• When you execute the put command, a file

file-name

with fixed size and content is created on the 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 bi

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

By default, no login username is configured.

By default, no login password is configured.

Optional.

active by default.

Optional.

file may result in test failure due

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

Before you start HTTP tests, configure the HTTP server.

Configuring HTTP tests

To configure HTTP tests:

Step Command Remarks

1. Enter system view.

2. Enter NQA test group view.

3. Configure the test type as

HTTP and enter test type view.

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.

system-view N/A

nqa entry admin-name operation-tag

type http N/A

destination ip ip-address

source ip ip-address

operation { get | post }

url url N/A

N/A

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

NOTE:

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:

Optional.

By default, HTTP 1.0 is used.

Optional.

”

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

+ 180 hidden pages

H3C SR8800 User Manual

Preface

Audience

Conventions

Command conventions

GUI conventions

Symbols

Network topology icons

Port numbering in examples

About the H3C SR8800 documentation set

Obtaining documentation

Technical support

Documentation feedback

Contents

Using ping, tracert, and system debugging

Ping

Introduction

Configuring ping

Ping configuration example

Network requirements

Configuration procedure

Tracert

Introduction

Configuring tracert

Configuration prerequisites

Tracert configuration

System debugging

Introduction to system debugging

Configuring system debugging

Ping and tracert configuration example

Network requirements

Configuration procedure

Configuring NQA

NQA overview

NQA features

Supporting multiple test types

Supporting the collaboration function

Supporting threshold monitoring

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