JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: IP Services     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


Part I TCP/IP Administration

1.  Planning an IPv4 Addressing Scheme (Tasks)

2.  Planning an IPv6 Addressing Scheme (Overview)

3.  Planning an IPv6 Network (Tasks)

4.  Configuring TCP/IP Network Services and IPv4 Addressing (Tasks)

5.  Enabling IPv6 on a Network (Tasks)

6.  Administering a TCP/IP Network (Tasks)

7.  Configuring IP Tunnels

8.  Troubleshooting Network Problems (Tasks)

9.  TCP/IP and IPv4 in Depth (Reference)

10.  IPv6 in Depth (Reference)


11.  About DHCP (Overview)

12.  Planning for DHCP Service (Tasks)

13.  Configuring the DHCP Service (Tasks)

14.  Administering DHCP (Tasks)

15.  Configuring and Administering the DHCP Client

16.  Troubleshooting DHCP (Reference)

17.  DHCP Commands and Files (Reference)

Part III IP Security

18.  IP Security Architecture (Overview)

19.  Configuring IPsec (Tasks)

20.  IP Security Architecture (Reference)

21.  Internet Key Exchange (Overview)

22.  Configuring IKE (Tasks)

23.  Internet Key Exchange (Reference)

24.  IP Filter in Oracle Solaris (Overview)

25.   IP Filter (Tasks)

Part IV Networking Performance

26.  Integrated Load Balancer Overview

27.  Configuration of Integrated Load Balancer Tasks

Installing the Integrated Load Balancer

Enabling and Disabling ILB

How to Enable ILB

How to Disable ILB

Configuring ILB

DSR, Full-NAT, and Half-NAT Topologies

Half-NAT Load-Balancing Topology

Full-NAT Load-Balancing Topology

ILB High-Availability Configuration (Active-Passive Mode Only)

ILB HA Configuration Using the DSR Topology

How to Configure ILB to Achieve High-Availability by Using the DSR Topology

ILB High-Availability Configuration by Using the Half-NAT Topology

How to Configure ILB to Achieve High-Availability by Using the Half-NAT Topology

Setting Up User Authorization for ILB Configuration Subcommands

Administering ILB Server Groups

How to Create a Server Group

How to Delete a Server Group

Displaying a Server Group

Administering Back-End Servers in ILB

How to Add a Back-End Server to a Server Group

How to Remove a Back-End Server From a Server Group

How to Re-enable or Disable a Back-End Server

Administering Health Checks in ILB

Creating a Health Check

User-Supplied Test Details

Deleting a Health Check

Listing Health Checks

Displaying Health Check Results

Administering ILB Rules

How to Create a Rule

Deleting a Rule

Listing Rules

Displaying ILB Statistics

Obtaining Statistical Information Using the show-statistics Subcommand

Displaying the NAT Connection Table

Displaying the Session Persistence Mapping Table

Using Import and Export Subcommands

28.  Virtual Router Redundancy Protocol (Overview)

29.  VRRP Configuration (Tasks)

30.  Implementing Congestion Control

Part V IP Quality of Service (IPQoS)

31.  Introducing IPQoS (Overview)

32.  Planning for an IPQoS-Enabled Network (Tasks)

33.  Creating the IPQoS Configuration File (Tasks)

34.  Starting and Maintaining IPQoS (Tasks)

35.  Using Flow Accounting and Statistics Gathering (Tasks)

36.  IPQoS in Detail (Reference)



Administering Health Checks in ILB

ILB provides the following optional types of server health checks for the user to select from:

By default, ILB does not perform any health checks. You can specify health checks for each server group when creating a load-balancing rule. You can configure only one health check per load-balancing rule. As long as a virtual service is enabled, the health checks on the server group that is associated with the enabled virtual service start automatically and repeat periodically. The health checks stop as soon as the virtual service is disabled. The previous health check states are not preserved when the virtual service is re-enabled.

When you specify a TCP, UDP, or custom test probe for running a health check, ILB sends a ping probe, by default, to determine if the server is reachable before it sends the specified TCP, UDP, or custom test probe to the server. The ping probe is a method of monitoring server health. If the ping probe fails, the corresponding server is disabled with the health check status of unreachable. If the ping probe succeeds, but the TCP, UDP, or custom test probe fails, the server is disabled with the health check status of dead.

You can use the ilbadm command to create, delete, and list the health checks. For a list of definitions, see ILB Terminology.

Creating a Health Check

In the following example, two health checks objects,hc1 and hc-myscript, are created. The first health check uses the built-in TCP probe. The second health check uses a custom test, /var/tmp/my-script.

# ilbadm create-healthcheck \
-h hc-timeout=3,hc-count=2,hc-interval=8,hc-test=tcp hc1
# ilbadm create-healthcheck \ -h hc-timeout=3,hc-count=2,hc-interval=8,hc-test=/var/tmp/my-script hc-myscript

hc-test specifies the type of health check.

hc-interval specifies the interval between consecutive health checks. To avoid synchronization, the actual interval is randomized between 0.5 * hc-interval and 1.5 * hc-interval.

hc-timeout specifies the timeout when the health check considered to have failed if it does not complete.

hc-count specifies the number of attempts to run the hc-test health check.

Note - The port specification for hc-test is specified with the hc-port keyword in the create-rule subcommand. For details, refer to ilbadm(1M) man page.

User-Supplied Test Details

The following criteria must be met by the user-supplied test:

The user-supplied test, my-script , might or might not use all the arguments, but it must return one of the following :

By default, the health check test runs with the following privileges: PRIV_PROC_FORK, RIV_PROC_EXEC, RIV_NET_ICMPACCESS.

If a broader privilege set is required, you must implement setuid in the test. For more details on the privileges, refer to the privileges(5) man page.

Deleting a Health Check

The following example deletes a health check called hc1:

# ilbadm destroy-healthcheck hc1

Listing Health Checks

You can use the list-healthcheck subcommand to obtain detailed information about configured health checks. The following example lists two configured health checks:

# ilbadm list-healthcheck

Displaying Health Check Results

You can use the list-hc-result subcommand to obtain health check results. If a rule or a health check is not specified, the subcommand lists all the health checks.

The following example displays the health check results associated with a rule called rule1:

# ilbadm list-hc-result rule1