Mobile IP Configuration Examples


Mobile IP Configuration Examples
 
 
This chapter provides information for several configuration examples that can be implemented on the system to support Mobile IP (MIP) data services.
Important: This chapter does not discuss the configuration of the local management context. Information about the local management context can be found in Chapter 1 of Command Line Reference. Additionally, when configuring Mobile IP take into account the MIP timing considerations discussed in MIP Timer Considerations.
 
Example 1: Mobile IP Support Using the System as a PDSN/FA
The system supports both Simple and Mobile IP. For Mobile IP applications, the system can be configured to perform the function of a Packet Data Serving Node/Foreign Agent (PDSN/FA) and/or a Home Agent (HA). This example describes what is needed for and how the system performs the role of the PDSN/FA. Examples 2 and 3 provide information on using the system to provide HA functionality.
The system’s PDSN/FA configuration for Mobile IP applications is best addressed with three contexts (one source, one AAA, and one Mobile IP destination) configured as shown in the figure below.
 
Important: A fourth context that serves as a destination context must also be configured if Reverse Tunneling is disabled in the FA service configuration. Reverse Tunneling is enabled by default.
The source context will facilitate the PDSN service(s), and the R-P interfaces. The AAA context will be configured to provide foreign AAA functionality for subscriber sessions and facilitate the AAA interfaces. The MIP destination context will facilitate the FA service(s) and the Pi interface(s) from the PDSN/FA to the HA.
The optional destination context will allow the routing of data from the mobile node to the packet data network by facilitating a packet data network (PDN) interface. This context will be used only if reverse tunneling was disabled.
 
Mobile IP Support using the system as a PDSN/FA
 
Information Required
Prior to configuring the system as shown in this example, there is a minimum amount of information required. The following sections describe the information required to configure the source and destination contexts.
 
Source Context Configuration
The following table lists the information that is required to configure the source context.
Required Information for Source Context Configuration
 
AAA Context Configuration
The following table lists the information that is required to configure the AAA context.
Required Information for AAA Context Configuration
NOTE: If a separate system is used to provide HA functionality, the AAA context name should match the name of the context in which the AAA functionality is configured on the HA machine.
 
Mobile IP Destination Context Configuration
The following table lists the information required to configure the destination context.
Required Information for Destination Context Configuration
NOTE: For this configuration, the destination context name should not match the domain name of a specific domain. It should, however, match the name of the context in which the HA service is configured if a separate system is used to provide HA functionality.
 
System-Level AAA Configuration
The following table lists the information that is required to configure the system-level AAA parameters.
Required Information for System-Level AAA Configuration
NOTE: The default domain name can be the same as the source context.
NOTE: The last-resort context name can be the same as the source context.
NOTE: The username string is searched from right to left for the separator character. Therefore, if there is one or more separator characters in the string , only the first one that is recognized is considered the actual separator. For example, if the default username format was used, then for the username string user1@enterprise@isp1, the system resolves to the username user1@enterprise with domain isp1.
 
Optional Destination Context
The following table lists the information required to configure the optional destination context. As discussed previously, This context is required if: 1) reverse tunneling is disabled in the FA service, or 2) if access control lists (ACLs) are used.
Required Information for Destination Context Configuration
NOTE: For this configuration, the destination context name should not match the domain name of a specific domain.
 
How This Configuration Works
The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a Mobile IP data call.
Call Processing When Using the system as a PDSN/FA
 
1.
2.
3.
For this example, the result of this process is that PDSN service determined that foreign AAA functionality should be provided by the AAA context.
4.
5.
The PDSN service uses the Mobile IP FA context name to determine what destination context is facilitating the FA service. In this example, it determines that it must use the MIP Destination context.
6.
7.
8.
9.
 
