Руководство По Устранению Ошибки для Cisco Cisco Tunnel Terminating Gateway (TTG)
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
Required Information
Description
―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.
Destination Context Configuration
The following table lists the information that is required to configure the destination context.
Table 11.
Required Information for Destination Context Configuration
Required Information
Description
Destination context
name
name
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the
destination context will be recognized by the system.
NOTE: For this configuration, the destination context name should not match the domain name of a
specific domain.
destination context will be recognized by the system.
NOTE: For this configuration, the destination context name should not match the domain name of a
specific domain.
PDN Interface Configuration
PDN 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.
PDN interfaces are configured in the destination context.
will 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(s)
description(s)
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 will be needed if multiple ports will be used.
Physical ports are configured within the destination context and are used to bind logical PDN interfaces.
port will be recognized by the system.
Multiple descriptions will be 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(s)
name(s)
If IP address pools will be configured in the destination context(s), names or identifiers will be needed for
them. The pool name can be between 1 and 31 alpha and/or numeric characters and is case sensitive.
them. The pool name can be between 1 and 31 alpha and/or numeric characters and is case sensitive.
IP pool 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.
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.
AAA Interface Configuration