HPE FlexNetwork 10500 SERIES Installation manual

HPE FlexNetwork 10500 Switch Series
Network Management and Monitoring
Command Reference
P
art number: 5200-1903
Software
version: 10500-CMW710-R7524
Document version: 6W100-20161230

© Copyright 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license fromHewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® andAcrobat® are trademarks ofAdobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

i
Contents
Ping, tracert, and system debugging commands············································1
debugging ··················································································································································1
display debugging······································································································································1
ping ····························································································································································2
ping ipv6·····················································································································································5
tracert·························································································································································7
tracert ipv6 ·················································································································································9
NQA commands····························································································12
NQA client commands ·····································································································································12
advantage-factor······································································································································12
codec-type················································································································································12
community read········································································································································13
data-fill······················································································································································14
data-size···················································································································································15
description················································································································································16
destination host········································································································································17
destination ip············································································································································17
destination ipv6········································································································································18
destination port·········································································································································19
display nqa history ···································································································································20
display nqa reaction counters ··················································································································21
display nqa result·····································································································································23
display nqa statistics································································································································30
expect data···············································································································································39
expect ip···················································································································································40
expect ipv6···············································································································································41
expect status············································································································································41
filename····················································································································································42
frequency ·················································································································································43
history-record enable ·······························································································································44
history-record keep-time ··························································································································44
history-record number······························································································································45
init-ttl·························································································································································46
key····························································································································································46
lsr-path·····················································································································································47
max-failure ···············································································································································48
mode························································································································································48
next-hop ip ···············································································································································49
next-hop ipv6············································································································································50
no-fragment enable··································································································································50
nqa···························································································································································51
nqa agent enable ·····································································································································52
nqa schedule············································································································································52
nqa template ············································································································································53
operation (FTP operation view)················································································································54
operation (HTTP/HTTPS operation view) ································································································55
out interface ·············································································································································56
password··················································································································································57
probe count··············································································································································58
probe packet-interval································································································································59
probe packet-number·······························································································································59
probe packet-timeout ·······························································································································60
probe timeout···········································································································································61
raw-request··············································································································································62
reaction checked-element { jitter-ds | jitter-sd }························································································62
reaction checked-element { owd-ds | owd-sd } ························································································64

ii
reaction checked-element icpif·················································································································65
reaction checked-element mos················································································································66
reaction checked-element packet-loss·····································································································67
reaction checked-element probe-duration································································································68
reaction checked-element probe-fail (for trap)·························································································69
reaction checked-element probe-fail (for trigger)·····················································································71
reaction checked-element rtt····················································································································71
reaction trap·············································································································································73
reaction trigger per-probe·························································································································74
reaction trigger probe-fail·························································································································75
reaction trigger probe-pass······················································································································75
resolve-target···········································································································································76
resolve-type··············································································································································77
route-option bypass-route························································································································77
source interface (ICMP echo/UDP tracert operation view) ······································································78
source ip···················································································································································79
source ipv6···············································································································································80
source port···············································································································································81
ssl-client-policy·········································································································································82
statistics hold-time····································································································································82
statistics interval·······································································································································83
statistics max-group·································································································································84
target-only················································································································································84
tos ····························································································································································85
ttl ······························································································································································86
type ··························································································································································86
url·····························································································································································87
username·················································································································································88
version······················································································································································89
vpn-instance·············································································································································90
NQA server commands····································································································································91
display nqa server····································································································································91
nqa server enable ····································································································································92
nqa server tcp-connect·····························································································································92
nqa server udp-echo································································································································93
NTP commands····························································································95
display ntp-service ipv6 sessions·············································································································95
display ntp-service sessions ··················································································································100
display ntp-service status·······················································································································104
display ntp-service trace ························································································································106
ntp-service acl········································································································································108
ntp-service authentication enable ··········································································································109
ntp-service authentication-keyid·············································································································109
ntp-service broadcast-client···················································································································111
ntp-service broadcast-server··················································································································111
ntp-service dscp·····································································································································112
ntp-service enable··································································································································113
ntp-service inbound enable····················································································································113
ntp-service ipv6 acl ································································································································114
ntp-service ipv6 dscp ·····························································································································115
ntp-service ipv6 inbound enable ············································································································115
ntp-service ipv6 multicast-client·············································································································116
ntp-service ipv6 multicast-server············································································································117
ntp-service ipv6 source··························································································································118
ntp-service ipv6 unicast-peer·················································································································119
ntp-service ipv6 unicast-server ··············································································································120
ntp-service max-dynamic-sessions········································································································121
ntp-service multicast-client·····················································································································122
ntp-service multicast-server···················································································································123
ntp-service refclock-master····················································································································124
ntp-service reliable authentication-keyid································································································125

