Cisco Cisco Packet Data Interworking Function (PDIF) Guía Para Resolver Problemas
Simple IP and Mobile IP in a Single System Configuration Example
Using the System as Both a PDSN/FA and an HA ▀
Cisco ASR 5000 Series Packet Data Serving Node Administration Guide ▄
OL-22939-01
Required Information
Description
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 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 MD5.
A hash-algorithm is required for each SPI configured.
Replay-protection process:
Specifies how protection against replay-attacks is implemented. The possible processes are nonce and
timestamp. The default is timestamp with a tolerance of 60 seconds.
A replay-protection process is required for each SPI configured.
Specifies how protection against replay-attacks is implemented. The possible processes are nonce and
timestamp. The default is timestamp with a tolerance of 60 seconds.
A replay-protection process is required for each SPI configured.
Subscriber session
lifetime
lifetime
Specifies the time in seconds that an A10 connection can exist before its registration is considered
expired.
The time is expressed in seconds and can be configured to any integer value between 1 and 65534, or the
timer can be disabled to set an infinite lifetime. The default value is 1800 seconds.
expired.
The time is expressed in seconds and can be configured to any integer value between 1 and 65534, or the
timer can be disabled to set an infinite lifetime. The default value is 1800 seconds.
Mobile IP FA context
name
name
Specifies the name of the context in which the FA service is configured.
Default Subscriber Configuration
―Default‖ subscriber‘s
IP context name
IP 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.
AAA Context Configuration
The following table lists the information that is required to configure the AAA context.
Table 24.
Required Information for AAA Context Configuration
Required Information
Description
AAA context name
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the AAA
context will be recognized by the system.
context will be recognized by the system.
AAA Interface Configuration
AAA 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.
AAA interfaces will be configured in the source context.
interface will be recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
AAA interfaces will be configured in the source context.
IP address and subnet
These will be assigned to the AAA 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.
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.