HPE MSR2004-48, MSR1002-4, MSR958, MSR2004-24, MSR3024 Command Reference Manual

...
HPE FlexNetwork MSR Router Series
Comware 7 Network Management and Monitoring Command Reference
Part number: 5998-8765 Software version: CMW710-E0407 Document version: 6W100-20160526
© 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 acco mpanying such products and services. Nothing herein should be construe d as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions co ntained herein.
Confidential computer software. V alid 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 T e chnical 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 In corporated. 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 ··············································································································· 2 ping ·································································································································· 2 ping ipv6 ···························································································································· 6 tracert ······························································································································· 8 tracert ipv6 ······················································································································· 11
NQA commands ············································································ 14
NQA client commands ·············································································································· 14
advantage-factor ··············································································································· 14 codec-type ······················································································································· 14 data-fill ···························································································································· 15 data-size ························································································································· 16 description ······················································································································· 18 destination ip ···················································································································· 18 destination ipv6 ················································································································· 19 destination port ················································································································· 20 display nqa history ············································································································· 20 display nqa reaction counters ······························································································· 22 display nqa result ·············································································································· 24 display nqa statistics ·········································································································· 31 filename ·························································································································· 40 frequency ························································································································ 41 history-record enable ········································································································· 42 history-record keep-time ····································································································· 42 history-record number ········································································································ 43 init-ttl ······························································································································ 44 lsr-path ···························································································································· 45 max-failure ······················································································································· 45 mode ······························································································································ 46 next-hop ip ······················································································································· 47 next-hop ipv6 ···················································································································· 47 no-fragment enable ············································································································ 48 nqa································································································································· 49 nqa agent enable ·············································································································· 49 nqa schedule ···················································································································· 50 operation (FTP operation view) ···························································································· 51
i
operation (HTTP operation view) ·························································································· 52 out interface ····················································································································· 53 password ························································································································· 54 probe count ······················································································································ 55 probe packet-interval ·········································································································· 56 probe packet-number ········································································································· 57 probe packet-timeout ········································································································· 58 probe timeout ··················································································································· 59 raw-request ······················································································································ 60 reaction checked-element { jitter-ds | jitter-sd } ········································································· 60 reaction checked-element { owd-ds | owd-sd } ········································································· 62 reaction checked-element icpif ····························································································· 63 reaction checked-element mos ····························································································· 64 reaction checked-element packet-loss ··················································································· 66 reaction checked-element probe-duration ··············································································· 67 reaction checked-element probe-fail (for trap) ·········································································· 69 reaction checked-element probe-fail (for trigger) ······································································ 70 reaction checked-element rtt ································································································ 71 reaction trap ····················································································································· 73 rresolve-target ·················································································································· 74 route-option bypass-route ··································································································· 75 source interface ················································································································ 75 source ip ························································································································· 76 source ipv6 ······················································································································ 77 source port ······················································································································· 78 statistics hold-time ············································································································· 79 statistics interval ················································································································ 80 statistics max-group ··········································································································· 80 target-only ······················································································································· 81 tos·································································································································· 82 ttl ··································································································································· 82 type ································································································································ 83 url ·································································································································· 84 username ························································································································ 85 version ···························································································································· 86 vpn-instance ····················································································································· 86
NQA server commands ············································································································· 87
display nqa server ············································································································· 87 nqa server enable ·············································································································· 88 nqa server tcp-connect ······································································································· 89 nqa server udp-echo ·········································································································· 90
ii
NTP commands ············································································· 92
display ntp-service ipv6 sessions ·························································································· 92 display ntp-service sessions ································································································ 97 display ntp-service status ·································································································· 101 display ntp-service trace ··································································································· 103 ntp-service acl ················································································································ 104 ntp-service authentication enable ························································································ 106 ntp-service authentication-keyid ························································································· 106 ntp-service broadcast-client ······························································································· 107 ntp-service broadcast-server ······························································································ 108 ntp-service dscp ·············································································································· 109 ntp-service enable ··········································································································· 110 ntp-service inboundenable ································································································ 110 ntp-service ipv6 acl ·········································································································· 111 ntp-service ipv6 dscp ······································································································· 112 ntp-service ipv6 inbound enable ························································································· 113 ntp-service ipv6 multicast-client ·························································································· 114 ntp-service ipv6 multicast-server ························································································· 115 ntp-service ipv6 source ····································································································· 116 ntp-service ipv6 unicast-peer ····························································································· 117 ntp-service ipv6 unicast-server ··························································································· 118 ntp-service max-dynamic-sessions ······················································································ 120 ntp-service multicast-client ································································································ 121 ntp-service multicast-server ······························································································· 121 ntp-service refclock-master ································································································ 123 ntp-service reliable authentication-keyid ··············································································· 124 ntp-service source ··········································································································· 125 ntp-service unicast-peer ···································································································· 126 ntp-service unicast-server ································································································· 127
SNTP commands ········································································· 129
display sntp ipv6 sessions ································································································· 129 display sntp sessions ······································································································· 130 sntp authentication enable ································································································· 130 sntp authentication-keyid ·································································································· 131 sntp enable ···················································································································· 132 sntp ipv6 unicast-server ···································································································· 133 sntp reliable authentication-keyid ························································································ 134 sntp unicast-server ·········································································································· 135
iii
PoE commands ··········································································· 137
apply poe-profile ············································································································· 137 apply poe-profile interface ································································································· 138 display poe device ··········································································································· 139 display poe interface ········································································································ 141 display poe interface power ······························································································· 143 display poe power-usage ·································································································· 144 display poe pse ··············································································································· 147 display poe pse interface ·································································································· 149 display poe pse interface power ························································································· 151 display poe-power ··········································································································· 152 display poe-profile ··········································································································· 156 display poe-profile interface ······························································································· 157 poe disconnect ··············································································································· 158 poe enable ····················································································································· 159 poe enable pse ··············································································································· 160 poe legacy enable ··········································································································· 160 poe max-power ··············································································································· 161 poe max-power (system view) ···························································································· 162 poe pd-description ··········································································································· 162 poe pd-policy priority ········································································································ 163 poe priority ····················································································································· 164 poe priority (system view) ·································································································· 165 poe pse-policy priority ······································································································ 166 poe update ····················································································································· 166 poe-profile ····················································································································· 167 poe utilization-threshold ···································································································· 168
SNMP commands ········································································ 170
display snmp-agent community ·························································································· 170 display snmp-agent context ······························································································· 172 display snmp-agent group ································································································· 172 display snmp-agent local-engineid ······················································································ 174 display snmp-agent mib-node ···························································································· 174 display snmp-agent mib-view ····························································································· 180 display snmp-agent remote ······························································································· 182 display snmp-agent statistics ····························································································· 183 display snmp-agent sys-info ······························································································ 185 display snmp-agent trap queue ·························································································· 186 display snmp-agent trap-list ······························································································· 186 display snmp-agent usm-user ···························································································· 187 enable snmp trap updown ································································································· 189
iv
snmp-agent ···················································································································· 190 snmp-agent calculate-password ························································································· 191 snmp-agent community ···································································································· 192 snmp-agent community-map ······························································································ 195 snmp-agent context ········································································································· 196 snmp-agent group ··········································································································· 197 snmp-agent local-engineid ································································································ 199 snmp-agent log ··············································································································· 200 snmp-agent mib-view ······································································································· 201 snmp-agent packet max-size ····························································································· 202 snmp-agent port ·············································································································· 203 snmp-agent remote ·········································································································· 204 snmp-agent { inform | trap } source ······················································································ 205 snmp-agent sys-info contact ······························································································ 206 snmp-agent sys-info location ····························································································· 207 snmp-agent sys-info version ······························································································ 207 snmp-agent target-host ····································································································· 208 snmp-agent trap enable ···································································································· 211 snmp-agent trap if-mib link extended ··················································································· 212 snmp-agent trap life ········································································································· 213 snmp-agent trap log ········································································································· 213 snmp-agent trap queue-size ······························································································ 214 snmp-agent usm-user { v1 | v2c } ························································································ 215 snmp-agent usm-user v3 ·································································································· 217 snmp-agent usm-user v3 user-role ······················································································ 222
RMON commands ········································································ 224
display rmon alarm ·········································································································· 224 display rmon event ·········································································································· 225 display rmon eventlog ······································································································ 227 display rmon history ········································································································· 228 display rmon prialarm ······································································································· 231 display rmon statistics ······································································································ 233 rmon alarm ···················································································································· 235 rmon event ····················································································································· 237 rmon history ··················································································································· 239 rmon prialarm ················································································································· 240 rmon statistics ················································································································ 242
Event MIB commands ··································································· 244
action ···························································································································· 244 comparison ···················································································································· 245 context (action-set view) ··································································································· 246
v
context (trigger view) ········································································································ 247 delta falling ···················································································································· 247 delta rising ····················································································································· 248 description (event view) ···································································································· 249 description (trigger view) ··································································································· 250 display snmp mib event ···································································································· 251 display snmp mib event event ···························································································· 252 display snmp mib event object list ······················································································· 254 display snmp mib event summary ······················································································· 255 display snmp mib event trigger ··························································································· 256 event enable ·················································································································· 259 event owner (trigger-Boolean view) ····················································································· 260 event owner (trigger-existence view)···················································································· 260 falling ···························································································································· 261 frequency ······················································································································ 262 object list (action-notification view) ······················································································ 263 object list (trigger view) ····································································································· 264 object list (trigger-Boolean view) ························································································· 265 object list (trigger-existence view) ······················································································· 266 object list (trigger-threshold view) ························································································ 266 oid (action-notification view) ······························································································· 267 oid (action-set view) ········································································································· 268 oid (trigger view) ············································································································· 269 rising ···························································································································· 269 sample ·························································································································· 270 snmp mib event ·············································································································· 271 snmp mib event object list ································································································· 272 snmp mib event sample instance maximum ·········································································· 273 snmp mib event sample minimum ······················································································· 274 snmp mib event trigger ····································································································· 275 snmp-agent trap enable event-mib ······················································································ 276 startup (trigger-existence view) ··························································································· 276 startup (trigger-threshold view) ··························································································· 277 startup enable ················································································································· 278 test ······························································································································· 279 trigger enable ················································································································· 280 type ······························································································································ 281 value (action-set view) ······································································································ 282 value (trigger-Boolean view) ······························································································ 282 wildcard context (action-set view)························································································ 283 wildcard context (trigger view) ···························································································· 284 wildcard oid (action-set view) ····························································································· 285 wildcard oid (trigger view) ·································································································· 286
vi
NETCONF commands ·································································· 287
netconf log ····················································································································· 287 netconf soap http acl ········································································································ 288 netconf soap http enable ··································································································· 289 netconf soap https acl ······································································································ 290 netconf soap https enable ································································································· 290 netconf ssh server enable ································································································· 291 netconf ssh server port ····································································································· 292 xml ······························································································································· 292
CWMP commands ······································································· 294
cwmp ···························································································································· 294 cwmp acs default password ······························································································· 294 cwmp acs default url ········································································································ 295 cwmp acs default username ······························································································ 296 cwmp acs password ········································································································· 297 cwmp acs url ·················································································································· 298 cwmp acs username ········································································································ 299 cwmp cpe connect interface ······························································································ 299 cwmp cpe connect retry ···································································································· 300 cwmp cpe inform interval ·································································································· 301 cwmp cpe inform interval enable ························································································· 302 cwmp cpe inform time ······································································································ 302 cwmp cpe password ········································································································ 303 cwmp cpe provision-code ·································································································· 304 cwmp cpe stun enable ······································································································ 305 cwmp cpe username ········································································································ 306 cwmp cpe wait timeout ····································································································· 307 cwmp enable ·················································································································· 307 display cwmp configuration ································································································ 308 display cwmp status ········································································································· 309 ssl client-policy ··············································································································· 311
EAA commands ··········································································· 312
action reboot ·················································································································· 313 action switchover ············································································································· 315 action syslog ·················································································································· 316 commit ·························································································································· 317 display rtm environment ···································································································· 318 display rtm policy ············································································································· 318 event cli ························································································································· 320
vii
event hotplug ·················································································································· 321 event interface ················································································································ 323 event process ················································································································· 326 event snmp oid ··············································································································· 327 event snmp-notification ····································································································· 329 event syslog ··················································································································· 330 rtm cli-policy ··················································································································· 331 rtm environment ·············································································································· 332 rtm scheduler suspend ····································································································· 334 rtm tcl-policy ··················································································································· 334 running-time ··················································································································· 335 user-role ························································································································ 336
Process monitoring and maintenance commands ································ 338
display exception context ·································································································· 338 display exception filepath ·································································································· 343 display kernel deadloop ···································································································· 344 display kernel deadloop configuration ·················································································· 348 display kernel exception ···································································································· 349 display kernel reboot ········································································································ 353 display kernel starvation ··································································································· 356 display kernel starvation configuration·················································································· 359 display process ··············································································································· 361 display process cpu ········································································································· 364 display process log ·········································································································· 366 display process memory ··································································································· 367 display process memory heap ···························································································· 369 display process memory heap address ················································································ 371 display process memory heap size ······················································································ 372 exception filepath ············································································································ 374 monitor kernel deadloop enable ·························································································· 375 monitor kernel deadloop exclude-thread ··············································································· 376 monitor kernel deadloop time ····························································································· 378 monitor kernel starvation enable ························································································· 379 monitor kernel starvation exclude-thread ·············································································· 380 monitor kernel starvation time ···························································································· 382 monitor process ·············································································································· 383 monitor thread ················································································································ 388 process core ·················································································································· 392 reset exception context ····································································································· 394 reset kernel deadloop ······································································································· 395 reset kernel exception ······································································································ 395 reset kernel reboot ··········································································································· 396
viii
reset kernel starvation ······································································································ 397 third-part-process start ····································································································· 398 third-part-process stop ······································································································ 399
Sampler commands ······································································ 401
display sampler ··············································································································· 401 sampler ························································································································· 402
Port mirroring commands ······························································· 404
display mirroring-group ····································································································· 404 mirroring-group ··············································································································· 405 mirroring-group mirroring-port (interface view) ······································································· 406 mirroring-group mirroring-port (system view) ········································································· 407 mirroring-group monitor-port (interface view) ········································································· 408 mirroring-group monitor-port (system view) ··········································································· 408
Flow mirroring commands ······························································ 410
mirror-to ························································································································ 410
NetStream configuration commands ················································· 411
display ip netstream cache ································································································ 411 display ip netstream export ································································································ 418 display ip netstream template ····························································································· 419 enable ··························································································································· 422 ip netstream ··················································································································· 423 ip netstream filter ············································································································· 423 ip netstream sampler ········································································································ 424 ip netstream aggregation ·································································································· 425 ip netstream export host ··································································································· 427 ip netstream export rate ···································································································· 428 ip netstream export source ································································································ 429 ip netstream export v9-template refresh-rate packet ································································ 430 ip netstream export v9-template refresh-rate time ··································································· 431 ip netstream export version ······························································································· 432 ip netstream max-entry ····································································································· 433 ip netstream mpls ············································································································ 434 ip netstream timeout active ································································································ 435 ip netstream timeout inactive ····························································································· 435 reset ip netstream statistics ······························································································· 436
IPv6 NetStream commands ···························································· 437
display ipv6 netstream cache ····························································································· 437
ix
display ipv6 netstream export ····························································································· 442 display ipv6 netstream template ························································································· 443 enable ··························································································································· 447 ipv6 netstream ················································································································ 448 ipv6 netstream filter ········································································································· 448 ipv6 netstream sampler ···································································································· 449 ipv6 netstream aggregation ······························································································· 450 ipv6 netstream export host ································································································ 452 ipv6 netstream export rate ································································································· 453 ipv6 netstream export source ····························································································· 454 ipv6 netstream export v9-template refresh-rate packet ···························································· 455 ipv6 netstream export v9-template refresh-rate time ································································ 456 ipv6 netstream export version 9 ·························································································· 456 ipv6 netstream max-entry ·································································································· 457 ipv6 netstream timeout active ····························································································· 458 ipv6 netstream timeout inactive ·························································································· 459 reset ipv6 netstream statistics ···························································································· 460
sFlow commands ········································································· 461
display sflow ··················································································································· 461 sflow agent ···················································································································· 462 sflow collector ················································································································· 463 sflow counter interval ······································································································· 464 sflow counter collector ······································································································ 465 sflow flow collector ··········································································································· 466 sflow flow max-header ······································································································ 466 sflow sampling-mode ······································································································· 467 sflow sampling-rate ·········································································································· 468 sflow source ··················································································································· 468
Information center commands ························································· 470
diagnostic-logfile save ······································································································ 470 display diagnostic-logfile summary ······················································································ 471 display info-center ··········································································································· 471 display logbuffer ·············································································································· 472 display logbuffer summary ································································································· 475 display logfile summary ···································································································· 476 display security-logfile summary ························································································· 477 enable log updown ·········································································································· 478 info-center diagnostic-logfile directory ·················································································· 479 info-center diagnostic-logfile enable····················································································· 479 info-center diagnostic-logfile frequency ················································································ 480 info-center diagnostic-logfile quota ······················································································ 481
x
info-center enable ············································································································ 481 info-center format ············································································································ 482 info-center logbuffer ········································································································· 482 info-center logbuffer size ··································································································· 483 info-center logfile directory ································································································ 484 info-center logfile enable ··································································································· 485 info-center logfile frequency ······························································································· 485 info-center logfile overwrite-protection ·················································································· 486 info-center logfile size-quota ······························································································ 487 info-center logging suppress duplicates ················································································ 487 info-center loghost ··········································································································· 489 info-center loghost source ································································································· 490 info-center security-logfile alarm-threshold ············································································ 491 info-center security-logfile directory ····················································································· 491 info-center security-logfile enable ························································································ 492 info-center security-logfile frequency···················································································· 493 info-center security-logfile size-quota ··················································································· 494 info-center source ············································································································ 494 info-center synchronous ···································································································· 496 info-center syslog min-age ································································································ 497 info-center syslog trap buffersize ························································································ 498 info-center timestamp ······································································································· 499 info-center timestamp loghost ···························································································· 500 info-center trace-logfile quota ····························································································· 500 logfile save ····················································································································· 501 reset logbuffer ················································································································ 502 security-logfile save ········································································································· 502 snmp-agent trap enable syslog ··························································································· 503 terminal debugging ·········································································································· 504 terminal logging level ······································································································· 505 terminal monitor ·············································································································· 506
Flow log commands ······································································ 507
display userlog export ······································································································ 507 reset userlog flow export ··································································································· 508 userlog flow export host ···································································································· 508 userlog flow export load-balancing ······················································································ 509 userlog flow export source-ip ····························································································· 510 userlog flow export timestamp localtime ··············································································· 511 userlog flow export version ································································································ 511 userlog flow syslog ·········································································································· 512
xi
Packet capture commands ····························································· 514
display packet-capture status ····························································································· 514 packet-capture (on wired devices) ······················································································· 515 packet-capture local interface (on wired devices/fat APs) ························································· 518 packet-capture read (on wired devices) ················································································ 520 packet-capture remote interface (on wired devices/fat APs) ······················································ 521 packet-capture stop ········································································································· 521
Document conventions and icons ···················································· 523
Conventions ························································································································· 523 Network topology icons ··········································································································· 524
Support and other resources ·························································· 525
Accessing Hewlett Packard Enterprise Support ············································································ 525 Accessing updates ················································································································· 525
Websites ······················································································································· 526 Customer self repair ········································································································· 526 Remote support ·············································································································· 526 Documentation feedback ·································································································· 527
Index ························································································· 528
xii

