Retrived object is session but update came for different object.!! Ignoring update!
(Doc ID 2696959.1)
Last updated on AUGUST 18, 2020
Applies to:Acme Packet 3900 - Version S-Cz8.3.0 and later
Information in this document applies to any platform.
After upgrading the 3900 h/w to cz830m1p2 version, it was observed that the log.sipdxx files from only the Standby node were getting filled with following entries:
[REDUNDANCY] (1) Error in session update, object xxxxxxx Retrived object is session but update came for different object.!! Ignoring update!
where xxxxxxx stands for random numerical value and is masked so, from security aspect.
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