Cisco Cisco Packet Data Gateway (PDG) Guia De Resolução De Problemas
Mobile IP Configuration Examples
Example 1: Mobile IP Support Using the System as a PDSN/FA ▀
Cisco ASR 5000 Series Packet Data Serving Node Administration Guide ▄
OL-22939-01
Required
Information
Information
Description
Subscriber
username
format
username
format
Specifies the format of subscriber usernames as to whether or not the username or domain is specified first and
the character that separates them. The possible separator characters are:
the character that separates them. The possible separator characters are:
@
%
-
\
#
/
Up to six username formats can be specified. The default is username @.
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.
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.
This context is required if: 1) reverse tunneling is disabled in the FA service, or 2) if access control lists (ACLs) are
used.
Table 17. Required Information for Destination Context Configuration
Required
Information
Information
Description
Destination
context name
context name
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.
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.
PDN Interface Configuration
PDN interface
name
name
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the interface will
be recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
PDN interfaces are configured in the destination context.
be recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
PDN interfaces are configured in the destination context.
IP address and
subnet
subnet
These will be assigned to the PDN interface.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured.
Physical port
number
number
This specifies the physical port to which the interface will be bound. Ports are identified by the chassis slot
number where the line card resides in, followed by the number of the physical connector on the line card. For
example, port 17/1 identifies connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces.
number where the line card resides in, followed by the number of the physical connector on the line card. For
example, port 17/1 identifies connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces.