<!-- Fragment document type declaration subset:
ArborText, Inc., 1988-1997, v.4001
<!DOCTYPE SET PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [
<!ENTITY ha.cluster.messages SYSTEM "figures/ha.cluster.messages.eps" NDATA eps>
<!ENTITY machine.not.in.ha.cluster SYSTEM "figures/machine.not.in.ha.cluster.eps" NDATA eps>
<!ENTITY ha.cluster.config.info.flow SYSTEM "figures/ha.cluster.config.info.flow.eps" NDATA eps>
<!ENTITY software.layers SYSTEM "figures/software.layers.eps" NDATA eps>
<!ENTITY n1n4 SYSTEM "figures/n1n4.eps" NDATA eps>
<!ENTITY example.sgml SYSTEM "example.sgml">
<!ENTITY appupgrade.sgml SYSTEM "appupgrade.sgml">
<!ENTITY a1-1.failsafe.components SYSTEM "figures/a1-1.failsafe.components.eps" NDATA eps>
<!ENTITY a1-6.disk.storage.takeover SYSTEM "figures/a1-6.disk.storage.takeover.eps" NDATA eps>
<!ENTITY a2-3.non.shared.disk.config SYSTEM "figures/a2-3.non.shared.disk.config.eps" NDATA eps>
<!ENTITY a2-4.shared.disk.config SYSTEM "figures/a2-4.shared.disk.config.eps" NDATA eps>
<!ENTITY a2-5.shred.disk.2active.cnfig SYSTEM "figures/a2-5.shred.disk.2active.cnfig.eps" NDATA eps>
<!ENTITY a2-1.examp.interface.config SYSTEM "figures/a2-1.examp.interface.config.eps" NDATA eps>
<!ENTITY intro.sgml SYSTEM "intro.sgml">
<!ENTITY overview.sgml SYSTEM "overview.sgml">
<!ENTITY planning.sgml SYSTEM "planning.sgml">
<!ENTITY nodeconfig.sgml SYSTEM "nodeconfig.sgml">
<!ENTITY admintools.sgml SYSTEM "admintools.sgml">
<!ENTITY config.sgml SYSTEM "config.sgml">
<!ENTITY operate.sgml SYSTEM "operate.sgml">
<!ENTITY recover.sgml SYSTEM "recover.sgml">
<!ENTITY clustproc.sgml SYSTEM "clustproc.sgml">
<!ENTITY appfiles.sgml SYSTEM "appfiles.sgml">
<!ENTITY gloss.sgml SYSTEM "gloss.sgml">
<!ENTITY preface.sgml SYSTEM "preface.sgml">
<!ENTITY index.sgml SYSTEM "index.sgml">
]>
-->
<chapter id="LE56830-PARENT">
<title id="LE56830-TITLE">Testing Linux FailSafe Configuration</title>
<para>This chapter explains how to test the Linux FailSafe system configuration
using the Cluster Manager GUI and the Cluster Manager CLI. For general
information on using the Cluster Manager GUI and the Cluster Manager CLI,
see <xref linkend="LE73346-PARENT">.</para>
<para>The sections in this chapter are as follows:</para>
<itemizedlist>
<listitem><para><xref linkend="LE67057-PARENT"></para>
</listitem>
<listitem><para><xref linkend="LE42786-PARENT"></para>
</listitem>
<listitem><para><xref linkend="LE37273-PARENT"></para>
</listitem>
</itemizedlist>
<sect1 id="LE67057-PARENT">
<title id="LE67057-TITLE">Overview of FailSafe Diagnostic Commands</title>
<para><indexterm id="ITdiag-0"><primary>diagnostic command overview</primary>
</indexterm> <indexterm id="ITdiag-1"><primary>diags_nodename log file
</primary></indexterm> <indexterm id="ITdiag-2"><primary>connectivity,
testing with GUI</primary></indexterm><xref linkend="LE10721-PARENT">
shows the tests you can perform with Linux FailSafe diagnostic commands:
</para>
<table frame="topbot" id="LE10721-PARENT">
<title id="LE10721-TITLE">FailSafe Diagnostic Test Summary</title>
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="139*">
<colspec colwidth="347*">
<thead>
<row rowsep="1"><entry align="left" valign="bottom"><para>Diagnostic Test
</para></entry><entry align="left" valign="bottom"><para>Checks Performed
</para></entry></row>
</thead>
<tbody>
<row>
<entry align="left" valign="top"><para>resource</para></entry>
<entry align="left" valign="top"><para>Checks that the resource type parameters
are set</para><para>Check that the parameters are syntactically correct
</para><para>Validates that the parameters exist</para></entry>
</row>
<row>
<entry align="left" valign="top"><para>resource group</para></entry>
<entry align="left" valign="top"><para>Tests all resources defined in
the resource group</para></entry>
</row>
<row>
<entry align="left" valign="top"><para>failover policy</para></entry>
<entry align="left" valign="top"><para>Checks that the failover policy
exists</para><para>Checks that the failover domain contains a valid list
of hosts</para></entry>
</row>
<row>
<entry align="left" valign="top"><para>network connectivity</para></entry>
<entry align="left" valign="top"><para>Checks that the control interfaces
are on the same network</para><para>Checks that the nodes can communicate
with each other</para></entry>
</row>
<row>
<entry align="left" valign="top"><para>serial connection</para></entry>
<entry align="left" valign="top"><para>Checks that the nodes can reset
each other</para></entry>
</row>
</tbody>
</tgroup>
</table>
<para>All transactions are logged to the diagnostics file <filename>diags_
</filename><emphasis>nodename</emphasis> in the log directory.</para>
<para>You should test resource groups before starting FailSafe HA services
or starting a resource group. These tests are designed to check for resource
inconsistencies which could prevent the resource group from starting successfully.
</para>
</sect1>
<sect1 id="LE42786-PARENT">
<title id="LE42786-TITLE">Performing Diagnostic Tasks with the Cluster
Manager GUI</title>
<para>To test the components of a FailSafe system using the Cluster Manager
GUI, perform the following steps:</para>
<orderedlist>
<listitem><para>Select Task Manager on the FailSafe Toolchest.</para>
</listitem>
<listitem><para>On the left side of the display, click on the “Diagnostics”
category.</para>
</listitem>
<listitem><para>Select one of the diagnostics tasks that appear on the
right side of the display: “Test Connectivity,” “Test
Resources,” or “Test Failover Policy.”</para>
</listitem>
</orderedlist>
<sect2 id="fs-testconnectivity" role="fs-testconnectivity">
<title>Testing Connectivity with the Cluster Manager GUI</title>
<para><indexterm id="ITdiag-3"><primary>network connectivity</primary>
<secondary>testing with GUI</secondary></indexterm> <indexterm id="ITdiag-4">
<primary>serial connections</primary><secondary>testing with GUI</secondary>
</indexterm>When you select the “Test Connectivity” task from
the Diagnostics display, you can test the network and serial connections
on the nodes in your cluster by entering the requested inputs. You can
test all of the nodes in the cluster at one time, or you can specify an
individual node to test.</para>
</sect2>
<sect2 id="fs-testresources" role="fs-testresources">
<title>Testing Resources with the Cluster Manager GUI</title>
<para>When you select the “Test Resources” task from the Diagnostics
display, you can test the resources on the nodes in your cluster by entering
the requested inputs. You can test resources by type and by group. You
can test the resources of a resource type or in a resource group on all
of the nodes in the cluster at one time, or you can specify an individual
node to test. Resource tests are performed only on nodes in the resource
group's application failover domain.</para>
</sect2>
<sect2 id="fs-testfailoverpol" role="fs-testfailoverpol">
<title>Testing Failover Policies with the Cluster Manager GUI</title>
<para><indexterm id="ITdiag-5"><primary>failover policy</primary><secondary>
testing with GUI</secondary></indexterm>When you select the “Test
Failover Policy” task from the Diagnostics display, you can test
whether a failover policy is defined correctly. This test checks the failover
policy by validating the policy script, failover attributes, and whether
the application failover domain consists of valid nodes from the cluster.
</para>
</sect2>
</sect1>
<sect1 id="LE37273-PARENT">
<title id="LE37273-TITLE">Performing Diagnostic Tasks with the Cluster
Manager CLI</title>
<para>The following subsections described how to perform diagnostic tasks
on your system using the Cluster Manager CLI commands.</para>
<sect2>
<title> Testing the Serial Connections with the Cluster Manager CLI</title>
<para><indexterm id="ITdiag-6"><primary>serial connections</primary><secondary>
testing with CLI</secondary></indexterm>You can use the Cluster Manager
CLI to test the serial connections between the Linux FailSafe nodes. This
test pings each specified node through the serial line and produces an
error message if the ping is not successful. Do not execute this command
while FailSafe is running.</para>
<para>When you are using the Cluster Manager CLI, use the following command
to test the serial connections for the machines in a cluster</para>
<screen>cmgr> <userinput>test serial in cluster </userinput><replaceable>
A</replaceable> [<userinput>on node</userinput> <replaceable>B </replaceable><userinput>
node</userinput> <replaceable>C ...</replaceable>]</screen>
<para>This test yields an error message when it encounters its first error,
indicating the node that did not respond. If you receive an error message
after executing this test, verify the cable connections of the serial
cable from the indicated node's serial port to the remote power control
unit or the system controller port of the other nodes and run the test
again.</para>
<para>The following shows an example of the <command>test serial</command>
CLI command:</para>
<screen># <userinput>cluster_mgr</userinput>
Welcome to Linux<?Pub Caret> FailSafe Cluster Manager Command-Line Interface
cmgr> <userinput>test serial in cluster eagan on node cm1</userinput>
Success: testing serial...
Success: Ensuring Node Can Get IP Addresses For All Specified Hosts
Success: Number of IP addresses obtained for <cm1> = 1
Success: The first IP address for <cm1> = 128.162.19.34
Success: Checking serial lines via crsd (crsd is running)
Success: Successfully checked serial line
Success: Serial Line OK
Success: overall exit status:success, tests failed:0, total tests executed:1
</screen>
<para>The following shows an example of an attempt to run the <command>
test serial</command> CLI command while FailSafe is running (causing the
command to fail to execute):</para>
<screen>cmgr> <userinput>test serial in cluster eagan on node cm1</userinput>
Error: Cannot run the serial tests, diagnostics has detected FailSafe (ha_cmsd) is running
Failed to execute FailSafe tests/diagnostics ha
test command failed
cmgr></screen>
</sect2>
<sect2 id="LE11186-PARENT">
<title id="LE11186-TITLE">Testing Network Connectivity with the Cluster
Manager CLI</title>
<para><indexterm id="ITdiag-7"><primary>network connectivity</primary>
<secondary>testing with CLI</secondary></indexterm>You can use the Cluster
Manager CLI to test the network connectivity in a cluster. This test checks
if the specified nodes can communicate with each other through each configured
interface in the nodes. This test will not run if FailSafe is running.
</para>
<para>When you are using the Cluster Manager CLI, use the following command
to test the network connectivity for the machines in a cluster</para>
<screen>cmgr> <userinput>test connectivity in cluster </userinput><replaceable>
A</replaceable> [<userinput>on node</userinput> <replaceable>B </replaceable><userinput>
node</userinput> <replaceable>C ...</replaceable>]</screen>
<para>The following shows an example of the <command>test connectivity
</command> CLI command:</para>
<screen>cmgr> <userinput>test connectivity in cluster eagan on node cm1
</userinput>
Success: testing connectivity...
Success: checking that the control IP_addresses are on the same networks
Success: pinging address cm1-priv interface ef0 from host cm1
Success: pinging address cm1 interface ef1 from host cm1
Success: overall exit status:success, tests failed:0, total tests
executed:1</screen>
<para>This test yields an error message when it encounters its first error,
indicating the node that did not respond. If you receive an error message
after executing this test, verify that the network interface has been
configured up, using the <command>ifconfig</command> command, for example:
</para>
<para># <userinput>/usr/etc/ifconfig ec3</userinput></para>
<screen>ec3: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,FILTMULTI,MULTICAST>
  inet 190.0.3.1 netmask 0xffffff00 broadcast 190.0.3.255</screen>
