Review the following prerequisites before starting the Failover Manager.
The Failover Manager must be started with root privileges since the Failover Manager must be able to execute ICMP pings on the hosts that are monitored.
For Windows, the failover service (ic-failover)needs to be started as an administrator service for PowerShell remoting to work. Normally, all EMC Smarts services start up with the Local System account which does not have PowerShell remoting access and this causes the failover service remote execution to fail in Windows. “Setting up Administrator service for PowerShell remoting (Windows only)” on page 57 provides instructions.
File permissions must be set to allow the copying of files from one host to another.
The Failover solution uses secure copy and remote login programs. Appropriate network and host configurations must be in place for the solution to function. The requirement also includes non-prompting authentication settings whenever applicable, either with SCP or SSH commands or with VMware Smart Assurance programs, such as dmctl, sm_config, or others.
For more information on setting up non-prompting authentication, refer to “Set up passwordless communication between Active and Standby hosts” on page 20.
Start the Failover Manager only after all the components to be monitored are started and configured.
After creating the Failover Manager service and assuming that you have yet to reboot the host machine, you can use the sm_service start command to start or stop the Failover Manager.