Cisco Cisco Packet Data Gateway (PDG) Guía Para Resolver Problemas
PDN Gateway Configuration
▀ Configuring the System as a Standalone eGTP P-GW
▄ Cisco ASR 5000 Series Packet Data Network Gateway Administration Guide
OL-22985-01
Configuring the System as a Standalone eGTP P-GW
This section provides a high-level series of steps and the associated configuration file examples for configuring the
system to perform as a eGTP P-GW in a test environment. For a complete configuration file example, refer to the
Sample Configuration Files appendix. Information provided in this section includes the following:
system to perform as a eGTP P-GW in a test environment. For a complete configuration file example, refer to the
Sample Configuration Files appendix. Information provided in this section includes the following:
Information Required
The following sections describe the minimum amount of information required to configure and make the P-GW
operational on the network. To make the process more efficient, it is recommended that this information be available
prior to configuring the system.
operational on the network. To make the process more efficient, it is recommended that this information be available
prior to configuring the system.
There are additional configuration parameters that are not described in this section. These parameters deal mostly with
fine-tuning the operation of the P-GW in the network. Information on these parameters can be found in the appropriate
sections of the Command Line Interface Reference.
fine-tuning the operation of the P-GW in the network. Information on these parameters can be found in the appropriate
sections of the Command Line Interface Reference.
Required Local Context Configuration Information
The following table lists the information that is required to configure the local context on an P-GW.
Table 9. Required Information for Local Context Configuration
Required
Information
Description
Management Interface Configuration
Interface name
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.
recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
IP address and
subnet
subnet
IPv4 addresses assigned to the interface.
Multiple addresses and subnets are needed if multiple interfaces will be configured.
Multiple addresses and subnets are needed if multiple interfaces will be configured.
Physical port
number
number
The physical port to which the interface will be bound. Ports are identified by the chassis slot number
where the line card resides followed by the number of the physical connector on the card. For example, port
17/1 identifies connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces.
where the line card resides followed by the number of the physical connector on the card. For example, port
17/1 identifies connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces.