Manual

Cisco Packet Data Serving Node (PDSN) Release 2.0
Resource Management
31
12.3(11)T
Conditional Debugging Support Under Clustering Feature
The Cisco PDSN 2.0 Clustering feature adds additional support for the conditional debugging with the
following clustering debug command on both controller and member:
Debug cdma pdsn cluster controller message {event | error | packet}
Note PDSNs in controller-member mode and peer-to-peer mode cannot co-exist in the same cluster. They are
mutually exclusive.
For information on redundancy and load balancing in the PDSN Release 2.0, see the “PDSN Clustering
Peer-to-Peer and Controller / Member Architecture” section on page 43.
Upgrading the Controller PDSN Software from R1.2 to R2.0
To upgrade the PDSN controller to Release 2.0, perform the following tasks:
Step 1 Reload either the Active/Standby controller so that at least one of the controllers is operating to take care
new incoming calls.
Step 2 Load Release 2.0 software. Once the controller with Release 2.0 software is operational, ensure both
controllers have synched session information using the following command:
# show cdma pdsn cluster controller configuration
Step 3 Issue the following command to make use of the scalable bulk-synch mechanism of session information
between Controller and member PDSN introduced in Release 2.0 PDSN Software.
config# cdma pdsn cluster controller member periodic-update
Follow the same procedure as above to upgrade the other PDSN controller to Release 2.0.
Upgrading the Member PDSN Software from R1.2 to R2.0
To upgrade a member PDSN to Release 2.0, perform the following tasks:
Step 1 Separate a member PDSN out of the cluster by configuring the following command on the member
PDSN:
config# cdma pdsn cluster member prohibit administratively
The status of the member will be updated to the controller in a subsequent periodic keepalive reply
message that the member sends to the controller. The controller, upon reception of this message, does
not select this member for any of the new incoming calls.
Step 2 Display the member PDSNs which are prohibited administratively by issuing the following command:
#show cluster controller member prohibited administratively
The calls, which are already connected to the member, will be alive until the mobile node disconnects
the call. Alternatively, the calls can be forcibly cleared on the prohibited member using the following
command:
#clear cdma pdsn session all