Diameter Messages Delayed After SCTP Path Failover
(Doc ID 2566693.1)
Last updated on JULY 23, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On a HA(high availability) environment, once the Stream Control Transmission Protocol (SCTP) fails overs to the secondary interface automatically (the 1st interface is shutdown manually), the Gy CCA (Diameter Credit Control Answer) messages do not show at network layer until much later even though the application layer had sent the CCA messages.
The failover is happening, however when communication fails over to the other interface, response times are gradually increasing. Once the process is restarted using the secondary interface, then there is no such delay problem observed.
What is the probable cause and solution for this SCTP failover delay issue?
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