Issue with DiameterGateway Failover

(Doc ID 2379065.1)

Last updated on APRIL 04, 2018

Applies to:

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

Goal

On : 11.3.0.1.0 version, Diameter Gateway

Diameter Gateway (DGW) failover has an issue if same name is used for two different sites. One is active and the other is hot standby, i.e. site1 is running with 2 DGW and has similar setup in site2.

The DGW s configured with multi-home SCTP network which needs to use the same diameter name for both sites. Because during the failover, if the diameter names are different, pending messages in JMS are not processed by site2 DGW.

Below are the diameter names used:

Site1
diameterGateway1
diameterGateway2

Site2
diameterGateway1
diameterGateway2

For using the same diameter gateway name for both sites, the manual reconfiguration (JMX update, set the MBeans) is required to bring the DGW in site2 during failover.

Below values need to be updated in diameterGatewayConfig:
diameterTrafficHostSctp
originHost
originRealm

The requirement is to have some solution to avoid the manual reconfiguration.
 

Solution

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