Problem registering Nexus1000V plugin

krachako · ‎05-28-2009

I always bump into this error whenever I try to install plug-in for Nexus 1000 in VC. Can you help me resolve this problem or point me to a person who can help me on this.

Krishna

dcasteli · ‎05-29-2009

You dont have to click on "Download and Install".Just hit close button and you should be fine.

Let us know, if that does not work.

Thanks

Deepak

krachako · ‎05-29-2009

Hi Deepak,

I am getting stuck as VC registration is failing with below error..

xus1000v(config)# svs connection VC
nexus1000v(config-svs-conn)# vmware ?
dvs Create vmware dvswitch

nexus1000v(config-svs-conn)# vmware dvs datacenter-name ESX4.0-VCCTEST
nexus1000v(config-svs-conn)# protocol vmware-vim
nexus1000v(config-svs-conn)# remote ip address 10.35.20.20
nexus1000v(config-svs-conn)# exit
nexus1000v(config)# exit
nexus1000v# config t
nexus1000v(config)# svs connection VC
nexus1000v(config-svs-conn)# connect
ERROR: [VMWARE-VIM] Operation could not be completed due to connection failure.HTTP/1.1 404 Not Found. <HTML><BODY><H1>404 Not Found</H1></BODY></HTML>
nexus1000v(config-svs-conn)#

Let me know if you want to access my test bed

lwatta · ‎06-01-2009

Can you verify what code versions you are running on the VMware vCenter Server and the vSphere client?

I saw similar error last week and the issue was related to the code being at different levels between the Nexus 1000V and VMware vCenter Server

You should be running the below code on the N1KV

Software
loader:    version 1.2(2) [last: image booted through mgmt0]
kickstart: version 4.0(4)SV1(1)
system:    version 4.0(4)SV1(1)
kickstart image file is:
kickstart compile time: 4/2/2009 23:00:00
system image file is:    bootflash:/nexus-1000v-mz.4.0.4.SV1.1.bin
system compile time:     4/2/2009 23:00:00 [04/26/2009 13:27:23]

From VMware you should be running

VMware vCenter Server build 162856 and make sure the vSphere client is version 162856 as well.

Make sure you load your eval license, download and load the Nexus 1000 XML extension into VMware vCenter Server, and then attempt to issue "connect" under "svs connection"