HP 6125G Installation manual

HP 6125 Blade Switch Series
Network Management and Monitoring
Command Reference
Part number: 5998-3173
Software version: Release 2103
Document version: 6W100-20120907

Legal and notice information
© Copyright 2012 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.

i
Contents
Ping, tracert, and system debugging commands······································································································· 1
Ping and tracert commands ·············································································································································1
ping············································································································································································1
ping ipv6···································································································································································5
tracert·········································································································································································7
tracert ipv6································································································································································9
System debugging commands······································································································································ 10
debugging······························································································································································ 10
display debugging ················································································································································ 11
NTP configuration commands···································································································································12
display ntp-service sessions ·································································································································· 12
display ntp-service status ······································································································································ 16
display ntp-service trace ······································································································································· 17
ntp-service access·················································································································································· 18
ntp-service authentication enable ························································································································ 19
ntp-service authentication-keyid ··························································································································· 20
ntp-service broadcast-client ·································································································································· 21
ntp-service broadcast-server ································································································································· 21
ntp-service dscp ····················································································································································· 22
ntp-service in-interface disable····························································································································· 23
ntp-service max-dynamic-sessions ························································································································ 23
ntp-service multicast-client····································································································································· 24
ntp-service multicast-server···································································································································· 25
ntp-service reliable authentication-keyid ············································································································· 25
ntp-service source-interface··································································································································· 26
ntp-service unicast-peer········································································································································· 27
ntp-service unicast-server ······································································································································ 28
Information center configuration commands············································································································29
display channel ····················································································································································· 29
display info-center ················································································································································· 30
display logbuffer···················································································································································· 32
display logbuffer summary ··································································································································· 34
display trapbuffer ·················································································································································· 35
enable log updown··············································································································································· 36
info-center channel name ····································································································································· 37
info-center console channel ·································································································································· 37
info-center enable·················································································································································· 38
info-center format unicom ····································································································································· 38
info-center logbuffer ·············································································································································· 39
info-center loghost ················································································································································· 40
info-center loghost source ····································································································································· 41
info-center monitor channel ·································································································································· 42
info-center snmp channel······································································································································ 43
info-center source ·················································································································································· 43
info-center synchronous ········································································································································ 45
info-center syslog channel ···································································································································· 46
info-center timestamp ············································································································································ 47
info-center timestamp loghost······························································································································· 48

ii
info-center trapbuffer············································································································································· 49
reset logbuffer························································································································································ 49
reset trapbuffer······················································································································································· 50
terminal debugging··············································································································································· 50
terminal logging ···················································································································································· 51
terminal monitor····················································································································································· 51
terminal trapping··················································································································································· 52
SNMP configuration commands ·······························································································································54
display snmp-agent community···························································································································· 54
display snmp-agent group ···································································································································· 55
display snmp-agent local-engineid ······················································································································ 56
display snmp-agent mib-view ······························································································································· 57
display snmp-agent statistics ································································································································ 59
display snmp-agent sys-info·································································································································· 60
display snmp-agent trap queue···························································································································· 61
display snmp-agent trap-list ·································································································································· 62
display snmp-agent usm-user································································································································ 63
enable snmp trap updown ··································································································································· 64
snmp-agent····························································································································································· 65
snmp-agent calculate-password ··························································································································· 66
snmp-agent community ········································································································································· 67
snmp-agent group·················································································································································· 68
snmp-agent local-engineid···································································································································· 69
snmp-agent log ······················································································································································ 70
snmp-agent ifmib long-ifindex enable ················································································································· 71
snmp-agent mib-view············································································································································· 72
snmp-agent packet max-size ································································································································ 73
snmp-agent packet response dscp······················································································································· 73
snmp-agent sys-info ··············································································································································· 74
snmp-agent target-host ·········································································································································· 75
snmp-agent trap enable ········································································································································ 76
snmp-agent trap if-mib link extended ·················································································································· 78
snmp-agent trap life··············································································································································· 79
snmp-agent trap queue-size·································································································································· 80
snmp-agent trap source········································································································································· 80
snmp-agent usm-user { v1 | v2c }························································································································ 81
snmp-agent usm-user v3········································································································································ 82
RMON configuration commands······························································································································86
display rmon alarm ··············································································································································· 86
display rmon event················································································································································ 87
display rmon eventlog··········································································································································· 88
display rmon history·············································································································································· 90
display rmon prialarm ·········································································································································· 92
display rmon statistics ··········································································································································· 94
rmon alarm····························································································································································· 96
rmon event······························································································································································ 98
rmon history ··························································································································································· 99
rmon prialarm ······················································································································································100
rmon statistics·······················································································································································102
Port mirroring configuration commands ················································································································ 103
display mirroring-group ······································································································································103
mirroring-group····················································································································································104
mirroring-group mirroring-port ···························································································································105

