HPE FlexNetwork MSR3012 Installation manual

HPE FlexNetwork MSR Router Series
Comware 7 Network Management and Monitoring
Command Reference
Part number: 5200-2374
Software version: MSR-CMW710-R0411
Document version: 6W101-20161114

© 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 from Hewlett 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® and Acrobat® are trademarks of Adobe 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························································································································· 10
NQA commands ············································································12
NQA client commands ················································································································ 12
advantage-factor················································································································· 12
codec-type························································································································· 12
data-fill······························································································································ 13
data-size···························································································································· 14
description ························································································································· 15
destination ip······················································································································ 16
destination ipv6··················································································································· 16
destination port··················································································································· 17
display nqa history··············································································································· 17
display nqa reaction counters ································································································ 19
display nqa result ················································································································ 21
display nqa statistics············································································································ 28
filename ···························································································································· 36
frequency··························································································································· 37
history-record enable ··········································································································· 38
history-record keep-time······································································································· 38
history-record number·········································································································· 39
init-ttl································································································································· 40
lsr-path······························································································································ 40
max-failure························································································································· 41
mode ································································································································ 42
next-hop ip························································································································· 42
next-hop ipv6······················································································································ 43
no-fragment enable ············································································································· 43
nqa··································································································································· 44
nqa agent enable ················································································································ 45
nqa schedule······················································································································ 45
operation (FTP operation view)······························································································ 46
operation (HTTP operation view)···························································································· 47
out interface······················································································································· 48
password··························································································································· 49
probe count························································································································ 49
probe packet-interval ··········································································································· 51
probe packet-number··········································································································· 51
probe packet-timeout ··········································································································· 52
probe timeout ····················································································································· 53
raw-request························································································································ 53
reaction checked-element { jitter-ds | jitter-sd }·········································································· 54
reaction checked-element { owd-ds | owd-sd } ·········································································· 55
reaction checked-element icpif······························································································· 56
reaction checked-element mos ······························································································ 57
reaction checked-element packet-loss····················································································· 58
reaction checked-element probe-duration ················································································ 59
reaction checked-element probe-fail (for trap)··········································································· 61
reaction checked-element probe-fail (for trigger)········································································ 62
reaction checked-element rtt ·································································································63
reaction trap······················································································································· 64

ii
rresolve-target ···················································································································· 65
route-option bypass-route ····································································································· 66
source interface ·················································································································· 67
source ip···························································································································· 67
source ipv6 ························································································································ 68
source port························································································································· 69
statistics hold-time··············································································································· 69
statistics interval·················································································································· 70
statistics max-group············································································································· 71
target-only·························································································································· 71
tos···································································································································· 72
ttl······································································································································ 72
type ·································································································································· 73
url····································································································································· 74
username ·························································································································· 75
version······························································································································ 76
vpn-instance······················································································································· 76
NQA server commands··············································································································· 77
display nqa server ··············································································································· 77
nqa server enable················································································································ 78
nqa server tcp-connect········································································································· 78
nqa server udp-echo············································································································ 79
NTP commands·············································································81
display ntp-service ipv6 sessions···························································································· 81
display ntp-service sessions·································································································· 85
display ntp-service status······································································································ 89
display ntp-service trace······································································································· 92
ntp-service acl ···················································································································· 93
ntp-service authentication enable ··························································································· 94
ntp-service authentication-keyid····························································································· 94
ntp-service broadcast-client··································································································· 96
ntp-service broadcast-server ·································································································96
ntp-service dscp·················································································································· 97
ntp-service enable··············································································································· 98
ntp-service inbound enable ··································································································· 98
ntp-service ipv6 acl·············································································································· 99
ntp-service ipv6 dscp ········································································································· 100
ntp-service ipv6 inbound enable··························································································· 100
ntp-service ipv6 multicast-client···························································································· 101
ntp-service ipv6 multicast-server ·························································································· 102
ntp-service ipv6 source······································································································· 103
ntp-service ipv6 unicast-peer······························································································· 104
ntp-service ipv6 unicast-server····························································································· 105
ntp-service max-dynamic-sessions ······················································································· 106
ntp-service multicast-client·································································································· 107
ntp-service multicast-server································································································· 108
ntp-service refclock-master ································································································· 108
ntp-service reliable authentication-keyid ················································································ 109
ntp-service source············································································································· 110
ntp-service unicast-peer ····································································································· 111
ntp-service unicast-server··································································································· 112
SNTP commands········································································· 114
display sntp ipv6 sessions··································································································· 114
display sntp sessions········································································································· 114
sntp authentication enable ·································································································· 115
sntp authentication-keyid···································································································· 116
sntp enable ······················································································································ 117
sntp ipv6 unicast-server······································································································ 117
sntp reliable authentication-keyid·························································································· 118
sntp unicast-server ············································································································ 119