iii
ntp-service source··································································································································126
ntp-service unicast-peer·························································································································127
ntp-service unicast-server······················································································································128
SNTP commands························································································130
display sntp ipv6 sessions······················································································································130
display sntp sessions·····························································································································130
sntp authentication enable·····················································································································131
sntp authentication-keyid ·······················································································································132
sntp enable·············································································································································133
sntp ipv6 unicast-server·························································································································133
sntp reliable authentication-keyid···········································································································135
sntp unicast-server·································································································································135
SNMP commands·······················································································138
display snmp-agent community··············································································································138
display snmp-agent context ···················································································································140
display snmp-agent group······················································································································140
display snmp-agent local-engineid·········································································································141
display snmp-agent mib-node················································································································142
display snmp-agent mib-view·················································································································146
display snmp-agent remote····················································································································147
display snmp-agent statistics·················································································································148
display snmp-agent sys-info···················································································································150
display snmp-agent trap queue··············································································································151
display snmp-agent trap-list···················································································································151
display snmp-agent usm-user················································································································152
enable snmp trap updown······················································································································154
snmp-agent············································································································································155
snmp-agent { inform | trap } source········································································································155
snmp-agent calculate-password ············································································································156
snmp-agent community··························································································································158
snmp-agent community-map··················································································································160
snmp-agent context································································································································161
snmp-agent group··································································································································162
snmp-agent local-engineid·····················································································································164
snmp-agent log ······································································································································165
snmp-agent mib-view·····························································································································166
snmp-agent packet max-size·················································································································167
snmp-agent port·····································································································································168
snmp-agent remote································································································································168
snmp-agent sys-info contact··················································································································169
snmp-agent sys-info location ·················································································································170
snmp-agent sys-info version··················································································································170
snmp-agent target-host··························································································································171
snmp-agent trap enable·························································································································173
snmp-agent trap if-mib link extended·····································································································174
snmp-agent trap life ·······························································································································175
snmp-agent trap log·······························································································································175
snmp-agent trap queue-size ··················································································································176
snmp-agent usm-user { v1 | v2c } ··········································································································177
snmp-agent usm-user v3 ·······················································································································179
snmp-agent usm-user v3 user-role········································································································183
RMON commands ······················································································184
display rmon alarm·································································································································184
display rmon event·································································································································185
display rmon eventlog····························································································································186
display rmon history·······························································································································188
display rmon prialarm·····························································································································190
display rmon statistics····························································································································191
rmon alarm·············································································································································193

iv
rmon event·············································································································································195
rmon history ···········································································································································196
rmon prialarm·········································································································································197
rmon statistics········································································································································199
NETCONF commands················································································201
netconf idle-timeout································································································································201
netconf log··············································································································································202
netconf soap domain······························································································································203
netconf soap http acl······························································································································203
netconf soap http dscp···························································································································204
netconf soap http enable························································································································205
netconf soap https acl····························································································································205
netconf soap https dscp·························································································································206
netconf soap https enable······················································································································207
netconf ssh server enable······················································································································207
netconf ssh server port···························································································································208
xml··························································································································································208
EAA commands··························································································211
action cli·················································································································································211
action reboot ··········································································································································212
action switchover····································································································································213
action syslog ··········································································································································214
commit····················································································································································214
display rtm environment·························································································································215
display rtm policy····································································································································216
event cli··················································································································································218
event hotplug··········································································································································219
event interface········································································································································220
event process·········································································································································222
event snmp oid·······································································································································223
event snmp-notification··························································································································224
event syslog···········································································································································225
event track··············································································································································226
rtm cli-policy···········································································································································227
rtm environment·····································································································································228
rtm event syslog buffer-size···················································································································230
rtm scheduler suspend···························································································································230
rtm tcl-policy···········································································································································231
running-time···········································································································································232
user-role·················································································································································232
Process monitoring and maintenance commands······································234
display exception context·······················································································································234
display exception filepath·······················································································································238
display kernel deadloop ·························································································································239
display kernel deadloop configuration····································································································242
display kernel exception·························································································································244
display kernel reboot······························································································································247
display kernel starvation·························································································································250
display kernel starvation configuration···································································································253
display process ······································································································································254
display process cpu································································································································257
display process log·································································································································258
display process memory ························································································································259
display process memory heap ···············································································································260
display process memory heap address··································································································262
display process memory heap size········································································································263
exception filepath···································································································································264
monitor kernel deadloop action··············································································································265
monitor kernel deadloop enable·············································································································266

