HP FlexNetwork MSR3012, FlexNetwork MSR3024, FlexNetwork MSR3044, FlexNetwork MSR4080, FlexNetwork MSR3064 Comware 7 Network Management and Monitoring Command Reference

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

Contents

Ping, tracert, and system debugging commands ·····································1
debugging ···························································································································· 1 display debugging ················································································································· 1 ping ···································································································································· 2 ping ipv6 ······························································································································ 5 tracert ································································································································· 7 tracert ipv6 ························································································································· 10
NQA commands ············································································ 12
NQA client commands ················································································································ 12
advantage-factor ················································································································· 12 codec-type ························································································································· 12 data-fill ······························································································································ 13 data-size ···························································································································· 14 description ························································································································· 15 destination ip ······················································································································ 16 destination ipv6 ··················································································································· 16 destination port ··················································································································· 17 display nqa history ··············································································································· 17 display nqa reaction counters ································································································ 19 display nqa result ················································································································ 21 display nqa statistics ············································································································ 28 filename ···························································································································· 36 frequency··························································································································· 37 history-record enable ··········································································································· 38 history-record keep-time ······································································································· 38 history-record number ·········································································································· 39 init-ttl ································································································································· 40 lsr-path ······························································································································ 40 max-failure ························································································································· 41 mode ································································································································ 42 next-hop ip ························································································································· 42 next-hop ipv6 ······················································································································ 43 no-fragment enable ············································································································· 43 nqa ··································································································································· 44 nqa agent enable ················································································································ 45 nqa schedule ······················································································································ 45 operation (FTP operation view) ······························································································ 46 operation (HTTP operation view) ···························································································· 47 out interface ······················································································································· 48 password ··························································································································· 49 probe count ························································································································ 49 probe packet-interval ··········································································································· 51 probe packet-number ··········································································································· 51 probe packet-timeout ··········································································································· 52 probe timeout ····················································································································· 53 raw-request ························································································································ 53 reaction checked-element { jitter-ds | jitter-sd } ·········································································· 54 reaction checked-element { owd-ds | owd-sd } ·········································································· 55 reaction checked-element icpif ······························································································· 56 reaction checked-element mos ······························································································ 57 reaction checked-element packet-loss ····················································································· 58 reaction checked-element probe-duration ················································································ 59 reaction checked-element probe-fail (for trap) ··········································································· 61 reaction checked-element probe-fail (for trigger) ········································································ 62 reaction checked-element rtt ································································································· 63 reaction trap ······················································································································· 64
i
rresolve-target ···················································································································· 65 route-option bypass-route ····································································································· 66 source interface ·················································································································· 67 source ip ···························································································································· 67 source ipv6 ························································································································ 68 source port ························································································································· 69 statistics hold-time ··············································································································· 69 statistics interval ·················································································································· 70 statistics max-group ············································································································· 71 target-only·························································································································· 71 tos ···································································································································· 72 ttl······································································································································ 72 type ·································································································································· 73 url····································································································································· 74 username ·························································································································· 75 version ······························································································································ 76 vpn-instance ······················································································································· 76
NQA server commands ··············································································································· 77
display nqa server ··············································································································· 77 nqa server enable················································································································ 78 nqa server tcp-connect ········································································································· 78 nqa server udp-echo ············································································································ 79
NTP commands ············································································· 81
display ntp-service ipv6 sessions ···························································································· 81 display ntp-service sessions ·································································································· 85 display ntp-service status ······································································································ 89 display ntp-service trace ······································································································· 92 ntp-service acl ···················································································································· 93 ntp-service authentication enable ··························································································· 94 ntp-service authentication-keyid ····························································································· 94 ntp-service broadcast-client ··································································································· 96 ntp-service broadcast-server ································································································· 96 ntp-service dscp ·················································································································· 97 ntp-service enable ··············································································································· 98 ntp-service inbound enable ··································································································· 98 ntp-service ipv6 acl ·············································································································· 99 ntp-service ipv6 dscp ········································································································· 100 ntp-service ipv6 inbound enable ··························································································· 100 ntp-service ipv6 multicast-client ···························································································· 101 ntp-service ipv6 multicast-server ·························································································· 102 ntp-service ipv6 source ······································································································· 103 ntp-service ipv6 unicast-peer ······························································································· 104 ntp-service ipv6 unicast-server ····························································································· 105 ntp-service max-dynamic-sessions ······················································································· 106 ntp-service multicast-client ·································································································· 107 ntp-service multicast-server ································································································· 108 ntp-service refclock-master ································································································· 108 ntp-service reliable authentication-keyid ················································································ 109 ntp-service source ············································································································· 110 ntp-service unicast-peer ····································································································· 111 ntp-service unicast-server ··································································································· 112
SNTP commands ········································································· 114
display sntp ipv6 sessions ··································································································· 114 display sntp sessions ········································································································· 114 sntp authentication enable ·································································································· 115 sntp authentication-keyid ···································································································· 116 sntp enable ······················································································································ 117 sntp ipv6 unicast-server ······································································································ 117 sntp reliable authentication-keyid ·························································································· 118 sntp unicast-server ············································································································ 119
ii
PoE commands ··········································································· 121
apply poe-profile ··············································································································· 121 apply poe-profile interface ··································································································· 122 display poe device ············································································································· 122 display poe interface ·········································································································· 124 display poe interface power ································································································· 127 display poe power-usage ···································································································· 128 display poe pse ················································································································· 130 display poe pse interface ···································································································· 132 display poe pse interface power ··························································································· 134 display poe-power ············································································································· 135 display poe-profile ············································································································· 139 display poe-profile interface ································································································· 140 poe disconnect ················································································································· 141 poe enable ······················································································································· 141 poe enable pse ················································································································· 142 poe legacy enable ············································································································· 142 poe max-power ················································································································· 143 poe max-power (system view) ····························································································· 144 poe pd-description ············································································································· 144 poe pd-policy priority ·········································································································· 145 poe priority ······················································································································· 146 poe priority (system view) ··································································································· 147 poe pse-policy priority ········································································································ 147 poe update ······················································································································· 148 poe-profile························································································································ 149 poe utilization-threshold ······································································································ 150
SNMP commands ········································································ 151
display snmp-agent community ···························································································· 151 display snmp-agent context ································································································· 153 display snmp-agent group ··································································································· 153 display snmp-agent local-engineid ························································································ 154 display snmp-agent mib-node ······························································································ 155 display snmp-agent mib-view ······························································································· 161 display snmp-agent remote ································································································· 162 display snmp-agent statistics ······························································································· 163 display snmp-agent sys-info ································································································ 165 display snmp-agent trap queue ···························································································· 166 display snmp-agent trap-list ································································································· 166 display snmp-agent usm-user ······························································································ 167 enable snmp trap updown ··································································································· 169 snmp-agent ······················································································································ 170 snmp-agent calculate-password ··························································································· 170 snmp-agent community ······································································································ 171 snmp-agent community-map ······························································································· 174 snmp-agent context ··········································································································· 175 snmp-agent group ············································································································· 175 snmp-agent local-engineid ·································································································· 177 snmp-agent log ················································································································· 178 snmp-agent mib-view ········································································································· 179 snmp-agent packet max-size ······························································································· 180 snmp-agent port ················································································································ 181 snmp-agent remote············································································································ 181 snmp-agent { inform | trap } source ······················································································· 182 snmp-agent sys-inf o contact ································································································ 183 snmp-agent sys-info location ······························································································· 184 snmp-agent sys-info version ································································································ 184 snmp-agent target-host ······································································································ 185 snmp-agent trap enable ······································································································ 187 snmp-agent trap if-mib link extended ····················································································· 188
iii
snmp-agent trap life ··········································································································· 189 snmp-agent trap log ··········································································································· 189 snmp-agent trap queue-size ································································································ 190 snmp-agent usm-user { v1 | v2c } ························································································· 191 snmp-agent usm-user v3 ···································································································· 192 snmp-agent usm-user v3 user-role ······················································································· 196
RMON commands ········································································ 198
display rmon alarm ············································································································ 198 display rmon event ············································································································ 199 display rmon eventlog ········································································································ 201 display rmon history ··········································································································· 202 display rmon prialarm ········································································································· 205 display rmon statistics ········································································································ 207 rmon alarm······················································································································· 208 rmon event ······················································································································· 210 rmon history ····················································································································· 212 rmon prialarm ··················································································································· 212 rmon statistics ·················································································································· 215
Event MIB commands ··································································· 216
action ······························································································································ 216 comparison ······················································································································ 217 context (action-set view) ····································································································· 218 context (trigger view) ·········································································································· 218 delta falling ······················································································································ 219 delta rising ······················································································································· 220 description (event view) ······································································································ 221 description (trigger view) ····································································································· 221 display snmp mib event ······································································································ 222 display snmp mib event event ······························································································ 223 display snmp mib event object list ························································································· 225 display snmp mib event summary ························································································· 226 display snmp mib event trigger ····························································································· 226 event enable ···················································································································· 230 event owner (trigger-Boolean view) ······················································································· 230 event owner (trigger-existence view) ····················································································· 231 falling ······························································································································ 232 frequency························································································································· 232 object list (action-notification view) ························································································ 233 object list (trigger view) ······································································································· 234 object list (trigger-Boolean view) ··························································································· 235 object list (trigger-existence view) ························································································· 235 object list (trigger-threshold view) ························································································· 236 oid (action-notification view) ································································································ 237 oid (action-set view) ··········································································································· 237 oid (trigger view) ··············································································································· 238 rising ······························································································································· 239 sample ···························································································································· 240 snmp mib event ················································································································ 240 snmp mib event object list ··································································································· 241 snmp mib event sample instance maximum············································································ 242 snmp mib event sample minimum ························································································· 243 snmp mib event trigger ······································································································· 243 snmp-agent trap enable event-mib························································································ 244 startup (trigger-existence view) ···························································································· 245 startup (trigger-threshold view) ····························································································· 246 startup enable ··················································································································· 246 test ································································································································· 247 trigger enable ··················································································································· 248 type ································································································································ 248 value (action-set view) ········································································································ 249
iv
value (trigger-Boolean view) ································································································ 250 wildcard context (action-set view) ························································································· 251 wildcard context (trigger view) ······························································································ 251 wildcard oid (action-set view) ······························································································· 252 wildcard oid (trigger view) ··································································································· 253
NETCONF commands ·································································· 254
netconf idle-timeout ··········································································································· 254 netconf log ······················································································································· 255 netconf soap http acl ·········································································································· 256 netconf soap http enable ····································································································· 256 netconf soap https acl ········································································································ 257 netconf soap https enable ··································································································· 258 netconf ssh server enable ··································································································· 258 netconf ssh server port ······································································································· 259 xml ································································································································· 259
CWMP commands ······································································· 261
cwmp ······························································································································ 261 cwmp acs default password································································································· 261 cwmp acs default url ·········································································································· 262 cwmp acs default username ································································································ 263 cwmp acs password ·········································································································· 263 cwmp acs url ···················································································································· 264 cwmp acs username ·········································································································· 265 cwmp cpe connect interface ································································································ 266 cwmp cpe connect retry ······································································································ 266 cwmp cpe inform interval ···································································································· 267 cwmp cpe inform interval enable ·························································································· 268 cwmp cpe inform time ········································································································ 268 cwmp cpe password ·········································································································· 269 cwmp cpe provision-code ···································································································· 270 cwmp cpe stun enable ········································································································ 270 cwmp cpe username ·········································································································· 271 cwmp cpe wait timeout ······································································································· 272 cwmp enable ···················································································································· 273 display cwmp configuration ································································································· 273 display cwmp status ··········································································································· 275 ssl client-policy ················································································································· 276
EAA commands ··········································································· 277
action cli ·························································································································· 277 action reboot ···················································································································· 278 action switchover ··············································································································· 279 action syslog ···················································································································· 280 commit ···························································································································· 281 display rtm environment ······································································································ 282 display rtm policy ··············································································································· 282 event cli ··························································································································· 284 event hotplug ···················································································································· 285 event interface ·················································································································· 287 event process ··················································································································· 289 event snmp oid ················································································································· 290 event snmp-notification ······································································································· 291 event syslog ····················································································································· 292 rtm cli-policy ····················································································································· 293 rtm environment ················································································································ 294 rtm scheduler suspend ······································································································· 295 rtm tcl-policy ····················································································································· 296 running-time ····················································································································· 297 user-role ·························································································································· 297
v
Process monitoring and maintenance commands ································ 299
display exception context ···································································································· 299 display exception filepath ···································································································· 304 display kernel deadloop ······································································································ 305 display kernel deadloop configuration ···················································································· 308 display kernel exception ····································································································· 310 display kernel reboot ·········································································································· 313 display kernel starvation ····································································································· 316 display kernel starvation configuration ··················································································· 319 display process ················································································································· 320 display process cpu ··········································································································· 323 display process log ············································································································ 325 display process memory ····································································································· 326 display process memory heap ····························································································· 328 display process memory heap address ·················································································· 329 display process memory heap size ······················································································· 330 exception filepath ·············································································································· 332 monitor kernel deadloop enable ··························································································· 333 monitor kernel deadloop exclude-thread ················································································ 334 monitor kernel deadloop time ······························································································· 335 monitor kernel starvation enable ··························································································· 336 monitor kernel starvation exclude-thread ················································································ 337 monitor kernel starvation time ······························································································ 338 monitor process ················································································································ 339 monitor thread ·················································································································· 344 process core ···················································································································· 348 reset exception context ······································································································· 349 reset kernel deadloop ········································································································· 350 reset kernel exception ········································································································ 351 reset kernel reboot············································································································· 351 reset kernel starvation ········································································································ 352 third-part-process start ······································································································· 353 third-part-process stop ······································································································· 353
Sampler commands ······································································ 355
display sampler ················································································································· 355 sampler ··························································································································· 356
Port mirroring commands ······························································· 358
display mirroring-group ······································································································· 358 mirroring-group ················································································································· 359 mirroring-group mirroring-port (interface view) ········································································ 359 mirroring-group mirroring-port (system view)··········································································· 360 mirroring-group monitor-port (interface view) ·········································································· 361 mirroring-group monitor-port (system view) ············································································ 362
Flow mirroring commands ······························································ 363
mirror-to ·························································································································· 363
NetStream configuration commands ················································· 364
display ip netstream cache ·································································································· 364 display ip netstream export·································································································· 371 display ip netstream template ······························································································ 372 enable ····························································································································· 375 ip netstream ····················································································································· 375 ip netstream filter ··············································································································· 376 ip netstream sampler ········································································································· 377 ip netstream aggregation ···································································································· 377 ip netstream export host ····································································································· 379 ip netstream export rate ······································································································ 380 ip netstream export source ·································································································· 381
vi
ip netstream export v9-template refresh-rate packet ································································· 382 ip netstream export v9-template refresh-rate time ···································································· 382 ip netstream export version ································································································· 383 ip netstream max-entry ······································································································· 384 ip netstream mpls ·············································································································· 385 ip netstream timeout active·································································································· 385 ip netstream timeout inactive ······························································································· 386 reset ip netstream statistics ································································································· 387
IPv6 NetStream commands ···························································· 388
display ipv6 netstream cache ······························································································· 388 display ipv6 netstream export ······························································································ 393 display ipv6 netstream template ··························································································· 394 enable ····························································································································· 398 ipv6 netstream ·················································································································· 398 ipv6 netstream filter ··········································································································· 399 ipv6 netstream sampler ······································································································ 400 ipv6 netstream aggregation ································································································· 400 ipv6 netstream export host ·································································································· 402 ipv6 netstream export rate··································································································· 403 ipv6 netstream export source ······························································································· 403 ipv6 netstream export v9-template refresh-rate packet ····························································· 404 ipv6 netstream export v9-template refresh-rate time ································································· 405 ipv6 netstream export version 9 ··························································································· 406 ipv6 netstream max-entry ···································································································· 406 ipv6 netstream timeout active ······························································································ 407 ipv6 netstream timeout inactive ···························································································· 408 reset ipv6 netstream statistics ······························································································ 408
sFlow commands ········································································· 410
display sflow ····················································································································· 410 sflow agent ······················································································································ 411 sflow collector ··················································································································· 412 sflow counter interval ········································································································· 413 sflow counter collector ········································································································ 414 sflow flow collector············································································································· 414 sflow flow max-header ········································································································ 415 sflow sampling-mode ········································································································· 415 sflow sampling-rate ············································································································ 416 sflow source ····················································································································· 416
Information center commands ························································· 418
diagnostic-logfile save ········································································································ 418 display diagnostic-logfile summary························································································ 418 display info-center ············································································································· 419 display logbuffer ················································································································ 420 display logbuffer summary ·································································································· 422 display logfile summary ······································································································ 424 display security-logfile summary ··························································································· 424 enable log updown ············································································································ 425 info-center diagnostic-logfile directory ··················································································· 426 info-center diagnostic-logfile enable ······················································································ 426 info-center diagnostic-logfile frequency ·················································································· 427 info-center diagnostic-logfile quota························································································ 427 info-center enable·············································································································· 428 info-center format ·············································································································· 428 info-center logbuffer ··········································································································· 429 info-center logbuffer size ····································································································· 430 info-center logfile directory ·································································································· 430 info-center logfile enable ····································································································· 431 info-center logfile frequency ································································································ 431 info-center logfile overwrite-protection ··················································································· 432
vii
info-center logfile size-quota ································································································ 433 info-center logging suppress duplicates ················································································· 433 info-center loghost ············································································································· 435 info-center loghost source ··································································································· 435 info-center security-logfile alarm-threshold ············································································· 436 info-center security-logfile directory ······················································································· 437 info-center security-logfile enable ························································································· 438 info-center security-logfile frequency ····················································································· 438 info-center security-logfile size-quota ···················································································· 439 info-center source·············································································································· 439 info-center synchronous ····································································································· 441 info-center syslog min-age ·································································································· 442 info-center syslog trap buffersize ·························································································· 442 info-center timestamp ········································································································· 443 info-center timestamp loghost ······························································································ 444 info-center trace-logfile quota ······························································································ 445 logfile save ······················································································································· 445 reset logbuffer ·················································································································· 446 security-logfile save ··········································································································· 446 snmp-agent trap enable syslog ···························································································· 447 terminal debugging ············································································································ 447 terminal logging level ········································································································· 448 terminal monitor ················································································································ 449
Flow log commands ······································································ 450
display userlog export ········································································································ 450 reset userlog flow export ····································································································· 451 userlog flow export host ······································································································ 451 userlog flow export load-balancing ························································································ 452 userlog flow export source-ip ······························································································· 453 userlog flow export timestamp localtime ················································································· 453 userlog flow export version ·································································································· 454 userlog flow syslog ············································································································ 455
Document conventions and icons ···················································· 456
Conventions ···························································································································· 456 Network topology icons ············································································································· 457
Support and other resources··························································· 458
Accessing Hewlett Packard Enterprise Support·············································································· 458 Accessing updates ··················································································································· 458
Websites ························································································································· 459 Customer self repair ·········································································································· 459 Remote support ················································································································ 459 Documentation feedback ···································································································· 459
Index ························································································· 461
viii