Ping, tracert, and system debugging commands

debugging

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

display debugging

Use display debugging to display the enabled debugging features for a module or for all modules.
Syntax
display debugging [ module-name ]
Views
Any view
Predefined user roles
network-admin network-operator
Parameters
module-name: Specifies a module by its name. For a list of supported modules, use the display debugging ? command. If you do not specify a module name, this command displays the enabled
debugging features for all modules.
Examples
# Display all enabled debugging features.
<Sysname> display debugging DEV debugging switch is on
Related commands
debugging

ping

Use ping to test the reachability of the destination IP address and display ping statistics.
Syntax
ping [ ip ] [ -a source-ip | -c count | -f | -h ttl | -i interface-type interface-number | -m interval | -n | -p
pad | -q | -r | -s packet-size | -t timeout | -tos tos | -v | { -topology topo-name | -vpn-instance vpn-instance-name } ] * host
Views
Any view
Predefined user roles
network-admin
Parameters
ip: Distinguishes between a destination host name and the ping command keywords if the name of the destination host is i, ip, ipv, or ipv6. For example, you must use the command in the form of ping ip ip instead of ping ip if the destination host name is ip.
2
-a source-ip: Specifies an IP address of the device as the so urce IP address of ICMP echo requests. If this option is not specified, the source IP address of ICMP echo requests is the primary IP address of the outbound interface.
-c count: Specifies the number of ICMP echo requests that are sent to the destination. The value range is 1 to 4294967295, and the default is 5.
-f: Sets the "do-not-fragment" bit in the IP header.
-h ttl: Specifies the TTL value of ICMP echo requests. The value range is 1 to 255, and the default is
255.
-i interface-type interface-number: Specifies the source interface for ICMP echo requests. If you do not specify this option, the system uses the primary IP address of the matching route's egress interface as the source interface for ICMP echo requests.
-m interval: Specifies the interval (in milliseconds) to send ICMP echo requests. The value range is 1 to 65535, and the default is 200.
-n: Disables domain name resolution for the host argument. If the host argument represents the host name of the destination, and if this keyword is not specified, the device translates host into an address.
-p pad: Specifies the value of the pad field in an ICMP echo request, in hexadecimal format, 1 to 8 bits. The pad argument is in the range of 0 to ffffffff. If the specified value is less than 8 bits, 0s are added in front of the value to extend it to 8 bits. For example, if pad is configured as 0x2f, then the packets are padded with 0x0000002f to make the total length of the packet meet the requi rements of the device. By default, the padded value starts from 0x01 up to 0xff, where another round starts again if necessary, such as 0x010203…feff01….
-q: Displays only the summary statistics. If this keyword is not specified, the system displays all the ping statistics.
-r: Records the addresses of the hops (up to 9) the ICMP echo requests passed. If this keyword is not specified, the addresses of the hops that the ICMP echo requests passed are not recorded.
-s packet-size: Specifies the length (in bytes) of ICMP echo requests (excluding the IP packet header and the ICMP packet header). The value range is 20 to 81 00, and the default is 56.
-t timeout: Specifies the timeout time (in millise conds) of an ICMP echo re ply. The value range is 0 to 65535, and the default is 2000. If the source does not receive an ICMP echo reply within the timeout, it considers the ICMP echo reply timed out.
-tos tos: Specifies the ToS value of ICMP echo requests. The value range is 0 to 255, and the default is 0.
-v: Displays non-ICMP echo reply packets. If this keyword is not specified, the system does not display non-ICMP echo reply packets.
-topology topo-name: Specifies the topology to which the destination belongs, where topo-name is a case-sensitive string of 1 to 31 characters. If the destination is on the public net
work, do not specify
this option.
3
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination belongs, where the vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
host: Specifies the IP address or host name of the destination. The host name is a case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
T o ping a device identified by its host name, configu re the DNS settings on the device first. If the DNS settings are not configured, the ping operation fails.
To abort the ping operation during the execution of the command, press Ctrl+C.
Examples
# Test whether the device with an IP address of 1.1.2.2 is reachable.
<Sysname> ping 1.1.2.2 Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break 56 bytes from 1.1.2.2: icmp_seq=0 ttl=254 time=2.137 ms 56 bytes from 1.1.2.2: icmp_seq=1 ttl=254 time=2.051 ms 56 bytes from 1.1.2.2: icmp_seq=2 ttl=254 time=1.996 ms 56 bytes from 1.1.2.2: icmp_seq=3 ttl=254 time=1.963 ms 56 bytes from 1.1.2.2: icmp_seq=4 ttl=254 time=1.991 ms
--- Ping statistics for 1.1.2.2 --­5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.963/2.028/2.137/0.062 ms
# Test whether the device with an IP address of 1.1.2.2 in VPN 1 is reachable.
<Sysname> ping -vpn-instance vpn1 1.1.2.2 Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break 56 bytes from 1.1.2.2: icmp_seq=0 ttl=254 time=2.137 ms 56 bytes from 1.1.2.2: icmp_seq=1 ttl=254 time=2.051 ms 56 bytes from 1.1.2.2: icmp_seq=2 ttl=254 time=1.996 ms 56 bytes from 1.1.2.2: icmp_seq=3 ttl=254 time=1.963 ms 56 bytes from 1.1.2.2: icmp_seq=4 ttl=254 time=1.991 ms
--- Ping statistics for 1.1.2.2 in VPN instance vpn1 --­5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.963/2.028/2.137/0.062 ms
# Test whether the device with an IP address of 1.1.2.2 is reachable. Only results are displayed.
<Sysname> ping -q 1.1.2.2 Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break
--- Ping statistics for 1.1.2.2 --­5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.962/2.196/2.665/0.244 ms
4
# Test whether the device with an IP address of 1.1.2.2 is reachable. The IP addresses of the hops that the ICMP packets passed in the path are displayed.
<Sysname> ping -r 1.1.2.2 Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break 56 bytes from 1.1.2.2: icmp_seq=0 ttl=254 time=4.685 ms RR: 1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1 56 bytes from 1.1.2.2: icmp_seq=1 ttl=254 time=4.834 ms (same route) 56 bytes from 1.1.2.2: icmp_seq=2 ttl=254 time=4.770 ms (same route) 56 bytes from 1.1.2.2: icmp_seq=3 ttl=254 time=4.812 ms (same route) 56 bytes from 1.1.2.2: icmp_seq=4 ttl=254 time=4.704 ms (same route)
--- Ping statistics for 1.1.2.2 --­5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 4.685/4.761/4.834/0.058 ms
The output shows that:
The destination is reachable.
The route is 1.1.1.1 <-> {1.1.1.2; 1.1.2.1} <-> 1.1.2.2.
Table 1 Command output
Field Description
Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break
56 bytes from 1.1.2.2: icmp_seq=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.
--- 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.
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
ping operation. Received ICMP echo replies from the device whose IP address is
1.1.2.2. If no echo reply is received within the timeout period, no information is displayed.
bytes—Number of bytes in the ICMP echo reply.
icmp_seq—Packet sequence, used to determine whether a
segment is lost, disordered or repeated.
ttl—TTL value in the ICMP echo reply.
time—Response time.
Routers through which the ICMP echo request passed. They are displayed in inversed order, which means the router with a smaller distance to the destination is displayed first.
Ping statistics for a device in a VPN instance.
to abort the
0.0% packet loss Percentage of unacknowledged packets to the total packets sent. round-trip min/avg/max/std-dev =
4.685/4.761/4.834/0.058 ms
Minimum/average/maximum/standard deviation response time, in milliseconds.
5

