MicroStrategy ONE

Configuring Environments with Multiple IP Addresses

We do not recommend using machines with more than one IP address as a communication agent. If your environment includes one or more machines and machines with more than one IP address are used as communication agents, make sure all IPs are available when installing. The IP mapping to the FQDN of the machine is included in the consul.json file, as shown below.

Copy
{
  "enable_debug": true,
  "datacenter": "dc1",
  "enable_script_checks": true,
  "check_update_interval": "0s",
  "log_level": "WARN",
  "data_dir": "../data",
  "watches": [
    {
      "type": "key",
      "key": "envInfoTime",
      "handler_type": "script",
      "args": [
        "C:\\Program Files (x86)\\Common Files\\MicroStrategy\\JRE\\180_77\\Win64\\bin\\java",
        "-jar",
        "../jar/envinfo-collector.jar",
        "collect"
      ]
    }
  ],
  "retry_join": [
    "SAP-W10-ent",
    "localhost",
    "10.27.17.238"
  ],
  "server": true,
  "bind_addr": "10.21.20.188",
  "bootstrap_expect": 3
}

If a machine has two available IP addresses, the consul may bind itself to one IP mapping for FQDN, while other machines use FQDN mapping to another IP. In this situation, you should manually modify consul.json. The IP used for "bind_addr" should be consistent with the IP the other machine finds using the FQDN; the IP for "bind_addr" and the IP (if not using FQDN ) in "retry_join" list representing this machine should be consistent. After all manual modifications of consul.json are complete on all machines with consul installed, stop the consul on all machines, delete the data folder in the /MicroStrategy/Services Registration path on every machine, and restart all consuls.

If MicroStrategy is installed when only one IP is available and runs later when multiple IPs are available, the consul will not start. The ServiceRegistration.log displays the error, "Multiple private IPv4 addresses found. Please configure one."

Using FQDN for the communication agent machine list during the installation is recommended. If the IP address list is used during installation, make sure to use the IP mapping to the FQDN for the machine with multiple IPs.

Machines with more than one IP address, as well as dynamic IPs, are not supported for automatic clustering.

Related Topics

Installing and Configuring Topology