iii
PoE commands ··········································································· 121
apply poe-profile ··············································································································· 121
apply poe-profile interface··································································································· 122
display poe device············································································································· 122
display poe interface·········································································································· 124
display poe interface power································································································· 127
display poe power-usage···································································································· 128
display poe pse················································································································· 130
display poe pse interface ···································································································· 132
display poe pse interface power··························································································· 134
display poe-power ············································································································· 135
display poe-profile············································································································· 139
display poe-profile interface································································································· 140
poe disconnect ················································································································· 141
poe enable······················································································································· 141
poe enable pse················································································································· 142
poe legacy enable ············································································································· 142
poe max-power················································································································· 143
poe max-power (system view) ····························································································· 144
poe pd-description············································································································· 144
poe pd-policy priority·········································································································· 145
poe priority······················································································································· 146
poe priority (system view) ··································································································· 147
poe pse-policy priority ········································································································ 147
poe update······················································································································· 148
poe-profile························································································································ 149
poe utilization-threshold······································································································ 150
SNMP commands ········································································ 151
display snmp-agent community···························································································· 151
display snmp-agent context································································································· 153
display snmp-agent group··································································································· 153
display snmp-agent local-engineid························································································ 154
display snmp-agent mib-node······························································································ 155
display snmp-agent mib-view······························································································· 161
display snmp-agent remote ································································································· 162
display snmp-agent statistics······························································································· 163
display snmp-agent sys-info ································································································ 165
display snmp-agent trap queue···························································································· 166
display snmp-agent trap-list································································································· 166
display snmp-agent usm-user······························································································ 167
enable snmp trap updown··································································································· 169
snmp-agent······················································································································ 170
snmp-agent calculate-password··························································································· 170
snmp-agent community ······································································································ 171
snmp-agent community-map ······························································································· 174
snmp-agent context ··········································································································· 175
snmp-agent group ············································································································· 175
snmp-agent local-engineid ·································································································· 177
snmp-agent log················································································································· 178
snmp-agent mib-view········································································································· 179
snmp-agent packet max-size······························································································· 180
snmp-agent port················································································································ 181
snmp-agent remote············································································································ 181
snmp-agent { inform | trap } source······················································································· 182
snmp-agent sys-info contact································································································ 183
snmp-agent sys-info location······························································································· 184
snmp-agent sys-info version································································································ 184
snmp-agent target-host ······································································································ 185
snmp-agent trap enable······································································································ 187
snmp-agent trap if-mib link extended····················································································· 188

