The ServerSection defines the components of the failover solution. The ServerSection contains mandatory parameters.

  • Name—The VMware Smart Assurance product name (example: INCHARGE-SA). “Values for the Name parameter” on page 57 provides a list of product names.

  • UIServices—Required for a SAM with Notification Cache Publishing. Specify the services for VMware Smart Assurance Data Web Applications (smarts-tomcat), VMware Smart Assurance Notification Exchange (smarts-rabbitmq), and VMware Smart Assurance Notification Cache (smarts-elasticsearch).

    Configure Hostname, PortNumber, Basedir, and InstalledServiceName for each pair of Active and Standby components in the LocationA and LocationB entries, respectively:

  • Hostname—Is the fully qualified hostname or IP address of the host where the component is running. For Linux, the value must exactly match the name displayed when you run the Linux hostname command.

  • PortNumber—Is the port where the component is running.

    For Trap Exploder, the PortNumber value must match the --sport value in the sm_service install command.

  • Basedir—Is the directory path where the component is installed.

  • InstalledServiceName—Is the service name of the Trap Exploder (ic-trapd-exploder) or the VoIP Trap Adapter (ic-voip-notification-trapd-receiver). Failover Manager uses this value to start the component as a service. Trap Exploder, VoIP Trap Adapter, and the Broker (specified in the BrokerSection) are the only components that Failover Manager restarts. Specifying this parameter for other components has no effect since the Failover Manager does not restart them.

    The following parameters are optional:

  • ServerType—Is the type of component or Domain Manager. “ServerType” on page 57 provides a list of ServerType values.

  • DetachInterval— “DetachInterval” on page 57 provides detailed information about when to specify this parameter.

    In the entry, once you specify the value of the Name parameter, you need to provide specific information for Active and Standby (sibling) components within the two separate subsections: LocationA and LocationB.

    LocationA and LocationB are two segments in a given network environment. Each contains a set of hosts on which Active and/or Standby VMware Smart Assurance products run.

    An example is provided for defining the parameters for SAM:

    ServerSection
    {
     Server
     {
    DetachInterval = 300;
     Name= "INCHARGE-SA";
     ServerType= "SAM";
    # UIServices = "smarts-tomcat,smarts-rabbitmq, smarts-elasticsearch";
     DetachInterval=300;
     LocationA
      {
      HostName= "<host-A>";
      PortNumber= 2611;
      Basedir= "/opt/InCharge/SAM";
      }
     LocationB
      {
      HostName= "<host-B>";
      PortNumber = 2622;
      Basedir = /opt/InCharge/SAM
      }
     }
    }
    

    Configure ServerSection for each VMware Smart Assurance component lists the VMware Smart Assurance components and their entry examples for the ServerSection.

Table 1. Configure ServerSection for each VMware Smart Assurance component

Component

Go to

Broker

“Add the Broker to the Failover Manager” on page 53

SAM, Adapter Platform, and BIM

“Configure the failover.conf file for SAM, Adapter Platform, and BIM” on page 27

IP Manager

“Add IP Managers to the Failover Manager” on page 29

MPLS Manager

“Add the MPLS Manager to the Failover Manager” on page 31

Server Manager (ESM)

“Add the Server Manager to the Failover Manager” on page 33

NPM

“Add Network Protocol Manager to the Failover Manager” on page 40

VoIP Availability Manager

“Add VoIP Availability Manager and VoIP Trap Adapter to the Failover Manager” on page 47

Trap Adapter

“Add the Trap Adapter to the Failover Manager” on page 49

Trap Exploder

“Add the Trap Exploder to the Failover Manager” on page 51