Ping, tracert, and system debugging commands

debugging

Use debugging to enable debugging for a module. Use undo debugging to disable debugging for a module.
Syntax
debugging module-name [ option ] undo debugging module-name [ option ]
Default
Debugging is disabled for all modules.
Views
User view
Predefined user roles
network-admin
Parameters
module-name: Specifies a module by its name, such as arp or device. For a list of supported modules, use the debugging ? command.
option: Specifies the debugging option for a module. Available options vary by module. T o display the debugging options supported by a module, use the debugging module-name ? command.
Usage guidelines
Output from debugging commands is memory intensive. To guarantee system performance, enable debugging only for modules that are in an exceptional condition.
The system sends the debugging comm and output as debug m essages to the device i nformation center. The information center then sends the m essages to appropri ate destinations based o n the log output configuration. For more information about configuring debug message output, see Network Management and Mon itori ng Conf ig ur ati on Guid e.
Examples
# Enable debugging for the device management module.
<Sysname> debugging dev
Related commands

display debugging

display debugging
Use display debugging to display the enabled debugging features for a module or for all modules.
Syntax
display debugging [ module-name ]
1
Views
Any view
Predefined user roles
network-admin network-operator
Parameters
module-name: S pecifies a module b y its name. For a list of suppor ted modules, use the display debugging ? command. If you do not spec ify a module name, this comm and displays the enab led
debugging features for all modules.
Examples
# Display all enabled debugging features.
<Sysname> disp lay debugging DEV debugging switch is on
Related commands
debugging