iv
snmp-agent trap life··········································································································· 189
snmp-agent trap log··········································································································· 189
snmp-agent trap queue-size································································································ 190
snmp-agent usm-user { v1 | v2c } ························································································· 191
snmp-agent usm-user v3 ···································································································· 192
snmp-agent usm-user v3 user-role ······················································································· 196
RMON commands········································································ 198
display rmon alarm ············································································································ 198
display rmon event ············································································································ 199
display rmon eventlog ········································································································ 201
display rmon history··········································································································· 202
display rmon prialarm········································································································· 205
display rmon statistics ········································································································ 207
rmon alarm······················································································································· 208
rmon event······················································································································· 210
rmon history····················································································································· 212
rmon prialarm··················································································································· 212
rmon statistics ·················································································································· 215
Event MIB commands ··································································· 216
action······························································································································ 216
comparison ······················································································································ 217
context (action-set view)····································································································· 218
context (trigger view)·········································································································· 218
delta falling ······················································································································ 219
delta rising ······················································································································· 220
description (event view)······································································································ 221
description (trigger view)····································································································· 221
display snmp mib event······································································································ 222
display snmp mib event event······························································································ 223
display snmp mib event object list························································································· 225
display snmp mib event summary························································································· 226
display snmp mib event trigger····························································································· 226
event enable ···················································································································· 230
event owner (trigger-Boolean view)······················································································· 230
event owner (trigger-existence view)····················································································· 231
falling······························································································································ 232
frequency························································································································· 232
object list (action-notification view)························································································ 233
object list (trigger view)······································································································· 234
object list (trigger-Boolean view)··························································································· 235
object list (trigger-existence view)························································································· 235
object list (trigger-threshold view) ························································································· 236
oid (action-notification view) ································································································ 237
oid (action-set view)··········································································································· 237
oid (trigger view) ··············································································································· 238
rising······························································································································· 239
sample···························································································································· 240
snmp mib event ················································································································ 240
snmp mib event object list··································································································· 241
snmp mib event sample instance maximum············································································ 242
snmp mib event sample minimum························································································· 243
snmp mib event trigger······································································································· 243
snmp-agent trap enable event-mib························································································ 244
startup (trigger-existence view) ···························································································· 245
startup (trigger-threshold view)····························································································· 246
startup enable··················································································································· 246
test································································································································· 247
trigger enable ··················································································································· 248
type ································································································································ 248
value (action-set view)········································································································ 249

v
value (trigger-Boolean view)································································································ 250
wildcard context (action-set view)························································································· 251
wildcard context (trigger view)······························································································ 251
wildcard oid (action-set view)······························································································· 252
wildcard oid (trigger view) ··································································································· 253
NETCONF commands ·································································· 254
netconf idle-timeout ··········································································································· 254
netconf log······················································································································· 255
netconf soap http acl·········································································································· 256
netconf soap http enable····································································································· 256
netconf soap https acl ········································································································ 257
netconf soap https enable··································································································· 258
netconf ssh server enable··································································································· 258
netconf ssh server port······································································································· 259
xml ································································································································· 259
CWMP commands ······································································· 261
cwmp······························································································································ 261
cwmp acs default password································································································· 261
cwmp acs default url ·········································································································· 262
cwmp acs default username································································································ 263
cwmp acs password ·········································································································· 263
cwmp acs url···················································································································· 264
cwmp acs username·········································································································· 265
cwmp cpe connect interface ································································································ 266
cwmp cpe connect retry······································································································ 266
cwmp cpe inform interval ···································································································· 267
cwmp cpe inform interval enable ·························································································· 268
cwmp cpe inform time ········································································································ 268
cwmp cpe password ·········································································································· 269
cwmp cpe provision-code···································································································· 270
cwmp cpe stun enable········································································································ 270
cwmp cpe username·········································································································· 271
cwmp cpe wait timeout······································································································· 272
cwmp enable···················································································································· 273
display cwmp configuration ································································································· 273
display cwmp status··········································································································· 275
ssl client-policy ················································································································· 276
EAA commands··········································································· 277
action cli·························································································································· 277
action reboot ···················································································································· 278
action switchover··············································································································· 279
action syslog ···················································································································· 280
commit···························································································································· 281
display rtm environment······································································································ 282
display rtm policy··············································································································· 282
event cli··························································································································· 284
event hotplug···················································································································· 285
event interface·················································································································· 287
event process··················································································································· 289
event snmp oid ················································································································· 290
event snmp-notification······································································································· 291
event syslog····················································································································· 292
rtm cli-policy····················································································································· 293
rtm environment················································································································ 294
rtm scheduler suspend ······································································································· 295
rtm tcl-policy····················································································································· 296
running-time····················································································································· 297
user-role·························································································································· 297

