Cisco Cisco Packet Data Gateway (PDG) Guia De Resolução De Problemas
ASN Gateway Service Operation and Configuration
How the System Selects Contexts ▀
Cisco ASR 5000 Series Access Service Network Gateway Administration Guide ▄
OL-22953-01
Destination Context Selection for Subscriber Sessions
This section provides information on how a destination context is selected for subscribers whose profiles are configured
on a RADIUS AAA server, and those whose profiles are locally configured. Note that the destination context for
context-level administrative users is always the local context.
on a RADIUS AAA server, and those whose profiles are locally configured. Note that the destination context for
context-level administrative users is always the local context.
The following table and figure describe the process that the system uses to select a destination context for a RADIUS-
based subscriber whose profile is configured on a RADIUS AAA server and for a subscriber whose profile is configured
within a specific context.
based subscriber whose profile is configured on a RADIUS AAA server and for a subscriber whose profile is configured
within a specific context.
Table 20.
Subscriber Destination Context Selection
Item
Description
1
The system supports a RADIUS attribute called SN1-VPN-name (or SN-VPN-name in some dictionaries). This attribute
specifies the name of the subscriber’s destination context. If configured in the subscriber’s RADIUS user profile, it is
returned as part of the Access Accept message.
If the SN1-VPN-Name attribute is returned, and it matches a configured context, then that context is used as the destination
context.
If the SN1-VPN-Name attribute is returned, and it does not match a configured context, the call is rejected.
If the SN1-VPN-Name attribute is not returned with a value, go to item 2 in this table.
specifies the name of the subscriber’s destination context. If configured in the subscriber’s RADIUS user profile, it is
returned as part of the Access Accept message.
If the SN1-VPN-Name attribute is returned, and it matches a configured context, then that context is used as the destination
context.
If the SN1-VPN-Name attribute is returned, and it does not match a configured context, the call is rejected.
If the SN1-VPN-Name attribute is not returned with a value, go to item 2 in this table.
2
The system attempts to use the ip context name parameter configuration for the realm-based subscriber template or context-
level default subscriber configured within the AAA context.
If a realm-based subscriber template does not exist, go to item 3 in this table.
If a realm-based subscriber template exists, the system checks to see if ip context-name is configured in the template.
If ip context-name is not configured in the template, the AAA context is used for the destination context.
If ip context-name is configured in the template, a check is made to see if it matches the name of a configured context.
If ip context-name is configured in the template, but does not match the name of a configured context, the call is rejected.
If ip context-name is configured in the template, and matches the name of a configured context, the destination context is
set to the ip name-context f or the default subscriber.
level default subscriber configured within the AAA context.
If a realm-based subscriber template does not exist, go to item 3 in this table.
If a realm-based subscriber template exists, the system checks to see if ip context-name is configured in the template.
If ip context-name is not configured in the template, the AAA context is used for the destination context.
If ip context-name is configured in the template, a check is made to see if it matches the name of a configured context.
If ip context-name is configured in the template, but does not match the name of a configured context, the call is rejected.
If ip context-name is configured in the template, and matches the name of a configured context, the destination context is
set to the ip name-context f or the default subscriber.
3
The local default subscriber profile contains an attribute called ip context-name. This attribute specifies the destination
context to use for a local subscriber.
If ip context-name is not configured, the AAA context is used for the destination context.
If ip context-name is configured, a check is made to see if it matches the name of a configured context.
If ip context-name is configured, but does not match the name of a configured context, the AAA context is used for the
destination context.
If ip context-name is configured, and matches the name of a configured context, the destination context is set to the ip
name-context for the default subscriber.
context to use for a local subscriber.
If ip context-name is not configured, the AAA context is used for the destination context.
If ip context-name is configured, a check is made to see if it matches the name of a configured context.
If ip context-name is configured, but does not match the name of a configured context, the AAA context is used for the
destination context.
If ip context-name is configured, and matches the name of a configured context, the destination context is set to the ip
name-context for the default subscriber.