ping

Use ping to test the reachability of the destination IP address and disp lay ping statistics.
Syntax
ping [ ip ] [ -a source-ip | -c count | -f | -h ttl | -i interface-type interface-number | -m interval | -n | -p
pad | -q | -r | -s packet-size | -t timeout | -tos tos | -v | { -topology topo-name | -vpn-instance vpn-instance-name } ] * host
Views
Any view
Predefined user roles
network-admin
Parameters
ip: Distinguishes between a destination host name and the ping command keywords if the name of the destination host is i, ip, ipv, or ipv6. For example, you must use the command in the form of ping ip ip instead of ping ip if the destination host name is ip.
-a source-ip: Specifies an IP address of the device as the source IP address of ICMP echo requests.
If this option is not specified, the source IP address of ICMP echo requests is the primary IP address of the outbound interface.
-c count: Specifies the number of ICMP echo req uests 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 in ter fac e -number: Specifies t he s o urc e i nterface for ICMP echo reques ts. If you do not specify this option, the system uses the primary IP address of the matching route's egress interface as the source interface for ICMP echo requests.
-m interval: Specifies the interval (in milliseconds) to send ICMP echo requests. The value range is 1 to 65535, and the default is 200.
2
-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 v alue of the pad field in an ICMP echo request, in hexa deci m al format , 1 to 8 bits. The pad argum ent is in th e ran ge of 0 to ffffffff. If the specified valu e is les s t han 8 b its, 0s are added in front of t he valu e to ex tend it to 8 bits . For exam ple, if pad is conf igure d 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, t he padded value starts from 0x01 up to 0xff, where another round starts again if necessary, such as 0x010203…feff01….
-q: Displays only the summ ar y statistics. If this keyword is not specified , the system displa ys all t he ping statistics.
-r: Records the a ddresses of the hops (up to 9) the ICMP echo requests passed. If this keyword is not specified, the addresses of the hops that the ICMP echo requests passed are not recorded.
-s packet-size: Specifies the length (in bytes) of ICMP echo requests (excluding the IP packet header and the ICMP packet header). The value range is 20 to 8100, and the default is 56.
-t timeout: Specifies the timeout time (in milliseconds) of an ICMP echo reply. The value range is 0 to 65535, and the default is 2000. If the source does not receive an ICMP echo reply within the timeout, it considers the ICMP echo reply timed out.
-tos tos: Specifies the ToS value of ICMP echo requests. The value range is 0 to 255, and the default is 0.
-v: Displays n on-ICMP echo reply packets. If this keyword is not specified, the system does not display non-ICMP echo reply packets .
-topology topo-name: Specifies the topolog y to which the des tin ation bel on gs , wher e topo-name is a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-vpn-instance vpn-instance-name: Spec ifies the MPLS L3VPN instance to which th e destination belongs, where the vpn-instance-name argum ent is a case-s ensitive string of 1 to 31 charac ters. If the destination is on the public network, do not specify this option.
host: Specifies the IP addres s or hos t name of the destination. The hos t 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
T o ping a device identified by its host name, configure the DNS settings on the device first. If the DNS settings are not configured, the ping operation fails.
To abort the ping operation during the execution of the command, press Ctrl+C.
Examples
# Test whether the device with an IP address of 1.1.2.2 is reachable.
<Sysname> ping 1.1.2.2 Ping 1.1.2.2 (1 .1.2.2): 56 data byt es, 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
3
# Test whether the device with an IP address of 1.1.2.2 in VPN 1 is reachable.
Field
Description
(1.1.2.2): 56 data
<Sysname> ping -vpn-instance vpn1 1.1.2.2 Ping 1.1.2.2 (1 .1.2.2): 56 data byt es, 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 byt es, 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.6 65/0.244 ms
# Test whether the devic e with an IP addres s of 1.1.2.2 is reachable. The IP address es of t he h ops 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 byt es, 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
Ping 1.1.2.2 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.
4
Field
Description
Received ICMP echo replies
from the device whose IP address is
, used to determine whether a
displayed in inversed order, which means the router with a smaller
dev =
tandard deviation response time, in
1.1.2.2. If no echo reply is received within the timeout period, no information is displayed.
56 bytes from 1.1.2.2: icmp_ se q=0 ttl=254 time=4.685 ms
RR:
--- Ping statistics for 1.1.2.2 --- Statistics on data received and sent in the ping operation.
bytes—Number of bytes in the ICMP echo reply.
icmp_seq—Packet sequence
segment is lost, disordered or repeated.
ttl—TTL value in the ICMP echo reply.
time—Response time.
Routers through which the ICMP echo request passed. They are distance to the destination is displayed first.
--- Ping statistics for 1.1.2.2 in VPN instance vpn1 ---
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-
4.685/4.761/4.834/0.058 ms

