Configuration Mismatch Detected Between Sites In Geography Redundancy Setup
(Doc ID 2284128.1)
Last updated on MARCH 28, 2018
Applies to:Oracle Communications Services Gatekeeper - Version 6.0.0 and later
Information in this document applies to any platform.
In Geography Redundancy setup, Alarm 113701 is frequently getting raised on both Master and Slave site:
The error remains after re-sync the slave site manually using the syncFromGeoMaster operation of GeoStorageService.
See the following error in NT default.log:
Despite of the alarm, no function is impacted.
This can be reproduced when a geo-redundant SLA configuration is set on the master site.
If set on slave site it always works.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!