HP 12500 Series Installation manual

HP FlexFabric 12500 and 12500E Routing
Switch Series
Network Management and Monitoring
Command Reference
Part number: 5998-4887
Software version: 12500-CMW710-R7328
Document version: 6PW100-20140128

Legal and notice information
© Copyright 2014 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained
herein.

i
Contents
Ping, tracert, and system debugging commands······································································································· 1
debugging·································································································································································1
display debugging ···················································································································································2
ping············································································································································································2
ping ipv6···································································································································································5
tracert·········································································································································································8
tracert ipv6····························································································································································· 10
NQA commands························································································································································12
NQA client commands·················································································································································· 12
advantage-factor ··················································································································································· 12
codec-type······························································································································································ 12
data-fill···································································································································································· 13
data-size ································································································································································· 14
description (any NQA operation type view)······································································································ 15
destination ip ························································································································································· 16
destination ipv6 ····················································································································································· 17
destination port······················································································································································ 17
display nqa history················································································································································ 18
display nqa reaction counters······························································································································ 19
display nqa result ·················································································································································· 21
display nqa statistics ············································································································································· 27
expect data ···························································································································································· 34
expect status··························································································································································· 35
expect ip································································································································································· 36
expect ipv6 ···························································································································································· 36
filename·································································································································································· 37
frequency································································································································································ 38
history-record enable ············································································································································ 39
history-record keep-time········································································································································ 39
history-record number ··········································································································································· 40
lsr-path ···································································································································································· 41
mode······································································································································································· 41
next-hop·································································································································································· 42
nqa·········································································································································································· 43
nqa template ·························································································································································· 44
nqa agent enable ·················································································································································· 44
nqa schedule·························································································································································· 45
operation (FTP operation view)···························································································································· 46
operation (HTTP operation view) ························································································································· 47
password································································································································································ 47
probe count···························································································································································· 48
probe packet-interval ············································································································································ 50
probe packet-number ············································································································································ 50
probe packet-timeout············································································································································· 51
probe timeout························································································································································· 51
raw-request····························································································································································· 52
reaction checked-element icpif····························································································································· 53
reaction checked-element { jitter-ds | jitter-sd } ·································································································· 54

ii
reaction checked-element mos ····························································································································· 56
reaction checked-element { owd-ds | owd-sd }·································································································· 57
reaction checked-element packet-loss·················································································································· 58
reaction checked-element probe-duration··········································································································· 59
reaction checked-element probe-fail (for trap)···································································································· 60
reaction checked-element probe-fail (for trigger) ······························································································· 62
reaction checked-element rtt································································································································· 63
reaction trap ·························································································································································· 64
reaction trigger probe-fail····································································································································· 65
reaction trigger probe-pass ·································································································································· 66
resolve-target·························································································································································· 66
resolve-type ···························································································································································· 67
route-option bypass-route······································································································································ 68
source interface ····················································································································································· 68
source ip································································································································································· 69
source ipv6····························································································································································· 70
source port ····························································································································································· 71
statistics hold-time·················································································································································· 72
statistics interval····················································································································································· 72
statistics max-group ··············································································································································· 73
target-only······························································································································································· 74
tos············································································································································································ 74
ttl·············································································································································································· 75
type ········································································································································································· 76
url ············································································································································································ 77
username································································································································································ 77
version ···································································································································································· 78
vpn-instance ··························································································································································· 79
NQA server commands················································································································································· 80
display nqa server················································································································································· 80
nqa server enable ················································································································································· 81
nqa server tcp-connect ·········································································································································· 81
nqa server udp-echo ············································································································································· 82
NTP commands ··························································································································································84
display ntp-service sessions ·································································································································· 84
display ntp-service status ······································································································································ 88
display ntp-service trace ······································································································································· 90
ntp-service acl ························································································································································ 91
ntp-service authentication enable ························································································································ 92
ntp-service authentication-keyid ··························································································································· 93
ntp-service broadcast-client ·································································································································· 94
ntp-service broadcast-server ································································································································· 94
ntp-service dscp ····················································································································································· 95
ntp-service enable·················································································································································· 96
ntp-service inbound disable·································································································································· 96
ntp-service max-dynamic-sessions ························································································································ 97
ntp-service multicast-client····································································································································· 98
ntp-service multicast-server···································································································································· 98
ntp-service refclock-master···································································································································· 99
ntp-service reliable authentication-keyid ···········································································································100
ntp-service source ················································································································································101
ntp-service unicast-peer·······································································································································102
ntp-service unicast-server ····································································································································104

