Руководство По Устранению Ошибки для Cisco Cisco Packet Data Gateway (PDG)
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
Source Context Configuration
The following table lists the information that is required to configure the source context.
Table 2. Required Information for Source Context Configuration
Required Information
Description
Source context name
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the
source context will be recognized by the system.
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.
source context will be recognized by the system.
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.
Pi Interface Configuration
Pi interface 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.
Pi interfaces are configured in the destination context.
If this interface is being used for Interchassis Session Recovery, you must specify a loopback
interface type after the interface_name.
interface will be recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
Pi interfaces are configured in the destination context.
If this interface is being used for Interchassis Session Recovery, you must specify a loopback
interface type after the interface_name.
IP address and subnet
These will be assigned to the Pi interfaces.Multiple addresses and/or subnets are needed if multiple
interfaces will be configured.
interfaces will be configured.
Physical port 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.
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
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 Pi interfaces.
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 Pi interfaces.
Gateway IP address(es)
Used when configuring static routes from the Pi interfaces to a specific network.
HA service Configuration
HA service name
This is an identification string between 1 and 63 characters (alpha and/or numeric) by which the HA
service will be recognized by the system.
Multiple names are needed if multiple HA services will be used.
HA services are configured in the destination context.
service will be recognized by the system.
Multiple names are needed if multiple HA services will be used.
HA services are configured in the destination context.
UDP port number for
Mobile IP traffic
Mobile IP traffic
Specifies the port used by the HA service and the FA for communications. The UDP port number can
be any integer value between 1 and 65535. The default value is 434.
be any integer value between 1 and 65535. The default value is 434.
Mobile node re-
registration requirements
registration requirements
Specifies how the system should handle authentication for mobile node re-registrations.The HA
service can be configured as follows:
service can be configured as follows:
Always require authentication
Never require authentication (NOTE: the initial registration and de-registration will still be
handled normally)
handled normally)
Never look for mn-aaa extension
Not require authentication but will authenticate if mn-aaa extension present