H3C SR6600 SPE-FWM Installation manual
H3C SR6600/SR6600-X Routers
Network Management and Monitoring
Command Reference
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: SR6600X-CMW520-R3103
SR6602-CMW520-R3103
SR6602X_MCP-CMW520-R3103
SR6600-CMW520-R3103-RPE
SR6600-CMW520-R3103-RSE
Document version: 20130222-C-1.12
Copyright © 2007-2013, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,
SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of
Hangzhou H3C Technologies Co., Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
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
NQA configuration commands·································································································································13
NQA client configuration commands ·························································································································· 13
advantage-factor ··················································································································································· 13
codec-type······························································································································································ 13
data-fill···································································································································································· 14
data-size ································································································································································· 15
description (any NQA operation view) ·············································································································· 16
destination ip ························································································································································· 16
destination port······················································································································································ 17
display nqa history················································································································································ 18
display nqa reaction counters······························································································································ 19
display nqa result ·················································································································································· 21
display nqa statistics ············································································································································· 25
filename·································································································································································· 31
frequency································································································································································ 31
history-record enable ············································································································································ 32
history-record keep-time········································································································································ 32
history-record number ··········································································································································· 33
http-version ····························································································································································· 34
mode······································································································································································· 34
next-hop·································································································································································· 35
nqa·········································································································································································· 36
nqa agent enable ·················································································································································· 36
nqa agent max-concurrent···································································································································· 37
nqa schedule·························································································································································· 37
operation (FTP operation view)···························································································································· 38
operation (HTTP operation view) ························································································································· 39
operation interface ················································································································································ 39
password (FTP operation view)···························································································································· 40
probe count···························································································································································· 41
probe packet-interval ············································································································································ 42
probe packet-number ············································································································································ 42
probe packet-timeout············································································································································· 43
probe timeout························································································································································· 44
reaction checked-element icpif····························································································································· 44
reaction checked-element { jitter-ds | jitter-sd } ·································································································· 45
reaction checked-element mos ····························································································································· 47
reaction checked-element { owd-ds | owd-sd }·································································································· 48
reaction checked-element packet-loss·················································································································· 49
ii
reaction checked-element probe-duration··········································································································· 50
reaction checked-element probe-fail (for trap)···································································································· 51
reaction checked-element probe-fail (for trigger) ······························································································· 52
reaction checked-element rtt································································································································· 53
reaction trap ·························································································································································· 55
resolve-target·························································································································································· 55
route-option bypass-route······································································································································ 56
source interface ····················································································································································· 57
source ip································································································································································· 57
source port ····························································································································································· 58
statistics hold-time·················································································································································· 59
statistics max-group ··············································································································································· 60
statistics interval····················································································································································· 60
tos············································································································································································ 61
ttl·············································································································································································· 62
type ········································································································································································· 62
url ············································································································································································ 63
username (FTP operation view)···························································································································· 64
vpn-instance (ICMP echo operation view) ·········································································································· 64
NQA server configuration commands························································································································· 65
display nqa server status ······································································································································ 65
nqa server enable ················································································································································· 66
nqa server tcp-connect ·········································································································································· 66
nqa server udp-echo ············································································································································· 67
NTP configuration commands···································································································································69
display ntp-service sessions ·································································································································· 69
display ntp-service status ······································································································································ 73
display ntp-service trace ······································································································································· 74
ntp-service access·················································································································································· 75
ntp-service authentication enable ························································································································ 76
ntp-service authentication-keyid ··························································································································· 77
ntp-service broadcast-client ·································································································································· 78
ntp-service broadcast-server ································································································································· 78
ntp-service in-interface disable····························································································································· 79
ntp-service max-dynamic-sessions ························································································································ 80
ntp-service multicast-client····································································································································· 80
ntp-service multicast-server···································································································································· 81
ntp-service refclock-master···································································································································· 82
ntp-service reliable authentication-keyid ············································································································· 82
ntp-service source-interface··································································································································· 83
ntp-service unicast-peer········································································································································· 84
ntp-service unicast-server ······································································································································ 85
IPC configuration commands ····································································································································87
display ipc channel ··············································································································································· 87
display ipc link······················································································································································· 88
display ipc multicast-group··································································································································· 89
display ipc node···················································································································································· 90
display ipc packet ················································································································································· 91
display ipc performance······································································································································· 92
display ipc queue ·················································································································································· 93
ipc performance enable ······································································································································· 95
reset ipc performance ··········································································································································· 96
iii
SNMP commands ······················································································································································97
display snmp-agent community···························································································································· 97
display snmp-agent group ···································································································································· 98
display snmp-agent local-engineid ····················································································································100
display snmp-agent mib-view ·····························································································································100
display snmp-agent statistics ······························································································································102
display snmp-agent sys-info································································································································104
display snmp-agent trap queue··························································································································105
display snmp-agent trap-list ································································································································105
display snmp-agent usm-user······························································································································106
enable snmp trap updown ·································································································································108
snmp-agent···························································································································································109
snmp-agent calculate-password ·························································································································109
snmp-agent community ·······································································································································110
snmp-agent group················································································································································112
snmp-agent local-engineid··································································································································114
snmp-agent log ····················································································································································114
snmp-agent mib-view···········································································································································115
snmp-agent packet max-size ······························································································································116
snmp-agent sys-info ·············································································································································117
snmp-agent target-host ········································································································································118
snmp-agent trap enable ······································································································································120
snmp-agent trap if-mib link extended ················································································································122
snmp-agent trap life·············································································································································123
snmp-agent trap queue-size································································································································124
snmp-agent trap source·······································································································································124
snmp-agent usm-user { v1 | v2c }······················································································································125
snmp-agent usm-user v3······································································································································127
MIB configuration commands ································································································································ 130
display mib-style ··················································································································································130
mib-style································································································································································130
RMON configuration commands··························································································································· 132
display rmon alarm ·············································································································································132
display rmon event··············································································································································133
display rmon eventlog·········································································································································135
display rmon history············································································································································136
display rmon prialarm ········································································································································139
display rmon statistics ·········································································································································140
rmon alarm···························································································································································142
rmon event····························································································································································144
rmon history ·························································································································································145
rmon prialarm ······················································································································································146
rmon statistics·······················································································································································148
Sampler configuration commands ························································································································· 150
display sampler ···················································································································································150
reset sampler statistics·········································································································································151
sampler·································································································································································151
Port mirroring configuration commands ················································································································ 153
display mirroring-group ······································································································································153
mirroring-group····················································································································································154
mirroring-group mirroring-port ···························································································································155
mirroring-group monitor-egress··························································································································156
iv
mirroring-group monitor-port ······························································································································157
mirroring-group remote-probe vlan····················································································································158
mirroring-port ·······················································································································································159
monitor-port··························································································································································160
Traffic mirroring configuration commands ············································································································ 162
mirror-to ································································································································································162
NetStream configuration commands ····················································································································· 163
display ip netstream cache·································································································································163
display ip netstream export ································································································································166
display ip netstream template ····························································································································168
enable···································································································································································170
ip netstream··························································································································································171
ip netstream aggregation ···································································································································172
ip netstream export host ·····································································································································173
ip netstream export rate······································································································································174
ip netstream export source ·································································································································174
ip netstream export v9-template refresh-rate packet ························································································175
ip netstream export v9-template refresh-rate time ····························································································176
ip netstream export version ································································································································177
ip netstream filter·················································································································································178
ip netstream max-entry········································································································································179
ip netstream mpls·················································································································································180
ip netstream sampler···········································································································································180
ip netstream timeout active·································································································································181
ip netstream timeout inactive······························································································································182
reset ip netstream statistics ·································································································································182
IPv6 NetStream configuration commands············································································································· 184
display ipv6 netstream cache ····························································································································184
display ipv6 netstream export····························································································································188
display ipv6 netstream template························································································································189
enable···································································································································································192
ipv6 netstream ·····················································································································································193
ipv6 netstream aggregation·······························································································································193
ipv6 netstream export host ·································································································································194
ipv6 netstream export rate ·································································································································196
ipv6 netstream export source·····························································································································196
ipv6 netstream export v9-template refresh-rate packet····················································································197
ipv6 netstream export v9-template refresh-rate time························································································198
ipv6 netstream export version 9 ························································································································199
ipv6 netstream max-entry····································································································································199
ipv6 netstream timeout active ····························································································································200
ipv6 netstream timeout inactive ·························································································································201
reset ipv6 netstream statistics ·····························································································································202
Information center configuration commands········································································································· 203
display channel ···················································································································································203
display info-center ···············································································································································204
display logbuffer··················································································································································205
display logbuffer summary ·································································································································207
display logfile buffer ···········································································································································208
display logfile summary······································································································································209
display trapbuffer ················································································································································210
enable log updown·············································································································································211
v
info-center channel name ···································································································································212
info-center console channel ································································································································213
info-center enable················································································································································213
info-center format unicom ···································································································································214
info-center logbuffer ············································································································································214
info-center logfile enable ····································································································································215
info-center logfile frequency ·······························································································································215
info-center logfile overwrite-protection ··············································································································216
info-center logfile size-quota·······························································································································217
info-center logfile switch-directory ·····················································································································217
info-center loghost ···············································································································································218
info-center loghost source ···································································································································219
info-center monitor channel ································································································································220
info-center snmp channel····································································································································221
info-center source ················································································································································221
info-center synchronous ······································································································································223
info-center syslog channel ··································································································································224
info-center timestamp ··········································································································································225
info-center timestamp loghost·····························································································································226
info-center trapbuffer···········································································································································227
logfile save···························································································································································228
reset logbuffer······················································································································································228
reset trapbuffer·····················································································································································228
terminal debugging·············································································································································229
terminal logging ··················································································································································229
terminal monitor···················································································································································230
terminal trapping·················································································································································231
Flow logging configuration commands ················································································································· 232
display userlog export ········································································································································232
reset userlog flow export ····································································································································233
reset userlog flow logbuffer································································································································234
userlog flow export host ·····································································································································235
userlog flow export host ipv6·····························································································································236
userlog flow export source-ip ·····························································································································237
userlog flow export timestamps localtime·········································································································238
userlog flow export version ································································································································239
userlog flow syslog··············································································································································239
sFlow configuration commands······························································································································ 241
display sflow ························································································································································241
sflow agent···························································································································································242
sflow collector ······················································································································································243
sflow counter interval ··········································································································································244
sflow counter collector ········································································································································245
sflow flow collector··············································································································································245
sflow flow max-header········································································································································246
sflow sampling-mode ··········································································································································246
sflow sampling-rate ·············································································································································247
sflow source ·························································································································································248
Gateway mode configuration commands············································································································· 249
display gateway-mode forwarding-cache ········································································································249
gateway-mode ·····················································································································································251
reset gateway-mode forwarding-cache statistics······························································································252
1
Ping, tracert, and system debugging
commands
Ping and tracert commands
ping
Use ping to verify whether the destination in an IP network is reachable, and to display the related
statistics.
Syntax
ping [ ip ] [ -a source-ip | -c count | -f | -h ttl | -i interface-type interface-number | -m interval | -n | -p
pad | -q | -r | -s packet-size | -t timeout | -tos tos | -v | { -mt topology-name | -vpn-instance
vpn-instance-name } ] * host
Views
Any view
Default command 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 parameter is not provided, 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 ranges from 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 ranges from 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 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.
-m interval: Specifies the interval (in milliseconds) to send an ICMP echo request, which ranges from 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.
2
-n: Disables domain name resolution for the host argument. When this keyword is not provided, if the
host argument represents the host name of the destination, 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,
in the range 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: Presence of this keyword indicates that only statistics are displayed. Absence of this keyword
indicates that all information is displayed.
-r: Records routing information. If this keyword is not provided, routes are not recorded.
-s packet-size: Specifies length (in bytes) of an ICMP echo request, which ranges from 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 ranges from 0 to 65535 and defaults to 2000.
-tos tos: Specifies the ToS value of an echo request, which ranges from 0 to 255 and defaults to 0.
-v: Displays non ICMP echo reply received. If this keyword is not provided, the system does not display
non ICMP echo reply.
-mt topology-name: Specifies the topology name, which is a case-sensitive string of 1 to 31 characters.
To verify whether two nodes of a topology can reach each other, specify the name of the topology to
which the two nodes belong. You cannot specify both a topology name and an MPLS L3VPN at the same
time.
-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: IP address or host name (a string of 1 to 255 characters) of the destination.
Usage guidelines
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. For more information about
DNS, see Layer 3—IP Services Configuration Guide.
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
3
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 was reachable.
•All ICMP echo requests sent by the source 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 was reachable.
•All ICMP echo requests sent by the source 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 topology voice is reachable.
<Sysname> ping -mt voice 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
4
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 topology voice was reachable.
•All ICMP echo requests sent by the source 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
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
5
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 was reachable.
•T h e r o u te 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.
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—Number of data bytes in the ICMP reply.
•Sequence—Packet sequence, used to determine whether a segment is
lost, disordered or repeated.
•ttl—TTL value in the ICMP reply.
•time—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
Use ping ipv6 to verify whether an IPv6 address is reachable, and display the corresponding statistics.
Syntax
ping ipv6 [ -a source-ipv6 | -c count | -m interval | -s packet-size | -t timeout | -vpn-instance
vpn-instance-name ] * host [ -i interface-type interface-number ]
6
Views
Any view
Default command 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 parameter is not provided, the source IPv6 address of an ICMP
echo request is the IPv6 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 ranges from 1 to
4294967295 and defaults to 5.
-m interval: Specifies the interval (in milliseconds) to send an ICMPv6 echo reply, which ranges from 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.
-s packet-size: Specifies length (in bytes) of an ICMPv6 echo request, which ranges from 20 to 8100 and
defaults to 56.
-t timeout: Specifies the timeout value (in milliseconds) of an ICMPv6 echo reply, which ranges from 0 to
65535 and defaults to 2000.
host: IPv6 address or host name of the destination, which is 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 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.
Usage guidelines
To use the name of the destination host to perform the ping IPv6 operation, 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
7
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
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 the description on other fields, see Table 1.
tracert
Use tracert to trace the path the packets traverse from source to destination.
Syntax
tracert [ -a source-ip | -f first-ttl |-m max-ttl | -p port | -q packet-number | { -mt topology-name |
-vpn-instance vpn-instance-name } |-w timeout ] * host
Views
Any view
Default command level
0: Visit level
8
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 parameter is not provided, 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 ranges from 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 ranges
from 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 ranges from 1 to 65535 and defaults to
33434. You do not need to modify this parameter.
-q packet-number: Specifies the number of probe packets sent each time, which ranges from 1 to 65535
and defaults to 3.
-mt topology-name: Specifies the topology name, which is a case-sensitive string of 1 to 31 characters.
-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 ranges from 1 to
65535 milliseconds and defaults to 5000 milliseconds.
host: IP address or host name (a string of 1 to 255 characters) of the destination.
Usage guidelines
After having identified network failure with the ping command, use the tracert command to determine the
failed nodes.
Output from the tracert command includes IP 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
# Display the path 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> 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
9
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.
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.
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
Use tracert ipv6 to view the path the IPv6 packets traverse from source to destination.
Syntax
tracert ipv6 [ -f first-ttl | -m max-ttl | -p port | -q packet-number | -vpn-instance vpn-instance-name | -w
timeout ] * host
Views
Any view
Default command level
0: Visit level
Parameters
-f first-ttl: Specifies the first TTL, or, the allowed number of hops for the first packet. It ranges from 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 ranges
from 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 ranges from 1 to 65535 and defaults to
33434. It is unnecessary to modify this parameter.
-q packet-number: Specifies the number of probe packets sent each time, which ranges from 1 to 65535
and defaults to 3.
10
-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 ranges from 1 to
65535 milliseconds and defaults to 5000 milliseconds.
host: IPv6 address or host name of the destination, which is a string of 1 to 46 characters.
Usage guidelines
In the event of network failure, you can use the tracert 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 description on the fields in the above output, see Table 2.
System debugging commands
debugging
Use debugging to enable the debugging of a specific module.
Use undo debugging to disable the debugging of a specific module.
Syntax
debugging { all [ timeout time ] | module-name [ option ] }
undo debugging { all | module-name [ option ] }
Default
Debugging functions for all modules are disabled.
Views
User view
Default command level
3: System level
11
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 ranges
from 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.
Usage guidelines
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 command 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 configuration commands."
Examples
# Enable IP packet debugging.
<Sysname> debugging ip packet
Related commands
display debugging
display debugging
Use display debugging to display enabled debugging functions.
Syntax
display debugging [ interface interface-type interface-number ] [module-name ] [ |{ begin | exclude |
include } regular-expression ]
Views
Any view
Default command level
1: Monitor level
Parameters
interface interface-type interface-number: Displays the debugging settings of the specified interface,
where interface-type interface-number 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.
12
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.
Examples
# Display all enabled debugging functions.
<Sysname> display debugging
IP packet debugging is on
Related commands
debugging
Other manuals for SR6600 SPE-FWM
13
This manual suits for next models
1
Table of contents
Other H3C Network Router manuals
H3C
H3C AR19 Series User manual
H3C
H3C SR6608 User manual
H3C
H3C MSR810 Installation manual
H3C
H3C RA100 User manual
H3C
H3C SR8800-X Operating and maintenance manual
H3C
H3C MSR 5600 Operating and maintenance manual
H3C
H3C S3100-52P User manual
H3C
H3C MSR 30-16 Manual
H3C
H3C H3C S3600 Series User manual
H3C
H3C AR 18-22-24 User manual
H3C
H3C MSR 2600 Operating and maintenance manual
H3C
H3C RA200 User manual
H3C
H3C MSR 20 Series User manual
H3C
H3C MSR 5660 Use and care manual
H3C
H3C SR6600 SPE-FWM Installation manual
H3C
H3C H3C S3600 Series Installation instructions
H3C
H3C CR16000-F User manual
H3C
H3C SR8800-X User manual
H3C
H3C SR6602-X1 User manual
H3C
H3C SR6604 User manual
