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 an HA ▀
Cisco ASR 5000 Series Home Agent Administration ▄
OL-22980-01
Required Information
Description
RADIUS attribute NAS
Identifier
Identifier
Specifies the name by which the source context will be identified in the Access-Request message(s) it
sends to the home RADIUS server. The name must be between 1 and 32 alpha and/or numeric
characters and is case sensitive.
sends to the home RADIUS server. The name must be between 1 and 32 alpha and/or numeric
characters and is case sensitive.
RADIUS NAS IP address
Specifies the IP address of the source context’s AAA interface. A secondary address can be optionally
configured.
configured.
Default Subscriber Configuration
“Default” subscriber’s IP
context name
context name
Specifies the name of the egress context on the system that facilitates the PDN ports.
NOTE: For this configuration, the IP context name should be identical to the name of the destination
context.
NOTE: For this configuration, the IP context name should be identical to the name of the destination
context.
Destination Context Configuration
The following table lists the information required to configure the destination context.
Table 3. 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.
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.
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.
Physical port
description
description
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the physical port
will be recognized by the system.
Multiple descriptions are needed if multiple ports will be used.
Physical ports are configured within the destination context and are used to bind logical PDN interfaces.
will be recognized by the system.
Multiple descriptions are needed if multiple ports will be used.
Physical ports are configured within the destination context and are used to bind logical PDN interfaces.
Gateway IP
address(es)
address(es)
Used when configuring static routes from the PDN interface(s) to a specific network.
IP Address Pool Configuration