1973567 - Failed SUP cluster sync leads to client syncs working fine on the primary node of a 2 node SUP 2.x cluster. Syncs fail on second node due to 'login failed' error.

Initial symptom is that user syncs failed with this error, but only on the secondary node of a 2 node cluster:

2014-01-15 10:12:05.507 DEBUG MMS pool-1-thread-140 - /registration/RegistrationServlet [com.sybase.djc.mobilink.LoginHandler] authentication failure code = 4000
2014-01-15 10:12:05.551 DEBUG MMS pool-1-thread-140 - /registration/RegistrationServlet [com.sybase.djc.mobilink.LoginHandler] authentication failure reason = Login Failed: user 'SELHORM@SUPSAPSecurityCRS'
2014-01-15 10:12:05.552 ERROR MMS pool-1-thread-140 - /registration/RegistrationServlet [com.sybase.sup.server.registration.RegistrationHandler] Login Failed: user 'SELHORM@SUPSAPSecurityCRS'
com.sybase.sup.server.registration.RegistrationException: Login Failed: user 'SELHORM@SUPSAPSecurityCRS'
at com.sybase.sup.server.registration.RegistrationHandler.processRegistrationRequest(RegistrationHandler.java:207)

Further troubleshooting led to the discovery that cluster sync's(replicating cluster data from the primary server to the secondary server) was not occurring.  As a result of the cluster sync not occurring, the security profile that was set up on the pimary server was not copied to the secondary server.   Without the security profile the application could not authenticate users when syncs were attempted on the secondary server. 

SUP 2.1.x through 2.3.x
SAP backend EIS
Load balancer between client devices and SUP(no Relay Server).
Any client device.

KBA , MOB-SUP , Sybase Unwired Platform , Problem