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

...

Download

Page 1

HPE FlexNetwork MSR Rout e r Series

Comware 7 Networ k Management and Monitorin g

Command Reference

Document version: 6W101-20161114

Part number: 5200-2374 Software version: MSR-CMW710-R0411

Page 2

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.

Page 3

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

Page 4

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

Page 5

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

Page 6

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

Page 7

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

Page 8

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

Page 9

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

Page 10

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

Page 11

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

Use display debugging to display the enabled debugging features for a module or for all modules.

Syntax

display debugging [ module-name ]

Page 12

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

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.

Page 13

-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

Page 14

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

Page 15

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

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.

Page 16

-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

Page 17

•

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.

Page 18

-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

Page 19

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

Page 20

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

Page 21

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.

Page 22

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.

Page 23

•

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.

Page 24

•

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

Page 25

•

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

Page 26

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.

Page 27

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

Page 28

•

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

Page 29

•

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

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.

Page 30

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.

N completed probes.

packets.

threshold.

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.

packets.

the oneexceeding the threshold.

Number of packets with the oneexceeding the threshold.

Total packet loss.

Page 31

metric

Monitored performance

ICPIF N/A N/A N/A N/A MOS N/A N/A N/A N/A

display nqa result

Use display nqa result to display the most recent result of the specified NQA operation.

Syntax

display nqa result [ admin-name operation-tag ]

Views

Any view

Predefined user roles

network-admin network-operator

Parameters

Threshold type

Collect data in Checked Num Over-threshold Num

Examples

# Display the most recent result of the TCP operation with administrator name admin and operation tag test.

<Sysname> display nqa result admin test NQA entry (admin admin, tag test) test results: Send operation times: 1 Receive response times: 1 Min/Max/Average round trip time: 35/35/35 Square-Sum of round trip time: 1225 Last succee ded probe time: 20 11-05-29 10:50:33.2 Extended resu lts: Packet loss ratio: 0% Failures due to timeout: 0 Failures due to disconnect: 0 Failures du e to no connection: 0 Failures du e to internal error: 0 Failures due to other errors: 0

# Display the most rec ent result of the ICMP jitter oper ation with administrator name admin and operation tag test.

<Sysname> display nqa result admin test NQA entry (admin admin, tag test) test results: Send operat ion times: 10 Receive response tim es: 10 Min/Max/Average round trip time: 1/2/1 Square-Sum of round trip time: 13

Page 32

Last packet received time: 2015-03-09 17:40:29.8 Extended resu lts: Packet loss ratio: 0% Failures du e to timeout: 0 Failures du e to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived late: 0 ICMP-jitter results: RTT number: 10 Min positiv e SD: 0 Min positive DS: 0 Max positiv e SD: 0 Max positive DS: 0 Positive SD number: 0 Positive DS numb er: 0 Positive SD sum: 0 Positive DS sum: 0 Positive SD average: 0 Positive DS average: 0 Positive SD square-sum: 0 Positive DS square-sum: 0 Min negativ e SD: 1 Min negative DS: 2 Max negativ e SD: 1 Max negative DS: 2 Negative SD number: 1 Negative DS numb er: 1 Negative SD sum: 1 Negative DS sum: 2 Negative SD average: 1 Negative DS average: 2 Negative SD square-sum: 1 Negative DS square-sum: 4 One way results: Max SD delay: 1 Max DS delay: 2 Min SD delay: 1 Min DS delay: 2 Number of SD de lay: 1 Number of DS delay: 1 Sum of SD delay : 1 Sum of DS delay: 2 Square-Sum of SD delay: 1 Square-Sum of DS delay: 4 Lost packet s for unknown reason: 0

# Display th e most recent result of the UDP jitter operation with administrator nam e admin and operation tag test.

<Sysname> display nqa result admin test NQA entry (ad min admin, tag test) test results: Send operat ion times: 10 Receive response tim es: 10 Min/Max/Average round trip time: 15/46/26 Square-Sum of round trip time: 8103 Last packet receiv ed time: 2011-05-29 10:56:38.7 Extended resu lts: Packet loss ratio: 0% Failures du e to timeout: 0 Failures du e to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived late: 0 UDP-jitter results: RTT number: 10 Min positiv e SD: 8 Min positive DS: 8 Max positive SD: 18 Max positive DS: 8

Page 33

Positive SD number: 5 Positive DS number: 2 Positive SD sum: 75 Positive DS sum: 32 Positive SD average: 15 Positive DS average: 16 Positive SD square-sum: 1189 Positive DS square-sum: 640 Min negativ e SD: 8 Min negative DS: 1 Max negative SD: 24 Max negative DS: 30 Negative SD number: 4 Negative DS numb er: 7 Negative SD sum: 56 Negative DS sum: 99 Negative SD averag e: 14 Negative DS average: 14 Negative SD square-sum: 946 Negative DS square-sum: 1495 One way results: Max SD delay: 22 Max DS del ay: 23 Min SD delay: 7 Min DS delay: 7 Number of SD de lay: 10 Number of DS delay : 10 Sum of SD delay: 125 Sum of DS delay: 132 Square-Sum of SD delay: 1805 Square-Sum of DS delay: 1988 SD lost packets: 0 DS lost packets: 0 Lost packets for unknown reason: 0

# Display the most recent result of the voice operation with administrator name admin and operation tag test.

<Sysname> display nqa result admin test NQA entry (ad min admin, tag test) test results: Send operation times: 1000 Receive response times: 0 Min/Max/Average round trip time: 0/0/0 Square-Sum of round trip time: 0 Last packet receiv ed time: 0-00-00 00:00:00.0 Extended resu lts: Packet loss ratio: 100% Failures du e to timeout: 1000 Failures du e to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived late: 0 Voice results: RTT number: 0 Min positiv e SD: 0 Min positive DS: 0 Max positiv e SD: 0 Max positive DS: 0 Positive SD number: 0 Positive DS numb er: 0 Positive SD sum: 0 Positive DS sum: 0 Positive SD average: 0 Positive DS average: 0 Positive SD square-sum: 0 Positive DS square-sum: 0 Min negativ e SD: 0 Min negative DS: 0 Max negativ e SD: 0 Max negative DS: 0 Negative SD number: 0 Negative DS number: 0 Negative SD sum: 0 Negative DS sum: 0 Negative SD average: 0 Negative DS average: 0 Negative SD square-sum: 0 Negative DS square-sum: 0 One way results:

Page 34

Max SD delay: 0 Max DS delay: 0 Min SD delay: 0 Min DS delay: 0 Number of SD de lay: 0 Number of DS delay: 0 Sum of SD delay : 0 Sum of DS delay: 0 Square-Sum of SD delay: 0 Square-Sum of DS delay: 0 SD lost packets: 0 DS lost packets: 0 Lost packets for unknown reason: 1000 Voice scores: MOS value: 0.99 ICPIF value: 87

# Display the most recent result of the path jitter operation with administrator name admin and operation tag test.

<Sysname> display nqa result admin test NQA entry (admin admin, tag test) test results: Hop IP 192.168.40.210 Basic Results: Send operation times: 10 Receive response times: 10 Min/Max/Average round trip time: 1/1/1 Square-Sum of round trip time: 10 Extended Re sults: Packet loss ratio: 0% Failure s due to timeout: 0 Failures due to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived late: 0 Path-Jitter Result s: Jitter nu mber: 9 Min/Max/Average jitter: 0/0/0 Positive jitter number: 0 Min/Max/Average positive jitter: 0/ 0/0 Sum/Square-Sum positiv e jitter: 0/0 Negative jitter number: 0 Min/M ax/Average negative jitter: 0/0/0 Sum/Square-Sum negativ e jitter: 0/0 Hop IP 192.168.50.209 Basic Results: Send operation time s: 10 Receive response times: 10 Min/Max/Average round trip time: 1/1/1 Square-Sum of round trip time: 10 Extended Re sults: Packet loss ratio: 0% Failure s due to timeout: 0 Failure s due to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived late: 0

Page 35

Field

Description

This field is not available for UDP jitter, path jitter, and voice

Path-Jitter Result s: Jitter nu mber: 9 Min/Max/Average jitter: 0/0/0 Positive jitter number: 0 Min/M ax/Average positive jitter: 0/0/0 Sum/Square-Sum positiv e jitter: 0/0 Negative jitter number: 0 Min/M ax/Average negative jitter: 0/0/0 Sum/Square-Sum negativ e jitter: 0/0

# Display the most rec ent result of the UDP tracert oper ation with administrator name admin and operation tag test.

<Sysname> display nqa result admin test NQA entry (admin admin, tag test) test results: Send operat ion times: 6 Receive response times: 6 Min/Max/A verage round trip time: 35/35/35 Square-Sum of round trip time: 1225 Last succee ded probe time: 2013-09-09 14:23:24.5 Extended resu lts: Packet loss ratio: 0% Failures du e to timeout: 0 Failures du e to internal error: 0 Failures due to other errors: 0 UDP-tracert results: TTL Ho p IP Time 1 3.1.1.1 2013-09-09 14:23:24.5 2 4.1.1.1 2013-09-09 14:23:24.5

Table 9 Command output

Data collecting in progress The operation is in progress. Send operation times Number of operations. Receive response times Number of response packets received.

Min/Max/Average round trip time Minimum/maximum/average round-trip time in milliseconds. Square-Sum of round trip time Square sum of round-trip time.

Time when the last successful probe was completed. If no probes

Last succeeded probe time

Last packet received time

Packet loss ratio Average packet loss ratio. Failures due to timeout Number of timeout occurrences in an operation. Failures due to disconnect Number of disconnections by the peer.

are successful in an operation, the field displays 0.

operations. Time when the last response packet was received. If no response

packets in a probe were received, the field displays 0. This field is available only for UDP jitter and voice operations.

Failures due to no connection Number of failures to connect with the peer.

Page 36

Field

Description

negative jitters from source to

values of negative jitters from source to

Sum of absolute values of negative jitters from destination to

Failures due to internal error Number of failures due to internal errors. Failures due to other errors Failures due to other errors. Packets out of sequence Number of failur es due to out-of-sequence packets. Packets arrived late Number of response packets received after a probe times out.

UDP-jitter results

ICMP-jitter results

Voice results

RTT number Number of response packets received. Min positive SD Minimum positive jitter from source to destination. Min positive DS Minimum positive jitter from destination to source. Max positive SD Maximum positive jitter from source to destination. Max positive DS Maximum positive jitter from destination to source. Positive SD number Number of positive jitters from source to destination. Positive DS number Number of positive jitters from destination to source. Positive SD sum Sum of positive jitters from source to destination. Positive DS sum Sum of positive jitters from destinatio n to source. Positive SD average Average positive jitters from source to destination.

UDP jitter operation results. This field is available only for the UDP jitter operation.

ICMP jitter operation results. This field is available only for the ICMP jitter operation.

Voice operation results. This field is available only for the voice operation.

Positive DS average Average positive jitters from destination to source. Positive SD square-sum Square sum of positive jitters from source to destination. Positive DS square-sum Square su m of positive jitters from destination to source.

Min negative SD

Min negative DS

Max negative SD

Max negative DS

Negative SD number Number of negative jitters from source to destination. Negative DS number Number of negative jitters from destination to source.

Negative SD sum

Negative DS sum

Minimum absolute value among destination.

Minimum absolute value among negative jitt ers from destination to source.

Maximum absolute value among destination.

Maximum absolute val ue among negative jitters fr om destination to source.

Sum of absolute destination.

source.

Page 37

Field

Description

from source to

of negative jitters from destination to

Negative SD average

Negative DS average

Negative SD square-sum Square sum of negative jitters from source to destinat i on. Negative DS square-sum Square sum of negative jitters from destinat ion to source.

One way results

Max SD delay Maximum delay from source to destination. Max DS delay Maximum delay from destination to source. Min SD delay Minimum delay from source to destination. Min DS delay Minimum delay from destination to source. Number of SD delay Number of delays from source to destination. Number of DS delay Number of delays from destination to source. Sum of SD delay Sum of delays from source to destination. Sum of DS delay Sum of delays from destination to source.

Average absolute value of negative jitters destination.

Average absolute value source.

Unidirectional delay. This field is available only for the ICMP jitter, UDP jitter, and voice

operations.

Square-Sum of SD delay Square sum of delays from source to destination. Square-Sum of DS delay Square sum of delays from destination to source. SD lost packets Number of lost packets from the source to the destination. DS lost packets Number of lost packets from the destination to the source. Lost packets for unknown reason Number of lost packets for unknown reasons.

Voice scores

MOS value MOS value calculated for the voice operation. ICPIF value ICPIF value calculated for the voice operation.

Hop IP

Path-jitter results

Jitter number

Min/Max/Average jitter

Voice parameters. This field is available only for the voice operation.

IP address of the hop. This field is available only for the path jitter operation.

Path jitter operation results. This field is available only for the path jitter operation.

Number of jitters. This field is available only for the path jitter operation.

