Oracle Communications Policy Management
 

PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
 

A bug  has been uncovered in 12.2.0 wherein,  the number of  RARs  triggered via PNRs will be  square of the number of Gx sessions per subscriber after the upgrade to 12.2.0

Applies to:

Description

A bug (Bugid#25369514) has been uncovered in 12.2.0 wherein, the number of RARs triggered via PNRs will be square of the number of Gx sessions per subscriber. The expected behavior is to generate one RAR per session for the subscriber.

For example, if a subscriber had 2 sessions, then 2 RARs are expected; but 4 RARs will be generated. And if a subscriber had 5 sessions then 5 RARs are expected; but 25 RARs will be generated.

Occurrence

Product affected : MPE

Releases Affected : 12.2.0

Symptoms

 Impact Statement:
1. Based on the number of the PNR’s and number of sessions per user per APN , this may result in a significant increase in TPS. If the TPS exceeds the capacity value, this may eventually result in the MPE going busy .

Workaround

This workaround can only reduce the impact by proactively removing stale sessions for an APN.

1> Set the maximum number of session per APN to 2.

How to Set :

1. Login to CMP GUI
2. Click on the “Configuration” under “Policy Server” on the left hand side of the GUI.
3. Select the MPE cluster and click on “Policy Server” tab
4. Click on “Modify” on that page at the top.
5. Scroll Down to “Diameter” settings and look for “Identify Duplicate sessions based on APN” option . Check mark that option.
6. For the above setting to work , the indexing for the option “Subscriber ID to detect duplicate sessions” also has to be chosen . There is a dropdown menu against this option . Select the one which you have chosen for your subscriber indexing which you can see at the top of the same page under the section “Subscriber Indexing”.
7. Click on save.
8. Go back to “Policy Server” tab and Click on "Advanced" tab
9. Click on "Modify" on top left.
10. Click on "ADD" under "Service Override" section , and do the following setting:

    CONFIGURATION kEY : DIAMETER.ENF.MaxPdnConnectionsPerSubscriberPerAPN
    vALUE: 2

11. Click "save" at the bottom of the page.
12. Repeat the above for all MPE clusters.

Patches

The issue has been fixed in 12.2.1 which is due to be released in March 2017

History

Alert Created on 01/30/2017

References

This solution has no attachment