Cisco Cisco Packet Data Gateway (PDG) Guia De Resolução De Problemas
Mobile-IP and Proxy-MIP Timer Considerations
▀ Call Flow Summary
▄ Cisco ASR 5000 Series Home Agent Administration
OL-22980-01
Call Flow Summary
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.
keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all
commands.
The following steps describe the call flow as regards the timers that affect a call initiated by the Mobile Node (MN).
1. The call arrives at the system and A11 (or L2TP, for Closed RP interfaces) (or L2TP, for Closed RP interfaces)
is processed successfully. The call arrives at the system and R6 isThe call arrives at the system and R6 is
processed successfully.The GGSN receives a Create PDP Context Request Message
processed successfully.The GGSN receives a Create PDP Context Request Message
2. PPP negotiation is started. At this point,PPP negotiation is started. At this point, since authentication is not
performed the system does not have a username or password. So during the PPP phase, the system selects the
default subscriber in the source context for a subscriber template (DNS, and timer settings can be configured in
the default subscriber template). Once PPP is successfully established the system understands that the call is a
Mobile IP call. since authentication is not performed the system does not have a username or password. So
during the PPP phase, the system selects the default subscriber in the source context for a subscriber template
(DNS, and timer settings can be configured in the default subscriber template). Once PPP is successfully
established the system understands that the call is a Mobile IP call.The system determines the propertiesThe
system determines the properties
default subscriber in the source context for a subscriber template (DNS, and timer settings can be configured in
the default subscriber template). Once PPP is successfully established the system understands that the call is a
Mobile IP call. since authentication is not performed the system does not have a username or password. So
during the PPP phase, the system selects the default subscriber in the source context for a subscriber template
(DNS, and timer settings can be configured in the default subscriber template). Once PPP is successfully
established the system understands that the call is a Mobile IP call.The system determines the propertiesThe
system determines the properties
3. The new RRQ is accepted by the FA and sent to the HA. The HA authenticates the user and compares the
requested lifetime to the configured MIP lifetime in the HA-service and the subscriber idle and absolute
timeouts. If the MIP lifetime is lower it is be sent back to the mobile; if the MIP lifetime is higher the system
sends back an RRQ accept with the lifetime set to 5 seconds less than the lower of the idle or absolute timeout
for the user.
timeouts. If the MIP lifetime is lower it is be sent back to the mobile; if the MIP lifetime is higher the system
sends back an RRQ accept with the lifetime set to 5 seconds less than the lower of the idle or absolute timeout
for the user.
The following CLI command sequence is used to configure the Mobile IP reg-lifetime in the HA service: