Cisco Cisco ASR 5500
Mobile IP Configuration Examples
Example 1: Mobile IP Support Using the System as an HA ▀
HA Administration Guide, StarOS Release 18 ▄
45
Required
Information
Information
Description
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.
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.
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 destination context and are used to bind logical PDN interfaces.
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 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
IP address pool
name
name
Each IP address pool is identified by a name.
The pool name can be between 1 and 31 alpha and/or numeric characters and is case sensitive.
IP address pools are configured in the destination context(s).
Multiple address pools can be configured within a single context.
The pool name can be between 1 and 31 alpha and/or numeric characters and is case sensitive.
IP address pools are configured in the destination context(s).
Multiple address pools can be configured within a single context.
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.
If this IP pool is being used for Interchassis Session Recovery, it must be a static and srp-activated.
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.
If this IP pool is being used for Interchassis Session Recovery, it must be a static and srp-activated.
How This Configuration Works
The following figure and the text that follows describe how this configuration with a single source and destination
context would be used by the system to process a Mobile IP data call.
context would be used by the system to process a Mobile IP data call.