iii
mirroring-group monitor-egress··························································································································106
mirroring-group monitor-port ······························································································································107
mirroring-group remote-probe vlan····················································································································108
mirroring-port ·······················································································································································109
monitor-port··························································································································································110
Traffic mirroring configuration commands ············································································································ 111
mirror-to ································································································································································111
NQA configuration commands······························································································································ 112
NQA client configuration commands ························································································································112
advantage-factor ·················································································································································112
codec-type····························································································································································112
data-fill··································································································································································113
data-size ·······························································································································································114
description (any NQA operation view) ············································································································115
destination ip ·······················································································································································115
destination port····················································································································································116
display nqa history··············································································································································116
display nqa reaction counters····························································································································118
display nqa result ················································································································································120
display nqa statistics ···········································································································································124
filename································································································································································130
frequency······························································································································································131
history-record enable ··········································································································································131
history-record keep-time······································································································································132
history-record number ·········································································································································132
http-version ···························································································································································133
mode·····································································································································································134
next-hop································································································································································134
nqa········································································································································································135
nqa agent enable ················································································································································136
nqa agent max-concurrent··································································································································136
nqa schedule························································································································································137
operation (FTP operation view)··························································································································138
operation (HTTP operation view) ·······················································································································138
operation interface ··············································································································································139
password (FTP operation view)··························································································································139
probe count··························································································································································140
probe packet-interval ··········································································································································141
probe packet-number ··········································································································································142
probe packet-timeout···········································································································································142
probe timeout·······················································································································································143
reaction checked-element icpif···························································································································144
reaction checked-element { jitter-ds | jitter-sd } ································································································145
reaction checked-element mos ···························································································································146
reaction checked-element { owd-ds | owd-sd }································································································147
reaction checked-element packet-loss················································································································148
reaction checked-element probe-duration·········································································································149
reaction checked-element probe-fail (for trap)··································································································151
reaction checked-element probe-fail (for trigger) ·····························································································152
reaction checked-element rtt·······························································································································153
reaction trap ························································································································································154
resolve-target························································································································································155
route-option bypass-route····································································································································155

iv
source interface ···················································································································································156
source ip·······························································································································································157
source port ···························································································································································157
statistics hold-time················································································································································158
statistics max-group ·············································································································································158
statistics interval···················································································································································159
tos··········································································································································································160
ttl············································································································································································160
type ·······································································································································································161
url ··········································································································································································162
username (FTP operation view)··························································································································162
vpn-instance (ICMP echo operation view) ········································································································163
NQA server configuration commands·······················································································································163
display nqa server status ····································································································································164
nqa server enable ···············································································································································165
nqa server tcp-connect ········································································································································165
nqa server tcp-connect tos ··································································································································166
nqa server udp-echo ···········································································································································166
nqa server udp-echo tos······································································································································167
sFlow configuration commands······························································································································ 168
display sflow ························································································································································168
sflow agent···························································································································································169
sflow collector ······················································································································································170
sflow counter interval ··········································································································································171
sflow counter collector ········································································································································172
sflow flow collector··············································································································································172
sflow flow max-header········································································································································173
sflow sampling-mode ··········································································································································173
sflow sampling-rate ·············································································································································174
sflow source ·························································································································································175
IPC configuration commands ································································································································· 176
display ipc channel ·············································································································································176
display ipc link·····················································································································································177
display ipc multicast-group·································································································································178
display ipc node··················································································································································179
display ipc packet ···············································································································································179
display ipc performance·····································································································································181
display ipc queue ················································································································································182
ipc performance enable ·····································································································································183
reset ipc performance ·········································································································································184
Support and other resources ·································································································································· 185
Contacting HP ······························································································································································185
Subscription service ············································································································································185
Related information······················································································································································185
Documents····························································································································································185
Websites·······························································································································································185
Conventions ··································································································································································186
Index ········································································································································································ 188

