H3C H3C S7500E Series Installation manual

H3C S7500E Switch Series
Network Management and Monitoring
Command Reference
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: S7500E Series--Release 6701 and Later
S7508E-X--------Release 6901 and Later
Document version: 6W101-20120903

Copyright © 2012, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
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, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL,
SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT,
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.

Preface
The H3C S7500E documentation set includes 12 command references, which describe the commands
and command syntax options available for the H3C S7500E Release 6700 Series and the H3C
S7508E-X Release 6900 Series.
The Network Management and Monitoring Command Reference describes network management and
monitoring configuration commands. It covers the commands for viewing system information, collecting
traffic statistics, assessing the network performance, synchronizing time for all devices with clocks in your
network, and checking and debugging the current network connectivity with the ping, tracert, and
debug commands.
This preface includes:
•Audience
•Conventions
•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 S7500E series
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
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 | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical

bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Descri
p
tion
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
Convention Descri
p
tion
WARNING An alert that calls attention to important information that if not understood or followed can
result in personal injury.
CAUTION 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.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
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] – Provides hardware installation, software
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] – Provides the documentation released with the
software version.
Technical support
servi[email protected]
http://www.h3c.com

Documentation feedback
You can e-mail your comments about product documentation to inf[email protected].
We appreciate your comments.

i
Contents
Ping, tracert, and system debugging commands······································································································· 1
Ping and tracert commands ·············································································································································1
ping············································································································································································1
ping ipv6···································································································································································5
tracert·········································································································································································7
tracert ipv6································································································································································9
System debugging commands······································································································································ 10
debugging······························································································································································ 10
display debugging ················································································································································ 11
NTP configuration commands···································································································································13
display ntp-service sessions ·································································································································· 13
display ntp-service status ······································································································································ 17
display ntp-service trace ······································································································································· 18
ntp-service access·················································································································································· 19
ntp-service authentication enable ························································································································ 20
ntp-service authentication-keyid ··························································································································· 21
ntp-service broadcast-client ·································································································································· 22
ntp-service broadcast-server ································································································································· 22
ntp-service dscp ····················································································································································· 23
ntp-service in-interface disable····························································································································· 24
ntp-service max-dynamic-sessions ························································································································ 24
ntp-service multicast-client····································································································································· 25
ntp-service multicast-server···································································································································· 25
ntp-service refclock-master···································································································································· 26
ntp-service reliable authentication-keyid ············································································································· 27
ntp-service source-interface··································································································································· 27
ntp-service unicast-peer········································································································································· 28
ntp-service unicast-server ······································································································································ 29
PTP configuration commands ····································································································································31
display ptp ····························································································································································· 31
ptp active force-state ············································································································································· 35
ptp announce-interval············································································································································ 35
ptp announce-timeout············································································································································ 36
ptp asym-correction ··············································································································································· 37
ptp clock-source ····················································································································································· 37
ptp clock-step ························································································································································· 40
ptp delay-mechanism ············································································································································ 40
ptp destination-mac ··············································································································································· 41
ptp enable ······························································································································································ 42
ptp force-state ························································································································································ 43
ptp min-delayreq-interval ······································································································································ 43
ptp mode ································································································································································ 44
ptp pdelay-req-interval ·········································································································································· 45
ptp port-mode ························································································································································ 46
ptp priority······························································································································································ 46
ptp slave-only ························································································································································· 47
ptp syn-interval······················································································································································· 48
ptp utc····································································································································································· 48

ii
ptp utc offset··························································································································································· 49
reset ptp·································································································································································· 50
Information center configuration commands············································································································51
display channel ····················································································································································· 51
display info-center ················································································································································· 52
display logbuffer···················································································································································· 54
display logbuffer summary ··································································································································· 56
display logfile buffer ············································································································································· 58
display logfile summary········································································································································ 58
display trapbuffer ·················································································································································· 59
enable log updown··············································································································································· 61
info-center channel name ····································································································································· 61
info-center console channel·································································································································· 62
info-center enable·················································································································································· 62
info-center format unicom ····································································································································· 63
info-center logbuffer ·············································································································································· 63
info-center logfile enable ······································································································································ 64
info-center logfile frequency ································································································································· 65
info-center logfile size-quota································································································································· 65
info-center logfile switch-directory ······················································································································· 66
info-center loghost ················································································································································· 66
info-center loghost source ····································································································································· 67
info-center monitor channel ·································································································································· 69
info-center snmp channel······································································································································ 69
info-center source ·················································································································································· 70
info-center synchronous ········································································································································ 72
info-center timestamp ············································································································································ 73
info-center timestamp loghost······························································································································· 74
info-center trapbuffer············································································································································· 75
logfile save····························································································································································· 76
reset logbuffer························································································································································ 76
reset trapbuffer······················································································································································· 77
terminal debugging··············································································································································· 77
terminal logging ···················································································································································· 77
terminal monitor····················································································································································· 78
terminal trapping··················································································································································· 79
SNMP commands ························································································································································ 1
display snmp-agent community·······························································································································1
display snmp-agent group ·······································································································································2
display snmp-agent local-engineid ·························································································································4
display snmp-agent mib-view ··································································································································4
display snmp-agent statistics ···································································································································6
display snmp-agent sys-info·····································································································································8
display snmp-agent trap queue·······························································································································9
display snmp-agent trap-list ·····································································································································9
display snmp-agent usm-user································································································································ 10
enable snmp trap updown ··································································································································· 12
snmp-agent····························································································································································· 13
snmp-agent calculate-password ··························································································································· 13
snmp-agent community ········································································································································· 14
snmp-agent group·················································································································································· 16
snmp-agent local-engineid···································································································································· 17
snmp-agent log ······················································································································································ 18

iii
snmp-agent ifmib long-ifindex enable ················································································································· 19
snmp-agent mib-view············································································································································· 19
snmp-agent packet max-size ································································································································ 21
snmp-agent packet response dscp······················································································································· 21
snmp-agent sys-info ··············································································································································· 22
snmp-agent target-host ·········································································································································· 23
snmp-agent trap enable ········································································································································ 24
snmp-agent trap if-mib link extended ·················································································································· 26
snmp-agent trap life··············································································································································· 27
snmp-agent trap queue-size·································································································································· 28
snmp-agent trap source········································································································································· 29
snmp-agent usm-user { v1 | v2c }························································································································ 30
snmp-agent usm-user v3········································································································································ 31
MIB configuration commands ···································································································································34
display mib-style ···················································································································································· 34
mib-style·································································································································································· 34
RMON configuration commands······························································································································36
display rmon alarm ··············································································································································· 36
display rmon event················································································································································ 37
display rmon eventlog··········································································································································· 39
display rmon history·············································································································································· 40
display rmon prialarm ·········································································································································· 43
display rmon statistics ··········································································································································· 44
rmon alarm····························································································································································· 46
rmon event······························································································································································ 48
rmon history ··························································································································································· 49
rmon prialarm ························································································································································ 50
rmon statistics························································································································································· 52
Port mirroring configuration commands ···················································································································54
display mirroring-group ········································································································································ 54
mirroring-group······················································································································································ 55
mirroring-group mirroring-port ····························································································································· 56
mirroring-group monitor-egress···························································································································· 57
mirroring-group monitor-port ································································································································ 58
mirroring-group reflector-port ······························································································································· 59
mirroring-group remote-probe vlan······················································································································ 60
mirroring-port ························································································································································· 61
monitor-port···························································································································································· 62
uni mirroring-port··················································································································································· 63
uni monitor-port······················································································································································ 63
Traffic mirroring configuration commands ···············································································································65
mirror-to ·································································································································································· 65
NQA configuration commands·································································································································66
NQA client configuration commands ·························································································································· 66
advantage-factor ··················································································································································· 66
codec-type······························································································································································ 66
data-fill···································································································································································· 67
data-size ································································································································································· 68
description (any NQA operation view) ·············································································································· 69
destination ip ························································································································································· 69
destination port······················································································································································ 70
display nqa history················································································································································ 71

