H3C S5120-HI Series User manual

H3C S5120-HI Switch Series
Layer 3 - IP Routing Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 5101
Document version: 6W101-20120427

Copyright © 2011-2012, 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, , Aolynk, , H3Care,
, TOP G, , IRF, NetPilot, Neocean, NeoVTL,
SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT,
XGbus, N-Bus, TiGem, InnoVision 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.

Preface
The H3C S5120-HI documentation set includes 10 configuration guides, which describe the software
features for the H3C S5120-HI Switch Series Release 5101, and guide you through the software
configuration procedures. These configuration guides also provide configuration examples to help you
apply software features to different network scenarios.
The Layer 3 – IP Routing Configuration Guide describes routing fundamentals and static routing
configuration.
This preface includes:
•Audience
•Conventions
•About the S5120-HI documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the S5120-HI Switch Series
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.

Convention Descri
p
tion
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Descri
p
tion
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
Convention Descri
p
tion
WARNING An alert that calls attention to important information that if not understood or followed can
result in personal injury.
CAUTION An alert that calls attention to important information that if not understood or followed can
result in data loss, data corruption, or damage to hardware or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
About the S5120-HI documentation set
The H3C S5120-HI documentation set includes:
Documents Pur
p
oses
Product descri
p
tion and s
p
ecifications
Marketing brochure Describe product specifications and benefits.
Technology white papers Provide an in-depth description of software features and
technologies.

Documents Pur
p
oses
Hardware s
p
ecifications and installation
Compliance and safety manual
CE DOCs
Provide regulatory information and the safety instructions that must be
followed during installation.
Installation quick start Guides you through initial installation and setup procedures to help
you quickly set up your device.
Installation guide Provides a complete guide to switch installation and specifications.
LSPM1FAN and LSPM1FANB
Installation Manual
Describes the appearances, specifications, installation, and removal
of the pluggable fan modules available for the products.
PSR150-A [ PSR150-D ] Power
Modules User Manual
Describe the specifications, installation, and replacement of hot
swappable 150W power modules.
RPS Ordering Information for H3C
Low-End Ethernet Switches Helps you order RPSs for switches that can work with an RPS.
User manuals for RPSs Describe the specifications, installation, and replacement of RPSs.
User manuals for interface cards Describe the specifications, installation, and replacement of
expansion interface cards.
H3C Low End Series Ethernet Switches
Pluggable Modules Manual Describes the specifications of pluggable transceiver modules.
Pluggable SFP[SFP+][XFP] Transceiver
Modules Installation Guide
Describe the installation, and replacement of SFP/SFP+/XFP
transceiver modules.
Software confi
g
uration
Configuration guides Describe software features and configuration procedures.
Command references Provide a quick reference to all available commands.
O
p
erations and maintenance
H3C Series Ethernet Switches Login
Password Recovery Manual Helps you deal with switch login password loss.
Release notes
Provide information about the product release, including the version
history, hardware and software compatibility matrix, version
upgrade information, technical support information, and software
upgrading.
Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies, as well as solutions.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.

Technical support
[e-mail]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [email protected].
We appreciate your comments.

i
Contents
IP routing basics ··························································································································································· 1
IP routing overview ···························································································································································1
Routing table·····························································································································································1
Routing preference ···················································································································································2
Route backup ····························································································································································2
Displaying and maintaining a routing table ··················································································································3
Static routing configuration ········································································································································· 4
Introduction ········································································································································································4
Static route ································································································································································4
Default route······························································································································································4
Static route configuration items·······························································································································4
Configuring a static route·················································································································································5
Configuration prerequisites ·····································································································································5
Configuration procedure ·········································································································································5
Displaying and maintaining static routes ·······················································································································6
Static route configuration examples································································································································6
Basic static route configuration example ···············································································································6
IPv6 static routing configuration·································································································································· 9
Introduction to IPv6 static routing ····································································································································9
Features of IPv6 static routes ···································································································································9
Default IPv6 route ·····················································································································································9
Configuring an IPv6 static route ······································································································································9
Configuration prerequisites ·····································································································································9
Configuration procedure ·········································································································································9
Displaying and maintaining IPv6 static routes············································································································ 10
IPv6 static routing configuration example ··················································································································· 10
Index ···········································································································································································13

