Learn how to configure Load Balancer Connectors (LBCs). Complete these steps every time a new collector host is added to the environment to scale-out collectors.
- The Load Balancer Arbiter is installed on the primary backend with the listener port of 2020.
- The LBCs are installed on all of the collector hosts.
- The LBC listens on port 2020 local on that collector server and communicates with the Load Balancer Arbiter on the primary backend also using port 2020.
- During the installation of the LBC, when the script asks for the Web-Service gateway hostname or IP address [localhost], enter the DNS of the primary backend server where the arbiter is installed.
- The collector server has the LBC installed by default, but you must reconfigured it to point it to the primary backend and its arbiter:
Note: Reconfigure Generic-SNMP and Generic-RSC just after the installation by navigating to: Centralized Management > SolutionPacks > Other Components > click on the pencil icon against Generic SNMP or Generic RSC > click Reconfigure
- In Reconfigure button for the load-balancer-connector. , filter on the collector name, and click the
- Update all of the host names and gateway URLs so they point to the primary backend.
- Update the Alerting Backend hostname to Primary Backend host and 2010 port.
- Update the Frontend Web Service to point to the Frontend host.
- generic-rsc is installed by default on the collector host. Click the Reconfigure button and update the Frontend Web Service to point to frontend host. Update the Topology service question by changing the host name and gateway to point to the primary backend host.
- Click the Reconfigure button for generic-snmp. Update the Frontend Web service to point to frontend host. Update the Topology service question by changing the host name and gateway to point to primary backend host