Smarts Failover reports error in log. Mismatch in version of servers
search cancel

Smarts Failover reports error in log. Mismatch in version of servers

book

Article ID: 315836

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

To assist in resolving the issue after an upgrade from an older version of Smarts to the 10.1.x version when implementing failover..

Symptoms:
After upgrade from an older version of Smarts and setting up Failover the logs report messages like these:

    Line 288: determine_version:  23-Aug-2021 17:40:25 CEST;  type = 'SAM'
    Line 289: determine_version:  23-Aug-2021 17:40:25 CEST; Active: 'SAM' Verison: 9.3
    Line 290: determine_version:  23-Aug-2021 17:40:25 CEST; Standby:  'SAM' Verison: 10.1.5.0
    Line 291: determine_version:  23-Aug-2021 17:40:25 CEST; Mismatch in version of servers. activeVersion 9.3 , standbyVersion 10.1.5.0
    Line 293: resync_actions:  23-Aug-2021 17:40:30 CEST; determine_version.pl is picked from /opt/InCharge10/SAM/smarts/actions  


Environment

VMware Smart Assurance - SMARTS

Cause

SM_System version is in turn determined by the value set in lib/libsm_sms.so,  The upgrade or migration placed the older version of the library in place of the current version.

Resolution


Review the local library lib/libsm_sms.so, and the base lib/libsm_sms.so, and revert to the base file in the current 10.1.5 installation

Additional Information

Impact/Risks:
No risk,

Migration of old files should be reviewed for conflicts and best practice is to keep the latest GA library files. In this case the older library was copied and used instead of the current GA installed 10.1.5 library.