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.

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:

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

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

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

• 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 Domain Managers to point to the new location of 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.