iv
display nqa reaction counters······························································································································ 72
display nqa result ·················································································································································· 74
display nqa statistics ············································································································································· 78
filename·································································································································································· 83
frequency································································································································································ 84
history-record enable ············································································································································ 85
history-record keep-time········································································································································ 85
history-record number ··········································································································································· 86
http-version ····························································································································································· 87
mode······································································································································································· 87
next-hop·································································································································································· 88
nqa·········································································································································································· 88
nqa agent enable ·················································································································································· 89
nqa agent max-concurrent···································································································································· 90
nqa schedule·························································································································································· 90
operation (FTP operation view)···························································································································· 91
operation (HTTP operation view) ························································································································· 92
operation interface ················································································································································ 92
password (FTP operation view)···························································································································· 93
probe count···························································································································································· 94
probe packet-interval ············································································································································ 95
probe packet-number ············································································································································ 95
probe packet-timeout············································································································································· 96
probe timeout························································································································································· 96
reaction checked-element icpif····························································································································· 97
reaction checked-element { jitter-ds | jitter-sd } ·································································································· 98
reaction checked-element mos ···························································································································100
reaction checked-element { owd-ds | owd-sd }································································································101
reaction checked-element packet-loss················································································································102
reaction checked-element probe-duration·········································································································103
reaction checked-element probe-fail (for trap)··································································································104
reaction checked-element probe-fail (for trigger) ·····························································································105
reaction checked-element rtt·······························································································································106
reaction trap ························································································································································108
resolve-target························································································································································109
route-option bypass-route····································································································································109
source interface ···················································································································································110
source ip·······························································································································································111
source port ···························································································································································111
statistics hold-time················································································································································112
statistics max-group ·············································································································································113
statistics interval···················································································································································113
tos··········································································································································································114
ttl············································································································································································115
type ·······································································································································································115
url ··········································································································································································116
username (FTP operation view)··························································································································117
vpn-instance (ICMP echo operation view) ········································································································117
NQA server configuration commands·······················································································································118
display nqa server status ····································································································································118
nqa server enable ···············································································································································119
nqa server tcp-connect ········································································································································120
nqa server udp-echo ···········································································································································120
nqa server tos ······················································································································································121

v
sFlow configuration commands······························································································································ 123
display sflow ························································································································································123
sflow agent···························································································································································125
sflow collector ······················································································································································125
sflow counter interval ··········································································································································126
sflow counter collector ········································································································································127
sflow flow collector··············································································································································127
sflow flow max-header········································································································································128
sflow sampling-mode ··········································································································································128
sflow sampling-rate ·············································································································································129
sflow source ·························································································································································130
NetStream configuration commands ····················································································································· 131
display ip netstream cache·································································································································131
display ip netstream export ································································································································133
display ip netstream template ····························································································································135
enable···································································································································································137
ip netstream··························································································································································137
ip netstream aggregation ···································································································································138
ip netstream aggregation advanced·················································································································139
ip netstream export host ·····································································································································140
ip netstream export rate······································································································································141
ip netstream export source ·································································································································141
ip netstream export v9-template refresh-rate packet ························································································142
ip netstream export v9-template refresh-rate time ····························································································143
ip netstream export version ································································································································144
ip netstream filter·················································································································································145
ip netstream sampler···········································································································································145
ip netstream timeout active·································································································································146
ip netstream timeout inactive······························································································································147
netstream filter······················································································································································147
reset ip netstream statistics ·································································································································148
IPv6 NetStream configuration commands············································································································· 149
display ipv6 netstream cache ····························································································································149
display ipv6 netstream export····························································································································151
display ipv6 netstream template························································································································152
enable···································································································································································155
ipv6 netstream ·····················································································································································155
ipv6 netstream aggregation·······························································································································156
ipv6 netstream aggregation advanced·············································································································157
ipv6 netstream export host ·································································································································157
ipv6 netstream export rate ·································································································································159
ipv6 netstream export source·····························································································································159
ipv6 netstream export v9-template refresh-rate packet····················································································160
ipv6 netstream export v9-template refresh-rate time························································································161
ipv6 netstream export version 9 ························································································································162
reset ipv6 netstream statistics ·····························································································································162
Sampler configuration commands ························································································································· 164
display sampler ···················································································································································164
sampler·································································································································································165
IPC configuration commands ································································································································· 166
display ipc channel ·············································································································································166
display ipc link·····················································································································································167

