RHEL 6 Virtual Server - 3.3. Putting the Configuration Together

Red Hat Enterprise Linux 9 Essentials Book now available.

Purchase a copy of Red Hat Enterprise Linux 9 (RHEL 9) Essentials

Red Hat Enterprise Linux 9 Essentials Print and eBook (PDF) editions contain 34 chapters and 298 pages

3.3. Putting the Configuration Together

After determining which of the preceding routing methods to use, the hardware 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 connects to public network and eth1 connects to the private network, 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.

After physically connecting together the hardware, configure the network interfaces on the primary and backup LVS routers. This can be done using a graphical application such as system-config-network or by editing the network scripts manually. For more information about adding devices using system-config-network, see the chapter titled Network Configuration in the Red Hat Enterprise Linux Deployment Guide. For the remainder of the chapter, example alterations to network interfaces are made either manually or through the Piranha Configuration Tool.

3.3.1. General Load Balancer Add-On Networking Tips

Configure the real IP addresses for both the public and private networks on the LVS routers before attempting to configure Load Balancer Add-On using the Piranha Configuration Tool. The sections on each topology give example network addresses, but the actual network addresses are needed. Below are some useful commands for bringing up network interfaces or checking their status.

Bringing Up Real Network Interfaces: To bring up a real network interface, use the following command as root, replacing N with the number corresponding to the interface (eth0 and eth1).

/sbin/ifup ethN

Warning

Do not use the ifup scripts to bring up any floating IP addresses you may configure using Piranha Configuration Tool (eth0:1 or eth1:1). Use the service command to start pulse instead (see Section 4.8, “Starting the Load Balancer Add-On” for details).
Bringing Down Real Network Interfaces: To bring down a real network interface, use the following command as root, replacing N with the number corresponding to the interface (eth0 and eth1).

/sbin/ifdown ethN
Checking the Status of Network Interfaces: If you need to check which network interfaces are up at any given time, type the following:

/sbin/ifconfig

To view the routing table for a machine, issue the following command:

/sbin/route

3.3. Putting the Configuration Together

Important

3.3.1. General Load Balancer Add-On Networking Tips

Warning