Minimum/maximum/avera ge jit ter in milliseconds. This field is available only for the path jitter operation.

Positive jitter number

Number of positive jitter. This field is available only for the path jitter operation.

Page 38

Field

Description

•

Min/Max/Average positive jitt er

Sum/Square-Sum positive jitter

Negative jitter number

Min/Max/Average negative jitter

Sum/Square-Sum negative jitter

TTL TTL value in the received reply packet. Hop IP IP address of the node that sent the reply packet. Time Time when the NQA client received the reply packet.

display nqa statistics

Use display nqa statistics to display NQA operation statistics.

Syntax

Minimum/maximum/average positive jitter in millisecon ds. This field is available only for the path jitter operation.

Sum/square sum of the positive jitter. This field is available only for the path jitter operation.

Number of negative jitter. This field is available only for the path jitter operation.

Minimum/maximum/average negative jitter in milliseconds. This field is available only for the path jitter operation.

Sum/square sum of the negative jitter. This field is available only for the path jitter operation.

display nqa statistics [ admin-name operation-tag ]

Views

Any view

Predefined user roles

network-admin network-operator

Parameters

Usage guidelines

The statistics are ge nerated after the NQA operation completes . If you execute the display nqa statistics command before the operation completes, the statistics are displayed as all 0s.

If a reaction entry is configured, the command displays the monitoring results of the reaction entry i n the period specified by the statistics internal command. The result fields display hyphens (-) in one of the following conditions:

The threshold t ype is average value. The monitored performance metric is ICPIF or MOS for the voice operation.

The command is not available for the UDP tracert operation.

Examples

# Display the statistics for the TCP operation with administrator name admin and operation tag test.

Page 39

<Sysname> display nqa statistics admin test NQA entry (admin admin, tag test) test statistics: NO. : 1 Start time: 2007-01-01 09:30:20.0 Life time: 2 se conds Send operation times: 1 Receive response times: 1 Min/Max/A verage round trip time: 13/13/13 Square-Sum of round trip time: 169 Extended resu lts: Packet loss ratio: 0% Failures du e to timeout: 0 Failures due to disconnect: 0 Failures du e to no connection: 0 Failures du e to internal error: 0 Failures due to other errors: 0

# Display the statistics for the ICMP jitter operation with administrator name admin and operation tag test.

<Sysname> display nqa statistics admin test NQA entry (adm in admin, tag test) te st statistics: NO. : 1 Start time: 2015-03-09 17:42:10.7 Life time: 15 6 seconds Send operat ion times: 1560 Receive respon se times: 1560 Min/Max/Average round trip time: 1/2/1 Square-Sum of round trip time: 1563 Extended resu lts: Packet loss ratio: 0% Failures du e to timeout: 0 Failures du e to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived la te: 0 ICMP-jitter results: RTT number: 1560 Min positiv e SD: 1 Min positive DS: 1 Max positiv e SD: 1 Max positive DS: 2 Positive SD number: 18 Positive DS number: 46 Positive SD sum: 18 Positive DS sum: 49 Positive SD average: 1 Positive DS average: 1 Positive SD square-sum: 18 Positive DS square-sum: 55 Min negativ e SD: 1 Min negative DS: 1 Max negativ e SD: 1 Max negative DS: 2 Negative SD number: 24 Negative DS number: 57 Negative SD sum: 24 Negative DS sum: 58 Negative SD average: 1 Negative DS average: 1 Negative SD square-sum: 24 Negative DS square-sum: 60 One way results: Max SD delay: 1 Max DS delay: 2

Page 40

Min SD delay: 1 Min DS delay: 1 Number of SD de lay: 4 Number of DS delay: 4 Sum of SD delay : 4 Sum of DS delay: 5 Square-Sum of SD delay: 4 Square-Sum of DS delay: 7 Lost packet s for unknown reason: 0 Reaction statistics: Index Checked Element Threshold Type Check ed Num Over-threshold Num 1 jitter-DS accumulate 1500 10 2 jitter-SD average - 3 OWD-DS - 1560 2 4 OWD-SD - 1560 0 5 packet-lo ss accumulate 0 0 6 RTT accumulate 1560 0

# Display the statistics for the UDP jitter operation with administrator name admin and operation tag test.

<Sysname> display nqa statistics admin test NQA entry (adm in admin, tag test) te st statistics: NO. : 1 Start time: 2007-01-01 09:33:22.3 Life time: 23 seconds Send operation times: 100 Receive response times: 100 Min/Max/Average round trip time: 1/11/5 Square-Sum of round trip time: 24360 Extended resu lts: Packet loss ratio: 0% Failures du e to timeout: 0 Failures due to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived late: 0 UDP-jitter results: RTT number: 550 Min positiv e SD: 1 Min positive DS: 1 Max positiv e SD: 7 Max positiv e DS: 1 Positive SD number: 220 Positive DS number: 97 Positive SD sum: 283 Positive DS sum: 287 Positive SD average: 1 Positive DS average: 2 Positive SD square-sum: 709 Positive DS square-sum: 1937 Min negativ e SD: 2 Min negative DS: 1 Max negative SD: 10 Max negative DS: 1 Negative SD number: 81 Negative DS number: 94 Negative SD sum: 556 Negative DS sum: 191 Negative SD average: 6 Negative DS average: 2 Negative SD square-sum: 4292 Negative DS square-sum: 967 One way results: Max SD delay: 5 Max DS delay: 5 Min SD delay: 1 Min DS delay: 1 Number of SD de lay: 550 Number of DS delay: 550

Page 41

Sum of SD delay: 1475 Sum of DS delay: 1201 Square-Sum of SD delay: 5407 Square-Sum of DS delay: 3959 SD lost packets: 0 DS lost packets: 0 Lost packets for unknown reason: 0 Reaction statistics: Index Checked Element Threshold Type Check ed Num Over-threshold Num 1 jitter-DS accumulate 90 25 2 jitter-SD average - 3 OWD-DS - 100 24 4 OWD-SD - 100 13 5 packet-lo ss accumulate 0 0 6 RTT accumulate 100 52

# Display the statistics for the voice operation with administrator name admin and operation tag test.

<Sysname> display nqa statistics admin test NQA entry (admin admin, tag test) test statistics: NO. : 1 Start time: 2007-01-01 09:33:45.3 Life time: 12 0 seconds Send operat ion times: 10 Receive response tim es: 10 Min/Max/Average round trip time: 1/12/7 Square-Sum of round trip time: 620 Extended resu lts: Packet loss ratio: 0% Failures du e to timeout: 0 Failures du e to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived late: 0 Voice results: RTT number: 10 Min positiv e SD: 3 Min positive DS: 1 Max positive SD: 10 Max positive DS: 1 Positive SD number: 3 Positive DS numb er: 2 Positive SD sum: 18 Positive DS sum: 2 Positive SD average: 6 Positive DS average: 1 Positive SD square-sum: 134 Positive DS square-sum: 2 Min negativ e SD: 3 Min negative DS: 1 Max negativ e SD: 9 Max negative DS: 1 Negative SD number: 4 Negative DS number: 2 Negative SD sum: 25 Negative DS sum: 2 Negative SD average: 6 Negative DS average: 1 Negative SD square-sum: 187 Negative DS square-sum: 2 One way results: Max SD delay: 0 Max DS delay: 0 Min SD delay: 0 Min DS delay: 0 Number of SD de lay: 0 Number of DS delay: 0 Sum of SD delay : 0 Sum of DS delay: 0 Square-Sum of SD delay: 0 Square-Sum of DS delay: 0

Page 42

SD lost packets: 0 DS lost packets: 0 Lost packets for unknown reason: 0 Voice scores: Max MOS value: 4.40 Min MOS value: 4.40 Max ICPIF val ue: 0 Min ICPIF value: 0 Reaction statistics: Index Checked Element Threshold Type Check ed Num Over-threshold Num 1 ICPIF - - 2 MOS - - -

# Display the statistics for the path jitter operation with administrator name admin and operation tag test.

<Sysname> display nqa statistics admin test NQA entry (admin admin, tag test) test statistics: NO. : 1 Path 1: Hop IP 192.168.40.210 Basic Results: Send operation times: 10 Receive response times: 10 Min/Max/Average round trip time: 1/1/1 Square-Sum of round trip time: 10 Extended Re sults: Packet loss ratio: 0% Failure s due to timeout: 0 Failure s due to internal error: 0 Failures due to other errors: 0 Packets out of sequence: 0 Packets arrived late: 0 Path-Jitter Result s: Jitter nu mber: 9 Min/Max/Average jitter: 0/0/0 Positive jitter number: 0 Min/M ax/Average positive jitter: 0/0/0 Sum/Square-Sum positiv e jitter: 0/0 Negative jitter number: 0 Min/M ax/Average negative jitter: 0/0/0 Sum/Square-Sum negativ e jitter: 0/0 Hop IP 192.168.50.209 Basic Results: Send operation times: 10 Receive response times: 10 Min/Max/Average round trip time: 1/1/1 Square-Sum of round trip time: 10 Extended Results: Packet loss ratio: 0% Failure s due to timeout: 0 Failure s due to internal error: 0 Failures due to other errors: 0

Page 43

Field

Description

Packets out of sequence: 0 Packets arrived late: 0 Path-Jitter Result s: Jitter nu mber: 9 Min/Max/Average jitter: 0/0/0 Positive jitter number: 0 Min/M ax/Average positive jitter: 0/0/0 Sum/Square-Sum positiv e jitter: 0/0 Negative jitter number: 0 Min/M ax/Average negative jitter: 0/0/0 Sum/Square-Sum negative jitter: 0/0

Table 10 Command output

No. Statistics group ID. Start time Time when the operation started. Life time Duration of the operation in seconds. Send operation times Number of probe packets sent . Receive response times Number of response packets received. Min/Max/Average round trip time Minimum/maximum/average round-trip time in milliseconds. Square-Sum of round trip time Square sum of round-trip time.

Packet loss ratio Average packet loss ratio. Failures due to timeout Number of timeout occurrences in an operation. Failures due to disconnect Number of disconnections by the peer. Failures due to no connection Number of failures to connect with the peer. Failures due to internal error Number of failur es due to internal errors. Failures due to other errors Failures due to other errors . Packets out of sequence Number of failures due to out-of-se quence packets. Packets arrived late Number of response packets received after a probe times out.

UDP-jitter results

ICMP-jitter results

Voice results

UDP jitter operation results. This field is available only for the UDP jitter operation.

ICMP jitter operation results. This field is available only for the ICMP jitter operation.

Voice operation results. This field is available only for the voice operation.

Page 44

Field

Description

negative jitters from

values of negative jitters from source to

Sum of absolute values of negative jitters from destination to

of negative jitters from source to

of negative jitters from destination to

This field is available only for the ICMP jitter, UDP jitter, and

Max positive DS Maximum positive jitter from destination to source. Positive SD number Number of positive jitters from source to destination. Positive DS number Number of positive jitters from destination to source. Positive SD sum Sum of positive jitters from source to destination. Positive DS sum Sum of positive jitters from destinatio n to source. Positive SD average Average positive jitters from source to destination. Positive DS average Average positive jitters from destination to source. Positive SD square-sum Square sum of positive jitters from source to destination. Positive DS square-sum Square sum of positive jitters from destination to source.

Min negative SD

Min negative DS

Max negative SD

Max negative DS

Negative SD number Number of negative jitters from source to destination. Negative DS number Number of negative jitters from destination to source.

Negative SD sum

Negative DS sum

Negative SD average

Negative DS average

Negative SD square-sum Square sum of negative jitter s from sour ce to desti nati on. Negative DS square-sum Square sum of negative jitter s from dest inat ion to source.

Minimum absolute value among negative j itter s fr o m s our ce t o destination.

Minimum absolute value among destination to source.

Maximum absolute value among negative jitt ers from source to destination.

Maximum absolute value among destination to source.

Sum of absolute destination.

source. Average absolute value

destination. Average ab solute val ue

source.

One way results

Max SD delay Maximum delay from source to destination. Max DS delay Maximum delay from destination to source. Min SD delay Minimum delay from source to destination. Min DS delay Minimum delay from destination to source. Number of SD delay Number of delays from source to destinati on. Number of DS delay Number of delays from destina tion to sourc e.

Unidirectional delay result.

voice operations.

Page 45

Field

Description

been monitored for data

Sum of SD delay Sum of delays from source to destination. Sum of DS delay Sum of delays from destination to source. Square-Sum of SD delay Square sum of delays from source to destination. Square-Sum of DS delay Squar e su m of delay s from destination to source. SD lost packets Number of lost packets from the source to the destination. DS lost packets Number of lost packets from the destination to the source. Lost packets for unknown reason Number of lost packets for unknown reasons.

Voice scores

Max MOS value Maximum MOS value. Min MOS value Minimum MOS value. Max ICPIF value Maximum ICPIF value. Min ICPIF value Minimum ICPIF value. Reaction statistics Statistics about the reaction entry in the counting interval. Index ID of a reaction entry. Checked Element Monitored element. Threshold Type Threshold type.

