HPE FlexNetwork 7500 Series Installation manual

HPE FlexNetwork 7500 Switch Series
Network Management and Monitoring
Command Reference
Part number: 5998-7478R
Software version: 7500-CMW710-R7178
Document version: 6W100-20160129

© 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® 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····························································································11
NQA client commands ·····································································································································11
advantage-factor······································································································································11
codec-type················································································································································11
data-fill······················································································································································12
data-size···················································································································································13
description (any NQA operation type view)······························································································14
destination ip············································································································································15
destination ipv6········································································································································16
destination port·········································································································································16
display nqa history ···································································································································17
display nqa reaction counters ··················································································································19
display nqa result·····································································································································20
display nqa statistics································································································································27
expect data···············································································································································34
expect ip···················································································································································35
expect ipv6···············································································································································36
expect status············································································································································36
filename····················································································································································37
frequency ·················································································································································38
history-record enable ·······························································································································39
history-record keep-time ··························································································································39
history-record number······························································································································40
init-ttl·························································································································································41
lsr-path·····················································································································································41
max-failure ···············································································································································42
mode························································································································································43
next-hop···················································································································································43
no-fragment enable··································································································································44
nqa···························································································································································44
nqa agent enable ·····································································································································45
nqa schedule············································································································································46
nqa template ············································································································································47
operation (FTP operation view)················································································································47
operation (HTTP operation view)·············································································································48
out interface ·············································································································································49
password··················································································································································50
probe count··············································································································································51
probe packet-interval································································································································52
probe packet-number·······························································································································52
probe packet-timeout ·······························································································································53
probe timeout···········································································································································54
raw-request··············································································································································55
reaction checked-element { jitter-ds | jitter-sd }························································································55
reaction checked-element { owd-ds | owd-sd } ························································································57
reaction checked-element icpif·················································································································58
reaction checked-element mos················································································································59
reaction checked-element packet-loss·····································································································60
reaction checked-element probe-duration································································································61

ii
reaction checked-element probe-fail (for trap)·························································································62
reaction checked-element probe-fail (for trigger)·····················································································64
reaction checked-element rtt····················································································································64
reaction trap·············································································································································66
reaction trigger probe-fail·························································································································67
reaction trigger probe-pass······················································································································67
resolve-target···········································································································································68
resolve-type··············································································································································69
route-option bypass-route························································································································69
source interface········································································································································70
source ip···················································································································································71
source ipv6···············································································································································72
source port···············································································································································73
statistics hold-time····································································································································73
statistics interval·······································································································································74
statistics max-group·································································································································75
target-only················································································································································76
tos ····························································································································································76
ttl ······························································································································································77
type ··························································································································································78
url·····························································································································································78
username·················································································································································79
version······················································································································································80
vpn-instance·············································································································································81
NQA server commands····································································································································81
display nqa server····································································································································82
nqa server enable ····································································································································82
nqa server tcp-connect·····························································································································83
nqa server udp-echo································································································································84
NTP commands····························································································86
display ntp-service ipv6 sessions·············································································································86
display ntp-service sessions ····················································································································90
display ntp-service status·························································································································94
display ntp-service trace ··························································································································96
ntp-service acl··········································································································································97
ntp-service authentication enable ············································································································98
ntp-service authentication-keyid···············································································································99
ntp-service broadcast-client···················································································································100
ntp-service broadcast-server··················································································································100
ntp-service dscp·····································································································································101
ntp-service enable··································································································································102
ntp-service inbound enable····················································································································102
ntp-service ipv6 acl ································································································································103
ntp-service ipv6 dscp ·····························································································································104
ntp-service ipv6 inbound enable ············································································································105
ntp-service ipv6 multicast-client·············································································································105
ntp-service ipv6 multicast-server············································································································106
ntp-service ipv6 source··························································································································107
ntp-service ipv6 unicast-peer·················································································································108
ntp-service ipv6 unicast-server ··············································································································109
ntp-service max-dynamic-sessions········································································································110
ntp-service multicast-client·····················································································································111
ntp-service multicast-server···················································································································112
ntp-service refclock-master····················································································································113
ntp-service reliable authentication-keyid································································································114
ntp-service source··································································································································115
ntp-service unicast-peer·························································································································116
ntp-service unicast-server······················································································································117
SNTP commands························································································119
display sntp ipv6 sessions······················································································································119

