diff --git a/docs/en-US/add-load-balancer-rule.xml b/docs/en-US/add-load-balancer-rule.xml
index 2d911feaf75..b679736ba8b 100644
--- a/docs/en-US/add-load-balancer-rule.xml
+++ b/docs/en-US/add-load-balancer-rule.xml
@@ -67,8 +67,8 @@
Stickiness: (Optional) Click Configure and choose
- the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer
- Rules.
+ the algorithm for the stickiness policy. See .
AutoScale: Click Configure and complete the
@@ -76,6 +76,22 @@
+ Health Check: (Optional; NetScaler load balancers only) Click
+ Configure and fill in the characteristics of the health check policy. See .
+
+ Ping path (Optional): Sequence of destinations to which to send health check queries.
+ Default: / (all).
+ Response time (Optional): How long to wait for a response from the health check (2 - 60 seconds).
+ Default: 5 seconds.
+ Interval time (Optional): Amount of time between health checks (1 second - 5 minutes).
+ Default value is set in the global configuration parameter lbrule_health check_time_interval.
+ Healthy threshold (Optional): Number of consecutive health check successes
+ that are required before declaring an instance healthy.
+ Default: 2.
+ Unhealthy threshold (Optional): Number of consecutive health check failures that are required before declaring an instance unhealthy.
+ Default: 10.
+
Click Add VMs, then select two or more VMs that will divide the load of incoming
traffic, and click Apply.
diff --git a/docs/en-US/health-checks-for-lb-rules.xml b/docs/en-US/health-checks-for-lb-rules.xml
new file mode 100644
index 00000000000..84cae658120
--- /dev/null
+++ b/docs/en-US/health-checks-for-lb-rules.xml
@@ -0,0 +1,48 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+
+
+ Health Checks for Load Balancer Rules
+ (NetScaler load balancer only)
+
+ Health checks are used in load-balanced applications to ensure that requests are forwarded
+ only to running, available services.
+ When creating a load balancer rule, you can specify a health check policy.
+ This is in addition to specifying the
+ stickiness policy, algorithm, and other load balancer rule options.
+ You can configure one health check policy per load balancer rule.
+ Any load balancer rule defined on a NetScaler load balancer in &PRODUCT; can have a health check policy.
+ The policy consists of a ping path, thresholds to define "healthy" and "unhealthy" states,
+ health check frequency, and timeout wait interval.
+ When a health check policy is in effect,
+ the load balancer will stop forwarding requests to any resources that are found to be unhealthy.
+ If the resource later becomes available again, the periodic health check
+ will discover it, and the resource will once again be added to the pool of resources that can
+ receive requests from the load balancer.
+ You can delete or modify existing health check policies.
+ To configure how often the health check is performed by default, use the global
+ configuration setting lbrule_health check_time_interval.
+ You can override this value for an individual health check policy.
+ For details on how to set a health check policy using the UI, see .
+
diff --git a/docs/en-US/load-balancer-rules.xml b/docs/en-US/load-balancer-rules.xml
index 77739001966..884647c6f8b 100644
--- a/docs/en-US/load-balancer-rules.xml
+++ b/docs/en-US/load-balancer-rules.xml
@@ -37,4 +37,5 @@
+