<para>The UP in the first line of output indicates that the interface
is configured up.</para>
<para>If the network interface is configured up, verify that the network
cables are connected properly and run the test again.</para>
</sect2>
<sect2 id="LE28447-PARENT">
<title id="LE28447-TITLE">Testing Resources with the Cluster Manager CLI
</title>
<para>You can use the Cluster Manager CLI to test any configured resource
by resource name or by resource type.</para>
<para>The Cluster Manager CLI uses the following syntax to test a resource
by name:</para>
<screen>cmgr> <userinput>test resource </userinput><replaceable>A</replaceable> <userinput>
of resource_type</userinput> <replaceable>B </replaceable><userinput>
in cluster</userinput> <replaceable>C </replaceable>[<userinput>
on node</userinput> <replaceable>D </replaceable><userinput>node
</userinput> <replaceable>E ...</replaceable>]</screen>
<para>The following shows an example of testing a resource by name:</para>
<screen>cmgr> <userinput>test resource /disk1 of resource_type filesystem in cluster eagan on machine cm1
</userinput>
Success: *** testing node resources on node cm1 ***
Success: *** testing all filesystem resources on node cm1 ***
Success: testing resource /disk1 of resource type filesystem on node cm1
Success: overall exit status:success, tests failed:0, total tests executed:1
</screen>
<para>The Cluster Manager CLI uses the following syntax to test a resource
by resource type:</para>
<screen>cmgr> <userinput>test resource_type</userinput> <replaceable>
A </replaceable><userinput>in cluster</userinput> <replaceable>B
</replaceable>[<userinput>on node</userinput> <replaceable>C </replaceable><userinput>
node</userinput> <replaceable>D...</replaceable>]</screen>
<para>The following shows an example of testing resources by resource
type:</para>
<screen>cmgr> <userinput>test resource_type filesystem in cluster eagan on machine cm1
</userinput>
Success: *** testing node resources on node cm1 ***
Success: *** testing all filesystem resources on node cm1 ***
Success: testing resource /disk4 of resource type filesystem on node cm1
Success: testing resource /disk5 of resource type filesystem on node cm1
Success: testing resource /disk2 of resource type filesystem on node cm1
Success: testing resource /disk3 of resource type filesystem on node cm1
Success: testing resource /disk1 of resource type filesystem on node cm1
Success: overall exit status:success, tests failed:0, total tests executed:5
</screen>
<para>You can use the CLI to test volume and filesystem resources in <emphasis>
destructive</emphasis> mode. This provides a more thorough test of filesystems
and volumes. CLI tests will not run in destructive mode if FailSafe is
running.</para>
<para>The Cluster Manager CLI uses the following syntax for the commands
that test resources in destructive mode:</para>
<screen>cmgr> <userinput>test resource </userinput><replaceable>A</replaceable> <userinput>
of resource_type</userinput> <replaceable>B </replaceable><userinput>
in cluster</userinput> <replaceable>C </replaceable>[<userinput>
on node</userinput> <replaceable>D</replaceable><userinput> node
</userinput> <replaceable>C ...</replaceable>] <userinput>destructive
</userinput></screen>
<para>The following sections describe the diagnostic tests available for
resources.</para>
<sect3>
<title> Testing Logical Volumes</title>
<para><indexterm id="ITdiag-8"><primary>volume</primary><secondary>testing
with CLI</secondary></indexterm>You can use the Cluster Manager CLI to
test the logical volumes in a cluster. This test checks if the specified
volume is configured correctly.</para>
<para>When you are using the Cluster Manager CLI, use the following command
to test a logical volume:</para>
<screen>cmgr> <userinput>test resource </userinput><replaceable>A</replaceable> <userinput>
of resource_type volume on cluster</userinput> <replaceable>B </replaceable>[<userinput>
on node</userinput> <replaceable>C </replaceable><userinput>node
</userinput> <replaceable>D ...</replaceable>]</screen>
<para>The following example tests a logical volume:</para>
<screen>cmgr> <userinput>test resource alternate of resource_type volume on cluster eagan
</userinput>
Success: *** testing node resources on node cm1 ***
Success: *** testing all volume resources on node cm1 ***
Success: running resource type volume tests on node cm1
Success: *** testing node resources on node cm2 ***
Success: *** testing all volume resources on node cm2 ***
Success: running resource type volume tests on node cm2
Success: overall exit status:success, tests failed:0, total tests executed:2
cmgr></screen>
<para>The following example tests a logical volume in destructive mode:
</para>
<screen>cmgr> <userinput>test resource alternate of resource_type volume on cluster eagan destructive
</userinput>
Warning: executing the tests in destructive mode
Success: *** testing node resources on node cm1 ***
Success: *** testing all volume resources on node cm1 ***
Success: running resource type volume tests on node cm1
Success: successfully assembled volume: alternate
Success: *** testing node resources on node cm2 ***
Success: *** testing all volume resources on node cm2 ***
Success: running resource type volume tests on node cm2
Success: successfully assembled volume: alternate
Success: overall exit status:success, tests failed:0, total tests executed:2
cmgr></screen>
</sect3>
<sect3>
<title>Testing Filesystems</title>
<para>You can use the Cluster Manager CLI to test the filesystems configured
in a cluster. This test checks if the specified filesystem is configured
correctly and, in addition, checks whether the volume the filesystem will
reside on is configured correctly.<indexterm id="ITdiag-9"><primary>filesystem
</primary><secondary>testing with CLI</secondary></indexterm></para>
<para>When you are using the Cluster Manager CLI, use the following command
to test a filesystem:</para>
<screen>cmgr> <userinput>test resource </userinput><replaceable>A</replaceable> <userinput>
of resource_type filesystems on cluster</userinput> <replaceable>
B </replaceable>[<userinput>on node</userinput> <replaceable>C</replaceable><userinput>
 node</userinput> <replaceable>D ...</replaceable>]</screen>
<para>The following example tests a filesystem. This example first uses
a CLI <command>show</command> command to display the filesystems that
have been defined in a cluster.</para>
<screen>cmgr> <userinput>show resources of resource_type filesystem in cluster eagan
</userinput>
/disk4 type filesystem
/disk5 type filesystem
/disk2 type filesystem
/disk3 type filesystem
/disk1 type filesystem
cmgr> <userinput>test resource /disk4 of resource_type filesystem in cluster eagan on node cm1
</userinput>
Success: *** testing node resources on node cm1 ***
Success: *** testing all filesystem resources on node cm1 ***
Success: successfully mounted filesystem: /disk4
Success: overall exit status:success, tests failed:0, total tests executed:1
cmgr></screen>
<para>The following example tests a filesystem in destructive mode:</para>
<screen>cmgr> <userinput>test resource /disk4 of resource_type filesystem in cluster eagan on node cm1 destructive
</userinput>
Warning: executing the tests in destructive mode
Success: *** testing node resources on node cm1 ***
Success: *** testing all filesystem resources on node cm1 ***
Success: successfully mounted filesystem: /disk4
Success: overall exit status:success, tests failed:0, total tests executed:1
cmgr></screen>
</sect3>
<sect3>
<title>Testing NFS Filesystems</title>
<para>You can use the Cluster Manager CLI to test the NFS filesystems
configured in a cluster. This test checks if the specified NFS filesystem
is configured correctly and, in addition, checks whether the volume the
NFS filesystem will reside on is configured correctly.<indexterm id="ITdiag-10">
<primary>filesystem</primary><secondary>NFS, testing with CLI</secondary>
</indexterm> <indexterm id="ITdiag-11"><primary>NFS filesystem testing
with CLI</primary></indexterm></para>
<para>When you are using the Cluster Manager CLI, use the following command
to test an NFS filesystem:</para>
<screen>cmgr> <userinput>test resource </userinput><replaceable>A</replaceable> <userinput>
of resource_type NFS on cluster</userinput> <replaceable>B </replaceable>[<userinput>
on node</userinput> <replaceable>C </replaceable><userinput>node
</userinput> <replaceable>D ...</replaceable>]</screen>
<para>The following example tests an NFS filesystem:</para>
<screen>cmgr> <userinput>test resource /disk4 of resource_type NFS in cluster eagan
</userinput>
Success: *** testing node resources on node cm1 ***
Success: *** testing all NFS resources on node cm1 ***
Success: *** testing node resources on node cm2 ***
Success: *** testing all NFS resources on node cm2 ***
Success: overall exit status:success, tests failed:0, total tests executed:2
cmgr></screen>
</sect3>
<sect3>
<title>Testing statd Resources</title>
<para>You can use the Cluster Manager CLI to test the statd resources
configured in a cluster. When you are using the Cluster Manager CLI, use
the following command to test an NFS filesystem:<indexterm id="ITdiag-12">
<primary>statd</primary><secondary>testing with CLI</secondary></indexterm> <indexterm
id="ITdiag-13"><primary>resource</primary><secondary>statd, testing with
CLI</secondary></indexterm></para>
<screen>cmgr> <userinput>test resource </userinput><replaceable>A</replaceable> <userinput>
of resource_type statd on cluster</userinput> <replaceable>B </replaceable>[<userinput>
on node</userinput> <replaceable>C </replaceable><userinput>node
</userinput> <replaceable>D ...</replaceable>]</screen>
<para>The following example tests a statd resource:</para>
<screen>cmgr> <userinput>test resource /disk1/statmon of resource_type statd in cluster eagan
</userinput>
Success: *** testing node resources on node cm1 ***
Success: *** testing all statd resources on node cm1 ***
Success: *** testing node resources on node cm2 ***
Success: *** testing all statd resources on node cm2 ***
Success: overall exit status:success, tests failed:0, total tests executed:2
cmgr></screen>
</sect3>
<sect3>
<title>Testing Netscape-web Resources</title>
<para>You can use the Cluster Manager CLI to test the Netscape Web resources
configured in a cluster.<indexterm id="ITdiag-14"><primary>Netscape Web
</primary><secondary>testing with CLI</secondary></indexterm> <indexterm
id="ITdiag-15"><primary>resource</primary><secondary>Netscape Web, testing
with CLI</secondary></indexterm></para>
<para>When you are using the Cluster Manager CLI, use the following command
to test a Netscape-web resource:</para>
<screen>cmgr> <userinput>test resource </userinput><replaceable>A</replaceable> <userinput>
of resource_type Netscape_web on cluster</userinput> <replaceable>
B </replaceable>[<userinput>on node</userinput> <replaceable>C
</replaceable><userinput>node</userinput> <replaceable>D ...</replaceable>]
</screen>
<para>The following example tests a Netscape-web resource. In this example,
the Netscape-web resource on node cm2 failed the diagnostic test.</para>
<screen>cmgr> <userinput>test resource nss-enterprise of resource_type Netscape_web in cluster eagan
</userinput>
Success: *** testing node resources on node cm1 ***
Success: *** testing all Netscape_web resources on node cm1 ***
Success: *** testing node resources on node cm2 ***
Success: *** testing all Netscape_web resources on node cm2 ***
Warning: resource nss-enterprise has invaild script /var/netscape/suitespot/https-ha85 location
Warning: /var/netscape/suitespot/https-ha85/config/magnus.conf must contain the
"Port" parameter
Warning: /var/netscape/suitespot/https-ha85/config/magnus.conf must contain the
"Address" parameter
Warning: resource nss-enterprise of type Netscape_web failed
Success: overall exit status:failed, tests failed:1, total tests executed:2
Failed to execute FailSafe tests/diagnostics ha
test command failed
cmgr></screen>
</sect3>
<sect3 id="LE62758-PARENT">
<title id="LE62758-TITLE">Testing Resource Groups</title>
<para>You can use the Cluster Manager CLI to test a resource group. This
test cycles through the resource tests for all of the resources defined
for a resource group. Resource tests are performed only on nodes in the
resource group's application failover domain.<indexterm id="ITdiag-16">
<primary>resource group</primary><secondary>testing with CLI</secondary>
</indexterm> <indexterm id="ITdiag-17"><primary>Netscape servers, testing
with CLI</primary></indexterm></para>
<para>The Cluster Manager CLI uses the following syntax for the commands
that test resource groups:</para>
<screen>cmgr> <userinput>test resource_group </userinput><replaceable>
A</replaceable> <userinput>in cluster</userinput> <replaceable>
B </replaceable>[<userinput>on node</userinput> <replaceable>C </replaceable><userinput>
node</userinput> <replaceable>D</replaceable><replaceable> ...
</replaceable>]</screen>
<para>The following example tests a resource group. This example first
uses a CLI <command>show</command> command to display the resource groups
that have been defined in a cluster.</para>
<screen>cmgr> <userinput>show resource_groups in cluster eagan</userinput>
Resource Groups:
  nfs2
  informix
