Active SAM failure scenario

In case of an Active SAM failure, the Failover Manager forces a reconfiguration of the newly-promoted Active SAM to cause it to reconnect to the Active underlying analysis Domain Managers and Adapter Platform servers. At this point, the new Active SAM remains the Active SAM until it fails, or you manually initiate a failback.

The Active SAM server with Notification Cache Publishing Enabled is the SAM that is configured in the SolutionPack for VMware Smart Assurance for use with the VMware M&R User Interface. Sometimes, this SAM is referred to as the Presentation SAM server and its service name is ic-sam-server-pres. Three additional components compose this SAM:

• VMware Smart Assurance Data Web Applications (Tomcat)—Service name is smarts-tomcat.

  The EMC Data Access API (EDAA) with service name smarts-edaa resides in Tomcat.

• VMware Smart Assurance Notification Exchange (Rabbit MQ)—Service name is smarts-rabbitmq.

• VMware Smart Assurance Notification Cache (ElasticSearch)—Service name is smarts-elasticsearch.

  If the Active SAM or any of the three components go down, Failover Manager considers the Active SAM to be down and performs the following:

• Promotes the Standby SAM and Standby Tomcat, Rabbit MQ, and ElasticSearch services to Active.

• Reconfigures the SolutionPack for VMware Smart Assurance to point to the new location of VMware Smart Assurance Tomcat.

• Forces a reconfiguration of the newly-promoted Active SAM to cause it to reconnect to the Active underlying analysis Domain Managers and Adapter Platform servers.

  At this point, the new Active SAM remains the Active SAM until it fails, or you manually initiate a failback.

  Note:

  Presentation SAM server is the server that is configured in the SolutionPack for VMware Smart Assurance for use with the VMware M&R UI. This does not mean that a hierarchical SAM is required.