1
IP routing basics
NOTE:
The types of interfaces that appear in any figures other than the network diagrams for configuration
examples are for illustration only. Some of them might be unavailable on your switch.
IP routing overview
Upon receiving a packet, a router determines the optimal route based on the destination address and
forwards the packet to the next router in the path. When the packet reaches the last router, it then
forwards the packet to the destination host.
Routing provides the path information that guides the forwarding of packets.
Routes can be divided into the following categories by destination:
•Network route—The destination is a network. The subnet mask is less than 32 bits.
•Host route—The destination is a host. The subnet mask is 32 bits.
Routes can be divided into the following types based on whether the destination is directly connected to
the router:
•Direct routes—The destination is directly connected to the router.
•Indirect routes—The destination is not directly connected to the router.
Routing table
Introduction to routing table
A router selects optimal routes from the routing table, and sends them to the forwarding information base
(FIB) table to guide packet forwarding. Each router maintains a routing table and a FIB table.
Routes in a routing table can be divided into the following categories by origin:
•Direct routes—Routes discovered by data link protocols, also known as “interface routes”
•Static routes—Routes manually configured. Static routes are easy to configure and require less
system resources. They work well in small and stable networks. Static routes cannot adjust to
network changes. You must manually configure the routes again whenever the network topology
changes.
•Dynamic routes—Routes discovered dynamically by routing protocols
Each entry in the FIB table specifies a physical interface that packets destined for a certain address
should go out to reach the next hop—the next router—or the directly connected destination.
NOTE:
For more information about the FIB table, see
Layer 3—IP Services Configuration Guide .
Routing table information
Display the brief information of a routing table by using the display ip routing-table command.

2
For example:
<Sysname> display ip routing-table
Routing Tables: Public
Destinations : 7 Routes : 7
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.0/24 Direct 0 0 1.1.1.1 Vlan11
2.2.2.0/24 Static 60 0 12.2.2.2 Vlan12
…(Part of the output information is omitted)
A route entry includes the following key items:
•Destination—Destination IP address or destination network
•Mask—The network mask specifies, in company with the destination address, the address of the
destination network. A logical AND operation between the destination address and the network
mask yields the address of the destination network. For example, if the destination address is
129.102.8.10 and the mask 255.255.0.0, the address of the destination network is 129.102.0.0. A
network mask is made up of a certain number of consecutive 1s. It can be expressed in dotted
decimal format or by the number of the 1s.
•Pre—Preference of the route. Among routes to the same destination, the one with the highest
preference is optimal.
•Cost—When multiple routes to a destination have the same preference, the one with the smallest
cost becomes the optimal route.
•NextHop—Specifies the IP address of the next hop
•Interface—Specifies the interface through which a matching IP packet is to be forwarded
Routing preference
Different routing protocols can find different routes to the same destination. However, not all of those
routes are optimal. For route selection, direct routes, and static routes are assigned different preferences.
The route with the highest preference is preferred.
The preference of a direct route is always 0 and cannot be changed. You can manually configure
preferences for any other route type. Each static route can be configured with a different preference. The
following table lists the types of routes and the default preferences. The smaller the preference value, the
higher the preference.
Routing approach Preference
Direct route 0
Static route 60
Route backup
Route backup can help improve network reliability. With route backup, you can configure multiple routes
to the same destination, expecting the one with the highest preference to be the main route and all the
rest backup routes.
Under normal circumstances, packets are forwarded through the main route. When the link fails, the
route with the highest preference among the backup routes is selected to forward packets. When the link

