Forum Discussion

tanyshka's avatar
tanyshka
Level 3
11 years ago

VCS ERROR V-16-1-10600 Cannot connect to VCS engine

I have installed Symantec Storage Foundation v.4.0 for Linux, Veritas Cluster Servises 4.1 with oracle agents on Red Hat Enterprise Linux 4 update 8.

I have installed two nodes in the cluster. Everything worked perfectly. There has been a power failure. After that one node has changed status to UNKNOWN.

node1.JPG

 

node2.JPG

In log file:

node3.JPG

I I tried to implement the recommendations in http://www.symantec.com/business/support/index?page=content&id=TECH54873  

It did not help.

What to do to start another node (erpnode2)?

 

business continuity
Cluster Server
Error messages
Linux
Recovering
  • rsharma1's avatar
    rsharma1
    11 years ago

    based on the o/p above vxfen is already started now on node2 now.  You may just execute a 'hastart'  on node2.

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    So, can we assume that frencing was configured and working before the power failure? 

    When you tried to manually start fencing as per TECH54873, what was the output?

    Please show us output of 'gabconfig -a' on both nodes.

  • tanyshka's avatar
    tanyshka
    Level 3
    11 years ago

    Yes frencing was configured and working before perfectly. It was set up specialist.

    [root@erpnode2 ~]# /etc/init.d/vxfen start
    Starting VxFEN:
    VxFEN: module already loaded and configured

    [root@erpnode2 ~]# gabconfig -a
    GAB Port Memberships
    ===============================================================
    Port a gen   f75302 membership 01
    Port b gen   f75303 membership 01

    [root@erpnode1 ~]# gabconfig -a
    GAB Port Memberships
    ===============================================================
    Port a gen   f75302 membership 01
    Port b gen   f75303 membership 01
    Port h gen   f75304 membership 0
    Port h gen   f75304    visible ;1

     

     

  • rsharma1's avatar
    rsharma1
    Level 5
    11 years ago

    based on the o/p above vxfen is already started now on node2 now.  You may just execute a 'hastart'  on node2.