Install guide

ifcfg-eth2

# Intel Corporation 82546GB Gigabit Ethernet Controller

DEVICE=eth2

HWADDR=00:04:23:D4:88:BE

MASTER=bond0

SLAVE=yes

BOOTPROTO=none

TYPE=Ethernet

ONBOOT=no

ifcfg-eth3

# Intel Corporation 82546GB Gigabit Ethernet Controller

DEVICE=eth3

HWADDR=00:04:23:D4:88:BF

MASTER=bond0

SLAVE=yes

BOOTPROTO=none

TYPE=Ethernet

ONBOOT=no

ifcfg-bond0

DEVICE=bond0

IPADDR=192.168.2.162

NETMASK=255.255.255.0

NETWORK=192.168.2.0

BROADCAST=192.168.2.255

BOOTPROTO=none

TYPE=Ethernet

ONBOOT=yes

3.3.3. Fencing Network

When Red Hat Cluster Suite has determined that a cluster node must be removed from the active

cluster, it will need to fence this node. T he methods used in this cluster are both power-managed. T he

HP iLO BMC has one Ethernet port, which must be configured, and this information must exactly match

the fencing clauses in the /etc/cluster.conf file. Most IPMI-based interfaces only have one network

interface, which may prove to be a single point of failure for the fencing mechanism. A unique feature of

Red Hat Cluster Suite is the ability to nest fence domains to provide an alternative fence method, in case

the BMC pathway fails. A switched Power Distribution Unit (PDU) can be configured (and it frequently

has only one port). We do not recommend the use of FCP port fencing, nor T .10 SCSI reservations fence

agent for mission critical database applications. T he address and user/password must also be correct

in the /etc/cluster/conf file.

<fencedevice agent="fence_ilo" hostname="192.168.1.7" login="rac" name="jLO7"

passwd="jeff99"/>

<fencedevice agent="fence_ilo" hostname="192.168.1.8" login=”rac” name="jLO8"

passwd="jeff99"/>

</fencedevices>

Chapter 3. Software Installation and Configuration