Slingsh0t
Enthusiast
Enthusiast

VXLAN cluster preparation issue

Guys I have successfully deployed vCloud Director 5.1 along with the vShield Manager and have deployed a few vApps and VCDNI networks etc...  All seems to be OK there.

The issue I'm having is I want to test VXLAN.  When I go to prepare a cluster, I see a new portgroup appear on the DVswitch "vxw-vmknicPg-dvs.....blah" however no vmkernel port is created on the port group.  From what I've read, a vmk port should be created and its on this interface that DHCP waits for an address.  I'm unable to manually create a vmk port on the newly created VXLAN port group as I get the following error message:

  • Call "HostNetworkSystem.AddVirtualNic" for object "networkSystem-1944" on vCenter Server "PVPVC01P201.poc.pvp.lon5.telecity.net" failed.
    Operation failed, diagnostics report: Sysinfo error on operation returned status : Would block. Please see the VMkernel log for detailed error information

In the end I need to unprepare the cluster to remove the portgroup.  I have rebooted the hosts, vSM and vCenter.  This has made no difference.

27 Replies
sunvmman
Enthusiast
Enthusiast

you should see an error message in vcenter stating the vib package can not be installed. if that is the case, let me know and i'll help you 

0 Kudos
John_David_Robi
Contributor
Contributor

It took me the better part of a week to come across the solution to this at random. I changed the license for VCNS (from an old VCNS eval to a purchased vCloud Suite Standard) and rebooted the vShield Manager. I'm not sure if the old license was expired or what, but I tried all of the solutions I could find online, and ultimately this was the only thing that worked.

0 Kudos
garcia94
Contributor
Contributor

I still get this error message after upgrading to 5.1.2a:

Invalid format for VIB module at  (vShield-VXLAN-service) error 10.201.4.132 com.vmware.vim.eam

Here is the output from /var/log/esxupdate.log

2013-05-16T16:53:00Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetTimeout']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2013-05-16T16:53:00Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRetries']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2013-05-16T16:53:00Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRateLimit']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2013-05-16T16:53:01Z esxupdate: esxupdate: INFO: ---

Command: scan

Args: ['scan']

Options: {'nosigcheck': None, 'retry': 5, 'loglevel': None, 'cleancache': None, 'viburls': None, 'meta': ['http://WIN-8LO7SJ6PTTQ:80/eam/vib?id=47f1be13-04f5-4fdf-9c90-1332f17f98a1-0'], 'proxyurl': None, 'timeout': 30.0, 'cachesize': None, 'hamode': True, 'maintenancemode': None}

2013-05-16T16:53:01Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2013-05-16T16:53:01Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2013-05-16T16:53:01Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2013-05-16T16:53:01Z esxupdate: downloader: DEBUG: Downloading http://WIN-8LO7SJ6PTTQ:80/eam/vib?id=47f1be13-04f5-4fdf-9c90-1332f17f98a1-0 to /tmp/tmpNTB3Fs...

2013-05-16T16:53:03Z esxupdate: downloader: DEBUG: Using redirect URL http://www.website-unavailable.com/?wc=EWJvGgFmAhtfBBRwGAkKHQ==&url=WIN%2D8LO7SJ6PTTQ%3A80%2Feam%2Fv...

2013-05-16T16:53:03Z esxupdate: esxupdate: ERROR: An esxupdate error exception was caught:

2013-05-16T16:53:03Z esxupdate: esxupdate: ERROR: Traceback (most recent call last):

2013-05-16T16:53:03Z esxupdate: esxupdate: ERROR:   File "/usr/sbin/esxupdate", line 216, in main

2013-05-16T16:53:03Z esxupdate: esxupdate: ERROR:     cmd.Run()

2013-05-16T16:53:03Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-799733/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esx5update/Cmdline.py", line 106, in Run

2013-05-16T16:53:03Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-799733/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/Transaction.py", line 74, in DownloadMetadatas

2013-05-16T16:53:03Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-799733/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/Metadata.py", line 67, in ReadMetadataZip

2013-05-16T16:53:03Z esxupdate: esxupdate: ERROR: MetadataFormatError: File is not a zip file

2013-05-16T16:53:03Z esxupdate: esxupdate: DEBUG: <<<

Any ideas?

0 Kudos
sachinthakkar
Enthusiast
Enthusiast

It looks like your FQDN for the VC is not resolvable.

http://WIN-8LO7SJ6PTTQ:80

I'm guessing this based on the following message in the logs:

Using redirect URL

http://www.website-unavailable.com/?wc=EWJvGgFmAhtfBBRwGAkKHQ==&url=WIN%2D8LO7SJ6PTTQ%3A80%2Feam%2Fv...

You can go to the Advanced Settings VC variables to ensure these are correctly set. See the following screenshot (get to this menu from Administration > vCenter Server Settings > Advanced Settings)

Screen Shot 2013-05-16 at 1.41.01 PM.png

If you don't have a valid FQDN, please clear that VirtualCenter.FQDN field and fill in the VirtualCenter.ManagedIP field with an explicit IP address.

If you need help, please feel free to reach out to me over direct message.

Sachin

IamTHEvilONE
Immortal
Immortal

It looks like your FQDN for the VC is not resolvable.

http://WIN-8LO7SJ6PTTQ:80

From what point of view are you referring to DNS resolution?  e.g. on the ESXi hosts, from the vShield/vCNS Manager, etc.

It also looks like a spawned ID for vCenter ... and it might not be the actual DNS value ... this also means that some certificates in vCenter may be using this ID rather than the more appropriate FQDN as defined in DNS.

0 Kudos
sachinthakkar
Enthusiast
Enthusiast

The ESX host trying to resolve the VC IP. VC hosts the VIBs provided to it from the vCNS manager.

0 Kudos
garcia94
Contributor
Contributor

I changed the FQDN and it's working now.  Thanks for your help!

0 Kudos
naveenreddy_j
Contributor
Contributor

Yes. I had the same problem and it was resolved after changing the fqdn.

saved my time.

Regards

Naveen

http://www.tivolisupport.com

0 Kudos