![]() |
Interface and Hardware Component Configuration Guide, Cisco IOS Release 15S
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
IPv6 over IPv4 GRE Tunnels
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Contents
IPv6 over IPv4 GRE TunnelsLast Updated: November 26, 2012
GRE tunnels are links between two points, with a separate tunnel for each link. The tunnels are not tied to a specific passenger or transport protocol, but in this case carry IPv6 as the passenger protocol with the GRE as the carrier protocol and IPv4 or IPv6 as the transport protocol. Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Information About IPv6 over IPv4 GRE TunnelsOverlay Tunnels for IPv6Overlay tunneling encapsulates IPv6 packets in IPv4 packets for delivery across an IPv4 infrastructure (a core network or the figure below). By using overlay tunnels, you can communicate with isolated IPv6 networks without upgrading the IPv4 infrastructure between them. Overlay tunnels can be configured between border devices or between a border device and a host; however, both tunnel endpoints must support both the IPv4 and IPv6 protocol stacks. IPv6 supports the following types of overlay tunneling mechanisms:
Use the table below to help you determine which type of tunnel that you want to configure to carry IPv6 packets over an IPv4 network.
Individual tunnel types are discussed in detail in this document. We recommend that you review and understand the information about the specific tunnel type that you want to implement. When you are familiar with the type of tunnel you need, see the table below for a summary of the tunnel configuration parameters that you may find useful.
GRE IPv4 Tunnel Support for IPv6 TrafficIPv6 traffic can be carried over IPv4 GRE tunnels using the standard GRE tunneling technique that is designed to provide the services to implement any standard point-to-point encapsulation scheme. As in IPv6 manually configured tunnels, GRE tunnels are links between two points, with a separate tunnel for each link. The tunnels are not tied to a specific passenger or transport protocol but, in this case, carry IPv6 as the passenger protocol with the GRE as the carrier protocol and IPv4 or IPv6 as the transport protocol. The primary use of GRE tunnels is for stable connections that require regular secure communication between two edge devices or between an edge device and an end system. The edge devices and the end systems must be dual-stack implementations. How to Configure IPv6 over IPv4 GRE TunnelsConfiguring GRE IPv6 TunnelsPerform this task to configure a GRE tunnel on an IPv6 network. GRE tunnels can be configured to run over an IPv6 network layer and to transport IPv6 packets in IPv6 tunnels and IPv4 packets in IPv6 tunnels. Before You Begin
SUMMARY STEPS
When GRE IPv6 tunnels are configured, IPv6 addresses are assigned to the tunnel source and the tunnel destination. The tunnel interface can have either IPv4 or IPv6 addresses assigned (this is not shown in the task). The host or router at each end of a configured tunnel must support both the IPv4 and IPv6 protocol stacks. DETAILED STEPS Configuration Examples for IPv6 over IPv4 GRE Tunnels
Example: GRE Tunnel Running IS-IS and IPv6 TrafficThe following example configures a GRE tunnel running both IS-IS and IPv6 traffic between Router A and Router B: Router A Configurationipv6 unicast-routing clns routing ! interface tunnel 0 no ip address ipv6 address 3ffe:b00:c18:1::3/127 ipv6 router isis tunnel source Ethernet 0/0 tunnel destination 2001:DB8:1111:2222::1/64 tunnel mode gre ipv6 ! interface Ethernet0/0 ip address 10.0.0.1 255.255.255.0 ! router isis net 49.0000.0000.000a.00 Router B Configurationipv6 unicast-routing clns routing ! interface tunnel 0 no ip address ipv6 address 3ffe:b00:c18:1::2/127 ipv6 router isis tunnel source Ethernet 0/0 tunnel destination 2001:DB8:1111:2222::2/64 tunnel mode gre ipv6 ! interface Ethernet0/0 ip address 10.0.0.2 255.255.255.0 ! router isis net 49.0000.0000.000b.00 address-family ipv6 redistribute static exit-address-family Example: Tunnel Destination Address for IPv6 TunnelRouter(config ) # interface Tunnel0 Router(config -if) # no ip address Router(config -if) # ipv6 router isis Router(config -if) # tunnel source Ethernet 0/0 Router(config -if) # tunnel destination 2001:DB8:1111:2222::1/64 Router(config -if) # tunnel mode gre ipv6 Router(config -if) # exit ! Router(config ) # interface Ethernet0/0 Router(config -if) # ip address 10.0.0.1 255.255.255.0 Router(config -if) # exit ! Router(config ) # ipv6 unicast-routing Router(config ) # router isis Router(config ) # net 49.0000.0000.000a.00 Additional ReferencesRelated Documents
MIBsTechnical Assistance
Feature Information for IPv6 over IPv4 GRE TunnelsThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|