Cisco Cisco ASR 5700
Context Configuration Mode Commands I-M
ip pool ▀
Command Line Interface Reference, StarOS Release 17 ▄
2545
and VLAN. A maximum of 128 over-lapping pools can be configured per context and a maximum of 256
over-lapping pools can be configured per system.
over-lapping pools can be configured per system.
Important:
Overlapping IP address functionality is currently supported for use with systems configured as an
HA for Mobile IP, or as a PDSN for Simple IP, or as a GGSN. For deployments in which subscriber traffic is tunneled
from the FA to the HA using IP-in-IP, a separate HA service must be configured for each over-lapping pool.
from the FA to the HA using IP-in-IP, a separate HA service must be configured for each over-lapping pool.
IP Pool Address Assignment Method: IP addresses can be dynamically assigned from a single pool or from
a group of pools. The addresses are placed into a queue in each pool. An address is assigned from the head of
the queue and, when released, returned to the end. This method is known as least recently used (LRU).
When a group of pools have the same priority, an algorithm is used to determine a probability for each pool
based on the number of available addresses, then a pool is chosen based on the probability. This method, over
time, allocates addresses evenly from the group of pools.
a group of pools. The addresses are placed into a queue in each pool. An address is assigned from the head of
the queue and, when released, returned to the end. This method is known as least recently used (LRU).
When a group of pools have the same priority, an algorithm is used to determine a probability for each pool
based on the number of available addresses, then a pool is chosen based on the probability. This method, over
time, allocates addresses evenly from the group of pools.
Important:
Note that setting different priorities on each individual pool in a group can cause addresses in some
pools to be used more frequently.
Important:
In NAT IP pool configurations, the minimum number of public IP addresses that must be allocated to
each NAT pool must be greater than or equal to the number of Session Managers (SessMgrs) available on the system.
On the ASR 5000, it is >= 84 public IP addresses. This can be met by a range of 84 host addresses from a single Class
C. The remaining space from the Class C can be used for other allocations.
On the ASR 5000, it is >= 84 public IP addresses. This can be met by a range of 84 host addresses from a single Class
C. The remaining space from the Class C can be used for other allocations.
Example
The following commands define a private IP address pool, a public IP address pool, and a static address pool,
respectively.
respectively.
ip pool samplePool1 1.2.3.0 255.255.255.0 private
ip pool samplePool2 1.3.0.0 255.255.0.0 public
ip pool samplePool3 1.4.5.0 255.255.255.0 static
The following command defines a private IP pool specified with a range of IP addresses. The pool has 101
addresses.
addresses.
ip pool samplePool4 range 10.5.5.0 10.5.5.100 private
The following command sets the address hold timer on the pool to
60
minutes (
3600
seconds):
ip pool samplePool4 address-hold-timer 3600
The following command removes the IP address pool from the configuration:
no ip pool samplePool1
The following command creates a static IP pool:
ip pool pool1 100.1.1.0/24 static
The following command resizes the static IP pool created in the previous example:
ip pool pool1 100.1.1.0/25 static