1
Ping, tracert, and system debugging
commands
Ping and tracert commands
ping
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 ] * host
View
Any view
Default level
0: Visit level
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 the source IP address of an ICMP echo request (ECHO-REQUEST). It must be an
IP address configured on the device. If this option is not specified, the source IP address of an ICMP echo
request is the primary IP address of the outbound interface of the request.
-c count: Specifies the number of times that an ICMP echo request is sent, which is in the range of 1 to
4294967295 and defaults to 5.
-f: Discards packets larger than the MTU of a given interface, which means the ICMP echo request is not
allowed to be fragmented.
-h ttl: Specifies the TTL value for an ICMP echo request, which is in the range of 1 to 255 and defaults to
255.
-i interface-type interface-number: Specifies the ICMP echo request sending interface by its type and
number. If this option is not specified, the ICMP echo request sending interface is determined by
searching the routing table or forwarding table according to the destination IP address.
-m interval: Specifies the interval (in milliseconds) to send an ICMP echo request, which is in the range
of 1 to 65535 and defaults to 200.
•If a response from the destination is received within the timeout time, the interval to send the next
echo request equals the actual response period plus the value of interval.
•If no response from the destination is received within the timeout time, the interval to send the next
echo request equals the timeout value plus the value of interval.
-n: Disables domain name resolution for the host argument. When this keyword is not specified, if the
host argument represents the host name of the destination, the device translates host into an address.

2
-p pad: Specifies the value of the pad field in an ICMP echo request, in hexadecimal format, 1 to 8 bits,
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 repeatedly 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, like
0x010203…feff01….
-q: Specifies that only statistics are displayed. Absence of this keyword indicates that all information is
displayed.
-r: Specifies the recording routing information. If this keyword is not specified, routes are not recorded.
-s packet-size: Specifies the length (in bytes) of an ICMP echo request, which is in the range of 20 to 8100
and defaults to 56.
-t timeout: Specifies the timeout value (in milliseconds) of an ICMP echo reply (ECHO-REPLY). If the
source does not receive an ICMP echo reply within the timeout, it considers the ICMP echo reply timed
out. The value is in the range of 0 to 65535 and defaults to 2000.
-tos tos: Specifies the ToS value for an echo request, which is in the range of 0 to 255 and defaults to 0.
-v: Displays the non-ICMP echo reply received. If this keyword is not specified, the system does not
display non ICMP echo reply.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN to which the destination belongs, where
vpn-instance-name 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 (a string of 1 to 255 characters) for the destination.
Description
Use ping to verify whether the destination in an IP network is reachable, and to display the related
statistics.
With the ping command executed, the source sends an ICMP echo request to the destination:
•If the destination name is unrecognizable, the system outputs "Error: Ping: Unknown host
host-name."
•If the source receives an ICMP echo reply from the destination within the timeout, the system outputs
the related information of the reply.
•If the source does not receive an ICMP echo reply from the destination within the timeout, the system
outputs "Request time out."
•To use the name of the destination host to perform the ping operation, you must configure the
Domain Name System (DNS) on the device first. Otherwise, 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: 56 data bytes, press CTRL_C to break
Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=205 ms
Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms

3
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/41/205 ms
The output shows the following:
•The destination is reachable.
•All ICMP echo requests sent by the source have got responses.
•The minimum time, average time, and maximum time for the packet’s roundtrip time are 1 ms, 41
ms, and 205 ms respectively.
# 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: 56 data bytes, press CTRL_C to break
Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=205 ms
Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/41/205 ms
The output shows the following:
•The destination in VPN 1 is reachable.
•All ICMP echo requests sent by the source have got responses.
•The minimum time, average time, and maximum time for the packet’s roundtrip time are 1 ms, 41
ms, and 205 ms respectively.
# Test whether the device with an IP address of 1.1.2.2 is reachable. Only the check results are displayed.
<Sysname> ping -q 1.1.2.2
PING 1.1.2.2: 56 data bytes, press CTRL_C to break
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
4 packet(s) received
20.00% packet loss
round-trip min/avg/max = 1/12/29 ms
# Test whether the device with an IP address of 1.1.2.2 is reachable. The route information is displayed.
<Sysname> ping -r 1.1.2.2
PING 1.1.2.2: 56 data bytes, press CTRL_C to break
Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=53 ms
Record Route:
1.1.2.1
1.1.2.2

4
1.1.1.2
1.1.1.1
Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms
Record Route:
1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms
Record Route:
1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms
Record Route:
1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms
Record Route:
1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/11/53 ms
The output shows the following:
•The destination is reachable.
•T h e ro 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
p
tion
PING 1.1.2.2 Test whether the device with IP address 1.1.2.2 is reachable.
56 data bytes Number of data bytes in each ICMP echo request.
press CTRL_C to break During the execution of the command, you can press Ctrl+C to abort the
ping operation.

5
Field Descri
p
tion
Reply from 1.1.2.2 : bytes=56
Sequence=1 ttl=255 time=1 ms
Received the ICMP reply from the device whose IP address is 1.1.2.2. If
no reply is received during the timeout period, "Request time out" is
displayed.
•bytes—Indicates the number of data bytes in the ICMP reply.
•Sequence—Indicates the packet sequence, used to determine
whether a segment is lost, disordered or repeated.
•ttl—Indicates the TTL value in the ICMP reply.
•time—Indicates the response time.
Record Route:
Routers through which the ICMP echo request passed. They are
displayed in inversed order. The router with a smaller distance to the
destination is displayed first.
--- 1.1.2.2 ping statistics --- Statistics on data received and sent in the ping operation.
5 packet(s) transmitted Number of ICMP echo requests sent.
5 packet(s) received Number of ICMP echo requests received.
0.00% packet loss Percentage of packets not responded to the total packets sent.
round-trip min/avg/max = 0/4/20
ms
Minimum/average/maximum response time, in ms. The field is not
available for failed ping attempts in an IPv4 network. In an IPv6 network,
however, the field is available and set to 0/0/0 ms.
ping ipv6
Syntax
ping ipv6 [ -a source-ipv6 | -c count | -m interval | -s packet-size | -t timeout | -tos tos| -vpn-instance
vpn-instance-name ] * host [ -i interface-type interface-number ]
View
Any view
Default level
0: Visit level
Parameters
-a source-ipv6: Specifies the source IPv6 address of an ICMP echo request. It must be a legal IPv6
address configured on the device. If this option is not specified, the source IPv6 address of an ICMP echo
request is the address of the outbound interface of the request. The address selection rule is defined by
RFC 3484.
-c count: Specifies the number of times that an ICMPv6 echo request is sent, which is in the range of 1
to 4294967295 and defaults to 5.
-m interval: Specifies the interval (in milliseconds) to send an ICMPv6 echo reply, which is in the range
of 1 to 65535 and defaults to 200.
•If a response from the destination is received within the timeout time, the interval to send the next
echo request equals the actual response period plus the value of interval.
•If no response from the destination is received within the timeout time, the interval to send the next
echo request equals the timeout value plus the value of interval.

