![]() |
IP Mobility: Mobile Networks Configuration Guide, Cisco IOS Release 15M&T
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Mobile IP - Generic Routing Encapsulation for Cisco Mobile Networks
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Contents
Mobile IP - Generic Routing Encapsulation for Cisco Mobile NetworksLast Updated: December 2, 2012
Prior to the introduction of the Generic Routing Encapsulation for Cisco Mobile Networks feature, Cisco Mobile Networks supported only IP-in-IP encapsulation. This feature adds generic routing encapsulation (GRE) support for mobile networks. Benefits of the Generic Routing Encapsulation for Cisco Mobile Networks feature include the following:
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. Prerequisites for GRE for Cisco Mobile NetworksRoaming must be enabled on an interface before GRE encapsulation can be enabled on the interface. Restrictions for GRE for Cisco Mobile NetworksThe foreign agent (FA) and home agent (HA) must support GRE encapsulation in order for the mobile router to register with GRE encapsulation enabled. If the mobile router is attempting to register using collocated care-of address (CCoA) with GRE encapsulation, the HA must support GRE encapsulation. GRE keepalives do not support Network Address Translation (NAT). If there is NAT in the path between a mobile router and its HA, GRE keepalive messages will not work properly. To work around the problem, consider using the Mobile IP NAT Traversal feature, which offers UDP encapsulation. The Mobile IP NAT Traversal feature documentation can be found at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_8/gtnatmip.htm Information About GRE for Cisco Mobile Networks
Generic Routing EncapsulationGeneric routing encapsulation (GRE) is a tunneling protocol used by Mobile IP. The GRE tunnel interface creates a virtual point-to-point link between two routers at remote points over an IP internetwork. GRE tunnels can transport a passenger protocol or encapsulated protocol. Unlike IP-in-IP encapsulation, GRE provides the following:
GRE is beneficial for certain applications because of its support for multiprotocol tunneling and explicit prevention of recursive encapsulation. GRE for Cisco Mobile Networks Feature DesignTo understand the components of the Cisco Mobile Networks solution, refer to the http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ftmbrout.htm Cisco Mobile Networks feature documentation. During agent discovery, HAs and FAs advertise their presence on their attached links by periodically multicasting or broadcasting messages called agent advertisements. The agent advertisements are ICMP Router Discovery Protocol (IRDP) messages with one or more extensions specific to Mobile IP. The agent advertisement extension consists of several fields including the following field that is relevant to this feature:
If the GRE for Cisco Mobile Networks feature is enabled, the mobile router will request GRE encapsulation in the registration request only if the FA advertises that it is capable of GRE encapsulation (the G bit is set in the advertisement). If the registration request is successful, packets will be tunneled using GRE encapsulation. If the GRE for Cisco Mobile Networks feature is enabled and the mobile router is using collocated care-of address (CCoA), the mobile router will attempt to register with the HA using GRE encapsulation. If the registration request is successful, packets will be tunneled using GRE encapsulation. If the mobile router receives a denied registration reply with error code 72 (foreign agent required encapsulation unavailable) or error code 139 (home agent unsupported encapsulation), the mobile router will send another registration request with the G bit unset and the default IP-in-IP encapsulation will be used. GRE Keepalive MessagesGRE tunnels support keepalive messages, which are messages sent periodically to the HA that allow the detection of an interruption in the end-to-end tunnel. Tunnels that use IP-in-IP encapsulation do not use keepalive messages. If a tunnel that is using IP-in-IP encapsulation loses its connection to the HA, the mobile router will not be aware of the disruption until it tries to register with the HA again. This can take up to one half of the mobile router's registration lifetime. GRE keepalive messages allow the status of the end-to-end tunnel to be checked at a configurable interval. If the mobile router detects an interruption in the connection to the HA, it will tear down the existing tunnel and attempt to reregister using the best interface. Typically this is the same interface on which the connection was previously established. If the registration attempt is unsuccessful, the mobile router will then try to register on the next best interface if one exists. Benefits of GRE for Cisco Mobile NetworksThe GRE for Cisco Mobile Networks feature introduces the ability for a mobile router to use GRE tunneling in addition to the default encapsulation method of IP-in-IP. GRE is a widely supported tunneling protocol, and some platforms support GRE tunnels in hardware. Hardware support of GRE tunneling offloads software operations, such as Cisco Express Forwarding (CEF) switching, from the CPU and increases the performance of the router. In addition, GRE supports multiprotocol tunneling and provides explicit protection against recursive encapsulation. Finally, the ability to configure keepalive messages with GRE allows the status of the end-to-end tunnel to be checked at a configurable interval, and reregistration can be attempted as soon as an interruption is detected. How to Configure GRE for Cisco Mobile NetworksConfiguring GRE on the Mobile RouterGRE encapsulation can be configured per interface or globally. Configuring GRE encapsulation on an interface allows only that interface to attempt to register with GRE encapsulation enabled. Configuring GRE encapsulation globally allows all roaming interfaces to attempt to register with GRE encapsulation enabled, unless the interface is configured for IP-in-IP encapsulation. The interface-level configuration overrides the global configuration. Perform one of the following tasks to configure GRE on the mobile router: Configuring GRE Globally on the Mobile Router
SUMMARY STEPS
DETAILED STEPS Configuring GRE per Interface on the Mobile Router
SUMMARY STEPS
DETAILED STEPS
Configuring GRE Keepalive MessagesPerform this task on the mobile router to enable GRE keepalive messages. No configuration is required on the HA to respond to GRE keepalive messages from the mobile router. DETAILED STEPS
Configuration Examples for GRE for Cisco Mobile Networks
Configuring GRE for Cisco Mobile Networks Globally ExampleThe following example globally configures GRE encapsulation on a mobile router and enables GRE keepalive messages: router mobile ! ip mobile secure home-agent 10.40.40.1 spi 101 key hex 12345678123456781234567812345678 algorithm md5 mode prefix-suffix ip mobile router address 10.80.80.1 255.255.255.0 home-agent 10.40.40.1 mobile-network Ethernet1/3 mobile-network FastEthernet0/0 template Tunnel 121 tunnel mode gre ! interface tunnel 121 keepalive 5 3 Configuring GRE for Cisco Mobile Networks on an Interface ExampleThe following example configures GRE encapsulation on an interface of a mobile router and enables GRE keepalive messages: interface FastEthernet0/0 ip address 10.52.52.2 255.255.255.0 ip mobile router-service roam ip mobile router-service tunnel mode gre ! interface tunnel 121 keepalive 5 3 ! ip mobile router template tunnel 121 Verifying GRE for Cisco Mobile Networks ExamplesThe following example shows display output from the show ip mobile router registration command when GRE encapsulation is configured on the mobile router. The Flags field shows that GRE encapsulation is enabled by displaying a capital "G." If GRE encapsulation were not enabled, a lowercase "g" would be displayed. Router# show ip mobile router registration Mobile Router Registrations: Foreign agent 10.52.52.1: Registration accepted 01/11/00 07:01:24, On FastEthernet0/0 Care-of addr 10.52.52.1, HA addr 10.40.40.1, Home addr 10.80.80.1 Lifetime requested 10:00:00 (36000), Granted 01:00:00 (3600) Remaining 00:59:47 Flags sbdmG-t- , Identification B68B7673.81565B8 Register next time 00:59:27 Extensions: Mobile Network 172.16.153.0/24 Mobile Network 172.16.143.0/24 MN-HA Authentication SPI 101 The following example shows display output from the show ip mobile routercommand when GRE encapsulation is globally configured on the mobile router. When GRE encapsulation is enabled, the line "Request GRE tunnel" is displayed in the output and the tunnel mode is shown as "GRE/IP". Router# show ip mobile router Mobile Router Enabled 01/11/00 06:59:19 Last redundancy state transition NEVER Configuration: Home Address 10.80.80.1 Mask 255.255.255.0 Home Agent 10.40.40.1 Priority 100 (best) (current) Registration lifetime 65534 sec Retransmit Init 1000, Max 5000 msec, Limit 3 Extend Expire 20, Retry 10, Interval 1 Request GRE tunnel Mobile Networks:Ethernet1/3 (172.16.143.0/255.255.255.0) FastEthernet0/0 (172.16.153.0/255.255.255.0) Monitor: Status -Registered- Active foreign agent 10.52.52.1, Care-of 10.52.52.1 On interface FastEthernet0/0 Tunnel0 mode GRE/IP The following example shows display output from the show ip mobile router interface command when GRE encapsulation is configured on an interface of the mobile router. When GRE encapsulation is enabled on the interface, the line "Request GRE tunnel" is displayed in the output. Router# show ip mobile router interface FastEthernet0/0: Priority 110, Bandwidth 100000, Address 10.52.52.2 Periodic solicitation disabled, Interval 600 sec Retransmit Init 1000, Max 5000 msec, Limit 3 Current 2000, Remaining 0 msec, Count 2 Hold down 0 sec Routing disallowed Collocated CoA disabled Request GRE tunnel Additional ReferencesRelated Documents
MIBsTechnical AssistanceCommand ReferenceThe following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS IP Mobility Command Reference at http://www.cisco.com/en/US/docs/ios/ipmobility/command/reference/imo_book.html. For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List . Glossaryagent advertisement --An advertisement message constructed by an attachment of a special extension to an ICMP Router Discovery Protocol (IRDP) to advertise mobility services to potential users. agent discovery --The method by which a mobile node or mobile router determines whether it is currently connected to its home network or a foreign network and detects whether it has moved and the way it has moved. It is the mechanism by which mobile nodes or mobile routers query and discover mobility agents. Agent discovery is an extension to ICMP Router Discovery Protocol (IRDP) (RFC 1256), which includes a mechanism to advertise mobility services to potential users. care-of address --The termination point of the tunnel to a mobile node or mobile router. This can be a collocated care-of address, by which the mobile node or mobile router acquires a local address and detunnels its own packets, or a foreign agent care-of address, by which a foreign agent detunnels packets and forwards them to the mobile node or mobile router. FA --Foreign agent. A router on the visited network of a foreign network that provides routing services to the mobile node while registered. The foreign agent detunnels and delivers packets to the mobile node or mobile router that were tunneled by the home agent of the mobile node. For packets sent by a mobile node, the foreign agent may serve as a default router for registered mobile nodes. GRE --generic routing encapsulation. Tunneling protocol that can encapsulate a wide variety of protocol packet types inside IP tunnels, creating a virtual point-to-point link to routers at remote points over an IP internetwork. By connecting multiprotocol subnetworks in a single-protocol backbone environment, IP tunneling using GRE allows network expansion across a single-protocol backbone environment. HA --Home agent. A router on a home network of the mobile node that tunnels packets to the mobile node or mobile router while the mobile node or router is away from home. It keeps current location information for registered mobile nodes called a mobility binding . mobile network --A network that moves with the mobile router. A mobile network is a collection of hosts and routes that are fixed with respect to each other but are mobile, as a unit, with respect to the rest of the Internet. mobile router --A mobile node that is a router. It provides for the mobility of one or more entire networks moving together, perhaps on an airplane, a ship, a train, an automobile, a bicycle, or a kayak. The nodes connected to a network served by the mobile router may themselves be fixed nodes or mobile nodes or routers. registration --The process by which the mobile node is associated with a care-of address on the home agent while it is away from home. Registration may happen directly from the mobile node to the home agent or through a foreign agent. tunnel --The path followed by a packet while it is encapsulated from the home agent to the mobile node. The model is that, while the packet is encapsulated, it is routed to a knowledgeable decapsulating agent, which decapsulates the datagram and then correctly delivers it to its ultimate destination.
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.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|