cmquerycl: where does it extract the informations?

[Enrico Venturi]

Hi all,
the man pages of "cmquerycl" command explain that it can provide, by the -C option, a template of the configuration file as output, i.e. cmquerycl -v -n node1 -n node2 -n node3 -C /tmp/clusterconf.ascii provides a description of the cluster possible configuration of the three nodes node1 ... node3. I didn't understand WHERE those data are extracted ... I mean: do they derive from HW analysis? or from some other data file? Concerning the heartbeat (this in more in detail my doubt): how the command can provide a list of the possible heartbeats of the node? Does it check for the cross connectivity between the nodes?
I thank you in advance.
Regards
Enrico

[James R. Ferguson · Accepted solution]

Hi Venturi:

'cmquerycl' gathers its configuration data by probing the hardware its running on as well as servers over the network to see if they are running MC/ServiceGuard.

The entries defined in /etc/services that begin with "hacl" (high-availablity cluster) are part of, and vital to, this process.

Regards!

...JRF...

[Sanjay_6]

Hi Venturi,

"cmquercl" scan all the IO paths and the lan paths. It reads the PV info from all the disks and the lan ip's and other info. It sort of queries them to see to which VG they belong to. This is done for all the nodes individually. It also queries the disk for the timeouts for those disks, so that it will be easy for you to settle on the lock disk. The man pages of "cmquerycl" is very helpful in this regard.

The data "cmquerycl" generates is not produced by any earlier hardware info, it is generated by the command querying all the disks, lan and vg's at that time.

Hope this helps.

thanks