Table of Contents
Advertisement
106
9.1.3. Enabling NAT Routing on the LVS Routers
In a simple NAT LVS cluster where each clustered service uses only one port, like HTTP
on port 80, the administrator needs only to enable packet forwarding on the LVS routers
for the requests to be properly routed between the outside world and the real servers. See
Section 8.5 Turning on Packet Forwarding for instructions on turning on packet forward-
ing. However, more configuration is necessary when the clustered services require more
than one port to go to the same real server during a user session. For information on creat-
ing multi-port services using firewall marks, see Section 9.3 Multi-port Services and LVS
Clustering.
Once forwarding is enabled on the LVS routers and the real servers are set up and have the
clustered services running, use the Piranha Configuration Tool to configure the cluster as
shown in Chapter 10 Configuring the LVS Routers with Piranha Configuration Tool.
Warning
Do not configure the floating IP for
or using a network configuration tool. Instead, use the Piranha Configuration Tool as
shown in Section 10.4 GLOBAL SETTINGS and Section 10.6.1 The VIRTUAL SERVER
Subsection to configure any cluster-related virtual interfaces.
When finished, start the
is up and running, the active LVS router will begin routing requests to the pool of
pulse
real servers.
9.2. Putting the Cluster Together
After determining which of the above routing methods to use, the hardware for the LVS
cluster should be linked together on the network.
Important
The adapter devices on the LVS routers must be configured to access the same networks.
For instance if
eth0
then these same devices on the backup LVS router must connect to the same networks.
Also the gateway listed in the first interface to come up at boot time is added to the routing
table and subsequent gateways listed in other interfaces are ignored. This is especially
important to consider when configuring the real servers.
Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster
eth0:1
service as shown in Section 10.8 Starting the Cluster. Once
pulse
connects to public network and
or
by manually editing network scripts
eth1:1
connects to the private network,
eth1
Advertisement
Table of Contents