vi
display ipc multicast-group·································································································································168
display ipc node··················································································································································169
display ipc packet ···············································································································································169
display ipc performance·····································································································································170
display ipc queue ················································································································································172
ipc performance enable ·····································································································································173
reset ipc performance ·········································································································································174
PoE configuration commands································································································································· 174
apply poe-profile ·················································································································································175
apply poe-profile interface ·································································································································175
display poe device··············································································································································176
display poe interface ··········································································································································177
display poe interface power ······························································································································180
display poe power-usage ···································································································································182
display poe pse ···················································································································································184
display poe pse interface ···································································································································186
display poe pse interface power ·······················································································································187
display poe-power···············································································································································188
display poe-power ac-input state·······················································································································191
display poe-power alarm····································································································································193
display poe-power dc-output state·····················································································································194
display poe-power dc-output value····················································································································195
display poe-power status ····································································································································196
display poe-power supervision-module·············································································································198
display poe-power switch state··························································································································199
display poe-profile···············································································································································201
display poe-profile interface·······························································································································202
poe enable···························································································································································203
poe enable pse····················································································································································204
poe legacy enable ··············································································································································204
poe max-power····················································································································································205
poe max-power (system view)····························································································································206
poe pd-description ··············································································································································206
poe pd-policy priority··········································································································································207
poe power max-value ·········································································································································207
poe priority ··························································································································································208
poe priority (system view)···································································································································209
poe pse-policy priority ········································································································································210
poe update···························································································································································211
poe utilization-threshold······································································································································211
poe-power input-threshold ··································································································································212
poe-power output-threshold ································································································································213
poe-profile ····························································································································································214
Index ········································································································································································ 215

1
Ping, tracert, and system debugging
commands
Ping and tracert commands
ping
Use ping to verify whether the destination in an IP network is reachable, and to display the related
statistics.
Syntax
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
Views
Any view
Default command level
0: Visit level
Parameters
ip: Supports IPv4 protocol. If this keyword is not provided, IPv4 is also supported.
-a source-ip: Specifies the source IP address of an ICMP echo request (ECHO-REQUEST). It must be an
IP address configured on the device. If this parameter is not provided, the source IP address of an ICMP
echo request is the primary IP address of the outbound interface of the request.
-c count: Specifies the number of times that an ICMP echo request is sent, which ranges from 1 to
4294967295 and defaults to 5.
-f: Discards packets larger than the MTU of a given interface, which means the ICMP echo request is not
allowed to be fragmented.
-h ttl: Specifies the TTL value for an ICMP echo request, which ranges from 1 to 255 and defaults to 255.
-i interface-type interface-number: Specifies the ICMP echo request sending interface by its type and
number. If this parameter is not provided, the ICMP echo request sending interface is determined by
searching the routing table or forwarding table according to the destination IP address.
-m interval: Specifies the interval (in milliseconds) to send an ICMP echo request, which ranges from 1 to
65535 and defaults to 200.
•If a response from the destination is received within the timeout time, the interval to send the next
echo request equals the actual response period plus the value of interval.
•If no response from the destination is received within the timeout time, the interval to send the next
echo request equals the timeout value plus the value of interval.
-n: Disables domain name resolution for the host argument. When this keyword is not provided, if the
host argument represents the host name of the destination, the device translates host into an address.

