TBKing's Posts

In vCops Custom UI, I'm setting up some applications and I noticed I have multiple resources of the same Name. In the "Edit Application" view, under List, I have objects with the same "Name", ... See more...
In vCops Custom UI, I'm setting up some applications and I noticed I have multiple resources of the same Name. In the "Edit Application" view, under List, I have objects with the same "Name", "Identifier 1" and "Identifier 3" The "Identifier 2" field is what is unique - "vm-1353", "vm-1357" I know, in the two instances I found, that I had to rebuild the VM for one reason or another. vCenter and everything else looks OK. Where is this coming from?  Should I be concerned? Thanks
I'm new to vCops too. Those videos are a good start. I created a 7 Day Health chart displaying each of my clusters, and a Storage Heat Map - colored between 50 and 100% I set up a few "Appli... See more...
I'm new to vCops too. Those videos are a good start. I created a 7 Day Health chart displaying each of my clusters, and a Storage Heat Map - colored between 50 and 100% I set up a few "Application Tiers" as well - those could come in handy... somewhere
This deserves a bump and a pat on the back to FGSheperd (and more points if we could) Glad I found it before I pulled out all of my hair. Thanks
Yes, vMotion "should" still work with HA and DRS turned off ... if everything else were healthy. You can restart the mgmt agents without affecting the guests, couldn't hurt. .. did you also... See more...
Yes, vMotion "should" still work with HA and DRS turned off ... if everything else were healthy. You can restart the mgmt agents without affecting the guests, couldn't hurt. .. did you also try what Andre mentioned - "Reconfigure for HA" ?
How many hosts in your cluster? Is your faulting host able to talk to any of the others? Can you vMotion to a different host? In my situation, one host couldn't talk to 3 or 4 of the 7 hosts... See more...
How many hosts in your cluster? Is your faulting host able to talk to any of the others? Can you vMotion to a different host? In my situation, one host couldn't talk to 3 or 4 of the 7 hosts in the cluster but I was still able to vMotion. Otherwise kind of a Catch 22 - You need to put in Maintenance mode to fix vMotion, but you have to vMotion to put it in Maintenance mode. Would turning off HA or DRS on the cluster help?
I've seen this a few times: 1) Put in Maintenance mode 2) Move out of cluster (removes HA client) 3) Reboot (not sure if needed, but why not) 4) Move back into cluster. That's assuming y... See more...
I've seen this a few times: 1) Put in Maintenance mode 2) Move out of cluster (removes HA client) 3) Reboot (not sure if needed, but why not) 4) Move back into cluster. That's assuming you've chased down any other possibilities of routing, dns, firewalls (shouldn't be any) cables, etc. There are also KBs on how to manually uninstall and re-install the HA agent.... hope you don't have to go there!
v5.0.2 Enterprise With the "cancel multiple alerts" - The Alert records were gone by the next day - and I expect the same for the lower count from this morning,  but the Alert Volume graph on ... See more...
v5.0.2 Enterprise With the "cancel multiple alerts" - The Alert records were gone by the next day - and I expect the same for the lower count from this morning,  but the Alert Volume graph on the Alerts page, as well as on the Dashboard under Health don't reflect it. We're just shy of 3 weeks since the install. So now we're into the "What does This do?" mode. Thanks!
We're into about our third week of vC Ops install. So we've gone through some "Let's try this" with the fault and alerts settings and thresholds. As it was explained to me, those are re calcu... See more...
We're into about our third week of vC Ops install. So we've gone through some "Let's try this" with the fault and alerts settings and thresholds. As it was explained to me, those are re calculated once a day as some process. I saw this evidence as I made some changes one day, and the next day we had almost 300 alerts across the Red-Orange-Yellow flags - 6 pages worth A little more sensitive than we needed. I re adjusted the thresholds and settings. And then tried to cancel the Fault Alerts.  If I selected 1 or multiple, the interface replied "Please Select Fault Alterts to Cancel".  So I went home ... Next day (today) the alert volume/indicator still showed +300 alerts.  But in the Alerts pane, it only had a handful - one page worth - more closely resembling what we're looking for - so I knew the adjustments worked, and were updated. I was able to select the alerts and hit the button to cancel and it prompted with an "are you sure" .. as expected. .. and I said yes. However, the alerts records still show, but I can't select to cancel (again) I've restarted my browser, and the vSphere client, and it is still acting the same - showing too many "active alerts" in the graph and side-bar icons, and can't select to cancel (even though I already canceled) Time for a vC Ops reboot?
I set up a separate cluster for the new hardware.
Jul 3, 2012 Re: Update HP ESXi 5.0 to Update 1 Is it also possible to perform the upgrade using the HP ISO with vSphere Update Manager? I used VUM to bring all servers to Update 1 ... See more...
Jul 3, 2012 Re: Update HP ESXi 5.0 to Update 1 Is it also possible to perform the upgrade using the HP ISO with vSphere Update Manager? I used VUM to bring all servers to Update 1 HP does have downloadable bundles to use with VUM for their drivers and management tools.
Interesting observation: Migrating VMs from VI3 and old hardware to Esxi5 and new hardware. Because of the differences, I had to shut down the VMs in order to vMotion them to the new environm... See more...
Interesting observation: Migrating VMs from VI3 and old hardware to Esxi5 and new hardware. Because of the differences, I had to shut down the VMs in order to vMotion them to the new environment - as expected. All in vCenter 5, shared datastores, same network.  Just a Host vMotion. When I boot up the VMs for the first time in the new environment, I noticed some of the machines apparently detected new hardware and wanted another reboot, while others didn't. This was even before the vmTools and vHardware was upgraded. I *think* the difference is the 64-bit os VMs want the reboot, while 32-bit don't. Does this make sense?
The VMs on the same host on the "lost" vLan could talk to each other, but not to VMs on the other blade in the same chassis. It turned out to be a config on a switch upstream of the blades was... See more...
The VMs on the same host on the "lost" vLan could talk to each other, but not to VMs on the other blade in the same chassis. It turned out to be a config on a switch upstream of the blades was apparently not passing that subnet as vLan 0 Thanks for your replies.
Yes - They lost connectivity to the network - but the VMs do not show a port-down, disconnect or anything apparent like that.
13 HP blade servers in a VM- ESXi5 cluster.  2 of the blades are in Blade Center #2. All servers have: 2 paired/redundant nics for vMotion and vMgmt, on 2 vLans 2 paired/redundant nics for Dat... See more...
13 HP blade servers in a VM- ESXi5 cluster.  2 of the blades are in Blade Center #2. All servers have: 2 paired/redundant nics for vMotion and vMgmt, on 2 vLans 2 paired/redundant nics for Data network supporting 3 vLANs Without any apparent reason, One of the Data vLANs stopped working for the two blades in BC#2. It is the "Default" vLAN ( "0" ) for that segment. The other vLANs continue to work fine. vLan 0 works fine in the other blade center. vMotion, management, console, etc all work. We've rebooted the ESX boxes and the HP blade switches and no change. Nosed around logs, configs, etc and nothing apparent. ESX does not report a disconnect or any other issues.  Infact, before I remembered to turn off DRS, it pushed one of the affected VMs back while I was clearing for a reboot :smileysilly: Because it's both blades in one chassis, I'm leaning towards a chassis issue, or the next step out. Network guys say "Not Us", VM guys say "Not Us" .. any ideas where to look or pin this down further? Thanks.
Luckily it wasn't too drastic. I was still able to vMotion to / from the hosts and everything else looked fine. Disconnect and Reconnect didn't work. I had to Remove and then Add Host, the... See more...
Luckily it wasn't too drastic. I was still able to vMotion to / from the hosts and everything else looked fine. Disconnect and Reconnect didn't work. I had to Remove and then Add Host, then the data started showing up again.
Thanks for the info: Peetz:  I see the second msg from the KB article in the logs, but didn't see the first. vLarus:  We'll see how drastic I have to get, but thanks for the info on the vpxa. ... See more...
Thanks for the info: Peetz:  I see the second msg from the KB article in the logs, but didn't see the first. vLarus:  We'll see how drastic I have to get, but thanks for the info on the vpxa. After combing through one-by-one, I found there were actually 4 out of 52 hosts that stopped reporting after patching. Some HP extensions and the Critical and Non-Critical patches for ESX5i from VM - includes the "Update 1" patch. I'll try to get the numbers later. Thanks
esxi5u1, vCenter 5, using VUM, alot of hosts, a number of clusters...etc I noticed that one of my hosts in a cluster stopped reporting performance data to vCenter after I used VUM to patch to ... See more...
esxi5u1, vCenter 5, using VUM, alot of hosts, a number of clusters...etc I noticed that one of my hosts in a cluster stopped reporting performance data to vCenter after I used VUM to patch to latest-greatest. All of my other hosts in the same cluster, and other clusters are reporting fine. I restarted the mgmt services on the host. If I connect vSphere client directly to host, I can see the real-time data. There are no firewalls between the mgmt interfaces on host and vCenter server - can ping from vCenter server to host mgmt port I browsed through some logs (vpxd) looking for something obvious - based on some similar-but-not-quite-the-same issues posted in other blogs - but no luck. It seems like there are no other issues (of course, can't see performance info for guests either - how I first noticed it) Storage vMotion works. Followed the same process for 50+ hosts, and of course one of the last ones has to burp :smileysilly: Any thoughts? Thanks
André Pett wrote: Is there a special requirement to add the ESXi hosts to the domain? Usually you would only add the vCenter Server (Windows server) to the domain. In order to have a proper n... See more...
André Pett wrote: Is there a special requirement to add the ESXi hosts to the domain? Usually you would only add the vCenter Server (Windows server) to the domain. In order to have a proper name resolution you have to manually add a "Host-A" entry for each ESXi host to your DNS server and configure the DNS server IP address(es) on the ESXi hosts. André I was thinking along the same lines while reading this thread - by "Domain" - is it meant to be Active Directory Domain, or Network domain? We don't add our hosts to the AD domain.  vCenter handles AD user authentication for access/mgmt. If for some reason we need to access the host directly, we use root.
Don't ping and you won't see any packets dropped!  Is there a lot of vMotion happening and causing problems? Turn down the aggressiveness of the DRS rules. Add more resources so there is ... See more...
Don't ping and you won't see any packets dropped!  Is there a lot of vMotion happening and causing problems? Turn down the aggressiveness of the DRS rules. Add more resources so there is less DRS-induced vMotion Can you tune RAC to be not so sensitive? When I watch (which is seldom, these days) I usually only see one missed ping, which is typically a moment before vCenter reports Complete.
The thread was mostly about CLI. I'm looking for a fix, not a work-around. Thanks