An Error Occured During 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
An Error Occurred During Port Configuration
This content has been marked as final. Show 23 replies 15. Re: An error an error occurred during port configuration. this operation is not supported occurred during configuration of the HA Agent on the host Rajesh_interoute Dec 21, 2007 8:08 AM (in response to gwatson) Error
An Error Occurred During Port Configuration Operation Could Not Be Completed
: An error occurred during configuration of the HA Agent on the hostSolution : Try these 4 steps one by one1) Check the DNS is working correctly and using your DNS Server you can an error occurred during port configuration this operation is not supported windows 7 resolve each ESX host by name.2) If No DNS Server in place 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 an error occurred during port configuration the requested resource is in use will solve your problem.Raj Like Show 0 Likes (0) Actions 16. Re: An error occurred during configuration 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
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
An Error Occurred During Port Configuration Access Is Denied Vista
during configuration of the HA Agent on the host Welcome to The SLOG! an error occurred during port configuration windows xp ! If you are new here, you might want to subscribe to the RSS feed for regular Virtualization related posts.A funny
An Error Occurred During Port Configuration 0x00000aa
thing happened whilst configuring a new ESX3.5 cluster, 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 https://communities.vmware.com/thread/63697?start=15&tstart=0 default settings my Hosts begin to Configure HA. All seemed to 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 http://www.simonlong.co.uk/blog/2009/02/05/an-error-occurred-during-configuration-of-the-ha-agent-on-the-host/ a few of the other initial checks I made: I had gone through and checked all of 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 Firewal
Last chance saloon » Feb 05 An error occurred during configuration of the HA Agent on the host Categories: Tips by Simon A funny thing happened whilst configuring a new ESX3.5 cluster, part of my process was to enable HA on my hosts. After checking http://planetvm.net/blog/?p=282 the “Enable VMware HA” box and making a few changes to the default settings my Hosts http://itknowledgeexchange.techtarget.com/virtualization-pro/vmware-ha-failure-got-you-down/ begin to Configure HA. All seemed to 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 an error of the other initial checks I made: I had gone through and checked all of 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 an error occurred 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 Default Gateway, it thinks it doesn't exist so it is a misconfiguration error. So lets Test this theory. I re-set the Gateway for HA to our secondary Default Gateway which DID allow ping requests and low and behold after changing the Service Console Gateway settings and re-enabling HA on the cluster it all sprang in to life, both Hosts were now HA enabled!!!! Here is what the log shows now that the HA agent can see the Default Gateway. Simon is a Senior Systems Specialist of a major finance house you can follow him
? Ask a question, help others, and get answers from the community Discussions Start a thread and discuss today's topics with top experts Blogs Read the latest tech blogs written by experienced community members >>VIEW ALL POSTS Virtualization Pro « Log file locations in VMware Infrastructure 3 Where are all the vExperts? » Mar 24 2009 6:14PM GMT VMware HA failure got you down? Edward Haletky Profile: Texiwill Consider yourself lucky if you've never gotten the VMware HA message: An error occurred during configuration of the HA Agent on the host. But if you have, you may know that the ways to fix the error are extremely limited. Here is a method that worked for me. Current methods The current methods of troubleshooting this issue involve checking that the DNS is working properly, that the FT_HOSTS file in /etc/opt/vmware/aam is properly written for the hosts involved in your VMware Cluster, and disabling and re-enabling VMware HA within the VMware Cluster. New method The new method assumes that the VMware HA configuration is somehow at fault. I began to think this was the case when I noticed that the /opt/vmware/aam/ha/VMap process was not terminating on a reset of VMware HA. This process, as seen from the output of ps ax issued from the service console command line interface, should not exist when VMware HA is disabled. However, in my configuration it did exist. I also noticed I had problems reestablishing VMware HA after a recent reboot of a server caused by a faulty UPS. DNS was working, FT_HOSTS looked correct, and disabling and re-enabling VMware HA did no good. Here are the steps that I followed to fix it: Log in to the service console of your problem hosts and verify that VMware HA is disabled using: service vmware-aam stop Ensure there are no VMware HA processes running by using: ps ax | grep aam | grep -v grep If processes exist, kill them using the Process ID returned by the previous command (first column) as the PID: kill -9 PID Issue th