6.4. Cluster Configuration File with Dual Power Supply Fencing


Configuring a cluster with Conga modifies the cluster configuration file. This section shows the cluster configuration file before and after the procedures documented in Section 6.3, “Dual Power Fencing Configuration Procedure” were performed.
Before the cluster resources and service were configured, the cluster.conf file appeared as follows.

<?xml version="1.0"?>
<cluster alias="apcclust" config_version="34" name="apcclust">
        <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
        <clusternodes>
                <clusternode name="clusternode1.example.com" nodeid="1" votes="1">
                        <fence/>
                </clusternode>
                <clusternode name="clusternode2.example.com" nodeid="2" votes="1">
                        <fence/>
                </clusternode>
                <clusternode name="clusternode3.example.com" nodeid="3" votes="1">
                        </fence>
                </clusternode>
        </clusternodes>
        <cman/>
        <fencedevices/>
        <rm>
                <failoverdomains/>
                <resources/>
        </rm>
</cluster>

After the cluster resources and service were configured, the cluster.conf file appears as follows.

<?xml version="1.0"?>
<cluster alias="apcclust" config_version="40" name="apcclust">
    <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/>
    <clusternodes>
          <clusternode name="clusternode1.example.com" nodeid="1" votes="1">
                  <fence>
                          <method name="1">
                                <device name="pwr01" option="off" port="1"/>
                                <device name="pwr02" option="off" port="1"/>
                                <device name="pwr01" option="on" port="1"/>
                                <device name="pwr02" option="on" port="1"/>
                          </method>
                  </fence>
          </clusternode>
          <clusternode name="clusternode2.example.com" nodeid="2" votes="1">
                  <fence>
                          <method name="1">
                                <device name="pwr01" option="off" port="2"/>
                                <device name="pwr02" option="off" port="2"/>
                                <device name="pwr01" option="on" port="2"/>
                                <device name="pwr02" option="on" port="2"/>
                          </method>
                  </fence>
          </clusternode>
          <clusternode name="clusternode3.example.com" nodeid="3" votes="1">
                  <fence>
                          <method name="1">
                                <device name="pwr01" option="off" port="3"/>
                                <device name="pwr02" option="off" port="3"/>
                                <device name="pwr01" option="on" port="3"/>
                                <device name="pwr02" option="on" port="3"/>
                          </method>
                  </fence>
            </clusternode>
    </clusternodes>
    <cman/>
    <fencedevices>
          <fencedevice agent="fence_apc" ipaddr="10.15.86.96" login="apclogin" name="pwr01" passwd="apcpword"/>
          <fencedevice agent="fence_apc" ipaddr="10.15.86.97" login="apclogin" name="pwr02" passwd="apcpword"/>
    </fencedevices>
    <rm>
          <failoverdomains/>
          <resources/>
    </rm>
</cluster>

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.