Checked Num

Over-threshold Num Number of threshold violations.

Path

Hop IP

Voice parameters. This field is available only for the voice operation.

Number of targets that have collection.

Serial number for the path in the path jitter operation. This field is available only for the path jitter oper atio n.

IP address of the hop. This field is available only for the path jitter operation.

Path-jitter results

Jitter number

Min/Max/Average jitter

Positive jitter number

Min/Max/Average positive jitt er

Sum/Square-Sum positive jitter

Path jitter operation results. This field is available only for the path jitter oper atio n.

Number of jitters. This field is available only for the path jitter oper atio n.

Minimum/maximum/average positive jitter in milliseconds. This field is available only for the path jitter oper atio n.

Number of positive jitters. This field is available only for the path jitter oper atio n.

Minimum/maximum/average positive jitter in milliseconds. This field is available only for the path jitter oper atio n.

Sum/square sum of positive jitters. This field is available only for the path jitter oper atio n.

Page 46

Field

Description

metric

Probes in the

umber of

Number of probes of which the duration

Probes in the

umber of

umber of probes of

which the duration

Probes in the

umber of

Probes in the

umber of

Number of sent

Number of packets of

Number of sent

Number of packets of

way jitter

Number of sent

Negative jitter number

Min/Max/Average negative jitter

Sum/Square-Sum negative jitter

Number of negative jitters. This field is available only for the path jitter oper atio n.

Minimum/maximum/average negative jitter in milliseconds. This field is available only for the path jitter oper atio n.

Sum/square sum of negative jitters. This field is available only for the path jitter oper atio n.

Table 11 Description of the threshold monitoring fields

Monitored performance

probe-duration

probe-fail

Threshold type

accumulate

average N/A N/A N/A

consecutive

accumulate

consecutive

Collect data in Checked Num Over-threshold Num

counting interval.

completed probes.

N completed probes.

exceeds the threshold.

N exceeds the threshold.

Number of probe failures.

RTT

jitter-DS/jitter-SD

OWD-DS/OWD-SD N/A

packet-loss accumulate

ICPIF N/A N/A N/A N/A MOS N/A N/A N/A N/A

Related commands

statistics interval

filename

Packets sent in

accumulate

average N/A N/A N/A

accumulate

average N/A N/A N/A

the counting interval.

Packets sent in the counting interval.

packets.

which the round-trip time exceeds the threshold.

which the oneexceeds the threshold.

Number of packets of which the one-way delay exceeds the threshold.

Number of packet loss.

Use filename to specify a file to be transferred between the FTP server and the FTP client.

Page 47

Use undo filename to restore the default.

Syntax

filename filename undo filename

Default

No file is specified.

Views

FTP operation view

Predefined user roles

network-admin

Parameters

filename: Specifies the nam e of a file, a case-sensitive string of 1 to 200 chara cters that cannot contain slashes (/).

Examples

# Specify config.txt as the f ile t o b e trans f er red b etween the FTP server a nd the F T P client for the FTP operation.

<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type ftp [Sysname-nqa-admin-test-ftp] file name config.txt

frequency

Use frequency to specify the interval at which the NQA operation repeats. Use undo frequency to restore the default.

Syntax

frequency interval undo frequency

Default

The interval between two consecutive voice or path jitter operations is 60000 milliseconds. The interval between two consecutive operations of other types is 0 milliseconds.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view ICMP/UDP echo operation vie w ICMP/path/UDP jitter operation view UDP tracert operation vie w

Predefined user roles

network-admin

Parameters

interval: Specif ies th e interval between t wo c ons ec u ti ve operations, in the range of 0 to 604800000 milliseconds. An interval of 0 m illisec onds c onf igures N QA to perform the operat ion o nly onc e, an d not to generate any statistics.

Page 48

Usage guidelines

If an operation is not completed when the interval is reached, the next operation does not start.

Examples

# Configure the ICMP echo operation to repeat every 1000 milliseconds.

<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] frequency 1000

history-record enable

Use history-record enable to enable the saving of history records for the NQA operation. Use undo history-record enable to disable the saving of history records.

Syntax

history-record enable undo history-record enable

Default

The saving of history records is enabled only for the UDP tracert operation.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP operation view ICMP/UDP echo operation view UDP tracert operation view

Predefined user roles

network-admin

Usage guidelines

To display the history records of the NQA operation, use the display nqa history command. The undo form of the command also removes existing history records of an NQA operation.

Examples

# Enable the saving of history records for the NQA operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] history-record enable

Related commands

display nqa history

history-record keep-time

Use history-record keep-time to set the lifetime of history records for an NQA operation. Use undo history-record keep-time to restor e the de f ault.

Syntax

history-record keep-time keep-time

Page 49

undo history-record keep-time

Default

The history records of an NQA operation are kept for 120 minutes.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP operation view ICMP/UDP echo operation view UDP tracert operation view

Predefined user roles

network-admin

Parameters

keep-time: Specifies how long the history records can be saved. The value range is 1 to 1440 minutes.

Usage guidelines

When an NQA operation completes, the timer starts. All records are removed when the lifetime is reached.

Examples

# Set the lifetime of the history records to 100 minutes for the ICMP echo operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] history-record keep-time 100

history-record number

Use history-record number to set the maximum number of history records that can be saved for an NQA operation.

Use undo history-record number to restore the default.

Syntax

history-record number number undo history-record number

Default

A maximum of 50 history records can be saved for an NQA operation.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP operation view ICMP/UDP echo operatio n vie w UDP tracert operation view

Predefined user roles

network-admin

Parameters

number: Specifies the maximum number of history records that can be saved for an NQA operation. The value range is 0 to 50.

Page 50

Usage guidelines

If the number of history records for an NQA operation exceeds the maximum number, earliest history records are removed.

Examples

# Set the maximum number of history records to 10 for the ICMP echo operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] history-record number 10

init-ttl

Use init-ttl to set the TTL value for UDP packets in the start round of the UDP tracert operation. Use undo init-ttl to restore the default.

Syntax

init-ttl value undo init-ttl

Default

The NQA client sends a UDP packet with the TTL value 1 to start the UDP tracert operation.

Views

UDP tracert operation view

Predefined user roles

network-admin

Parameters

value: Specifies the TTL value in the range of 1 to 255.

Examples

# Set the TTL value to 5 for the UDP packets in the start round.

<Sysname> system-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type udp-tracert [Sysname-nqa-admin-test-udp-tracert] init-ttl 5

lsr-path

Use lsr-path to specify a loose source routing (LSR) path. Use undo lsr-path to restore the default.

Syntax

Default

lsr-path ip-address&<1-8> undo lsr-path

No LSR path is configured.

Page 51

Views

Path jitter operation view

Predefined user roles

network-admin

Parameters

ip-address&<1-8>: Spec ifies a space-separ ated list of up to e ight IP addresses. Each IP address represents a hop on the path.

Usage guidelines

The path jitter operation first uses tracert to det ect eac h hop to t he destination. It then sends ICMP echo requests to measure the delay and jitters from the source to each node. If multiple routes exist between the source and destination, the operation uses the path specified by using lsr-path command.

Examples

# Specify 10.1.1.20 and 10.1.2.10 as the hops on the LSR path for the path jitter operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type path-jitter [Sysname-nqa-admin-test- path-jitter] lsr-path 10.1.1.2 0 10.1.2.10

max-failure

Use max-failure to set the maximum number of consecutive probe failures in a UDP tracert operation.

Use undo max-failure to restore the default.

Syntax

max-failure times undo max-failure

Default

A UDP tracert operation stops and fails when it detects five consecutive probe failures.

Views

UDP tracert operation view

Predefined user roles

network-admin

Parameters

times: Specifies the m aximum number in the range of 0 to 255. When this ar gument is set to 0 or 255, the UDP tracert operation does not stop when consecutive probe failures occur.

Usage guidelines

When a UDP tracert operation detects the maximum number of consecutive probe failures, the operation fails and stops probing the path.

Examples

# Set the maximum number of consecutive probe failures to 20 in a UDP tracert operation.

<Sysname> system-view [Sysname] nqa entry admin test

Page 52

[Sysname-nqa-admin-test] type udp-tracert [Sysname-nqa-admin-test-udp-tracert] max-failure 20

mode

Use mode to set the data transmission mode for the FTP operation. Use undo mode to restore the default.

Syntax

mode { active | passive } undo mode

Default

The FTP operation uses the active data transmission mode.

Views

FTP operation view

Predefined user roles

network-admin

Parameters

active: Sets the data transmission mode to active. The FTP server initiates a connection request. passive: Sets the data transmission mode to passive. The FTP client initiates a connection request.

Examples

# Set the data transmission mode to passive for the FTP operation.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type ftp [Sysname-nqa-admin-test-ftp] mode passive

next-hop ip

Use next-hop ip to specify the next hop IPv4 address for probe packets. Use undo next-hop ip to restore the default.

Syntax

next-hop ip ip-address undo next-hop ip

Default

No next hop IPv4 address is specified for probe packets.

Views

ICMP echo operation view

Predefined user roles

network-admin

Parameters

ip-address: Specifies the IPv4 address of the next hop.

Page 53

Usage guidelines

If the next hop IPv4 address is not configured, the device searches the routing table to determine the next hop IPv4 address for the probe packets.

Examples

# Specify 10.1.1.1 as the next hop IPv4 address for the ICMP echo operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] next-hop ip 10.1.1.1

next-hop ipv6

Use next-hop ipv6 to specify the next hop IPv6 address for probe packets. Use undo next-hop ipv6 to restore the default.

Syntax

next-hop ipv6 ipv6-address undo next-hop ipv6

Default

No next hop IPv6 address is specified for probe packets.

Views

ICMP echo operation view

Predefined user roles

network-admin

Parameters

ipv6-address: Specifies the IPv6 address of the next hop. IPv6 link-local addresses are not supported.

Usage guidelines

If the next hop IPv6 address is not configured, the device searches the routing table to determine the next hop IPv6 address for the probe packets.

Examples

# Specify 10::1 as the next hop IPv6 address for the ICMP echo operation.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] next-hop ipv6 10::1

no-fragment enabl e

Syntax

Use no-fragment enable to enable the no-fragmentation feature. Use undo no-fragment enable to disable the no-fragmentation feature.

no-fragment enable undo no-fragment enable

Page 54

Default

The no-fragmentation feature is disabled.

Views

UDP tracert operation view

Predefined user roles

network-admin

Usage guidelines

The no-fragmentation feature sets the DF field to 1. Packets with the DF field set cannot be fragmented during the forwarding process.

You can use this command to test the path MTU of a link.

Examples

# Enable the no-fragmentation feature for the UDP tracert operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-tracert [Sysname-nqa-admin-test-udp-tra ce rt] no-fragment enable

nqa

Use nqa to create an NQA operation and enter its view, or enter the view of an existing NQA operation.

Use undo nqa to remove the operation.

Syntax

nqa entry admin-name operation-tag undo nqa { all | entry admin-name operation-tag }

Default

No NQA operations exist.

Views

System view

Predefined user roles

network-admin

Parameters

all: Removes all NQA operations.

Examples

# Create an NQA operation with administrator nam e admin and operat ion tag test, and enter NQ A operation view.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test]

Page 55

nqa agent enable

Use nqa agent enable to enable the NQA client. Use undo nqa agent enable to disable the NQA client and stop all operations being performed.

Syntax

nqa agent enable undo nqa agent enable

Default

The NQA client is enabled.

Views

System view

Predefined user roles

network-admin

Examples

# Enable the NQA client.

<Sysname> sy stem-view [Sysname] nqa agent enable

Related commands

nqa server enable

nqa schedule

Use nqa schedule to configure scheduling parameters for an NQA operation. Use undo nqa schedule to stop the operation.

Syntax

nqa schedule admin-name operation-tag start-time { hh:mm:ss [ yyyy/mm/dd | mm/dd/yyyy ] | now } lifetime { lifetime | forever } [ recurring ]

undo nqa schedule admin-name operation-tag

Default

No schedule is configured for an NQA operation.

Views

System view

Predefined user roles

network-admin

Parameters

start-time: Specifies the start time and date of the NQA operation. hh:mm:ss: Specifies the start time of an NQA operation.

Page 56

yyyy/mm/dd: Specifies the start date of an NQA operation. The default value is the current s ystem time, and the value for the yyyy argument is in the range of 2000 to 2035.

mm/dd/yyyy: Specifies the start date of an N QA operation. The default value is the current s ystem time, and the value for the yyyy argument is in the range of 2000 to 2035.

now: Starts the operation immediately. lifetime: Specifies the duration of an operation.

lifetime: Specifies the duration of an operation in seconds. The value range is 1 to 2147483647.

forever: Performs the operation until you stop it by using the undo nqa schedule command. recurring: Runs the operation automatically at the start time and for the specified duration. If you do

not specify this keyword, the NQA operation is performed only once at the specified date and time.

Usage guidelines