iii
SNTP commands ····················································································································································· 106
display sntp sessions···········································································································································106
sntp authentication enable ·································································································································106
sntp authentication-keyid ····································································································································107
sntp enable···························································································································································108
sntp reliable authentication-keyid ······················································································································109
sntp unicast-server ···············································································································································109
SNMP commands ··················································································································································· 112
display snmp-agent community··························································································································112
display snmp-agent context ································································································································113
display snmp-agent group ··································································································································114
display snmp-agent local-engineid ····················································································································115
display snmp-agent mib-node ····························································································································116
display snmp-agent mib-view ·····························································································································122
display snmp-agent remote ································································································································124
display snmp-agent statistics ······························································································································125
display snmp-agent sys-info································································································································126
display snmp-agent trap queue··························································································································127
display snmp-agent trap-list ································································································································128
display snmp-agent usm-user······························································································································128
enable snmp trap updown ·································································································································130
snmp-agent···························································································································································131
snmp-agent calculate-password ·························································································································131
snmp-agent community ·······································································································································132
snmp-agent community-map·······························································································································134
snmp-agent context··············································································································································135
snmp-agent group················································································································································136
snmp-agent local-engineid··································································································································138
snmp-agent log ····················································································································································139
snmp-agent mib-view···········································································································································140
snmp-agent packet max-size ······························································································································141
snmp-agent port···················································································································································141
snmp-agent remote ··············································································································································142
snmp-agent source···············································································································································143
snmp-agent sys-info contact································································································································144
snmp-agent sys-info location·······························································································································145
snmp-agent sys-info version ································································································································145
snmp-agent target-host ········································································································································146
snmp-agent trap enable ······································································································································148
snmp-agent trap if-mib link extended ················································································································149
snmp-agent trap life·············································································································································150
snmp-agent trap log ············································································································································151
snmp-agent trap queue-size································································································································151
snmp-agent usm-user { v1 | v2c }······················································································································152
snmp-agent usm-user v3······································································································································153
RMON commands ·················································································································································· 157
display rmon alarm ·············································································································································157
display rmon event··············································································································································159
display rmon eventlog·········································································································································160
display rmon history············································································································································162
display rmon prialarm ········································································································································165
display rmon statistics ·········································································································································167
rmon alarm···························································································································································169

iv
rmon event····························································································································································171
rmon history ·························································································································································172
rmon prialarm ······················································································································································173
rmon statistics·······················································································································································176
NETCONF commands············································································································································ 178
xml·········································································································································································178
netconf soap http enable ····································································································································179
netconf soap https enable ··································································································································180
Port mirroring commands ······································································································································· 181
display mirroring-group ······································································································································181
mirroring-group····················································································································································182
mirroring-group mirroring-port (interface view)································································································183
mirroring-group mirroring-port (system view) ···································································································184
mirroring-group mirroring-vlan···························································································································185
mirroring-group monitor-port (interface view)···································································································186
mirroring-group monitor-port (system view) ······································································································187
mirroring-group reflector-port ·····························································································································188
mirroring-group remote-probe vlan····················································································································190
Traffic mirroring commands ··································································································································· 192
mirror-to ································································································································································192
Sampler commands ················································································································································ 194
display sampler ···················································································································································194
sampler·································································································································································195
sFlow commands····················································································································································· 196
display sflow ························································································································································196
sflow agent···························································································································································197
sflow collector ······················································································································································198
sflow counter interval ··········································································································································199
sflow counter collector ········································································································································200
sflow flow collector··············································································································································200
sflow flow max-header········································································································································201
sflow sampling-mode ··········································································································································201
sflow sampling-rate ·············································································································································202
sflow source ·························································································································································203
Information center commands ································································································································ 204
diagnostic-logfile save ········································································································································204
display diagnostic-logfile summary ···················································································································204
display info-center ···············································································································································205
display logbuffer··················································································································································206
display logbuffer summary ·································································································································208
display logfile summary······································································································································209
display security-logfile summary ························································································································210
enable log updown·············································································································································211
info-center diagnostic-logfile enable··················································································································211
info-center diagnostic-logfile frequency·············································································································212
info-center diagnostic-logfile quota····················································································································213
info-center diagnostic-logfile directory ··············································································································213
info-center logfile overwrite-protection ··············································································································214
info-center enable················································································································································215
info-center format·················································································································································215
info-center logbuffer ············································································································································216