iii
display sntp sessions·····························································································································119
sntp authentication enable·····················································································································120
sntp authentication-keyid ·······················································································································121
sntp enable·············································································································································122
sntp ipv6 unicast-server·························································································································122
sntp reliable authentication-keyid···········································································································123
sntp unicast-server·································································································································124
PoE commands···························································································126
apply poe-profile·····································································································································126
apply poe-profile interface······················································································································126
display poe device··································································································································127
display poe interface······························································································································128
display poe interface power ···················································································································131
display poe power-usage·······················································································································132
display poe pse······································································································································134
display poe pse interface ·······················································································································136
display poe pse interface power·············································································································138
display poe-power··································································································································139
display poe-profile··································································································································142
display poe-profile interface···················································································································143
poe enable ·············································································································································143
poe enable pse·······································································································································144
poe legacy enable··································································································································145
poe max-power ······································································································································145
poe max-power (system view) ···············································································································146
poe mode···············································································································································147
poe pd-description··································································································································148
poe pd-policy priority······························································································································148
poe power max-value·····························································································································149
poe priority ·············································································································································150
poe priority (system view) ······················································································································151
poe pse-policy priority····························································································································152
poe temperature-protection····················································································································152
poe update·············································································································································153
poe-profile··············································································································································154
poe utilization-threshold·························································································································155
SNMP commands·······················································································156
display snmp-agent community··············································································································156
display snmp-agent context ···················································································································157
display snmp-agent group······················································································································158
display snmp-agent local-engineid·········································································································159
display snmp-agent mib-node················································································································160
display snmp-agent mib-view·················································································································166
display snmp-agent remote····················································································································167
display snmp-agent statistics·················································································································168
display snmp-agent sys-info···················································································································170
display snmp-agent trap queue··············································································································171
display snmp-agent trap-list···················································································································171
display snmp-agent usm-user················································································································172
enable snmp trap updown······················································································································174
snmp-agent············································································································································175
snmp-agent calculate-password ············································································································175
snmp-agent community··························································································································176
snmp-agent community-map··················································································································179
snmp-agent context································································································································179
snmp-agent group··································································································································180
snmp-agent local-engineid·····················································································································182
snmp-agent log ······································································································································183
snmp-agent mib-view·····························································································································184
snmp-agent packet max-size·················································································································185

iv
snmp-agent port·····································································································································186
snmp-agent remote································································································································186
snmp-agent { inform | trap } source········································································································187
snmp-agent sys-info contact··················································································································188
snmp-agent sys-info location ·················································································································189
snmp-agent sys-info version··················································································································189
snmp-agent target-host··························································································································190
snmp-agent trap enable·························································································································192
snmp-agent trap if-mib link extended·····································································································193
snmp-agent trap life ·······························································································································194
snmp-agent trap log·······························································································································195
snmp-agent trap queue-size ··················································································································195
snmp-agent usm-user { v1 | v2c } ··········································································································196
snmp-agent usm-user v3 ·······················································································································197
snmp-agent usm-user v3 user-role········································································································202
RMON commands ······················································································204
display rmon alarm·································································································································204
display rmon event·································································································································206
display rmon eventlog····························································································································207
display rmon history·······························································································································208
display rmon prialarm·····························································································································211
display rmon statistics····························································································································213
rmon alarm·············································································································································215
rmon event·············································································································································217
rmon history ···········································································································································218
rmon prialarm·········································································································································219
rmon statistics········································································································································221
NETCONF commands················································································223
netconf log··············································································································································223
netconf soap http dscp···························································································································224
netconf soap http enable························································································································224
netconf soap https dscp·························································································································225
netconf soap https enable······················································································································226
netconf ssh server enable······················································································································226
netconf ssh server port···························································································································227
xml··························································································································································227
EAA commands··························································································230
action cli·················································································································································230
action reboot ··········································································································································231
action switchover····································································································································232
action syslog ··········································································································································233
commit····················································································································································233
display rtm environment·························································································································234
display rtm policy····································································································································235
event cli··················································································································································236
event hotplug··········································································································································237
event interface········································································································································238
event process·········································································································································240
event snmp oid·······································································································································241
event snmp-notification··························································································································243
event syslog···········································································································································244
rtm cli-policy···········································································································································245
rtm environment·····································································································································245
rtm scheduler suspend···························································································································247
rtm tcl-policy···········································································································································247
running-time···········································································································································248
user-role·················································································································································249

