First, enable enterprise load balancing on the central manager. Then, configure S-TAPs to point to
the central manager. Then the central manager allocates managed units to the S-TAP.
Before you begin
- The enterprise load balancer runs on a central manager or managed unit, listens
to port 8443, and uses Transport Layer Security (TLS).
- No new firewall or extra system setup is required.
- Load information is only collected from managed units that are online and configured with the
central management parameter LOAD_BALANCER_ENABLED=1. Setting
LOAD_BALANCER_ENABLED=0 disables load balancing and prevents that managed unit
from being dynamically allocated to S-TAP® agents during
load balancing activities.
Procedure
-
Enable enterprise load balancing on the central manager. Go to
and set
LOAD_BALANCER_ENABLED=1.
- Point one or more S-TAPs to the central manager by modifying the S-TAP parameter in the
S-TAP Control page:
- Load balancer host name or IP address
- load_balancer_port
- Modify the S-TAP configuration parameters in the S-TAP Control
page:
- Managed Units: The number of managed units the
enterprise load balancer allocates for this S-TAP.
- Load balancing: Defines how the load is split between the assigned
managed units. For example,
- Managed Units=2, and Load balancing=1 (load
balancing). The Enterprise Load Balancer assigns two managed units to the S-TAP, and traffic is
split between the managed units.
- Managed Units=2, and Load balancing=2 (mirroring).
The Enterprise Load Balancer assigns two managed units to the S-TAP, and traffic is mirrored to both
of the managed units.
- For Unix-Linux databases only. Load balancer node affinity: Whether the S-TAP connects to more than one managed
unit, for enterprise load balancing. Some scenarios need all traffic to go to the same collector.
With Oracle ATAP, for example, the analyzed client IP only shows if both the encrypted and
unencrypted sessions go to the same managed unit. For
more information, see Load balancer node affinity.