Cisco Cisco Packet Data Gateway (PDG) Guida Alla Risoluzione Dei Problemi
Simple IP Configuration Examples
Example 1: Simple IP Support Using a Single Source and Destination Context ▀
Cisco ASR 5000 Series Packet Data Serving Node Administration Guide ▄
OL-22939-01
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 8. 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
PDSN service name
This is an identification string between 1 and 63 characters (alpha and/or numeric) by which the PDSN
service will be recognized by the system.
Multiple names are needed if multiple PDSN services will be used.
PDSN services are configured in the source context.
service will be recognized by the system.
Multiple names are needed if multiple PDSN services will be used.
PDSN services are configured in the source context.
UDP port number for
R-P traffic
R-P traffic
Specifies the port used by the PDSN service and the PCF for communications. The UDP port number
and can be any integer value between 1 and 65535. The default value is 699.
and can be any integer value between 1 and 65535. The default value is 699.
Authentication
protocols used
protocols used
Specifies how the system handles authentication: using a protocol (such as CHAP, PAP, or MSCHAP),
or not requiring any authentication.
or not requiring any authentication.
Domain alias for NAI-
construction
construction
Specifies a context name for the system to use to provide accounting functionality for a subscriber
session. This parameter is needed only if the system is configured to support no authentication.
session. This parameter is needed only if the system is configured to support no authentication.