Table Of Contents
Tunnel Templates
Applying the Tunnel Template on the Home Agent
Applying the Tunnel Template on the Mobile Router
Example Configuration
Applying Tunnel Templates to the IPSec Two-box Solution
Related Documents
Tunnel Templates
Tunnel templates allow a mobile router to carry multicast sessions to mobile networks as it roams. The Tunnel Templates for Multicast feature allows the configuration of multicast sessions on statically created tunnels to be applied to dynamic tunnels brought up on a home agent and a mobile router. A tunnel template is defined and applied to the tunnels between the home agent and the mobile router.
Reverse tunneling must be enabled from the mobile router to the home agent.
The following restrictions apply:
•
Tunnels cannot be removed if they are being used as templates.
•
This feature does not support mobile routers that are acting as mobile nodes.
Applying the Tunnel Template on the Home Agent
To apply the tunnel template to the tunnels brought up at the home agent, use the interface tunnel command. For example:
wd>password ! If prompted
wd(config)#ip multicast-routing ! Enables IP multicast routing.
wd(config)#interface tunnel interfacenumber ! Designates a tunnel interface and enters
interface configuration mode. This is the tunnel template that will be applied to the
mobile networks.
wd(config-in)#ip pim sparse-mode ! Enables Protocol Independent Multicast (PIM)
on the tunnel interface in sparse mode.
wd(config)#router mobile ! Enables Mobile IP on the router.
wd(config)#ip mobile mobile-networks ! Configures mobile networks for the mobile host
and enters mobile networks configuration mode.
wd(config)#tunnel template interfacenumber ! Designates the tunnel template to apply during
registration. The interfacenumber argument is set to the tunnel template.
Use the show ip mobile tunnel command to display the active tunnels. The following example displays the active Mobile IP tunnels and the template configuration for the tunnel on the home agent:
Router# show ip mobile tunnel
Total mobile ip tunnels 2
src 1.1.1.1, dest 20.20.0.1
encap IP/IP, mode reverse-allowed, tunnel-users 1
Path MTU Discovery, mtu:0, ager:10 mins, expires:never
outbound interface Tunnel0
HA created, fast switching enabled, ICMP unreachable enabled
27 packets input, 2919 bytes, 0 drops
24 packets output, 2568 bytes
Running template configuration for this tunnel:
src 1.1.1.1, dest 30.30.10.2
encap IP/IP, mode reverse-allowed, tunnel-users 1
Path MTU Discovery, mtu:0, ager:10 mins, expires:never
outbound interface Ethernet1/3
HA created, fast switching enabled, ICMP unreachable enabled
0 packets input, 0 bytes, 0 drops
24 packets output, 3048 bytes
Applying the Tunnel Template on the Mobile Router
To apply the tunnel template to the tunnels brought up at the mobile router, follow this example:
wd>password ! If prompted
wd(config)#ip multicast-routing ! Enables IP multicast routing.
wd(config)#interface tunnel interfacenumber ! Designates a tunnel interface and enters
interface configuration mode. This is the tunnel template that will be applied to the
mobile networks.
wd(config-in)#ip pim sparse-mode ! Enables Protocol Independent Multicast (PIM)
on the tunnel interface in sparse mode.
wd(config)#router mobile ! Enables Mobile IP on the router.
wd(config)#ip router mobile ! Enables the mobile router and enters mobile
router configuration mode.
wd(config)#tunnel template interfacenumber ! Designates the tunnel template to apply during
registration. The interfacenumber argument is set to the tunnel template.
Use the show ip mobile tunnel command to display the active tunnels.
Example Configuration
In the following example configuration, a tunnel template is defined and configured to be brought up at the home agent and mobile router. The foreign agent does not require any additional configuration to support the Cisco Mobile Networks—Tunnel Templates for Multicast feature.
Home Agent
ip address 1.1.1.1 255.255.255.255
! Tunnel template to be applied to mobile networks
ip address 13.0.0.1 255.0.0.0
ip mobile mobile-networks 11.1.0.1
network 11.1.2.0 255.255.255.0
network 11.1.1.0 255.255.255.0
! Select tunnel template to apply during registration
ip mobile secure host 11.1.0.1 spi 101 key hex 12345678123456781234567812345678 algorithm
md5 mode prefix-suffix
no ip mobile tunnel route-cache
Mobile Router
ip address 11.1.0.1 255.255.255.255
! Tunnel template to be applied to mobile networks
ip address 20.0.0.1 255.0.0.0
ip mobile router-service roam
ip pim rp-address 7.7.7.7
ip mobile secure home-agent 1.1.1.1 spi 102 key hex 23456781234567812345678123456781
algorithm md5 mode prefix-suffix
address 11.2.0.1 255.255.0.0
! Select tunnel template to apply during registration
register extend expire 5 retry 2 interval 15
Applying Tunnel Templates to the IPSec Two-box Solution
Configuring IPSec in conjunction with Cisco IOS Mobile Network software requires special attention because the egress interface of the traffic can change and IPSec is typically configured on the egress interface. The previous recommendation had been to configure the crypto map on the loopback interface and to use policy routing to set next hop loopback for all traffic that needed encryption.
Note
Applying a crypto map on a loopback interface is not a supported configuration (as documented in CSCdx79795).
Tunnel templates, introduced in Cisco IOS Release 12.2(15)T, add multicast support, but can be used to apply other parameters to the inner tunnel interface. Applying the crypto map to the tunnel template requires the crypto map local-address commands as shown in the following example configuration. The local address should be set to the home address interface. This recommendation eliminates the need for policy routing and allows for all traffic to be Cisco Express Forwarding (CEF) switched (which is not supported on loopback interfaces).
To be encrypted, all traffic from the mobile router must be reverse tunneled; the reverse tunnel becomes the egress interface at which the crypto map is applied.
Example Configuration
crypto isakmp key skeleton
crypto ipsec transform-set aes esp-aes 256 esp-sha-hmac
! Local-address must point to the Home Address
crypto map MAR_VPN local-address Loopback 0
crypto map MAR_VPN 1 ipsec-isakmp
description Mobile Networks Tunnel Template
ip address 192.168.100.10 255.255.255.255
ip address 169.254.255.1 255.255.255.255
ip mobile router-service roam
description Mobile Network
ip address 192.168.124.1 255.255.255.0
ip mobile secure home-agent 192.168.1.2 spi 100 key hex 1234567890abcdef1234567890abcdef
algorithm md5 mode prefix-suffix
address 192.168.100.10 255.255.255.0
mobile-network Ethernet1/0
! Tunnel Template where the crypto map is applied
! Reverse tunneling must be enabled or traffic will not exit via the tunnel
access-list 110 permit ip any host 192.168.2.2
Validating the Configuration
The configuration can be validated by using the show ip mobile router command to identify the tunnel interface that is being used by the mobile router, Then use the show crypto ipsec sa interface tunnel n command to verify that the relevant SAs are active. The important sections have been emphasized in the following sample output.
Enabled 10/18/05 18:50:54
Last redundancy state transition NEVER
Home Address 192.168.100.10 Mask 255.255.255.0
Home Agent 192.168.1.2 Priority 100 (best) (current)
Registration lifetime 65534 sec
Retransmit Init 1000, Max 5000 msec, Limit 3
Extend Expire 120, Retry 3, Interval 10
Mobile Networks: Loopback2 (192.168.123.0/255.255.255.0)
Ethernet1/0 (192.168.124.0/255.255.255.0)
Active foreign agent 192.168.6.1, Care-of 192.168.6.1 On interface EthernetO/O
MN#show crypto ipsec sa interface tunnel 0
Crypto map tag: MAR_VPN, local addr 192.168.100.10
local ident (addr/mask/prot/port): (0.0.0.0/0.0.0.0/0/0)
remote ident (addr/mask/prot/port): (192.168.2.2/255.255.255.255/0/0)
current-peer 192.168.1.1 port 500
#pkts encaps: 5, #pkts encrypt: 5, #pkts digest: 5
#pkts decaps: 9, #pkts decrypt: 9, #pkts verify: 9
#pkts compressed: 0, #pkts decompressed: 0
#pkts not compressed: 0, #pkts compr. failed: 0
#pkts not decompressed: 0, #pkts decompress failed: 0
#send errors 0, #recv errors 0
local crypto endpt.: 192.168.100.10, remote crypto endpt.: 192.168.1.1
path mtu 1514, ip mtu 1514
current outbound spi: OxC8D41EOA(336934452~)
spi: OxB7BClB29 (3082558249)
transfor.m: esp-256-aes esp-sha-hmac ,
in use settings ={Tunnel, }
conn id: 1, flow_id: SW:l, crypto map: MAR_VPN
sa timdng: remaining key lifetime (k/sec): (4602927/3584) IV size: 16 bytes
replay detection support: Y
spi: OxC8D41EOA(3369344522)
transfor.m: esp-256-aes esp-sha-hmac ,
in use settings ={Tunnel, }
conn id: 2, flow_id: SW:2, crypto map: MAR VPN
sa timdng: remaining key lifetime (k/sec): (4602928/3582) IV size: 16 bytes
replay detection support: Y
local ident (addr/mask/prot/port): (0.0.0.0/0.0.0.0/0/0)
remote ident (addr/mask/prot/port): (192.168.2.2,255.255.255.255/0/0) current-peer
192.168.1.1 port 500
PERMIT, flags={origin_is_acl,ipsec_sa_request_sent}
#pkts encaps: 0, #pkts encrypt: 0, #pkts digest: 0
#pkts decaps: 0, #pkts decrypt: 0, #pkts verify: 0
#pkts compressed: 0, #pkts decompressed: 0
#pkts not compressed: 0, #pkts compr. failed: 0
#pkts not decompressed: 0, #pkts decompress failed: 0
#send errors 8, #recv errors 0
local crypto endpt,:192.168.100.10, remote crypto endpt.: 192.168.1.1
path mtu 1514, ip mtu 1514
current outbound spi: 0x0(0)
Related Documents
Cisco Mobile Networks Tunnel Templates for Multicast
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a0080455164.html
Other Configuration Tasks in the Cisco Mobile Wireless Home Agent Feature Guide
http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide_chapter09186a00805eb0d4.html
You can access these documents on the Documentation page on Cisco Connection Online (CCO) at www.cisco.com. The following documentation is available at the http://www.cisco.com/en/US/products/hw/routers/ps272/tsd_products_support_series_home.html
URL:
•
Release Notes for the Cisco 3200 Series Mobile Access Routers—Provides information on accessing documentation and technical assistance for the Cisco 3200 Series wireless and mobile router.
•
Cisco IOS Command Reference for Cisco Access Points and Bridges1—New and revised Cisco IOS commands for the radio ports provided on the Wireless Mobile Interface Card (WMIC).
•
Cisco 3200 Series Wireless MIC Software Configuration Guide1—Example procedures for using the IOS commands to configure the Wireless Mobile Interface Card (WMIC).
•
Configuration Guide for the Cisco 3200 Series Mobile Access Router1—Example procedures for using the IOS commands to configure assembled Cisco 3200 Series routers.
•
Cisco 3200 Series Mobile Access Router Hardware Reference1—This document. It provides descriptions of the Cisco MIC I/O cards found in Cisco 3200 Series routers.
•
Cisco 3200 Series Mobile Access Router Reference Sell Document1—An overview of the reference sell program and components for the Cisco 3200 Series router.
The Release Notes for the Cisco 3250 Mobile Router lists the enhancements to and caveats for Cisco IOS releases as they relate to the Cisco 3200 Series router can be found at:
http://www.cisco.com/en/US/products/sw/iosswrel/products_ios_cisco_ios_software_releases.html or
http://www.cisco.com/en/US/products/sw/iosswrel/ps5012/ps4629/index.html
1. Also available on the platform-specific CD-ROM.
This feature adds support for RFC 2006 Set operations and security violation traps. For specifications, see RFC 2006, The Definitions of Managed Objects for IP Mobility Support Using SMIv2.
For information about using Cisco IOS software to configure SNMP, refer to the following documents:
•
The "Configuring SNMP Support" chapter of the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2
•
The "SNMP Commands" chapter of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2
For information about using Cisco IOS software to configure SNMP MIB features, refer to the appropriate documentation for your network management system.
For information on configuring Mobile IP using Cisco IOS software, refer to the following documents:
•
The "Configuring Mobile IP" chapter of the Cisco IOS IP Configuration Guide, Release 12.2
•
The "Mobile IP Commands" chapter of the Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2
Related documents from the Cisco TAC Web pages include:
•
Antenna Cabling (http://www.cisco.com/warp/public/102/wlan/antcable.html)