Diameter Peer - SNR Not Published After DPR (Doc ID 2302474.1)

Last updated on SEPTEMBER 11, 2017

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.1.0 and later
Information in this document applies to any platform.

Symptoms

There were two issues with Diameter Gateway.

Issue 1: Diameter Gateway was sending SNR request to alternate peer with incorrect Host details, which resulted with error (DIAMETER_UNABLE_TO_DELIVER) in SNA.

Steps to reproduce:
=============
1. PCRF started Sy Session (from node-1: ncc-pcrf-app-1-rt-sy) by sending SLR to ECE
2. PCEF sent Gy CCR-i, CCR-U
3. PCRF node-1 was stopped
=> As part of usage consumption, once usage breached threshold, ECE published SNR. But as node-1 was down, it tried to send SNR to alternate peer (i.e. node-2: ncc-pcrf-app-2-rt-sy) and failed due to incorrect host details in message.

2017-04-12 20:12:26.791 IST DEBUG - - - - Diameter:ncc-pcrf-app-2-rt-sy(10.xx.xx.xx:54177): Sending SNR [3297638641:1375790671 / ncc-pcrf-app-1-rt-sy;1491988426;12;729] message:

Diameter Message: SNR
 Session-Id (263,M,l=46) = ncc-pcrf-app-1-rt-sy;1491988426;12;729
 Origin-Host (264,M,l=38) = dgw1.CVM-1438.test.com
 Origin-Realm (296,M,l=33) = CVM-1438 test.com
 Auth-Application-Id (258,M,l=12) = 16777302
 Destination-Realm (283,M,l=19) = yahclick.ae
 Destination-Host (293,M,l=28) = ncc-pcrf-app-1-rt-sy
 Policy-Counter-Status-Report (2903,VM,v=10415,l=120) =
  Policy-Counter-Identifier (2901,VM,v=10415,l=15) = KBU
  Policy-Counter-Status (2902,VM,v=10415,l=29) = Over_threshold_75

2017-04-12 20:12:26.949 IST DEBUG - - - - Diameter:ncc-pcrf-app-2-rt-sy(10.xx.xx.xxx:54177): Received SNA [3297638641:1375790671 / ncc-pcrf-app-1-rt-sy;1491988426;12;729] DIAMETER_UNABLE_TO_DELIVER (3002) message:
Diameter Message: SNA
 Session-Id (263,M,l=46) = ncc-pcrf-app-1-rt-sy;1491988426;12;729
 Origin-Host (264,M,l=28) = ncc-pcrf-app-2-rt-sy
 Origin-Realm (296,M,l=19) = yahclick.ae
 Result-Code (268,M,l=12) = DIAMETER_UNABLE_TO_DELIVER (3002)
 Error-Reporting-Host (294,M,l=28) = ncc-pcrf-app-2-rt-sy


Issue 2: Diameter Gateway was not able to send STA, if peer was down. It was not sending request to alternate peer, which resulted with error in STA ,

Steps to reproduce:
=============
1. PCRF started Sy Session (from node-1: ncc-pcrf-app-1-rt-sy) by sending SLR to ECE
2. PCEF sent Gy CCR-i, CCR-U
3. PCRF node-1 was stopped
4. PCRF node-2 sent STR to terminate Sy session
=> DiameterGateway was fetching session detail from cache as Sy was started from node-1, it was trying to send STA on node-1, whereas the request was came from node-2. As node-1 was down, it was not sending STA to PCRF, which resulted in error.
But the session was terminated in ECE. As PCRF didn't get any response from ECE, it was trying to send STR again, which resulted in DIAMETER_UNKNOWN_SESSION_ID error.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms