Cisco Cisco Packet Data Gateway (PDG) Guia De Resolução De Problemas
WiMAX PMIPv6 Operation
▀ Fallback Mechanism between PMIPv6 and PMIPv4
▄ Cisco ASR 5000 Series Access Service Network Gateway Administration Guide
OL-22953-01
Fallback Mechanism between PMIPv6 and PMIPv4
This section briefly describes the fallback mechanism from PMIPv6 to PMIPv4. The following assumptions must be
taken into consideration:
taken into consideration:
fa-service is configured and running.
The AAA server supports the SN1-Proxy-MIP = Enabled RADIUS attribute in Access-Accept or the subscriber
configuration has the proxy-mip flag set to allow.
The AAA server does not support the Service Info attribute and therefore, does not send the attribute in the
Access-Accept messages
The following table shows the network access server’s (NAS) behavior based on whether:
The SN1-Proxy-MIP is present in Access-Accept messages
The SN1-Proxy-MIP is configured locally in subscriber templates
The Service Info attribute is present or absent in Access-Accept messages during the authentication and
authorization phase.
Table 25. NAS Behavior Based on SN1-Proxy-MIP and Service Info Attribute
SN1-Proxy-
MIP
MIP
Service Info, if received in
Access-Accept
Access-Accept
NAS Behavior
0
0
Treated as an SIPv4 call.
0
1
This is a success scenario. PMIPv6 is triggered. The acquisition of the home address
is based on the bit set in the Service Info attribute.
is based on the bit set in the Service Info attribute.
1
0
This is a success scenario. PMIPv4 is triggered. The acquisition of the home address
is IPv4.
is IPv4.
1
1
This is a success scenario. PMIPv6 is triggered. The acquisition of the home address
is based on the bit set in the Service Info attribute.
is based on the bit set in the Service Info attribute.