Table Of Contents
Implementing Dynamic Multipoint VPN for IPv6
Prerequisites for Implementing DMVPN for IPv6
Restrictions for Implementing DMVPN for IPv6
Information About Implementing DMVPN for IPv6
IPv6 Addressing and Restrictions
How to Configure DMVPN for IPv6
Configuring an IPsec Profile in DMVPN for IPv6
Configuring the Hub for IPv6 over DMVPN
Configuring the NHRP Redirect and Shortcut Features On the Hub
Configuring the Spoke for IPv6 over DMVPN
Verifying DMVPN for IPv6 Configuration
Monitoring and Maintaining DMVPN for IPv6 Configuration and Operation
Configuration Examples for Implementing DMVPN for IPv6
Configuring an IPsec Profile: Example
Configuring the Hub for DMVPN: Example
Configuring the NHRP Redirect and Shortcut Features On the Hub: Example
Configuring the Spoke for DMVPN: Example
Feature Information for Implementing DMVPN for IPv6
Implementing Dynamic Multipoint VPN for IPv6
First Published: July 11, 2008Last Updated: July 11, 2008This document describes how to implement Dynamic Multipoint VPN for IPv6 feature, which allows users to better scale large and small IPsec Virtual Private Networks (VPNs) by combining generic routing encapsulation (GRE) tunnels, IP security (IPsec) encryption, and the Next Hop Resolution Protocol (NHRP). In Dynamic Multipoint Virtual Private Network (DMVPN) for IPv6, the public network (the Internet) is a pure IPv4 network, and the private network (the intranet) is IPv6 capable.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see 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 for Implementing DMVPN for IPv6" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Implementing DMVPN for IPv6
•
Restrictions for Implementing DMVPN for IPv6
•
Information About Implementing DMVPN for IPv6
•
How to Configure DMVPN for IPv6
•
Configuration Examples for Implementing DMVPN for IPv6
•
Feature Information for Implementing DMVPN for IPv6
Prerequisites for Implementing DMVPN for IPv6
•
This document assumes that you are familiar with IPv6 and IPv4. See the publications referenced in the "Additional References" section for IPv6 and IPv4 configuration and command reference information.
•
Perform basic IPv6 addressing and basic connectivity as described in "Implementing IPv6 Addressing and Basic Connectivity."
•
Supported routing protocols include Border Gateway Protocol (BGP), Enhanced Interior Gateway Routing Protocol (EIGRP), On-Demand Routing (ODR), Open Shortest Path First (OSPF), and Routing Information Protocol (RIP). One of these protocols must be enabled for DMVPN for IPv6 to work.
Restrictions for Implementing DMVPN for IPv6
•
IPV6 can be configured only on the protected network.
•
Every IPv6 NHRP interface is configured with one IPv6 unicast address. This address can be a globally reachable or unique local address.
•
Every IPv6 NHRP interface is configured with one IPv6 link-local address that is unique across all the DMVPN hosts in the DMVPN cloud (that is, the hubs and spokes).
•
IPv6 VRFs are not supported fully by IPv6 routing protocols such as EIGRP or OSPF. Therefore, DMVPN for IPv6 does not support IPv6 VRFs.
•
The WAN network has to be a IPv4 network.
Information About Implementing DMVPN for IPv6
To configure DMVPN for Cisco IOS software, you must understand the following concept:
DMVPN for IPv6 Overview
The DMVPN feature combines NHRP routing, multipoint generic routing encapsulation (mGRE) tunnels, and IPsec encryption to provide users an ease of configuration via crypto profiles—which override the requirement for defining static crypto maps—and dynamic discovery of tunnel endpoints.
This feature relies on the following Cisco enhanced standard technologies:
•
NHRP—A client and server protocol where the hub is the server and the spokes are the clients. The hub maintains an NHRP database of the public interface addresses of each spoke. Each spoke registers its real address when it boots and queries the NHRP database for real addresses of the destination spokes to build direct tunnels.
•
mGRE tunnel interface—An mGRE tunnel interface allows a single GRE interface to support multiple IPsec tunnels and simplifies the size and complexity of the configuration.
•
IPsec encryption—An IPsec tunnel interface allows for the protection of site-to-site IPv6 traffic with native encapsulation.
In DMVPN for IPv6, the public network (the Internet) is a pure IPv4 network, and the private network (the intranet) is IPv6 capable. The intranets could be a mix of IPv4 or IPv6 clouds connected to each other using the DMVPN technologies, with the underlying carrier being traditional IPv4.
NHRP Routing
The NHRP protocol resolves a given intranet address (IPv4 or IPv6) to an Internet address (IPv4 nonbroadcast multiaccess [NBMA] address).
In Figure 1, the intranets that are connected over the DMVPN network are IPv6 clouds, and the Internet is a pure IPv4 cloud. Spokes S1 and S2 are connected to the Hub H over the Internet using a statically configured mGRE tunnel. The address of the tunnel itself is in the IPv6 domain, because it is another node on the intranet. The source and destinations of the tunnel (the mGRE endpoints), however, are always in IPv4, in the Internet domain. The mGRE tunnel is aware of the IPv6 network because the GRE passenger protocol is an IPv6 packet, and the GRE transport (or carrier) protocol is an IPv4 packet.
Figure 1 IPv6 Topology That Triggers NHRP
When an IPv6 host in LAN L1 sends a packet destined to an IPv6 host in LAN L2, the packet is first routed to the gateway (which is Spoke S1) in LAN L1. Spoke S1 is a dual-stack router, which means both IPv4 and IPv6 are configured. The IPv6 routing table in S1 points to a next hop, which is the IPv6 address of the tunnel on Spoke S2. This is a VPN address that must be mapped to an NBMA address, triggering NHRP.
IPv6 NHRP Redirect and Shortcut Features
When IPv6 NHRP redirect is enabled, NHRP examines every data packet in the output feature path. If the data packet enters and leaves on the same logical network, it sends an NHRP traffic indication message to the originator of the data packet. In NHRP, a logical network is identified by the NHRP network ID, which groups multiple physical interfaces into a single logical network.
When IPv6 NHRP shortcut is enabled, NHRP intercepts every data packet in the output feature path. It checks to see if there is an NHRP cache entry to the destination of the data packet and, if yes, it replaces the current output adjacency with the one present in the NHRP cache. The data packet is therefore switched out using the new adjacency provided by NHRP.
IPv6 Routing
NHRP is automatically invoked for mGRE tunnels carrying the IPv6 passenger protocol. When a packet is routed and the packet is sent to the switching path, NHRP looks up the given next hop and, if required, initiates an NHRP resolution query. If the resolution is successful, NHRP populates the tunnel endpoint database, which then populates the Cisco Express Forwarding adjacency table. The subsequent packets are Cisco Express Forwarding switched if Cisco Express Forwarding is enabled.
IPv6 Addressing and Restrictions
IPv6 allows multiple unicast addresses on a given IPv6 interface. IPv6 also allows special address types, such as anycast, multicast, link-local addresses, and unicast addresses.
DMVPN for IPv6 has the following addressing restrictions:
•
Every IPv6 NHRP interface is configured with one IPv6 unicast address. This address can be a globally reachable or unique local address.
•
Every IPv6 NHRP interface is configured with one IPv6 link-local address that is unique across all the DMVPN hosts in the DMVPN cloud (that is, the hubs and spokes).
–
If no other tunnels on the router are using the same tunnel source, then the tunnel source address can be embedded into an IPv6 address.
–
If the router has only one DMVPN IPv6 tunnel, then manual configuration of the IPv6 link-local address is not required. Instead, use the ipv6 enable command to autogenerate a link-local address.
–
If the router has more than one DMVPN IPv6 tunnel, then the link-local address must be manually configured using the ipv6 address fe80::2001 link-local command.
How to Configure DMVPN for IPv6
To enable mGRE and IPsec tunneling for hub and spoke routers, you must configure an IPsec profile that uses a global IPsec policy template and configure your mGRE tunnel for IPsec encryption. This section contains the following procedures:
•
Configuring an IPsec Profile in DMVPN for IPv6 (required)
•
Configuring the Hub for IPv6 over DMVPN (required)
•
Configuring the Spoke for IPv6 over DMVPN (required)
•
Verifying DMVPN for IPv6 Configuration (optional)
•
Monitoring and Maintaining DMVPN for IPv6 Configuration and Operation (optional)
Configuring an IPsec Profile in DMVPN for IPv6
The IPsec profile shares most of the same commands with the crypto map configuration, but only a subset of the commands are valid in an IPsec profile. Only commands that pertain to an IPsec policy can be issued under an IPsec profile; you cannot specify the IPsec peer address or the access control list (ACL) to match the packets that are to be encrypted.
Prerequisites
Before configuring an IPsec profile, you must do the following:
•
Define a transform set by using the crypto ipsec transform-set command.
•
Make sure that Internet Security Association Key Management Protocol (ISAKMP) is configured with default ISAKMP settings. For further information about default ISAKMP settings, see the Implementing IPsec in IPv6 Security module and the Cisco IOS IPv6 Command Reference.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
crypto identity name
4.
crypto ipsec profile name
5.
set transform-set transform-set-name
6.
set identity
7.
set security-association lifetime {seconds seconds | kilobytes kilobytes}
8.
set pfs [group1 | group2]
DETAILED STEPS
Configuring the Hub for IPv6 over DMVPN
This task describes how to configure the hub router for IPv6 over DMVPN for mGRE and IPsec integration (that is, associate the tunnel with the IPsec profile configured in the previous procedure).
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface tunnel number
4.
ipv6 address {ipv6-address/prefix-length | prefix-name sub-bits/prefix-length}
5.
ipv6 address ipv6-address/prefix-length link-local
6.
ipv6 mtu bytes
7.
ipv6 nhrp authentication string
8.
ipv6 nhrp map multicast dynamic
9.
ipv6 nhrp network-id network-id
10.
tunnel source {ip-address | ipv6-address | interface-type interface-number}
11.
tunnel mode {aurp | cayman | dvmrp | eon | gre | gre multipoint | gre ipv6 | ipip [decapsulate-any] | ipsec ipv4 | iptalk | ipv6 | ipsec ipv6 | mpls | nos | rbscp}
12.
tunnel protection ipsec profile name [shared]
13.
bandwidth {interzone | total | session} {default | zone zone-name} bandwidth-size
14.
ipv6 nhrp holdtime seconds
DETAILED STEPS
Configuring the NHRP Redirect and Shortcut Features On the Hub
This task describes how to configure the NHRP redirect and shortcut features on the hub.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface tunnel number
4.
ipv6 address {ipv6-address/prefix-length | prefix-name sub-bits/prefix-length}
5.
ipv6 nhrp redirect [timeout seconds]
6.
ipv6 nhrp shortcut
DETAILED STEPS
Configuring the Spoke for IPv6 over DMVPN
This task describes how to configure the spoke for IPv6 over DMVPN.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface tunnel number
4.
ipv6 address {ipv6-address/prefix-length | prefix-name sub-bits/prefix-length}
5.
ipv6 address ipv6-address/prefix-length link-local
6.
ipv6 mtu bytes
7.
ipv6 nhrp authentication string
8.
ipv6 nhrp map ipv6-address nbma-address
9.
ipv6 nhrp map multicast ipv4-nbma-address
10.
ipv6 nhrp nhs ipv6-nhs-address [net-address]
11.
ipv6 nhrp network-id network-id
12.
tunnel source {ip-address | ipv6-address | interface-type interface-number}
13.
tunnel mode {aurp | cayman | dvmrp | eon | gre | gre multipoint | gre ipv6 | ipip [decapsulate-any] | ipsec ipv4 | iptalk | ipv6 | ipsec ipv6 | mpls | nos | rbscp}
or
tunnel destination {host-name | ip-address | ipv6-address}
14.
tunnel protection ipsec profile name [shared]
15.
bandwidth {interzone | total | session} {default | zone zone-name} bandwidth-size
16.
ipv6 nhrp holdtime seconds
DETAILED STEPS
Verifying DMVPN for IPv6 Configuration
This optional task describes how to display information to verify DMVPN for IPv6 configuration. Use the following optional commands as needed to verify configuration and operation.
SUMMARY STEPS
1.
enable
2.
show dmvpn [ipv4 | ipv6] [peer [nbma | tunnel {ip-address | ipv6-address}] | network {ip-address mask}] [vrf vrf-name] [interface tunnel number] [detail] [static] [debug-condition]
3.
show ipv6 nhrp [dynamic [ipv6-address] | incomplete | static] [address | interface] [brief | detail] [purge]
4.
show ipv6 nhrp multicast [ipv6-address | interface]
5.
show ipv6 nhrp summary
6.
show ipv6 nhrp traffic [interface tunnel number]
DETAILED STEPS
Monitoring and Maintaining DMVPN for IPv6 Configuration and Operation
This optional task explains how to display information to monitor and maintain DMVPN for IPv6 configuration and operation. Use the following optional commands only as needed to monitor configuration and operation.
SUMMARY STEPS
1.
enable
2.
clear dmvpn session [peer {nbma | tunnel ipv4-address | ipv6-address}] [interface tunnel number] [vrf vrf-name] [static]
3.
clear ipv6 nhrp [ipv6-address | counters]
4.
debug dmvpn [condition [unmatched] | [peer [nbma | tunnel | ipv4-address | ipv6-address] | vrf [vrf-name] | interface {tunnel number} | error | detail | packet | all | nhrp [crypto | tunnel | socket | all]
5.
debug nhrp {ipv4 | ipv6} [cache | extension | packet | rate]
6.
debug nhrp condition [peer [nbma | tunnel | ip-address | ipv6-address]] | interface tunnel number | [vrf vrf-name]
7.
debug nhrp {ipv4 | ipv6} error
DETAILED STEPS
Examples
This section provides the following output examples:
•
Sample Output from the show dmvpn Command
•
Sample Output from the show ipv6 nhrp Command
•
Sample Output for the debug nhrp Command
Sample Output from the show dmvpn Command
The following sample output is from the show dmvpn command, with the ipv6 and detail keywords, for the hub:
Router# show dmvpn ipv6 detailLegend: Attrb --> S - Static, D - Dynamic, I - IncompleteN - NATed, L - Local, X - No Socket# Ent --> Number of NHRP entries with same NBMA peerNHS Status: E --> Expecting Replies, R --> RespondingUpDn Time --> Up or Down Time for a Tunnel==========================================================================Intferface Tunnel1 is up/up, Addr. is 10.0.0.3, VRF ""Tunnel Src./Dest. addr: 192.169.2.9/MGRE, Tunnel VRF ""Protocol/Transport: "multi-GRE/IP", Protect "test_profile"Type:Hub, Total NBMA Peers (v4/v6): 21.Peer NBMA Address: 192.169.2.10Tunnel IPv6 Address: 2001::4IPv6 Target Network: 2001::4/128# Ent: 2, Status: UP, UpDn Time: 00:01:51, Cache Attrib: DType:Hub, Total NBMA Peers (v4/v6): 22.Peer NBMA Address: 192.169.2.10Tunnel IPv6 Address: 2001::4IPv6 Target Network: FE80::2/128# Ent: 0, Status: UP, UpDn Time: 00:01:51, Cache Attrib: DType:Hub, Total NBMA Peers (v4/v6): 23.Peer NBMA Address: 192.169.2.11Tunnel IPv6 Address: 2001::5IPv6 Target Network: 2001::5/128# Ent: 2, Status: UP, UpDn Time: 00:26:38, Cache Attrib: DType:Hub, Total NBMA Peers (v4/v6): 24.Peer NBMA Address: 192.169.2.11Tunnel IPv6 Address: 2001::5IPv6 Target Network: FE80::3/128# Ent: 0, Status: UP, UpDn Time: 00:26:38, Cache Attrib: DPending DMVPN Sessions:Interface: Tunnel1IKE SA: local 192.169.2.9/500 remote 192.169.2.10/500 ActiveCrypto Session Status: UP-ACTIVEfvrf: (none), Phase1_id: 192.169.2.10IPSEC FLOW: permit 47 host 192.169.2.9 host 192.169.2.10Active SAs: 2, origin: crypto mapOutbound SPI : 0x BB0ED02, transform : esp-3des esp-sha-hmacSocket State: OpenInterface: Tunnel1IKE SA: local 192.169.2.9/500 remote 192.169.2.11/500 ActiveCrypto Session Status: UP-ACTIVEfvrf: (none), Phase1_id: 192.169.2.11IPSEC FLOW: permit 47 host 192.169.2.9 host 192.169.2.11Active SAs: 2, origin: crypto mapOutbound SPI : 0xB79B277B, transform : esp-3des esp-sha-hmacSocket State: OpenThe following sample output is from the show dmvpn command, with the ipv6 and detail keywords, for the spoke:
Router# show dmvpn ipv6 detailLegend: Attrb --> S - Static, D - Dynamic, I - IncompleteN - NATed, L - Local, X - No Socket# Ent --> Number of NHRP entries with same NBMA peerNHS Status: E --> Expecting Replies, R --> RespondingUpDn Time --> Up or Down Time for a Tunnel==========================================================================Intferface Tunnel1 is up/up, Addr. is 10.0.0.1, VRF ""Tunnel Src./Dest. addr: 192.169.2.10/MGRE, Tunnel VRF ""Protocol/Transport: "multi-GRE/IP", Protect "test_profile"IPv6 NHS: 2001::6 REType:Spoke, Total NBMA Peers (v4/v6): 11.Peer NBMA Address: 192.169.2.9Tunnel IPv6 Address: 2001::6IPv6 Target Network: 2001::/112# Ent: 2, Status: NHRP, UpDn Time: never, Cache Attrib: SIPv6 NHS: 2001::6 REType:Unknown, Total NBMA Peers (v4/v6): 12.Peer NBMA Address: 192.169.2.9Tunnel IPv6 Address: FE80::1IPv6 Target Network: FE80::1/128# Ent: 0, Status: UP, UpDn Time: 00:00:24, Cache Attrib: DPending DMVPN Sessions:Interface: Tunnel1IKE SA: local 192.169.2.10/500 remote 192.169.2.9/500 ActiveCrypto Session Status: UP-ACTIVEfvrf: (none), Phase1_id: 192.169.2.9IPSEC FLOW: permit 47 host 192.169.2.10 host 192.169.2.9Active SAs: 2, origin: crypto mapOutbound SPI : 0x6F75C431, transform : esp-3des esp-sha-hmacSocket State: OpenSample Output from the show ipv6 nhrp Command
The following sample output is from the show ipv6 nhrp command for the hub and the spoke:
Hub
Router# show ipv6 nhrp2001::4/128 via 2001::4Tunnel1 created 00:02:40, expire 00:00:47Type: dynamic, Flags: unique registered usedNBMA address: 192.169.2.102001::5/128 via 2001::5Tunnel1 created 00:02:37, expire 00:00:47Type: dynamic, Flags: unique registered usedNBMA address: 192.169.2.11FE80::2/128 via 2001::4Tunnel1 created 00:02:40, expire 00:00:47Type: dynamic, Flags: unique registered usedNBMA address: 192.169.2.10FE80::3/128 via 2001::5Tunnel1 created 00:02:37, expire 00:00:47Type: dynamic, Flags: unique registered usedNBMA address: 192.169.2.11Spoke
Router# show ipv6 nhrp2001::8/128Tunnel1 created 00:00:13, expire 00:02:51Type: incomplete, Flags: negativeCache hits: 22001::/112 via 2001::6Tunnel1 created 00:01:16, never expireType: static, Flags: usedNBMA address: 192.169.2.9FE80::1/128 via FE80::1Tunnel1 created 00:01:15, expire 00:00:43Type: dynamic, Flags:NBMA address: 192.169.2.9Sample Output from the show ipv6 nhrp multicast Command
The following sample output is from the show ipv6 nhrp multicast command for the hub and the spoke:
Hub
Router# show ipv6 nhrp multicastI/F NBMA addressTunnel1 192.169.2.10 Flags: dynamicTunnel1 192.169.2.11 Flags: dynamicSpoke
Router# show ipv6 nhrp multicastI/F NBMA addressTunnel1 192.169.2.9 Flags: staticSample Output for the show ipv6 nhrp traffic Command
The following sample output is from the show ipv6 nhrp traffic command:
Router# show ipv6 nhrp trafficTunnel0: Max-send limit:100Pkts/10Sec, Usage:0%Sent: Total 81 Resolution Request 1 Resolution Reply 6 Registration Request0 Registration Reply 0 Purge Request 0 Purge Reply0 Error Indication 0 Traffic IndicationRcvd: Total 51 Resolution Request 1 Resolution Reply 0 Registration Request2 Registration Reply 0 Purge Request 0 Purge Reply0 Error Indication 1 Traffic IndicationSample Output for the debug nhrp Command
The following sample output is from the debug nhrp command with the ipv6 keyword:
Router# debug nhrp ipv6Aug 9 13:13:41.486: NHRP: Attempting to send packet via DEST- 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32Aug 9 13:13:41.486: NHRP: Encapsulation succeeded.Aug 9 13:13:41.486: NHRP: Tunnel NBMA addr 11.11.11.99Aug 9 13:13:41.486: NHRP: Send Registration Request via Tunnel0 vrf 0, packet size: 105Aug 9 13:13:41.486: src: 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32,dst: 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32Aug 9 13:13:41.486: NHRP: 105 bytes out Tunnel0Aug 9 13:13:41.486: NHRP: Receive Registration Reply via Tunnel0 vrf 0, packet size: 125Configuration Examples for Implementing DMVPN for IPv6
This section provides the following DMVPN configuration examples:
•
Configuring an IPsec Profile: Example
•
Configuring the Hub for DMVPN: Example
•
Configuring the NHRP Redirect and Shortcut Features On the Hub: Example
•
Configuring the Spoke for DMVPN: Example
Configuring an IPsec Profile: Example
The following example shows how to configure an IPsec profile:
Router(config)# crypto identity router1
Router(config)# crypto ipsec profile example1Router(config-crypto-map)# set transform-set example-setRouter(config-crypto-map)# set identity router1Router(config-crypto-map)# set security-association lifetime seconds 1800
Router(config-crypto-map)# set pfs group2
Configuring the Hub for DMVPN: Example
This example displays information on configuring the hub for DMVPN:
Router# show running-configversion 12.4service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname Hub-99!boot-start-markerboot-end-marker!logging message-counter syslog!no aaa new-modelclock timezone IST 0mmi polling-interval 60no mmi auto-configureno mmi pvcmmi snmp-timeout 180ip auth-proxy max-nodata-conns 3ip admission max-nodata-conns 3...ip cefno ip domain lookupipv6 unicast-routingipv6 cef!multilink bundle-name authenticated!!!archivelog confighidekeys!!crypto isakmp policy 1authentication pre-sharecrypto isakmp key cisco123 address 10.0.0.0 0.0.0.0!!crypto ipsec transform-set cisco-ts esp-3des esp-md5-hmacmode transport!crypto ipsec profile cisco-ipsecset transform-set cisco-ts...interface Tunnel0bandwidth 100000ip address 10.1.1.99 255.255.255.0no ip redirectsip nhrp map multicast dynamicdelay 50000ipv6 address 2001:0DB8:99/64 2001:0db8::99/64ipv6 address FE80::0B:0B:0B:8F link-localipv6 enableipv6 eigrp 1no ipv6 split-horizon eigrp 1no ipv6 next-hop-self eigrp 1ipv6 nhrp map multicast dynamicipv6 nhrp network-id 99tunnel source Ethernet0/0tunnel mode gre multipointtunnel protection ipsec profile cisco-ipsec!interface Ethernet0/0ip address 10.11.11.99 255.255.255.0!interface Ethernet0/1no ip addressshutdown!interface Ethernet0/2no ip addressshutdowninterface Ethernet0/3no ip addressshutdown!interface Ethernet1/0no ip addressipv6 address 2001:0db8:EEEE::99/64ipv6 enableipv6 eigrp 1!interface Ethernet1/1no ip addressshutdown!interface Ethernet1/2no ip addressshutdown!interface Ethernet1/3no ip addressshutdown!!ip forward-protocol nd!!ip http serverno ip http secure-server!ipv6 router eigrp 1no shutdown!control-plane!!line con 0exec-timeout 0 0logging synchronousline aux 0line vty 0 4login!exception data-corruption buffer truncateConfiguring the NHRP Redirect and Shortcut Features On the Hub: Example
The following example shows how to configure NHRP redirect and shortcut features on the hub:
Router(config)# interface tunnel 5Router(config-if)# ipv6 address 2001:0db8:1:1::72/64Router(config-if)# ipv6 nhrp redirect
Router(config-if)# ipv6 nhrp shortcut
Configuring the Spoke for DMVPN: Example
This example provides show running-config output for a DMVPN spoke configuration:
Router# show running-configversion 12.4service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname Spoke-11!boot-start-markerboot-end-marker!logging message-counter syslog!no aaa new-modelclock timezone IST 0mmi polling-interval 60no mmi auto-configureno mmi pvcmmi snmp-timeout 180ip auth-proxy max-nodata-conns 3ip admission max-nodata-conns 3!!ip cefipv6 unicast-routingipv6 cef!multilink bundle-name authenticated!!archivelog confighidekeys!!crypto isakmp policy 1authentication pre-sharecrypto isakmp key cisco123 address 10.0.0.0 0.0.0.0!!crypto ipsec transform-set cisco-ts esp-3des esp-md5-hmacmode transport!crypto ipsec profile cisco-ipsecset transform-set cisco-ts!interface Tunnel0bandwidth 100000no ip addressno ip redirectsdelay 50000ipv6 address 2001:0DB8::11/64ipv6 address FE80::0B:0B:0B:0B link-localipv6 eigrp 1no ipv6 split-horizon eigrp 1no ipv6 next-hop-self eigrp 1ipv6 nhrp map 2001:0db8::11/64 10.11.11.99ipv6 nhrp map multicast 10.11.11.99ipv6 nhrp network-id 99ipv6 nhrp nhs 2001:0db8::99tunnel source Ethernet0/0tunnel mode gre multipointtunnel protection ipsec profile cisco-ipsec!interface Ethernet0/0ip address 10.11.11.11 255.255.255.0ipv6 enableipv6 nd ra mtu suppress!interface Ethernet0/1no ip address!interface Ethernet0/2no ip addressshutdown!interface Ethernet0/3no ip addressshutdown!interface Ethernet1/0ip address 172.16.11.11 255.255.255.0ipv6 address 2001:0db8:dddd::1/64ipv6 enableipv6 nd ra mtu suppressipv6 eigrp 1!interface Ethernet1/1no ip addressshutdownipv6 enableipv6 nd ra mtu suppress!interface Ethernet1/2no ip addressshutdown!interface Ethernet1/3no ip addressshutdown!ip forward-protocol nd!!ip http serverno ip http secure-server!ipv6 router eigrp 1no shutdown!control-plane!!line con 0exec-timeout 0 0logging synchronousline aux 0line vty 0 4login!exception data-corruption buffer truncateAdditional References
The following sections provide references related to the Implementing DMVPN for IPv6 feature.
Related Documents
Related Topic Document TitleIPv6 supported feature list
"Start Here: Cisco IOS Software Release Specifics for IPv6 Features," Cisco IOS IPv6 Configuration Guide
IPv6 IPsec
"Implementing IPsec in IPv6 Security," Cisco IOS IPv6 Configuration Guide
IPv6 basic connectivity
"Implementing IPv6 Addressing and Basic Connectivity," Cisco IOS IPv6 Configuration Guide
IPv6 commands: complete command syntax, command mode, defaults, usage guidelines, and examples
DMVPN implementation for IPv4
"Dynamic Multipoint VPN (DMVPN)" module of the Cisco IOS Security Configuration Guide
DMVPN commands for IPv4
NHRP for IPv4
"Configuring NHRP" module of the Cisco IOS IP Addressing Services Configuration Guide
NHRP commands for IPv4
"NHRP Commands" section of the Cisco IOS IP Addressing Services Command Reference
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
Technical Assistance
Feature Information for Implementing DMVPN for IPv6
Table 1 lists the release history for this feature.
For information on a feature in this technology that is not documented here, see the Start Here: Cisco IOS Software Release Specifies for IPv6 Features roadmap.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0910R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008-2009 Cisco Systems, Inc. All rights reserved.