2
-p pad: Specifies the value of the pad field in an ICMP echo request, in hexadecimal format, 1 to 8 bits,
in the range 0 to ffffffff. If the specified value is less than 8 bits, 0s are added in front of the value to
extend it to 8 bits. For example, if pad is configured as 0x2f, then the packets are padded with
0x0000002f repeatedly to make the total length of the packet meet the requirements of the device. By
default, the padded value starts from 0x01 up to 0xff, where another round starts again if necessary, like
0x010203…feff01….
-q: Presence of this keyword indicates that only statistics are displayed. Absence of this keyword
indicates that all information is displayed.
-r: Records routing information. If this keyword is not provided, routes are not recorded.
-s packet-size: Specifies length (in bytes) of an ICMP echo request, which ranges from 20 to 8100 and
defaults to 56.
-t timeout: Specifies the timeout value (in milliseconds) of an ICMP echo reply (ECHO-REPLY). If the
source does not receive an ICMP echo reply within the timeout, it considers the ICMP echo reply timed
out. The value ranges from 0 to 65535 and defaults to 2000.
-tos tos: Specifies the type of service (ToS) value of an ICMP echo request, which ranges from 0 to 255
and defaults to 0. Starting from 0, every four consecutive ToS values map to a DSCP value. The network
device uses the DSCP value as a reference to determine the packet priority for transmission.
-v: Displays non ICMP echo reply received. If this keyword is not provided, the system does not display
non ICMP echo reply.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN to which the destination belongs, where
vpn-instance-name is a case-sensitive string of 1 to 31 characters. If the destination is on the public
network, do not specify this option.
host: IP address or host name (a string of 1 to 255 characters) of the destination.
Usage guidelines
With the ping command executed, the source sends an ICMP echo request to the destination:
•If the destination name is unrecognizable, the system outputs "Error: Ping: Unknown host
host-name".
•If the source receives an ICMP echo reply from the destination within the timeout, the system outputs
the related information of the reply.
•If the source does not receive an ICMP echo reply from the destination within the timeout, the system
outputs "Request time out".
To use the name of the destination host to perform the ping operation, you must configure the Domain
Name System (DNS) on the device first. Otherwise, the ping operation fails. For more information about
DNS, see Layer 3—IP Services Configuration Guide.
To abort the ping operation during the execution of the command, press Ctrl+C.
Examples
# Examine whether the device with an IP address of 1.1.2.2 is reachable.
<Sysname> 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

3
--- 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
The output shows the following:
•The destination was reachable.
•All ICMP echo requests sent by the source got responses.
•The minimum time, average time, and maximum time for the packet’s roundtrip time are 1 ms, 41
ms, and 205 ms respectively.
# Examine whether the device with an IP address of 1.1.2.2 in VPN 1 is reachable.
<Sysname> ping -vpn-instance vpn1 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
The output shows the following:
•The destination in VPN 1 was reachable.
•All ICMP echo requests sent by the source got responses.
•The minimum time, average time, and maximum time for the packet’s roundtrip time are 1 ms, 41
ms, and 205 ms respectively.
# Examine whether the device with an IP address of 1.1.2.2 is reachable. Only the results are displayed.
<Sysname> ping -q 1.1.2.2
PING 1.1.2.2: 56 data bytes, press CTRL_C to break
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
4 packet(s) received
20.00% packet loss
round-trip min/avg/max = 1/12/29 ms
# Examine whether the device with an IP address of 1.1.2.2 is reachable. The route information is
displayed.
<Sysname> 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:

4
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 output shows the following information:
•The destination was reachable.
•T h e ro u t e i s 1.1.1.1 < - > { 1.1.1. 2; 1.1. 2.1 } < - > 1.1. 2. 2.
Table 1 Command output
Field Descri
p
tion
PING 1.1.2.2 Examine whether the device with IP address 1.1.2.2 is reachable.
56 data bytes Number of data bytes in each ICMP echo request.
press CTRL_C to break During the execution of the command, you can press Ctrl+C to abort the
ping operation.