v
Process monitoring and maintenance commands······································251
display exception context·······················································································································251
display exception filepath·······················································································································255
display kernel deadloop ·························································································································256
display kernel deadloop configuration····································································································260
display kernel exception·························································································································261
display kernel reboot······························································································································264
display kernel starvation·························································································································267
display kernel starvation configuration···································································································270
display process ······································································································································271
display process cpu································································································································274
display process log·································································································································275
display process memory ························································································································276
display process memory heap ···············································································································278
display process memory heap address··································································································279
display process memory heap size········································································································280
exception filepath···································································································································282
monitor kernel deadloop enable·············································································································283
monitor kernel deadloop exclude-thread································································································284
monitor kernel deadloop time·················································································································285
monitor kernel starvation enable············································································································286
monitor kernel starvation exclude-thread·······························································································287
monitor kernel starvation time················································································································288
monitor process······································································································································289
monitor thread········································································································································294
process core···········································································································································297
reset exception context··························································································································298
reset kernel deadloop·····························································································································299
reset kernel exception····························································································································299
reset kernel reboot·································································································································300
reset kernel starvation····························································································································300
Port mirroring commands············································································302
display mirroring-group ··························································································································302
mirroring-group·······································································································································303
mirroring-group mirroring-cpu ················································································································304
mirroring-group mirroring-port (interface view)·······················································································305
mirroring-group mirroring-port (system view)·························································································306
mirroring-group monitor-egress··············································································································307
mirroring-group monitor-port (interface view)·························································································308
mirroring-group monitor-port (system view)···························································································309
mirroring-group reflector-port·················································································································310
mirroring-group remote-probe vlan ········································································································311
Flow mirroring commands···········································································313
mirror-to··················································································································································313
NetStream configuration commands···························································314
display ip netstream cache·····················································································································314
display ip netstream export····················································································································317
display ip netstream template ················································································································319
enable ····················································································································································321
ip netstream ···········································································································································321
ip netstream { inbound | outbound } filter ·······························································································322
ip netstream aggregation ·······················································································································323
ip netstream aggregation advanced·······································································································324
ip netstream export host·························································································································325
ip netstream export rate·························································································································326
ip netstream export source·····················································································································327
ip netstream export v9-template refresh-rate packet ·············································································328
ip netstream export v9-template refresh-rate time·················································································328

