crescendas
2 Iron

vCenter could not connect to the VSM server

Jump to solution

I have SanHQ and HIT running well on vSphere 4.1. After upgrading to vSphere 5.5 and HIT to VSM 4, my new vCenter could not connect to the VSM server at all.

1. Should VSM ip address be configured on the management or iSCSI network?

2. I have 2 vCenters at HQ and DC respectively. In this case, do I need to install 2 VSM, each at each site? Note that while my management and VM networks at both sites are all connected thru VPN, the iSCSI networks are isolated.

3. Is it possible to deploy both VSM 3.5 and 4 so that both vmware Web Client and VI Client have access to VSM features?

0 Kudos
1 Solution

Accepted Solutions
DELL-Donald Wi
1 Copper

RE: vCenter could not connect to the VSM server

Jump to solution

VSM does not work with Linked mode vCenters so that one VSM would be able to access two vCenters.

You will need to deploy two VSMs.

You can't run both VSM 3.5.x and 4.0.x at the same time.  

Social Media and Community Professional
#IWork4Dell
Get Support on Twitter - @dellcarespro

View solution in original post

0 Kudos
8 Replies
crescendas
2 Iron

RE: vCenter could not connect to the VSM server

Jump to solution

I have EQL at 2 locations with vCenter link mode enabled. While their management IP network are linked, their iSCSI network are isolated according to the best practice. In this case, I will need to deploy VSM at both location right? Or can a single VSM manage both? And is it possible to deploy both 3.5.3 and 4 so that I have VSM in both Web and VI Clients?

I need to know if the VSM ip address be deployed on the management or iSCSI network? And the VSM login is using EQL or vCenter credential? These are not mentioned in the user guide, so please have these critical missing info added in the next revision.

0 Kudos
DELL-Donald Wi
1 Copper

RE: vCenter could not connect to the VSM server

Jump to solution

VSM does not work with Linked mode vCenters so that one VSM would be able to access two vCenters.

You will need to deploy two VSMs.

You can't run both VSM 3.5.x and 4.0.x at the same time.  

Social Media and Community Professional
#IWork4Dell
Get Support on Twitter - @dellcarespro

View solution in original post

0 Kudos
crescendas
2 Iron

RE: vCenter could not connect to the VSM server

Jump to solution

Since I need to deploy 2 VSMs, can't I deploy 3.5.x at one site and 4.0.x at the other site since both are independent?

Moreover, the deployment of VSM 3.5.x works on vSphere 5.5 just fine. However, it no longer works after upgraded to 4.0.x. In the web client, what is the Group IP of EQL? Is it iSCSI or Management network? If this is iSCSI network, does this mean that VSM 4.0.x IP address need to be also on the iSCSI in order to communicate with EQL? (Since iSCSI and Management networks are isolated)

0 Kudos
crescendas
2 Iron

RE: vCenter could not connect to the VSM server

Jump to solution

btw, I have raise this issue to EQL support team but until now, there is no response from them. 😞

0 Kudos
crescendas
2 Iron

RE: vCenter could not connect to the VSM server

Jump to solution

<ADMIN NOTE: Image containing Service tag removed as per privacy policy>

Is there anyone in Dell managing the support case raise from the customer portal? This forum is more responsive.

0 Kudos
crescendas
2 Iron

RE: vCenter could not connect to the VSM server

Jump to solution

If I have deleted the VSM VM without unregister it from the vCenter, how do I manually remove it from the vCenter?

0 Kudos
DELL-Donald Wi
1 Copper

RE: vCenter could not connect to the VSM server

Jump to solution

To delete it, right mouse over the VM when powered off and delete it.

re: 3.5.x and 4.0. in different vCenters.  Absolutely.  In my lab my 4.1, 5.0 environments runs 3.5.3 and the 5.1/5.5 run VSM 4.0.  

Social Media and Community Professional
#IWork4Dell
Get Support on Twitter - @dellcarespro

0 Kudos
crescendas
2 Iron

RE: vCenter could not connect to the VSM server

Jump to solution

I tried that previously and found that the VSM icon is still in vCenter:

This mean it has to be properly unregistered first, isn't it?

But since I have already removed the VM, is there anyway to unregister it manually?

Cause I'm not sure if my new deployment could not connect issue is related to improperly removal or there is something wrong with the configuration. I have no issue getting 3.5.x to work, but not 4.0.x. Dell support is completely silent about this.

0 Kudos