Net: 1380: invalid Net_Create: class cisco_nexus_1000v not supported

[sunday111]

Hello everyone,

I have a problem integrating the distributed virtual switch 1000 V in to my ESXi5 server throw vCenter. I have installed it OK. No when I add a host to the switch if displays an error  vDS operation failed on host esx8, An error occurred during host configuration. got (vim.fault.PlatformConfigFault) exception.

When I look at the vmkernel.log file I get:

....

2012-01-10T12:18:26.103Z cpu0:3471)Net: 1380: invalid Net_Create: class cisco_nexus_1000v not supported

ESXi5 has a hardware:

IBM System x3550 M3

32 GB RAM

I have the full licence applied (Enterprice plus).

Any idea what could be the problem???

I can not believe that it could be a hardware compatibility problem. The server is 5 mounths old.

[Jerry75]

Hi,

Not sure if you have the same problem as me, but a reboot of the host resolved my problem.

Add the host, get an error, reboot, then add the host again.

Could be a different problem of course 😉

/Jerry

[sunday111]

Nop. I have tried that several times. Didn't help.

Thanks anyway.

[bwill322]

I'm experiencing this exact same problem. The ESXi 5 host I'm trying install the VEM VIB files on communicates back to the VSM with Layer 3. There is a firewall in between, but this is not the problem. We proved this by taking the firewall out of the mix and still got the exact same error. Multiple reboots have been attempted, too. The install process starts. VUM says it "cannot scan the entity <ip address>" then fails with the vim.fault.PlatformConfigFault exception.

Versions:

ESXi 5.0.0 Build 469512

VEM VIB (located in the VUM repository): VEM500-201108271-BG

The same pop-up dialog appears when trying to install the VEM files using VUM when logged in to vCenter with the vSphere client. Our next steps at this point are:

- Rebuild the VUM VM

- Rebuild the ESXi host

The 1000v is working fine on another ESXi 5 host sitting in the same subnet. It's just this one host that is causing problems.

[sysxperts]

I had this exact error; turned out that VUM was lying to me about the status of the vem package and it needed to be installed manually.  Might also be caused if version installed does not match version for the VSM - compare the versions and install appropriate one...  I wrote about it here: http://www.sysxperts.com/vmware/vum---why-must-you-lie-to-me

[yonish]

install the vib in the esx like that

vmfs/volumes/521ca999-5aac0ca2-076f-003048f6dee0/Setup # esxcli software vib install -d /vmfs/volumes/521ca999-5aac0ca2-076f-003048f6dee0/Setup/VEM510-201306160101-BG-release.zip

Installation Result

   Message: Operation finished successfully.

   Reboot Required: false

   VIBs Installed: Cisco_bootbank_cisco-vem-v160-esx_4.2.1.2.2.1.0-3.1.1

   VIBs Removed:

   VIBs Skipped:

esxcli software vib list | grep cisco

cisco-vem-v160-esx             4.2.1.2.2.1.0-3.1.1                 Cisco   PartnerSupported  2013-08-27

or

esxcli software vib list

Name                           Version                             Vendor  Acceptance Level  Install Date

-----------------------------  ----------------------------------  ------  ----------------  ------------

cisco-vem-v160-esx             4.2.1.2.2.1.0-3.1.1                 Cisco   PartnerSupported  2013-08-27

ata-pata-amd                   0.3.10-3vmw.510.0.0.799733          VMware  VMwareCertified   2013-01-28

ata-pata-atiixp                0.4.6-4vmw.510.0.0.799733           VMware  VMwareCertified   2013-01-28