Cisco Cisco Packet Data Interworking Function (PDIF) Guida Alla Risoluzione Dei Problemi
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
Description
Mobile IP 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. It should, however, match the name of the context in which the HA service is
configured if a separate system is used to provide HA functionality.
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. It should, however, match the name of the context in which the HA service is
configured if a separate system is used to provide HA 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.
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.
IP address and subnet
These will be assigned to the Pi 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
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 interface(s) to a specific network.
FA Service Configuration
FA service name
This is an identification string between 1 and 63 characters (alpha and/or numeric) by which the FA
service will be recognized by the system.
Multiple names are needed if multiple FA services will be used.
FA services are configured in the destination context.
service will be recognized by the system.
Multiple names are needed if multiple FA services will be used.
FA services are configured in the destination context.
UDP port number for
Mobile IP traffic
Mobile IP traffic
Specifies the port used by the FA service and the HA for communications. The UDP port number
can be any integer value between 1 and 65535. The default value is 434.
can be any integer value between 1 and 65535. The default value is 434.
Security Parameter Index
(indices) Information
(indices) Information
HA IP address:
Specifies the IP address of the HAs with which the FA service communicates. The FA service
allows the creation of a security profile that can be associated with a particular HA.
Specifies the IP address of the HAs with which the FA service communicates. The FA service
allows the creation of a security profile that can be associated with a particular HA.
Index:
Specifies the shared SPI between the FA service and a particular HA. The SPI can be configured to
any integer value between 256 and 4294967295. Multiple SPIs can be configured if the FA service
is to communicate with multiple HAs.
Specifies the shared SPI between the FA service and a particular HA. The SPI can be configured to
any integer value between 256 and 4294967295. Multiple SPIs can be configured if the FA service
is to communicate with multiple HAs.
Secrets:
Specifies the shared SPI secret between the FA service and the HA. The secret can be between 1
and 127 characters (alpha and/or numeric).An SPI secret is required for each SPI configured.
Specifies the shared SPI secret between the FA service and the HA. The secret can be between 1
and 127 characters (alpha and/or numeric).An SPI secret is required for each SPI configured.
Hash-algorithm:
Specifies the algorithm used to hash the SPI and SPI secret. The possible algorithms that can be
configured are MD5 per RFC 1321 and keyed-MD5 per RFC 2002. The default is hmac-md5.
A hash-algorithm is required for each SPI configured.
Specifies the algorithm used to hash the SPI and SPI secret. The possible algorithms that can be
configured are MD5 per RFC 1321 and keyed-MD5 per RFC 2002. The default is hmac-md5.
A hash-algorithm is required for each SPI configured.