HP MSR1003-8S, MSR1002-4, MSR3012, MSR3024, MSR3044 Command Reference (V7)

...
HP MSR Router Series Network Management and Monitoring
Command Reference(V7)
Part number: 5998-7743b Software version: Document version: 6PW10
4-20150914
i
Legal and notice information
© Copyright 2015 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
ii

Contents

Ping, tracert, and system debugging commands ······································································································· 1
debugging ································································································································································· 1 display debugging ··················································································································································· 2 ping ············································································································································································ 2 ping ipv6 ··································································································································································· 5 tracert ········································································································································································· 8 tracert ipv6 ································································································································································ 9
NQA commands ························································································································································ 12
NQA client commands ·················································································································································· 12
advantage-factor ··················································································································································· 12 codec-type ······························································································································································ 12 community read ····················································································································································· 13 data-fill ···································································································································································· 14 data-size ································································································································································· 15 description (any NQA operation type view) ······································································································ 16 destination ip ························································································································································· 17 destination ipv6 ····················································································································································· 17 destination port ······················································································································································ 18 display nqa history ················································································································································ 18 display nqa reaction counters ······························································································································ 20 display nqa result ·················································································································································· 22 display nqa statistics ············································································································································· 28 filename ·································································································································································· 36 frequency ································································································································································ 36 history-record enable ············································································································································ 37 history-record keep-time ········································································································································ 38 history-record number ··········································································································································· 39 init-ttl ········································································································································································ 39 lsr-path ···································································································································································· 40 max-failure ······························································································································································ 41 mode ······································································································································································· 41 next-hop ·································································································································································· 42 next-hop ipv6 ························································································································································· 42 no-fragment enable ··············································································································································· 43 nqa ·········································································································································································· 44 nqa agent enable ·················································································································································· 44 nqa schedule ·························································································································································· 45 operation (FTP operation view) ···························································································································· 46 operation (HTTP operation view) ························································································································· 47 out interface ··························································································································································· 47 password ································································································································································ 48 probe count ···························································································································································· 49 probe packet-interval ············································································································································ 50 probe packet-number ············································································································································ 51 probe packet-timeout ············································································································································· 52 probe timeout ························································································································································· 52 raw-request ····························································································································································· 53 reaction checked-element { jitter-ds | jitter-sd } ·································································································· 54
i
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 resolve-target ·························································································································································· 65 route-option bypass-route ······································································································································ 66 source interface ····················································································································································· 67 source ip ································································································································································· 67 source ipv6····························································································································································· 68 source port ····························································································································································· 69 statistics hold-time ·················································································································································· 70 statistics interval ····················································································································································· 70 statistics max-group ··············································································································································· 71 target-only ······························································································································································· 72 tos ············································································································································································ 72 ttl ·············································································································································································· 73 type ········································································································································································· 74 url ············································································································································································ 75 username ································································································································································ 75 version ···································································································································································· 76 vpn-instance ··························································································································································· 77
NQA server commands ················································································································································· 77
display nqa server ················································································································································· 77 nqa server enable ················································································································································· 78 nqa server tcp-connect ·········································································································································· 79 nqa server udp-echo ············································································································································· 80
NTP commands ·························································································································································· 82
display ntp-service ipv6 sessions ························································································································· 82 display ntp-service sessions ·································································································································· 87 display ntp-service status ······································································································································ 91 display ntp-service trace ······································································································································· 93 ntp-service acl ························································································································································ 94 ntp-service authentication enable ························································································································ 96 ntp-service authentication-keyid ··························································································································· 96 ntp-service broadcast-client ·································································································································· 97 ntp-service broadcast-server ································································································································· 98 ntp-service dscp ····················································································································································· 99 ntp-service enable ·················································································································································· 99 ntp-service inbound enable ································································································································ 100 ntp-service ipv6 acl ············································································································································· 101 ntp-service ipv6 dscp ·········································································································································· 102 ntp-service ipv6 inbound enable························································································································ 102 ntp-service ipv6 multicast-client ·························································································································· 103 ntp-service ipv6 multicast-server ························································································································· 104 ntp-service ipv6 source ······································································································································· 105 ntp-service ipv6 unicast-peer ······························································································································ 106 ntp-service ipv6 unicast-server ···························································································································· 107 ntp-service max-dynamic-sessions ······················································································································ 108 ntp-service multicast-client ··································································································································· 109
ii
ntp-service multicast-server ·································································································································· 110 ntp-service refclock-master ·································································································································· 111 ntp-service reliable authentication-keyid ··········································································································· 112 ntp-service source ················································································································································ 112 ntp-service unicast-peer ······································································································································· 113 ntp-service unicast-server ···································································································································· 115
SNTP commands ····················································································································································· 117
display sntp ipv6 sessions ·································································································································· 117 display sntp sessions ··········································································································································· 118 sntp authentication enable ································································································································· 118 sntp authentication-keyid ···································································································································· 119 sntp enable ··························································································································································· 120 sntp ipv6 unicast-server ······································································································································· 120 sntp reliable authentication-keyid ······················································································································ 122 sntp unicast-server ··············································································································································· 122
PoE commands ························································································································································ 125
apply poe-profile ················································································································································· 125 apply poe-profile interface ································································································································· 126 display poe device ·············································································································································· 127 display poe interface ·········································································································································· 128 display poe interface power ······························································································································ 131 display poe power-usage ··································································································································· 132 display poe pse ··················································································································································· 135 display poe pse interface ··································································································································· 137 display poe pse interface power ······················································································································· 139 display poe-power ··············································································································································· 140 display poe-profile ··············································································································································· 144 display poe-profile interface ······························································································································· 145 poe disconnect ····················································································································································· 145 poe enable ··························································································································································· 146 poe enable pse ···················································································································································· 147 poe legacy enable ·············································································································································· 147 poe max-power ···················································································································································· 148 poe max-power (system view) ···························································································································· 149 poe pd-description ·············································································································································· 149 poe pd-policy priority ·········································································································································· 150 poe priority ·························································································································································· 151 poe priority (system view) ··································································································································· 152 poe pse-policy priority ········································································································································ 152 poe update ··························································································································································· 153 poe-profile ···························································································································································· 154 poe utilization-threshold ······································································································································ 155
SNMP commands ··················································································································································· 156
display snmp-agent community ·························································································································· 156 display snmp-agent context ································································································································ 158 display snmp-agent group ·································································································································· 158 display snmp-agent local-engineid ···················································································································· 159 display snmp-agent mib-node ···························································································································· 160 display snmp-agent mib-view ····························································································································· 166 display snmp-agent remote ································································································································ 168 display snmp-agent statistics ······························································································································ 169 display snmp-agent sys-info ································································································································ 171 display snmp-agent trap queue ·························································································································· 171
iii
display snmp-agent trap-list ································································································································ 172 display snmp-agent usm-user ······························································································································ 172 enable snmp trap updown ································································································································· 174 snmp-agent ··························································································································································· 175 snmp-agent calculate-password ························································································································· 176 snmp-agent community ······································································································································· 177 snmp-agent community-map ······························································································································· 180 snmp-agent context ·············································································································································· 181 snmp-agent group ················································································································································ 181 snmp-agent local-engineid ·································································································································· 184 snmp-agent log ···················································································································································· 185 snmp-agent mib-view ··········································································································································· 185 snmp-agent packet max-size ······························································································································ 187 snmp-agent port ··················································································································································· 187 snmp-agent remote ·············································································································································· 188 snmp-agent { inform | trap } source ·················································································································· 189 snmp-agent sys-info contact ································································································································ 190 snmp-agent sys-info location······························································································································· 190 snmp-agent sys-info version ································································································································ 191 snmp-agent target-host ········································································································································ 192 snmp-agent trap enable ······································································································································ 194 snmp-agent trap if-mib link extended ················································································································ 195 snmp-agent trap life ············································································································································· 196 snmp-agent trap log ············································································································································ 196 snmp-agent trap queue-size ································································································································ 197 snmp-agent usm-user { v1 | v2c } ······················································································································ 198 snmp-agent usm-user v3 ······································································································································ 200 snmp-agent usm-user v3 user-role ······················································································································ 204
RMON commands ·················································································································································· 206
display rmon alarm ············································································································································· 206 display rmon event ·············································································································································· 208 display rmon eventlog ········································································································································· 209 display rmon history ············································································································································ 211 display rmon prialarm ········································································································································ 213 display rmon statistics ········································································································································· 216 rmon alarm ··························································································································································· 218 rmon event ···························································································································································· 220 rmon history ························································································································································· 221 rmon prialarm ······················································································································································ 222 rmon statistics ······················································································································································· 224
Event MIB commands ·············································································································································· 226
action ···································································································································································· 226 comparison ·························································································································································· 227 context (action-set view) ······································································································································ 228 context (trigger view) ·········································································································································· 228 delta falling ·························································································································································· 229 delta rising ··························································································································································· 230 description (event view) ······································································································································ 231 description (trigger view) ···································································································································· 231 display snmp mib event ······································································································································ 232 display snmp mib event event ···························································································································· 233 display snmp mib event object list ····················································································································· 235 display snmp mib event summary ······················································································································ 236
iv
display snmp mib event trigger ·························································································································· 237 event enable ························································································································································· 240 event owner (trigger-Boolean view) ··················································································································· 241 event owner (trigger-existence view) ················································································································· 241 falling ···································································································································································· 242 frequency ······························································································································································ 243 object list owner (action-notification view) ········································································································ 244 object list owner (trigger-Boolean view) ············································································································ 244 object list owner (trigger-existence view) ·········································································································· 245 object list owner (trigger-threshold view) ·········································································································· 246 object list owner (trigger view) ·························································································································· 247 oid (action-notification view) ······························································································································ 248 oid (action-set view) ············································································································································ 248 oid (trigger view) ················································································································································· 249 rising ····································································································································································· 250 sample ·································································································································································· 251 snmp mib event owner ········································································································································ 251 snmp mib event object list ·································································································································· 252 snmp mib event sample instance maximum ····································································································· 253 snmp mib event sample minimum ······················································································································ 254 snmp mib event trigger ······································································································································· 255 snmp-agent trap enable event-mib ····················································································································· 255 startup (trigger-existence view) ··························································································································· 256 startup (trigger-threshold view) ··························································································································· 257 startup enable ······················································································································································ 258 test ········································································································································································· 258 trigger enable ······················································································································································ 259 type ······································································································································································· 260 value (action-set view) ········································································································································· 261 value (trigger-Boolean view) ······························································································································· 261 wildcard context (action-set view) ······················································································································ 262 wildcard context (trigger view) ·························································································································· 263 wildcard oid (action-set view) ···························································································································· 263 wildcard oid (trigger view) ································································································································· 264
NETCONF commands ············································································································································ 266
netconf soap http enable ···································································································································· 266 netconf soap https enable ·································································································································· 266 netconf ssh server enable ··································································································································· 267 netconf ssh server port ········································································································································ 268 xml········································································································································································· 268
CWMP commands ·················································································································································· 270
cwmp ···································································································································································· 270 cwmp acs default password ······························································································································· 270 cwmp acs default url ··········································································································································· 271 cwmp acs default username ······························································································································· 272 cwmp acs password ··········································································································································· 272 cwmp acs url ························································································································································ 273 cwmp acs username ············································································································································ 274 cwmp cpe connect interface ······························································································································ 275 cwmp cpe connect retry······································································································································ 276 cwmp cpe inform interval ··································································································································· 276 cwmp cpe inform interval enable ······················································································································ 277 cwmp cpe inform time ········································································································································ 278
v
cwmp cpe password ··········································································································································· 278 cwmp cpe provision-code ··································································································································· 279 cwmp cpe stun enable ········································································································································ 280 cwmp cpe username ··········································································································································· 281 cwmp cpe wait timeout ······································································································································· 281 cwmp enable ······················································································································································· 282 display cwmp configuration ······························································································································· 283 display cwmp status ············································································································································ 284 ssl client-policy ····················································································································································· 285
EAA commands ······················································································································································· 287
action cli ······························································································································································· 287 action reboot ························································································································································ 288 action switchover ················································································································································· 290 action syslog ························································································································································ 290 commit ·································································································································································· 291 display rtm environment······································································································································ 292 display rtm policy ················································································································································ 292 event cli ································································································································································ 294 event hotplug ······················································································································································· 295 event interface ····················································································································································· 296 event process ······················································································································································· 298 event snmp oid ···················································································································································· 300 event snmp-notification········································································································································ 301 event syslog ·························································································································································· 302 rtm cli-policy ························································································································································· 303 rtm environment ··················································································································································· 304 rtm scheduler suspend ········································································································································· 305 rtm tcl-policy ························································································································································· 306 running-time ·························································································································································· 307 user-role ································································································································································ 307
Process monitoring and maintenance commands ································································································ 309
display exception context ··································································································································· 309 display exception filepath ·································································································································· 314 display kernel deadloop ····································································································································· 315 display kernel deadloop configuration ············································································································· 319 display kernel exception ····································································································································· 320 display process ···················································································································································· 323 display process cpu ············································································································································ 326 display process log ············································································································································· 328 display process memory ····································································································································· 329 display process memory heap ··························································································································· 331 display process memory heap address ············································································································ 332 display process memory heap size ··················································································································· 334 exception filepath ················································································································································ 335 monitor kernel deadloop enable ······················································································································· 336 monitor kernel deadloop exclude-thread ·········································································································· 337 monitor kernel deadloop time ···························································································································· 338 monitor process ··················································································································································· 339 monitor thread ····················································································································································· 345 process core ························································································································································· 348 reset exception context ······································································································································· 349 reset kernel deadloop ········································································································································· 350 reset kernel exception ········································································································································· 351
vi
Sampler configuration commands ························································································································· 353
display sampler ··················································································································································· 353 sampler ································································································································································· 354
Port mirroring commands ······································································································································· 356
display mirroring-group ······································································································································ 356 mirroring-group ···················································································································································· 357 mirroring-group mirroring-port (interface view) ································································································ 357 mirroring-group mirroring-port (system view) ··································································································· 358 mirroring-group monitor-port (interface view) ··································································································· 359 mirroring-group monitor-port (system view) ······································································································ 360
Flow mirroring commands ······································································································································ 361
mirror-to ································································································································································ 361
NetStream configuration commands ····················································································································· 362
display ip netstream cache ································································································································· 362 display ip netstream export ································································································································ 368 display ip netstream template ···························································································································· 369 enable ··································································································································································· 372 ip netstream ·························································································································································· 373 ip netstream { inbound | outbound } filter ········································································································ 373 ip netstream { inbound | outbound } sampler ·································································································· 374 ip netstream aggregation ··································································································································· 375 ip netstream export host ····································································································································· 376 ip netstream export rate ······································································································································ 378 ip netstream export source ································································································································· 378 ip netstream export v9-template refresh-rate packet ························································································ 379 ip netstream export v9-template refresh-rate time ···························································································· 380 ip netstream export version ································································································································ 381 ip netstream max-entry ········································································································································ 382 ip netstream mpls ················································································································································· 382 ip netstream timeout active ································································································································· 383 ip netstream timeout inactive ······························································································································ 384 reset ip netstream statistics ································································································································· 384
IPv6 NetStream commands ···································································································································· 386
display ipv6 netstream cache ···························································································································· 386 display ipv6 netstream export ···························································································································· 391 display ipv6 netstream template ························································································································ 392 enable ··································································································································································· 396 ipv6 netstream ····················································································································································· 397 ipv6 netstream { inbound | outbound } filter ···································································································· 397 ipv6 netstream { inbound | outbound } sampler ····························································································· 398 ipv6 netstream aggregation ······························································································································· 399 ipv6 netstream export host ································································································································· 400 ipv6 netstream export rate ································································································································· 401 ipv6 netstream export source ····························································································································· 402 ipv6 netstream export v9-template refresh-rate packet ···················································································· 403 ipv6 netstream export v9-template refresh-rate time ························································································ 403 ipv6 netstream export version 9 ························································································································ 404 ipv6 netstream max-entry ···································································································································· 405 ipv6 netstream timeout active ···························································································································· 406 ipv6 netstream timeout inactive ························································································································· 406 reset ipv6 netstream statistics ····························································································································· 407
vii
sFlow commands ····················································································································································· 408
display sflow ························································································································································ 408 sflow agent ··························································································································································· 409 sflow collector ······················································································································································ 410 sflow counter interval ·········································································································································· 411 sflow counter collector ········································································································································ 411 sflow flow collector ·············································································································································· 412 sflow flow max-header ········································································································································ 413 sflow sampling-mode ·········································································································································· 413 sflow sampling-rate ············································································································································· 414 sflow source ························································································································································· 415
Information center commands ································································································································ 416
diagnostic-logfile save ········································································································································ 416 display diagnostic-logfile summary ··················································································································· 416 display info-center ··············································································································································· 417 display logbuffer ·················································································································································· 418 display logbuffer summary ································································································································· 420 display logfile summary ······································································································································ 422 display security-logfile summary ························································································································ 423 enable log updown ············································································································································· 423 info-center diagnostic-logfile enable ·················································································································· 424 info-center diagnostic-logfile frequency ············································································································· 425 info-center diagnostic-logfile quota ···················································································································· 425 info-center diagnostic-logfile directory ·············································································································· 426 info-center logfile overwrite-protection ·············································································································· 427 info-center enable ················································································································································ 427 info-center format ················································································································································· 428 info-center logbuffer ············································································································································ 428 info-center logbuffer size ···································································································································· 429 info-center logfile enable ···································································································································· 430 info-center logfile frequency ······························································································································· 430 info-center logfile size-quota ······························································································································· 431 info-center logfile directory ································································································································· 431 info-center logging suppress duplicates ············································································································ 432 info-center loghost ··············································································································································· 434 info-center loghost source ··································································································································· 435 info-center security-logfile alarm-threshold ········································································································ 435 info-center security-logfile enable ······················································································································· 436 info-center security-logfile frequency ················································································································· 437 info-center security-logfile size-quota ················································································································· 437 info-center security-logfile directory ··················································································································· 438 info-center source ················································································································································ 439 info-center synchronous ······································································································································ 440 info-center timestamp ·········································································································································· 441 info-center timestamp loghost ····························································································································· 442 info-center trace-logfile quota ····························································································································· 443 logfile save ··························································································································································· 443 reset logbuffer ······················································································································································ 444 security-logfile save ············································································································································· 444 terminal debugging ············································································································································· 445 terminal logging level ········································································································································· 446 terminal monitor ··················································································································································· 447
viii
Packet capture commands ······································································································································ 448
packet-capture interface ····································································································································· 448 packet-capture read ············································································································································ 450
Support and other resources ·································································································································· 452
Contacting HP ······························································································································································ 452
Subscription service ············································································································································ 452
Related information ······················································································································································ 452
Documents ···························································································································································· 452 Websites ······························································································································································· 452
Conventions ·································································································································································· 453
Index ········································································································································································ 455
ix

