i´m trying to get vxlan working within a vcloud director 5.1 environment.
Within vshield manager i configured the sgement id and in the next step i try
to create the vxlan under connectivity. ProviderDC is not yet created.
I can select the cluster and my desired switch and start the installation. This takes
about 5 minutes and ends in state "not ready" and error.
During setup the portgroup is created but no vmknic within this.
On my esx hosts i see events "vib-module for agent not installed on host 172.... (vshield-vxlan-service)"
and "Agent activating" which end with error.
Tried basics like creating new dvSwitch, reboot Hosts, reinstall everything...
I upgraded my networking & security appliance to latest version as stated here:
I also tried to install the agentpackage vxlan.zip manual via esxcli on all of the 3 hosts but still no success...
Anyone an idea where i can get deeper error message to find the solution, or perhaps a hint to the solution?
Have you checked the status of EAM (ESX Agent Manager)? EAM is an app running with vCenter that's used for install and management of host modules (ie, VXLAN VIBs). It needs to be able to talk to the hosts on port 80. You can check it's status in the vSphere Client from:
Home -> vCenter Solutions Manager -> EAM (on the right) -> Summary tab (Health should be green). Also check the Management tab and look for VSM.
thanks for your answer!
Checked this today, ESX Agent Manager is green, but below i can see an error from "vshield manager" - its state is red.
There is a button "resolve" which restarts installation and ends up again with error. He says he installs the agent and the next
event is from "activating agent" - this ends up with error.
Any more ideas?
Restarted everythin quite often but there is no change in situation.
The errors in the Log are:
- problem vibnotinstalled solved (key 93)
- agent-vib-module not installed
- changed state from vshield-vxlan-service on host from yellow to red
This is the output from tasks & events per host. Is there a better log to search?
I´m not an unix specialist - sorry...
Tried http-connect from esx-hosts to vshield manager via netcat for tcp 80 - works fine.
All the hosts are on one subnet on one switch and everything else is working quite well. Seems
to be a little setting for vshield that is incorrect.
I do also have the same problem with a new installation.
Configured vCenter 5.1, ESXi 5.1, configured dvSwitch, deployed VSM 5.1.2-943471, started Network Virtualization Preparation.
But now I can't continue, because the cluster and the esxi hosts stay in the status "not ready"
The VMKNICs aren't deployed automatically and i think it's very interesting, that the automatically created Portgroup has 0 available ports, but a change of the ports and a resolve in the VSM GUI also doesn't create the vmknic.
2013-03-28T16:56:54Z esxupdate: downloader: DEBUG: Downloading http://servername.domain.lcl:80/eam/vib?id=7c5f5da7-cdd7-4654-af20-ae147c15123a-0 to /tmp/tmpvr0bRV...
2013-03-28T16:56:54Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file
I've already read many blogs and community entries, but with none of the workarounds it was possible to solve my problem.
Opened several ports between esxi and vc, restart web-management readd vcenter, restarted esxi servers, tried to install vib manually ...
Already checked the nw communication with nc, but everything seems to be fine.
Maybe someone of you guys might help me.
Chris, I have exactly same problem with my setup. 100%.
Home -> Adm -> VSM -> vShield Manager reports "agent vib module is not installed" etc.. and I have also tried everything, uploading that .zip from vshield via update manager or by hand, no luck. Googled dozens of blogs about these issues but no luck so far.
So I keep my fingers crossed for your SR Please report when u hear anything.
Hi all, any news on this topic?
I have donwloaded VMware-vShield-Manager-5.1.2-943471 OVA file, and I am experiencing this same issue:
During vxlan cluster preparation step, the vmknic is not created and vShield task fail informing "Not ready" for the DHCP IP address.
On vCenter 5.1, I tried to manually add a vmknic in the vxlan port group, but the following error is returned:
Call "HostNetworkSystem.AddVirtualNic" for object "networkSystem-5540" on vCenter Server "IO-VCENTER51" failed.
Operation failed, diagnostics report: Sysinfo error on operation returned status : Would block. Please see the VMkernel log for detailed error information
As informed in other posts, the error "HostNetworkSystem.AddVirtualNic" seems to be expected due to a protection in the vxlan PG. Any workaround for this issue?
On vCenter 5.0, I can add the vmknick without errors, but with 5.0 version my setup fails due a "Agent VIB module is not installed" error message.
Right now I am using 5.1 versions, as following:
- vCenter Server: 5.1.0 - build 1038139
- ESX hosts: ESXi, 5.1.0, 1029768
Also, I manually installed the agent on hosts, released http ports on vCenter firewall, added/removed hosts from maintenance, added VUM to my vCenter and all the other suggestions, but no luck in the setup.
Looking the agent I manually installed, it has the version 5.1.0-0.0.799733. Is this expected?
Is there some log file to guide me to a solution?
Just an update on this thread:
After a hard work digging the internet, I found a blog informing that the patch kit 5.1.2a should fix the "vmknic not created" issue.
However, I am not able to get it. VMWare page returns "We are activating your licensing key entitlement, re-try your download soon".
Once I purchased a trial version of vShield 5.1.2, is there an easy way to get the 5.1.2a patch kit file?
I got the same issue. I have followed http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=204445... to update my vShied Manager to 5.1.2a(it need to reboot vShied Manager twice) ,still the same error.
What shoud I do? give up.:smileyconfused:
I had the same issue. Was able to finally figure out what's happening. Probably it's specific to my environment only.
In a nutshell what happened was my vCenter Server was not correctly operating on port 80. (Easiest way to verify this is to open up the browswer and you should get directed to the vCenter Server web page. If you are not then that indicates an issue) The culprit here was SQL Inventory Service. It was operating on port 80 and blocking the vCenter Server.
After resolving this issue everything was fine again.
Good inforamtion, thanks. However, it seems not the case for me.
I can open the vcenter:80 without problem. I double checked it with netstat command.
I do have both SQL/Oracle XE installed on the vCenter. I also installed vShpere Web client which uses port 9443.
Sorry to hear that. Just in case if it helps following are the list of things I tried but didn't work except for the last method I described.
1) Disable/Enable Web admin on vSheild
2) Enable "http" firewall access on each and every esx host
3) Make sure dns/domain are correctly configured
4) Manually install the vxlan VIB on each esxi host.
None of these things work for me. Except the following
5) Make sure the vCenter Server is operating on port 80.
I am soooooooooooo luck today. I just tried another time to click the "fix" button in vCenter and it did work!!!
It's in the right side or the Management tab.
I have tried many times, it never work. ahaha.
The only change I made today is change the vShield VM memory setting from 4G to 2G because it complain the host is almost out of memory.
good luck to everyone.