v
monitor kernel deadloop exclude-thread································································································267
monitor kernel deadloop time·················································································································268
monitor kernel starvation enable············································································································269
monitor kernel starvation exclude-thread·······························································································270
monitor kernel starvation time················································································································271
monitor process······································································································································272
monitor thread········································································································································277
process core···········································································································································281
reset exception context··························································································································282
reset kernel deadloop·····························································································································282
reset kernel exception····························································································································283
reset kernel reboot·································································································································284
reset kernel starvation····························································································································284
Sampler commands····················································································286
display sampler······································································································································286
sampler ··················································································································································287
Port mirroring commands············································································288
display mirroring-group ··························································································································288
mirroring-group·······································································································································289
mirroring-group mirroring-cpu ················································································································289
mirroring-group mirroring-port (interface view)·······················································································291
mirroring-group mirroring-port (system view)·························································································292
mirroring-group monitor-egress··············································································································293
mirroring-group monitor-port (interface view)·························································································294
mirroring-group monitor-port (system view)···························································································295
mirroring-group reflector-port·················································································································296
mirroring-group remote-probe vlan ········································································································297
Flow mirroring commands···········································································299
mirror-to cpu···········································································································································299
mirror-to interface···································································································································299
NetStream configuration commands···························································301
display ip netstream cache·····················································································································301
display ip netstream export····················································································································305
display ip netstream template ················································································································307
enable ····················································································································································309
ip netstream ···········································································································································310
ip netstream aggregation ·······················································································································310
ip netstream aggregation advanced·······································································································312
ip netstream export host·························································································································313
ip netstream export rate·························································································································314
ip netstream export source·····················································································································315
ip netstream export template refresh-rate······························································································315
ip netstream export version····················································································································316
ip netstream filter····································································································································317
ip netstream sampler······························································································································318
ip netstream timeout active····················································································································319
ip netstream timeout inactive ·················································································································319
reset ip netstream statistics····················································································································320
IPv6 NetStream commands········································································321
display ipv6 netstream cache·················································································································321
display ipv6 netstream export ················································································································324
display ipv6 netstream template·············································································································325
enable ····················································································································································328
ipv6 netstream········································································································································328
ipv6 netstream aggregation····················································································································329
ipv6 netstream aggregation advanced···································································································330
ipv6 netstream export host·····················································································································331

vi
ipv6 netstream export rate ·····················································································································332
ipv6 netstream export source·················································································································332
ipv6 netstream export template refresh-rate··························································································333
ipv6 netstream export version················································································································334
ipv6 netstream filter································································································································335
ipv6 netstream sampler··························································································································336
ipv6 netstream timeout active ················································································································336
ipv6 netstream timeout inactive··············································································································337
reset ipv6 netstream statistics················································································································338
sFlow commands························································································339
display sflow···········································································································································339
sflow agent·············································································································································340
sflow collector·········································································································································341
sflow counter collector····························································································································342
sflow counter interval ·····························································································································342
sflow flow collector·································································································································343
sflow flow max-header ···························································································································344
sflow sampling-mode ·····························································································································344
sflow sampling-rate································································································································345
sflow source···········································································································································346
Information center commands ····································································347
diagnostic-logfile save····························································································································347
display diagnostic-logfile summary ········································································································347
display info-center··································································································································348
display logbuffer·····································································································································349
display logbuffer summary·····················································································································351
display logfile summary··························································································································352
display security-logfile summary············································································································352
enable log updown·································································································································353
info-center diagnostic-logfile directory····································································································354
info-center diagnostic-logfile enable·······································································································354
info-center diagnostic-logfile frequency··································································································355
info-center diagnostic-logfile quota ········································································································355
info-center enable ··································································································································356
info-center format···································································································································356
info-center logbuffer·······························································································································357
info-center logbuffer size························································································································358
info-center logfile directory·····················································································································358
info-center logfile enable························································································································359
info-center logfile frequency···················································································································360
info-center logfile overwrite-protection···································································································360
info-center logfile size-quota··················································································································361
info-center logging suppress duplicates·································································································361
info-center logging suppress module·····································································································363
info-center loghost··································································································································364
info-center loghost source······················································································································365
info-center security-logfile alarm-threshold····························································································365
info-center security-logfile directory ·······································································································366
info-center security-logfile enable ··········································································································367
info-center security-logfile frequency ·····································································································367
info-center security-logfile size-quota·····································································································368
info-center source ··································································································································368
info-center synchronous·························································································································370
info-center syslog min-age·····················································································································371
info-center timestamp·····························································································································372
info-center timestamp loghost················································································································372
info-center trace-logfile quota·················································································································373
logfile save·············································································································································374
reset logbuffer········································································································································374
security-logfile save································································································································375

