Cisco Cisco Packet Data Interworking Function (PDIF) Guida Alla Risoluzione Dei Problemi
Mobile-IP and Proxy-MIP Timer Considerations
▀ Controlling the Mobile IP Lifetime on a Per-Domain Basis
▄ Cisco ASR 5000 Series Gateway GPRS Support Node Administration Guide
OL-22943-01
In the example above, two domains (ptt.bigco.com and bigco.com) are configured. The default subscribers are defined
for the two domains respectively. The desired operation requires a Mobile IP lifetime of 1 hour (3600 secs) for the
ptt.bigco.com domain, and a lifetime of 2 hours (7200 secs) for the bigco.com domain.
for the two domains respectively. The desired operation requires a Mobile IP lifetime of 1 hour (3600 secs) for the
ptt.bigco.com domain, and a lifetime of 2 hours (7200 secs) for the bigco.com domain.
Whenever a subscriber session belonging to the ptt.bigco.com domain arrives, the system uses a Mobile IP lifetime
timer value equal to 5 seconds less than the idle timeout configured for the default subscriber because the configured
value is less than the registration lifetime value configured for the Agent Advertisement. 5 seconds less than the
configured value of 3605 seconds equals 3600 seconds which meets the desired operation.
timer value equal to 5 seconds less than the idle timeout configured for the default subscriber because the configured
value is less than the registration lifetime value configured for the Agent Advertisement. 5 seconds less than the
configured value of 3605 seconds equals 3600 seconds which meets the desired operation.
Whenever a subscriber session belonging to the bigco.com domain arrives, the system uses the configured registration
lifetime value as the Mobile IP lifetime in Agent Advertisements because it is less than the configured idle timeout in
the default subscriber‟s profile.
lifetime value as the Mobile IP lifetime in Agent Advertisements because it is less than the configured idle timeout in
the default subscriber‟s profile.
As a general rule, the registration lifetime value on the agent must be configured as the highest Mobile IP lifetime that
is desired for a subscriber. (In the above example, it would be the subscriber bigco.com.)
is desired for a subscriber. (In the above example, it would be the subscriber bigco.com.)
Another important factor to consider is that the idle timeout value should be reset on receipt of a renewal request. To
support this operation, the system provides the idle-timeout-mode configurable in the HA service. The following
modes are supported:
support this operation, the system provides the idle-timeout-mode configurable in the HA service. The following
modes are supported:
normal: Resets the idle timeout value on receipt of Mobile IP user data and control signaling
aggressive: Resets the idle timeout value on receipt of Mobile IP user data only (this is the default behavior)
handoff: Resets the idle timeout value on receipt of Mobile IP user dataand upon inter-AGW handoff
The following optional modifier is also supported: