My Oracle Support Banner

Timeout Errors In DGWs For Subs Residing In New ECSes, After Adding New ECS Nodes (Doc ID 2997343.1)

Last updated on JANUARY 16, 2024

Applies to:

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

Symptoms

On Oracle Communications Elastic Charging Engine (ECE) 12.0.0.5.3 environment, on which there was a recent topology change (supplementary ecs nodes were added running on newly added machines), it has been observed a high increase in number of occurrences of below timeout error logged by Diameter Gateway (DGW) processes:

See below supplementary information:

- customer explained this problem occurs for some accounts (roughly around 200), from both legacy (existing) and newly added ecs nodes

- it was observed for accounts having this problem, when enabling subscriber tracing, only DGW trace file is created but no Event Charging Server(ECS) trace; it seems like no messages are received by ECS for these calls

- it was observed calls having the problem are data calls

- when such call is coming to DGW and error occurs, Packet Data Network Gateway(PGW) is putting account in degraded mode and subscriber is allowed to use data service; after 1 minute another call is sent to DGW, and so on; this is why having multiple errors for one subscriber

- timeout configured in DGW is 3 seconds

- this problem was also happening before the topology change, but number of occurrences was much smaller

- it was observed all accounts impacted by this problem are part of sharing groups

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.