03-30-2011 12:48 AM
following is my configuration
Solved! Go to Solution.
03-30-2011 10:45 AM
Kuldeep,
if you are trying to see the keys on coordinator disks then you are running command on wrong file .. you should run it on
# vxfenadm -g all -f /etc/vxfentab
/etc/vxfentab will be populated automatically once fencing modules read the coordinator configuration. /etc/vxfendg just stores the configuration as to what is the diskgorup name of coordinator diskgroup, you can't read keys form it
or else you can read the configuration in your case manually by using:
# vxfenadm -g /dev/vx/rdmp/6120-63200_0
Gaurav
03-30-2011 07:03 AM
You need to run the command against the actual raw device names using OS_NATIVE_NAME.
Run:
vxdisk -o alldgs -e list |grep fendg
Add the raw device names to a file:
e.g.
# vi /tmp/disklist
For example:
/dev/rdsk/c3t216000C0FF898E3Dd2s2
/dev/rdsk/c3t216000C0FF898E3Dd3s2
/dev/rdsk/c3t216000C0FF898E3Dd4s2
Read the existing keys:
# vxfenadm -g all -f /tmp/disklist
03-30-2011 10:45 AM
Kuldeep,
if you are trying to see the keys on coordinator disks then you are running command on wrong file .. you should run it on
# vxfenadm -g all -f /etc/vxfentab
/etc/vxfentab will be populated automatically once fencing modules read the coordinator configuration. /etc/vxfendg just stores the configuration as to what is the diskgorup name of coordinator diskgroup, you can't read keys form it
or else you can read the configuration in your case manually by using:
# vxfenadm -g /dev/vx/rdmp/6120-63200_0
Gaurav
03-30-2011 10:53 AM
ohh i got it now i was using wrong file
i shud have user the command
vxfenadm -g all -f /etc/vxfentab