Orphaned LDAP Sync in Cluster - How to remove old LDAP Sync instances in VIP Enterprise Gateway

Products

• VIP Service

Issue/Introduction

Orphaned LDAP Sync Instances are created when the old server was shutdown without first properly turning off the LDAP Synchronization Service. These sync services are registered in the VIP Cloud services and show up in the local EGConsole home page in order to help schedule LDAP Synchronizations. (Note: LDAP Synchronizations from different EGW servers must be scheduled at least 2 hours apart from any other server).

This can happen due to a few different scenarios:

1. Old or decommissioned VIP Enterprise Gateway server was shut down without first turning off the LDAP Sync service properly
2. VIP Enterprise Gateway server is replaced, migrated, or reinstalled (even with same IP Address) without first turning off the LDAP Sync service properly

These orphaned LDAP Sync Instances do not cause any problems and will not affect the current VIP Enterprise Gateway services and LDAP Synchronizations from functioning.

 

Environment

Symantec VIP Enterprise Gateway - version 9.9.x or higher

Resolution

• If the status is "Stopped" for the orphaned VIP LDAP Sync Instance, then the instance will eventually turn into dead status and it will be removed from the EGConsole Home screen after a few days.
• If the status is "Started" for the orphaned instance, then the only way to remove it is by setting up another VIP Enterprise Gateway service with an identical IP Address and Sync Cluster, then turning on the LDAP Synchronization service and turning it back off again properly through the EGConsole.