You cannot enter the operation view or operation type view of a scheduled NQA operation. The NQA operation works between the s pecified start time and the e nd time (the start time plus

operation duration). If the specified start time is ahead of the system time, the operation starts immediately. If both the specified start time and end time are ahead of the system time, the operation does not start. To display the current system time, use the d isplay clock command.

Specify a lifetime long enough for an operation to complete.

Examples

# Schedule the operation with administrator name admin and operation tag test to start on 08:08:08 2008/08/08 and last 1000 sec onds .

<Sysname> system-view [Sysname] nqa schedule admin test start-time 08:08: 08 2008/08/08 lifetim e 1000 recurring

Related commands

destination ip display clock (Fundamentals Command Reference) nqa entry type

operation (FTP operation view)

Use operation to specify the operation type for the FTP operation. Use undo operation to restore the default.

Syntax

operation { get | put } undo operation

Default

The FTP operation type is get.

Views

FTP operation view

Predefined user roles

network-admin

Page 57

Parameters

get: Gets a file from the FTP server. put: Transfers a file to the FTP server.

Usage guidelines

When you perform the put operation with the filename comm and configured, make sure the file exists on the NQA client.

If you get a file from the FTP server, make sure the file specified in the URL exists on the FTP server. The NQA client does not save the file obtained from the FTP server.

Use a small file for the FTP operation. A big file might result in transfer failure because of timeout, or might affect other services for occupying much network bandwidth.

Examples

# Set the operation type to put for the FTP operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type ftp [Sysname-nqa-admin-test-ftp] operation put

Related commands

password username

operation (HTTP operation view)

Use operation to specify the operation type for the HTTP operation. Use undo operation to restore the default.

Syntax

operation { get | post | raw } undo operation

Default

The HTTP operation type is get.

Views

HTTP operation view

Predefined user roles

network-admin

Parameters

get: Gets data from the HTTP server. post: Transfers data to the HTTP server. raw: Sends the RAW request to the HTTP server.

Usage guidelines

The HTTP operation use HTTP requests as probe packets. For the get or post operation, the content in the request is obtained from the URL specified by the url

command.

Page 58

For the raw operation, the content in the request is configured in raw request view. You can use the

raw-request command to enter the raw request view.

Examples

# Set the operation type to raw for the HTTP operation.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type http [Sysname-nqa-admin-test-http] operation raw

Related commands

password raw-request username

out interface

Use out interface to specify the output interface for probe packets. Use undo out interface to restore the default.

Syntax

out interface interface-type interface-number undo out interface

Default

The output interface for probe packets is not specified. The NQA client determines the output interface based on the routing table lookup.

Views

DHCP operation view ICMP echo operation view UDP tracert operation view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number.

Usage guidelines

For successful operation, the specified output interface must be up. If both the next-hop and out interface commands are configured for the ICMP echo operation, the

out interface command does not take effect.

Examples

# Specify GigabitEthernet 1/0/1 as the output interface for probe packets in the UDP tracert operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-tracert [Sysname-nqa-admin-test-udp-tracert] out interface gigabitethernet 1/0/1

Page 59

password

Use password to specify a password. Use undo password to restore the default.

Syntax

password { cipher | simple } string undo password

Default

No password is specified.

Views

FTP operation view HTTP operation view

Predefined user roles

network-admin

Parameters

cipher: Specifies a password in encrypted form. simple: Specif ies a password in plaintext form . F or security purposes, the password spec ified in

plaintext form will b e stored in encrypted form. string: Specif ies the pass word. The plaintext f orm of the p asswor d is a c ase -sens itive str ing of 1 t o

32 characters. The encrypted form of the password is a case-sensitive string of 1 to 73 characters.

Examples

# Set the FTP login password to ftpuser.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type ftp [Sysname-nqa-admin-test-ftp] password simple ftpuser

Related commands

operation username

probe count

Use probe count to specify the probe times. Use undo probe count to restore the default.

Syntax

Default

probe count times undo probe count

In an UDP tracert operation, the NQA client sends three probe packets to each hop along the path. In other types of operations, the NQA client performs one probe to the destination per operation.

Page 60

•

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP operation view ICMP/UDP echo operation view ICMP/UDP jitter operation view UDP tracert operation view

Predefined user roles

network-admin

Parameters

times: Specifies the probe times.

For the UDP tracert operation, this argument specifies the times of probes to each hop along

the path. The value range for this argument is 1 to 10.

For other types of operations, this argument specifies the times of probes to the destination per

operation. The value range for this argument is 1 to 15.

Usage guidelines

The following describes how NQA performs different types of operations:

A TCP or DLSw operation sets up a connection. A UDP jitter operation sends a number of probe packets. The number of probe packets is set by

using the probe packet-number command. An FTP operation uploads or downloads a file. An HTTP operation gets a Web page. A DHCP operation gets an IP address through DHCP. A DNS operation translates a domain name to an IP address. An ICMP echo sends an ICMP echo request. A UDP echo operation sends a UDP packet. An SNMP operation sends one SNMPv1 packet, one SNMPv2c packet, and one SNMPv3

packet.

A path jitter operation is accomplished in the following steps:

a. The operation uses tracert to obtain the path from the NQA client to the destination. A

maximum of 64 hops can be detected.

b. The NQA client sends ICMP echo requests to each hop along the path. The number of

ICMP echo requests is set by using the probe packet-number command.

A UDP tracert operation determines the routing path from the source to the destination. The

number of probe packets sent to each hop is set by using the probe count command.

If an operation is to perform multiple probes, the NQA client starts a new probe in one of the following conditions:

This command is not available for the voice or path jitter operations. Each of these operations performs only one probe.

Examples

# Configure the ICMP echo operation to perform 10 probes.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo

The NQA client receives responses to packets sent in the last probe. The probe timeout time expires.

Page 61

[Sysname-nqa-admin-test-icmp-echo] probe count 10

probe packet-interval

Use probe packet-interval to configure the packet sending interval in the probe. Use undo probe packet-interval to restore the default.

Syntax

probe packet-interval interval undo probe packet-interval

Default

The packet sending interval is 20 milliseconds.

Views

ICMP jitter operation view Path jitter operation view UDP jitter operation view Voice operation view

Predefined user roles

network-admin

Parameters

interval: Specifies the sending interval in the range of 10 to 60000 milliseconds.

Examples

# Configure the UDP jitter operation to send packets every 100 milliseconds.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jitter] probe packet-interval 100

probe packet-number

Use probe packet -number to set t he number of packet s to be sent in a UDP jitter, path jitter, or voice probe.

Use undo probe packet-number to restore the default.

Syntax

probe packet-number packet-number undo probe packet-number

Default

Views

A UDP jitter or path jitter probe sends 10 packets and a voice probe sends 1000 packets.

ICMP jitter operation view Path jitter operation view UDP jitter operation view

Page 62

•

Voice operation view

Predefined user roles

network-admin

Parameters

packet-number: Specifies the number of packets to be sent per probe. Available value ranges include:

10 to 1000 for the ICMP jitter, UDP jitter, or path jitter operation. 10 to 60000 for the voice operation.

Examples

# Configure the UDP jitter probe to send 100 packets.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jitter] probe packet-number 100

probe packet-timeout

Use probe packet -timeout to set th e t imeout time for wait ing for a response in the UDP jitter, path jitter, or voice operation.

Use undo probe packet-timeout to restore the default.

Syntax

probe packet-timeout timeout undo probe packet-timeout

Default

The response timeout time in the ICMP jitter, UDP jitter, and path jitter operations is 3000 milliseconds.

The response timeout time in the voice operation is 5000 milliseconds.

Views

ICMP jitter operation view Path jitter operation view UDP jitter operation view Voice operation view

Predefined user roles

network-admin

Parameters

timeout: Specifies the timeout time in milliseconds. The value range is 10 to 3600000.

Examples

# Set the response timeout time to 100 milliseconds in the UDP jitter operation.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jitter] probe packet-timeout 100

Page 63

•

probe timeout

Use probe timeout to set the probe timeout time. Use undo probe timeout to restore the default.

Syntax

probe timeout timeout undo probe timeout

Default

The timeout time of a probe is 3000 milliseconds.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP operation view ICMP/UDP echo operation view UDP tracert operation view

Predefined user roles

network-admin

Parameters

timeout: Specifies the probe timeout time in milliseconds. Available value ranges include:

10 to 86400000 for the FTP or HTTP operation. 10 to 3600000 for the DHCP, DNS, DLSw, ICMP echo, SNMP , TCP, UDP echo, or UDP tracert

operation.

Usage guidelines

If a probe does not complete within the period, the probe is timed out.

Examples

# Set the probe timeout time to 10000 milliseconds for the DHCP operation.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type dhcp [Sysname-nqa-admin-test-dhcp] probe timeout 10000

raw-request

Use raw-request to enter raw request view and specify the content of an HTTP request. Use undo raw-request to restore the default.

Syntax

raw-request

Default

Views

undo raw-request

The contents of an HTTP raw request are not specified.

HTTP operation view

Page 64

Predefined user roles

network-admin

Usage guidelines

This command places you in raw request view and deletes the previously configured request content. To ensure successful operations, make sure the request content is in the correct format.

If the HTTP operation type is set to raw, you must enter raw request view and configure the request content to be sent to the HTTP server.

Examples

# Enter raw request view and specify the content of a GET request for the HTTP operation.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type http [Sysname-nqa-admin-test-http] raw-request [Sysname-nqa-admin-test-http-raw-request] GET /sdn/ui/app/index HTTP/1.0\r\nHost:

172.0.0.2\r\n\r\n

reaction checked-element { jitter-ds | jitter-sd }

Use re action checked-element { jitter-ds | jitter-sd } to configure a react ion entr y for monitorin g one-way jitter in the NQA operation.

Use undo reaction to delete the specified reaction entry.

Syntax

reaction item-number checked-element { jitter-ds | jitter-sd } threshold-type { accumulate

accumulate-occurrences | average } threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

undo reaction item-number

Default

No reaction entries for monitoring one-way jitter exist.

Views

ICMP jitter operation view UDP jitter operation view Voice operation view

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

jitter-ds: Specifies the destination-to-source jitter of each probe packet as the monitored element (or performance metric).

jitter-sd: Specifies source-to-destination jitter of each probe packet as the monitored element. threshold-type: Specifies a threshold type. accumulate accumulate-occurrences: Checks the total number of threshold violations in the

operation. The value range is 1 to 14999 for the ICMP jitter and UDP jitter operations, and 1 to 59999 for the voice operation.

average: Checks the average one-way jitter.

Page 65

threshold-value: Specifies threshold range in milliseconds.

upper-threshold: Specifies the upper limit in the range of 0 to 3600000. lower-threshold: Specifies the lower limit in the range of 0 to 3600000. It must not be greater than the

upper limit.

action-type: Specifies the action to be triggered. The def ault actio n is none. none: Specifies the action of displaying results on the terminal display. trap-only: Specifies the ac t ion of disp laying results on the t er minal display and m eanwh ile s en din g

SNMP trap messages to the NMS.

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reaction entr y, use the undo reaction command to delete the entry, and then configure a new one.

Only successful probe packets are monitored. Statistics about failed probe packets are not collected.

Examples

# Create reaction entry 1 for monitoring the average destination-to-source jitter of UDP jitter packets, and set the upper limit to 50 m illiseconds and the lower limit to 5 millisecon ds. Before the NQA operation starts, the initial state of the reaction e ntry is invalid. After the operation, the average destination-to-sourc e jitter is c heck ed against the threshold ra nge. If it ex ceeds t he upper limit, the state of the reaction entr y is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jit ter] reaction 1 checked-element jitter-ds threshold-type

average threshold-value 50 5 ac tion-type trap-only

# Create reac tion entr y 2 for monitori ng the dest ination-to-source jitter of UDP jitt er probe pack ets, and set the upper l imit to 50 millisec onds, and the lower lim it to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the destination-to-sourc e jitter is check ed against the thre shold range. If the t otal number of threshold violations reaches or exceeds 100, the state of the entry is set to over-threshold. Otherwise, the state of the entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jitter] reaction 2 checked-element jitter-ds threshold-type

accumulate 10 0 threshold-value 50 5 action-type trap-only

reaction checked-element { owd-ds | owd-sd }

Use reaction checked-element { owd-ds | owd-sd } to configure a reaction entry for monitoring the one-way delay.

Use undo reaction to delete the specified reaction entry.

Syntax

reaction item-number checked-element { owd-ds | owd-sd } threshold-value upper-threshold

lower-threshold undo reaction item-number

Page 66

Default

No reaction entries for monitoring the one-way delay exist.

Views

ICMP jitter operation view UDP jitter operation view Voice operation view

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

owd-ds: Specifies the destination-to-source delay of each probe packet as the monitored element. owd-sd: Specifies the source-to-destination delay of each probe packet as the monitored element. threshold-value: Specifies threshold range in milliseconds.

upper-threshold: Specifies the upper limit in the range of 0 to 3600000. lower-threshold: Specifies the lower limit in the range of 0 to 3600000. It must not be greater than the

