An Error Occured During The Configuration Of The Ha Agent
Contents |
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vCenter™ > VMware vCenter™ Server > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 1 2 Previous Next 23 Replies Latest reply: Dec 10, 2008 6:50 AM by Randy_B Go to original post This content has been marked as an error occurred during port configuration final. Show 23 replies 15. Re: An error occurred during configuration of the HA Agent an error occurred during port configuration. this operation is not supported on the host Rajesh_interoute Dec 21, 2007 8:08 AM (in response to gwatson) Error : An error occurred during configuration of the HA an error occurred during port configuration operation could not be completed Agent on the hostSolution : Try these 4 steps one by one1) Check the DNS is working correctly and using your DNS Server you can resolve each ESX host by name.2) If No DNS Server in place an error occurred during port configuration this operation is not supported windows 7 edit the /etc/hosts file and add entry for each ESX host.NOTE : Make sure you add FQDN and also the shortname.You can obtain the shortname by typing hostname -s.3) Disconnect the ESX host from virtual center and connect them back.4) Disbale VMware HA feature from Cluster and enable them back. You will find that one of this steps will solve your problem.Raj Like Show 0 Likes (0) Actions 16. Re: An error occurred during configuration
An Error Occurred During Port Configuration The Requested Resource Is In Use
of the HA Agent on the host R0v3r Feb 22, 2008 4:47 AM (in response to Rajesh_interoute) I have a question about the DNS portion. Does this still apply to 3i 3.5? Is there still a hosts file on this version that we can look at? Like Show 0 Likes (0) Actions 17. Re: An error occurred during configuration of the HA Agent on the host Rajesh_interoute Feb 22, 2008 4:54 AM (in response to R0v3r) Host file :/etc/hostsAlso look at : /etc/resolv.conf for DNS.. Like Show 0 Likes (0) Actions 18. Re: An error occurred during configuration of the HA Agent on the host R0v3r Feb 22, 2008 4:58 AM (in response to Rajesh_interoute) Thanks for the reply. I thought Linux was not on the new version that is why we use the Remote CLI. How does one get to the ESX Host local hosts file then? Like Show 0 Likes (0) Actions 19. Re: An error occurred during configuration of the HA Agent on the host R0v3r Feb 22, 2008 6:39 AM (in response to R0v3r) I think I found a way to see the hosts file and the rest of the files as well on a 3i 3.5 host. In the VI client, open the Administration menu and choose Export Diagostic Data. Select the hosts whose logs you want and the destination direct
ExtremeInformation PersonaManagement PCoIPTroubleshooting ContactSimon Latest vBeers: vBeers – St. Louis, MO ( Wednesday, October 19th, 2016 ) View all vBeer events Posted by Simon Long Feb 5, 2009 An error occurred during configuration of the HA
An Error Occurred During Port Configuration Access Is Denied Vista
Agent on the host Welcome to The SLOG! ! If you are new here, you an error occurred during port configuration windows xp might want to subscribe to the RSS feed for regular Virtualization related posts.A funny thing happened whilst configuring a new ESX3.5 cluster, an error occurred during port configuration 0x00000aa part of my process was to enable HA on my hosts. After checking the “Enable VMware HA” box and making a few changes to the default settings my Hosts begin to Configure HA. All seemed to https://communities.vmware.com/thread/63697?start=15&tstart=0 be going well until I was presented with this; Now I have had this error before on systems and I remembered that this could be to do with DNS issues, but first things first I tried to disable and re-enable HA a few times in case there was a “glitch” but this made no difference. Here are a few of the other initial checks I made: I had gone through and checked all of http://www.simonlong.co.uk/blog/2009/02/05/an-error-occurred-during-configuration-of-the-ha-agent-on-the-host/ my DNS settings to make sure everything is set in lowercase I had checked all connectivity, between VC, Host1, Host2 by pinging FQDN's, using vmkping, everything could connect to each other. I rebooted VC, I reboot both hosts I disconnected and reconnect both hosts. I removed and recreated a new Cluster and added the hosts back in. Nothing fixed my issue. After revisiting my settings several times, I noticed on the Summary tab of the Cluster in the VMware HA box it said this: Current Failover Capacity: 0 Hosts Configured Failover Capacity: 1 Host Clearly this wasn’t correct, so I decided to look closer at the HA agent’s installed on the host themselves. I decided to have a look at the HA agent log (aam_config_util_addnode.log) this is found at the following location on the ESX host; cat /var/log/vmware/aam/aam_config_util_addnode.log Whilst looking through the log I noticed that I wasn't getting a ping response from my Default Gateway; I knew my Gateway was working fine as my workstation was configured to use it and that was functioning fine. Now this Gateway is an interface on a Firewall and that interface had been configured to discard ping requests. Eureka moment, Was this the reason why the HA agent would not configure? Because it couldn't receive a ping response from the Defau
and the free VMWare Server are some sweet wares, but nothing compares to 8 cores of bare-metal virtualization with 32 Gigs of http://www.rthilton.com/Blog/BlogArticle.aspx?ArticleID=12 RAM (per node).The first hurdle was licensing. I was unaware of how the licensing worked for ESX server and was not expecting the license activation process and the need to setup a Virtual Center server to handle the license serving. Not a big deal, I had a server I was about ready to retire anyways so I just reloaded it with Server 2003 R2 Standard an error and loaded up my Virtual Center with the licensing server. Problem solved, ESX servers licensed.The next hurdle was VMotion. I could not for the life of me figure out what needed to happen to setup VMotion. I kept getting errors saying "The VMotion interface is not configured (or is misconfigured) on the source host "ESX01". A little bit of googling and I discovered that I needed an error occurred to setup a VMKernel interface and enable it for VMotion. After playing around with that and setting up an internal 192.168.xxx.xxx network for VMotion I was rocking and rolling. Migrated a server in 2.25 minutes with 1 dropped ping, pretty frickin' sweet if you ask me.The final hurdle (for now) was setting up HA and DRS. Primarily the problem was with HA. I configured the cluster, added my hosts, but they all said "An error occurred during configuration of the HA Agent on the host" when trying to reconfigure HA. After even more googling I learned that DNS was the most common culprit. I verified DNS on all of the hosts, could ping them all by name and IP,short nameand FQDN. What could possibly be the problem? Well, the problem was simple, and stupid, and in my opinion a bug and not afeature.ESX is appearantly case sensitive on hostnames. So, my server labled in the hosts file as CORPESX01.DOM.LOC needed to be labeled as corpesx01.DOM.LOC in order to resolve properly. A simple nslookup from my Windows machine of one of the IP addresses confirmed this capitalization scheme. I went through each host file maki