All rights reserved. Printed in the USA. September 1997.
The information in this document is subject to change without notice. The statements, configurations, technical data,
and recommendations in this document are believed to be accurate and reliable, but are presented without express or
implied warranty . Users must tak e full responsibility for their applications of an y products specified in this document.
The information in this document is proprietary to Bay Networks, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance
with the terms of that license. A summary of the Software License is included in this document.
Trademarks
ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, PPX, and Bay Networks are registered
trademarks and Advanced Remote Node, ANH, ARN, ASN, Bay•SIS, BayStack, BayStream, BCNX, BLNX,
IP AutoLearn, SN, SPEX, Switch Node, System 5000, Bay Networks Press, and the Bay Networks logo are
trademarks of Bay Networks, Inc.
All other trademarks and registered trademarks are the property of their respective owners.
Restricted Rights Legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in
the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the
right to make changes to the products described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
In addition, the program and information contained herein are licensed only pursuant to a license agreement that
contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed
by third parties).
Bay Networks, Inc. Software License Agreement
NOTICE:
installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement).
ii
Please carefully read this license agreement before copying or using the accompanying software or
118428-A Rev. A
BY COPYING OR USING THE SOFTWARE, YOU A CCEPT ALL OF THE TERMS AND CONDITIONS OF THIS
LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER
WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and
conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a
credit for the full purchase price
1. License Grant.
nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single
authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup
purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in
support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend
to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other
Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software
License Agreement that accompanies such software and upon payment by the end user of the applicable license fees
for such software.
2. Restrictions on use; reservation of rights.
Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any
revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any
copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use
for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user
manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or
transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and
its licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise
disclose to any third party the Software, or any information about the operation, design, performance, or
implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however,
Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s f acility,
provided they have agreed to use the Software only in accordance with the terms of this license.
3. Limited warranty.
installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function
substantially as described in its accompanying user manual during its warranty period, which begins on the date
Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole
remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be
included in a future Software release. Bay Networks further warrants to Licensee that the media on which the
Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days
from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is
returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not
apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility
for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained
from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the
Licensee’s requirements, b) that the Software will operate in the hardw are or softw are combinations that the Licensee
may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the
operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot
be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered,
except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product,
resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE
FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL
OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF
MERCHANT ABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of
its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or
altered files, data, or programs.
4. Limitation of liability.
COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR
Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal,
The Software and user manuals are protected under copyright laws.
Bay Networks warrants each item of Software, as delivered by Bay Networks and properly
IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY
118428-A Rev. A
iii
PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN
IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT
SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT
EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.
5. Government Licensees.
by or on behalf of the United States Government. The Software and documentation are commercial products, licensed
on the open market at market prices, and were developed entirely at private expense and without the use of any U.S.
Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or
disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial
Computer Software––Restricted Rights clause of F AR 52.227-19 and the limitations set out in this license for civilian
agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.
6. Use of Software in the European Community.
European Community. If Licensee uses the Software within a country in the European Community, the Software
Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the
examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such
intended examination of the Software and may procure support and assistance from Bay Networks.
7. Term and termination.
Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the
Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information
shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if
Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason,
Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay
Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.
8. Export and Re-export.
or information without first obtaining any required export licenses or other governmental approvals. Without limiting
the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first
obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert
any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports
are restricted or embargoed under United States export control laws and regulations, or to any national or resident of
such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any
military end user or for any military end use, including the design, development, or production of any chemical,
nuclear, or biological weapons.
9. General.
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement
will be governed by the laws of the state of California.
Should you have any questions concerning this Agreement, contact Ba y Networks, Inc., 4401 Great America P arkway,
P.O. Box 58185, Santa Clara, California 95054-8185.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND
LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND
COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS
AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY
NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.
If any provision of this Agreement is held to be invalid or unenforceable by a court of competent
This provision applies to all Software and documentation acquired directly or indirectly
This provision applies to all Software acquired for use within the
This license is effective until terminated; however, all of the restrictions with respect to
Licensee agrees not to export, directly or indirectly, the Software or related technical data
iv
118428-A Rev. A
Contents
About This Guide
Before You Begin .............................................................................................................xvi
Figure 1-6.IPV6 Header and Extension Headers ....................................................1-11
118428-A Rev. A
ix
About This Guide
If you are responsible for configuring IPv6 and RIPv6, you need to read this
guide.
If you want toGo to
Learn about IPv6 concepts and servicesChapter
Start IPv6 services on the routerChapter 2
Configure and Customize IPv6Chapter 3
Configure and customize RIPv6Chapter 4
Obtain information about Site Manager parameters (this is the same
information you obtain using Site Manager online Help)
Appendix A
1
118428-A Rev. A
xi
Configuring IPv6 Services
.
.
Before You Begin
Before using this guide, you must complete the following procedures. For a new
router:
•Install the router (refer to the installation manual that came with your router).
•Connect the router to the network and create a pilot configuration file (see
Quick-Starting Routers, Configuring BayStack Remote Access
ASN Routers to a Network)
Make sure that you are running the latest version of Bay Networks® Site Manager
and router software. For instructions, see
7–11.xx to Version 12.00
Conventions
angle brackets (< >)Indicate that you choose the text to enter based on the
, or
.
Upgrading Routers from Version
.
description inside the brackets. Do not type the
brackets when entering the command.
ping
Example: if command syntax is
you enter
ping 192.32.10.12
<ip_address>
Connecting
,
bold text
Indicates text that you need to enter, command names,
and buttons in menu paths.
Example: Enter
Example: Use the
Example: ATM DXI > Interfaces >
wfsm &
dinfo
command.
PVCs
identifies the
PVCs button in the window that appears when you
select the Interfaces option from the ATM DXI menu.
brackets ([ ])Indicate optional elements. You can choose none, one,
or all of the options.
.
ellipsis pointsHorizontal (. . .) and verticalellipsis points indicate
()
omitted information.
italic text
Indicates variable values in command syntax
descriptions, new terms, file and directory names, and
book titles.
quotation marks (“ ”)Indicate the title of a chapter or section within a book.
xii
118428-A Rev. A
About This Guide
Acronyms
screen text
Indicates data that appears on the screen.
Example:
Set Bay Networks Trap Monitor Filters
separator ( > )Separates menu and option names in instructions and
internal pin-to-pin wire connections.
Example: Protocols > AppleTalk identifies the
AppleTalk option in the Protocols menu.
Example: Pin 7 > 19 > 20
vertical line (|)Indicates that you enter only one of the parts of the
command. The vertical line separates choices. Do not
type the vertical line when entering the command.
Example: If the command syntax is
show at routes
show at routes
AUIAttachment Unit Interface
BootPBootstrap Protocol
BRIBasic Rate Interface
CCITTInternational Telegraph and Telephone Consultative Committee
(now ITU-T)
CSMA/CDcarrier sense multiple access with collision detection
DLCMIData Link Control Management Interface
GUIgraphical user interface
HDLChigh-level data link control
IPInternet Protocol
ISDNIntegrated Services Digital Network
ISOInternational Organization for Standardization
ITU-TInternational Telecommunications Union-Telecommunications
(formerly CCITT)
LANlocal area network
MACmedia access control
MAUmedia access unit
MDI-Xmedia-dependent interface with crossover
NBMAnonbroadcast multi-access
nets
|
, you enter either
show at nets
or
, but not both.
118428-A Rev. A
xiii
Configuring IPv6 Services
OSIOpen Systems Interconnection
OSPFOpen Shortest Path First (Protocol)
PPPPoint-to-Point Protocol
SMDSswitched multimegabit data service
SNMPSimple Network Management Protocol
STPshielded twisted-pair
TCP/IPTransmission Control Protocol/Internet Protocol
TelnetTelecommunication Network
TFTPTrivial File Transfer Protocol
TPEtwisted-pair Ethernet
UTPunshielded twisted-pair
WANwide area network
Ordering Bay Networks Publications
To purchase additional copies of this document or other Bay Networks
publications, order by part number from Bay Networks Press™ at the following
numbers:
xiv
•Phone--U.S./Canada: 888-422-9773
•Phone--International: 510-490-4752
•FAX--U.S./Canada and International: 510-498-2609
The Bay Networks Press catalog is available on the World Wide Web at
support.baynetworks.com/Library/GenMisc
available on the World Wide Web at
support.baynetworks.com/Library/tpubs
. Bay Networks publications are
118428-A Rev. A
.
Bay Networks Customer Service
You can purchase a support contract from your Bay Networks distributor or
authorized reseller, or directly from Bay Networks Services. For information
about, or to purchase a Bay Networks service contract, either call your local Bay
Networks field sales office or one of the following numbers:
RegionTelephone numberFax number
About This Guide
United States and
Canada
Europe33-4-92-96-69-6633-4-92-96-69-96
Asia/Pacific61-2-9927-8888 61-2-9927-8899
Latin America561-988-7661561-988-7550
Information about customer service is also available on the World Wide Web at
support.baynetworks.com
How to Get Help
If you purchased a service contract for your Bay Networks product from a
distributor or authorized reseller, contact the technical support staff for that
distributor or reseller for assistance.
If you purchased a Bay Networks service program, call one of the following Bay
Networks Technical Solutions Centers:
800-2LANWAN; then enter Express
Routing Code (ERC) 290, when prompted,
to purchase or renew a service contract
978-916-8880 (direct)
.
978-916-3514
118428-A Rev. A
Technical Solutions Center Telephone numberFax number
Billerica, MA800-2LANWAN978-916-3514
Santa Clara, CA800-2LANWAN408-495-1188
Valbonne, France33-4-92-96-69-6833-4-92-96-69-98
Sydney, Australia61-2-9927-880061-2-9927-8811
Tokyo, Japan81-3-5402-018081-3-5402-0173
xv
Chapter 1
IPv6 Overview
This overview of IP Version 6 covers the following topics:
The IPv6 protocol defines the header used by IPv6 nodes (hosts and routers) to
deliver a data packet from a sender to one or more destinations.
The
address for a data packet. The header also includes a flow control field that an
IPv6 host can use to label packets that require special handling by IPv6 routers -for example, packets that require a real-time service.
IPv6 header
1-17
supplies a 128-bit source address and a 128-bit destination
118428-A Rev. A
1-17
Configuring IPv6 Services
IPv6 Addresses
An IPv6 address consists of 128 bits that identify an interface or a set of
interfaces. The address consists of two parts: an address prefix and an IPv6
interface ID. The first 3 bits of the address indicate the type of address that follows
-- a unicast address, for example.
igure 1-1 shows the basic parts of an IPv6 address.
F
Figure 1-1.128-Bit IPv6 Address Format
Address Prefix
The
are listed in the hierarchical order of the organizations that issue them.
•At the top of the hierarchy, international registries assign blocks of addresses
•TLAs allocate blocks of address to the
•An NLA that is a service provider further allocates its addresses to its
TLA and NLA addresses are part of the public Internet topology. SLA addresses
are part of private site-level topologies.
Type Address prefix
address pr efix
to
top-level aggregators
consists of one or more
(TLAs). TLA addresses provide the public transit
InterfaceID ( or Token )
aggregator addr esses
IPV0003A
. These addresses
points where long-haul service providers establish peer connections.
next-level aggregators
(NLAs), the
large Internet service providers and global corporate networks.
subscribers, the lowest-level aggregators, the
site-level aggregators
(SLAs).
1-18
118428-A Rev. A
Interface ID
The
interface ID
router). For stateless autoconfiguration (see “Address Autoconfiguration” on page
1-27), this ID is 64 bits long.
In IPv6 stateless autoconfiguration, the interface ID is derived by a formula that
uses the link layer 48-bit MAC address. (In most cases, the interface ID is a 64-bit
token that contains the 48-bit MAC address.) This means that to the extent that the
MAC address is unique, the IPv6 interface ID is unique.
If you configure tokens or MAC addresses (or both) manually, there need be no
relation between the MAC address and the token. A manually configured token
may also be longer or shorter than 64 bits.
Anycast Address
or
IPv6 Overview
token
is a unique number identifying an IPv6 node (a host or a
An IPv6
that share a common variable-length address prefix. A packet bearing an anycast
address is delivered to one node in the group.
Multicast Address
An IPv6
multicast address is delivered to all members of the group. (The function of IPv4
broadcast addresses has been superseded by IPv6 multicast addresses.)
igure 1-2 shows the format of an IPv6 multicast address.
F
8 bits4 bits4 bits
11111111
Figure 1-2.Multicast Address Format
A value of FF (11111111) in the 8 high-order bits of an IPv6 address indicates
that the address specifies a multicast group. The 4-bit
the group is permanent or transient. The 4 -bit
the group specified in the 112-bit
anycast address
multicast addres
flagsscopegroup ID
is a unicast address identifying a group of IPv6 nodes
s identifies a group of nodes. A packet bearing a
112 bits
IPV0001A
flags
field indicates whether
scope
field indicates the scope of
group ID
field.
118428-A Rev. A
1-19
Configuring IPv6 Services
IPv4-Compatible Address
The IPv4-compatible address, which includes an IPv4 address in the low-order 32
bits, is intended for IPv6 nodes that need to interoperate with IPv4 nodes.
igure 1-3 shows the format of an IPv4-compatible address.
F
0000 0000 0000 0000 0000 0000
Figure 1-3.IPv4-Compatible Unicast Address Format
Address Formats
The format for representing an IPv6 address is
n:n:n:n:n:n:n:n
n is the hexadecimal representation of 16 bits in the address. For example:
FF01:0:0:0:0:0:0:43
Each nonzero field must contain at least one numeral. W ithin a gi v en hexadecimal
field, however, leading 0s are not required.
Certain classes of IPv6 addresses commonly include multiple contiguous fields
containing hexadecimal 0. Our sample address includes five contiguous fields
containing 0. These fields can be represented by double colons (::). For example:
96 bits
32 bits
IPv4 address
IPV0002A
FF01::43
A double colon can also be used to compress the leading zero fields in a
hexadecimal address. A double colon can appear once in an address.
1-20118428-A Rev. A
Tunnels
IPv6 Overview
An IPv4-compatible address combines hexadecimal and decimal values as
follows:
x.x.x.x.x.x.d.d.d.d
x:x:x:x:x:x is a hexadecimal representation of the six high-order 16-bit pieces of
d.d.d.d
the address and
is a decimal representation of the four 8-bit pieces of the
address. For example:
0:0:0:0:0:0:13.1.68.3
or
::13.1.68.3
Tunneling is a forwarding technique in which a packet is encapsulated inside
another packet.
IPv6 supports two kinds of encapsulating tunnels: IPv4 tunnels and IPv6 tunnels.
In IPv4 tunneling, a router running both IPv6 and IPv4 encapsulates an IPv6
packet within an IPv4 packet. This technique allo ws IPv6 nodes in noncontiguous
IPv6 regions to forward messages through an intervening region of IPv4 nodes.
In IPv6 tunneling, a router running IPv6 encapsulates an IPv6 packet in another
IPv6 packet. This section covers the following topics:
A static tunnel -- also called a configured tunnel -- is a mechanism for forwarding
any IPv6 packet through an IPv4 region. F
an IPv4 interface on router C and an IPv4 interface on router D. (Note that routers
C and D are running both IPv4 and IPv6).
igure 1-4 shows a static tunnel between
IPv6
A
IPv6
B
Region 1
IPv6IPv6
Configured
IPv6
C
IPv4
IPV4 tunnel
with end points
IPv4
G
IPv4
I
IPv4
Region 2
IPv4
H
IPv4
J
Region 3
IPv6
E
IPv6
F
IPv6
D
IPv4
IP0042A
Figure 1-4.Configured IPv4 Static Tunnel
In Figure 1-4, for example, a user connected to router B in Region 1 sends a
packet addressed to a user on router F in Region 3. The following steps occur:
1. Router C receives the IPv6 packet and determines that it must be forwarded
out its tunnel interface.
1-22118428-A Rev. A
2. Router C encapsulates the IPv6 packet in an IPv4 header.
The source address in the IPv4 header is the IPv4 address of the local tunnel
interface on router C. The destination address is the IPv4 address of the
remote tunnel interface on router D.
3. Using the IPv4 header, intermediate IPv4 routers in Region 2 forward the
encapsulated packet through the IPv4 region to router D.
4. Router D decapsulates the packet (removing the IPv4 header) and forwards
the original IPv6 packet to router F.
After you have configured the IPv4 interfaces on the end point routers, the tunnel
becomes a permanent point-to-point link in the IPv6 topology.
Automatic IPv4 Tunnel
An automatic tunnel is a mechanism for forwarding unicast IPv6 packets that use
the IPv4-compatible address format. All routers in IPv6 re gions that use automatic
tunneling must run both IPv6 and IPv4.
IPv6 creates the tunnel dynamically as needed for the purpose of forwarding an
IPv6 packet through multiple IPv4 and IPv4/IPv6 routers.
IPv6 Overview
igure 1-5, for example, a user connected to router B in Region 1 wants to send
In F
an IPv6 packet to a user on router J in Region 3.
118428-A Rev. A1-23
Configuring IPv6 Services
IPv6
A
IPv4
IPv6
B
IPv4
Region 1
IPv6
C
IPv4
IPv6/V4
IPv6
D
IPv4
Automatic
IPV4 tunnel
with end points
IPv4
F
IPv4
E
Region 2
IPv4
IPv4
G
IPv6
H
IPv4
Region 3
IPv6
J
IPv4
IPv6
I
IPv4
IPv6/V4
IP0041A
Figure 1-5.Automatic IPv4 Tunnel
The following steps occur:
1.Router D receives the packet and determines that the next hop requires an
automatic tunnel.
2.Router D encapsulates the packet in an IPv4 header.
The source address in the IPv4 header is the IPv4 address of the local tunnel
interface on node D.
The destination address is the IPv4 address contained in the IPv4-compatible
IPv6 address. This is the address of an IPv4 interface on router J.
3.IPv4 routers in Region 2 forward the packet to Region 3.
4.IPv4/ IPv6 router in Region 3 forward the IPv4 packet to router J.
1-24118428-A Rev. A
5.Router J decapsulates the packet.
Note that unlike a configured tunnel, which is a permanent point-to-point link in
the IPv6 topology, an automatic tunnel is a dynamic mechanism, created by the
encapsulating end point for the purpose forwarding an IPv6 packet. After the
packet reaches its destination, the automatic tunnel no longer exists.
Semiautomatic IPv4 Tunnel
A semiautomatic tunnel acts as a static tunnel for outgoing traffic and as an
automatic (multipoint-to-point) tunnel for incoming traffic.
IPv6 Tunnels
Like an IPv4 tunnel, an IPv6 tunnel can be a static tunnel, an automatic tunnel, or
a semiautomatic tunnel.
Packet Forwarding
IPv6 forwards
IPv6 Overview
•Unicast packets not addressed to itself.
•Packets with predefined multicast addresses.
•Packets addressed to itself that include a routing source extension header. The
extension header specifies a list of one or more intermediate nodes that define
a path for the packet to follow through the network to its destination.
IPv6 processes packets that are addressed to itself (with the exception of packets
that contain a routing option extension header). IPv6 recognizes the following
addresses as identifying itself:
•A unicast address assigned to the router
•A loopback address used by a node to send an IPv6 datagram to itself
•An all-nodes or all-hosts multicast address
•An anycast address assigned to the router
118428-A Rev. A1-25
Configuring IPv6 Services
IPv6 Extension Headers
IPv6 extension headers describe processing options. Each extension header
contains a separate category of options. A packet can include zero or more
extension headers (F
igure 1-6).
Datalink
header
Figure 1-6.IPV6 Header and Extension Headers
IPv6
header
Ipv6 extension
headers
•••
Upper-layer
headers
User data
IP0046A
IPv6 examines the destination address in the main header of each packet it
receives to determine whether the router is the packet’s destination or an
intermediate node in the packet’s data path.
•If the router is the destination of the packet, IPv6 examines the header
extensions that contain options for destination processing.
•If the router is an intermediate node, IPv6 e xamines the header extensions that
contain forwarding options.
By examining only the extension headers that apply to the operations it performs,
IPv6 reduces the amount of time and processing resources required to process a
packet.
IPv6 defines the following extension headers:
•The source routing extension header contains a list of one or more
intermediate nodes that define a path for the packet to follow through the
network to its destination. The packet source creates this list. This function is
similar to IPv4 source routing options.
•The fragmentation extension header is used by an IPv6 source to send packets
larger than the size specified for the path MTU.
•The authentication extension header and the security encapsulation extension
header, used singly or together, provide security services for IPv6 datagrams.
1-26118428-A Rev. A
•The hop-by-hop extension header contains optional information that must be
examined by all intermediate IPv6 routers between the source and the
destination.
•The end-to-end extension header contains optional information that must be
examined by the destination node.
Neighbor Discovery
Neighbor discovery (ND) allows IPv6 nodes on the same link to discover link
layer addresses and to obtain and advertise various network parameters and
reachability information. ND combines the services provided for IPv4 by the
Address Resolution Protocol (ARP) and router discovery.
Address Autoconfiguration
Typically, to start the process of autoconfiguration, a node
•Self-configures a link-local address to use temporarily. The host can form this
address by adding a generic local address prefix to a unique token (typically,
the host’s IEE LAN interface address).
IPv6 Overview
•Sends out an ND message to the address to ensure that it is unique. If no ND
message comes back, the address is unique. If a message comes back
indicating that the link-local address is already in use, the host uses a different
token (for example, an administrative token or a randomly generated token).
•Uses the IPv6 multicast service to send out an ND router solicitation request,
using the new link-local address as a source address. Unlike the broadcast
ARPs of IPv4, ND multicast solicitations are not necessarily processed by all
nodes on the link. IPv6 defines several permanent multicast groups for finding
resources on a local node or link, including an all-routers group, an all-hosts
group, and a Dynamic Host Configuration Protocol (DHCP) server group.
Routers respond to the solicitation messages from hosts with a unique router
advertisement that includes prefix information indicating a valid range of
addresses for the subnet. Routers can also send these advertisements periodically
to local multicast groups, whether or not they receive solicitations.
Using the router advertisement message that it sends in response to a solicitation
from a host, an IPv6 router can control whether the host uses stateful or stateless
autoconfiguration.
118428-A Rev. A1-27
Configuring IPv6 Services
In stateful autoconfiguration, the host contacts a DHCP or similar address server,
which assigns an address from a manually administered list.
In stateless autoconfiguration, a host can automatically configure its own IPv6
address without the help of a stateful address server. The host uses the globally
valid address prefix information in the router advertisement message to create its
own IPv6 address. The host concatenates the valid prefix with its link layer
address (or a similar unique token) to create an IPv6 address.
RIPv6
RIPv6 -- the Routing Information Protocol for IPv6 -- is a distance-vector
protocol that enables IPv6 routers in the same autonomous system to exchange
routing information by means of periodic RIP updates. Routers transmit their own
RIPv6 updates to neighboring networks and listen for RIPv6 updates from the
routers on those neighboring networks. Routers use the information in the RIPv6
updates to keep their internal routing tables current. For RIPv6, the “best” path to
a destination is the shortest path (the path with the fewest hops). RIPv6 computes
distance as a metric, usually the number of hops (or routers) from the origin
network to the target network.
RIPv6 is described in Cha
1-28118428-A Rev. A
pter 4.
Starting IPv6
Before you can choose a protocol to run on the router, you must configure a circuit
that the protocol can use as an interface to an attached network. For information
and instructions, see Configuring Ethernet, FDDI, and Token Ring Services or Configuring WAN Line Services.
When you have successfully configured the circuit, the Select Protocols window
opens. Proceed as follows:
Chapter 2
Starting IPv6 Services
Site Manager Procedure
You do thisSystem responds
1. In the Select Protocols window, choose
IPv6.
2. Click on OK to accept default values for
IPv6 parameters.
The Configure Interfaces window opens.
You return to the Configuration Manager
window.
IPv6 is now configured on this interface and slot with default values for all global
and interface parameters. You customize IPv6 by modifying IPv6 parameters as
described in Cha
118428-A Rev. A2-1
pter 3.
Configuring IPv6 Services
Adding Neighbor Discovery to an IPv6 Interface
Use Site Manager to add Neighbor Discovery to an IPv6 interface as follows.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IPv6.The IPv6 menu opens.
3. Choose Neighbor Discovery.The List IPv6 Neighbor Discovery window
4. Choose Add.The Values Selection window opens.
5. Choose the IPv6 interface to which you
want to add Neighbor Discovery, and click
on OK.
6. Click on Apply and Done to accept def ault
values for Neighbor Discovery
parameters.
To customize the Neighbor Discovery values, go to pa
Adding RIPv6 to an IPv6 Interface
Use Site Manager to add RIPv6 to an IPv6 interface as follows.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.