v
info-center logbuffer size ····································································································································217
info-center logfile enable ····································································································································217
info-center logfile frequency ·······························································································································218
info-center logfile size-quota·······························································································································219
info-center logfile directory·································································································································219
info-center logging suppress duplicates ············································································································220
info-center loghost ···············································································································································222
info-center loghost source ···································································································································222
info-center security-logfile alarm-threshold ········································································································223
info-center security-logfile enable·······················································································································224
info-center security-logfile frequency ·················································································································225
info-center security-logfile size-quota·················································································································225
info-center security-logfile directory ···················································································································226
info-center source ················································································································································227
info-center synchronous ······································································································································228
info-center timestamp ··········································································································································229
info-center timestamp loghost·····························································································································230
info-center trace-logfile quota·····························································································································231
logfile save···························································································································································232
reset logbuffer······················································································································································232
security-logfile save ·············································································································································233
terminal debugging·············································································································································233
terminal logging level ·········································································································································234
terminal monitor···················································································································································235
EAA commands······················································································································································· 236
action cli·······························································································································································236
action reboot························································································································································237
action switchover·················································································································································238
action syslog ························································································································································238
commit ··································································································································································239
display rtm environment······································································································································240
display rtm policy ················································································································································240
event cli ································································································································································242
event hotplug ·······················································································································································243
event interface ·····················································································································································244
event process ·······················································································································································246
event snmp oid ····················································································································································247
event snmp-notification········································································································································248
event syslog··························································································································································249
rtm cli-policy·························································································································································250
rtm environment ···················································································································································251
rtm scheduler suspend·········································································································································253
rtm tcl-policy ·························································································································································253
running-time··························································································································································254
user-role ································································································································································255
Process monitoring and maintenance commands ································································································ 256
display exception context ···································································································································256
display exception filepath ··································································································································258
display kernel deadloop·····································································································································259
display kernel deadloop configuration ·············································································································263
display kernel exception·····································································································································264
display kernel reboot ··········································································································································267
display kernel starvation·····································································································································270

vi
display kernel starvation configuration ·············································································································273
display process····················································································································································274
display process cpu ············································································································································277
display process log ·············································································································································278
display process memory ·····································································································································279
display process memory heap ···························································································································281
display process memory heap address ············································································································282
display process memory heap size ···················································································································284
exception filepath ················································································································································285
monitor kernel deadloop enable ·······················································································································286
monitor kernel deadloop exclude-thread ··········································································································287
monitor kernel deadloop time ····························································································································288
monitor kernel starvation enable ·······················································································································289
monitor kernel starvation exclude-thread ··········································································································290
monitor kernel starvation time····························································································································291
monitor process ···················································································································································292
monitor thread ·····················································································································································297
process core·························································································································································300
reset exception context ·······································································································································301
reset kernel deadloop ·········································································································································302
reset kernel exception ·········································································································································303
reset kernel reboot···············································································································································303
reset kernel starvation ·········································································································································304
Support and other resources ·································································································································· 306
Contacting HP ······························································································································································306
Subscription service ············································································································································306
Related information······················································································································································306
Documents····························································································································································306
Websites·······························································································································································306
Conventions ··································································································································································307
Index ········································································································································································ 309