Ping, tracert, and system debugging commands

debugging

Use debugging to enable debugging for a module.
Use undo debugging to disable debugging for a module.
Syntax
debugging { all [ timeout time ] | module-name [ option ] }
undo debugging { all | module-name [ option ] }
Default
Debugging functions are disabled for all modules.
Views
User view
Predefined user roles
network-admin
Parameters
all: Enables all debugging functions.
timeout time: Specifies the timeout time for the debugging all command. When all debugging is enabled,
the system automatically executes the undo debugging all command after the timeout time. The time argument is in the range of 1 to 1440 minutes.
module-name: Specifies a module by its name, such as arp or device. To display the current module name, use the debugging ? command.
option: Specifies the debugging option for a module. The option number and content differ for different modules. To display the supported options, use the debugging module-name ? command.
Usage guidelines
Output of debugging commands is memory intensive. To guarantee system performance, enable debugging only for modules that are in an exceptional condition.
Examples
# Enable debugging for the device management module.
<Sysname> debugging dev
Related commands
display debugging
1

display debugging

Use display debugging to display the enabled debugging functions.
Syntax
display debugging [ module-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
module-name: Specifies a module by its name. To display the current module name, use the display debugging ? command.
Examples
# Display all enabled debugging functions.
<Sysname> display debugging DEV debugging switch is on
Related commands
debugging

ping

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

ping ipv6

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

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 } | -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.
-f first-ttl: Specifies the TTL of the first packet sent to the destination. The value range is 1 to 255, and the default is 1. It must be no greater than the value of the max-ttl argument.
-m max-ttl: Specifies the maximum number of hops allowed for a probe packet. The value range is 1 to 255, and the default is 30. It must be no smaller than the value of the first-ttl argument.
-p port: Specifies an invalid UDP port of the destination. The value range is 1 to 65535, and the default is 33434.
-q packet-number: Specifies the number of probe packets to send per hop. The value range is 1 to 65535, and the default is 3.
-t tos: Specifies the ToS value of probe packets. The value range is 0 to 255, and the default is 0.
-topology topo-name: Specifies the topology to which the destination belongs, where topo-name is a
case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination belongs, where the vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-w timeout: Specifies the timeout time in milliseconds of the reply packet for a probe packet. The value range is 1 to 65535, and the default is 5000.
host: Specifies the IP address or host name of the destination. The host name is a case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping command, use the tracert command to locate failed nodes.
The output of the tracert command includes IP addresses of all the Layer 3 devices that the packets traverse from source to destination. Asterisks (* * *) are displayed if the device cannot reply with an ICMP error message. The reason might be the destination is unreachable or sending ICMP timeout/destination unreachable packets is disabled.
To abort the tracert operation during the execution of the command, press Ctrl+C.
8
Examples
p
# Display the path that the packets traverse from source to destination (1.1.2.2).
<Sysname> tracert 1.1.2.2 traceroute to 1.1.2.2 (1.1.2.2), 30 hops at most, 40 bytes each packet, press CTRL_C to
break 1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms 2 1.1.2.2 (1.1.2.2) 580 ms 470 ms 80 ms
# Trace the path to destination (192.168.0.46) over an MPLS network.
<Sysname> tracert 192.168.0.46 traceroute to 192.168.0.46(192.168.0.46), 30 hops at most, 40 bytes each packet, press
CTRL_C to break 1 192.0.2.13 (192.0.2.13) 0.661 ms 0.618 ms 0.579 ms 2 192.0.2.9 (192.0.2.9) 0.861 ms 0.718 ms 0.679 ms MPLS Label=100048 Exp=0 TTL=1 S=1 3 192.0.2.5 (192.0.2.5) 0.822 ms 0.731 ms 0.708 ms MPLS Label=100016 Exp=0 TTL=1 S=1 4 192.0.2.1 (192.0.2.1) 0.961 ms 8.676 ms 0.875 ms
Table 3 Command output
Field Descri
traceroute to 1.1.2.2 (1.1.2.2)
hops at most
bytes each packet Number of bytes of a probe packet.
press CTRL_C to break
Display the route that the IP packets traverse from the current device to the device whose IP address is 1.1.2.2.
Maximum number of hops of the probe packets, which can be set by the -m keyword.
During the execution of the command, press Ctrl+C to abort the tracert operation.
Probe result of the probe packets whose TTL is 1, including the following:
tion
Domain name (or IP address, if the domain name is not configured) of the
1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms
first hop.
The round-trip time of the three probe packets.
The number of packets that can be sent in each probe can be set through the
-q keyword.
ICMP timeout packets on an MPLS network, carrying MPLS label information:
Label—Label value that is used to identify a forwarding equivalence class
(FEC).
MPLS Label=100048 Exp=0 TTL=1 S=1
Exp—Reserved, usually used for class of service (CoS).
TTL—TTL value.
S—MPLS supports multiple levels of labels. Value 1 indicates that the label
is at the bottom of the label stack, and value 0 indicates that the label is in another label stack.

