Cisco Cisco IOS Software Release 12.4(22)XR
118
Cisco Packet Data Serving Node Release 5.0 for Cisco IOS Release 12.4(22)XR
OL-19026-01
New Features in This Release
Supervisor Support
This release introduces support for SUP32, SUP720, and RSP720 variants.
Supervisor support is provided for: Cisco Catalyst 6500 Supervisor Engine 32 (WS-SUP32-GE-3B and
WS-SUP32-10GE-3B), Cisco Catalyst 6500 Supervisor Engine 720 (WS-SUP720-3B and
WS-SUP720), and the new Cisco Route Switch Processor 720 (RSP720-3C-GE, RSP720-3CXL-GE, and
RSP720-3CXL-10GE)
WS-SUP32-10GE-3B), Cisco Catalyst 6500 Supervisor Engine 720 (WS-SUP720-3B and
WS-SUP720), and the new Cisco Route Switch Processor 720 (RSP720-3C-GE, RSP720-3CXL-GE, and
RSP720-3CXL-10GE)
Data Over Signaling
This release introduces support for Data Over Signaling (DOS), also known as Short Data Burst feature
enabling you to send short data bursts to and from mobile station (MS) using the available signaling
channel.
enabling you to send short data bursts to and from mobile station (MS) using the available signaling
channel.
IOS uses the Modular QoS CLI (MQC) command set and Common Classification Engine (CCE) APIs
to support the flow-based infrastructure for policing. CCE is a general framework that provides
classification and feature association functions to IOS applications (for example, QoS and ACL). An IOS
flow is defined in CCE as a unique instance of a class and as a whole or subset of source address, source
port, destination address, destination port, and protocol.
to support the flow-based infrastructure for policing. CCE is a general framework that provides
classification and feature association functions to IOS applications (for example, QoS and ACL). An IOS
flow is defined in CCE as a unique instance of a class and as a whole or subset of source address, source
port, destination address, destination port, and protocol.
While only one vaccess per MIP session is available, there are multiple flows and each flow downloads
a different policy name. So, vaccess is not a target. To enable flow-based QoS on PDSN, a virtual object
is created on PDSN, which acts as an interface and attaches the service policy. This virtual object
identifies flow and marking parameters to QoS.
a different policy name. So, vaccess is not a target. To enable flow-based QoS on PDSN, a virtual object
is created on PDSN, which acts as an interface and attaches the service policy. This virtual object
identifies flow and marking parameters to QoS.
DOS packet is identified based on the policy map configured (flow-based policy) on the router. This
policy map must be downloaded from the AAA server during access-accept for each direction, The
downloaded policy is installed on the PDSN over that virtual interface for that particular direction.
policy map must be downloaded from the AAA server during access-accept for each direction, The
downloaded policy is installed on the PDSN over that virtual interface for that particular direction.
QoS marks the packet as eligible for DOS marking. PDSN must mark the packets with DOS attribute in
the GRE header in downstream or forward direction only based on the classification criteria and only
when the session is in dormant state.
the GRE header in downstream or forward direction only based on the classification criteria and only
when the session is in dormant state.
Note
To enable DOS feature, you need to configure cdma pdsn dos.
Note
You can install the policy either as vaccess or flow; both are not supported together. If vaccess-based
installation is used, then ensure that you disable CDMA PDSN QoS policy flow-only using the no cdma
pdsn QoS policy flow-only command.
installation is used, then ensure that you disable CDMA PDSN QoS policy flow-only using the no cdma
pdsn QoS policy flow-only command.
The following sections describe:
•
•
•
•
•
•
•