upper limit.

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reaction entr y, use the undo reaction command to delete the entry, and then configure a new one.

Only successful probe packets are monitored. Statistics about failed probe packets are not collected. No actions can be configured for a reaction entry of monitoring one-way delays. To display the

monitoring results and statistics, use the display nqa reaction counters and display nqa

statistics commands.

Examples

# Create reaction entry 1 f or m onitoring the dest inatio n-to-sourc e dela y of ever y UDP jitter p acket, and set the upper limit to 50 milliseconds and lower limit to 5 milliseconds. Before the NQA operation starts, the initial stat e of the reaction e ntry is invalid. The destination-to-sourc e delay is calculated after the response t o the pr obe pac k et arrives. If the d ela y excee ds th e upper lim it, the s tate of the reaction entry is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element owd-ds threshold-value 50

reaction checked-element icpif

Syntax

Use reaction checked-element icpif to configure a reaction entry for monitoring the ICPIF value in the voice operation.

Use undo reaction to delete the specified reaction entry.

reaction item-number checked-element icpif threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

Page 67

undo reaction item-number

Default

No reaction entries for monitoring ICPIF values exist.

Views

Voice operation view

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

threshold-value: Specifies threshold range.

upper-threshold: Specifies the upper limit in the range of 1 to 100. lower-threshold: S pecifies the lower limit in the ran ge of 1 to 100. It must not be greater than the

upper limit.

action-type: Specifies what action to be triggered. The default action is none. none: Specifies the action of displaying results on the terminal display. trap-only: Specifies the ac t ion of disp laying results on the t er minal display and m eanwh ile s en din g

SNMP trap messages to the NMS.

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reaction entr y, use the undo reaction command to delete the entry, and then configure a new one.

Examples

# Create reaction entry 1 for monitoring the ICPIF value in the voice operation, and set the upper limit to 50 and lower lim it to 5. Befor e the voice o peration s tarts, the initial state of th e reaction entr y is invalid. After the operation, the ICPIF value is checked against the threshold range. If it exceeds the upper limit, the stat e of the reaction e ntry is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once th e state of the reaction e ntry changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type voice [Sysname-nqa-admin-test-voice] reaction 1 checked-element icpif threshold-value 50 5

action-type trap-only

reaction checked-element mos

Use reaction checked -element mos to configure a reaction entry for monitoring the MOS value in the voice operation.

Use undo reaction to delete the specified reaction entry.

Syntax

Default

reaction item-number checked-element mos threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

undo reaction item-number

No reaction entries for monitoring the MOS value exist.

Page 68

Views

Voice operation view

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

threshold-value: Specifies threshold range.

upper-threshold: Specifies the upper limit in the range of 1 to 500. lower-threshold: Specif ies the lower limit in the range of 1 to 500. It must not be greater th an the

upper limit.

SNMP trap messages to the NMS.

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reaction entr y, use the undo reaction command to delete the entry, and then configure a new one.

For the MOS threshold, the number is expressed in three digits representing ones, tenths, and hundredths. For example, to express a MOS threshold of 1, enter 100.

Examples

# Create reaction entry 1 for monitoring the MOS value of the voice operation, and set the upper limit to 2 and lower limit to 1. Befor e the NQA operation starts, the in itial state of the reaction entry is invalid. After the operation, the MOS value is checked against the threshold range. If it exceeds the upper limit, the stat e of the reactio n entry is set to over-threshold. If it is below the lower limit, the state is set to below-thr eshold. Once the state of the reaction e ntry changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type voice [Sysname-nqa-admin-test-voice] reaction 1 checked-element mos threshold-value 200 100

action-type trap-only

reaction checked-element packet-loss

Use reaction checked-element packet-loss to conf igure a reaction entry for monitoring packet loss in UDP jitter or voice operation.

Use undo reaction to delete the specified reaction entry.

Syntax

Default

reaction item-number checked-element packet-loss threshold-type accumulate accumulate-occurrences [ action-type { none | trap-only } ]

undo reaction item-number

No reaction entries for monitoring packet loss exist.

Page 69

Views

ICMP jitter operation view UDP jitter operation view Voice operation view

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

threshold-type: Specifies a threshold type. accumulate accumulate-occurrences: Specifies the total number of lost pack ets in the operation.

The value range is 1 to 15 000 for th e ICMP jitter a nd UDP jitter operations , and 1 to 60000 for the voice operation.

SNMP trap messages to the NMS.

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reac tion entr y, use the undo reaction command to delete the entry, and then configure a new one.

Examples

# Create reaction entr y 1 for monitoring p acket loss in the UDP jitter operation. Befor e the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the total number of the lost packets is checked against the threshold. If the number reaches or exceeds 100, the state of the reaction entr y is set to over-thres hold. Otherwise, the state is set to be low-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element packet-loss

threshold-type accumulate 100 action-type trap-only

reaction checked-element probe-duration

Use reaction checked-element probe-duration to configure a reac tion entry for monitoring the probe duration.

Use undo reaction to delete the specified reaction entry.

Syntax

reaction item-number checked-element probe-duration threshold-type { accumulate

accumulate-occurrences | average | consecutive consecutive-occurrences } threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

Default

undo reaction item-number

No reaction entries for monitoring the probe duration exist.

Page 70

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP operation view ICMP/UDP echo operation vie w

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

threshold-type: Specifies a threshold type. accumulate accumulate-occurrences: Check s the total number of threshold vi olations. The value

range is 1 to 15.

average: Checks the average probe duration. consecutive consecutive-occurrences: Specifies the number of consecutive threshold violations

after the NQA operation starts. The value range is 1 to 16. threshold-value: Specifies threshold range in milliseconds.

upper-threshold: Specifies the upper limit in the range of 0 to 3600000. lower-threshold: Specifies the lower limit in the range of 0 to 3600000. It must not be greater than the

upper threshold.

SNMP trap messages to the NMS. This keyword is not available for the DNS operation.

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reaction entr y, use the undo reaction command to delete the entry, and then configure a new one.

Only successful probe packets are monitored. Statistics about failed probe packets are not collected.

Examples

# Create reaction entry 1 for monitoring the average probe duration of ICMP echo operation, and set the upper limit to 50 milliseconds and lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the react ion entry is invalid. After the operation, th e average probe duration is checked. If it exceeds the upper lim it, the state is set t o over -thresho ld. If it is belo w the lo wer lim it, the state of the reaction entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-duration

threshold-type average threshold-value 50 5 action-t ype trap-only

# Create reac tion entry 2 for monitoring the probe duration of ICMP echo oper ation, and set the upper limit to 50 milliseconds and the lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the accumulated probe duration is checked against the thres h old ran ge. If the total number of thr eshold v io lat ions r eaches or exc eeds 10, the state of the entr y is set to over -threshold. If it is below the lower thresh old, the state of the entry is set to below-thres hold. Once the state of the reaction entr y changes, a trap m essage is generated and sent to the NMS.

<Sysname> sy stem-view [Sysname] nq a entry admin test

Page 71

[Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] reaction 2 checked-elem ent probe-duration

threshold-type accumulate 10 threshold-value 50 5 action-type trap-only

# Create reaction entry 3 for monitoring the probe duration time of ICMP echo operation, and set the upper limit to 50 milliseconds and the lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the r eaction entry is invalid . After t he operat io n, th e c ons ec ut ive pr obe duration is checked against the threshold range. If the total number of consecutive threshold violations reaches or exceeds 10, the s tate of the entry is se t to over -threshold. If it is belo w the low er threshold, the state of the entry is set to belo w-threshold. Once the s tate of the reaction entry changes , a trap message is generat ed and sent to the NM S.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] reaction 3 checked-element prob e-duration

threshold-type consecutive 10 threshold-value 50 5 action-type trap-only

reaction checked-element probe-fail (for trap)

Use reaction checked-element probe-fail to configure a reaction entry for monitoring the probe failures of the operation.

Use undo reaction to delete the specified reaction entry.

Syntax

reaction item-number checked-element probe-fail threshold-type { accumulate accumulate-occurrences | consecutive consecutive-occurrences } [ action-type { none | trap-only } ]

undo reaction item-number

Default

No reaction entries for monitoring probe fai lures ex ist.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP operation view ICMP/UDP echo operation vie w

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

threshold-type: Specifies a threshold type. accumulate accumulate-occurrences: Checks the total number of probe failures. The value range is

1 to 15. consecutive consecutive-occurrences: Checks the maximum number of consecutive probe failures.

The value range is 1 to 16.

SNMP trap messages to the NMS. This keyword is not available for the DNS operation.

Page 72

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reaction entr y, use the undo reaction command to delete the entry, and then configure a new one.

Examples

# Create reaction entr y 1 for m onitorin g the pr obe f ai lur es in ICMP echo operation. Before the NQ A operation starts, the initial state of the reac tion entr y is inval id. If th e total n umber of probe f ailures reaches or exceeds 10, the state of the entry is set to over-threshold. If it is below the threshold, the state of the entry is set to belo w-threshold. Once the s tate of the reaction entry changes , a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] r eaction 1 checked-e lement probe-fail threshold-type

accumulate 10 action-type trap-only

# Create reaction entry 2 for monitoring the probe f ai lur es in ICMP ec ho operation. Before the NQA operation starts, the i nitial state of the reaction entry is inval id. If the num ber of consecuti ve probe failures reaches or exceeds 10, the state of the entr y is set to over-threshold. If it is below the threshold, the state of the entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] reaction 2 checked-element probe-fail threshold-type

consecutive 10 action-type trap-only

reaction checked-element probe-fail (for trigger )

Use reaction checked-element probe-fail to configure a reaction entry for monitoring probe failures.

Use undo reaction to remove the specified reaction entry.

Syntax

reaction item-number checked-element probe-fail threshold-type consecutive consecutive-occurrences action-type trigger-only

undo reaction item-number

Default

No reaction entries for monitoring probe fai lures ex ist.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP operation view ICMP/UDP echo operation vie w

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

threshold-type: Specifies a threshold type. consecutive consecutive-occurrences: Checks the maximum number of consecutive probe failures,

in the range of 1 to 16.

Page 73

•

action-type: Specifies what action to be triggered. trigger-only: Triggers other modules to react to certain conditions.

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reaction entr y, use the undo reaction command to delete the entry, and then configure a new one.

Examples

# Create reaction entry 1. If the num ber of consecutive probe failures reaches 3, collab oration is triggered.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type tcp [Sysname-nqa-admin-test-tcp] reacti on 1 checked-element probe-fail threshold-type

consecutive 3 action-type trigger-only

Related commands

track (High Availability Command Reference)

reaction checked-element rtt

Use reaction checked-element rtt to co nfigure a reaction entry for m onitoring packet round-trip time.

Use undo reaction to delete the specified reaction entry.

Syntax

reaction item-number checked-element rtt threshold-type { accumulate

accumulate-occurrences | average } threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

undo reaction item-number

Default

No reaction entries for monitoring packet round-trip time exist.

Views

ICMP jitter operation view UDP jitter operation view Voice operation view

Predefined user roles

network-admin

Parameters

item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.

threshold-type: Specifies a threshold type. accumulate accumulate-occurrences: Check s the total number of threshold violatio ns. Available

value ranges include:

1 to 15000 for the ICMP jitter and UDP jitter operations. 1 to 60000 for the voice operation.

average: Checks the packet average round-trip time. threshold-value: Specifies threshold range in milliseconds.

Page 74

upper-threshold: Specifies the upper limit in the range of 0 to 3600000. lower-threshold: Specifies the lower limit in the range of 0 to 3600000. It must not be greater than the

upper limit.

SNMP trap messages to the NMS.

Usage guidelines

You cannot edit a reaction entr y after it is create d. To change the attributes in a reaction entr y, use the undo reaction command to delete the entry, and then configure a new one.

Only successful probe packets are monitored. Statistics about failed probe packets are not collected.

Examples

# Create reaction entry 1 for monitoring the average round-trip time of UDP jitter probe packets, and set the upper lim it to 50 milliseconds and low er limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the average packet round-trip time is checked. If it exceeds the upper limit, the state is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once the reaction entr y state changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element rtt threshold-type

average threshold-value 50 5 action-t ype trap-only

# Create reacti on e ntr y 2 f or monitoring the roun d -trip t ime of UDP jitter probe p ac kets, and set the upper limit to 50 milliseconds and lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the packet round-trip time is checked. If the total number of thr eshold violations reaches or exceeds 100, the state of the entr y is set to over-threshold. Other wise, the state of the entry is set to be low-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-jitter [Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element rtt threshold-type

accumulate 10 0 threshold-value 50 5 action-type trap-only

reaction trap

Use reaction trap to configure the sending of traps to the NMS under specific conditions. Use undo reaction trap to restore the default.

Syntax

reaction trap { path-change | probe-failure consecutive-probe-failures | test-complete | test-failure [ accumulate-probe-failures ] }

undo reaction trap { path-change | probe-failure | test-complete | test-failure }

Default

Views

