Installation guide

unique SAN physical port number: The port number for no d e-0 1. example. co m is 11, the port
number for no d e-0 2. example. co m is 12, and the port number for no d e-0 3. exampl e. co m is
13.
ccs -h node01.example.com --addmethod SAN node01.example.com
ccs -h node01.example.com --addmethod SAN node02.example.com
ccs -h node01.example.com --addmethod SAN node03.example.com
ccs -h node01.example.com --addfenceinst sanswitch1 node01.example.com
SAN port=11
ccs -h node01.example.com --addfenceinst sanswitch1 node02.example.com
SAN port=12
ccs -h node01.example.com --addfenceinst sanswitch1 node03.example.com
SAN port=13
ccs -h node01.example.com --addunfence sanswitch1 node01.example.com
port=11 action=on
ccs -h node01.example.com --addunfence sanswitch1 node02.example.com
port=12 action=on
ccs -h node01.example.com --addunfence sanswitch1 node03.example.com
port=13 action=on
Example 5.3, “ cl uster.co nf After Adding Storage-Based Fence Methods ” shows a
cl uster.co nf configuration file after you have added fencing methods, fencing instances, and
unfencing to each node in the cluster.
Examp le 5.3. cl uster.co nf Af t er Ad d in g St o rag e- Based Fen ce Met h o d s
<cluster name="mycluster" config_version="3">
<clusternodes>
<clusternode name="node-01.example.com" nodeid="1">
<fence>
<method name="SAN">
<device name="sanswitch1" port="11"/>
</method>
</fence>
<unfence>
<device name="sanswitch1" port="11" action="on"/>
</unfence>
</clusternode>
<clusternode name="node-02.example.com" nodeid="2">
<fence>
<method name="SAN">
<device name="sanswitch1" port="12"/>
</method>
</fence>
<unfence>
<device name="sanswitch1" port="12" action="on"/>
</unfence>
</clusternode>
<clusternode name="node-03.example.com" nodeid="3">
<fence>
<method name="SAN">
<device name="sanswitch1" port="13"/>
</method>
</fence>
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
80