Cisco ASR 5000 Series Administration Manual page 141

Mobile IP Configuration Examples
Subscriber username format =
No subscriber last-resort context name was configured
2. The subscriber IP context names were configured as follows:
Within the Source context, the IP context name was configured as
Within the Domainx context, the IP context name was configured as
3. Sessions are received by the HA service from the FA over the Gi interface for subscriber1@Domain1,
subscriber2, and subscriber3@Domain37.
4. The HA service attempts to determine the domain names for each session.
For subscriber1, the HA service determines that a domain name is present and is Domain1.
For subscriber2, the HA service determines that no domain name is present.
For subscriber3, the HA service determines that a domain name is present and is Domain37.
5. The HA service determi nes which context to use to provide AAA functionality for the 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 subscriber1, the HA service determines that a context was configured with a name (Domain1) that
For subscriber2, the HA service determines that Domainx is configured as the default domain name.
For subscriber3, the HA service determines that no context is configured that matches the domain name
6. The system then communicates with the Home AAA server specified in the Source context‟s AAA configuration
to authenticate the subscriber.
7. Upon successful authentication of all three subscribers, the HA service determines which destination context to
use for each of the subscriber sessions. 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 subscriber1, the HA service receives the SN-VPN-NAME or SN1-VPN-NAME attribute equal to
For subscriber2, the HA service determines that the SN-VPN-NAME or SN1-VPN-NAME attribute was
For subscriber3, the HA service determines that the SN-VPN-NAME or SN1-VPN-NAME attribute was
8. Data traffic for the subscriber session is then routed through the PDN interface in the each subscriber‟s
destination context.
9. Accounting messages for the session are sent to the AAA server over the appropriate AAA interface.
OL-22944-02
matches the domain name specified in the username string. Therefore, Domain1 is used.
Therefore, Domainx is used.
(Domain37) specified in the username string. Because no last-resort context name was configured,
the Source context is used.
Domain1 as part of the Authentication Accept message from the AAA server on Domain1‟s network.
Therefore, Domain1 is used as the destination context.
not returned with the Authentication Accept response, and determines the subscriber IP context name
configured within the Domainx context. Therefore, the Domainx context is used as the destination
context.
not returned with the Authentication Accept response, and determines the subscriber IP context name
configured within the Source context. Therefore, the Source context is used as the destination context.
Example 3: HA Using a Single Source Context and Multiple Outsourced Destination Contexts ▀
@
Cisco ASR 5000 Series Gateway GPRS Support Node Administration Guide ▄