diff --git a/docs/en-US/management-server-install-multi-node.xml b/docs/en-US/management-server-install-multi-node.xml index 3f011b83b87..21cf28fc719 100644 --- a/docs/en-US/management-server-install-multi-node.xml +++ b/docs/en-US/management-server-install-multi-node.xml @@ -65,8 +65,7 @@ linkend="sect-source-buildrpm"/> or as Repeat these steps on each additional Management Server. - Be sure to configure a load balancer for the Management Servers. See Management Server - Load Balancing. + Be sure to configure a load balancer for the Management Servers. See . diff --git a/docs/en-US/management-server-lb.xml b/docs/en-US/management-server-lb.xml index 85a86221c80..9aee1548026 100644 --- a/docs/en-US/management-server-lb.xml +++ b/docs/en-US/management-server-lb.xml @@ -19,7 +19,7 @@ under the License. -->
- Setting Zone VLAN and Running VM Maximums + Management Server Load Balancing &PRODUCT; can use a load balancer to provide a virtual IP for multiple Management Servers. The administrator is responsible for creating the load balancer rules for the Management Servers. The application requires persistence or stickiness across multiple sessions. @@ -58,4 +58,9 @@ + In addition to above settings, the adminstrator is responsible for setting the 'host' global + config value from the management server IP to load balancer virtual IP address. + If the 'host' value is not set to the VIP for Port 8250 and one of your management servers crashes, + the UI is still available but the system VMs will not be able to contact the management server. +
diff --git a/docs/en-US/sys-reliability-and-ha.xml b/docs/en-US/sys-reliability-and-ha.xml index 3d6ebe1fcd6..e3c1cd9026f 100644 --- a/docs/en-US/sys-reliability-and-ha.xml +++ b/docs/en-US/sys-reliability-and-ha.xml @@ -25,6 +25,7 @@ System Reliability and High Availability +