Smarts Failover: Seeing the following error in the Failover log; Warning. Primary SAM was not found. Please verify that all MBIM subscriptions have been failed over successfully. Should we be concerned.

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


We are observing the following error in the Failover action log.
 

Error logs:-

failover_actions: 11-Apr-2016 10:28:34 CEST; Failover Actions begin.
failover_actions: 11-Apr-2016 10:28:42 CEST; Successfully registered 'sesklsmsampr01.emea.astrazeneca.net:9010/AZ-MBIM' with broker 'sesklsmsampr01.emea.astrazeneca.net:426/dmbroker'.
failover_actions: 11-Apr-2016 10:28:43 CEST; Successfully registered 'sesklsmsampr01.emea.astrazeneca.net:9010/AZ-MBIM' with broker 'uspllsmsamdr01.americas.astrazeneca.net:426/dmbroker'.
Warning. Primary SAM was not found. Please verify that all MBIM subscriptions have been failed over successfully.

Environment

VMware Smart Assurance - SMARTS

Resolution

The reason for this error, is that the MBIM server was set to manually fallback.

There is no impact, but merely a warning message because the Primary MBIM was nanually failed over and was in Standby.

Smarts is functioning as designed.