Configure Service Assurance Manager, Adapter Platform, and BIM in the failover.conf file.
-
In the installation area where the Failover Manager is running, go to the BASEDIR/smarts/bin directory and type the following command to open the failover.conf file:
./sm_edit /conf/failover/failover.conf
-
Under the Server section, add SAM, Adapter Platform, and BIM details with Server Type as SAM, OI, and BIM, respectively. For example:
SAM:
Server { DetachInterval = 300; Name = "INCHARGE-SA"; ServerType = "SAM"; LocationA { HostName = "itops-tco-217.lss.emc.com"; PortNumber = 1751; Basedir = "/opt/InCharge/SAM/smarts"; } LocationB { HostName = "itops-tco-223.lss.emc.com"; PortNumber = 1751; Basedir = "/opt/InCharge/SAM/smarts"; } } Server { DetachInterval = 300; Name = "INCHARGE-SA-PRES"; ServerType = "SAM"; UIServices = "smarts-tomcat,smarts-rabbitmq,smarts-elasticsearch"; LocationA { HostName = "itops-tco-217.lss.emc.com"; PortNumber = 1751; Basedir = "/opt/InCharge/SAM/smarts"; } LocationB { HostName = "itops-tco-223.lss.emc.com"; PortNumber = 1751; Basedir = "/opt/InCharge/SAM/smarts"; } } Server { DetachInterval = 300; Name = "INCHARGE-OI"; ServerType = "OI"; LocationA { HostName = "smartslin02.svtdomain.us.dg.com"; PortNumber = 11308; Basedir = "/opt/InCharge/SAM/smarts"; } LocationB { HostName = "smartslin04.svtdomain.us.dg.com"; PortNumber = 11308; Basedir = "/opt/InCharge/SAM/smarts"; } } Server { DetachInterval = 300; Name = "INCHARGE-MBIM"; ServerType = "BIM"; LocationA { HostName = "itops-tco-217.lss.emc.com"; PortNumber = 1752; Basedir = "/opt/InCharge/SAM/smarts"; } LocationB { HostName = "itops-tco-223.lss.emc.com"; PortNumber = 1752; Basedir = "/opt/InCharge/SAM/smarts"; } }
-
Uncomment the MNRSection and specify values for the following parameters. The Failover Manager uses this information to set the Active EDAA and Active Broker in the SolutionPack for VMware Smart Assurance.
-
MNRHost—Is the VMware M&R Frontend server (tomcat) host.
-
MNRPort—Is the VMware M&R Frontend server (tomcat) port.
-
MNRProtocol—Is the VMware M&R Frontend server (tomcat) protocol.
-
GatewayHost—Is the VMware M&R web-service gateway host.
-
GatewayPort—Is the VMware M&R web-service gateway port.
-
GatewayProtocol—Is the VMware M&R web-service gateway protocol.
In case you have multiple SolutionPack instances, specify the SolutionPack that contains the Reports SolutionPack block.
For each SolutionPack block (Reports, Events, Data collection) specify the values exactly how they appear in the Centralized Management page in the VMware M&R UI. To locate and copy the values, navigate to the SolutionPacks page. (Log in to the VMware M&R UI and type http://<Frontend IP address>:58080/centralized-management. Click SolutionPacks and then click VMware Smart Assurance to locate the information.)
-
Component—Is the component. For example: Reports, Events, Data collection.
-
ComponentVersion—Is the component version.
-
SPInstance—Is the SolutionPack instance. For example: VMware-smarts
-
SPVersion—Is the SolutionPack version.
-
SPServer—Is the SolutionPack server distribution.
If you have upgraded VMware M&R, check the version information after the upgrade. You might need to update version information in the MNRSection of the failover.conf file.
For example:
MNRSection { MNRHost = "smartslin03.emc.com"; MNRPort = 58080; MNRProtocol = "http"; GatewayHost = "smartslin03.emc.com "; GatewayPort = 48443; GatewayProtocol = "https"; SolutionPackBlock { Component = "Reports"; ComponentVersion ="2.1.1"; SPInstance = "emc-smarts"; SPVersion = "2.1.1"; SPServer = "smartslin02.emc.com"; } SolutionPackBlock { Component = "Events"; ComponentVersion ="2.1.1"; SPInstance = "emc-smarts"; SPVersion = "2.1.1"; SPServer = "smartslin02.emc.com"; } SolutionPackBlock { Component = "Data collection"; ComponentVersion ="2.1.1"; SPInstance = "emc-smarts"; SPVersion = "2.1.1"; SPServer = "smartslin02.emc.com"; } }
-
-
-
Save the failover.conf file and exit.
Note:If you configure SAM for failover while the Failover Manager is already running, use the ic-failover-server script reload option to reload the failover.conf file and use the Reconfigure button in the Domain Manager Administration Console to reconfigure the Failover Manager.