SNR Resiliency Issue in ECE
(Doc ID 3018503.1)
Last updated on APRIL 30, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.8.0 and laterInformation in this document applies to any platform.
Symptoms
Customer observed that Subscribe Notification Request (SNR) Resiliency is not currently supported.
Scenario: If site1 which established Sy session is down, how does SNR messages will be picked up by site2 Diameter Gateway (DGW) connected to DRA/PCF peer.
In 3 site architecture, how do we decide the priority of DGW nodes which will handle SNR during site failure situation? Say, if DRA is connected to DGW1 (CL1), DGW2 (CL2), DGW3 (CL3), and if DGW1 (CL1) is down how do we decide if DGW2 (CL2) or DGW3 (CL3) should pickup
Expected Behaviour:
1. Need to avoid any conflicts in hashcode that we might be facing currently
2. Need to avoid any irrelevant notifications being published to incorrect partitions
3. Need to simplify the design and remove hashing logic.
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 |