No traps are sent to the NMS.

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view

Page 75

•

ICMP/UDP echo operation view ICMP/UDP jitter operation view UDP tracert operation view

Predefined user roles

network-admin

Parameters

path-change: Sends a trap when the UDP tracert operation detects a different path to the destination.

probe-failure consecutive-probe-failures: Sends a trap to the NMS if the num ber of consecutive

probe failures in an operation is greater than or equal to consecutive-probe-failures. The value range for the consecutive-probe-failures argument is 1 to 15. The system counts the number of consecutive probe failures for each operation, so multiple traps might be sent.

test-complete: Sends a trap to indicate that the operation is completed. test-failure: Sends a trap when an operation fails. For operations other than UDP tracert operation,

the system counts the total number of probe failures in an operation. If the number reaches or exceeds the value for the accumulate-probe-failures argument, a trap is sent for the operation failure.

accumulate-probe-failures: Specifies the to tal number of probe f ailures in an operation. T he value range is 1 to 15. This argument is not supported by the UDP tracert operation.

Usage guidelines

The ICMP jitter, UDP jitter, and voice operations support only the test-complete keyword. The following parameters are not available for the UDP tracert operation:

The probe-failure consecutive-probe-failures option. The accumulate-probe-failures argument.

Examples

# Configure the system to send a trap if five or more cons ecutive probe f ailures occur in an ICMP echo operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-ec ho ] reaction trap probe-failure 5

rresolve-target

Use resolve-target to specify the domain name to be resolved in the DNS operation. Use undo resolve-target to restore the default.

Syntax

resolve-target domain-name

Default

Views

undo resolve-target

The domain name to be resolved in the DNS operation is not specified.

DNS operation view

Page 76

•

Predefined user roles

network-admin

Parameters

domain-name: Specifies the domain name to be resolved. It is a dot-separated case-sensitive string of 1 to 255 characters including letters, digits, hyphens (-), and underscores (_) (for example, aabbcc.com). Each part consists of 1 to 63 characters, and consecutive dots (.) are not allowed.

Examples

# Specify domain1 as the domain name to be resolved.

<Sysname> sy stem-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type dns [Sysname-nqa-admin-test-dns] resolve-target domain1

route-option bypass-route

Use route-option bypa ss-route to enable the routing table bypass feature to test the connectivity to the direct destination.

Use undo route-option bypass-route to disable the routing table bypass feature.

Syntax

route-option bypass-route undo route-option bypass-route

Default

The routing table bypass feature is disabled.

Views

DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view ICMP/UDP echo operation view ICMP/UDP jitter operation view UDP tracert operation view

Predefined user roles

network-admin

Usage guidelines

When the routing table bypass feature is enabled, the follow ing events occur :

The routing table is not searched. Packets are sent to the destination in a directly connected

network. The TTL value in the probe packet is set to 1. The TTL set in the ttl command does not take

effect.

Examples

# Enable the routing table bypass feature.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] route-option bypass-route

Page 77

source interface

Use source interface to specify the IP address of the specified interface as the source IP address of probe packets.

Use undo source interface to restore the default.

Syntax

source interface interface-type interface-number undo source interface

Default

No source IP address is specified for probe packets. The probe packets take the primary IP address of the outgoing interface as their source IP address.

Views

ICMP echo operation view UDP tracert operation view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number.

Usage guidelines

If you execute this command and the source ip or source ipv6 command for an ICMP echo operation multiple times, the most recent configuration takes effect.

If you execute this command and the source ip command for a UDP tracert operation multiple times, the most recent configuration takes effect.

The specified source interface must be up. Otherwise, no probe requests can be sent out.

Examples

# Specify the IP addr ess of int erf ace Gigab itEthernet 1 /0/1 as the source IP addres s of ICMP echo request packets.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] source interface gigabitethernet 1/0/1

Related commands

source ip source ipv6

source ip

Syntax

Use source ip to configure the source IPv4 address for probe packets. Use undo source ip to restore the default.

source ip ip-address undo source ip

Page 78

Default

The probe packets takes the IP address of their output interface as the source IP address.

Views

DHCP/DLSw/FTP/HTTP/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 source IPv4 address for probe packets.

Usage guidelines

If you execute the sou rce interface and source ip com mands for an ICMP echo or UDP tracert operation multiple times, the most recent configuration takes effect.

The specified source IPv4 address must be the IPv4 address of a local interface, and the local interface must be up. Otherwise, no probe packets can be sent out.

Examples

# Specify 10.1.1.1 as the source IPv4 address 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] source ip 10.1.1.1

Related commands

source interface

source ipv6

Use source ipv6 to configure the source IPv6 address for probe packets. Use undo source ipv6 to restore the default.

Syntax

source ipv6 ipv6-address undo source ipv6

Default

The probe packets takes the IPv6 address of their output interface as the source IPv6 address.

Views

ICMP echo operation view

Predefined user roles

network-admin

Parameters

ipv6-address: Specifies the source IPv6 address for probe packets. IPv6 link-local addresses are not supported.

Page 79

Usage guidelines

If you execute the source interface and source ipv6 commands for an ICMP echo operation multiple times, the most recent configuration takes effect.

The specified source IPv6 address must be the IPv6 address of a local interface. The local interface must be up. Otherwise, no probe packets can be sent out.

Examples

# In ICMP echo operation view, specify 1::1 as the source IPv6 address 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] source ipv6 1 ::1

Related commands

source interface

source port

Use source port to configure the source port number for probe packets. Use undo source port to restore the default.

Syntax

source port port-number undo source port

Default

The source port number is not specified.

Views

SNMP/voice operation view UDP echo operation view UDP jitter operation view UDP tracert operation view

Predefined user roles

network-admin

Parameters

port-number: Specifies the source port number in the range of 1 to 65535.

Examples

# Set the source port number to 8000 for probe packets in the UDP echo operation.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-echo [Sysname-nqa-admin-test-udp-echo] source port 8000

statistics hold-time

Use statistics hold-time to set the hold time of statistics groups for an NQA operation.

Page 80

Use undo statistics hold-time to restore the default.

Syntax

statistics hold-time hold-time undo statistics hold-time

Default

The hold time of statistics groups for an NQA operation is 120 minutes.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view ICMP/UDP echo operation view ICMP/path/UDP jitter operation view

Predefined user roles

network-admin

Parameters

hold-time: Specifies the hold time in minutes, in the range of 1 to 1440.

Usage guidelines

A statistics group is deleted when its hold time expires.

Examples

# Set the hold time to 3 minutes for statistics groups of the ICMP echo operation.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp -echo [Sysname-nqa-admin-test-icmp-echo] statistics hold-time 3

statistics interval

Use statistics interval to set the statistics collection interval for an NQA operation. Use undo statistics interval to restore the default.

Syntax

statistics interval interval undo statistics interval

Default

The statistics collection interval is 60 minutes.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view ICMP/UDP echo operation view ICMP/path/UDP jitter operation view

Predefined user roles

network-admin

Parameters

interval: Specifies the interv al in minutes , in the range of 1 to 35791394.

Page 81

Usage guidelines

NQA forms statistics within the same collec tion inter val as a statistic s group . To display information about the statistics groups, use the display nqa statistics command.

Examples

# Configure NQA to collect the ICMP echo operation statistics every 2 minutes.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp -echo [Sysname-nqa-admin-test-icmp-echo] statistics interval 2

statistics max-group

Use statistics max-group to set the maximum number of statistics groups that can be saved. Use undo statistics max-group to restore the default.

Syntax

statistics max-group number undo statistics max-group

Default

A maximum of two statistics groups can be saved.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view ICMP/UDP echo operation view ICMP/path/UDP jitter operation view

Predefined user roles

network-admin

Parameters

number: Specifies th e maximum number of statistics groups, in the range of 0 to 100. To disable statistics collection, set the value to 0.

Usage guidelines

When the maximum number of statistics groups is reached and a new statistics group is to be saved, the earliest statistics group is deleted.

Examples

# Configure NQA to save a maximum of five statistics groups for the ICMP echo operation.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp -echo [Sysname-nqa-admin-test-icmp-echo] statistics max-group 5

target-only

Use target-only to perform the path jitter operation only on the destination address. Use undo target-only to restore the default.

Page 82

Syntax

target-only undo target-only

Default

NQA performs the path jitter operation to the destination hop by hop.

Views

Path jitter operation view

Predefined user roles

network-admin

Examples

# Perform the path jitter operation only on the destination address.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type path-jitter [Sysname-nqa-admin-test-path-jitter] target-only

tos

Use tos to set the ToS value in the IP header for probe packets. Use undo tos to restore the default.

Syntax

tos value undo tos

Default

The T oS value in the IP header of probe packets is 0.

Views

Any operation view

Predefined user roles

network-admin

Parameters

value: Specifies the ToS value in the range of 0 to 255.

Examples

# In ICMP echo operation view, set the ToS value to 1 in the IP header for probe packets.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] tos 1

ttl

Use ttl to set the maximum number of hops that the probe packets can traverse. Use undo ttl to restore the default.

Page 83

Syntax

ttl value undo ttl

Default

The m aximum num ber of hops is 30 for probe packets of the UD P tracert operation, and is 20 for probe packets of other types of operations.

Views

DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view ICMP/UDP echo operation view ICMP/UDP jitter operation view UDP tracert operation view

Predefined user roles

network-admin

Parameters

value: Specifies the maximum number of hops that the probe packets can traverse, in the range of 1 to 255.

Usage guidelines

The route-option bypass-route command sets the TTL to 1 for probe packets. If you configure both the route-option bypass-route and ttl commands for an operation, the ttl command does not take effect.

For a successful UDP tracert operation, make sure the maximum number of hops is not smaller than the value set in the init-ttl command.

Examples

# Set the maximum number of hops to 16 for probe packets in 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-echo] ttl 16

type

Use type to specify an NQA operation type and enter its view.

Syntax

type { dhcp | dlsw | dns | ftp | http | icmp-echo | icmp-jitter | path-jitter | snmp | tcp | udp-echo | udp-jitter | udp-tracert | voice }

Default

No operation t ype is specified.

Views

NQA operation view

Predefined user roles

network-admin

Page 84

Parameters

dhcp: Specifies the DHCP operation type. dlsw: Specifies the DLSw operation type. dns: Specifies the DNS operation type. ftp: Specifies the FTP operation type. http: Specifies the HTTP operation type. icmp-echo: Specifies the ICMP echo operation type. icmp-jitter: Specifies the ICMP jitter operation type. path-jitter: Specifies the path jitter operation type. snmp: Specifies the SNMP operation type. tcp: Specifies the TCP operation type. udp-echo: Specifies the UDP echo operation type. udp-jitter: Specifies the UDP jitter operation type. udp-tracert: Specifies the UDP tracert operation type. voice: Specifies the voice operation type.

Examples

# Specify FTP as the NQA operation type and enter FTP operation view.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type ftp [Sysname-nqa-admin-test-ftp]

url

Use url to specify the URL of the destination. Use undo url to restore the default.

Syntax

url url undo url

Default

The destination URL is not specified.

Views

FTP operation view HTTP operation view

Predefined user roles

network-admin

Parameters

url: Specifies the UR L of the destinatio n server, a case-s ensitive str ing of 1 to 255 charac ters. The following table describes the URL format and parameters for different operations.

Page 85

Operation

URL format

Parameter description

aabbcc.com for example. Each

description about the filename parameter, see

HTTP operation

FTP operation

Examples

# Configure the URL that the HTTP operation visits as http://www.company.com/index.htm.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type http [Sysname-nqa-admin-test-http] url http://www.company.com/index.h tml

username

Use username to specify a username.

http://host/resource http://host:port/resource

ftp://host/filename ftp://host:port/filename

The host parameter represents the host name of the destination server. The host name is a dot-separated case-sensitive string including letters, digits, hyphens (-), and underscores (_). Host names are composed of series of labels, label consists of 1 to 63 characters. Con secutive dot s (.) and question marks are not allowed.

For Fundamentals Configuration Guide.

Use undo username to restore the default.

Syntax

username username undo username

Default

No username is configured.

Views

FTP operation view HTTP operation view

Predefined user roles

network-admin

Parameters

username: Specifies the username, a case-sensitive string of 1 to 32 characters.

Examples

# Set the FTP login username to administrator.

<Sysname> sy stem-view [Sysname] nq a entry admin test [Sysname-nqa-admin-test] type ftp [Sysname-nqa-admin-test-ftp] user name administrator

Related commands

operation password

Page 86

version

Use version to specify the version used in the HTTP operation. Use undo version to restore the default.

Syntax

version { v1.0 | v1.1 } undo version

Default

Version 1.0 is used in the HTTP operation.

Views

HTTP operation view

Predefined user roles

network-admin

Parameters

v1.0: Uses version 1.0. v1.1: Uses version 1.1.

Examples

# Configure the HTTP operation to use HTTP version 1.1.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type http [Sysname-nqa-admin-test-http] version v1.1

vpn-instance

