Cisco Cisco Packet Data Interworking Function (PDIF) Guía Para Resolver Problemas
IP Pool Sharing Protocol
Overview ▀
Cisco ASR 5000 Series Enhanced Feature Configuration Guide ▄
OL-22983-01
Communicates with the primary HA, as needed, to request IP addresses that are not currently assigned to it; it
does not assign the address until the primary HA approves it
For graceful termination conditions (e.g. an administrative user issues the
command), it notifies the
primary HA that it is going out of service
Assumes the responsibility of the primary HA when requested to
In the event that it determines that primary HA is not available, it assumes the responsibility of the primary HA
if there is at least one address allocated to verify that the AAA server is re-configured to direct the calls
Requirements, Limitations, & Behavior
One IPSP interface can be configured per system context.
The IPSP interfaces for both the primary and secondary HAs must be configured to communicate on the same
network.
If IP pool busyout is enabled on any configured address pool, IPSP can not be configured.
The IP pool configuration (pool name, addresses, priority, pool group, etc.) on both the HAs must be identical.
IP pools cannot be modified on either the primary or the secondary HAs once IPSP is enabled.
Sessions are dropped during the IPSP setup process if:
the primary HA has not yet approved an IP address or address block.
the primary HA is not known to the secondary HA.
Once an address is assigned to the secondary HA, all the information about that address is erased on the primary
HA and that address becomes unusable by the primary HA.
LRU is not supported across the systems. Although, LRU continues to be supported within the system.
If the IPSP configuration is not disabled before removing the HA from the IPSP network link, sessions may be
rejected if the system‘s VPN Manager is rebooted or restarts.
IPSP does not control static IP pools. An external application (AAA, etc.) must be responsible for ensuring that
duplicate addresses are not assigned.
IPSP ignores interface failures allowing the configured dead-interval timer to determine when the HA should
become the primary and control the pool addresses. Before the dead-interval timer starts, the secondary HA
maintains its state and any busied out addresses remain busied out. After the dead-interval timer starts, IPSP
marks the neighboring peer HA as down, becomes primary, and will unbusy out all pool addresses.
maintains its state and any busied out addresses remain busied out. After the dead-interval timer starts, IPSP
marks the neighboring peer HA as down, becomes primary, and will unbusy out all pool addresses.