Cisco Cisco Packet Data Gateway (PDG) Guia De Resolução De Problemas
Mobile IP Configuration Examples
▀ Example 3: HA 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 HA service(s), and the Pi interface(s) to the FA(s).The source context will also be
configured with AAA interface(s) and to provide Home 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) and to provide AAA
functionality for that domain.
configured with AAA interface(s) and to provide Home 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) and 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 20.
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.
source context will be recognized by the system.
Pi Interface Configuration
Piinterface 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.
Pi interfaces are configured in the source context.
interface will be recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
Pi interfaces are configured in the source context.
IP address and subnet
These will be assigned to the Pi 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.
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.
Physical port 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 using multiple ports.
Physical ports are configured within the source context and are used to bind logical Pi interfaces.
physical port will be recognized by the system.
Multiple descriptions are needed if using multiple ports.
Physical ports are configured within the source context and are used to bind logical Pi interfaces.
Gateway IP address
Used when configuring static routes from the Pi interface(s) to a specific network.
HA service Configuration