6
-s packet-size: Specifies the length (in bytes) of an ICMPv6 echo request, which is in the range of 20 to
8100 and defaults to 56.
-t timeout: Specifies the timeout value (in milliseconds) of an ICMPv6 echo reply, which is in the range of
0 to 65535 and defaults to 2000.
-tos tos: Specifies the ToS value for an IPv6 echo request, which is in the range of 0 to 255 and defaults
to 0.
host: Specifies the IPv6 address or host name of the destination, a string of 1 to 46 characters.
-i interface-type interface-number: Specifies an outbound interface by its type and number. This
parameter can be used only when the destination address is the link local address and the specified
outbound interface must have a link local address. For more information about the configuration of a link
local address, see Layer 3—IP Services Configuration Guide. If this parameter is not provided, the ICMP
echo request sending interface is determined by searching the routing table or forwarding table
according to the destination IP address.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN to which the destination belongs, where
vpn-instance-name is a case-sensitive string of 1 to 31 characters. If the destination is on the public
network, do not specify this option.
Description
Use ping ipv6 to verify whether an IPv6 address is reachable, and display the corresponding statistics.
To use the name of the destination host to perform the ping ipv6 operation, you must configure DNS on
the device first. Otherwise, the ping ipv6 operation fails. For more information about DNS, see Layer
3—IP Services Configuration Guide.
To abort the ping ipv6 operation during the execution of the command, press Ctrl+C.
Examples
# Verify whether the IPv6 address 2001::1 is reachable.
<Sysname> ping ipv6 2001::1
PING 2001::2 : 56 data bytes, press CTRL_C to break
Reply from 2001::1
bytes=56 Sequence=1 hop limit=64 time = 62 ms
Reply from 2001::1
bytes=56 Sequence=2 hop limit=64 time = 26 ms
Reply from 2001::1
bytes=56 Sequence=3 hop limit=64 time = 20 ms
Reply from 2001::1
bytes=56 Sequence=4 hop limit=64 time = 4 ms
Reply from 2001::1
bytes=56 Sequence=5 hop limit=64 time = 16 ms
--- 2001::2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 4/25/62 ms
# Verify whether the IPv6 address 2001::1 in VPN 1 is reachable.
<Sysname> ping ipv6 –vpn-instance vpn1 2001::1
PING 2001::1 : 56 data bytes, press CTRL_C to break

7
Reply from 2001::1
bytes=56 Sequence=1 hop limit=64 time = 62 ms
Reply from 2001::1
bytes=56 Sequence=2 hop limit=64 time = 26 ms
Reply from 2001::1
bytes=56 Sequence=3 hop limit=64 time = 20 ms
Reply from 2001::1
bytes=56 Sequence=4 hop limit=64 time = 4 ms
Reply from 2001::1
bytes=56 Sequence=5 hop limit=64 time = 16 ms
--- 2001::2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 4/25/62 ms
The "hop limit" field in this prompt information has the same meaning as the "ttl" field in the prompt
information displayed by the IPv4 ping command, indicating the TTL value in the ICMPv6 echo request.
For a description of other fields, see Table 1.
tracert
Syntax
tracert [ -a source-ip | -f first-ttl |-m max-ttl | -p port | -q packet-number | -tos tos | -vpn-instance
vpn-instance-name |-w timeout ] * host
View
Any view
Default level
0: Visit level
Parameters
-a source-ip: Specifies the source IP address of a tracert packet. It must be a legal IP address configured
on the device. If this option is not specified, the source IP address of an ICMP echo request is the primary
IP address of the outbound interface of the tracert packet.
-f first-ttl: Specifies the first TTL (the allowed number of hops for the first packet). It is in the range of 1 to
255 and defaults to 1, and must be less than the maximum TTL.
-m max-ttl: Specifies the maximum TTL, or, the maximum allowed number of hops for a packet. It is in the
range of 1 to 255 and defaults to 30, and must be greater than the first TTL.
-p port: Specifies the UDP port number of the destination, which is in the range of 1 to 65535 and
defaults to 33434. You do not need to modify this option.
-q packet-number: Specifies the number of probe packets sent each time, which is in the range of 1 to
65535 and defaults to 3.
-tos tos: Specifies the ToS value for a tracert packet, which is in the range of 0 to 255 and defaults to 0.

8
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN to which the destination belongs, where
vpn-instance-name 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 of the reply packet of a probe packet, which is in the range of 1
to 65535 milliseconds and defaults to 5000 milliseconds.
host: Specifies the IP address or host name (a string of 1 to 255 characters) for the destination.
Description
Use tracert to trace the path that the packets traverse from source to destination.
In the event of network failure, you can use the tracert command to determine the failed nodes.
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 (probably because 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 with an IP address of 1.1.2.2.
<Sysname> tracert 1.1.2.2
traceroute to 1.1.2.2(1.1.2.2) 30 hops max,40 bytes packet, press CTRL_C to break
1 1.1.1.2 673 ms 425 ms 30 ms
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> system-view
[Sysname] ip ttl-expires enable
[Sysname] ip unreachables enable
[Sysname] tracert 192.168.0.46
traceroute to 192.168.0.46(192.168.0.46) 30 hops max,40 bytes 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 2 Command output
Field Descri
p
tion
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 max Maximum number of hops of the probe packets, which can be set
through the -m keyword.
bytes packet Number of bytes of a probe packet.
press CTRL_C to break During the execution of the command, you can press Ctrl+C to abort
the tracert operation.

9
Field Descri
p
tion
1 1.1.1.2 673 ms 425 ms 30 ms
Probe result of the probe packets whose TTL is 1, including the IP
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
through the -q keyword.
MPLS Label=100048 Exp=0 TTL=1
S=1
ICMP timeout packets on an MPLS network, carry MPLS label
information:
•Label—Label value that is used to identify a forwarding
equivalence class (FEC).
•Exp—Reserved, usually used for class of service (CoS).
•TTL—TTL value.
•S—MPLS supports multiple levels of labels. Value 1 indicates that
the label is at the bottom of the label stack, and value 0 indicates
that the label is not at the bottom of the label stack.
tracert ipv6
Syntax
tracert ipv6 [ -f first-ttl | -m max-ttl | -p port | -q packet-number | -tos tos| -vpn-instance
vpn-instance-name | -w timeout ] * host
View
Any view
Default level
0: Visit level
Parameters
-f first-ttl: Specifies the first TTL, or, the allowed number of hops for the first packet. It is in the range of 1
to 255 and defaults to 1, and must be less than the maximum TTL.
-m max-ttl: Specifies the maximum TTL (the maximum allowed number of hops for a packet). It is in the
range of 1 to 255 and defaults to 30, and must be greater than the first TTL.
-p port: Specifies the UDP port number of the destination, which is in the range of 1 to 65535 and
defaults to 33434. It is unnecessary to modify this option.
-q packet-number: Specifies the number of probe packets sent each time, which is in the range of 1 to
65535 and defaults to 3.
-w timeout: Specifies the timeout time of the reply packet of a probe packet, which is in the range of 1
to 65535 milliseconds and defaults to 5000 milliseconds.
host: Specifies the IPv6 address or host name of the destination, a string of 1 to 46 characters.
-tos tos: Specifies the ToS value for an IPv6 tracert packet, which is in the range of 0 to 255 and defaults
to 0.
-vpn-instance vpn-instance-name: Specifies the MPLS L3VPN to which the destination belongs, where
vpn-instance-name is a case-sensitive string of 1 to 31 characters. If the destination is on the public
network, do not specify this option.
Description
Use tracert ipv6 to view the path the IPv6 packets traverse from source to destination.

10
In the event of network failure, you can use this command to determine the failed nodes.
Output from the tracert ipv6 command includes IPv6 addresses of all the Layer 3 devices the packets
traverse from source to destination. Asterisks (* * *) are displayed if the device cannot reply with an
ICMP error message (probably because 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
# View the path the packets traverse from source to destination with IPv6 address 2001::1.
<Sysname> tracert ipv6 2001::1
traceroute to 2001::1 30 hops max,60 bytes packet, press CTRL_C to break
1 2001::1 3 ms <1 ms 19 ms
# View the path the packets traverse from source to destination with IPv6 address 2001::1 in VPN 1.
<Sysname> tracert ipv6 –vpn-instance vpn1 2001::1
traceroute to 2001::1 30 hops max,60 bytes packet, press CTRL_C to break
1 2001::1 3 ms <1 ms 19 ms
For a description of the fields in the output, see Table 2.
System debugging commands
debugging
Syntax
debugging { all [ timeout time ] | module-name [ option ] }
undo debugging { all | module-name [ option ] }
View
User view
Default level
1: Monitor level
Parameters
all: 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 time. The value is in the
range of 1 to 1440, in minutes.
module-name: Module name, such as arp or device. To display the current module name, use the
debugging ? command.
option: The debugging option for a specific module. Different modules have different debugging options
in terms of their number and content. To display the currently supported options, use the debugging
module-name ? command.
Description
Use debugging to enable the debugging of a specific module.
Use undo debugging to disable the debugging of a specific module.

11
By default, debugging functions of all modules are disabled.
Output of the debugging information may degrade system efficiency, so you should enable the
debugging of the corresponding module for diagnosing network failure, and not to enable debugging
of multiple modules at the same time.
Default level describes the default level of the debugging all command. Different debugging commands
may have different default levels.
Configure the debugging, terminal debugging and terminal monitor commands first to display detailed
debugging information on the terminal. For more information about the terminal debugging and
terminal monitor commands, see "Information center commands."
Related commands: display debugging.
Examples
# Enable IP packet debugging.
<Sysname> debugging ip packet
display debugging
Syntax
display debugging [ interface interface-type interface-number ] [module-name ] [ |{ begin | exclude |
include } regular-expression ]
View
Any view
Default level
1: Monitor level
Parameters
interface interface-type interface-number: Displays the debugging settings of the specified interface,
where the interface-type interface-number argument represents the interface type and number.
module-name: Module name.
|: Filters command output by specifying a regular expression. For more information about regular
expressions, see Fundamentals Configuration Guide.
begin: Displays the first line that matches the specified regular expression and all lines that follow.
exclude: Displays all lines that do not match the specified regular expression.
include: Displays all lines that match the specified regular expression.
regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.
Description
Use display debugging to display enabled debugging functions.
Related commands: debugging.
Examples
# Display all enabled debugging functions.
<Sysname> display debugging
IP packet debugging is on

12
NTP configuration commands
display ntp-service sessions
Syntax
display ntp-service sessions [ verbose ] [ |{ begin | exclude | include } regular-expression ]
View
Any view
Default level
1: Monitor level
Parameters
verbose: Displays detailed information about all NTP sessions. If you do not specify this keyword, the
command only displays brief information about the NTP sessions.
|: Filters command output by specifying a regular expression. For more information about regular
expressions, see Fundamentals Configuration Guide.
begin: Displays the first line that matches the specified regular expression and all lines that follow.
exclude: Displays all lines that do not match the specified regular expression.
include: Displays all lines that match the specified regular expression.
regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.
Description
Use display ntp-service sessions to display information about all NTP sessions.
Examples
# Display brief information about all NTP sessions.
<Sysname> display ntp-service sessions
source reference stra reach poll now offset delay disper
********************************************************************************
[12345]127.127.1.0 127.127.1.0 3 1 64 33 0.0 0.0 0.0
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured
Total associations : 1
Table 3 Command output
Field Descri
p
tion
source IP address of the clock source.

13
Field Descri
p
tion
reference
Reference clock ID of the clock source:
•If the reference clock is the local clock, the value of this field is
related to the value of the stra field:
{When the value of the stra field is 0 or 1, this field is LOCL.
{When the stra field has another value, this field is the IP
address of the local clock.
•If the reference clock is the clock of another device on the
network, the value of this field is the IP address of that device.
stra
Stratum level of the clock source, which determines the clock
precision. The value ranges from 1 to 16. The clock precision
decreases from stratum 1 to stratum 16. A stratum 1 clock has the
highest precision, and a stratum 16 clock is not synchronized.
reach Reachability count of the clock source. A value of 0 indicates that
the clock source in unreachable.
poll Poll interval in seconds, namely, the maximum interval between
successive NTP messages.
now
Length of time from when the last NTP message was received or
when the local clock was last updated to the current time.
Time is in seconds by default. If the time length is greater than 2048
seconds, it is displayed in minutes; if greater than 300 minutes, in
hours; if greater than 96 hours, in days.
offset Offset of the system clock relative to the reference clock, in
milliseconds.
delay Roundtrip delay from the local device to the clock source, in
milliseconds.
disper Maximum error of the system clock relative to the reference source.
[12345]
•1—Clock source selected by the switch, namely, the current
reference source.
•2—Stratum level of the clock source is less than or equal to 15.
•3—This clock source has survived the clock selection algorithm.
•4—This clock source is a candidate clock source.
•5—This clock source was created by a configuration command.
Total associations Total number of associations.
# Display detailed information about all NTP sessions.
<Sysname> display ntp-service sessions verbose
clock source: 127.127.1.0
clock stratum: 3
clock status: configured, master, sane, valid
reference clock ID: 127.127.1.0
local mode: client, local poll: 6
peer mode: server, peer poll: 6
offset: 0.0000 ms,delay: 0.00 ms, disper: 0.02 ms
root delay: 0.00 ms, root disper: 10.00 ms
reach: 1, sync dist: 0.010, sync state: 2
precision: 2^18, version: 3, peer interface: InLoopBack0

14
reftime: 10:56:22.442 UTC Jan 7 2011(CE2686D6.71484513)
orgtime: 10:56:22.442 UTC Jan 7 2011(CE2686D6.71484513)
rcvtime: 10:56:22.442 UTC Jan 7 2011(CE2686D6.7149E881)
xmttime: 10:56:22.442 UTC Jan 7 2011(CE2686D6.71464DC2)
filter delay : 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
filter offset: 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
filter disper: 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Total associations : 1
Table 4 Command output
Field Descri
p
tion
clock source IP address of the clock source.
clock stratum
Stratum level of the clock source, which determines the clock
precision. The value ranges from 1 to 16. The clock precision
decreases from stratum 1 to stratum 16. A stratum 1 clock has the
highest precision, and a stratum 16 clock is not synchronized.
clock status
Status of the clock source corresponding to this session:
•configured—The session was created by a configuration
command.
•dynamic—This session is established dynamically.
•master—The clock source is the primary reference source of the
current system.
•selected—The clock source has survived the clock selection
algorithm.
•candidate—The clock source is the candidate reference source.
•sane—The clock source has passed the sane authentication.
•insane—The clock source has failed the sane authentication.
•valid—The clock source is valid, which means the clock source
meet the following requirements: it has passed the authentication
and is being synchronized; its stratum level is valid; and its root
delay and root dispersion values are within their ranges.
•invalid—The clock source is invalid.
•unsynced—The clock source has not been synchronized or the
value of the stratum level is invalid.
reference clock ID
Reference clock ID of the clock source:
•If the reference clock is the local clock, the value of this field is
related to the stratum level of the clock source:
{When the stratum level of the clock source is 0 or 1, this field
is LOCL.
{When the stratum level of the clock source has another value,
this field is the IP address of the local clock.
•If the reference clock is the clock of another device on the
network, the value of this field is the IP address of that device.