ping ipv6

Use ping ipv6 to test the reachability of the destination IPv6 address and di splay IPv6 ping statistics.
Syntax
ping ipv6 [ -a source-ipv6 | -c count | -i interface-type interface-number | -m interval | -q | -s packet-size | -t timeout | -tc traffic-class| -v | -vpn-instance vpn-instance-name ] * host
Views
Any view
Predefined user roles
network-admin
Parameters
-a source-ipv6: Specifies an IPv6 address of the device as the source IP address of ICMP echo
requests. If this option is not specified, the source IPv6 address of ICMP echo requests is the IPv6 address of the outbound interface. See RFC 3484 for information about the address selection rule.
-c count: Specifies the number of ICMPv6 echo requests that are sent to the destination. The value range is 1 to 4294967295, and the default is 5.
-i interface-type interface-number: Specifies the source interface for ICMPv6 echo requests. This option must be specified when the destination address is a multicast addre ss or a link local addre ss. If you do not specify this option, the system uses the primary IP address of the matching route's egress interface as the source interface for ICMPv6 echo requests.
-m interval: Specifies the interval (in milliseconds) to send an ICMPv6 echo reply. The value range is 1 to 65535, and the default is 1000.
-q: Displays only the summary statistics. If you do not specify this keyword, the system displays all the ping statistics.
-s packet-size: Specifies the length (in bytes) of ICMPv6 echo requests (excluding the IPv6 packet header and the ICMPv6 packet header). The value range is 20 to 8100, and the default is 56.
-t timeout: Specifies the timeout time (in milliseconds) of an ICMPv6 echo reply . The value range is 0 to 65535, and the default is 2000.
-tc traffic-class: Specifies the traffic class value in an ICMPv6 packet. The value range is 0 to 255 and the default is 0.
-v: Displays detailed information (including the dst field and the idx field) about ICMPv6 echo replies. If this keyword is not specified, the system only displays brief information (not including the dst field and the idx field) about ICMPv6 echo replies.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination belongs, where the vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
6
host: Specifies the IPv6 address or host name of the destination. The host name is a case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
T o ping a device identified by its host name, configu re the DNS settings on the device first. If the DNS settings are not configured, the ping ipv6 operation fails.
To abort the ping ipv6 operation during the execution of the command, press Ctrl+C.
Examples
# Test whether the IPv6 address (2001::2) is reachable.
<Sysname> ping ipv6 2001::2 Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C to break 56 bytes from 2001::2, icmp_seq=0 hlim=64 time=62.000 ms 56 bytes from 2001::2, icmp_seq=1 hlim=64 time=23.000 ms 56 bytes from 2001::2, icmp_seq=2 hlim=64 time=20.000 ms 56 bytes from 2001::2, icmp_seq=3 hlim=64 time=4.000 ms 56 bytes from 2001::2, icmp_seq=4 hlim=64 time=16.000 ms
--- Ping6 statistics for 2001::2 --­5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 4.000/25.000/62.000/20.000 ms
# Test whether the IPv6 address (2001::2) is reachable. Only the statistics are displayed.
<Sysname> ping ipv6 –q 2001::2 Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C to break
--- Ping6 statistics for 2001::2 --­5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 4.000/25.000/62.000/20.000 ms
# Test whether the IPv6 address (2001::2) is reachable. Detailed ping information is displayed.
<Sysname> ping ipv6 –v 2001::2 Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C to break 56 bytes from 2001::2, icmp_seq=0 hlim=64 dst=2001::1 idx=3 time=62.000 ms 56 bytes from 2001::2, icmp_seq=1 hlim=64 dst=2001::1 idx=3 time=23.000 ms 56 bytes from 2001::2, icmp_seq=2 hlim=64 dst=2001::1 idx=3 time=20.000 ms 56 bytes from 2001::2, icmp_seq=3 hlim=64 dst=2001::1 idx=3 time=4.000 ms 56 bytes from 2001::2, icmp_seq=4 hlim=64 dst=2001::1 idx=3 time=16.000 ms
--- 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 millisecon ds,
25 milliseconds, 62 milliseconds, and 20 milliseconds.
7
Table 2 Command output
Field Description
Ping6(56 data bytes) 2001::1 --> 2001::2, press CTRL_C
to break
56 bytes from 2001::2, icmp_seq=1 hlim=64 dst=2001::1
idx=3 time=62.000 ms
--- Ping6 statistics for 2001::2 ------ Statistics on data received and sent in an IPv6 ping operation. 5 packet(s) transmitted Number of ICMPv6 echo requests sent. 5 packet(s) received Number of ICMPv6 echo replies received.
0.0% packet loss Percentage of unacknowledged packets to the total packets sent.
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 device whose IPv6 address
is 2001::2.
The number of data bytes is 56.
The packet sequence is 1.
The hop limit value is 64.
The destination address is 2001::1. Specify the -v keyword to
display this field.
The index for the packet inbound interface is 3. Specify the -v keyword to display this field.
The response time is 62 milliseconds.
to abort the ping IPv6 operation.
round-trip min/avg/max/ std-dev =4.000/25.000/62.000/20.000 ms

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.
Minimum/average/maximum/standard deviation response time, in milliseconds.
-f first-ttl: Specifies the TTL of the first packet sent to the destin ation. The value range is 1 to 255, and the default is 1. It must be no greater than the value of the max-ttl argument.
-m max-ttl: Specifies the maximum number of hops allowed for a probe packet. The value range is 1 to 255, and the default is 30. It must be no smaller than the value of the first-ttl argument.
8
-p port: Specifies an invalid UDP port of the destination. The value range is 1 to 65535, and the default is 33434. If the destination address is an EID address at a remote LISP site, specify a port number in the range of 33434 to 65535.
-q packet-number: Specifies the number of probe packets to send per hop. The value range is 1 to 65535, and the default is 3.
-t tos: Specifies the ToS value of probe packets. The value range is 0 to 255, and the default is 0.
-topology topo-name: Specifies the topology to which the destination belongs, where topo-name is
a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination belongs, where the vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-resolve-as: Specifies a routing table for autonomous system (AS) resolution. Tracert searches the specified routing table for the AS that each hop along the path belongs to. If you do not specify this keyword, the global routing table is used. If the AS information is found, this command displays the AS number next to the address of the hop in the probe result.
global: Specifies the global routing table.
none: Disables AS resolution.
vpn: Specifies the VPN routing table.
-w timeout: Specifies the timeout time in milliseconds of the reply packet for a probe packet. The value range is 1 to 65535, and the default is 5000.
host: Specifies the IP address or host name of the destination. The host name is a case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping command, use the tracert command to locate failed nodes.
If the destination address is on the public network, you do not need to specify the -resolve-as keyword to obtain the AS information. The device automatically uses the global routing table for AS resolution.
If the destination address is on a private network, address information of intermediate hops might be stored in either the global routing table or the VPN routing table. To learn the AS path that the packets traverse, execute the tracert command twice, once with the -resolve-as global keywords and again with the -resolve-as vpn keywords.
The output from the tracert command includes IP addresses of all the Layer 3 devices that the packets traverse from source to destination. Asterisks (* * *) are displayed if the device cannot reply with an ICMP error message. The reason might be the destination is unreachable or sending ICMP timeout/destination unreachable packets is disabled.
9
To abort the tracert operation during the execution of the command, press Ctrl+C.
Examples
# Display the path that the packets traverse from source to destination (1.1.2.2).
<Sysname> tracert 1.1.2.2 traceroute to 1.1.2.2 (1.1.2.2), 30 hops at most, 40 bytes each packet, press CTRL_C to
break 1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms 2 1.1.2.2 (1.1.2.2) [AS 100] 580 ms 470 ms 80 ms
# Display the path that the packets traverse from source to destination (1.1.3.2) in VPN instance vpn1, as well as the AS information of the hops along the path.
<Sysname> tracert –vpn-instance vpn1 –resolve-as vpn 1.1.3.2 traceroute to 1.1.3.2 (1.1.3.2), 30 hops at most, 40 bytes each packet, press CTRL_C to
break 1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms 2 1.1.2.2 (1.1.2.2) 580 ms 470 ms 80 ms 3 1.1.3.2 (1.1.3.2) [AS 65535] 530 ms 472 ms 380 ms
# Trace the path to destination (192.1 68.0.46) over an MPLS network.
<Sysname> tracert 192.168.0.46 traceroute to 192.168.0.46(192.168.0.46), 30 hops at most, 40 bytes each packet, press
CTRL_C to break 1 192.0.2.13 (192.0.2.13) 0.661 ms 0.618 ms 0.579 ms 2 192.0.2.9 (192.0.2.9) 0.861 ms 0.718 ms 0.679 ms MPLS Label=100048 Exp=0 TTL=1 S=1 3 192.0.2.5 (192.0.2.5) 0.822 ms 0.731 ms 0.708 ms MPLS Label=100016 Exp=0 TTL=1 S=1 4 192.0.2.1 (192.0.2.1) 0.961 ms 8.676 ms 0.875 ms
Table 3 Command output
Field Description
traceroute to 1.1.2.2 (1.1.2.2)
hops at most
bytes each packet Number of bytes of a probe packet.
press CTRL_C to break
2 1.1.2.2 (1.1.2.2) [AS 100] 580 ms 470 ms 80 ms
Display the route that the IP packets traverse from the current device to the device whose IP address is 1.1.2.2.
Maximum number of hops of the probe packets, which can be set by the -m keyword.
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.
IP address of the hop. The IP address is displayed in parentheses.
Number of the AS that the hop belongs to. The AS number appears
only when it is found for the hop in the specified routing table.
The round-trip time of the probe packets.
The number of packets that can be sent in each probe can be set by using
-q
the
keyword.
Ctrl+C
to abort the tracert
10
Field Description
MPLS Label=100048 Exp=0 TTL=1 S=1

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
ICMP timeout packets on an MPLS network, carrying MPLS label information:
Label—Label value that is used to identify a forwarding equivalence class (FEC).
Exp—Reserved, usually used for class of service (CoS).
TTL—TTL value.
S—MPLS supports multiple levels of labels. Value 1 indicates that the
label is at the bottom of the label stack, and value 0 indicates that the label is in another label stack.
Predefined user roles
network-admin
Parameters
-f first-hop: Specifies the TTL value of the first packet. The value range is 1 to 25 5, 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 ran ge i s 1 to 255, and the default is 30. The value must be no smaller than the value of the first-hop argument.
-p port: Specifies an invalid UDP port of the destination. The value range is 1 to 65535, and the default is 33434.
-q packet-number: Specifies the number of probe packets sent each time. The value range is 1 to 65535, and the default is 3.
-t traffic-class: Specifies the traffic class value in an IPv6 probe packet. The value ran ge i s 0 t o 255, and the default is 0.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination belongs, where the vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-resolve-as: Specifies a routing table for AS resolutio n. Tracert searches the specified routing table for the AS that each hop along the path belongs to. If you do not specify this keyword, the global routing table is used. If the AS information is found, this command displays the AS number next to the address of the hop in the probe result.
11
global: Specifies the global routing table.
none: Disables AS resolution.
vpn: Specifies the VPN routing table.
-w timeout: Specifies the timeout time (in milliseconds) of the reply packet of a probe packet. The value range is 1 to 65535, and the default is 5000.
host: Specifies the IPv6 address or host name of the destination. The host name is a case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping ipv6 command, you can use the tracert ipv6 command to locate failed nodes.
If the destination address is on the public network, you do not need to specify the -resolve-as keyword to obtain the AS information. The device automatically uses the global routing table for AS resolution.
If the destination address is on a private network, address information of intermediate hops might be stored in either the global routing table or the VPN routing table. To learn the AS path that the packets traverse, execute the tracert ipv6 command twice, once with the -resolve-as global keywords and again with the -resolve-as vpn keywords.
The output from the tracert ipv6 command includes IPv6 addresses of all the Layer 3 devices that the packets traverse from source to destination. Asterisks (* * *) are displayed if the device cannot reply with an ICMP error message. The reason might be the destination is unreachable or sending ICMP timeout/destination unreachable packets is disabled.
To abort the tracert operation during the execution of the command, press Ctrl+C.
Examples
# Display the path that the packets traverse from source to destination (2001:3::2).
<Sysname> tracert ipv6 2001:3::2 traceroute to 2001:3::2(2001:3::2), 30 hops at most, 60 byte packets, press CTRL_C to break 1 2001:1::2 0.661 ms 0.618 ms 0.579 ms 2 2001:2::2 [AS 100] 0.861 ms 0.718 ms 0.679 ms 3 2001:3::2 [AS 200] 0.822 ms 0.731 ms 0.708 ms
# Display the path that the packets traverse from source to destination (2001:3::2) in VPN instance vpn1, as well as the AS information of the hops along the path.
<Sysname> tracert ipv6 –vpn-instance vpn1 –resolve-as vpn 2001:3::2 traceroute to 2001:3::2(2001:3::2), 30 hops at most, 60 byte packets , press CTRL_C to
break 1 2001:1::2 0.661 ms 0.618 ms 0.579 ms 2 2001:2::2 0.861 ms 0.718 ms 0.679 ms 3 2001:3::2 [AS 65535] 0.822 ms 0.731 ms 0.708 ms
12
Table 4 Command output
Field Description
traceroute to 2001:3::2
Display the route that the IPv6 packets traverse from the current device to the device whose IP address is 2001:3:2.
hops at most
Maximum number of hops of the probe packets, which can be set by the
-m
keyword.
byte packets Number of bytes of a probe packet.
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.
2 2001:2::2 [AS 100] 0.861 ms
0.718 ms 0.679 ms
Number of the AS the hop belongs to. The AS number appears only when it is found for the hop in the specified routing table.
The round-trip time of the probe packets.
The number of packets that can be sent in each probe can be set by using the
-q
keyword.
13

NQA commands

NQA client commands

advantage-factor

Use advantage-factor to set the advantage factor 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 evaluation of voice quality depends on users' tolerance for voice quality. For users with higher tolerance for voice quality, use the advantage-factor command to set an advantage factor. When the system calculates the ICPIF value, it subtracts the advantage factor to modify ICPIF and MOS values for voice quality evaluation.
Examples
# Set the advantage factor to 10 for the voice operation.
<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type voice [Sysname-nqa-admin-test-voice] advantage-factor 10

codec-type

Use codec-type to configure the codec type for the voice operation.
14
Use undo codec-type to restore the default.
Syntax
codec-type { g711a | g711u | g729a } undo codec-type
Default
The codec type for the voice operation is G.711 A-law.
Views
Voice operation view
Predefined user roles
network-admin
Parameters
g711a: Specif ies G.71 1 A-law codec type. g711u: Speci f ies 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] nqa 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
15
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 length, only the first part of the string 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 length is greater than the string length, the system fills the payload with the string cyclically until the payload is full. For example, if you configure the string as abcd and the payload 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.
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] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] 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
undo data-size
The default payload size of a probe packet for different operations is describe d in Tab l e 5 .
16
Loading...
+ 495 hidden pages