Important: This chapter does not discuss the configuration of the local context. Information about the local 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 Mobile-IP and Proxy-MIP Timer Considerations.
NOTE: The name of the source context should be the same as the name of the context in which the FA-context is configured if a separate system is being used to provide PDSN/FA functionality.
• 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.
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the destination context will be recognized by the system.NOTE: For this configuration, the destination context name should not match the domain name of a specific domain.
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.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |