Intel_RAID_HA_Solution_RHEL_WhitePaper

Installation Intel® RAID High Availability Solution for Red Hat* Linux Systems White Paper
Intel Confidential Revision 1.0
18
For example, add a method “fencemethod_ipmi” for both nodes:
CCS h HA02.SH addmethod fencemethid_ipmi HA01.SH
CCS h HA02.SH addmethod fencemethid_ipmi HA02.SH
5. Add a fence device for the fence method with the following command:
ccs -h host --addfencedev node1fence agent=fence_ipmilan
ipaddr=ipmi_ip login=ipmi_user passwd=ipmi_passwd auth=md5
action=off
For example, add the fence device node1fence and node2fence for node1 and
node2:
ccs h HA02.SH --addfencedev node1fence agent=fence_ipmilan
ipaddr=192.168.144.21 login=admin passwd=password auth=md5
action=off
ccs h HA02.SH --addfencedev node2fence agent=fence_ipmilan
ipaddr=192.168.144.32 login=admin passwd=password auth=md5
action=off
6. Add a fence instance for the fence method with the following command:
ccs -h host --addfenceinst fencedevicename node method
For example:
ccs -h HA02.SH --addfenceinst node1fence HA01.SH fencemethid_ipmi
ccs -h HA02.SH --addfenceinst node2fence HA02.SH fencemethid_ipmi
2.9.3 Create a Failover Domain
By default, all of the nodes can run any cluster service. A failover domain is a named subset of
cluster nodes that are eligible to run a cluster service in the event of a node failure. A failover
domain can have the following characteristics:
Unrestricted Allows you to specify that a subset of members is preferred, but that a
cluster service assigned to this domain can run on any available member.
Restricted Allows you to restrict the members that can run a particular cluster service.
If none of the members in a restricted failover domain are available, the cluster service
cannot be started (either manually or by the cluster software).
Unordered When a cluster service is assigned to an unordered failover domain, the
member on which the cluster service runs is chosen from the available failover domain
members with no priority ordering.
Ordered Allows you to specify a preference order among the members of a failover
domain. The member at the top of the list is the most preferred, followed by the second
member in the list, and so on.