Use vpn-instance to apply the operation to a VPN instance. Use undo vpn-instance to restore the default.

Syntax

vpn-instance vpn-instance-name undo vpn-instance

Default

The operation applies to the public network.

Views

DHCP/DLSw/DNS/FTP/HTTP/SNMP/TCP/voice operation view ICMP/UDP echo operation vie w ICMP/path/UDP jitter operation view UDP tracert operation vie w

Predefined user roles

network-admin

Page 87

Parameters

vpn-instance-name: Specifies a VPN instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

After you specify the VPN, the NQA operation tests the connectivity in the specified VPN instance.

Examples

# Apply the ICMP echo operation to vpn1.

<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] vpn-instance vpn1

NQA server commands

display nqa serv er

Use display nqa server status to display NQA server status.

Syntax

display nqa server

Views

Any view

Predefined user roles

network-admin network-operator

Examples

# Display NQA server status.

<Sysname> disp lay nqa server NQA server status: Enabled TCP connect: IP Address Port ToS Vpn-instance

2.2.2.2 2000 200 UDP echo: IP Address Port ToS Vpn-instance

3.3.3.3 3000 255 vpn1

Table 12 Command output

Field Description

NQA server status Whether the NQA serv er is enabled. TCP connect Information about the TCP listening service on the NQA server. UDP echo Information about the UDP listening service on the NQA server. IP Address IP address specified for the TCP/UDP listening service on the NQA server. Port Port number specified for the TCP/UD P listening serv ice on the NQ A server.

Page 88

Field

Description

ToS ToS value in reply packets sent by the NQA server.

Vpn-instance

Related commands

nqa server enable nqa server tcp-connect nqa server udp-echo

nqa server enable

Use nqa server enable to enable the NQA server. Use undo nqa server enable to dis ab le the NQ A server.

Syntax

nqa server enable

Name of the VPN instance to which the IP address that the NQA server listens on belongs. This field displays a hyphen (-) if the NQA server listens on a public IP address.

undo nqa server enable

Default

The NQA server is disabled.

Views

System view

Predefined user roles

network-admin

Examples

# Enable the NQA server.

<Sysname> system-view [Sysname] nqa serve r enable

Related commands

display nqa server nqa server tcp-connect nqa server udp-echo

nqa server tcp-connect

Use nqa server tcp-connect to configure a TCP listening service to enable the NQA server to listen to a port on the specified IP address.

Use undo nqa server tcp-connect to remove a TCP listening service.

Syntax

nqa server tcp-connect ip-address port-number [ vpn-instance vpn-instance-name ] [ tos tos ] undo nqa server tcp-connect ip-address port-number

Page 89

•

Default

No TCP listening services exist.

Views

System view

Predefined user roles

network-admin

Parameters

ip-address: Specifies the IP address for the TCP listening service. port-number: Specifies the port number for the TCP listening service, in the range of 1 to 65535.

vpn-instance vpn-instance-name: Specifies a VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the NQA server listens on the public IP address.

tos tos: Specifies the ToS value in the IP header for reply packets. The value range is 0 to 255, and the default value is 0.

Usage guidelines

Use this command on the NQA server only for the TCP operation. When you configure the IP address and port number for a TCP listening service on the NQA server,

follow these restrictions and guidelines:

The IP address and port number must be unique on the NQA server and match the

configuration on the NQA client.

The IP address must be the address of an interface on the NQA server. To ensure successful NQA operations and avoid affecting existing services, do not configure

the TCP listening service on well-known ports from 1 to 1023.

Examples

# Configure a TCP listening service to enable t he NQA server to listen to port 9000 on the IP address

169.254.10.2.

<Sysname> sy stem-view [Sysname] nq a server tcp-connect 169.254.10.2 9000

Related commands

display nqa server nqa server enable

nqa server udp-echo

Use nqa server udp-echo to configure a UDP listening service to enable the NQA server to listen to a port on the specified IP address.

Use undo nqa server udp-echo to remove the UDP listening service created.

Syntax

nqa server udp-echo ip-address port-number [ vpn-instance vpn-instance-name ] [ tos tos ] undo nqa server udp-echo ip-address port-number

Default

No UDP listening services exist.

Page 90

•

Views

System view

Predefined user roles

network-admin

Parameters

ip-address: Specifies the IP address for the UDP listening service. port-number: Specifies the port number for the UDP listening service, in the range of 1 to 65535.

vpn-instance vpn-instance-name: Specifies a VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the NQA server listens on a public IP address.

tos tos: Specifies the T oS value in the IP header for reply packets. The value range for this argument is 0 to 255, and the default value is 0.

Usage guidelines

Use this command on the NQA server only for the UDP jitter, UDP echo, and voice operations. When you configure the IP address and port number for a UDP listening service on the NQA server,

follow these restrictions and guidelines:

The IP address and port number must be unique on the NQA server and match the

configuration on the NQA client.

The IP address must be the address of an interface on the NQA server. To ensure successful NQA operations and avoid affecting existing services, do not configure

the UDP listening service on well-known ports from 1 to 1023.

Examples

# Configure a UDP listening service to enable the NQA server to listen to port 9000 on the IP address

169.254.10.2.

<Sysname> sy stem-view [Sysname] nq a server udp-echo 169.254.10.2 90 00

Related commands

display nqa server nqa server enable

Page 91

•

Field

Description

the current reference

NTP commands

NTP is supported on the following Layer 3 interfaces:

Layer 3 Ethernet interfaces . Layer 3 Ethernet subinterfaces. Layer 3 aggregate interfaces. VLAN interfaces. Tunnel interfaces.

display ntp-service ipv6 sessi ons

Use display ntp-service ipv6 sessions to display information about all IPv6 NTP associations.

Syntax

display ntp-service ipv6 sessions [ verbose ]

Views

Any view

Predefined user roles

network-admin network-operator

Parameters

verbose: Displays detai led information about all IPv6 NTP associations. If you do not s pecify this

keyword, the command displays only brief information about the IPv6 NTP associations.

Examples

# Display brief information about all IPv6 NTP associations.

<Sysname>display ntp-service ipv6 sessions Notes: 1 source(m aster), 2 source(peer), 3 selected, 4 candidate, 5 configured.

Source: [125]300 0::32 Reference: 127.127.1.0 Clock stratum: 2 Reachabiliti es: 1 Poll interval: 64 Last receive time: 6 Offset: -0.0 Roundtrip delay: 0.0 Dispersion: 0.0

Total sessions : 1

Table 13 Command output

[12345]

• 1—Clock source selected by the system ( source).

• 2—The stratum level of the clock source is less than or equal to 15.

• 3—The clock source has survived the clock selection algorithm.

• 4—The clock source is a candidate clock source.

• 5—The clock source was created by a command.

Page 92

Field

Description

field is 0 or 1, this field

f the reference clock i s t he cl ock of an other d evice on t he netw ork, thi s

stratum 16 clock is not synchronized and cannot be used as a

Length of time from when the last NTP message was received or when the

displayed in

Source

Reference

Clock stratum

Reachabilities

Poll interval

IPv6 address of the NTP server. If this field displays::, the IPv6 address of the NTP server has not been resolved successfully.

Reference clock ID of the NTP server:

• If the refe re nc e c lo ck is th e loca l cl oc k , t he v al ue of thi s f ie l d is rel a ted to the value of the Clock stratum field:

 When the value of the Clock stratum

displays LOCL.

 When the Clock stratum field has ano ther value , t his fi eld di splay s

the MD5 digest value of the first 32 bits of the IPv6 address. The MD5 digest value is in dotted decimal format.

• I field displays the MD5 digest value of the first 32 bits of the IPv6 address. The MD5 digest value is in dotted decimal format. If this field displays INIT, the local device has not establish ed a connec tion with the NTP server.

Stratum level of the NTP server, which determines the clock accuracy. The value is in the range of 1 to 16. A lower str atum lev el repre sents h igher clo ck accuracy. A reference clock.

Reachability count of the NTP server. 0 indicates that the NTP server is unreachable.

Polling interval in secon ds. It is the maximum interval between successive NTP messages.

local clock was last updated to the current time. Time is in seconds by default.

• If the time length is greater than 2048 seconds, it is minutes(m).

Last receive time

• If the time length is greater than 300 minutes, it is displayed in hours (h).

• If the time length is greater than 96 hours, it is displayed in days (d).

• If the time length is greater than 999 days, it is display ed in years (y).

If the time when the most recent NTP message was received or when the local clock was updated most recently is behind the current time, this fiel d

displays a hyphen (-). Offset Offset of the system clock relative to the reference clock, in milliseconds. Roundtrip delay Roundtrip delay from the local device to the clock source, in milliseconds. Dispersion Maximum error of the system clock relative to the reference source. Total sessions Total number of associations.

# Display detailed information about all IPv6 NTP associations.

<Sysname>display ntp-service ipv6 sessions verbose

Clock source: 1: :1 Session ID: 3614 4 Clock stratum: 16 Clock status: con figured, insane, valid, unsynced Reference cloc k ID: INIT VPN instance: No t specified Local mode: sym_active, local poll interval: 6

Page 93

Field

Description

The clock source is the candidate reference

be used as the

The clock source is valid, which means the clock

Peer mode: unspec, peer poll inte rval: 10 Offset: 0.0000 ms, roundtrip dela y: 0.0000ms, dispersion: 15937ms Root roundtrip delay: 0.0000m s, root dispersion: 0.0000ms Reachabiliti es:0, sync distanc e: 15.938 Precision: 2^10, version: 4, source interface: Not specified Reftime: 00000000.0000000 0 Thu, Feb 7 2036 6:28:16.0 00 Orgtime: d17cbb21.0f31810 6 Tue, May 17 2011 9:15:13 .059 Rcvtime: 00000000.0000000 0 Thu, Feb 7 2036 6:28:16.0 00 Xmttime: 00000000.0000000 0 Thu, Feb 7 2036 6:28:16.000 Roundtrip delay samples: 0.00 0 0.000 0.000 0.000 0. 000 0.000 0.000 0.000 Offset samples : 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 Filter order: 0 1 2 3 4 5 6 7

Total sessions : 1

Table 14 Command output

Clock source

Clock stratum

Clock status

IPv6 address of the clock source. If this field displays::, the IPv6 address of the NTP server has not been resolved successfully.

Stratum level of the NTP server, which determines the clock precision. The value is in the range of 1 to 16. A lower stratum level represents higher clock accuracy. A stratum 16 clock is not synchronized and cannot be used as a reference clock.

Status of the clock source corresponding to this association:

• configured—The association was created at the CLI.

• dynamic—The association is established dynamically.

• master—The clock source is the primary time server of the

current system.

• selected—The clock sour ce has surviv ed the cloc k selection algorithm.

• candidate— source.

• sane—The clock source has passed authentication and will be used as the reference source.

• insane—The clock sour ce h as not pas sed au thentic ation, or it has passed authentication but will not reference source.

• valid— source meets the following requirements:

 It has been authenticated and synchronized.  Its stratum level is valid.  Its root delay and root dispersion values are within their

ranges.

• invalid—The clock source is invalid.

• unsynced—The clock source has not been synchronized or

the value of the stratum level is invalid.

Page 94

Field

Description

value is in dotted

If the reference clock is the clock of another device on the

. The MD5 digest value is in

, in seconds. The value

displayed is a pow er of 2 . F or ex ample, if t he di splay ed val ue is 6,

, in seconds. The value

displayed is a pow er of 2 . F or ex ample, if t he di splay ed val ue is 6,

Roundtrip delay from the local device to the clock source, in

Reachability count of the clock source. 0 indicates that the clock

• If the reference clock is the local clock, the value of this field is related to the value of the Clock stratum field:

 When the value of the Clock stratum field is 0 or 1, this

field displays LOCL.

 When the Clock stratum field has another value, this

field displays the MD5 digest value of the first 32 bits of

Reference clock ID

the IPv6 address. The MD5 digest decimal format.

• network, this field displays the MD5 digest value of the first 32 bits of the IPv6 address dotted decimal format. If this field displays INIT, the local device has not establis hed a conne ction with the NTP serv er .

VPN instance

Local mode

local poll interval

peer mode

peer poll interval

VPN instance of the NTP server. If the NTP server is in a public network, this field displays

Not specified

Operation mode of the local device:

• unspec—The mode is unspecified.

• sym_active—Active mode.

• sym_passive—Passive mode.

• client—Client mode.

• server—Server mode.

• broadcast—Broadcast or multicast server mode.

• bclient—Broadcast or multicast client mode.

Polling interval for the local device the poll interval of the local device is 26, or 64 seconds.

Operation mode of the peer device:

• unspec—The mode is unsp ec ified.

• sym_active—Active mode.

• sym_passive—Passive mode.

• client—Client mode.

• server—Server mode.

• broadcast—Broadcast or multicast server mode.

• bclient—Broadcast or multicast client mode.

Polling interval for the peer device the polling interval of the local device is 26, or 64 seconds.

Offset

roundtrip delay

dispersion Maximum error of the sy stem cloc k relative t o the ref erence clock.

