MicroStrategy ONE

Configuring Environments with Nodes Using Dynamic IP Addresses

If you are using a single machine environment with a dynamic IP address and connecting Workstation to Library, you may encounter errors when accessing the Topology screen in Workstation.

After installation is finished and the machine is restarted, the communication agent may start before the network IP is fully resolved and ready on the machine. Therefore, the communication agent may obtain a temporary IP during the startup and consider it as the fully resolved one . Using the wrong IP on the machine affects the communication agent's function. If this problem continues to occur, a manual restart of the consul is required. See Restarting Services Registration for more information.

We do not recommend using machines with dynamic IP addresses as communication agents in a cluster. If your environment includes more than one machine and machines with dynamic IP addresses are used as communication agents, use FQDN (such as machine1.domain.com) in the communication agent machine list during installation.

If FQDN is not used, you should manually update the "retry_join" section in consul.json on all machines with communication and monitoring agents when all machines with dynamic IP addresses are fully resolved, every time those machines get new IPs.

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": [
    "10.27.16.239",
    "localhost",
    "10.27.17.238"
  ],
  "server": true,
  "bootstrap_expect": 3
}

Related Topics

Installing and Configuring Topology