5
Field Descri
p
tion
Reply from 1.1.2.2 : bytes=56
Sequence=1 ttl=255 time=1 ms
Received the ICMP reply from the device whose IP address is 1.1.2.2. If
no reply is received during the timeout period, "Request time out" is
displayed.
•bytes—Number of data bytes in the ICMP reply.
•Sequence—Packet sequence, used to determine whether a segment is
lost, disordered or repeated.
•ttl—TTL value in the ICMP reply.
•time—Response time.
Record Route
Routers through which the ICMP echo request passed. They are
displayed in inversed order, that is, the router with a smaller distance to
the destination is displayed first.
--- 1.1.2.2 ping statistics --- Statistics on data received and sent in the ping operation.
5 packet(s) transmitted Number of ICMP echo requests sent.
5 packet(s) received Number of ICMP echo requests received.
0.00% packet loss Percentage of packets not responded to the total packets sent.
round-trip min/avg/max = 0/4/20
ms
Minimum/average/maximum response time, in ms. The field is not
available for failed ping attempts in an IPv4 network. In an IPv6 network,
however, the field is available and set to 0/0/0 ms.
ping ipv6
Use ping ipv6 to verify whether an IPv6 address is reachable, and display the corresponding statistics.
Syntax
ping ipv6 [ -a source-ipv6 | -c count | -m interval | -s packet-size | -t timeout | -tos tos | -vpn-instance
vpn-instance-name ] * host [ -i interface-type interface-number ]
Views
Any view
Default command level
0: Visit level
Parameters
-a source-ipv6: Specifies the source IPv6 address of an ICMP echo request. It must be a legal IPv6
address configured on the device. If this parameter is not provided, the source IPv6 address of an ICMP
echo request is the IPv6 address of the outbound interface of the request (The address selection rule is
defined by RFC 3484).
-c count: Specifies the number of times that an ICMPv6 echo request is sent, which ranges from 1 to
4294967295 and defaults to 5.
-m interval: Specifies the interval (in milliseconds) to send an ICMPv6 echo reply, which ranges from 1
to 65535 and defaults to 200.
•If a response from the destination is received within the timeout time, the interval to send the next
echo request equals the actual response period plus the value of interval.
•If no response from the destination is received within the timeout time, the interval to send the next
echo request equals the timeout value plus the value of interval.

6
-s packet-size: Specifies length (in bytes) of an ICMPv6 echo request, which ranges from 20 to 8100 and
defaults to 56.
-t timeout: Specifies the timeout value (in milliseconds) of an ICMPv6 echo reply, which ranges from 0 to
65535 and defaults to 2000.
-tos tos: Specifies the ToS value of an ICMP echo request, which ranges from 0 to 255 and defaults to 0.
Starting from 0, every four consecutive ToS values map to a DSCP value. The network device uses the
DSCP value as a reference to determine the packet priority for transmission. This option is available in
S7500E Release 6703, S7508E-X Release 6903, and their later versions.
host: IPv6 address or host name of the destination, which is a string of 1 to 46 characters.
-i interface-type interface-number: Specifies an outbound interface by its type and number. This
parameter can be used only when the destination address is the link local address and the specified
outbound interface must have a link local address (see Layer 3—IP Services Configuration Guide). If this
parameter is not provided, the ICMP echo request sending interface is determined by searching the
routing table or forwarding table according to the destination IP address.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN to which the destination belongs, where
vpn-instance-name is a case-sensitive string of 1 to 31 characters. If the destination is on the public
network, do not specify this option.
Usage guidelines
To use the name of the destination host to perform the ping ipv6 operation, you must configure DNS on
the device first; otherwise, the ping ipv6 operation fails. For more information about DNS, see Layer
3—IP Services Configuration Guide.
To abort the ping ipv6 operation during the execution of the command, press Ctrl+C.
Examples
# Verify whether the IPv6 address 2001::1 is reachable.
<Sysname> ping ipv6 2001::1
PING 2001::2 : 56 data bytes, press CTRL_C to break
Reply from 2001::1
bytes=56 Sequence=1 hop limit=64 time = 62 ms
Reply from 2001::1
bytes=56 Sequence=2 hop limit=64 time = 26 ms
Reply from 2001::1
bytes=56 Sequence=3 hop limit=64 time = 20 ms
Reply from 2001::1
bytes=56 Sequence=4 hop limit=64 time = 4 ms
Reply from 2001::1
bytes=56 Sequence=5 hop limit=64 time = 16 ms
--- 2001::2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 4/25/62 ms
# Verify whether the IPv6 address 2001::1 in VPN 1 is reachable.
<Sysname> ping ipv6 –vpn-instance vpn1 2001::1
PING 2001::1 : 56 data bytes, press CTRL_C to break

7
Reply from 2001::1
bytes=56 Sequence=1 hop limit=64 time = 62 ms
Reply from 2001::1
bytes=56 Sequence=2 hop limit=64 time = 26 ms
Reply from 2001::1
bytes=56 Sequence=3 hop limit=64 time = 20 ms
Reply from 2001::1
bytes=56 Sequence=4 hop limit=64 time = 4 ms
Reply from 2001::1
bytes=56 Sequence=5 hop limit=64 time = 16 ms
--- 2001::2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 4/25/62 ms
The "hop limit" field in this prompt information has the same meaning as the "ttl" field in the prompt
information displayed by the IPv4 ping command, indicating the TTL value in the ICMPv6 echo request.
For the description on other fields, see Table 1
tracert
Use tracert to trace the path the packets traverse from source to destination.
Syntax
tracert [ -a source-ip | -f first-ttl |-m max-ttl | -p port | -q packet-number | -tos tos | -vpn-instance
vpn-instance-name |-w timeout ] * host
Views
Any view
Default command level
0: Visit level
Parameters
-a source-ip: Specifies the source IP address of a tracert packet. It must be a legal IP address configured
on the device. If this parameter is not provided, the source IP address of an ICMP echo request is the
primary IP address of the outbound interface of the tracert packet.
-f first-ttl: Specifies the first TTL, or, the allowed number of hops for the first packet. It ranges from 1 to 255
and defaults to 1, and must be less than the maximum TTL.
-m max-ttl: Specifies the maximum TTL, or, the maximum allowed number of hops for a packet. It ranges
from 1 to 255 and defaults to 30, and must be greater than the first TTL.
-p port: Specifies the UDP port number of the destination, which ranges from 1 to 65535 and defaults to
33434. You do not need to modify this parameter.
-q packet-number: Specifies the number of probe packets sent each time, which ranges from 1 to 65535
and defaults to 3.
-tos tos: Specifies the ToS value of a tracert packet, which ranges from 0 to 255 and defaults to 0.
Starting from 0, every four consecutive ToS values map to a DSCP value. The network device uses the

