Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: IP Services Oracle Solaris 11 Information Library |
1. Planning the Network Deployment
2. Considerations When Using IPv6 Addresses
3. Configuring an IPv4 Network
4. Enabling IPv6 on the Network
5. Administering a TCP/IP Network
7. Troubleshooting Network Problems
11. Administering the ISC DHCP Service
12. Configuring and Administering the DHCP Client
13. DHCP Commands and Files (Reference)
14. IP Security Architecture (Overview)
16. IP Security Architecture (Reference)
17. Internet Key Exchange (Overview)
19. Internet Key Exchange (Reference)
20. IP Filter in Oracle Solaris (Overview)
Part IV Networking Performance
22. Integrated Load Balancer Overview
23. Configuration of Integrated Load Balancer (Tasks)
Installing the Integrated Load Balancer
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
Administering Back-End Servers in ILB
How to Add a Back-End Server to a Server Group
Administering Health Checks in ILB
Displaying Health Check Results
Obtaining Statistical Information Using the show-statistics Subcommand
Displaying the NAT Connection Table
Displaying the Session Persistence Mapping Table
Using Import and Export Subcommands
24. Virtual Router Redundancy Protocol (Overview)
25. VRRP Configuration (Tasks)
26. Implementing Congestion Control
Part V IP Quality of Service (IPQoS)
27. Introducing IPQoS (Overview)
28. Planning for an IPQoS-Enabled Network (Tasks)
29. Creating the IPQoS Configuration File (Tasks)
30. Starting and Maintaining IPQoS (Tasks)
31. Using Flow Accounting and Statistics Gathering (Tasks)
You can use the ilbadm to add, remove, enable, and disable one or more back-end servers within server groups. For a list of definitions, see ILB Terminology.
Server specifications must include a host name or IP address and can also include an optional port or a range of ports. Server entries with the same IP address are disallowed within a server group.
# ilbadm add-server -s server=192.168.89.1,192.168.89.2 ftpgroup # ilbadm add-server -s server=[2001:7::feed:6]:8080 sgrp
The -e option enables the servers in addition to adding them to the group.
Note - IPv6 addresses must be enclosed in square brackets.
Example 23-3 Adding a Back-End Server to a Server Group
The following example adds servers to server groups ftpgroup and sgrp, and enables them.
# ilbadm add-server -s server=192.168.89.1,192.168.89.2 ftpgroup # ilbadm add-server -e -s server=[2001:7::feed:6]:8080 sgrp
# ilbadm remove-server -s server=_sg1.2 sg1
Example 23-4 Removing a Back-Server From a Server Group
The following example removes the server with server ID 10.1.1.2 from server group websg:
# ilbadm remove-server -s server=_sg1.2 sg1
Note the following:
If the server is being used by a NAT or half-NAT rule, disable the server by using the disable-server subcommand before removal. When a server is disabled, it enters the connection-draining state. After all the connections are drained, the server can be removed by using the remove-server subcommand. After issuing the disable-server command, periodically check the NAT table (by using the show-nat command) to see if the server in question still has connections. After all of the connections are drained (the server does not get displayed in the show-nat command output), the server can then be removed by using the remove-server command.
If the conn-drain timeout value is set, the connection-draining state will be completed upon conclusion of the timeout period. The default value of conn-drain timeout is 0, meaning it will keep waiting until a connection is gracefully shut down.
Note - A server can have multiple server IDs, if it belongs to multiple server groups.
# ilbadm enable-server websg.1 # ilbadm disable-server websg.1
Example 23-5 Re-enabling and Disabling a Back-End Server
In the following example a server with server ID websg.1 is enabled and then disabled.
# ilbadm enable-server websg.1 # ilbadm disable-server websg.1