cmgr> <userinput>test resource_group nfs2 in cluster eagan on machine cm1
</userinput>
Success: *** testing node resources on node cm1 ***
Success: testing resource /disk4 of resource type NFS on node cm1
Success: testing resource /disk3 of resource type NFS on node cm1
Success: testing resource /disk3/statmon of resource type statd on node cm1
Success: testing resource 128.162.19.45 of resource type IP_address on node cm1
Success: testing resource /disk4 of resource type filesystem on node cm1
Success: testing resource /disk3 of resource type filesystem on node cm1
Success: testing resource dmf1 of resource type volume on node cm1
Success: testing resource dmfjournals of resource type volume on node cm1
Success: overall exit status:success, tests failed:0, total tests executed:16
cmgr></screen>
</sect3>
</sect2>
<sect2 id="LE29671-PARENT">
<title id="LE29671-TITLE">Testing Failover Policies with the Cluster Manager
CLI</title>
<para>You can use the Cluster Manager CLI to test whether a failover policy
is defined correctly. This test checks the failover policy by validating
the policy script, failover attributes, and whether the application failover
domain consists of valid nodes from the cluster.<indexterm id="ITdiag-18">
<primary>failover policy</primary><secondary>testing with CLI</secondary>
</indexterm></para>
<para>The Cluster Manager CLI uses the following syntax for the commands
that test a failover policy:</para>
<screen>cmgr> <userinput>test failover_policy </userinput><replaceable>
A</replaceable> <userinput>in cluster</userinput> <replaceable>
B </replaceable>[<userinput>on node</userinput> <replaceable>C</replaceable><userinput>
 node</userinput> <replaceable>D</replaceable><replaceable>
 ...</replaceable>]</screen>
<para>The following example tests a failover policy. This example first
uses a CLI <command>show</command> command to display the failover policies
that have been defined in a cluster.</para>
<screen>cmgr> <userinput>show failover_policies</userinput>
Failover Policies:
  reverse
  ordered-in-order
cmgr> <userinput>test failover_policy reverse in cluster eagan</userinput>
Success: *** testing node resources on node cm1 ***
Success: testing policy reverse on node cm1
Success: *** testing node resources on node cm2 ***
Success: testing policy reverse on node cm2
Success: overall exit status:success, tests failed:0, total tests executed:2
cmgr></screen>
</sect2>
</sect1>
</chapter>
<?Pub *0000028120>
![[BACK]](/icons/back.gif){kind=icon}
Return to diag.sgml CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [Development] / projects / failsafe / FailSafe-books / LnxFailSafe_AG