Forum Discussion

IT-SYSMIKE's avatar
IT-SYSMIKE
Level 2
11 years ago

V-35-410: Cluster server not running on local node on solaris

Hello, We had a hardware failure and on restarting the server we could not reach our mount points or even start the server with hastart but nothing was started and we keep getting the error in Titl...
  • Gaurav_S's avatar
    11 years ago

    Hello

    looks like you have made your cluster to use IOFencing however fencing is not configured correctly ..

    refer below logs

    2013/11/28 11:11:46 VCS NOTICE V-16-1-52006 UseFence=SCSI3. Fencing is enabled
    2013/11/28 11:11:46 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
    2013/11/28 11:12:01 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...

    2013/11/28 11:12:16 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying..

     

    See if your main.cf contains below line

    UseFence = SCSI3

    # cat /etc/VRTSvcs/conf/config/main.cf |grep -i usefence

     

    Above line exists in main.cf, that means cluster is intended to use fencing which is not configured correctly.

    IOFencing provided data protection from cluster split brain situations

     

    Refer to VCS admin guide & see the article on how to configure IOFencing. If you do not intend to use IOFencing (which is not recommended), you can remove the entry from main.cf after stopping the cluster & start the cluster again.

     

    Link to documentation

     

    https://sort.symantec.com/documents

    IOFencing link for VCS 5.1 on solaris

    https://sort.symantec.com/public/documents/sf/5.1/solaris/html/vcs_admin/ch_admin_fencing.html#760094

     

    G