ping ipv6

Use ping ipv6 to test the reachability of the destination IPv6 address and display IPv6 ping statistics.
Syntax
ping ipv6 [ -a source-ipv6 | -c count | -i interface-type interface-number | -m interval | -q | -s packet-size | -t timeout | -tc traffic-class| -v | -vpn-instance vpn-instance-name ] * host
Views
Any view
Predefined user roles
network-admin
Ping statistics for a device in a VPN instance.
Minimum/average/maximum/s milliseconds.
Parameters
-a source-ipv6: Specifies an IPv6 addres s of the device as the source I P address of ICMP echo
requests. If this opt ion is n ot specif ied, th e sour ce IP v6 ad dress of ICMP ech o reques ts is t he I Pv6 address of the outbound interface. See RFC 3484 for information about the address selection rule.
-c count: Specifies the number of ICMPv6 echo requests that are sent to the destination. The value range is 1 to 4294967295, and the default is 5.
-i interface-type interface-number: Specifies the source interface f or 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 specif y this option, the system uses the primary IP address of the m atching 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 s umm ar y statistics. If you do not specif y this k e yword, the s ys tem displays all the ping statistics.
5
-s packet-size: Specifies the length (in b yt es) of ICMPv6 echo re quests (excluding the IP v6 pac ket 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 t he traffic class val ue in an IC MPv6 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 k eyword is n ot specif ied, the s ystem only displays brief inform ation ( not includ ing the
dst field and the idx field) about ICMPv6 echo replies.
-vpn-instance vpn-instance-name: Spec ifies the MPLS L3VPN instance to which th e destination
belongs, where the vpn-instance-name argum ent is a case-s ensitive string of 1 to 31 charac ters. 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 le tters, digits, and special characters such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
T o ping a device identified by its host name, configure the DNS settings on the device first. If the DNS settings are not configured, the ping ipv6 operation fails.
To abort the ping ipv6 operation during the execution of the command, press Ctrl+C.
Examples
# Test whether the IPv6 address (2001::2) is reachable.
<Sysname> pi ng ipv6 2001::2 Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C to break 56 bytes from 2001::2, icmp_se q=0 hlim=64 time=62 .000 ms 56 bytes from 2001::2, icmp_se q=1 hlim=64 time=23 .000 ms 56 bytes from 2001::2, icmp_se q=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_se q=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 ip v6 –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 ip v6 –v 2001::2 Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C to break 56 bytes from 2001::2, icmp_se q=0 hlim=64 dst=200 1::1 idx=3 time=6 2.000 ms 56 bytes from 2001::2, icm p_seq=1 hlim=64 ds t=2001::1 idx=3 time=23.000 ms 56 bytes from 2001::2, icmp_se q=2 hlim=64 dst=200 1::1 idx=3 time=2 0.000 ms 56 bytes from 2001::2, icmp_se q=3 hlim=64 dst=200 1::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
6
Field
Description
icmp_seq=1 hlim=64 dst=2001::1
tandard deviation response time, in
--- 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
Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C
to break
56 bytes from 2001::2,
idx=3 time=62.000 ms
--- Ping6 statistics for 2001::2 ------ Statistics on data received and sent in an IPv6 p ing oper atio n. 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
An ICMPv6 echo reply with a data length of 56 bytes is sent from 2001::1 to 2001::2.
Ctrl+C
Press Received ICMPv6 echo replies from the dev ice 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.
Minimum/average/maximum/s milliseconds.
to abort the ping IPv6 operation.

tracert

Use tracert to trace the path the packets traverse from source to destination.
Syntax
tracert [ -a source-ip | -f first-ttl | -m max-ttl | -p port | -q packet-number | -t tos | { -topology
topo-name |-vpn-instance vpn-instance-name [ -resolve-as { global | none | vpn } ] } | -w timeout ] * host
Views
Any view
Predefined user roles
network-admin
Parameters
-a source-ip: Specifies an IP address of the device as the source IP address of probe packets. If this
option is not specified, the source IP address of probe packets is the primary IP address of the outbound interface.
7
-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: Spec ifies an invalid UDP port of the des tination. The value range is 1 to 65535, and the default is 33434. If the destinat ion addres s is a n EID a ddress at a rem ote LISP sit e, spec ify a por t number in the range of 33434 to 65535.
-q packet-number: Specifies the num ber of probe packets to send per hop. The valu e range is 1 to 65535, and the default is 3.
-t tos: Specifies the ToS value of probe packets. The value range is 0 to 255, and the default is 0.
-topology topo-name: Specifies the topolog y to which the des tin ation bel on gs , wher e topo-name is
a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-vpn-instance vpn-instance-name: Spec ifies the MPLS L3VPN instance to which th e destination belongs, where the vpn-instance-name argument is a c ase-sensiti ve st ring of 1 to 31 c haracter s. If the destination is on the public network, do not specify this option.
-resolve-as: Specifies a routing table for autonomous system (AS) resolution. Tracert searches the specified routing tabl e f or the A S t hat eac h h op a lo ng the p ath bel on gs to. If you do no t s pec i fy th i s keyword, the global rout ing tab le is used. If the AS info rmation is found, this command displays the AS number next to the address of the hop in the probe result.
global: Specifies the global routing table. none: Disables AS resolution. vpn: Specifies the VPN routing table.
-w timeout: Specifies th e timeout time in milliseconds of the reply packet for a probe packet. The
value range is 1 to 65535, and the def ault is 5000. host: Specifies the IP addres s or hos t name of the destination. The hos t 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 netw ork failure with t he ping command, use th e tracert command to locate failed nodes.
If the destination address is on the public network, you do not need to specify the -resolve-as keyword to obtain the AS information. The device automatically uses the global routing table for AS resolution.
If the destination address is on a private network, address information of intermediate hops might be stored in either the global routing table or t he VPN routing table. To learn the AS path that the packets traverse, ex ecute the tracert com m and twice, once with t he -resolve-as global keywords and again with the -resolve-as vpn keywords.
The output from the tracert command includes IP addresses of all the Layer 3 dev ices that the packets traverse from source to destination. Asterisks (* * *) are displayed if the device cannot reply with an ICMP error mess age. T he reas on might be the destin ati on is unr eac h ab le 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
8
1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms
Field
Description
LS Label=100048 Exp=0
on an MPLS network, carrying MPLS label
Label value that is used to identify a forwarding equivalence
2 1.1.2.2 (1.1.2.2) [AS 100] 580 ms 470 ms 80 ms
# Display the path that the packets traverse from sour ce to destination (1.1.3.2) in VPN ins tance vpn1, as well as the AS information of the hops along the path.
<Sysname> tr acert –vpn-instanc e vpn1 –resolve-as vpn 1.1.3.2 traceroute to 1.1.3.2 (1.1.3.2), 30 hops at most, 40 bytes each packet, press CTRL_C to
break 1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms 2 1.1.2.2 (1.1.2.2) 580 ms 470 ms 80 ms 3 1.1.3.2 (1.1.3.2) [AS 65535] 530 ms 472 ms 380 ms
# Trace the path to destination (192.168.0.46) over an MPLS network.
<Sysname> tracert 192.168.0.46 traceroute to 1 92 .168.0.46(192.168.0.46), 30 hops at most, 40 bytes each packe t, press
CTRL_C to break 1 192.0.2.13 (192 .0.2.13) 0.661 ms 0.61 8 ms 0. 57 9 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 .70 8 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 .87 5 ms
Table 3 Command output
traceroute to 1.1.2.2 (1.1.2.2)
hops at most
Display the route that the IP packets tr averse from the curr ent device t o th e device whose IP address is 1.1.2.2.
Maximum number of hops of th e probe packet s, 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 operation.
Probe result of the probe packets that contain a TTL value of 2, including the following information about the second hop:
Domain name of the hop. If no domain name is configured, the IP address is displayed as the domain name.
2 1.1.2.2 (1.1.2.2) [AS 100] 580 ms 470 ms 80 ms
IP address of the hop. The IP addr e ss is dis play ed in pare nt hese s.
Number of the AS that the hop belongs to. The AS number appears
only when it is found for the hop in the specified routing table.
The round-trip time of the probe packets.
The number of packets that can be sent in each probe can be set by using
-q
the
keyword.
ICMP timeout packets information:
Label
MP TTL=1 S=1
class (FEC).
Exp—Reserved, usually used for class of service (CoS).
TTL—TTL value.
S—MPLS supports multiple le v els of la bel s. Value 1 indicates that the
label is at t he bo t tom of th e l abe l s t ac k, and va l u e 0 i ndic a t es th at t he label is in another label stack.
Ctrl+C
to abort the tracert
9

tracert ipv6

Use tracert ipv6 to display the path that the IPv6 packets traverse from source to destination.
Syntax
tracert ipv6 [ -f first-hop | -m max-hops | -p port | -q packet-number | -t traffic-class | -vpn-instance vpn-instance-name [ -resolve-as { global | none | vpn } ] | -w timeout ] * host
Views
Any view
Predefined user roles
network-admin
Parameters
-f first-hop: Specifies the TTL value of the first packet. The value range is 1 to 255, and the default is
1. The value must be no greater than the value of the max-hops argument.
-m max-hops: Specifies the maximum number of hops allowed for a packet. The value range is 1 to 255, and the default is 30. The value must be no smaller than the value of the first-hop argument.
-p port: Spec ifies an invalid UDP port of the des tination. The value range is 1 to 65535, and the default is 33434.
-q packet-number: Specifies the num ber of probe pac kets s ent each time. T he value range is 1 to 65535, and the default is 3.
-t traffic-class: Specifies the traffic class value in an IPv6 probe packet. The value range is 0 to 255, and the default is 0.
-vpn-instance vpn-instance-name: Spec ifies the MPLS L3VPN instance t o which the destination belongs, where the vpn-instance-name argument is a c ase-sensiti ve st ring of 1 to 31 c haracter s. If the destination is on the public network, do not specify this option.
-resolve-as: Specifies a routing table for AS resolution. Tracert searches the specified routing table for the AS that each hop a long the path belongs to . If you do not specif y this keyword, the glob al routing table is used. If t he AS infor mation is f ound, this command dis plays the A S number nex t to the address of the hop in the probe result.
global: Specifies the global routing table. none: Disables AS resolution. vpn: Specifies the VPN routing table.
-w timeout: Specifies the ti meout time (in milliseconds) of the reply packet of a probe packet. T he
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 le tters, digits, and special characters such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping ipv6 command, you can use the tracert ipv6 command to locate failed nodes.
If the destination address is on the public network, you do not need to specify the -resolve-as keyword to obtain the AS information. The device automatically uses the global routing table for AS resolution.
If the destination address is on a private network, address information of intermediate hops might be stored in either the global routing table or t he VPN routing table. To learn the AS path that the packets traverse, execute the tracert ipv6 command twice, once with the -resolve-as global keywords and again with the -resolve-as vpn keywords.
10
The output from the tracert ipv6 command includes IP v6 address es of all the La yer 3 de vices that
Field
Description
Number of the AS the hop belongs to. The AS number appears
the packets traverse from source to destina tion. Aster isks (* * *) are displa yed if the d evice ca nnot reply with an ICMP error message. T he reason might be the des tination is unr eachabl e 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> tr acert 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.61 8 ms 0.579 ms 2 2001:2::2 [AS 100] 0.861 ms 0.718 ms 0.679 ms 3 2001:3::2 [AS 200] 0.822 ms 0.73 1 ms 0.708 ms
# Display the path that the packets traverse fr om source to dest ination (2001:3::2) in VPN instanc e vpn1, as well as the AS information of the hops along the path.
<Sysname> tr acert ipv6 –vpn-instance vpn1 –resolve-as vp n 2001:3::2 traceroute to 20 01: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.86 1 ms 0.718 ms 0.679 ms 3 2001:3::2 [AS 6553 5] 0.822 ms 0.731 ms 0.7 08 ms
Table 4 Command output
traceroute to 2001:3::2
hops at most
byte packets Number of bytes of a probe packet.
2 2001:2::2 [AS 100] 0.861 ms
0.718 ms 0.679 ms
Display the route that the IPv6 packets traverse from th e curr ent dev ice to the device whose IP address is 2001:3:2.
Maximum number of hops of t he probe pa ckets, which can be set by the
-m
keyword.
Probe result of the probe packets that contain a hoplimit value of 2, including the following information about the second hop:
IPv6 address of the hop.
only when it is found for the hop in the specified routing table.
The round-trip time of the probe packets. The number of packets that can be sent in each probe can be set by
using the
-q
keyword.
11

NQA commands

NQA client commands

advantage-factor

Use advantage-factor to set the advantage f actor to be used for calculating 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
Parameters
factor: Specifies the advantage factor in the range of 0 to 20.
Usage guidelines
The evaluat ion of voice quality depends on users ' tolerance for voice qua lity. For users with higher tolerance for voice quali ty, use the advantage-factor command to set an advant age factor. When the system calculat es the ICPIF value, it subtracts the ad vantage f actor to m odif y ICPIF a nd MO S values for voice quality evaluation.
Examples
# Set the advantage factor to 10 for the voice operation.
<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type voice [Sysname-nqa-admin-test-voice] ad vantage-factor 10

codec-type

Use codec-type to configure the codec type for the voice operation.
Syntax
Default
Use undo codec-type to restore the default.
codec-type { g711a | g711u | g729a } undo codec-type
The codec type for the voice operation is G.711 A-law.
12
Views
Voice operation view
Predefined user roles
network-admin
Parameters
g711a: Specifies G.711 A-law codec type. g711u: Specifies G.711 µ-law codec type g729a: Specifies G.729 A-law codec type.
Examples
# Set the codec type to g729a for the voice operation.
<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type voice [Sysname-nqa-admin-test-voice] codec-type g729a

data-fill

Use data-fill to configure the payload fill string for probe packets. Use undo data-fill to restore the default.
Syntax
data-fill string undo data-fill
Default
The default payload fill string is 0123456789.
Views
ICMP/UDP echo operation view Path/UDP jitter operation view Voice operation view
Predefined user roles
network-admin
Parameters
string: Specifies a case-sensitive string of 1 to 200 characters.
Usage guidelines
If the payload length is smaller than the string len gth, only the first part of the str ing is filled. For example, if you configure the string as abcd and set the payload size to 3 bytes, abc is filled.
If the payload leng th is greater than the str ing length, the s ystem fills the payload with th e string cyclicall y until the p ayload is full. For example, if you conf igure the st ring as abcd and the pa yload size as 6 bytes, abcdab is filled.
How the string is filled depends on the operation type.
For the ICMP echo operation, the string fills the whole payload of an ICMP echo request. For the UDP echo operation, the first five bytes of the payload of a UDP packet are for special
purpose. The string fills the remaining part of payload.
13
Operation type
Codec type
Default size (bytes)
For the UDP jitter operation, the first 68 bytes of the payload of a UDP packet are for special
purpose. The string fills the remaining part of the payload.
For the voice operation, the first 16 bytes of the payload of a UDP packet are for special
purpose. The string fills the remaining part of the payload.
For the path jitter operation, the first four bytes of the payload of an ICMP echo request are for
special purpose. The string fills the remaining part of payload.
Examples
# Specify abcd as the payload fill string for ICMP echo requests.
<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] data-fill abcd