vii
terminal debugging·································································································································375
terminal logging level ·····························································································································376
terminal monitor ·····································································································································377
GOLD commands·······················································································378
diagnostic event-log size························································································································378
diagnostic monitor enable······················································································································378
diagnostic monitor interval ·····················································································································379
diagnostic ondemand failure··················································································································380
diagnostic ondemand repeating·············································································································381
diagnostic ondemand start·····················································································································382
diagnostic ondemand stop·····················································································································383
diagnostic simulation······························································································································384
display diagnostic content······················································································································385
display diagnostic event-log···················································································································388
display diagnostic ondemand configuration···························································································388
display diagnostic result·························································································································389
display diagnostic result statistics··········································································································391
display diagnostic simulation··················································································································393
reset diagnostic event-log······················································································································393
reset diagnostic result····························································································································394
Packet capture commands ·········································································395
packet-capture interface·························································································································395
packet-capture read·······························································································································397
VCF fabric commands ················································································399
display vcf-fabric topology······················································································································399
display vcf-fabric underlay autoconfigure·······························································································400
vcf-fabric role··········································································································································401
vcf-fabric spine-role master····················································································································402
vcf-fabric topology enable······················································································································403
vcf-fabric underlay autoconfigure···········································································································403
vcf-fabric underlay pause·······················································································································404
Document conventions and icons·······························································405
Conventions···················································································································································405
Network topology icons··································································································································406
Support and other resources ······································································407
Accessing Hewlett Packard Enterprise Support ····························································································407
Accessing updates·········································································································································407
Websites ················································································································································408
Customer self repair·······························································································································408
Remote support······································································································································408
Documentation feedback ·······················································································································408
Index···········································································································410

1
Ping, tracert, and system debugging
commands
debugging
Use debugging to enable debugging for a module.
Use undo debugging to disable debugging for a module or for all modules.
Syntax
debugging module-name [ option ]
undo debugging { all | module-name [ option ] }
Default
Debugging is disabled for all modules.
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
module-name: Specifies a module by its name, such as arp or device. For a list of supported
modules, use the debugging ? command.
option: Specifies the debugging option for a module. Available options vary by module. To display the
debugging options supported by a module, use the debugging module-name ?command.
all: Specifies all modules.
Usage guidelines
Output from debugging commands is memory intensive. To guarantee system performance, enable
debugging only for modules that are in an exceptional condition.
The system sends generated debug messages to the device information center, which then sends
the messages to appropriate destinations based on the log output configuration. For more
information about the information center, see Network Management and Monitoring Configuration
Guide.
Examples
# Enable debugging for the device management module.
<Sysname> debugging dev
Related commands
display debugging
display debugging
Use display debugging to display the enabled debugging features for a module or for all modules.

2
Syntax
display debugging [ module-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
module-name: Specifies a module by its name. For a list of supported modules, use the display
debugging ? command. If you do not specify a module name, this command displays the enabled
debugging features for all modules.
Examples
# Display all enabled debugging features.
<Sysname> display debugging
DEV debugging switch is on
Related commands
debugging
ping
Use ping to test the reachability of the destination IP address and display ping 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
Predefined user roles
network-admin
mdc-admin
Parameters
ip: Distinguishes between a destination host name and the ping command keywords if the name of
the destination host is i, ip, ipv, ipv6, l, ls, or lsp. For example, you must use the command in the
form of ping ip ip instead of ping ip if the destination host name is ip.
-a source-ip: Specifies an IP address of the device as the source IP address of ICMP echo requests.
If this option is not specified, the source IP address of ICMPecho requests is the primary IP address
of the outbound interface.
-c count: Specifies the number of ICMP echo requests that are sent to the destination. The value
range is 1 to 4294967295, and the default is 5.
-f: Sets the "do-not-fragment" bit in the IP header.
-h ttl: Specifies the TTLvalue of ICMP echo requests. The value range is 1 to 255, and the default is
255.

3
-i interface-type interface-number: Specifies the source interface for ICMP echo requests. If you do
not specify this option, the system uses the primary IP address of the matching route's egress
interface as the source interface for ICMP echo requests.
-m interval: Specifies the interval (in milliseconds) to send ICMP echo requests. The value range is 1
to 65535, and the default is 200.
-n: Disables domain name resolution for the host argument. If the host argument represents the host
name of the destination, and if this keyword is not specified, the device translates host into an
address.
-p pad: Specifies the value of the pad field in an ICMP echo request, in hexadecimal format, 1 to 8
bits. The pad argument is in the range of 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 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, such as 0x010203…feff01….
-q: Displays only the summary statistics. If this keyword is not specified, the system displays all the
ping statistics.
-r: Records the addresses of the hops (up to 9) the ICMP echo requests passed. If this keyword is
not specified, the addresses of the hops that the ICMP echo requests passed are not recorded.
-s packet-size: Specifies the length (in bytes) of ICMP echo requests (excluding the IP packet
header and the ICMP packet header). The value range is 20 to 8100, and the default is 56.
-t timeout: Specifies the timeout time (in milliseconds) of an ICMP echo reply. The value range is 0 to
65535, and the default is 2000. If the source does not receive an ICMP echo replywithin the timeout,
it considers the ICMP echo reply timed out.
-tos tos: Specifies the ToS value of ICMP echo requests. The value range is 0 to 255, and the default
is 0.
-v: Displays non-ICMP echo reply packets. If this keyword is not specified, the system does not
display non-ICMP echo reply packets.
-vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the destination
belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive
string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
host: Specifies the IP address or host name of the destination. The host name is a case-insensitive
string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-),
underscore (_), and dot (.).
Usage guidelines
To ping a device identified by its host name,configure the DNS settings on the device first.If the DNS
settings are not configured, the ping operation fails.
To abort the ping operation during the execution of the command, press Ctrl+C.
Examples
# Test 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 (1.1.2.2): 56 data bytes, press CTRL_C to break
56 bytes from 1.1.2.2: icmp_seq=0 ttl=254 time=2.137 ms
56 bytes from 1.1.2.2: icmp_seq=1 ttl=254 time=2.051 ms
56 bytes from 1.1.2.2: icmp_seq=2 ttl=254 time=1.996 ms
56 bytes from 1.1.2.2: icmp_seq=3 ttl=254 time=1.963 ms
56 bytes from 1.1.2.2: icmp_seq=4 ttl=254 time=1.991 ms
--- Ping statistics for 1.1.2.2 ---

