Thanks for the suggestion; guess I should've mentioned that I did put the host in maintenance mode first to ensure no VMs were moved back to it while I was updating. All of the VMs on the host had already been migrated off of it. I didn't think an alarm should fire on something that was flagged as in maintenance; maybe it a just a glitch. I've got a couple more to update yet, so I'll give it another try.
Thanks, Jeff On Fri, Jan 9, 2009 at 12:37 PM, Andy Shook <andy.sh...@peak10.com> wrote: > Jeff, > Put the host server in maintenance mode before you take it down. This tells > VC that this server is being worked on so don't move any VMs to it and ignore > connectivity issues. To put the host in maintenance mode, right click the > host in VC and select...you guessed it...Maintenance Mode. > > HTH, > > Shook > > -----Original Message----- > From: Jeff Bunting [mailto:bunting.j...@gmail.com] > Sent: Friday, January 09, 2009 12:09 PM > To: NT System Admin Issues > Subject: VMWare alarm question > > Hoping one of you VMWare gurus can answer this.... > > I'm updating the firmware on some of our ESX servers. In virtual > center, there is an alarm defined at the datacenter level to email an > alert when a host loses connection to VC. Is there a way to disable > this alarm when performing maintenance on an individual server? The > host indicates the alarm is read only except at the top level, and I > obviously don't want to disable all of the alarms. Creating an alarm > for each host just to be able to this isn't a very good solution > either. Is there a better way? > > Thanks, > Jeff > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