Root roundtrip delay

root dispersion

Reachabilities

Offset of the system clock relative to the reference clock, in milliseconds.

milliseconds.

Roundtrip delay from the local device to the primary time server, in milliseconds.

Maximum error of the system clock relative to the primary reference clock, in milliseconds.

source is unreachable.

Page 95

Field

Description

, in

and roundtrip delay

. Otherwise, the field is displayed as

Synchronization distance relative to the upper-level clock

sync distance

Precision Accuracy of the system clock. version NTP version in the range of 1 to 4.

source interface

Reftime Reference timestamp in the NTP message. Orgtime Originate timestamp in the NTP message. Rcvtime Receive timestamp in the NTP message. Xmttime Transmit timestamp in the NTP message. Filter order Dispersion information.

Reference clock status

seconds, and calculated from dispersion values.

Source interface. If the source interface is not specified, this field displays

specified

Status of the local clock. The fi eld is dis played o nly w hen you use the as a reference clock.

When the reach field of the local clock is 255, the field is di splayed as

working abnormally

ntp-service refclock-master

working normally

command to set the local cloc k

Not

Total sessions Total number of associations.

display ntp-service sessions

Use display ntp-service sessions to display information about all IPv4 NTP associations.

Syntax

display ntp-service sessions [verbose]

Views

Any view

Predefined user roles

network-admin network-operator

Parameters

verbose: Displays detai led information about al l IPv4 NTP associations. If you do not spec ify this

keyword, the command displays only brief information about the NTP associations.

Usage guidelines

When a device is op erating in NTP broadcast or multicast serv er mode, the display ntp-service sessions command does not displa y the IPv4 NTP association inform ation corresponding to the

broadcast or multicast server. However, the associations are counted in the total number of associations.

Examples

# Display brief information about all IPv4 NTP associations.

<Sysname>display ntp-service sessions

Page 96

Field

Description

local clock is

represents the NTP process

, the local device has not

Reachability count of the clock source. 0 indicates that the clock source is

Length of time from when the last NTP message was received or when the

onds, it is displayed in

source reference stra reach poll now offset delay disper ******************************************************************************** [12345]LOCAL(0) LOCL 0 1 64 - 0.0000 0.0000 7937.9 [5]0.0.0.0 INIT 16 0 64 - 0.0000 0.0000 0.0000 Notes: 1 source(m aster), 2 source(peer), 3 selected, 4 candidate, 5 configured. Total sessions : 1

Table 15 Command output

• When th e reference cl ock is the local clock, the field displays LOCAL (number). It indicates that the IP address of the

127.127.1.number, where number

source

reference

number in the range of 0 to 3.

• When the reference clock is the clock of another device, the field displays the IP address of the NTP server. If this field displays 0.0.0.0, the IP address of the NTP server has not been resolved successfully.

Reference clock ID of the NTP server:

• If the reference clock is the local clock, the value of this field is rel a ted to the value of the stra field:

 When the value of the stra field is 0 or 1, this field displays LOCL.  When the stra field has another value, this field displays the IP

address of the local clock.

• If the reference clock is the clock of another device on the netw ork, thi s field displays the IP address of the device. If the device supports IPv6, this field displays the M D 5 digest o f the first 32 bits o f the IPv6 addr es s of the device. If this field displays INIT established a connection with the NTP server.

Stratum level of the clock sou rce, which de termines the clock accuracy. The

stra

value is in the range of 1 to 16. The clock accuracy decreases from stratum 1 to stratum 16. A stratum 1 clock has the highest precision, and a stratum 16 clock is not synchronized and cannot be used as a reference clock.

reach

poll

unreachable. Polling interval in secon ds. It is the maximum interval between successive

NTP messages.

local clock was last updated to the current time. Time is in seconds by default.

• If the time length is greater than 2048 sec minutes (m).

now

• If the time length is greater than 300 minutes, it is displayed in hours (h).

• If the time length is greater than 96 hours, it is displayed in days (d).

• If the time length is greater than 999 days, it is display ed in years (y).

If the time when the most recent NTP message was received or when the local clock was updated most recently is behind the current time, this fiel d

displays a hyphen (-). offset Offset of the system clock relative to the reference clock, in milliseconds. delay Roundtrip delay from the local device to the NTP server, in milliseconds.

disper

Maximum error of the system clock relative to the reference source, in

milliseconds.

Page 97

Field

Description

Field

Description

• 1—Clock source selected by the syste m(the current r eference source).

• 2—The stratum level of the clock source is less than or equal to 15.

[12345]

• 3—The clock source has survived the clock selection algorithm.

• 4—The clock source is a cand idate clock source.

• 5—The clock source was created by a configuration command.

Total sessions Total number of associations.

# Display detailed information about all IPv4 NTP associations.

<Sysname>display ntp-service sessions verbose Clock source: 19 2.168.1.40 Session ID: 3588 8 Clock stratum: 2 Clock status: configured, mast er, sane, valid Reference cloc k ID: 127.127.1.0 VPN instance: No t specified Local mode: clie nt, local poll inter val: 6 Peer mode: server, peer poll inte rval: 6 Offset: 0.2862ms, roundtrip delay: 3.2653ms, dispersion: 4.5166ms Root roundtrip delay: 0.0000m s, root dispersion: 10.910ms Reachabilities:31, sync dis tance: 0.0194 Precision: 2^18, version: 3, so urce interface: No t specified Reftime: d17cbba5.1473de1 e Tue, May 17 2011 9:17:25 .079 Orgtime: 00000000.0000000 0 Thu, Feb 7 2036 6:28:16.000 Rcvtime: d17cbbc0.b1959a3 0 Tue, May 17 2011 9:17:52 .693 Xmttime: d17cbbc0.b1959a3 0 Tue, May 17 2011 9:17:52 .693 Roundtrip delay samples: 0.00 7 0.010 0.006 0.011 0. 010 0.005 0.007 0.003 Offset samples: 5629.55 3913. 76 5247.27 6526.92 31.99 148.72 38.2 7 0.29 Filter order: 7 5 2 6 0 4 1 3

Total sessions : 1

Table 16 Command output

Clock source

Clock stratum

IP address of the NTP server. If this field displays

0.0.0.0

, the IP

address of the NTP server has not been resolved successfully. Stratum level of the NTP server, which determines the clock

accuracy. The value is in the range of 1 to 16. A lower stratum level represents greater c lo ck acc uracy . A stratum 1 6 cl oc k i s not synchronized and cannot be used as a reference clock.

Page 98

Field

Description

e association was created by a

The clock source is the candidate reference

has passed authentication but will not be used as the

The clock source is valid, which means the clock

Its root delay and root dispersion values are within their

If the reference clock is the clock of another device on the device supports IPv6, this field displays the MD5 digest of

the first 32 bits of the IPv6 address of the device. If this field

, the local device has not established a

, in seconds. The value

Status of the clock source corresponding to this association:

• configured—Th configuration command.

• dynamic—The association is established dynamically.

• master—The clock source is the primary time server of the

current system.

• selected—The clock sour ce has surviv ed the cloc k selection algorithm.

• candidate— source.

• sane—The clock source has passed authentication and will

Clock status

be used as the reference source.

• insane—The clock sour ce h as not pas sed au thentic ation, or reference source.

• valid— source meets the following requirements:

 It has been authenticated and synchronized.  Its stratum level is valid.



ranges.

• invalid—The clock source is invalid.

• unsynced—The clock source has not been sy nchroniz ed or

the value of the stratum level is invalid.

Reference clock ID

VPN instance

Local mode

local poll interval

Reference clock ID of the NTP server:

• If the reference clock is the local clock, the value of this field is related to the value of the Clock stratum field:

 When the value of the Clock stratum field is 0 or 1, this

field displays LOCL.

 When the Clock stratum field has another value, this

field displays the IP address of the local c lock.

• network, this field display s the IP address of the device. If the

displays INIT connection with the NTP server.

VPN instance to which the NTP server belongs. If the NTP server is in a public network, the field displays

Not specified

Operation mode of the local device:

• unspec—The mode is unspecified.

• active—Active mode.

• passive—Passive mode.

• client—Client mode.

• server—Server mode.

• broadcast—Broadcast or multicast server mode.

• bclient—Broadcast or multicast client mode.

Polling interval of the local device displayed is a pow er of 2 . F or ex ample, if t he di splay ed val ue is 6, the poll interval of the local device is 26, or 64 seconds.

Page 99

Field

Description

, in seconds. The value

displayed is a pow er of 2 . F or ex ample, if t he di splay ed val ue is 6,

Offset of the system clock relative to the reference clock, in

, in

and roundtrip delay

. Otherwise, the field is displayed as

Operation mode of the peer device:

• unspec—The mode is unspecified.

• active—Active mode.

Peer mode

peer poll interval

• passive—Passive mode.

• client—Client mode.

• server—Server mode.

• broadcast—Broadcast or mu lticast server mode.

• bclient—Broadcast or multicast client mode.

Polling interval of the peer device the poll interval of the local device is 26, or 64 seconds.

Offset

Roundtrip delay

dispersion Maximum error of the sy stem cloc k relative t o the ref erence clock.

Root roundtrip delay

root dispersion

Reachabilities

sync distance

Precision Accuracy of the system clock. version NTP version in the range of 1 to 4.

source interface

Reftime Reference timestamp in the NTP message. Orgtime Originate timestamp in the NTP message.

milliseconds. Roundtrip delay from the local device to the NTP server, in

milliseconds.

Roundtrip delay from the local device to the primary timer serv er , in milliseconds.

Maximum error of the system clock relative to the primary reference clock, in milliseconds.

Reachability count of the clock source. 0 indicates that the clock source is unreachable.

Synchronization distance relative to the upper-level clock seconds, and calculated from dispersion values.

Source interface. If the source interface is not specified, this field is

Not specified

Rcvtime Receive timestamp in the NTP message. Xmttime Transmit timestamp in the NTP message. Filter order Sample information order.

Reference clock status

Total sessions Total number of associations.

display ntp-service status

Use display ntp-service status to display NTP service status.

Status of the local clock. The fi eld is dis played o nly w hen you use

ntp-service refclock-master

the as a reference clock.

When the reach field of the loc al clock is 255, the field is di splayed

working normally

working abnormally

command to set the local cloc k

Page 100

The system clock has been

The system clock has not been

Syntax

display ntp-service status

Views

Any view

Predefined user roles

network-admin network-operator

Examples

# Display NTP service status after time synchronization.

<Sysname>display ntp-service status Clock status: sy nchronized Clock stratum: 2 System peer: LOCAL(0) Local mode: client Reference cloc k ID: 127.127.1.0 Leap indicator : 00 Clock jitter: 0. 000977 s Stability: 0.000 pps Clock precision: 2^-10 Root delay: 0.00000 ms Root dispersion: 3.96367 ms Reference time : d0c5fc32.92c70 b1e Wed, Dec 29 2010 18:28:02.573

# Display the NTP service status when time is not synchronized.

<Sysname>display ntp-service status Clock status : unsynchronized Clock stratum: 16 Reference cloc k ID: none Clock jitter: 0. 000000 s Stability: 0.000 pps Clock precision: 2^-10 Root delay: 0.00 000 ms Root dispersion: 0.00002 ms Reference time : d0c5fc32.92c70 b1e Wed, Dec 29 2010 18:28:02.573

Table 17 Command output

Field Description

Status of the system clock:

• synchronized—

Clock status

Clock stratum Stratum level of the system clock. System peer IP address of the selected NTP server.

synchronized.

• unsynchronized— synchronized.

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

Contents

Ping, tracert, and system debugging commands

debugging

display debugging

ping

ping ipv6

tracert

tracert ipv6

NQA commands

NQA client commands

advantage-factor

codec-type

data-fill

data-size

description

destination ip

destination ipv6

destination por t

display nqa hist ory

display nqa reaction counters

display nqa result

display nqa statistics

filename

frequency

history-record enable

history-record keep-time

history-record number

init-ttl

lsr-path

max-failure

mode

next-hop ip

next-hop ipv6

no-fragment enabl e

nqa agent enable

nqa schedule

operation (FTP operation view)

operation (HTTP operation view)

out interface

password

probe count

probe packet-interval

probe packet-number

probe packet-timeout

probe timeout

raw-request

reaction checked-element { jitter-ds | jitter-sd }

reaction checked-element { owd-ds | owd-sd }

reaction checked-element icpif

reaction checked-element mos

reaction checked-element packet-loss

reaction checked-element probe-duration

reaction checked-element probe-fail (for trap)

reaction checked-element probe-fail (for trigger )

reaction checked-element rtt

reaction trap

rresolve-target

route-option bypass-route

source interface

source ip

source ipv6

source port

statistics hold-time

statistics interval

statistics max-group

target-only

type

username

version

vpn-instance

NQA server commands

display nqa serv er

nqa server enable

nqa server tcp-connect

nqa server udp-echo

NTP commands

display ntp-service ipv6 sessi ons

display ntp-service sessions

display ntp-service status