4
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.963/2.028/2.137/0.062 ms
# Test whether the device with an IP address of 1.1.2.2 in VPN instance vpn1 is reachable.
<Sysname> ping -vpn-instance vpn1 1.1.2.2
Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break
56 bytes from 1.1.2.2: icmp_seq=0 ttl=254 time=2.137 ms
56 bytes from 1.1.2.2: icmp_seq=1 ttl=254 time=2.051 ms
56 bytes from 1.1.2.2: icmp_seq=2 ttl=254 time=1.996 ms
56 bytes from 1.1.2.2: icmp_seq=3 ttl=254 time=1.963 ms
56 bytes from 1.1.2.2: icmp_seq=4 ttl=254 time=1.991 ms
--- Ping statistics for 1.1.2.2 in VPN instance vpn1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.963/2.028/2.137/0.062 ms
# Test whether the device with an IP address of 1.1.2.2 is reachable. Only results are displayed.
<Sysname> ping -q 1.1.2.2
Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break
--- Ping statistics for 1.1.2.2 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.962/2.196/2.665/0.244 ms
# Test whether the device with an IP address of 1.1.2.2 is reachable. The IP addresses of the hops
that the ICMP packets passed in the path are displayed.
<Sysname> ping -r 1.1.2.2
Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break
56 bytes from 1.1.2.2: icmp_seq=0 ttl=254 time=4.685 ms
RR: 1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
56 bytes from 1.1.2.2: icmp_seq=1 ttl=254 time=4.834 ms (same route)
56 bytes from 1.1.2.2: icmp_seq=2 ttl=254 time=4.770 ms (same route)
56 bytes from 1.1.2.2: icmp_seq=3 ttl=254 time=4.812 ms (same route)
56 bytes from 1.1.2.2: icmp_seq=4 ttl=254 time=4.704 ms (same route)
--- Ping statistics for 1.1.2.2 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 4.685/4.761/4.834/0.058 ms
The output shows the following information:
•The destination is reachable.
•The route is 1.1.1.1 <-> {1.1.1.2; 1.1.2.1} <-> 1.1.2.2.
Table 1 Command output
Field
Description
Ping 1.1.2.2 (1.1.2.2): 56 data
bytes, press CTRL_C to break
Test whether the device with IP address 1.1.2.2 is reachable. There
are 56 bytes in each ICMP echo request. Press Ctrl+C to abort the
ping operation.