3
recovers, the route selection process is performed again and the main route is selected again to forward
packets.
Displaying and maintaining a routing table
To do… Use the command… Remarks
Display information about the
routing table
display ip routing-table [ verbose ] [ |
{ begin |exclude |include }
regular-expression ]
Available in any view
Display information about routes to
the specified destination
display ip routing-table ip-address [ mask
|mask-length ] [ longer-match ]
[ verbose ] [ |{ begin | exclude |
include } regular-expression ]
Available in any view
Display information about routes
with destination addresses in the
specified range
display ip routing-table ip-address1
{ mask |mask-length } ip-address2 { mask
|mask-length } [ verbose ] [ |{ begin |
exclude | include } regular-expression ]
Available in any view
Display routes of a routing protocol
display ip routing-table protocol protocol
[ inactive | verbose ] [ |{ begin | exclude
| include } regular-expression ] [ |{ begin
| exclude | include } regular-expression ]
[ |{ begin | exclude | include }
regular-expression ]
Available in any view
Display statistics about the routing
table
display ip routing-table statistics [ |
{ begin | exclude | include }
regular-expression ]
Available in any view
Clear statistics for the routing table reset ip routing-table statistics protocol
{protocol |all }Available in user view
Display IPv6 routing table
information
display ipv6 routing-table [ verbose ] [ |
{ begin | exclude | include }
regular-expression ]
Available in any view
Display routing information for a
specified destination IPv6 address
display ipv6 routing-table ipv6-address
prefix-length [ longer-match ] [ verbose ]
[ |{ begin | exclude | include }
regular-expression ]
Available in any view
Display IPv6 routing information
for an IPv6 address range
display ipv6 routing-table ipv6-address1
prefix-length1 ipv6-address2
prefix-length2 [ verbose ] [ |{ begin |
exclude | include } regular-expression ]
Available in any view
Display IPv6 routing information of
a routing protocol
display ipv6 routing-table protocol
protocol [ inactive | verbose ] [ |{ begin
| exclude | include } regular-expression ]
Available in any view
Display IPv6 routing statistics
display ipv6 routing-table statistics [ |
{ begin | exclude | include }
regular-expression ]
Available in any view
Clear specified IPv6 routing
statistics
reset ipv6 routing-table statistics protocol
{ protocol |all } Available in user view

4
Static routing configuration
Introduction
Static route
Static routes are manually configured. If a network’s topology is simple, you only need to configure static
routes for the network to work properly. The proper configuration and usage of static routes can improve
network performance and ensure bandwidth for important network applications.
The disadvantage of using static routes is that they cannot adapt to network topology changes. If a fault
or a topological change occurs in the network, the relevant routes will be unreachable and the network
breaks. When this happens, the network administrator must modify the static routes manually.
Default route
Without a default route, a packet that does not match any routing entries is discarded.
A default route is used to forward packets that do not match any routing entry. The network administrator
can configure a default route with both the destination and mask being 0.0.0.0. The router forwards any
packet whose destination address fails to match any entry in the routing table to the next hop of the
default static route.
Static route configuration items
Before configuring a static route, you must know the following concepts:
1. Destination address and mask
In the ip route-static command, an IPv4 address is in dotted decimal format. A mask can be either in
dotted decimal format or in the form of mask length—the number of consecutive 1s in the mask.
2. Output interface and next hop address
When you configure a static route, specify either the output interface, next hop address, or both
depending on the specific occasion. The next hop address cannot be a local interface IP address;
otherwise, the route configuration will not take effect.
Each route lookup operation has to find the next hop to resolve the destination link layer address.
When specifying the output interface, observe the following rules:
•If the output interface is a Null 0 interface, no next hop address is required.
•If you specify a broadcast interface (such as ar VLAN interface) as the output interface, you must
specify the corresponding next hop for the output interface.
3. Other attributes
You can configure different priorities for different static routes so that route management policies can be
more flexible. For example, specifying different priorities for different routes to the same destination
enables route backup.

5
Configuring a static route
Configuration prerequisites
Before configuring a static route, complete the following tasks:
•Configure the physical parameters for related interfaces
•Configure the link-layer attributes for related interfaces
•Configure the IP addresses for related interfaces
Configuration procedure
Follow these steps to configure a static route:
To do… Use the command…
Remarks
Enter system view system-view —
Configure a static route
ip route-static dest-address { mask | mask-length }
{ next-hop-address [ track track-entry-number ] |
interface-type interface-number [ next-hop-address ] }
[ preference preference-value ] [ permanent ] [ description
description-text ]
Required
By default, preference
for static routes is 60,
and no description
information is
configured.
Do not specify the
permanent and track
keywords
simultaneously.
If the outgoing
interface is down, the
permanent static route
is still active.
Configure the default
preference for static
routes
ip route-static default-preference default-preference-value Optional
60 by default
NOTE:
•When you configure a static route, the static route does not take effect if you specify the next hop address
first and then configure it as the IP address of a local interface, such as VLAN interface.
•If you do not specify the preference when you configure a static route, the default preference will be
used. Reconfiguring the default preference applies only to newly created static routes.
•If the destination IP address and mask are both configured as 0.0.0.0 with the ip route-static command,
then the route is the default route.
•For detailed information about track, see
High Availability Configuration Guide .