data-size

Use data-size to set the payload size for each probe packet. Use undo data-size to restore the default.
Syntax
data-size size
Default
Views
undo data-size
The default payload size of a probe packet for different operations is described in Table 5.
Table 5 Default payload size of a probe packet
ICMP echo N/A 100 UDP echo N/A 100 UDP jitter N/A 100 UDP tracert N/A 100 Path jitter N/A 100 Voice G.711 A-law 172 Voice G.711 µ-law 172 Voice G.729 A-law 32
ICMP/UDP echo operation view Path/UDP jitter operation view
Predefined user roles
UDP tracert operation view Voice operation view
network-admin
14
Parameters
size: Specifies the payload size. Available value ranges include:
20 to 65507 bytes for the ICMP echo, UDP echo, or UDP tracert operation. 68 to 65507 bytes for the UDP jitter or path jitter operation. 16 to 65507 bytes for the voice operation.
Usage guidelines
In ICMP echo and path jitter operations, the com mand sets the payload s ize for each ICMP echo request.
In UDP echo, UDP jitter, UDP tracert, and voice operations , t he c om mand sets the payload s ize f or each UDP packet.
Examples
# Set the payload size to 80 bytes for each ICMP echo request.
<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] data-size 80

description

Use description to configure a description for an NQA operation, such as the operation type or purpose.
Use undo description to restore the default.
Syntax
description text undo description
Default
No description is configured for an NQA operation.
Views
DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view ICMP/UDP echo operatio n vie w ICMP/path/UDP jitter operation view UDP tracert operation view
Predefined user roles
network-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 200 characters.
Examples
# Configure the description as icmp-probe for the ICMP echo operation.
<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] description icmp-probe
15

