The system does not support the configuration of the MIP lifetime timer
on per- domain (context) basis. However, a domain-wide lifetime timer can be
achieved by configuring the idle-timeout attribute for the default subscriber
for each domain.
Important:
Mobile IP lifetime settings can be controlled on a per-domain basis
only in deployments for which the idle timeout attribute for
individual subscriber profiles is
not
used during operation.
In this configuration, the value of the registration lifetime sent by
the system in Agent Advertisements is selected by comparing the configured FA
Agent Advertisement lifetime setting, and the idle and/or absolute timeout
settings configured for the domain\'s default subscriber. If the value of the
idle and/or absolute timeout parameter is less than the Agent Advertisement
lifetime, then the system provides a registration lifetime equal to 5 seconds
less than the lowest timer value.
If the idle timeout attribute is configured in individual subscriber
profiles, per-domain lifetime control is not possible. In this case, the
registration lifetime configured for the FA must be the lower of the two
values.
Important:
Commands used in the examples in this section provide base
functionality to the extent that the most common or likely commands and/or
keyword options are presented. In many cases, other optional commands and/or
keyword options are available. Refer to the
Command Line Interface Reference for complete information
regarding all commands.
The following is an example CLI command sequence used to configure the
Mobile IP lifetime on a per-domain basis.
configure
context <aaa_context_name>
subscriber default
ip context-name <abc>
exit
subscriber name <ptt.bigco.com>
timeout idle <3605>
ip context-name <abc>
exit
subscriber name <bigco.com>
timeout idle <7205>
ip context-name <abc>
exit
domain <ptt.bigco.com> default subscriber <ptt.bigco.com>
domain <bigco.com> default subscriber <bigco.com>
end
configure
context <ha_context_name>
subscriber default
exit
ha-service <ha>
idle-timeout-mode normal
reg-lifetime <7200>
end
configure
context <fa_context_name>
fa-service <fa>
advertise reg-lifetime <7200>
end
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.
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.
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.
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.)
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:
-
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 data and upon inter-AGW handoff or inter access technologies
The following optional modifier is also supported:
Feedback