ajit_jain
15 years agoLevel 2
SCSI reservation on data disk
Hello All,
I have installed VCS HA clusterware on solaris 10 sparc arch. I have configured vxfen in SCSI3 mode.
What I observe is that all the disks which are part of co-ordinated DG have SCSI3 reservation but my data
disk doesn't have any reservation. My apprehension is that if VCS nodes doesnt do reservation how VCS is
going to protect the disk from outside world, in fact I tried to write on my data disk from a linux box which is not
the part of the cluster?
I am wondering if I have done the configuration correct?
Please find some of command output below which might help to analyze if there is some
configuration mistake:
===============
bash-3.00# vxfenadm -d
I/O Fencing Cluster Information:
================================
Fencing Protocol Version: 201
Fencing Mode: SCSI3
Fencing SCSI3 Disk Policy: raw
Cluster Members:
0 (Solaris146)
* 1 (Solaris148)
RFSM State Information:
node 0 in state 8 (running)
node 1 in state 8 (running)
bash-3.00# hagrp -state
#Group Attribute System Value
groupw State Solaris146 |OFFLINE|
groupw State Solaris148 |ONLINE|
bash-3.00# hares -state
#Resource Attribute System Value
fodg State Solaris146 OFFLINE
fodg State Solaris148 ONLINE
fofs State Solaris146 OFFLINE
fofs State Solaris148 ONLINE
bash-3.00#
============
I have installed VCS HA clusterware on solaris 10 sparc arch. I have configured vxfen in SCSI3 mode.
What I observe is that all the disks which are part of co-ordinated DG have SCSI3 reservation but my data
disk doesn't have any reservation. My apprehension is that if VCS nodes doesnt do reservation how VCS is
going to protect the disk from outside world, in fact I tried to write on my data disk from a linux box which is not
the part of the cluster?
I am wondering if I have done the configuration correct?
Please find some of command output below which might help to analyze if there is some
configuration mistake:
===============
bash-3.00# vxfenadm -d
I/O Fencing Cluster Information:
================================
Fencing Protocol Version: 201
Fencing Mode: SCSI3
Fencing SCSI3 Disk Policy: raw
Cluster Members:
0 (Solaris146)
* 1 (Solaris148)
RFSM State Information:
node 0 in state 8 (running)
node 1 in state 8 (running)
bash-3.00# hagrp -state
#Group Attribute System Value
groupw State Solaris146 |OFFLINE|
groupw State Solaris148 |ONLINE|
bash-3.00# hares -state
#Resource Attribute System Value
fodg State Solaris146 OFFLINE
fodg State Solaris148 ONLINE
fofs State Solaris146 OFFLINE
fofs State Solaris148 ONLINE
bash-3.00#
============
Hi Ajit,
To answer your questions......
Once the DG is imported by VCS, you will see the registraiton & reservation of only 1 node (in case of a failover diskgroup) ... However if its a Shared diskgroup (CVM diskgroup), then you would see registration & reservation of both nodes....
Yes you are right, VCS diskgroup agent imports the diskgroup with specific options ( -o groupreserve) then only reservations are placed.... If you have a normal filesystem where diskgroup was not imported with above options, then it is NOT protected by VCS IOFencing..... however you can configure that FS in VCS ... so basically you just loose the split brain protection (which is real purpose of fencing)....
Gaurav