tracert ipv6

Use tracert ipv6 to display the path that the IPv6 packets traverse from source to destination.
9
Syntax
tracert ipv6 [ -f first-hop | -m max-hops | -p port | -q packet-number | -t traffic-class | -vpn-instance vpn-instance-name | -w timeout ] * host
Views
Any view
Predefined user roles
network-admin
Parameters
-f first-hop: Specifies the TTL value of the first packet. The value range is 1 to 255, and the default is 1. The
value must be no greater than the value of the max-hops argument.
-m max-hops: Specifies the maximum number of hops allowed for a packet. The value range is 1 to 255, and the default is 30. The value must be no smaller than the value of the first-hop argument.
-p port: Specifies an invalid UDP port of the destination. The value range is 1 to 65535, and the default is 33434.
-q packet-number: Specifies the number of probe packets sent each time. The value range is 1 to 65535, and the default is 3.
-t traffic-class: Specifies the traffic class value in an IPv6 probe packet. The value range is 0 to 255, and the default is 0.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination belongs, where the vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.
-w timeout: Specifies the timeout time (in milliseconds) of the reply packet of a probe packet. The value range is 1 to 65535, and the default is 5000.
host: Specifies the IPv6 address or host name of the destination. The host name is a case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping ipv6 command, you can use the tracert ipv6 command to locate failed nodes.
The output of the tracert ipv6 command includes IPv6 addresses of all the Layer 3 devices that the packets traverse from source to destination. Asterisks (* * *) are displayed if the device cannot reply with an ICMP error message. The reason might be the destination is unreachable or sending ICMP timeout/destination unreachable packets is disabled.
To abort the tracert operation during the execution of the command, press Ctrl+C.
Examples
# Display the path that the packets traverse from source to destination (2001:3::2).
<Sysname> tracert ipv6 2001:3::2 traceroute to 2001:3::2(2001:3::2), 30 hops at most, 60 byte packets, press CTRL_C to break 1 2001:1::2 0.661 ms 0.618 ms 0.579 ms 2 2001:2::2 0.861 ms 0.718 ms 0.679 ms 3 2001:3::2 0.822 ms 0.731 ms 0.708 ms
10
Table 4 Command output
p
Field Descri
traceroute to 2001:3::2
hops at most
byte packets Number of bytes of a probe packet.
1 2001:1::2 0.661 ms 0.618 ms 0.579 ms
Display the route that the IPv6 packets traverse from the current device to the device whose IP address is 2001:3:2.
Maximum number of hops of the probe packets, which can be set by the
-m keyword.
Probe result of the probe packets whose hoplimit is 1, including the IPv6 address of the first hop, and the roundtrip time of three probe packets. The number of packets that can be sent in each probe can be set by the -q keyword.
tion
11

NQA commands

NQA client commands

advantage-factor

Use advantage-factor to set the advantage factor to be used for calculation of Mean Opinion Scores (MOS) and Calculated Planning Impairment Factor (ICPIF) values.
Use undo advantage-factor to restore the default.
Syntax
advantage-factor factor
undo advantage-factor
Default
The advantage factor is 0.
Views
Voice operation view
Predefined user roles
network-admin
Parameters
factor: Specifies the advantage factor in the range of 0 to 20.
Usage guidelines
The evaluation of voice quality depends on users' tolerance for voice quality. For users with higher tolerance for voice quality, use the advantage-factor command to set an advantage factor. When the system calculates the ICPIF value, it subtracts the advantage factor to modify ICPIF and MOS values for voice quality evaluation.
Examples
# Set the advantage factor to 10 for voice operations.
<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type voice [Sysname-nqa-admin-test-voice] advantage-factor 10

codec-type

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

community read

Use community read to specify the community name for SNMPv1 and SNMPv2c probe packets.
Use undo community read to restore the default.
Syntax
community read { cipher | simple } community-name
undo community read
Default
The SNMPv1 and SNMPv2c probe packets use the community name public.
Views
SNMP operation view
Predefined user roles
network-admin
Parameters
cipher: Sets a ciphertext community name.
simple: Sets a plaintext community name.
community-name: Specifies the community name. This argument is case sensitive. If you specify the
simple keyword, the name must be a string of 1 to 32 characters. If you specify the cipher keyword, the name must be a string of 33 to 73 characters.
13
Usage guidelines
Execute this command to specify the community name on the NQA client if the SNMP agent runs SNMPv1 or SNMPv2c. The specified community name must be the read-only community name that has been configured on the SNMP agent.
If the SNMP agent runs SNMPv3, you do not need to specify the community name on the NQA client.
For security purposes, the community name configured in plain text or cipher text is saved in cipher text.
Examples
# Specify readaccess as the community name for SNMPv1 and SNMPv2c probe packets.
<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type snmp [Sysname-nqa-admin-test-snmp] community read simple readaccess

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 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 length, only the first part of the string is filled. For example, if you configure the string as abcd and set the payload size to 3 bytes, abc is filled.
If the payload length is greater than the string length, the system fills the payload with the string cyclically until the payload is full. For example, if you configure the string as abcd and the payload size as 6 bytes, abcdab is filled.
How the string is filled depends on the operation type.
For the ICMP echo operation, the string fills the whole payload of an ICMP echo request.
For the UDP echo operation, the first five bytes of the payload of a UDP packet are for special
purpose. The string fills the remaining part of payload.
14
p
For the UDP jitter operation, the first 68 bytes of the payload of a UDP packet are for special
purpose. The string fills the remaining part of the payload.
For the voice operation, the first 16 bytes of the payload of a UDP packet are for special purpose.
The string fills the remaining part of the payload.
For the path jitter operation, the first four bytes of the payload of an ICMP echo request are for
special purpose. The string fills the remaining part of payload.
Examples
# Specify abcd as the payload fill string for ICMP echo requests.
<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] data-fill abcd

