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
Information
Description
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.
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 (optional)
IP address pool
name
name
Each IP address pool is identified by a name. The pool name can be between 1 and 31 alpha and/or numeric
characters and is case sensitive.
IP address pools are configured in the destination context(s). Multiple address pools can be configured within a
single context.
characters and is case sensitive.
IP address pools are configured in the destination context(s). Multiple address pools can be configured within a
single context.
IP pool
addresses
addresses
An initial address and a subnet, or a starting address and an ending address, are required for each configured
pool. The pool will then consist of every possible address within the subnet , or all addresses from the starting
address to the ending address.
The pool can be configured as public, private, or static.
pool. The pool will then consist of every possible address within the subnet , or all addresses from the starting
address to the ending address.
The pool can be configured as public, private, or static.
System-Level AAA Parameter Configuration
The following table lists the information that is required to configure the system-level AAA parameters.
Table 27.
Required Information for System-Level AAA Configuration
Required
Information
Information
Description
Subscriber
default domain
name
default domain
name
Specifies the name of a context that can provide AAA functions in the event that the domain-part of the
username is missing or poorly formed.
This parameter will be applied to all subscribers if their domain can not be determined from their username
regardless of what domain they are trying to access.
NOTE: The default domain name can be the same as the source context.
username is missing or poorly formed.
This parameter will be applied to all subscribers if their domain can not be determined from their username
regardless of what domain they are trying to access.
NOTE: The default domain name can be the same as the source context.