| Asset ID: |
1-72-1944284.1 |
| Update Date: | 2016-09-06 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1944284.1
:
Policy Charging and Rules Function (PCRF) - Subscriber Profile Repository (SPR) "DIAMETER_ERROR_USER_UNKNOWN" -
| Related Items |
- Oracle Communications Subscriber Data Management (SDM)
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec SDM
|
SNR autoenrollment does not work when SNR is received in the blade where DB is running as standby.
In this Document
Created from <SR 3-9741251681>
Applies to:
Oracle Communications Subscriber Data Management (SDM) - Version SDM 9.0.5 and later
Information in this document applies to any platform.
Symptoms
Performing the test for the new architecture: it is with the DSR between the GGSN and PCRF (GGSN-DSR DSR-PCRF-SPR) and we get the result "DIAMETER_ERROR_USER_UNKNOWN" in the SNA that sends the SPR.
The configuration on the PCRF/SPR is (The SNA enable in the SPR; Combine Lookup, State & Quota enable in the MPE).
The issue could be identified, as follows:
• Scenario #1
The SPRB working as SystemController & DataAccess
The SPRA processing traffic in Sh interface.
The SPRA responds in the SNA "DIAMETER_ERROR_USER_UNKNOWN " without user profile and creates the user profile in the database.
This causes a different behavior in the policies, consequently affects users.
• Scenario #2
The SPRA working as
The SPAR processing traffic in Sh interface.
The SPRA responds in the SNA "DIAMETER_SUCCESS" with empty user profile and make the profile in the database.
In this case, the Policies are executed correctly
Changes
No changes.
Cause
Consultation is done in the Standby in a short period of time after the first change. In standby side the DB has not be synchronized at that moment.
Solution
BlueVersion 9.0.5 Patch5 was created to modify the way consultation is done when SNR autoenrollment is used.
Attachments
This solution has no attachment
