HP Serviceguard manual Cmquerycl Options, Speeding up the Process

cmquerycl Options

Speeding up the Process

In a larger or more complex cluster with many nodes, networks or disks, the cmquerycl command may take several minutes to complete. To speed up the configuration process, you can direct the command to return selected information only by using the -kand -woptions:

-keliminates some disk probing, and does not return information about potential cluster lock volume groups and lock physical volumes.

-w local lets you specify local network probing, in which LAN connectivity is verified between interfaces within each node only. This is the default when you use cmquerycl with the-Coption.

(Do not use -w local if you need to discover nodes and subnets for a cross-subnet configuration; see “Full Network Probing” below.)

-w none skips network querying. If you have recently checked the networks, this option will save time.

Specifying the Address Family for the Cluster Hostnames

You can use the -aoption to tell Serviceguard to resolve cluster node names (as well as Quorum Server hostnames, if any) to IPv4 addresses only (-a ipv4) IPv6 addresses only (-a ipv6), or both (-a any). You can also configure the address family by means of the HOSTNAME_ADDRESS_FAMILY in the cluster configuration file.

IMPORTANT: See “About Hostname Address Families: IPv4-Only,IPv6-Only, and Mixed Mode” (page 106) for a full discussion, including important restrictions for IPv6–only and mixed modes.

If you use the -aoption, Serviceguard will ignore the value of the HOSTNAME_ADDRESS_FAMILY parameter in the existing cluster configuration, if any, and attempt to resolve the cluster and Quorum Server hostnames as specified by the -aoption:

•If you specify -a ipv4, each of the hostnames must resolve to at least one IPv4 address; otherwise the command will fail.

•Similarly, if you specify -a ipv6, each of the hostnames must resolve to at least one IPv6 address; otherwise the command will fail.

•If you specify -a any, Serviceguard will attempt to resolve each hostname to an IPv4 address, then, if that fails, to an IPv6 address.

If you do not use the -aoption:

•If a cluster is already configured, Serviceguard will use the value configured for

HOSTNAME_ADDRESS_FAMILY, which defaults to IPv4.

•If no cluster configured, and Serviceguard finds at least one IPv4 address that corresponds to the local node's hostname (that is, the node on which you are running cmquerycl), Serviceguard will attempt to resolve all hostnames to IPv4 addresses. If no IPv4 address is found for a given hostname, Serviceguard will look for an IPv6 address. (This is the same behavior as if you had specified -a any.)

Specifying the Address Family for the Heartbeat

To tell Serviceguard to use only IPv4, or only IPv6, addresses for the heartbeat, use the -hoption. For example, to use only IPv6 addresses:

cmquerycl -v -h ipv6 -C $SGCONF/clust1.conf -n ftsys9 -n ftsys10

•-h ipv4 tells Serviceguard to discover and configure only IPv4 subnets. If it does not find any eligible subnets, the command will fail.

•-h ipv6 tells Serviceguard to discover and configure only IPv6 subnets. If it does not find any eligible subnets, the command will fail.

Configuring the Cluster 187