cancel
Showing results for 
Search instead for 
Did you mean: 

The error occurs when hastart.

smileagain
Level 4
Partner

product : sfwha 5.1

os : windows 2003 enterprise

issue : The active normal, but when the hastart in the standby to the error occurred.

          hastart

          VCS INFO V-16-1-11020 Starting HAD on local node

          VCS ERROR V-16-11109 Cannot start had. Error=1068, ErrorText=The dependency service or group failed to start.

 

-cluster status 

active node

C:\Users\Administrator.AD> lltstat -n
LLT node information:
    Node                 State     Links
     0 TEST1             OPEN        2
   * 1 TEST2             OPEN        2
C:\Users\Administrator.AD> gabconfig -a
GAB Port Memberships
===============================================================
Port a gen   143b01 membership 01
Port h gen   143b03 membership ;1
Port h gen   143b03    visible 0
C:\Users\Administrator.AD>

 

standby node

C:\Users\Administrator.AD> lltstat -n
LLT node information:
    Node                 State     Links
   * 0 TEST1             OPEN        2
     1 TEST2             OPEN        2
C:\Users\Administrator.AD> gabconfig -a
GAB Port Memberships
===============================================================
Port a gen   143b01 membership 01
C:\Users\Administrator.AD>

 

6 REPLIES 6

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

check is vcscomms service is started on that node. you'll probably find its not which means LLT and/or GAB is not running.

Wally_Heim
Level 6
Employee

Hi smileagain,

If you check your event logs you may have an "incorrect function" error when trying to start the vcscomm service.  This typically means that there is a problem with the LLT configuration.  If this is the case then run the Veritas Cluster Configuration Wizard (vcw) to reconfigure the heartbeat network.

Thank you,

Wally

z_yf009
Not applicable
Partner

Hi smileagain,

If you check your event logs you may have an "incorrect function" error when trying to start the vcscomm service.  This typically means that there is a problem with the LLT configuration.  If this is the case then run the Veritas Cluster Configuration Wizard (vcw) to reconfigure the heartbeat network.

Thank you,

Wally

smileagain
Level 4
Partner

Active NODE

C:\Users\Administrator.AD> lltstat -n
LLT node information:
    Node                 State     Links
     0 TEST1             OPEN        2
   * 1 TEST2             OPEN        2
C:\Users\Administrator.AD> gabconfig -a
GAB Port Memberships
===============================================================
Port a gen   143b01 membership 01
Port h gen   143b03 membership ;1
Port h gen   143b03    visible 0
C:\Users\Administrator.AD>

 

Standby NODE


C:\Users\Administrator.AD> lltstat -n
LLT node information:
    Node                 State     Links
   * 0 TEST1             OPEN        2
     1 TEST2             OPEN        2
C:\Users\Administrator.AD> gabconfig -a
GAB Port Memberships
===============================================================
Port a gen   143b01 membership 01
C:\Users\Administrator.AD>

mikebounds
Level 6
Partner Accredited

As others have said, issue is probably vcscomms is not started so use "net start" to list running services to check if vcscomm is running and if not then start this service using "net start vcscomm" or start from service manager.

Mike

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Seems port a (GAB) is running on both nodes, but port h only on one node.

Seems you have only issued 'hastart' on one node.

Issue hastart on standby node as well.