data-size

Use data-size to set the payload size for each probe packet.
Use undo data-size to restore the default.
Syntax
Default
Views
data-size size
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
O
eration type Codec type
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
Default size (bytes)
ICMP/UDP echo operation view
Path/UDP jitter operation view
UDP tracert operation view
Voice operation view
15
Predefined user roles
network-admin
Parameters
size: Specifies the payload size. Available value ranges include:
20 to 8100 bytes for the ICMP echo, UDP echo, or UDP tracert operation.
68 to 8100 bytes for the UDP jitter or path jitter operation.
16 to 1500 bytes for the voice operation.
Usage guidelines
In ICMP echo and path jitter operations, the command sets the payload size for each ICMP echo request.
In UDP echo, UDP jitter, UDP tracert, and voice operations, the command sets the payload size for each UDP packet.
Examples
# Set the payload size to 80 bytes for each ICMP echo request.
<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] data-size 80

description (any NQA operation type view)

Use description to configure a description for an NQA operation, such as the operation type or purpose.
Use undo description to remove the description.
Syntax
description text
undo description
Default
No description is configured for an NQA operation.
Views
Any NQA operation type view
Predefined user roles
network-admin
Parameters
text: Specifies a case-sensitive string of 1 to 200 characters.
Examples
# Configure the description as icmp-probe for an NQA operation.
<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] description icmp-probe
16

