OpsCenter 2.1.2 and later operate in multiple regions or IP forwarding deployments.
Use the following approach for deployments where a public IP forwards to a private IP on the agent, but that machine is not aware of (that is, can't bind to) the public IP.
To configure OpsCenter agents for multiple regions or IP forwarding:
Open the address.yaml file for editing.
The location of this file depends on the type of installation:
Add the following option to the address.yaml:
local_interface: (Optional) The IP that the agent uses to connect to the local Cassandra process. This is typically the same as listen_address, and can usually be auto-detected.
agent_rpc_interface: The IP that the agent HTTP server listens on. In a multiple region deployment, this is typically a private IP.
agent_rpc_broadcast_address: The IP that the central OpsCenter process uses to connect to the agent.
local_interface: 10.114.187.46 agent_rpc_interface: 220.127.116.11 agent_rpc_broadcast_address: 18.104.22.168
Repeat the above steps for each node.