vi
ip netstream export version····················································································································329
ip netstream timeout active····················································································································330
ip netstream timeout inactive ·················································································································331
reset ip netstream statistics····················································································································331
IPv6 NetStream commands········································································333
display ipv6 netstream cache·················································································································333
display ipv6 netstream export ················································································································336
display ipv6 netstream template·············································································································337
enable ····················································································································································339
ipv6 netstream········································································································································340
ipv6 netstream { inbound | outbound } filter····························································································340
ipv6 netstream aggregation····················································································································341
ipv6 netstream aggregation advanced···································································································342
ipv6 netstream export host·····················································································································343
ipv6 netstream export rate ·····················································································································344
ipv6 netstream export source·················································································································345
ipv6 netstream export v9-template refresh-rate packet··········································································346
ipv6 netstream export v9-template refresh-rate time ·············································································346
ipv6 netstream export version 9·············································································································347
ipv6 netstream timeout active ················································································································348
ipv6 netstream timeout inactive··············································································································349
reset ipv6 netstream statistics················································································································349
sFlow commands························································································351
display sflow···········································································································································351
sflow agent·············································································································································352
sflow collector·········································································································································353
sflow counter interval ·····························································································································354
sflow counter collector····························································································································354
sflow flow collector·································································································································355
sflow flow max-header ···························································································································355
sflow sampling-mode ·····························································································································356
sflow sampling-rate································································································································357
sflow source···········································································································································357
Information center commands ····································································359
diagnostic-logfile save····························································································································359
display diagnostic-logfile summary ········································································································359
display info-center··································································································································360
display logbuffer·····································································································································361
display logbuffer summary·····················································································································363
display logfile summary··························································································································364
display security-logfile summary············································································································365
enable log updown·································································································································365
info-center diagnostic-logfile enable·······································································································366
info-center diagnostic-logfile frequency··································································································366
info-center diagnostic-logfile quota ········································································································367
info-center diagnostic-logfile directory····································································································368
info-center logfile overwrite-protection···································································································368
info-center enable ··································································································································369
info-center format···································································································································370
info-center logbuffer·······························································································································370
info-center logbuffer size························································································································371
info-center logfile enable························································································································371
info-center logfile frequency···················································································································372
info-center logfile size-quota··················································································································373
info-center logfile directory·····················································································································373
info-center logging suppress duplicates·································································································374
info-center logging suppress module·····································································································375
info-center loghost··································································································································376
info-center loghost source······················································································································377

vii
info-center security-logfile alarm-threshold····························································································378
info-center security-logfile enable ··········································································································379
info-center security-logfile frequency ·····································································································379
info-center security-logfile size-quota·····································································································380
info-center security-logfile directory ·······································································································381
info-center source ··································································································································381
info-center synchronous·························································································································383
info-center syslog min-age·····················································································································384
info-center timestamp·····························································································································385
info-center timestamp loghost················································································································385
info-center trace-logfile quota·················································································································386
logfile save·············································································································································387
reset logbuffer········································································································································387
security-logfile save································································································································387
terminal debugging·································································································································388
terminal logging level ·····························································································································389
terminal monitor ·····································································································································390
GOLD commands·······················································································391
diagnostic event-log size························································································································391
diagnostic monitor enable······················································································································391
diagnostic monitor interval ·····················································································································392
diagnostic ondemand failure··················································································································394
diagnostic ondemand repeating·············································································································394
diagnostic ondemand start·····················································································································395
diagnostic ondemand stop·····················································································································396
diagnostic simulation······························································································································397
display diagnostic content······················································································································398
display diagnostic event-log···················································································································400
display diagnostic ondemand configuration···························································································401
display diagnostic result·························································································································402
display diagnostic result statistics··········································································································403
display diagnostic simulation··················································································································405
reset diagnostic event-log······················································································································406
reset diagnostic result····························································································································406
Packet capture commands ·········································································408
packet-capture ·······································································································································408
packet-capture read·······························································································································410
Document conventions and icons·······························································412
Conventions···················································································································································412
Network topology icons··································································································································413
Support and other resources ······································································414
Accessing Hewlett Packard Enterprise Support ····························································································414
Accessing updates·········································································································································414
Websites ················································································································································415
Customer self repair·······························································································································415
Remote support······································································································································415
Documentation feedback ·······················································································································415
Index···········································································································417

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 { all [ timeout time ] | module-name [ option ] }
undo debugging { all | module-name [ option ] }
Default
Debugging functions are disabled for all modules.
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
all: Enables all debugging functions.
timeout time: Specifies the timeout time for the debugging all command. When all debugging is
enabled, the system automatically executes the undo debugging all command after the timeout
time.The time argument is in the range of 1 to 1440 minutes.
module-name: Specifies a module by its name, such as arp or device. To display the current module
name, use the debugging ? command.
option: Specifies the debugging option for a module. The option number and content differ for
different modules. To display the supported options, 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.
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 functions.
Syntax
display debugging [module-name ]

