Cisco Cisco ASR 5700
Context Configuration Mode Commands I-M
▀ ip pool
▄ Command Line Interface Reference, StarOS Release 17
2544
Important:
In static allocation scenario, the pool group name is returned by AAA in the attribute SN1-IP-Pool-
Name, and the IP address to use will be returned in the Framed-IP-Address attribute.
framed-route-vrf-listvrf_list_name
Configures a vrf-list in order for NVSE VRF authorization.
pool-route
ip_address/ip_mask
Configures the IP pool route instead of generating by-default. The address followed by the
pool-route
keyword can be an IPv4 or IPv6 address with the mask value.
+
Indicates that more than one of the previous keywords can be entered within a single command.
Usage
Define one or more pools of IP addresses for the context to use in assigning IPs to mobile stations. This
command is also useful in resizing existing IP pools to expand or contract the number of addresses allocated.
If you resize an IP pool, the change is effective immediately.
When using the
command is also useful in resizing existing IP pools to expand or contract the number of addresses allocated.
If you resize an IP pool, the change is effective immediately.
When using the
ip pool
command to resize an IP pool, the type must be specified since by default the
command assumes the type as public. In other words, the CLI syntax to resize an IP pool is the same syntax
used to create the pool. See examples below.
used to create the pool. See examples below.
ip pool pool1 100.1.1.0/24 static
The syntax to resize that pool would be:
ip pool pool1 100.1.1.0/25 static
A pool which is deleted will be marked as such. No new IP addresses will be assigned from a deleted pool.
Once all assigned IP addresses from a deleted pool have been released, the pool, and all associated resources,
are freed.
Once all assigned IP addresses from a deleted pool have been released, the pool, and all associated resources,
are freed.
Important:
If an IP address pool is matched to a ISAKMP crypto map and is resized, removed, or added, the
corresponding security association must be cleared in order for the change to take effect. Refer to the
clear crypto
command in the Exec mode for information on clearing security associations.
Over-lapping IP Pools: The system supports the configuration of over-lapping IP address pools within a
particular context. Over-lapping pools are configured using either the resource or overlap keywords.
The
particular context. Over-lapping pools are configured using either the resource or overlap keywords.
The
resource
keyword allows over-lapping addresses tunneled to different VPN end points.
The
overlap
keyword allows over-lapping addresses each associated with a specific virtual LAN (VLAN)
configured for an egress port. It uses the VLAN ID and the nexthop address to determine how to forward
subscriber traffic with addresses from the pool thus resolving any conflicts with overlapping addresses.
Note that if an overlapping IP Pool is bound to an IPSec Tunnel (refer to the
subscriber traffic with addresses from the pool thus resolving any conflicts with overlapping addresses.
Note that if an overlapping IP Pool is bound to an IPSec Tunnel (refer to the
match ip pool
command in
the Crypto Group Configuration Mode chapter), that tunnel carries the traffic ignoring the nexthop
configuration. Therefore, the IPSec Tunnel takes precedence over the nexthop configuration. (Thus, one can
configure the overlapping IP Pool with fake VLAN ID and nexthop and still be able to bind it to an IPSec
Tunnel for successful operation.
The
configuration. Therefore, the IPSec Tunnel takes precedence over the nexthop configuration. (Thus, one can
configure the overlapping IP Pool with fake VLAN ID and nexthop and still be able to bind it to an IPSec
Tunnel for successful operation.
The
overlap
keyword allows over-lapping addresses each associated with a specific VLAN can only be
issued for pools of type private or static and must be associated with a different nexthop forwarding address