Red Hat CLUSTER SUITE - CONFIGURING AND MANAGING A CLUSTER 2006 Manual page 123

Chapter 9. Setting Up a Red Hat Enterprise Linux LVS Cluster
After physically connecting together the cluster hardware, configure the network inter-
faces on the primary and backup LVS routers. This can be done using a graphical ap-
plication 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 ti-
tled Network Configuration in the Red Hat Enterprise Linux System Administration Guide.
For more information on editing network scripts by hand, see the chapter titled Network
Scripts in the Red Hat Enterprise Linux Reference Guide. For the remainder of the chapter,
example alterations to network interfaces are made either manually or through the Piranha
Configuration Tool.
9.2.1. General LVS Networking Tips
Configure the real IP addresses for both the public and private networks on the LVS routers
before attempting to configure the cluster using the Piranha Configuration Tool. The
sections on each topography give example network addresses, but the actual network ad-
dresses are needed. Below are some useful commands for bringing up network interfaces
or checking their status.
Bringing Up Real Network Interfaces
The best way to bring up any real network interface is to use the following commands
as root replacing N with the number corresponding to the interface (
/sbin/ifup ethN
Warning
Do not use the
using Piranha Configuration Tool (
to start
pulse
To bring a network interface down, type the following command:
/sbin/ifdown ethN
Again, replace N in the above command with the number corresponding to the inter-
face you wish to bring down.
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
scripts to bring up any floating IP addresses you may configure
ifup
instead (see Section 10.8 Starting the Cluster for details).
or ). Use the
eth0:1 eth1:1
107
and ):
eth0 eth1
command
service