Manual

Cisco Packet Data Serving Node (PDSN) Release 2.0

Resource Management

12.3(11)T

• The STC VSA returned from AAA in access-accept message during FA-CHAP and HA-CHAP will

be ignored, and local configuration on the PDSN and HA will take precedence.

• Revocation extension and messages, even if not protected by FHAE or IPSec, will be accepted and

processed by both PDSN and HA. It is recommended that the user takes care of providing the

security of the messages by either configuring FA-HA security association or by provisioning IPSec

tunnel between the two agents.

• MobileIP MIB is not updated with the Registration revocation information

• On PDSN all the 'ip mobile foreign-service …' commands need to be configured at the global level

and not at the interface level.

• On PDSN, for the I-bit support the local policy is to always negotiate I-bit and to always set it to 1

in the Revocation messages. Also the provision to set B-bit to 1 in the agent advertisement message

while informing MN of the revoked data flow is not provided.

• Resource Revocation on HA is not supported with Home Agent redundancy.

• Resource Revocation and Bind Update cannot be enabled simultaneously. Both are mutually

exclusive of each other.

Packet of Disconnect

Radius Disconnect, or Packet of Disconnect (PoD) is a mechanism that allows the RADIUS server to

send a Radius Disconnect Message to the PDSN to release Session related resources. Resources may be

released due to the session handoff, or for administrative purposes. Some of the resources identified

include PPP, RP sessions and Mobile IP bindings. Support for Radius Disconnect on the Cisco PDSN

and Home Agent is TIA835C compliant.

The PDSN communicates its Resource management capabilities to the Home AAA in the Access

Request message (sent for authentication/authorization procedure) by including a 3GPP2 Vendor

Specific Session Termination Capability (STC) VSA. The value communicated in the STC VSA is

obtained in the configuration. The PDSN also includes an NAS-Identifier attribute containing its Fully

Qualified Domain Name (FQDN) in the Access Request.

The Home AAA server establishes a relationship between the user and the NAS Identifier/ NAS-IP

address to detect a inter-PDSN handoff. If the NAS-Identifier/ NAS IP address received in the Access

Request is different from the previously stored value (non-zero), an inter-PDSN handoff is detected.

The Disconnect Request contains the NAS-ID and the Username (NAI) attributes. It can optionally

contain 3GPP2 Correlation ID Calling station ID (IMSI) and the Framed IP address—some session

identification attributes. A Disconnect Reason VSA is included if a inter-PDSN handoff is detected. The

session identification attributes supported by the PDSN are 3GPP2 Correlation ID and Calling station

ID (IMSI).

If the 3GPP2 Correlation ID and Calling station ID (IMSI) attributes are received in the Disconnect

Request, and the PDSN is able to find the session/flow corresponding to them, the PDSN will terminate

the associated flow and send a Disconnect ACK message to RADIUS server. If session is not found for

the received attributes, the PDSN will reply back with a Disconnect NACK message with error code

“session context not found”. If the Disconnect request has invalid attributes (for example, an 8 digit

IMSI), the PDSN will reply with a Disconnect NACK with error code “Invalid Request”.

The PDSN also supports processing Disconnect Requests that only contain the NAI attribute (if

configured). In compliance with the standards, the PDSN terminates all sessions corresponding to the

Username received.