6
Displaying and maintaining static routes
To do… Use the command… Remarks
Display information of static routes
display ip routing-table protocol static [ inactive |
verbose ] [ |{ begin | exclude | include }
regular-expression ]
Available in any
view
Delete all the static routes delete static-routes all Available in
system view
NOTE:
For more information about the display ip routing-table protocol static
[ inactive | verbose ] [ |{ be
g
in
| exclude | include }
regular-expression ] command, see Layer 3—IP Routing Command Reference .
Static route configuration examples
Basic static route configuration example
Network requirements
The IP addresses and masks of the switches and hosts are shown in Figure 1. Static routes are required for
interconnection between any two hosts.
Figure 1 Network diagram
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown)
2. Configure static routes.
# Configure a default route on Switch A.
<SwitchA> system-view
[SwitchA] ip route-static 0.0.0.0 0.0.0.0 1.1.4.2
# Configure two static routes on Switch B.
<SwitchB> system-view
[SwitchB] ip route-static 1.1.2.0 255.255.255.0 1.1.4.1

7
[SwitchB] ip route-static 1.1.3.0 255.255.255.0 1.1.5.6
# Configure a default route on Switch C
<SwitchC> system-view
[SwitchC] ip route-static 0.0.0.0 0.0.0.0 1.1.5.5
3. Configure the hosts.
The default gateways for hosts A, B, and C are 1.1.2.3, 1.1.6.1 and 1.1.3.1, respectively. The configuration
procedure is not shown.
4. Display the configuration.
# Display the IP routing table of Switch A.
[SwitchA] display ip routing-table
Routing Tables: Public
Destinations : 7 Routes : 7
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/0 Static 60 0 1.1.4.2 Vlan500
1.1.2.0/24 Direct 0 0 1.1.2.3 Vlan300
1.1.2.3/32 Direct 0 0 127.0.0.1 InLoop0
1.1.4.0/30 Direct 0 0 1.1.4.1 Vlan500
1.1.4.1/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
# Display the IP routing table of Switch B.
[SwitchB] display ip routing-table
Routing Tables: Public
Destinations : 10 Routes : 10
Destination/Mask Proto Pre Cost NextHop Interface
1.1.2.0/24 Static 60 0 1.1.4.1 Vlan500
1.1.3.0/24 Static 60 0 1.1.5.6 Vlan600
1.1.4.0/30 Direct 0 0 1.1.4.2 Vlan500
1.1.4.2/32 Direct 0 0 127.0.0.1 InLoop0
1.1.5.4/30 Direct 0 0 1.1.5.5 Vlan600
1.1.5.5/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
1.1.6.0/24 Direct 0 0 1.1.6.1 Vlan100
1.1.6.1/32 Direct 0 0 127.0.0.1 InLoop0
# Use the ping command on Host B to check the reachability of Host A, assuming Windows XP runs on
the two hosts.

8
C:\Documents and Settings\Administrator>ping 1.1.2.2
Pinging 1.1.2.2 with 32 bytes of data:
Reply from 1.1.2.2: bytes=32 time=1ms TTL=255
Reply from 1.1.2.2: bytes=32 time=1ms TTL=255
Reply from 1.1.2.2: bytes=32 time=1ms TTL=255
Reply from 1.1.2.2: bytes=32 time=1ms TTL=255
Ping statistics for 1.1.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
# Use the tracert command on Host B to check the reachability of Host A.
C:\Documents and Settings\Administrator>tracert 1.1.2.2
Tracing route to 1.1.2.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 1.1.6.1
2 <1 ms <1 ms <1 ms 1.1.4.1
3 1 ms <1 ms <1 ms 1.1.2.2
Trace complete.

9
IPv6 static routing configuration
Introduction to IPv6 static routing
Static routes are manually configured. They work well in simple networks. Proper configuration and use
can improve network performance and ensure enough bandwidth for important applications.
However, static routes also have limitations. Any topology changes require manual configuration and
modification to the relevant static routes.
Features of IPv6 static routes
Similar to IPv4 static routes, IPv6 static routes work well in simple IPv6 network environments.
Their major difference lies in the destination and next hop addresses. IPv6 static routes use IPv6
addresses, whereas IPv4 static routes use IPv4 addresses.
Default IPv6 route
An IPv6 static route with a destination prefix of ::/0 is a default IPv6 route. The default route is used to
forward packets that match no specific routes in the routing table.
Configuring an IPv6 static route
In small IPv6 networks, IPv6 static routes can be used to forward packets. In comparison to dynamic
routes, it helps to save network bandwidth.
Configuration prerequisites
Before configuring an IPv6 static route, complete the following tasks:
•Configure parameters for the related interfaces
•Configure link layer attributes for the related interfaces
•Enable IPv6 packet forwarding
•Ensure the neighboring nodes can reach each other
Configuration procedure
Follow these steps to configure an IPv6 static route:
To do… Use the commands…
Remarks
Enter system view system-view —

10
To do… Use the commands… Remarks
Configure an IPv6 static route
ipv6 route-static ipv6-address prefix-length
{ interface-type interface-number
[ next-hop-address ] | next-hop-address }
[ preference preference-value ]
Required
The default
preference of IPv6
static routes is 60.
NOTE:
If you specify a broadcast interface, such as a VLAN interface, as the output interface for a static
route, you must specify the next hop address.
Displaying and maintaining IPv6 static routes
To do… Use the command… Remarks
Display IPv6 static route
information
display ipv6 routing-table protocol
static [ inactive | verbose ] [ |
{ begin | exclude | include }
regular-expression ]
Available in any view
Remove all IPv6 static routes delete ipv6 static-routes all Available in system view
NOTE:
•Using the undo ipv6 route-static command can delete a single IPv6 static route. Using the
delete ipv6 static-routes all command deletes all IPv6 static routes including the default route.
•For more information about the display ipv6 routing-table protocol static [ inactive | verbose ]
[ |{ begin | exclude | include }
regular-expression ] command, see Layer 3—IP Routing
Command Reference
.
IPv6 static routing configuration example
Network requirements
As shown in Figure 2, configure IPv6 static routes so that hosts can reach one another.

11
Figure 2 Network diagram
Configuration procedure
1. Configure the IPv6 addresses for all VLAN interfaces. (Details not shown)
2. Configure IPv6 static routes.
# Configure a default IPv6 static route on Switch A.
<SwitchA> system-view
[SwitchA] ipv6
[SwitchA] ipv6 route-static :: 0 4::2
# Configure two IPv6 static routes on Switch B.
<SwitchB> system-view
[SwitchB] ipv6
[SwitchB] ipv6 route-static 1:: 64 4::1
[SwitchB] ipv6 route-static 3:: 64 5::1
# Configure a default IPv6 static route on Switch C.
<SwitchC> system-view
[SwitchC] ipv6
[SwitchC] ipv6 route-static :: 0 5::2
3. Configure the IPv6 addresses and gateways for hosts.
Configure the IPv6 addresses for all the hosts based on the network diagram, configure the default
gateway of Host A as 1::1, Host B as 2::1, and Host C as 3::1.
4. Verify the configuration.
# Display the IPv6 routing table of Switch A.
[SwitchA] display ipv6 routing-table
Routing Table :
Destinations : 5 Routes : 5
Destination : :: Protocol : Static
NextHop : 4::2 Preference : 60
Interface : Vlan-interface200 Cost : 0
Destination : ::1/128 Protocol : Direct
NextHop : ::1 Preference : 0

12
Interface : InLoop0 Cost : 0
Destination : 1::/64 Protocol : Direct
NextHop : 1::1 Preference : 0
Interface : Vlan-interface100 Cost : 0
Destination : 1::1/128 Protocol : Direct
NextHop : ::1 Preference : 0
Interface : InLoop0 Cost : 0
Destination : FE80::/10 Protocol : Direct
NextHop : :: Preference : 0
Interface : NULL0 Cost : 0
# Verify the connectivity with the ping command.
[SwitchA] ping ipv6 3::1
PING 3::1 : 56 data bytes, press CTRL_C to break
Reply from 3::1
bytes=56 Sequence=1 hop limit=254 time = 63 ms
Reply from 3::1
bytes=56 Sequence=2 hop limit=254 time = 62 ms
Reply from 3::1
bytes=56 Sequence=3 hop limit=254 time = 62 ms
Reply from 3::1
bytes=56 Sequence=4 hop limit=254 time = 63 ms
Reply from 3::1
bytes=56 Sequence=5 hop limit=254 time = 63 ms
--- 3::1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 62/62/63 ms

13
Index
C D I S
C
Configuring a static route,5
Configuring an IPv6 static route,9
D
Displaying and maintaining a routing table,3
Displaying and maintaining IPv6 static routes,10
Displaying and maintaining static routes,6
I
Introduction,4
Introduction to IPv6 static routing,9
IP routing overview,1
IPv6 static routing configuration example,10
S
Static route configuration examples,6