Live AF Sessions Found Dead After NT Service Restarted
Last updated on MARCH 01, 2017
Applies to:Oracle Communications Services Gatekeeper - Version 5.1.0 to 5.1.0 [Release 5.1]
Information in this document applies to any platform.
During failover test, it's found there are missing STR from AF session.
This situation was found by counting AAR/AAA and STR/STA counts in qos.log during the period of Failover test.
Normally in the case of applyQosFeature with specified duration, OCSG will start associated timer, when the timer is expired, OCSG will send STR to PCRF and then clear up the qos session.
However, when one of the two NTs is restarted as normal operation, the alive qos session created by applyQosFeature with duration will be kept death in the database forever, the reason is that the timer is NT wide, NOT cluster wide.
If applyQosFeature with a specified duration is heavily used, so nearly half of the online qos sessions are lost with NT restart operation.
In such case, it means end user will pay a big unnecessary money or telecom operator will waste network bandwidth.
Note: To have more details on the meaning of AAR/AAA or STR/STA messages, you could check the following reference : http://tools.ietf.org/html/rfc6733
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