5
Field
Description
56 bytes from 1.1.2.2: icmp_seq=0
ttl=254 time=4.685 ms
Received ICMP echo replies from the device whose IP address is
1.1.2.2. If no echo reply is received within the timeout period, no
information is displayed.
•bytes—Number of bytes in the ICMP echo reply.
•icmp_seq—Packet sequence, used to determine whether a
segment is lost, disordered or repeated.
•ttl—TTL value in the ICMP echo reply.
•time—Response time.
RR: Routers through which the ICMP echo request passed. They are displayed in inversed order, which means the router with a smaller
distance to the destination is displayed first.
--- Ping statistics for 1.1.2.2 --- Statistics on data received and sent in the ping operation.
--- Ping statistics for 1.1.2.2 in VPN
instance vpn1 --- Ping statistics for a device in a VPN instance.
5 packet(s) transmitted Number of ICMP echo requests sent.
5 packet(s) received Number of ICMP echo replies received.
0.0% packet loss Percentage of unacknowledged packets to the total packets sent.
round-trip min/avg/max/std-dev =
4.685/4.761/4.834/0.058 ms Minimum/average/maximum/standard deviation response time, in milliseconds.
ping ipv6
Use ping ipv6 to test the reachability of the destination IPv6 address and displayIPv6 ping statistics.
Syntax
ping ipv6 [ -a source-ipv6 | -c count | -i interface-type interface-number | -m interval | -q | -s
packet-size | -t timeout | -tc traffic-class | -v | -vpn-instance vpn-instance-name ] * host
Views
Any view
Predefined user roles
network-admin
mdc-admin
Parameters
-a source-ipv6: Specifies an IPv6 address of the device as the source IP address of ICMP echo
requests. If this option is not specified, the source IPv6 address of ICMP echo requests is the IPv6
address of the outbound interface. See RFC 3484 for information about the address selection rule.
-c count: Specifies the number of ICMPv6 echo requests that are sent to the destination. The value
range is 1 to 4294967295, and the default is 5.
-i interface-type interface-number: Specifies the source interface for ICMPv6 echo requests. This
option must be specified when the destination address is a multicast address or a link local address.
If you do not specify this option, the system uses the primary IP address of the matching route's
egress interface as the source interface for ICMPv6 echo requests.
-m interval: Specifies the interval (in milliseconds) to send an ICMPv6 echo reply. The value range is
1 to 65535, and the default is 1000.
-q: Displays only the summary statistics. If you do not specify this keyword, the system displays all
the ping statistics.

6
-s packet-size: Specifies the length (in bytes) of ICMPv6 echo requests (excluding the IPv6 packet
header and the ICMPv6 packet header). The value range is 20 to 8100, and the default is 56.
-t timeout: Specifies the timeout time (in milliseconds) of an ICMPv6 echo reply. The value range is 0
to 65535, and the default is 2000.
-tc traffic-class: Specifies the traffic class value in an ICMPv6 packet. The value range is 0 to 255
and the default is 0.
-v: Displays detailed information (including the dst field and the idx field) about ICMPv6 echo replies.
If this keyword is not specified, the system only displays brief information (not including the dst field
and the idx field) about ICMPv6 echo replies.
-vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the destination
belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive
string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
host: Specifies the IPv6 address or host name of the destination. The host name is a
case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters
such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
To ping a device identified by its host name,configure the DNS settings on the device first. If the DNS
settings are not configured, the ping ipv6 operation fails.
To abort the ping ipv6 operation during the execution of the command, press Ctrl+C.
Examples
# Test whether the IPv6 address (2001::2) is reachable.
<Sysname> ping ipv6 2001::2
Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C to break
56 bytes from 2001::2, icmp_seq=0 hlim=64 time=62.000 ms
56 bytes from 2001::2, icmp_seq=1 hlim=64 time=23.000 ms
56 bytes from 2001::2, icmp_seq=2 hlim=64 time=20.000 ms
56 bytes from 2001::2, icmp_seq=3 hlim=64 time=4.000 ms
56 bytes from 2001::2, icmp_seq=4 hlim=64 time=16.000 ms
--- Ping6 statistics for 2001::2 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 4.000/25.000/62.000/20.000 ms
# Test whether the IPv6 address (2001::2) is reachable. Only the statistics are displayed.
<Sysname> ping ipv6 –q 2001::2
Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C to break
--- Ping6 statistics for 2001::2 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 4.000/25.000/62.000/20.000 ms
# Test whether the IPv6 address (2001::2) is reachable. Detailed ping information is displayed.
<Sysname> ping ipv6 –v 2001::2
Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C to break
56 bytes from 2001::2, icmp_seq=0 hlim=64 dst=2001::1 idx=3 time=62.000 ms
56 bytes from 2001::2, icmp_seq=1 hlim=64 dst=2001::1 idx=3 time=23.000 ms
56 bytes from 2001::2, icmp_seq=2 hlim=64 dst=2001::1 idx=3 time=20.000 ms
56 bytes from 2001::2, icmp_seq=3 hlim=64 dst=2001::1 idx=3 time=4.000 ms
56 bytes from 2001::2, icmp_seq=4 hlim=64 dst=2001::1 idx=3 time=16.000 ms

7
--- Ping6 statistics for 2001::2 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 4.000/25.000/62.000/20.000 ms
Table 2 Command output
Field
Description
Ping6(56 data bytes)
2001::1 --> 2001::2, press CTRL_C
to break
An ICMPv6 echo reply with a data length of 56 bytes is sent from
2001::1 to 2001::2.
Press Ctrl+C to abort the ping IPv6 operation.
56 bytes from 2001::2,
icmp_seq=1 hlim=64 dst=2001::1
idx=3 time=62.000 ms
Received ICMPv6 echo replies from the device whose IPv6 address
is 2001::2.
•The number of data bytes is 56.
•The packet sequence is 1.
•The hop limit value is 64.
•The destination address is 2001::1. Specify the -v keyword to
display this field.
•The index for the packet inbound interface is 3. Specify the -v
keyword to display this field.
•The response time is 62 milliseconds.
--- Ping6 statistics for 2001::2 ------ Statistics on data received and sent in an IPv6 ping operation.
5 packet(s) transmitted Number of ICMPv6 echo requests sent.
5 packet(s) received Number of ICMPv6 echo replies received.
0.0% packet loss Percentage of unacknowledged packets to the total packets sent.
round-trip min/avg/max/ std-dev
=4.000/25.000/62.000/20.000 ms Minimum/average/maximum/standard deviation response time, in milliseconds.
tracert
Use tracert to trace the path that the packets traverse from source to destination.
Syntax
tracert [ -a source-ip | -f first-ttl |-m max-ttl | -p port | -q packet-number | -t tos | -vpn-instance
vpn-instance-name [ -resolve-as { global | none | vpn } ] | -w timeout ] * host
Views
Any view
Predefined user roles
network-admin
mdc-admin
Parameters
-a source-ip: Specifies an IP address of the device as the source IP address of probe packets. If this
option is not specified, the source IP address of probe packets is the primary IP address of the
outbound interface.
-f first-ttl: Specifies the TTLof the first packet sent to the destination. The value range is 1 to 255, and
the default is 1. It must be no greater than the value of the max-ttl argument.
-m max-ttl: Specifies the maximum number of hops allowed for a probe packet. The value range is 1
to 255, and the default is 30. It must be no smaller than the value of the first-ttl argument.

8
-p port: Specifies an invalid UDP port of the destination. The value range is 1 to 65535, and the
default is 33434. If the destination address is an EID address at a remote LISP site, specify a port
number in the range of 33434 to 65535.
-q packet-number: Specifies the number of probe packets to send per hop. The value range is 1 to
65535, and the default is 3.
-t tos: Specifies the ToS value of probe packets. The value range is 0 to 255, and the default is 0.
-vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the destination
belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive
string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-resolve-as: Specifies a routing table for autonomous system (AS) resolution. Tracert searches the
specified routing table for the AS that each hop along the path belongs to. If you do not specify this
keyword, the global routing table is used. If the AS information is found, this command displays the
AS number next to the address of the hop in the probe result.
•global: Specifies the global routing table.
•none: Disables AS resolution.
•vpn: Specifies the VPN routing table.
-w timeout: Specifies the timeout time in milliseconds of the reply packet for a probe packet. The
value range is 1 to 65535, and the default is 5000.
host: Specifies the IP address or host name of the destination. The host name is a case-insensitive
string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-),
underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping command, use the tracert command to locate failed
nodes.
If the destination address is on the public network, you do not need to specify the -resolve-as
keyword to obtain the AS information. The device automatically uses the global routing table for AS
resolution.
If the destination address is on a private network, address information of intermediate hops might be
stored in either the global routing table or the VPN routing table. To learn the AS path that the
packets traverse, execute the tracert command twice, once with the -resolve-as global keywords
and again with the -resolve-as vpn keywords.
The output from the tracert command includes IP addresses of all the Layer 3 devices that the
packets traverse from source to destination.Asterisks (* * *) are displayed if the device cannot reply
with an ICMP error message. The reason might be 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 that the packets traverse from source to destination (1.1.2.2).
<Sysname> tracert 1.1.2.2
traceroute to 1.1.2.2 (1.1.2.2), 30 hops at most, 40 bytes each packet, press CTRL_C to
break
1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms
2 1.1.2.2 (1.1.2.2) [AS 100] 580 ms 470 ms 80 ms
# Display the path that the packets traverse from source to destination (1.1.3.2) in VPN instance
vpn1, as well as theAS information of the hops along the path.
<Sysname> tracert –vpn-instance vpn1 –resolve-as vpn 1.1.3.2
traceroute to 1.1.3.2 (1.1.3.2), 30 hops at most, 40 bytes each packet, press CTRL_C to
break

9
1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms
2 1.1.2.2 (1.1.2.2) 580 ms 470 ms 80 ms
3 1.1.3.2 (1.1.3.2) [AS 65535] 530 ms 472 ms 380 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 at most, 40 bytes each 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 3 Command output
Field
Description
traceroute to 1.1.2.2 (1.1.2.2) Display the route that the IP packets traverse from the current device to the
device whose IP address is 1.1.2.2.
hops at most Maximum number of hops of the probe packets, which can be set by the -m
keyword.
bytes each packet Number of bytes of a probe packet.
press CTRL_C to break During the execution of the command, press Ctrl+C to abort the tracert
operation.
2 1.1.2.2 (1.1.2.2) [AS 100]
580 ms 470 ms 80 ms
Probe result of the probe packets that contain a TTL value of 2, including
the following information about the second hop:
•Domain name of the hop. If no domain name is configured, the IP
address is displayed as the domain name.
•IP address of the hop. The IP address is displayed in parentheses.
•Number of the AS that the hop belongs to. The AS number appears
only when it is found for the hop in the specified routing table.
•The round-trip time of the probe packets.
The number of packets that can be sent in each probe can be set by using
the -q keyword.
MPLS Label=100048 Exp=0
TTL=1 S=1
ICMP timeout packets on an MPLS network, carrying 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 in another label stack.
tracert ipv6
Use tracert ipv6 to display the path that the IPv6 packets traverse from source to destination.
Syntax
tracert ipv6 [ -f first-hop | -m max-hops | -p port | -q packet-number | -t traffic-class | -vpn-instance
vpn-instance-name [ -resolve-as { global | none | vpn } ] | -w timeout ] * host

10
Views
Any view
Predefined user roles
network-admin
mdc-admin
Parameters
-f first-hop: Specifies the TTL value of the first packet. The value range is 1 to 255, and the default is
1. The value must be no greater than the value of the max-hops argument.
-m max-hops: Specifies the maximum number of hops allowed for a packet. The value range is 1 to
255, and the default is 30. The value must be no smaller than the value of the first-hop argument.
-p port: Specifies an invalid UDP port of the destination. The value range is 1 to 65535, and the
default is 33434.
-q packet-number: Specifies the number of probe packets sent each time. The value range is 1 to
65535, and the default is 3.
-t traffic-class: Specifies the traffic class value in an IPv6 probe packet. The value range is 0 to 255,
and the default is 0.
-vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the destination
belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive
string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-resolve-as: Specifies a routing table forAS resolution. Tracert searches the specified routing table
for the AS that each hop along the path belongs to. If you do not specify this keyword, the global
routing table is used. If the AS information is found, this command displays the AS number next to
the address of the hop in the probe result.
•global: Specifies the global routing table.
•none: Disables AS resolution.
•vpn: Specifies the VPN routing table.
-w timeout: Specifies the timeout time (in milliseconds) of the reply packet of a probe packet. The
value range is 1 to 65535, and the default is 5000.
host: Specifies the IPv6 address or host name of the destination. The host name is a
case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters
such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping ipv6 command, you can use the tracert ipv6
command to locate failed nodes.
If the destination address is on the public network, you do not need to specify the -resolve-as
keyword to obtain the AS information. The device automatically uses the global routing table for AS
resolution.
If the destination address is on a private network, address information of intermediate hops might be
stored in either the global routing table or the VPN routing table. To learn the AS path that the
packets traverse, execute the tracert ipv6 command twice, once with the -resolve-as global
keywords and again with the -resolve-as vpn keywords.
The output from the tracert ipv6 command includes IPv6 addresses of all the Layer 3 devices that
the packets traverse from source to destination. Asterisks (* * *) are displayed if the device cannot
reply with an ICMP error message. The reason might be 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.

11
Examples
# Display the path that the packets traverse from source to destination (2001:3::2).
<Sysname> tracert ipv6 2001:3::2
traceroute to 2001:3::2(2001:3::2), 30 hops at most, 60 byte packets, press CTRL_C to break
1 2001:1::20.661 ms 0.618 ms 0.579 ms
2 2001:2::2 [AS 100] 0.861 ms 0.718 ms 0.679 ms
3 2001:3::2 [AS 200] 0.822 ms 0.731 ms 0.708 ms
# Display the path that the packets traverse from source to destination (2001:3::2) in VPN instance
vpn1, as well as theAS information of the hops along the path.
<Sysname> tracert ipv6 –vpn-instance vpn1 –resolve-as vpn 2001:3::2
traceroute to 2001:3::2(2001:3::2), 30 hops at most, 60 byte packets , press CTRL_C to
break
1 2001:1::2 0.661 ms 0.618 ms 0.579 ms
2 2001:2::2 0.861 ms 0.718 ms 0.679 ms
3 2001:3::2 [AS 65535] 0.822 ms 0.731 ms 0.708 ms
Table 4 Command output
Field
Description
traceroute to 2001:3::2 Display the route that the IPv6 packets traverse from the current device
to the device whose IP address is 2001:3:2.
hops at most Maximum number of hops of the probe packets, which can be set by the
-m
keyword.
byte packets Number of bytes of a probe packet.
2 2001:2::2 [AS 100] 0.861 ms
0.718 ms 0.679 ms
Probe result of the probe packets that contain a hoplimit value of 2,
including the following information about the second hop:
•IPv6 address of the hop.
•Number of the AS the hop belongs to. The AS number appears
only when it is found for the hop in the specified routing table.
•The round-trip time of the probe packets.
The number of packets that can be sent in each probe can be set by
using the
-q
keyword.