My Oracle Support Banner

DCA Doesn't Track Origin-State-ID for Each Permitted Instance (Doc ID 2564406.1)

Last updated on OCTOBER 03, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.1 and later
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), Diameter Control Agent (DCA) does not maintain the Origin-State-ID per connected instance but rather per port.

As a result, if 2 or more clients connect to the same DCA port (this requires DIAMETER.PeerSchemes.Peers.PermittedInstances to be either set to 0 (unlimited) or greater than 1), then if a request arrives from a different instance to the previous message, the following alarm is thrown:

Aug 21 09:56:26.762367 diameterControlAgent(16682) ERROR: {960197} Origin-State-Id changed for Origin-Host=<HOSTNAME>, Session-Id=<Session ID>. New origin-state-id=1503294498, old=1503294496

The Origin-State-ID is should be unique per connected instance.

Changes

PermittedInstances is set to 0 or greater than 1, and multiple instances are connected to the same DCA port.

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
Changes
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.