Same problem here. Is there somebody who fixed this problem?
This issue may occur due to changes in the vCenter Server configuration. Networking issues may break the communication between the service and the vSphere Storage Appliance cluster.
To resolve this issue, start the vSphere Storage Appliance Cluster service if it is not running, and repair the connection with the service if necessary.
Verifying if the vSphere Storage Appliance Cluster service is running
To verify if the service is running, check the
Alternatively, run this command to check if the service is running:
sc query vsaclusterservice
To start the service, run this command:
net start vsaclusterservice
Confirming that the VSA Cluster Service (VCS) IP is started on vCenter Server
To confirm that VSA Cluster Service is started, run this command:
# ipconfig /all
If the VSA Cluster Service is not started, you must add it.
Note: You can add it to the same NIC that vCenter Server is using or to a different NIC.
For more information on adding another IP address, see How do I add an additional IP address in Windows 2000/2003 Server?
Note: The preceding link was correct as of February 1, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.
To obtain the service details, search the VSA Manager logs for entries similar to:
2011-09-22 13:22:31,814 334 [CreateClusterThread] [Thread-122] INFO - Dump VSA Cluster Configuration
VSA Management Network Settings
IP Address Netmask Gateway/Interface
Cluster : 10.42.16.42 255.255.240.0 10.42.16.1
VSAManager Service: 10.42.16.43 255.255.240.0 Local Area Connection 2
VSA VM Network Settings : host-17
IP Address Netmask Gateway Vlan ID
Management: 10.42.16.44 255.255.240.0 10.42.16.1 0
NFS : 10.42.16.45 255.255.240.0 10.42.16.1 0
Backend : 192.168.0.1 255.255.255.0 - 0
Feature : 10.42.16.46 255.255.240.0 10.42.16.1 0
If the VSA Cluster Service IP is started, try to ping the other elements in the cluster:
- Ping the VSA Cluster IP from vCenter Server.
- Ping the VSA Cluster service from any of the VSA nodes.
If they are up, but not reachable, investigate if there is a network problem.
If these steps do not resolve the issue, try repairing the connection with the service using the GUI (VSA Manager tab).
Alternatively, run this command:
C:\Program Files\VMware\Infrastructure\VSA Manager\tools> "C:\Program Files\VMware\Infrastructure\jre\bin\java.exe" -jar WSCLI.jar VSA-Cluster-IP repairPseudoSva
VSA-Cluster-IPis the VSA Cluster IP (visible from VSA Manager).
I already tried that. The command repairPseudoSva doesn't work in VMware VSA 5.5.
The new name of the command is repairVCS.
The outcome of this command is:
org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
Failed to perform operation: Transport error: 404 Error: Not Found
When trying to repair the VSA Cluster service through the GUI the manager gives the following error:
I can't find any connection errors. Ping works fine...
Please help :-)
I tried all of the above in King_Robert reply too, thanks Robert. Vmware tell me the only way to resolve this is to delete the cluster and recreate it. As I only have 2 live Vms on the cluster I will back them up and try this sometime this week or next week. Will post back to see if it works.
since yesterday we have the same problem.
updated VSA-Manager and VCenter Server to 5.5
VSA-Cluster is still 5.1
Support told me to upgrade the cluster to 5.5, maybe the problem will be fixed with this act.
isn't there anybody with the same problem who has fixed it? We have a couple of VMs running on the cluster, i dont want to recreate it.