destination ip

Use destination ip to configure the destination IPv4 address for the operation. Use undo destination ip to restore the default.
Syntax
destination ip ip-address undo destination ip
Default
No destination IPv4 address is configured for an operation.
Views
DHCP/DLSw/DNS/SNMP/TCP/voice operation view ICMP/UDP echo operation view ICMP/path/UDP jitter operation view UDP tracert operation view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the destination IPv4 address for the operation.
Examples
# Specify 10.1.1.1 as the destination IPv4 address for the ICMP echo operation.
<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] destination ip 10.1.1.1

destination ipv6

Use destination ipv6 to configure the destination IPv6 address for the operation. Use undo destination ipv6 to restore the default.
Syntax
destination ipv6 ipv6-address undo destination ipv6
Default
No destination IPv6 address is configured for an operation.
Views
ICMP echo operation view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the destination IPv6 address for the operation. IPv6 link-local addresses are not supported.
16
Examples
# In ICMP echo operation view , specify 1::1 as the destination IPv6 address for ICMP echo requests.
<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] destination ipv6 1::1

destination por t

Use destination port to configure the destination port number for the operation. Use undo destination port to restore the default.
Syntax
destination port port-number undo destination port
Default
The destination port number is 33434 for the UDP tracert operation. No destination port number is configured for other types of operations.
Views
TCP/voice operation view UDP echo operation view UDP jitter operat ion vie w UDP tracert operation view
Predefined user roles
network-admin
Parameters
port-number: Specifies the destination port number for the operation, in the range of 1 to 65535.
Examples
# Set the destination port number to 9000 for the UDP ec ho operation.
<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type udp-echo [Sysname-nqa-admin-test-udp-echo] destination port 900 0