vi
Process monitoring and maintenance commands································ 299
display exception context···································································································· 299
display exception filepath···································································································· 304
display kernel deadloop······································································································ 305
display kernel deadloop configuration···················································································· 308
display kernel exception ····································································································· 310
display kernel reboot·········································································································· 313
display kernel starvation ····································································································· 316
display kernel starvation configuration··················································································· 319
display process················································································································· 320
display process cpu ··········································································································· 323
display process log············································································································ 325
display process memory····································································································· 326
display process memory heap ····························································································· 328
display process memory heap address·················································································· 329
display process memory heap size······················································································· 330
exception filepath ·············································································································· 332
monitor kernel deadloop enable ··························································································· 333
monitor kernel deadloop exclude-thread ················································································ 334
monitor kernel deadloop time······························································································· 335
monitor kernel starvation enable··························································································· 336
monitor kernel starvation exclude-thread················································································ 337
monitor kernel starvation time······························································································ 338
monitor process ················································································································ 339
monitor thread ·················································································································· 344
process core ···················································································································· 348
reset exception context······································································································· 349
reset kernel deadloop········································································································· 350
reset kernel exception········································································································ 351
reset kernel reboot············································································································· 351
reset kernel starvation········································································································ 352
third-part-process start ······································································································· 353
third-part-process stop ······································································································· 353
Sampler commands······································································ 355
display sampler················································································································· 355
sampler··························································································································· 356
Port mirroring commands······························································· 358
display mirroring-group······································································································· 358
mirroring-group················································································································· 359
mirroring-group mirroring-port (interface view) ········································································ 359
mirroring-group mirroring-port (system view)··········································································· 360
mirroring-group monitor-port (interface view) ·········································································· 361
mirroring-group monitor-port (system view) ············································································ 362
Flow mirroring commands······························································ 363
mirror-to ·························································································································· 363
NetStream configuration commands················································· 364
display ip netstream cache·································································································· 364
display ip netstream export·································································································· 371
display ip netstream template ······························································································ 372
enable····························································································································· 375
ip netstream····················································································································· 375
ip netstream filter··············································································································· 376
ip netstream sampler ········································································································· 377
ip netstream aggregation ···································································································· 377
ip netstream export host ····································································································· 379
ip netstream export rate······································································································ 380
ip netstream export source·································································································· 381

vii
ip netstream export v9-template refresh-rate packet································································· 382
ip netstream export v9-template refresh-rate time···································································· 382
ip netstream export version ································································································· 383
ip netstream max-entry······································································································· 384
ip netstream mpls·············································································································· 385
ip netstream timeout active·································································································· 385
ip netstream timeout inactive ······························································································· 386
reset ip netstream statistics································································································· 387
IPv6 NetStream commands···························································· 388
display ipv6 netstream cache······························································································· 388
display ipv6 netstream export ······························································································ 393
display ipv6 netstream template··························································································· 394
enable····························································································································· 398
ipv6 netstream·················································································································· 398
ipv6 netstream filter ··········································································································· 399
ipv6 netstream sampler ······································································································ 400
ipv6 netstream aggregation································································································· 400
ipv6 netstream export host·································································································· 402
ipv6 netstream export rate··································································································· 403
ipv6 netstream export source······························································································· 403
ipv6 netstream export v9-template refresh-rate packet ····························································· 404
ipv6 netstream export v9-template refresh-rate time································································· 405
ipv6 netstream export version 9 ··························································································· 406
ipv6 netstream max-entry···································································································· 406
ipv6 netstream timeout active ······························································································ 407
ipv6 netstream timeout inactive···························································································· 408
reset ipv6 netstream statistics······························································································ 408
sFlow commands········································································· 410
display sflow····················································································································· 410
sflow agent ······················································································································ 411
sflow collector··················································································································· 412
sflow counter interval ········································································································· 413
sflow counter collector········································································································ 414
sflow flow collector············································································································· 414
sflow flow max-header········································································································ 415
sflow sampling-mode ········································································································· 415
sflow sampling-rate············································································································ 416
sflow source····················································································································· 416
Information center commands························································· 418
diagnostic-logfile save········································································································ 418
display diagnostic-logfile summary························································································ 418
display info-center ············································································································· 419
display logbuffer················································································································ 420
display logbuffer summary ·································································································· 422
display logfile summary ······································································································ 424
display security-logfile summary··························································································· 424
enable log updown ············································································································ 425
info-center diagnostic-logfile directory ··················································································· 426
info-center diagnostic-logfile enable······················································································ 426
info-center diagnostic-logfile frequency·················································································· 427
info-center diagnostic-logfile quota························································································ 427
info-center enable·············································································································· 428
info-center format·············································································································· 428
info-center logbuffer··········································································································· 429
info-center logbuffer size····································································································· 430
info-center logfile directory·································································································· 430
info-center logfile enable····································································································· 431
info-center logfile frequency ································································································ 431
info-center logfile overwrite-protection ··················································································· 432

