Servers going in disconnected state in version 4.0.3 (4281877)

Servers going in disconnected state in version 4.0.3

Servers are going in disconnected mode in version 4.0.3

RESOLUTION 1:

Upgrade to a newer version of QAS. The 4.1 product  has been enhanced and how we discovered the network has been improved.  4.0.3.x is no longer supported.  This issue does not occur in the 4.1 product.    Please go to https://support.oneidentity.com/authentication-services/download-new-releases to download the latest software. 

RESOLUTION 2:

1-  Make a backup of /opt/quest/libexec/vas/scripts/check_network_state.sh

2 - Edit /opt/quest/libexec/vas/scripts/check_network_state.sh

Add the following lines after the ASDCOM line:

$ASDCOM NetUpNotification

exit 0

Here is the script after the changes:

#!/bin/sh

##==============================================================================
# Copyright 2012 Quest Software, Inc. ALL RIGHTS RESERVED.
##
## Version: 4.0.3.xx
##
##==============================================================================

DOMAIN_REACHABLE="/opt/quest/libexec/vas/get_domain_reachable"
ASDCOM="/opt/quest/libexec/vas/sugi/asdcom"
$ASDCOM NetUpNotification
exit 0

$DOMAIN_REACHABLE "$@"

RVAL=$?
if [ $RVAL = 0 ] ; then
$ASDCOM NetUpNotification
else
$ASDCOM NetDownNotification
fi
exit $RVAL

Extra info on this change: Basically the change made to the script is forcing it to return a success value, essentially we have bypassed the script. The check_network_state.sh script only checks for connectivity on one DC and if it doesn't get a response in a short period of time, 10 seconds, it returns a failure which causes the error messages that you see. By effectively taking out that script QAS reverts to it's previous method of checking connections to DC's which was more reliable. ** a sign that this script is the cause of the disconnected state is that the system will "flip flop" quickly between connected and disconnected.