destination ip

Use destination ip to configure the destination IP address for the operation.
Use undo destination ip to remove the destination IP address.
Syntax
destination ip ip-address
undo destination ip
Default
No destination IP address is configured for the operation.
Views
DHCP/DLSw/DNS/SNMP/TCP/voice operation view
ICMP/UDP echo operation view
Path/UDP jitter operation view
UDP tracert operation view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the destination IP address for the operation.
Examples
# Specify 10.1.1.1 as the destination IP 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-echo] 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 remove the destination IPv6 address.
Syntax
destination ipv6 ipv6-address
undo destination ipv6
Default
No destination IPv6 address is configured for the operation.
Views
ICMP echo operation view
Predefined user roles
network-admin
17
Parameters
ipv6-address: Specifies the destination IPv6 address for the operation. IPv6 link-local addresses are not supported.
Examples
# Specify 1::1 as the destination IPv6 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-echo] destination ipv6 1::1

destination port

Use destination port to configure the destination port number for the operation.
Use undo destination port to remove the destination port number.
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 operation view
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 echo operation.
<Sysname> system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type udp-echo [Sysname-nqa-admin-test-udp-echo] destination port 9000

display nqa history

Use display nqa history to display the history records of NQA operations.
18
Syntax
display nqa history [ admin-name operation-tag ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argument represents the operation tag. 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 UDP jitter and voice operations. Use the display nqa result or display nqa statistics command to verify the UDP jitter and voice operations.
Examples
# Display the history records of the UDP tracert operation with the administrator name administrator and the operation tag tracert.
<Sysname> display nqa history administrator tracert NQA entry (admin 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 the administrator name administrator and the 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
19
Loading...
+ 433 hidden pages