1753844 Members
7372 Online
108806 Solutions
New Discussion юеВ

cluster concern

 
SOLVED
Go to solution
gany59
Regular Advisor

cluster concern

Hello techies,

I have the output on the cluster configuration file like below :

FIRST_CLUSTER_LOCK_VG /dev/vgsyb
for node 1:
FIRST_CLUSTER_LOCK_PV /dev/dsk/c2t0d0
for node 2:
FIRST_CLUSTER_LOCK_PV /dev/dsk/c6t0d0

I got confused that, in the cluster concept we are exporting the same disk to the adoptive node. then how the disk device file is differ.

Please clarrify this. Lock disk in the one what we shared to all the nodes right ?
3 REPLIES 3
Torsten.
Acclaimed Contributor

Re: cluster concern

The cluster lock disk has to be the same disk, but for node1 it is named c2t0d0, the name on node2 is c6t0d0 - still the same disk.

Check vgdisplay of vgsyb to confirm.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Ismail Azad
Esteemed Contributor
Solution

Re: cluster concern

Hi gany,

The kernel of node1 gives the disk an instance number and by default the number after c on Legacy DSF's default to the instance of the bus connected to that disk. Node2 has a different kernel and it generates a different instance number and hence a different device file for the same disk on different nodes. So relating to your question would speak in terms of "the kernel in node1" and the "kernel in node2" and hence as instance numbers are given by the kernel... will generate different DSFs.

Regards
Ismail Azad
Read, read and read... Then read again until you read "between the lines".....
gany59
Regular Advisor

Re: cluster concern

Thanks a ton Ismail!

I got a clear picture on that ... :) keeps rocking