Aruba R9Y12A Reference guide

Category
Software
Type
Reference guide

This manual is also suitable for

HPE Networking Comware 5960 Switch Series
Network Management and Monitoring
Command Reference
Software
version: Release 9126P01 and later
Document version: 6W100-20230428
© Copyright 2023 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
i
Contents
Ping and tracert commands ··········································································· 1
ping ···························································································································································· 1
ping ipv6 ····················································································································································· 4
tracert ························································································································································· 6
tracert ipv6 ················································································································································· 8
System debugging commands ····································································· 11
debugging ················································································································································ 11
display debugging ···································································································································· 11
NQA commands ·························································································· 13
NQA client commands ····································································································································· 13
advantage-factor ······································································································································ 13
agent-type ················································································································································ 13
codec-type ················································································································································ 14
community read ········································································································································ 15
cpu ··························································································································································· 16
data-fill ······················································································································································ 17
data-size ··················································································································································· 18
description ················································································································································ 19
destination host ········································································································································ 19
destination ip ············································································································································ 20
destination ipv6 ········································································································································ 21
destination port ········································································································································· 21
disconnect-mode ······································································································································ 22
disk ··························································································································································· 23
display nqa history ··································································································································· 24
display nqa reaction counters ·················································································································· 25
display nqa result ····································································································································· 27
display nqa statistics ································································································································ 34
expect { data | hex-data } ························································································································· 43
expect { failed-data | hex-failed-data } ······································································································ 45
expect failed-status ·································································································································· 47
expect status ············································································································································ 47
filename ···················································································································································· 48
frequency ················································································································································· 49
frequency-adjustment ······························································································································· 50
hex-data-fill ··············································································································································· 50
history-record enable ······························································································································· 51
history-record keep-time ·························································································································· 52
history-record number ······························································································································ 53
init-ttl ························································································································································· 53
key ···························································································································································· 54
lsr-path ····················································································································································· 55
mailbox ····················································································································································· 55
max-failure ··············································································································································· 56
memory ···················································································································································· 57
mode ························································································································································ 57
next-hop ip ··············································································································································· 58
next-hop ipv6 ············································································································································ 59
no-fragment enable ·································································································································· 59
nqa ··························································································································································· 60
nqa agent enable ····································································································································· 60
nqa schedule ············································································································································ 61
nqa template ············································································································································ 62
oid ···························································································································································· 63
operation (FTP operation view) ················································································································ 64
ii
operation (HTTP operation view) ············································································································· 65
out interface ············································································································································· 66
password ·················································································································································· 66
port-detect enable ···································································································································· 67
probe count ·············································································································································· 68
probe packet-interval ································································································································ 69
probe packet-number ······························································································································· 70
probe packet-timeout ······························································································································· 71
probe timeout ··········································································································································· 71
proxy-url ··················································································································································· 72
raw-request ·············································································································································· 73
reaction checked-element { jitter-ds | jitter-sd } ························································································ 74
reaction checked-element { owd-ds | owd-sd } ························································································ 75
reaction checked-element icpif················································································································· 76
reaction checked-element mos ················································································································ 77
reaction checked-element packet-loss ····································································································· 78
reaction checked-element probe-duration································································································ 79
reaction checked-element probe-fail (for trap) ························································································· 81
reaction checked-element rtt ···················································································································· 82
reaction trap ············································································································································· 83
reaction trigger per-probe ························································································································· 84
reaction trigger probe-fail ························································································································· 85
reaction trigger probe-pass ······················································································································ 86
request-method ········································································································································ 86
resource-release { data-fill | hex-data-fill } ································································································ 87
route-option bypass-route ························································································································ 88
source interface (ICMP echo/UDP tracert operation view) ······································································ 89
source ip ··················································································································································· 89
source ipv6 ··············································································································································· 90
source port ··············································································································································· 91
statistics hold-time ···································································································································· 92
statistics interval ······································································································································· 93
statistics max-group ································································································································· 93
target-only ················································································································································ 94
tos ···························································································································································· 95
ttl ······························································································································································ 95
type ·························································································································································· 96
url ····························································································································································· 97
username ················································································································································· 98
Version (HTTP operation view) ················································································································ 99
version (SNMP DCA template view) ········································································································ 99
vpn-instance ··········································································································································· 100
NQA server commands ·································································································································· 101
display nqa server ·································································································································· 101
nqa server enable ·································································································································· 102
nqa server tcp-connect ··························································································································· 102
nqa server udp-echo ······························································································································ 103
NTP commands ························································································· 106
display ntp-service ipv6 sessions ··········································································································· 106
display ntp-service sessions ·················································································································· 110
display ntp-service status ······················································································································· 114
display ntp-service trace ························································································································ 116
ntp-service acl ········································································································································ 117
ntp-service authentication enable ·········································································································· 118
ntp-service authentication-keyid ············································································································· 119
ntp-service broadcast-client ··················································································································· 121
ntp-service broadcast-server ·················································································································· 121
ntp-service dscp ····································································································································· 122
ntp-service enable ·································································································································· 123
ntp-service inbound enable ···················································································································· 123
ntp-service ipv6 acl ································································································································ 124
iii
ntp-service ipv6 dscp ····························································································································· 125
ntp-service ipv6 inbound enable ············································································································ 125
ntp-service ipv6 multicast-client ············································································································· 126
ntp-service ipv6 multicast-server ············································································································ 127
ntp-service ipv6 source ·························································································································· 128
ntp-service ipv6 unicast-peer ················································································································· 129
ntp-service ipv6 unicast-server ·············································································································· 130
ntp-service max-dynamic-sessions ········································································································ 132
ntp-service multicast-client ····················································································································· 133
ntp-service multicast-server ··················································································································· 134
ntp-service refclock-master ···················································································································· 135
ntp-service reliable authentication-keyid ································································································ 135
ntp-service source ·································································································································· 136
ntp-service time-offset-threshold ············································································································ 137
ntp-service unicast-peer ························································································································· 138
ntp-service unicast-server ······················································································································ 140
SNTP commands······················································································· 142
display sntp ipv6 sessions ······················································································································ 142
display sntp sessions ····························································································································· 142
sntp authentication enable ····················································································································· 143
sntp authentication-keyid ······················································································································· 144
sntp enable ············································································································································· 145
sntp ipv6 unicast-server ························································································································· 146
sntp reliable authentication-keyid ··········································································································· 147
sntp time-offset-threshold ······················································································································· 148
sntp unicast-server ································································································································· 148
SNMP commands ······················································································ 151
display snmp-agent community ·············································································································· 151
display snmp-agent context ··················································································································· 153
display snmp-agent group ······················································································································ 153
display snmp-agent local-engineid ········································································································· 154
display snmp-agent mib-node ················································································································ 155
display snmp-agent mib-view ················································································································· 159
display snmp-agent remote ···················································································································· 160
display snmp-agent statistics ················································································································· 161
display snmp-agent sys-info ··················································································································· 163
display snmp-agent trap queue ·············································································································· 163
display snmp-agent trapbuffer drop ······································································································· 164
display snmp-agent trapbuffer send ······································································································· 164
display snmp-agent trap-list ··················································································································· 165
display snmp-agent usm-user ················································································································ 166
enable snmp trap updown ······················································································································ 168
reset snmp-agent trapbuffer ··················································································································· 169
snmp virtual-access visible ···················································································································· 169
snmp-agent ············································································································································ 170
snmp-agent { inform | trap } source ········································································································ 170
snmp-agent calculate-password ············································································································ 171
snmp-agent community ·························································································································· 173
snmp-agent community-map ·················································································································· 176
snmp-agent context ································································································································ 176
snmp-agent group ·································································································································· 177
snmp-agent local-engineid ····················································································································· 179
snmp-agent log ······································································································································ 180
snmp-agent mib-view ····························································································································· 181
snmp-agent packet max-size ················································································································· 182
snmp-agent packet response dscp ········································································································ 183
snmp-agent port ····································································································································· 183
snmp-agent remote ································································································································ 184
snmp-agent sys-info contact ·················································································································· 185
snmp-agent sys-info location ················································································································· 185
iv
snmp-agent sys-info version ·················································································································· 186
snmp-agent target-host ·························································································································· 187
snmp-agent trap enable ························································································································· 189
snmp-agent trap if-mib link extended ····································································································· 190
snmp-agent trap life ······························································································································· 190
snmp-agent trap log ······························································································································· 191
snmp-agent trap queue-size ·················································································································· 192
snmp-agent usm-user { v1 | v2c } ·········································································································· 192
snmp-agent usm-user v3 ······················································································································· 194
snmp-agent usm-user v3 user-role ········································································································ 198
Sampler commands ··················································································· 200
display sampler ······································································································································ 200
sampler ·················································································································································· 200
Port mirroring commands ··········································································· 202
display mirroring-group ·························································································································· 202
mirroring-group ······································································································································· 203
mirroring-group mirroring-port (interface view) ······················································································· 204
mirroring-group mirroring-port (system view) ························································································· 204
mirroring-group monitor-port (interface view) ························································································· 205
mirroring-group monitor-port (system view) ··························································································· 207
Flow mirroring commands ·········································································· 211
mirror-to ifa-processor ···························································································································· 211
mirror-to interface ··································································································································· 211
mirroring erspanv3 switch-id ·················································································································· 214
sFlow commands ······················································································· 216
display sflow ··········································································································································· 216
sflow agent ············································································································································· 217
sflow collector ········································································································································· 218
sflow counter collector ···························································································································· 219
sflow counter interval ····························································································································· 220
sflow flow collector ································································································································· 220
sflow flow max-header ··························································································································· 221
sflow sampling-mode ····························································································································· 221
sflow sampling-rate ································································································································ 222
sflow source ··········································································································································· 223
Document conventions and icons ······························································ 224
Conventions ··················································································································································· 224
Network topology icons ·································································································································· 225
Support and other resources ····································································· 226
Accessing Hewlett Packard Enterprise Support····························································································· 226
Accessing updates ········································································································································· 226
Websites ················································································································································ 227
Customer self repair ······························································································································· 227
Remote support ······································································································································ 227
Documentation feedback ······················································································································· 227
Index ·········································································································· 229
1
Ping and tracert commands
ping
Use ping to test the reachability of the destination IP address and display ping statistics.
Syntax
ping [ ip ] [ -a source-ip | -c count | -f | -h ttl | -i interface-type
interface-number | -m interval | -n | -p pad | -q | -r | -s packet-size | -t
timeout | -tos tos | -v | -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.
-f: Sets the "Don’t 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.
2
-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 9600, and the default is 56.
-t timeout: Specifies the timeout time (in milliseconds) of an ICMP echo reply. The value range is
0 to 65535, and the default is 2000. If the source does not receive an ICMP echo reply within the
timeout, it considers the ICMP echo reply timed out.
-tos tos: Specifies the ToS value of ICMP echo requests. The value range is 0 to 255, and the
default is 0.
-v: Displays non-ICMP echo reply packets. If this keyword is not specified, the system does not
display non-ICMP echo reply packets.
-vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the
destination belongs. The vpn-instance-name argument represents the VPN instance name, a
case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify
this option.
host: Specifies the IP address or host name of the destination. The host name is a case-insensitive
string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-),
underscore (_), and dot (.).
Usage guidelines
To ping a device identified by its host name, configure the DNS settings on the device first. If the DNS
settings are not configured, the ping operation fails.
To abort the ping operation during the execution of the command, press Ctrl+C.
Examples
# Test whether the device with an IP address of 1.1.2.2 is reachable.
<Sysname> ping 1.1.2.2
Ping 1.1.2.2 (1.1.2.2): 56 data 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 instance vpn1 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
3
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
The output shows the following information:
•
The destination is reachable.
•
The route is 1.1.1.1 <-> {1.1.1.2; 1.1.2.1} <-> 1.1.2.2.
Table 1 Command output
Field
Description
Ping 1.1.2.2 (1.1.2.2): 56 data
bytes, press CTRL_C to break
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.
56 bytes from 1.1.2.2: icmp_seq=0
ttl=254 time=4.685 ms
Received ICMP echo replies from the device whose IP address is
1.1.2.2. If no echo reply is received within the timeout period, no
information is displayed.
• bytes—Number of bytes in the ICMP echo reply.
• icmp_seq—Packet sequence, used to determine whether a
segment is lost, disordered or repeated.
• ttl—TTL value in the ICMP echo reply.
• time—Response time.
RR: Routers through which the ICMP echo request passed. They are
displayed in inversed order, which means the router with a smaller
distance to the destination is displayed first.
--- Ping statistics for 1.1.2.2 --- Statistics on data received and sent in the ping operation.
--- Ping statistics for 1.1.2.2 in VPN
instance vpn1 --- Ping statistics for a device in a VPN instance.
5 packet(s) transmitted Number of ICMP echo requests sent.
5 packet(s) received Number of ICMP echo replies received.
0.0% packet loss Percentage of unacknowledged packets to the total packets sent.
4
Field
Description
round-trip min/avg/max/std-dev =
4.685/4.761/4.834/0.058 ms Minimum/average/maximum/standard deviation response time, in
milliseconds.
ping ipv6
Use ping ipv6 to test the reachability of the destination IPv6 address and display IPv6 ping
statistics.
Syntax
ping ipv6 [ -a source-ipv6 | -c count | -i interface-type interface-number
| -m interval | -q | -s packet-size | -t timeout | -tc traffic-class | -v
| -vpn-instance vpn-instance-name ] * host
Views
Any view
Predefined user roles
network-admin
Parameters
-a source-ipv6: Specifies an IPv6 address of the device as the source IP address of ICMP echo
requests. If this option is not specified, the source IPv6 address of ICMP echo requests is the IPv6
address of the outbound interface. See RFC 3484 for information about the address selection rule.
-c count: Specifies the number of ICMPv6 echo requests that are sent to the destination. The
value range is 1 to 4294967295, and the default is 5.
-i interface-type interface-number: Specifies the source interface for ICMPv6 echo
requests. This option must be specified when the destination address is a multicast 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 9600, 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 an MPLS L3VPN instance to which the
destination belongs. The vpn-instance-name argument represents the VPN instance name, 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 (.).
5
Usage guidelines
To ping a device identified by its host name, configure the DNS settings on the device first. If the DNS
settings are not configured, the IPv6 ping operation fails.
To abort the IPv6 ping operation during the execution of the command, press Ctrl+C.
Examples
# Test whether the IPv6 address (3001::2) is reachable.
<Sysname> ping ipv6 3001::2
Ping6(56 data bytes) 3001::1 --> 3001::2, press CTRL_C to break
56 bytes from 3001::2, icmp_seq=0 hlim=64 time=62.000 ms
56 bytes from 3001::2, icmp_seq=1 hlim=64 time=23.000 ms
56 bytes from 3001::2, icmp_seq=2 hlim=64 time=20.000 ms
56 bytes from 3001::2, icmp_seq=3 hlim=64 time=4.000 ms
56 bytes from 3001::2, icmp_seq=4 hlim=64 time=16.000 ms
--- Ping6 statistics for 3001::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 (3001::2) is reachable. Only the statistics are displayed.
<Sysname> ping ipv6 –q 3001::2
Ping6(56 data bytes) 3001::1 --> 3001::2, press CTRL_C to break
--- Ping6 statistics for 3001::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 (3001::2) is reachable. Detailed ping information is displayed.
<Sysname> ping ipv6 –v 3001::2
Ping6(56 data bytes) 3001::1 --> 3001::2, press CTRL_C to break
56 bytes from 3001::2, icmp_seq=0 hlim=64 dst=3001::1 idx=3 time=62.000 ms
56 bytes from 3001::2, icmp_seq=1 hlim=64 dst=3001::1 idx=3 time=23.000 ms
56 bytes from 3001::2, icmp_seq=2 hlim=64 dst=3001::1 idx=3 time=20.000 ms
56 bytes from 3001::2, icmp_seq=3 hlim=64 dst=3001::1 idx=3 time=4.000 ms
56 bytes from 3001::2, icmp_seq=4 hlim=64 dst=3001::1 idx=3 time=16.000 ms
--- Ping6 statistics for 3001::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
Table 2 Command output
Field
Description
Ping6(56 data bytes)
3001::1 --> 3001::2, press CTRL_C
to break
An ICMPv6 echo reply with a data length of 56 bytes is sent from
3001::1 to 3001::2.
Press Ctrl+C to abort the IPv6 ping operation.
6
Field
Description
56 bytes from 3001::2,
icmp_seq=1 hlim=64 dst=3001::1
idx=3 time=62.000 ms
Received ICMPv6 echo replies from the device whose IPv6 address
is 3001::2.
• The number of data bytes is 56.
• The packet sequence is 1.
• The hop limit value is 64.
• The destination address is 3001::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 3001::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.
tracert
Use tracert to trace the path that the packets traverse from source to destination.
Syntax
tracert [ -a source-ip | -f first-ttl| -m max-ttl | -p port | -q packet-number
| -t tos | -vpn-instance vpn-instance-name [ -resolve-as { global | none |
vpn } ] | -w timeout ] * host
Views
Any view
Predefined user roles
network-admin
Parameters
-a source-ip: Specifies an IP address of the device as the source IP address of probe packets. If
this option is not specified, the source IP address of probe packets is the primary IP address of the
outbound interface.
-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.
-vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the
destination belongs. The vpn-instance-name argument represents the VPN instance name, a
7
case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify
this option.
-resolve-as: Specifies a routing table for autonomous system (AS) resolution. Tracert searches
the specified routing table for the AS that each hop along the path belongs to. If you do not specify
this keyword, the global routing table is used. If the AS information is found, this command displays
the AS number next to the address of the hop in the probe result.
•
global: Specifies the global routing table.
•
none: Disables AS resolution.
•
vpn: Specifies the VPN routing table.
-w timeout: Specifies the timeout time in milliseconds of the reply packet for a probe packet. The
value range is 1 to 65535, and the default is 5000.
host: Specifies the IP address or host name of the destination. The host name is a case-insensitive
string of 1 to 253 characters. It can contain letters, digits, and special characters such as hyphen (-),
underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping command, use the tracert command to locate
failed nodes.
If the destination address is on the public network, you do not need to specify the -resolve-as
keyword to obtain the AS information. The device automatically uses the global routing table for AS
resolution.
If the destination address is on a private network, address information of intermediate hops might be
stored in either the global routing table or the VPN routing table. To learn the AS path that the
packets traverse, execute the tracert command twice, once with the -resolve-as global
keywords and again with the -resolve-as vpn keywords.
The output from the tracert command includes IP addresses of all the Layer 3 devices that the
packets traverse from source to destination. Asterisks (* * *) are displayed if the device cannot reply
with an ICMP error message. The reason might be the destination is unreachable or sending ICMP
timeout/destination unreachable packets is disabled.
Before starting a tracert operation, you must enable sending of ICMP destination unreachable
messages on the intermediate devices between the source and destination. The tracert operation
stops if any one of the following ICMP destination unreachable messages is received:
•
!N—Network unreachable.
•
!H—Destination host unreachable.
•
!P—Protocol unreachable. The protocol number is unknown.
•
!F—Fragmentation needed. This message indicates that packet fragmentation is needed but
the "Don’t Fragment" bit is set on an immediate device.
•
!W—Destination host unknown.
•
!Q—Network unreachable for ToS.
•
!T—Host unreachable for ToS.
•
!X—Communication administratively prohibited by filtering policies.
•
!V—Host precedence violation.
•
!C—Precedence cutoff in effect.
To abort the tracert operation during the execution of the command, press Ctrl+C.
Examples
# Display the path that the packets traverse from source to destination (1.1.2.2).
<Sysname> tracert 1.1.2.2
8
traceroute to 1.1.2.2 (1.1.2.2), 30 hops at most, 40 bytes each packet, press CTRL_C to
break
1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms
2 1.1.2.2 (1.1.2.2) [AS 100] 580 ms 470 ms 80 ms
# Display the path that the packets traverse from source to destination (1.1.3.2) in VPN instance
vpn1, as well as the AS information of the hops along the path.
<Sysname> tracert –vpn-instance vpn1 –resolve-as vpn 1.1.3.2
traceroute to 1.1.3.2 (1.1.3.2), 30 hops at most, 40 bytes each packet, press CTRL_C to
break
1 1.1.1.2 (1.1.1.2) 673 ms 425 ms 30 ms
2 1.1.2.2 (1.1.2.2) 580 ms 470 ms 80 ms
3 1.1.3.2 (1.1.3.2) [AS 65535] 530 ms 472 ms 380 ms
Table 3 Command output
Field
Description
traceroute to 1.1.2.2 (1.1.2.2) Display the route that
the IP packets traverse from the current device to the
device whose IP address is 1.1.2.2.
hops at most Maximum number of hops of the probe packets, which can be set by the
-m
keyword.
bytes each packet Number of bytes of a probe packet.
press CTRL_C to break During the execution of the command, press Ctrl+C to abort the tracert
operation.
2 1.1.2.2 (1.1.2.2) [AS 100]
580 ms 470 ms 80 ms
Probe result of the probe packets that contain a TTL value of 2, including
the following information about the second hop:
• Domain name of the hop. If no domain name is configured, the IP
address is displayed as the domain name.
• IP address of the hop. The IP address is displayed in parentheses.
• Number of the AS that the hop belongs to. The AS number appears
only when it is found for the hop in the specified routing table.
• The round-trip time of the probe packets.
The number of packets that can be sent in each probe can be set by using
the
-q
keyword.
tracert ipv6
Use tracert ipv6 to display the path that the IPv6 packets traverse from source to destination.
Syntax
tracert ipv6 [ -a source-ipv6 | -f first-hop | -i interface-type
interface-number | -m max-hops | -p port | -q packet-number | -t
traffic-class | -vpn-instance vpn-instance-name [ -resolve-as { global |
none | vpn } ] | -w timeout ] * host
Views
Any view
Predefined user roles
network-admin
9
Parameters
-a source-ipv6: Specifies a valid IPv6 address on the device as the source IPv6 address of the
probe packets. If you do not specify a source IPv6 address, the source IPv6 address of the probe
packets is the IPv6 address of the outbound interface.
-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.
-i interface-type interface-number: Specifies the source interface of probe packets. If
you do not specify this option, the system looks up the routing table or forwarding table for a
matching route and uses the output interface of that route as the source interface of probe packets.
You must specify this option if the destination address is a multicast address or a link-local address.
-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 an MPLS L3VPN instance to which the
destination belongs. The vpn-instance-name argument represents the VPN instance name, a
case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify
this option.
-resolve-as: Specifies a routing table for AS resolution. Tracert searches the specified routing
table for the AS that each hop along the path belongs to. If you do not specify this keyword, the global
routing table is used. If the AS information is found, this command displays the AS number next to
the address of the hop in the probe result.
•
global: Specifies the global routing table.
•
none: Disables AS resolution.
•
vpn: Specifies the VPN routing table.
-w timeout: Specifies the timeout time (in milliseconds) of the reply packet of a probe packet. The
value range is 1 to 65535, and the default is 5000.
host: Specifies the IPv6 address or host name of the destination. The host name is a
case-insensitive string of 1 to 253 characters. It can contain letters, digits, and special characters
such as hyphen (-), underscore (_), and dot (.).
Usage guidelines
After identifying network failure with the ping ipv6 command, you can use the tracert ipv6
command to locate failed nodes.
If the destination address is on the public network, you do not need to specify the -resolve-as
keyword to obtain the AS information. The device automatically uses the global routing table for AS
resolution.
If the destination address is on a private network, address information of intermediate hops might be
stored in either the global routing table or the VPN routing table. To learn the AS path that the
packets traverse, execute the tracert ipv6 command twice, once with the -resolve-as
global keywords and again with the -resolve-as vpn keywords.
The output from the tracert ipv6 command includes IPv6 addresses of all the Layer 3 devices
that the packets traverse from source to destination. Asterisks (* * *) are displayed if the device
10
cannot reply with an ICMP error message. The reason might be the destination is unreachable or
sending ICMP timeout/destination unreachable packets is disabled.
Before starting an IPv6 tracert operation, you must enable sending of ICMPv6 destination
unreachable messages on the intermediate devices between the source and destination. The IPv6
tracert operation stops if any one of the following ICMPv6 destination unreachable messages is
received:
•
!N—No route to destination.
•
!P—Communication with destination administratively prohibited by filtering policies.
•
!A—Address unreachable. The unreachable reason is unknown.
•
!S—Beyond scope of source address. This message is displayed if the probe packet has a
link-local source address and a non-link-local destination address. Such a packet cannot be
delivered to the destination without leaving the scope of the source address.
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 (3001:3::2).
<Sysname> tracert ipv6 3001:3::2
traceroute to 3001:3::2(3001:3::2), 30 hops at most, 60 byte packets, press CTRL_C to break
1 3001:1::2 0.661 ms 0.618 ms 0.579 ms
2 3001:2::2 [AS 100] 0.861 ms 0.718 ms 0.679 ms
3 3001:3::2 [AS 200] 0.822 ms 0.731 ms 0.708 ms
# Display the path that the packets traverse from source to destination (3001:3::2) in VPN instance
vpn1, as well as the AS information of the hops along the path.
<Sysname> tracert ipv6 –vpn-instance vpn1 –resolve-as vpn 3001:3::2
traceroute to 3001:3::2(3001:3::2), 30 hops at most, 60 byte packets , press CTRL_C to
break
1 3001:1::2 0.661 ms 0.618 ms 0.579 ms
2 3001:2::2 0.861 ms 0.718 ms 0.679 ms
3 3001:3::2 [AS 65535] 0.822 ms 0.731 ms 0.708 ms
Table 4 Command output
Description
traceroute to 3001:3::2 Display the route that the IPv6 packets traverse from the current device
to the device whose IP address is 3001:3:2.
hops at most Maximum number of hops of the probe packets, which can be set by the
-m
keyword.
byte packets Number of bytes of a probe packet.
2 3001:2::2 [AS 100] 0.861 ms
0.718 ms 0.679 ms
Probe result of the probe packets that contain a hoplimit value of 2,
including the following information about the second hop:
• IPv6 address of the hop.
• Number of the AS the hop belongs to. The AS number appears
only when it is found for the hop in the specified routing table.
• The round-trip time of the probe packets.
The number of packets that can be sent in each probe can be set by
using the
-q
keyword.
11
System debugging commands
debugging
Use debugging to enable debugging for a module.
Use undo debugging to disable debugging for a module or for all modules.
Syntax
debugging module-name [ option ]
undo debugging { all | module-name [ option ] }
Default
Debugging is disabled for all modules.
Views
User view
Predefined user roles
network-admin
Parameters
module-name: Specifies a module by its name, such as arp or device. For a list of supported
modules, use the debugging ? command.
option: Specifies the debugging option for a module. Available options vary by module. To display
the debugging options supported by a module, use the debugging module-name ? command.
all: Specifies all modules.
Usage guidelines
CAUTION:
Output of excessive debugging messages increases the CPU usage and downgrades the system
performance.
To guarantee system performance, enable debugging only for modules that are in an
exceptional condition.
The system sends generated debug messages to the device information center, which then sends
the messages to appropriate destinations based on the log output configuration. For more
information about the information center, see System Management Configuration Guide.
Examples
# Enable debugging for the device management module.
<Sysname> debugging dev
Related commands
display debugging
display debugging
Use display debugging to display the enabled debugging features for a module or for all
modules.
12
Syntax
display debugging [ module-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
module-name: Specifies a module by its name. For a list of supported modules, use the display
debugging ? command. If you do not specify a module name, this command displays the enabled
debugging features for all modules.
Examples
# Display all enabled debugging features.
<Sysname> display debugging
DEV debugging switch is on
Related commands
debugging
13
NQA commands
NQA client commands
advantage-factor
Use advantage-factor to set the advantage factor to be used for calculating Mean Opinion
Scores (MOS) and Calculated Planning Impairment Factor (ICPIF) values.
Use undo advantage-factor to restore the default.
Syntax
advantage-factor factor
undo advantage-factor
Default
The advantage factor is 0.
Views
Voice operation view
Predefined user roles
network-admin
Parameters
factor: Specifies the advantage factor in the range of 0 to 20.
Usage guidelines
The evaluation of voice quality depends on users' tolerance for voice quality. For users with higher
tolerance for voice quality, use the advantage-factor command to set an advantage factor.
When the system calculates the ICPIF value, it subtracts the advantage factor to modify ICPIF and
MOS values for voice quality evaluation.
Examples
# Set the advantage factor to 10 for the voice operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type voice
[Sysname-nqa-admin-test-voice] advantage-factor 10
agent-type
Use agent-type to specify the SNMP agent type for the SNMP DCA operation.
Use undo agent-type to restore the default.
Syntax
agent-type { net-snmp | user-defined | windows }
undo agent-type
14
Default
The default SNMP agent type is Net-SNMP.
Views
SNMP DCA template view
Predefined user roles
network-admin
Parameters
net-snmp: Specifies the Net-SNMP agent type.
user-defined: Specifies the user-defined agent type.
windows: Specifies the Windows agent type.
Usage guidelines
The SNMP DCA operation monitors the performance of a device running an SNMP agent. It collects
the CPU, memory, and disk usage from the SNMP agent and determines the device performance
based on the collected object values and their associated thresholds and weights.
Different SNMP agent types use different OIDs for the CPU, memory, and disk usage objects. Make
sure the SNMP agent type specified in the SNMP DCA template matches the type of the SNMP
agent to be monitored.
For Net-SNMP or Windows SNMP agents, the NQA client has built-in OIDs to collect the CPU,
memory, and disk usage objects. You can use the cpu, memory, and disk commands to set the
thresholds and weights for these objects. You can also use the oid command to configure custom
SNMP objects.
For SNMP agents of the user-defined type, the NQA client does not have predefined SNMP objects
to collect. You must use the oid command to configure the interested SNMP objects and their
associated thresholds and weights.
Examples
# Set the SNMP agent type to Windows for SNMP DCA template test.
<Sysname> system-view
[Sysname] nqa template snmpdca test
[Sysname-nqatplt-snmpdca-test] agent-type windows
Related commands
cpu
disk
memory
oid
codec-type
Use codec-type to configure the codec type for the voice operation.
Use undo codec-type to restore the default.
Syntax
codec-type { g711a | g711u | g729a }
undo codec-type
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118
  • Page 119 119
  • Page 120 120
  • Page 121 121
  • Page 122 122
  • Page 123 123
  • Page 124 124
  • Page 125 125
  • Page 126 126
  • Page 127 127
  • Page 128 128
  • Page 129 129
  • Page 130 130
  • Page 131 131
  • Page 132 132
  • Page 133 133
  • Page 134 134
  • Page 135 135
  • Page 136 136
  • Page 137 137
  • Page 138 138
  • Page 139 139
  • Page 140 140
  • Page 141 141
  • Page 142 142
  • Page 143 143
  • Page 144 144
  • Page 145 145
  • Page 146 146
  • Page 147 147
  • Page 148 148
  • Page 149 149
  • Page 150 150
  • Page 151 151
  • Page 152 152
  • Page 153 153
  • Page 154 154
  • Page 155 155
  • Page 156 156
  • Page 157 157
  • Page 158 158
  • Page 159 159
  • Page 160 160
  • Page 161 161
  • Page 162 162
  • Page 163 163
  • Page 164 164
  • Page 165 165
  • Page 166 166
  • Page 167 167
  • Page 168 168
  • Page 169 169
  • Page 170 170
  • Page 171 171
  • Page 172 172
  • Page 173 173
  • Page 174 174
  • Page 175 175
  • Page 176 176
  • Page 177 177
  • Page 178 178
  • Page 179 179
  • Page 180 180
  • Page 181 181
  • Page 182 182
  • Page 183 183
  • Page 184 184
  • Page 185 185
  • Page 186 186
  • Page 187 187
  • Page 188 188
  • Page 189 189
  • Page 190 190
  • Page 191 191
  • Page 192 192
  • Page 193 193
  • Page 194 194
  • Page 195 195
  • Page 196 196
  • Page 197 197
  • Page 198 198
  • Page 199 199
  • Page 200 200
  • Page 201 201
  • Page 202 202
  • Page 203 203
  • Page 204 204
  • Page 205 205
  • Page 206 206
  • Page 207 207
  • Page 208 208
  • Page 209 209
  • Page 210 210
  • Page 211 211
  • Page 212 212
  • Page 213 213
  • Page 214 214
  • Page 215 215
  • Page 216 216
  • Page 217 217
  • Page 218 218
  • Page 219 219
  • Page 220 220
  • Page 221 221
  • Page 222 222
  • Page 223 223
  • Page 224 224
  • Page 225 225
  • Page 226 226
  • Page 227 227
  • Page 228 228
  • Page 229 229
  • Page 230 230
  • Page 231 231
  • Page 232 232
  • Page 233 233
  • Page 234 234
  • Page 235 235
  • Page 236 236
  • Page 237 237

Aruba R9Y12A Reference guide

Category
Software
Type
Reference guide
This manual is also suitable for

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI