Cisco Cisco IOS Software Release 12.4(22)XR
152
Cisco Packet Data Serving Node Release 5.5 for Cisco IOS Release 12.4(22)XR9
OL-19026-02
Features From Previous Releases
Option 2 - Include IP Flow in Main Flow:
Accounting is done only on main flow. No accounting records are sent for IPflows. But upstream and
downstream traffic are accounted in the respective IPflows and aux A10, if the TFT matches. However,
the accounting records (start or stop or interim) are not sent for IPflows. Counters for G1 or G2, packets
in or out for IPflows are added to G1 or G2 and packets in or out of main flow, when the accounting
records (interim and stop) of main flow are sent.
downstream traffic are accounted in the respective IPflows and aux A10, if the TFT matches. However,
the accounting records (start or stop or interim) are not sent for IPflows. Counters for G1 or G2, packets
in or out for IPflows are added to G1 or G2 and packets in or out of main flow, when the accounting
records (interim and stop) of main flow are sent.
Default Option - Per Flow Accounting:
Per-flow (IP flow)-based accounting is done. Accounting records are sent for main flow and IPflows.
Session and Flow Setup for Configurable Per-Flow Accounting Options
During initial call setup, the PDSN authenticates with the AAA server and downloads the accounting
option as part of access-accept. On downloading the attribute, the PDSN checks whether the downloaded
option is valid. If it is a valid option, the option is copied to the session. If it is not valid, the PDSN checks
for configured CLI command. If the accounting option is configured, it is copied to the session. If the
accounting option is not configured, there is no accounting option.
option as part of access-accept. On downloading the attribute, the PDSN checks whether the downloaded
option is valid. If it is a valid option, the option is copied to the session. If it is not valid, the PDSN checks
for configured CLI command. If the accounting option is configured, it is copied to the session. If the
accounting option is not configured, there is no accounting option.
If airlink records are received for the IPflows, the records are parsed and updated. If the accounting
option is valid, the accounting records for the IPflows, however, are not sent. The upstream and
downstream traffic are sent over the respective IPflows and aux A10s after checking the TFT.
option is valid, the accounting records for the IPflows, however, are not sent. The upstream and
downstream traffic are sent over the respective IPflows and aux A10s after checking the TFT.
Before sending the accounting records (interim and stop), the PDSN checks for the accounting option
and depending on the accounting option value, you can decide about including the G1 or G2, packets in
or packets out to the respective attributes of the main flow. If accounting option is valid, you can reset
G1 or G2, packets in or out of IPflows when you flush the IPflows for main flow.
and depending on the accounting option value, you can decide about including the G1 or G2, packets in
or packets out to the respective attributes of the main flow. If accounting option is valid, you can reset
G1 or G2, packets in or out of IPflows when you flush the IPflows for main flow.
Limitations in Configuring Per-Flow Accounting Options
The following are the limitations in configuring per-flow accounting options:
•
If the accounting option is downloaded twice, only the first downloaded version is considered.
•
The downloaded attribute is preferred to the configured value.
•
The accounting option is session-based and not flow-based.
•
The accounting option is considered only for single flow. If multiple MIP flows or a SIP, MIP flow
are opened, the same accounting option is applied for each flow.
are opened, the same accounting option is applied for each flow.
•
Removing the configurations commands cdma pdsn accounting main flow or cdma pdsn
accounting main flow include ipflows, removes the accounting option configuration.
accounting main flow include ipflows, removes the accounting option configuration.
•
To maintain redundancy, the accounting option is synchronized to standby.
IP Flow Discriminator Support for PCF Backward Compatibility
PDSN adds the 4-byte IP flow discriminator to the GRE header. But some PCFs are based on the standard
A.S0008 v3.0, or a lesser value that defines the IP flow discriminator to be 3 bytes without the reserved
byte.
A.S0008 v3.0, or a lesser value that defines the IP flow discriminator to be 3 bytes without the reserved
byte.
This release supports IP flow discriminator for backward compatibility of PCFs using the following new
command in global configuration mode:
command in global configuration mode:
pdsn# cdma pdsn compliance hrpd ipflow-discriminator