Important: This chapter does not discuss the configuration of the localout-of-band management context. Information about the localout-of-band 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 the section MIP Timer Considerations�.
NOTE: For this configuration, the IP context name should be identical to the name of the destination context.
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. NOTE: The system will only support multiple Mobile IP sessions per subscriber if the subscriber’s mobile node has a static IP address.
• Never require authentication (NOTE: the initial registration and de-registration will still be handled normally) NOTE: For this configuration, the IP context name should be identical to the name of the destination context.
NOTE: For this configuration, the destination context name should not match the domain name of a specific domain.
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.In this example, Subscriber1 is establishing a Simple IP data session, while Subscriber2 is establishing a Mobile IP data session.
•
• Subscriber username format = username @
2. The Default Subscriber was configured with an IP context name of SIP Destination.
3. The Mobile IP FA context name parameter within the PDSN service was configured to the MIP Destination context.
4. Sessions for Subscriber1 and Subscriber2 are received by the PDSN service over the R-P interface from the PCF.
5. For this configuration, the result of this process for both Subscriber1 and Subscriber2 would be that the system determines that AAA functionality should be provided by the AAA context.
6. The system would then communicate with the AAA server specified in the AAA context’s AAA configuration to authenticate the subscribers.
7. Upon successful authentication, the PDSN service will take the following actions for Subscriber1 and Subscriber2:
• Subscriber1: The system will go through the process of determining which destination context to use for the subscriber session. This process is described in the How the System Selects Contexts section located in the Understanding the System Operation and Configuration chapter of the System Administration Guide. For this configuration, the system determines that the egress context is the SIP Destination context based on the configuration of the Default subscriber in the Source context.
• Subscriber2: The system uses the Mobile IP FA context name configured within the PDSN service to determine what destination context facilitates the FA service. In this example, it determines that it must use the MIP Destination context and it passes the HA IP address to the FA service.
8. For Subscriber1’s session, data traffic would then be routed through the PDN interface in the SIP Destination context.
9. For Subscriber2, the FA service then establishes a connection to the specified HA service through the ICC interface.
10. For Subscriber2, the system would then communicate with the AAA server specified in the AAA context’s AAA configuration to authenticate the subscriber.
11. For Subscriber2, upon successful authentication, the MIP Destination context determines which destination context to use for the session and Mobile IP registration would be completed. This process is described in the How the System Selects Contexts section located in the Understanding the System Operation and Configuration chapter of the System Administration Guide.For this example, the Source context determines that the egress context is the MIP Destination context based on the configuration of the Default subscriber.
12. For Subscriber2’s session, data traffic would then be routed through the PDN interface in the MIP Destination context.
13.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |