cancel
Showing results for 
Search instead for 
Did you mean: 

problem with fencing [solaris box]

sam321
Level 4

following is my configuration

 

bash-3.00# hastatus -sum
 
-- SYSTEM STATE
-- System               State                Frozen
 
A  TEST1                RUNNING              0
A  TEST2                RUNNING              0
 
-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State
 
B  ClusterServices TEST1                Y          N               ONLINE
B  ClusterServices TEST2                Y          N               OFFLINE
B  cvm             TEST1                Y          N               ONLINE
B  cvm             TEST2                Y          N               ONLINE
bash-3.00# uname -a
SunOS TEST1 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V240
bash-3.00# pkginfo -l VRTSvcs
 
   PKGINST:  VRTSvcs
      NAME:  Veritas Cluster Server by Symantec
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  5.0
   BASEDIR:  /
    VENDOR:  Symantec Corporation
      DESC:  Veritas Cluster Server by Symantec
    PSTAMP:  Veritas-5.0-05/30/06-09:01:00
  INSTDATE:  Mar 26 2011 21:48
    STATUS:  completely installed
     FILES:      160 installed pathnames
                  22 shared pathnames
                   2 linked files
                  45 directories
                  83 executables
              141345 blocks used (approx)
 
bash-3.00#
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 (TEST1)
          1 (TEST2)
 
 RFSM State Information:
        node   0 in state  8 (running)
        node   1 in state  8 (running)
 
bash-3.00# vxdisk -oalldgs list
DEVICE       TYPE            DISK         GROUP        STATUS
c1t0d0s2     auto:none       -            -            online invalid
c1t1d0s2     auto:none       -            -            online invalid
c1t2d0       auto:sliced     -            (oradg)      online
c1t3d0       auto:sliced     -            (oradg)      online
6120-63200_0 auto:sliced     -            (fendg)      online
6120-63200_1 auto:sliced     -            (fendg)      online
6120-63200_2 auto:sliced     -            -            online
6120-63200_3 auto:sliced     -            -            online
6120-63200_4 auto:sliced     -            (fendg)      online
 
 
 
now when i do vxfenadm to see the keys it gives me error
am i going wron anywhere.Need your help guys
 
bash-3.00# vxfenadm -g all -f /etc/vxfendg
VCS FEN vxfenadm ERROR V-11-2-1116 Cannot open: fendg
VCS FEN vxfenadm ERROR V-11-2-1132 Open of file failed, errno = 0
VCS FEN vxfenadm ERROR V-11-2-1205 READ_KEYS failed for: fendg
VCS FEN vxfenadm ERROR V-11-2-1133 Error returned
bash-3.00# cat /etc/vxfendg
fendg
 
 
 
thaks in advance
 
Regards 
Kuldeep.
1 ACCEPTED SOLUTION

Accepted Solutions

Gaurav_S
Moderator
Moderator
   VIP    Certified

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

View solution in original post

3 REPLIES 3

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

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

Gaurav_S
Moderator
Moderator
   VIP    Certified

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

sam321
Level 4

ohh i got it now i was using wrong file

i shud have user the command

vxfenadm -g all -f /etc/vxfentab