Red Hat ENTERPRISE LINUX AS 2.1 Installation Manual page 124

124
The /etc/sysconfig/network-scripts/ifcfg-eth1 for the private NAT interface on the
LVS router could look something like this:
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
IPADDR=10.11.12.9
NETMASK=255.255.255.0
In this example, the VIP for the LVS router's public interface will be 192.168.26.10 and the VIP for
the NAT or private interface will be 10.11.12.10. So, it is essential that the real servers route requests
back to the VIP for the NAT interface.
The sample Ethernet interface configuration settings in this section are for the
real IP addresses of an LVS router and not the floating IP addresses. To con-
figure the public and private floating IP addresses the administrator should
use the Piranha Configuration Tool, as shown in Section 9.4,
SETTINGS
After configuring the primary LVS router node's network interfaces, configure the backup LVS
router's real network interfaces — taking care that none of the IP address conflict with any other IP
addresses on the network.
Be sure each interface on the backup node services the same network as the
interface on primary node. For instance, if eth0 connects to the public net-
work on the primary node, it must also connect to the public network on the
backup node as well.
8.2.1 Routing on the Real Servers
The most important thing to remember when configuring the real servers network interfaces in a NAT
cluster is to set the gateway for the NAT floating IP address of the LVS router. In this example, that
address will be 10.11.12.10.
Chapter 8:Setting Up a Red Hat Enterprise Linux AS LVS Cluster
Important
and Section 9.6.1, The
Important
Subsection.
VIRTUAL SERVER
GLOBAL