"[VMWARE-VIM] Operation could not be completed due to connection failure" error when i try to establish svs connection between n1000 and vc.

[aasmund.greibrokk]

Hi,

I got an error when i try to establish svs connection between n1000 and vc.

n1000v-hostname(config-svs-conn)# show svs connections

connection VC:
    ip address: 172.17.80.19
    protocol: vmware-vim https
    datacenter name: default
    DVS uuid: -
    config status: Disabled
    operational status: Disconnected

n1000v-hostname(config-svs-conn)#

[VMWARE-VIM] Operation could not be completed due to connection failure. EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()

I can ping 172.17.80.19.

i have the latest nexus software (nexus-1000v-mz.4.0.4.SV1.1.bin)

do sombody have any idea whats wrong in my setup?

[Robert Burns]

Can you also check the vCenter Server Ports being used.

From your vSphere client go to Administration -> vCenter Server Settings  -> Ports

Ensure you're vCenter is set to use port 80 for http and port 443 for https.  If this value was originally changed to something other than 80 (possibly due to a conflicting application running on the same server) the VSM will not be able to connect.  This is a limitation of the current VSM release and will be fixed next version.

Let me know if this is your issue.

If this is not your problem, send me a screen shot (or output) of "netstat -a" from a command prompt on your vCenter server.

Robert

[aasmund.greibrokk]

Can you also check the vCenter Server Ports being used.

From your vSphere client go to Administration -> vCenter Server Settings  -> Ports

Ensure you're vCenter is set to use port 80 for http and port 443 for https.  If this value was originally changed to something other than 80 (possibly due to a conflicting application running on the same server) the VSM will not be able to connect.  This is a limitation of the current VSM release and will be fixed next version.

THANK YOU !!!

The HTTP port was set to port 8080, i changed it to 80, rebooted the server, stoped IIS services, and i was able to connect !!!

Thank you everyone for all your help !!

[Robert Burns]

Bingo.  I knew it was port related.

Glad you're back online.

Robert

[antonokan]

I have this problem, on GUI svs connection not worked. I solved this problem when delete svs connections with GUI and create svs connection with Java utility.

[aasmund.greibrokk]

Hi,

you don't need three physical interfaces for the ESX box hosting the VSM. You could trunk the required VLANs across a single NIC.

But you do need three different VLANs. One for mgmt (connection between VSM and vCenter), one for system (connection between VSM and VEMs/ESX hosts) and one packet (also connection between VSM and VEMs/ESX hosts).

You cannot aggregate this traffic on a single VLAN.

At the same time, the issue you are describing shouldn't be related to this misconfiguration. Nonetheless, please try to resolve the issue before continuing with the troubleshooting.

In the proxy.xml file I see that the hostname of the vCenter should be srvkrsapp09.nov.com. Is this the correct hostname and does it resolve to the correct IP address (172.17.80.19) from this host?

I do not have a DNS server in the network 172.17.80.x network at the time being, but as a workaround i added "ip host srvkrsapp09.nov.com 172.17.80.19" and i was able to ping srvkrsapp09.nov.com afterwords. But still the same error message when i try to connect.

Here's why I'm asking this:

VMware uses a concept for accesing services which might appear a bit strange. They use a reverse proxy listening on port 80, that distributed the requests to other ports - where then services/daemons are listening - depending on the URL. Therefore you won't see the https traffic between the VSM and the vCenter going to port 443 on the vCenter. Instead it will be tunneled to port 80 on the vCenter, where the reverse proxy forwards the traffic to another port. And it looks like there is something wrong with that port.

Hope that helps.

Chris

[antonokan]

I have this problem, on GUI svs connection not worked. I solved this problem when delete svs connections with GUI and create svs connection with Java utility.