Руководство Администратора для Cisco Cisco Packet Data Gateway (PDG)
Simple IP and Mobile IP in a Single System Configuration Example
▀ Using the System as Both a PDSN/FA and an HA
▄ Cisco ASR 5x00 Home Agent Administration Guide
56
Mobile IP Destination Context Configuration
The following table lists the information that is required to configure the destination context.
Table 9. Required Information for Destination Context Configuration
Required Information
Description
Mobile IP Destination
context name
context name
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the
Mobile IP destination context will be recognized by the system.
Mobile IP destination context will be recognized by the system.
Important:
For this configuration, the destination context name should not match
the domain name of a specific domain. It should, however, match the name of the context
in which the HA service is configured if a separate system is used to provide HA
functionality.
in which the HA service is configured if a separate system is used to provide HA
functionality.
ICC Interface Configuration
ICC interface name
The intra-context communication (ICC) interface is configured to allow FA and HA services
configured within the same context to communicate with each other.
The ICC interface name 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.
ICC interface(s) are configured in the same destination context as the FA and HA services.
configured within the same context to communicate with each other.
The ICC interface name 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.
ICC interface(s) are configured in the same destination context as the FA and HA services.
IP address and subnet
These will be assigned to the ICC interface(s).
Multiple addresses (at least one per service) on the same subnet will be needed to assign to the same
ICC interface.
Multiple addresses (at least one per service) on the same subnet will be needed to assign to the same
ICC interface.
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 multiple ports will be used.
Physical ports are configured within the destination context and are used to bind logical ICC
interfaces.
physical port will be recognized by the system.
Multiple descriptions are needed if multiple ports will be used.
Physical ports are configured within the destination context and are used to bind logical ICC
interfaces.
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.
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.
IP address and 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
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.