1
Ping, tracert, and system debugging
commands
debugging
Use debugging to enable debugging for a specific module.
Use undo debugging to disable debugging for a specific 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 specific module. The option number and content differ for
different modules. To display the supported options, use the debugging module-name ?command.
Usage guidelines
Output of debugging commands is memory intensive. To guarantee system performance, enable
debugging only for modules that are in an exceptional condition.
For more information about the debugging commands and debugging information about a specific
module, see debugging manuals of the module.
Examples
# Enable debugging for the device management module.
<Sysname> debugging dev
Related commands
display debugging

2
display debugging
Use display debugging to display the enabled debugging functions.
Syntax
display debugging [module-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
module-name: Specifies a module by its name. 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.

3
-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 DF 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 of ICMP echo requests. If this option is
not provided, the system uses the primary IP address of the matching route's egress interface as the
source interface of ICMP echo requests.
-m interval: Specifies the interval (in milliseconds) to send ICMP echo requests. The value range is 1 to
65535, and the default is 200.
-n: Disables domain name resolution for the host argument. If the host argument represents the host name
for the destination, and 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, like
0x010203…feff01….
-q: Displays only statistics. If this keyword is not specified, the system displays all information.
-r: Records routing information. If this keyword is not specified, routes 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.
-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.

4
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.
<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 route information is 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

5
round-trip min/avg/max/std-dev = 4.685/4.761/4.834/0.058 ms
The output shows that:
•The destination is reachable.
•T h e ro u t e i s 1.1.1.1 < - > { 1.1.1. 2; 1.1. 2.1 } < - > 1.1.2. 2.
Table 1 Command output
Field Descri
p
tion
Ping 1.1.2.2 (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 data 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 during the timeout period, no
information is displayed.
•bytes—Number of data bytes in the ICMP reply.
•icmp_seq—Packet sequence, used to determine whether a segment is
lost, disordered or repeated.
•ttl—TTL value in the ICMP 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 packets not responded 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 | -m interval |-q | -s packet-size | -t timeout |-tc traffic-class|-v
| -vpn-instance vpn-instance-name ] * host [ -i interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
mdc-admin

6
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.
-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 statistics. Without this keyword, the system displays all the ping statistics.
-s packet-size: Specifies 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.
-i interface-type interface-number: Specifies the source interface of ICMPv6 echo requests. This option
must be specified when the destination address is a multicast address or a link local address. Without this
option, the system uses the primary IP address of the matching route's egress interface as the source
interface of ICMP echo requests.
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

7
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 is 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 ---
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 Descri
p
tion
Ping6(56 data bytes)
2001::1 --> 2001::2, press CTRL_C to
break
A 104-byte 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 packets not responded to the total packets sent.

8
Field Descri
p
tion
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.
-f first-ttl: Specifies the TTL of 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.
-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 in a tracert 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.
-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 of 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

9
ICMP error message (this can be because the destination is unreachable or sending ICMP
timeout/destination unreachable packets is disabled).
To abort the tracert operation during the execution of the command, press Ctrl+C.
Examples
# Display the path 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 Descri
p
tion
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.
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 domain name
(or IP address, if the domain name is not configured) of the first hop, and 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.

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 | -w timeout ] * host
Views
Any view
Predefined user roles
network-admin
mdc-admin
Parameters
-f first-hop: Specifies the TTL value of the first packet. The value range is 1 to 255, and the default is 1. The
value must be no greater than the value of the max-hops argument.
-m max-hops: Specifies the maximum number of hops allowed for a packet. The value range is 1 to 255,
and the default is 30. The value must be no smaller than the value of the first-hop argument.
-p port: Specifies an invalid UDP port of the destination. The value range is 1 to 65535, and the default
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 tracert 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.
-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 of 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 (this can be because the destination is unreachable or sending ICMP
timeout/destination unreachable packets is disabled).
To abort the tracert operation during the execution of the command, press Ctrl+C.
Examples
# Display the path that the packets traverse from source to destination (2001:3::2).
<Sysname> tracert ipv6 2001:3::2

11
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 Descri
p
tion
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.

12
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 so that both the objective and subjective factors are considered when you evaluate voice
quality.
Examples
# Configure the advantage factor for voice operations as 10.
<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.