display nqa hist ory

Use display nqa history to display the history records of NQA operations.
Syntax
display nqa history [ admin-name operation-tag ]
Views
Any view
Predefined user roles
network-admin
17
network-operator
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argum ent represents the operation ta g. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-). If you do not specify an NQA operation, the command displays the history records of all NQA operations.
Usage guidelines
The display nqa history command does not display the results or statistics of the following operations:
ICMP jitter. Path jitter. UDP jitter. Voice.
T o v iew the results or statistics of the ICMP jitter, path jitter, UDP jitter, and voice operations, use the
display nqa result or display nqa statistics command.
Examples
# Display the histor y records of the UDP tracert oper ation with adminis trator name administrator and operation tag tracert.
<Sysname> display nqa history administrator tracert NQA entry (adm in administrator, tag tracert) history records: Index TTL Response Hop IP Status Time 1 2 328 4.1.1.1 Succeeded 2013-09-09 14:46:06.2 1 2 328 4.1.1.1 Succeeded 2013-09-09 14:46:05.2 1 2 328 4.1.1.1 Succeeded 2013-09-09 14:46:04.2 1 1 328 3.1.1.2 Succeeded 2013-09-09 14:46:03.2 1 1 328 3.1.1.1 Succeeded 2013-09-09 14:46:02.2 1 1 328 3.1.1.1 Succeeded 2013-09-09 14:46:01.2
# Display the history records of the NQA operation with administrator name administrator and operation tag test.
<Sysname> display nqa history administrator test NQA entry (admin administrator, tag test) history records: Index Response Status Time 10 329 Succeeded 2011-04-29 20:54:26.5 9 344 Succeeded 2011-04-29 20:54:26.2 8 328 Succeeded 2011-04-29 20:54:25.8 7 328 Succeeded 2011-04-29 20:54:25.5 6 328 Succeeded 2011-04-29 20:54:25.1 5 328 Succeeded 2011-04-29 20:54:24.8 4 328 Succeeded 2011-04-29 20:54:24.5 3 328 Succeeded 2011-04-29 20:54:24.1 2 328 Succeeded 2011-04-29 20:54:23.8 1 328 Succeeded 2011-04-29 20:54:23.4
18
Table 6 Command output
Field Description
Index
TTL TTL value in the probe packet.
Response
Hop IP IP address of the node that sent the reply packet.
Status
Time Time when the operation was completed.
History record ID. The history records in one UDP tracert operation have the same ID.
Round-trip time if the operation succeeds, timeout time upon timeout, or 0 if the operation cannot be complete d, in milliseconds.
Status of the operation result:
Succeeded.
Unknown error.
Internal error.
Timeout.