2
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
module-name: Specifies a module by its name. To display the current module name, use the display
debugging ? command.
Examples
# Display all enabled debugging functions.
<Sysname> display debugging
DEV debugging switch is on
Related commands
debugging
ping
Use ping to verify whether the destination IP address is reachable, and display related statistics.
Syntax
ping [ ip ] [ -a source-ip | -c count | -f | -h ttl | -i interface-type interface-number | -m interval | -n | -p
pad | -q | -r | -s packet-size | -t timeout | -tos tos | -v | -vpn-instance vpn-instance-name ] * host
Views
Any view
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 IPaddress
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.

3
-m interval: Specifies the interval (in milliseconds) to send ICMPecho 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 thepacket 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 ICMPecho 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.
-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 use the name of the destination host to perform the ping operation, you must first configure the
DNS on the device. Otherwise, the ping operation will fail.
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
# Test whether the device with an IP address of 1.1.2.2 in VPN 1 is reachable.

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

5
Field Description
•
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 verify whether an IPv6 address is reachable, and display related 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. (The address selection rule is defined by RFC 3484.)
-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.
-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.

6
-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 use the name of the destination host to perform the ipv6 ping operation, you must first configure
DNS on the device. Otherwise, the ipv6 ping 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
--- Ping6 statistics for 2001::2 ---

7
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::1to 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 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 | -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.

8
-f first-ttl: Specifies the TTLof the first packet sent to the destination. The value range is 1 to255, 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.
-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 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.
-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.
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) 580 ms 470 ms 80 ms
# Trace the path to destination (192.168.0.46) over an MPLS network.
<Sysname> tracert 192.168.0.46
traceroute to 192.168.0.46(192.168.0.46), 30 hops 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.

9
Field Description
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.
1 1.1.1.2 (1.1.1.2) 673 ms
425 ms 30 ms
Probe result of the probe packets whose TTL is 1, including the following:
•Domain name (or IP address, if the domain name is not configured) of
the first hop.
•The round-trip time of the three probe packets.
The number of packets that can be sent in each probe can be set through
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 | -w timeout ] * host
Views
Any view
Predefined user roles
network-admin
mdc-admin
Parameters
-f first-hop: Specifies the TTLvalue 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.

10
-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.
-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.
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.
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::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 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.
1 2001:1::2 0.661 ms 0.618 ms
0.579 ms
Probe result of the probe packets whose hoplimit is 1, including the IPv6
address of the first hop, and the roundtrip time of three probe packets.
The number of packets that can be sent in each probe can be set by the
-q keyword.

11
NQA commands
NQA client commands
advantage-factor
Use advantage-factor to configure the advantage factor that is used to count Mean Opinion Scores
(MOS) and Calculated Planning Impairment Factor (ICPIF) values.
Use undo advantage-factor to restore the default.
Syntax
advantage-factor factor
undo advantage-factor
Default
The advantage factor is 0.
Views
Voice operation view
Predefined user roles
network-admin
mdc-admin
Parameters
factor: Specifies the advantage factor in the range of 0 to 20.
Usage guidelines
The evaluation of voice quality depends on users' tolerance for voice quality. For users with higher
tolerance for voice quality, use the advantage-factor command to configure the advantage factor.
When the system calculates the ICPIF value, the specified advantage factor is subtracted to modify
ICPIF and MOS values for voice quality evaluation.
Examples
# Configure the advantage factor as 10 for voice operations.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type voice
[Sysname-nqa-admin-test-voice] advantage-factor 10
codec-type
Use codec-type to configure the codec type for a voice operation.
Use undo codec-type to restore the default.
Syntax
codec-type { g711a | g711u | g729a }
undo codec-type