8
DSCP value as a reference to determine the packet priority for transmission. This option is available in
S7500E Release 6703, S7508E-X Release 6903, and their later versions.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN to which the destination belongs, where
vpn-instance-name is a case-sensitive string of 1 to 31 characters. If the destination is on the public
network, do not specify this option.
-w timeout: Specifies the timeout time of the reply packet of a probe packet, which ranges from 1 to
65535 milliseconds and defaults to 5000 milliseconds.
host: IP address or host name (a string of 1 to 255 characters) of the destination.
Usage guidelines
Output information of the tracert command includes IP addresses of all the Layer 3 devices the packets
traverse from source to destination. Asterisks (* * *) are displayed if the device cannot reply with an
ICMP error message (probably because the destination is unreachable or sending ICMP
timeout/destination unreachable packets is disabled).
To abort the tracert operation during the execution of the command, press Ctrl+C.
Examples
# Display the path the packets traverse from source to destination with an IP address of 1.1.2.2.
<Sysname> 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 break
1 1.1.1.2 673 ms 425 ms 30 ms
2 1.1.2.2 580 ms 470 ms 80 ms
# Trace the path to destination 192.168.0.46 over an MPLS network.
<Sysname> tracert 192.168.0.46
traceroute to 192.168.0.46(192.168.0.46) 30 hops max,40 bytes packet, press CTRL_C to
break
1 192.0.2.13 (192.0.2.13) 0.661 ms 0.618 ms 0.579 ms
2 192.0.2.9 (192.0.2.9) 0.861 ms 0.718 ms 0.679 ms
MPLS Label=100048 Exp=0 TTL=1 S=1
3 192.0.2.5 (192.0.2.5) 0.822 ms 0.731 ms 0.708 ms
MPLS Label=100016 Exp=0 TTL=1 S=1
4 192.0.2.1 (192.0.2.1) 0.961 ms 8.676 ms 0.875 ms
Table 2 Command output
Field Descri
p
tion
traceroute to 1.1.2.2(1.1.2.2) Display the route the IP packets traverse from the current device to the
device whose IP address is 1.1.2.2.
hops max Maximum number of hops of the probe packets, which can be set
through the -m keyword.
bytes packet Number of bytes of a probe packet.
press CTRL_C to break During the execution of the command, you can press Ctrl+C to abort
the tracert operation.
1 1.1.1.2 673 ms 425 ms 30 ms
Probe result of the probe packets whose TTL is 1, including the IP
address of the first hop and the roundtrip time of three probe packets.
Number of packets that can be sent in each probe can be set through
the -q keyword.

9
Field Descri
p
tion
MPLS Label=100048 Exp=0 TTL=1
S=1
ICMP timeout packets on an MPLS network, carry MPLS label
information:
•Label—Label value that is used to identify a forwarding
equivalence class (FEC).
•Exp—Reserved, usually used for class of service (CoS).
•TTL—TTL value.
•S—MPLS supports multiple levels of labels. Value 1 indicates that
the label is at the bottom of the label stack, and value 0 indicates
that the label is not at the bottom of the label stack.
tracert ipv6
Use tracert ipv6 to view the path the IPv6 packets traverse from source to destination.
Syntax
tracert ipv6 [ -f first-ttl | -m max-ttl | -p port | -q packet-number | -tos tos | -vpn-instance
vpn-instance-name | -w timeout ] * host
Views
Any view
Default command level
0: Visit level
Parameters
-f first-ttl: Specifies the first TTL, or, the allowed number of hops for the first packet. It ranges from 1 to 255
and defaults to 1, and must be less than the maximum TTL.
-m max-ttl: Specifies the maximum TTL, or, the maximum allowed number of hops for a packet. It ranges
from 1 to 255 and defaults to 30, and must be greater than the first TTL.
-p port: Specifies the UDP port number of the destination, which ranges from 1 to 65535 and defaults to
33434. It is unnecessary to modify this parameter.
-q packet-number: Specifies the number of probe packets sent each time, which ranges from 1 to 65535
and defaults to 3.
-w timeout: Specifies the timeout time of the reply packet of a probe packet, which ranges from 1 to
65535 milliseconds and defaults to 5000 milliseconds.
host: IPv6 address or host name of the destination, which is a string of 1 to 46 characters.
-tos tos: Specifies the ToS value of a tracert IPv6 packet, which ranges from 0 to 255 and defaults to 0.
Starting from 0, every four consecutive ToS values map to a DSCP value. The network device uses the
DSCP value as a reference to determine the packet priority for transmission. This option is available in
S7500E Release 6703, S7508E-X Release 6903, and their later versions.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN to which the destination belongs, where
vpn-instance-name is a case-sensitive string of 1 to 31 characters. If the destination is on the public
network, do not specify this option.