Last updated on MARCH 21, 2013
Applies to:Oracle Communications Network Charging and Control - Version 2.2.0 and later
Oracle Solaris on SPARC (64-bit)
In all versions of NCC (Network Charging and Control), the acsStatsMaster processes ensure the Event Counters available for use in ACS (Advanced Control Services) remain in sync across all the SLCs (Service Logic Controllers) in a network as well as presenting the data to the SMS (System Management Server) for viewing via the SMS/ACS Screens.
The number of acsStatsMaster processes that run on the Statistics Master node follow the following formula:
1 x acsStatsMaster process is the parent process listening for incoming connections from the acsStatsLocalSLEE processes
1 x acsStatsMaster process connects to the SMS and updates the counter value held on the SMS
N x acsStatsMaster(s) is typically the number of acsStatsLocalSLEE processes running in the entire solution (typically one acsStatsLocalSLEE per SLC). The "N" processes will only spawn as Event Counters are updated.
In an NCC deployment of 4 SLCs all updating Event Counters, the expected number of acsStatsMaster processes on the Master SLC is 6 (2 + 4).
In an NCC deployment of 2 SLCs which does not utilize Event Counters, the expected number of acsStatsMaster processes on the Master SLC is 2 (2 + 0).
A problem exists where extraneous acsStatsMaster processes are spawned. This results in two acsStatsMasters servicing the same acsStatsLocalSLEE, one falsely. This is a waste of system resources and can result in errors being reported in monitoring applications.
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