Idle ASDL IDLE_TIMER_ASDL Not Fired When Expected (Doc ID 1109332.1)

Last updated on FEBRUARY 24, 2017

Applies to:

Oracle Communications ASAP - Version 5.2.4 to 7.0.1 [Release 5.2 to 7.0.0]
Information in this document applies to any platform.

Symptoms

The IDLE ASDL, IDLE_TIMER_ASDL, is not working as expected.

Customer configured an IDLE ASDL to be fired every 2 minutes of provisioning inactivity to keep the connection between Network Element and ASAP alive. IDLE_TIMER_INTERVAL and IDLE_TIMER_ASDL have been included in tbl_comm_param for that Network Element. However, IDLE ASDL was not fired even at the end of 2 minutes and many minutes after that. The connection eventually dropped after drop timeout was reached.

Changes

 

Cause

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