viii
info-center logfile size-quota································································································ 433
info-center logging suppress duplicates················································································· 433
info-center loghost············································································································· 435
info-center loghost source··································································································· 435
info-center security-logfile alarm-threshold ············································································· 436
info-center security-logfile directory······················································································· 437
info-center security-logfile enable ························································································· 438
info-center security-logfile frequency····················································································· 438
info-center security-logfile size-quota ···················································································· 439
info-center source·············································································································· 439
info-center synchronous ····································································································· 441
info-center syslog min-age ·································································································· 442
info-center syslog trap buffersize·························································································· 442
info-center timestamp········································································································· 443
info-center timestamp loghost······························································································ 444
info-center trace-logfile quota ······························································································ 445
logfile save······················································································································· 445
reset logbuffer ·················································································································· 446
security-logfile save ··········································································································· 446
snmp-agent trap enable syslog ···························································································· 447
terminal debugging············································································································ 447
terminal logging level ········································································································· 448
terminal monitor················································································································ 449
Flow log commands······································································ 450
display userlog export ········································································································ 450
reset userlog flow export····································································································· 451
userlog flow export host······································································································ 451
userlog flow export load-balancing························································································ 452
userlog flow export source-ip······························································································· 453
userlog flow export timestamp localtime················································································· 453
userlog flow export version·································································································· 454
userlog flow syslog ············································································································ 455
Document conventions and icons ···················································· 456
Conventions···························································································································· 456
Network topology icons ············································································································· 457
Support and other resources··························································· 458
Accessing Hewlett Packard Enterprise Support·············································································· 458
Accessing updates··················································································································· 458
Websites ························································································································· 459
Customer self repair ·········································································································· 459
Remote support ················································································································ 459
Documentation feedback ···································································································· 459
Index························································································· 461

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.
Syntax
debugging module-name [ option ]
undo debugging module-name [ option ]
Default
Debugging is disabled for all modules.
Views
User view
Predefined user roles
network-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.
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 the debugging command output as debug messages to the device information
center. The information center then sends the messages to appropriate destinations based on the
log output configuration. For more information about configuring debug message output, 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.
Syntax
display debugging [module-name ]

2
Views
Any view
Predefined user roles
network-admin
network-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 | { -topology topo-name | -vpn-instance
vpn-instance-name } ] * host
Views
Any view
Predefined user roles
network-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, or ipv6. 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 ICMP echo 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 TTL value of ICMP echo requests. The value range is 1 to 255, and the default is
255.
-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.

3
-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 reply within 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.
-topology topo-name: Specifies the topology to which the destination belongs, where topo-name is
a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify
this option.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination
belongs, where the vpn-instance-name argument is 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 ---
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

4
# Test 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 (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 that:
•
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/s
tandard deviation response time, in
milliseconds.
ping ipv6
Use ping ipv6 to test the reachability of the destination IPv6 address and display IPv6 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
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 the MPLS L3VPN instance to which the destination
belongs, where the vpn-instance-name argument is 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
The output shows that:
•
The destination is reachable, and ICMPv6 echo requests are replied.
•
The minimum/average/maximum/standard deviation roundtrip time of packets is 4 milliseconds,
25 milliseconds, 62 milliseconds, and 20 milliseconds.
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/s
tandard deviation response time, in
milliseconds.
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 | -t tos | { -topology
topo-name |-vpn-instance vpn-instance-name [ -resolve-as { global | none | vpn } ] } | -w timeout ]
* host
Views
Any view
Predefined user roles
network-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.

8
-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.
-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.
-topology topo-name: Specifies the topology to which the destination belongs, where topo-name is
a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify
this option.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination
belongs, where the vpn-instance-name argument is 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

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) [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 the AS 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
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.
MP
LS 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.

10
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
Views
Any view
Predefined user roles
network-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 the MPLS L3VPN instance to which the destination
belongs, where the vpn-instance-name argument is 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 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 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.