display nqa reaction counters

Use display nqa reaction counters to display the current monitoring results of reaction entries.
Syntax
display nqa reaction counters [ admin-name operation-tag [ item-number ] ]
Views
Any view
Predefined user roles
network-admin network-operator
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argum ent represents the operation ta g. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-). If you do not specify an NQA operation, the command displ a ys t he c urr ent monitoring results of reac t ion entries f or a ll NQA operations.
item-number: Specif ies a reaction entry by its ID in the range of 1 to 10. If you do not spec ify a reaction entry, the command displays the results of all reaction entries.
Usage guidelines
The result fields display hyphens (-) in one of the following conditions:
The threshold type is the average value. The monitored performance metric is ICPIF or MOS of the voice operation.
The monitoring res ults of an operation are accum ulated, and are not cleared a fter the operation completes.
Examples
# Display the monitoring results of all reaction entries of the ICMP echo operation with administrator name admin and operation tag test.
19
Field
Description
been monitored for data
metric
robes after the
umber of
Number of probes with duration exceeding the
robes after the
umber of
Number of probes with duration exceeding the
robes after the
umber of
robes after the
umber of
ackets sent
after the
Number of sent
Number of packets with
ackets sent
after the
Number of sent
Number of packets with
way jitter
ackets sent
after the
Number of sent
way delay
ackets sent
after the
Number of sent
<Sysname> di splay nqa reaction counters admin tes t NQA entry (adm in admin, tag test) reaction counters: Index Checked Element Threshold Type Checked Num Over-threshold Num 1 probe-duration accumulate 12 4 2 probe-duration average - ­ 3 probe-duration consecutive 160 56 4 probe-fail accumulate 12 0 5 probe-fail consecutive 162 2
Table 7 Command output
Index ID of a reaction entry. Checked Element Monitored performance metric. Threshold Type Threshold type.
Checked Num
Over-threshold Num Number of threshold violations.
Number of targets that have collection.
Table 8 Description of the threshold monitoring fields
Monitored performance
probe-duration
probe-fail
RTT
Threshold type
accumulate
average N/A N/A N/A
consecutive
accumulate
consecutive
accumulate
Collect data in Checked Num Over-threshold Num
P operation starts.
P operation starts.
P operation starts.
P operation starts.
P operation starts.
N completed probes.
N completed probes.
N completed probes.
N completed probes.
packets.
threshold.
threshold.
Number of probe failures.
Number of probe failures.
round-trip time exceeding threshold.
jitter-DS/jitter-SD
OWD-DS/OWD-SD N/A
packet-loss accumulate
average N/A N/A N/A
accumulate
average N/A N/A N/A
P operation starts.
P operation starts.
P operation starts.
20
packets.
packets.
packets.
the one­exceeding the threshold.
Number of packets with the one­exceeding the threshold.
Total packet loss.
Loading...
+ 445 hidden pages