Cisco Cisco Packet Data Gateway (PDG) Guía Para Resolver Problemas
Simple IP Configuration Examples
▀ Example 2: Simple IP Using a Single Source Context and Multiple Outsourced Destination Contexts
▄ Cisco ASR 5000 Series Packet Data Serving Node Administration Guide
OL-22939-01
The source context will facilitate the PDSN service(s), and the R-P interface(s). The source context will also be
configured with AAA interface(s) to provide AAA functionality for subscriber sessions. The destination contexts will
each be configured to facilitate PDN interfaces. In addition, because each of the destination contexts can be outsourced
to different domains, they will also be configured with AAA interface(s) to provide AAA functionality for that domain.
configured with AAA interface(s) to provide AAA functionality for subscriber sessions. The destination contexts will
each be configured to facilitate PDN interfaces. In addition, because each of the destination contexts can be outsourced
to different domains, they will also be configured with AAA interface(s) to provide AAA functionality for that domain.
In addition to the source and destination contexts, there are additional system-level AAA parameters that must be
configured.
configured.
Information Required
Prior to configuring the system as shown in this example, there is a minimum amount of information required. The
following sections describe the information required to configure the source and destination contexts.
following sections describe the information required to configure the source and destination contexts.
Source Context Configuration
The following table lists the information that is required to configure the source context.
Table 10.
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.
context will be recognized by the system.
R-P Interface Configuration
R-P 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.
R-P interfaces are configured in the source context.
will be recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
R-P interfaces are configured in the source context.
IP address and subnet
These will be assigned to the R-P 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.
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 source context and are used to bind logical R-P interfaces.
port will be recognized by the system.
Multiple descriptions are needed if multiple ports will be used.
Physical ports are configured within the source context and are used to bind logical R-P interfaces.
Gateway IP address
Used when configuring static routes from the R-P interface(s) to a specific network.
PDSN service Configuration