cancel
Showing results for 
Search instead for 
Did you mean: 

After update VSFHA from 5.1SP1a to 5.1SP2 dont start VCSComm

 

After the update VSFHA for Windows from version 5.1SP1a to 5.1SP2 in one of two node service does not start "Veritas VCSComm Startup" and no start "Veritas High availability engine". When was update no errors, recovery does not help.
OS Windows 2003 EE x64. Installing the latest updates to the OS does not help.
Please help solve this problem.
 
1 Solution

Accepted Solutions
Accepted Solution!

Hi Shark1000,   We need to

Hi Shark1000,

 

We need to determine if GAB and LLT are simply disabled or if they had problems during the upgrade and did not get installed.

 

To check to see if GAB is disabled check the following registry location:

   hklm\SYSTEM\CurrentControlSet\Services\Gab

There should be a "Start" key in that location.  If the value is 4 then it is disabled.  Change the value to 2.

 

To check if LLT is disabled check the following registry location:

  hklm\SYSTEM\CurrentControlSet\Services\llt

There should be a "Start" key in that location.  If the value is 4 then it is disabled.  Change the value to 2.

 

If, however, neither of these registry locations exist then there was a problem reinstalling GAB and LLT during the upgrade.  If this is the case, I would recommend opening a case with Symantec Technical Support so we can determine why GAB and LLT failed to install and correct that issue.

 

Thanks,

Wally

View solution in original post

7 Replies

Did you upgrade the nodes

Did you upgrade the nodes one-by-one or both at the same time?

Are you saying that services are starting on one node and not on the other node?

Hi Shark1000,   The Veritas

Hi Shark1000,

 

The Veritas High Availability engine service depends on the Veritas VCSComm service, so if the VCSComm service is not start then that would cause the Veritas High Availability engine service not to start.  In other words, resolving the VCSComm service starting problem should resolve the Vertias High Availablity Engine service starting problem.

For the VCSComm service, if you check the event logs you should see an error message from VCSComm service failing to start.  If you open it I'm guessing that you will find it to say "Incorrect Function" for the reason the service is not starting.  This is typically a problem with the LLTtab file.  If you run VCW you can reconfigure the cluster heartbeats and that should recreate the LLTtab file and fix any issues with it.

Please let us know if that does not resolve your issue. 

If you would like you can open a case with Symantec Technical Support and we will help you though this process.

Thanks,

Wally

Yes. I'm upgrade both node at

Yes. I'm upgrade both node at same time.

Yes. And hardware is the same on both node.

Hi Wally, In event log when I

Hi Wally,

In event log when I start Veritas VCSComm service find next massage "The Veritas VCSComm Startup  service depends on the GAB service which failed to start because of the following error: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it."

VCW at the step "Edit Options" error "Node has not received cluster membership yet, cannot process HA command" See attach.

Accepted Solution!

Hi Shark1000,   We need to

Hi Shark1000,

 

We need to determine if GAB and LLT are simply disabled or if they had problems during the upgrade and did not get installed.

 

To check to see if GAB is disabled check the following registry location:

   hklm\SYSTEM\CurrentControlSet\Services\Gab

There should be a "Start" key in that location.  If the value is 4 then it is disabled.  Change the value to 2.

 

To check if LLT is disabled check the following registry location:

  hklm\SYSTEM\CurrentControlSet\Services\llt

There should be a "Start" key in that location.  If the value is 4 then it is disabled.  Change the value to 2.

 

If, however, neither of these registry locations exist then there was a problem reinstalling GAB and LLT during the upgrade.  If this is the case, I would recommend opening a case with Symantec Technical Support so we can determine why GAB and LLT failed to install and correct that issue.

 

Thanks,

Wally

View solution in original post

  Thanks, Wallys for the

 

Thanks, Wallys for the help.

 

In the registry hklm\SYSTEM\CurrentControlSet\Services\Gab  "Start" key the value had 4. After change on to 2 everything worked.
 
Why it happend? 

Hi Ivan, I'm not sure exactly

Hi Ivan,

I'm not sure exactly what happened.  However, during an upgrade GAB and LLT are uninstalled but the configureation is left in place and then the new versions of GAB and LLT are installed.  The default startup type for GAB and LLT after being installed is "Disabled" or 4.  The upgrade runs a post process which should set GAB and LLT startup type back to 2.  that post upgrade process must have had an issue performing the change to the startup type for GAB.

 

-Wally