Example 2: Mobile IP Support Using the System as an HA
The system supports both Simple and Mobile IP. For Mobile IP applications, the system can be configured to perform the function of a PDSN/FA and/or a HA. This example describes what is needed for and how the system performs the role of the HA. Example number 1 provides information on using the system to provide PDSN/FA functionality.
The system’s HA configuration for Mobile IP applications requires that at least two contexts (one source and one destination) be configured as shown in the following figure .
Mobile IP Support Using the system as an HA
The source context will facilitate the HA service(s), the Pi interfaces from the FA, and the AAA interfaces. The source context will also be configured to provide Home AAA functionality for subscriber sessions. The destination context will facilitate the PDN interface(s).
 
Information Required
Prior to configuring the system as shown in this example, there is a minimum amount of information required. The following sections describe the information required to configure the source and destination contexts.
 
Source Context Configuration
The following table lists the information that is required to configure the source context.
Required Information for Source Context Configuration
 
Destination Context Configuration
The following table lists the information required to configure the destination context.
Required Information for Destination Context Configuration
NOTE: For this configuration, the destination context name should not match the domain name of a specific domain.
 
How This Configuration Works
The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a Mobile IP data call.
Call Processing When Using the system as a PDSN/FA
 
1.
2.
3.
For this example, the result of this process is that PDSN service determined that foreign AAA functionality should be provided by the AAA context.
4.
5.
The PDSN service uses the Mobile IP FA context name to determine what destination context is facilitating the FA service. In this example, it determines that it must use the MIP Destination context.
6.
7.
8.
9.
 
Example 3: HA Using a Single Source Context and Multiple Outsourced Destination Contexts
The system allows the wireless carrier to easily generate additional revenue by providing the ability to configure separate contexts that can then be leased or outsourced to various enterprises or ISPs, each having a specific domain.
In order to perform the role of an HA and support multiple outsourced domains, the system must be configured with at least one source context and multiple destination contexts as shown in the following figure. The AAA servers could by owned/maintained by either the carrier or the domain. If they are owned by the domain, the carrier will have to receive the AAA information via proxy.
The system as an HA Using a Single Source Context and Multiple Outsourced Destination Contexts
The source context will facilitate the HA service(s), and the Pi interface(s) to the FA(s).The source context will also be configured with AAA interface(s) and to provide Home AAA functionality for subscriber sessions. The destination contexts will each be configured to facilitate PDN interfaces. In addition, because each of the destination contexts can be outsourced to different domains, they will also be configured with AAA interface(s) and to provide AAA functionality for that domain.
In addition to the source and destination contexts, there are additional system-level AAA parameters that must be configured.
 
Information Required
Prior to configuring the system as shown in this example, there is a minimum amount of information required. The following sections describe the information required to configure the source and destination contexts.
 
Source Context Configuration
The following table lists the information that is required to configure the source context.
Required Information for Source Context Configuration
 
Destination Context Configuration
The following table lists the information required to configure the destination context.
Required Information for Destination Context Configuration
NOTE: For this configuration, the destination context name should not match the domain name of a specific domain.
 
System-Level AAA Configuration
The following table lists the information that is required to configure the system-level AAA parameters.
Required Information for System-Level AAA Configuration
NOTE: The default domain name can be the same as the source context.
NOTE: The last-resort context name can be the same as the source context.
NOTE: The username string is searched from right to left for the separator character. Therefore, if there is one or more separator characters in the string , only the first one that is recognized is considered the actual separator. For example, if the default username format was used, then for the username string user1@enterprise@isp1, the system resolves to the username user1@enterprise with domain isp1.
 
How This Configuration Works
The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a Mobile IP data call.
Call Processing When Using the system as a PDSN/FA
 
1.
2.
3.
For this example, the result of this process is that PDSN service determined that foreign AAA functionality should be provided by the AAA context.
4.
5.
The PDSN service uses the Mobile IP FA context name to determine what destination context is facilitating the FA service. In this example, it determines that it must use the MIP Destination context.
6.
7.
8.
 
 
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883