Cisco Cisco IOS Software Release 12.4(15)XM Technische Referenzen
ip local pool
42
Cisco Mobile Wireless Home Agent Feature for IOS Release 12.4(15)XM2
12.4(15)XM2
Usage Guidelines
Use the ip local pool command to create one or more local address pools from which IP addresses are
assigned when a peer connects. You may also add another range of IP addresses to an existing pool. To
use a named IP address pool on an interface, use the peer default ip address pool interface
configuration command. A pool name can also be assigned to a specific user using authentication,
authorization, and accounting (AAA) RADIUS and TACACS functions.
assigned when a peer connects. You may also add another range of IP addresses to an existing pool. To
use a named IP address pool on an interface, use the peer default ip address pool interface
configuration command. A pool name can also be assigned to a specific user using authentication,
authorization, and accounting (AAA) RADIUS and TACACS functions.
If no named local IP address pool is created, a default address pool is used on all point-to-point interfaces
after the ip address-pool local global configuration command is issued. If no explicit IP address pool is
assigned, but pool use is requested by use of the ip address-pool local command, the special pool named
“default” is used.
after the ip address-pool local global configuration command is issued. If no explicit IP address pool is
assigned, but pool use is requested by use of the ip address-pool local command, the special pool named
“default” is used.
The optional group keyword and associated group name allows the association of an IP address pool
with a named group. Any IP address pool created without the group keyword automatically becomes a
member of a base system group.
with a named group. Any IP address pool created without the group keyword automatically becomes a
member of a base system group.
An IP address pool name can be associated with only one group. Subsequent use of the same pool name,
within a pool group, is treated as an extension of that pool, and any attempt to associate an existing local
IP address pool name with a different pool group is rejected. Therefore, each use of a pool name is an
implicit selection of the associated pool group.
within a pool group, is treated as an extension of that pool, and any attempt to associate an existing local
IP address pool name with a different pool group is rejected. Therefore, each use of a pool name is an
implicit selection of the associated pool group.
Note
To reduce the chances of inadvertent generation of duplicate addresses, the system allows creation of the
special pool named “default” only in the base system group, that is, no group name can be specified with
the pool name “default.”
special pool named “default” only in the base system group, that is, no group name can be specified with
the pool name “default.”
All IP address pools within a pool group are checked to prevent overlapping addresses; however, no
checks are made between any group pool member and a pool not in a group. The specification of a named
pool within a pool group allows the existence of overlapping IP addresses with pools in other groups,
and with pools in the base system group, but not among pools within a group. Otherwise, processing of
the IP address pools is not altered by their membership in a group. In particular, these pool names can
be specified in peer commands and returned in RADIUS and AAA functions with no special processing.
checks are made between any group pool member and a pool not in a group. The specification of a named
pool within a pool group allows the existence of overlapping IP addresses with pools in other groups,
and with pools in the base system group, but not among pools within a group. Otherwise, processing of
the IP address pools is not altered by their membership in a group. In particular, these pool names can
be specified in peer commands and returned in RADIUS and AAA functions with no special processing.
IP address pools can be associated with Virtual Private Networks (VPNs). This association permits
flexible IP address pool specifications that are compatible with a VPN and a VPN routing and forwarding
instance (VRF).
flexible IP address pool specifications that are compatible with a VPN and a VPN routing and forwarding
instance (VRF).
The IP address pools can also be used with the translate commands for one-step vty-async connections
and in certain AAA or TACACS+ authorization functions. Refer to the chapter “Configuring Protocol
Translation and Virtual Asynchronous Devices” in the Cisco IOS Terminal Services Configuration Guide
and the “System Management” part of the Cisco IOS Configuration Fundamentals Configuration Guide
for more information.
and in certain AAA or TACACS+ authorization functions. Refer to the chapter “Configuring Protocol
Translation and Virtual Asynchronous Devices” in the Cisco IOS Terminal Services Configuration Guide
and the “System Management” part of the Cisco IOS Configuration Fundamentals Configuration Guide
for more information.
Low and High Thresholds
Cisco Mobile Wireless Home Agent Release 3.1 enhanced the CISCO-IP-LOCAL-POOL-MIB to
generate traps when pool utilization reached a low threshold or high threshold in percentage. Objects
“cIpLocalPoolPercentAddrThldLo” and “cIpLocalPoolPercentAddrThldHi” are defined for the high and
low threshold watermark, respectively.
generate traps when pool utilization reached a low threshold or high threshold in percentage. Objects
“cIpLocalPoolPercentAddrThldLo” and “cIpLocalPoolPercentAddrThldHi” are defined for the high and
low threshold watermark, respectively.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T and support
was added for the Cisco 6400 node route processor 25v (NRP-25v) and
Cisco 7400 platforms.
was added for the Cisco 6400 node route processor 25v (NRP-25v) and
Cisco 7400 platforms.
12.3(14)YX5
The low-threshold and high-threshold variables were added.
Release
Modification