SNR Picked Up By The Wrong DiameterGateway
(Doc ID 2917031.1)
Last updated on APRIL 16, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
In a cloud native multi-site environment running Elastic Charging Engine (ECE) 12.0.0.4, it is observed that during a usage session initiated in site 2, an Spending Notification Request (SNR) is generated an sent to the Kafka partition assigned to diameterGateway in site2 (diameterGateway2). However the SNR is picked up by diameterGateway from site 1 (diameterGateway1).
In diameterGateway1 log it can be seen that a SNR is generated and sent to partition 86 based on GATEWAY_NAME=diameterGateway21BRM2 (site 2), which is correct.
However, the SNR notification is picked up by diameterGateway1 (site 1), which is not expected.
One more note: As per diameterGateway2.log file, during that period, there were connection issues between diameterGateway site 2 and Kafka site 1
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |