"Error V-16-10-4 Could not connect to a live system in cluster" reported when attempting to login to VCS Java Console
Article ID: 100003910
Updated On:
Description
Error Message
VCS ERROR V-16-10-106
Could not connect to a live system in the cluster localhost: 14141
Please check application event log for more details.
Closing all windows.
Cause
The issue can occur if:
1) Port 14161 is blocked or not open at the server or firewall level
2) The Veritas High Availability Engine (HAD) service in the Windows services console is not started/stuck in the starting phase, thereby preventing the cluster node from achieving the port h membership.
Resolution
1) Do a port test (Eg: Telnet) for port 14161 and confirm it is open.
Verify using netstat -abno | finstr 14161 to verify if the port is open
2) For issues with HAD service not starting, the below steps can be performed to achieve manual seeding of the node.
o If HAD service is stuck in the "Starting" phase, then do an "End process tree" for had.exe from Task Manager.
o From an elevated command prompt of the impacted cluster node, run the below commands
a) net stop llt /y
b) net start llt
c) net start vcscomm
d) gabconfig -x
e) hastart
3) At this point, check the status of the HAD service from services.msc and confirm it is in a STARTED state.
4) Verify the port h is retained by running the command: gabconfig -a and ensure it shows the below output
C:\Users\administrator.test>gabconfig -a
GAB Port Memberships
===============================================================
Port a gen 15590d membership 01
Port c gen 155912 membership 01
Port h gen 15590e membership 01 --->HAD started
NOTE: If the HAD service still fails to start, then run the "Veritas Cluster Configuration Wizard" and reconfigure the LLT links using the steps below:
Launch VCW -> Select Domain-> Add all nodes -> Edit Existing Cluster -> Reconfigure->Change Private Heartbeat links-> Unselect all LLT links for all nodes and select them again -> Reconfigure
Issue/Introduction
