Comments for VMwise http://vmwise.com Info on virtualization among other things Tue, 07 Feb 2012 14:44:56 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on SvMotion with RDM with Windows Dynamic Disks by How to Identify ESXi Boot LUN | VMwise http://vmwise.com/2012/01/30/svmotion-with-rdm-with-windows-dynamic-disks/#comment-1784 How to Identify ESXi Boot LUN | VMwise Tue, 07 Feb 2012 14:44:56 +0000 http://vmwise.com/?p=706#comment-1784 [...] 7, 2012By KjBI recently posted about my misadventures into SAN array migrations and RDM’s here and here.  Glad to say that part is at least completed.  Now, it’s time to move off of the [...] [...] 7, 2012By KjBI recently posted about my misadventures into SAN array migrations and RDM’s here and here.  Glad to say that part is at least completed.  Now, it’s time to move off of the [...]

]]> Comment on DC VMUG Jan 17th @ Nats park by Chris http://vmwise.com/2012/01/06/dc-vmug-jan-17th-nats-park/#comment-1736 Chris Tue, 31 Jan 2012 23:19:59 +0000 http://vmwise.com/?p=678#comment-1736 Hi Kanuj, Sorry that this message isn't in a relevant spot. I work for EMC, follow your blog and tweets, and would like to invite you to a special webcast/Q&A. I couldn't find your email, so I'll leave you mine. I'd like to send you more information on this event. I hope to hear from you. Thanks, Chris chris [dot] britt [at] emc [dot] com Hi Kanuj,
Sorry that this message isn’t in a relevant spot. I work for EMC, follow your blog and tweets, and would like to invite you to a special webcast/Q&A. I couldn’t find your email, so I’ll leave you mine. I’d like to send you more information on this event. I hope to hear from you.
Thanks,
Chris
chris [dot] britt [at] emc [dot] com

]]> Comment on Back from the Dead (Surviving vCenter crash for Lab Manager) by Lab Zepplin http://vmwise.com/2010/05/20/surviving-vcenter-crash-for-lab-manager/#comment-1525 Lab Zepplin Sun, 08 Jan 2012 03:59:44 +0000 http://vmwise.com/?p=5#comment-1525 This worked for me! Thanks - you saved me a lot of pain. This worked for me! Thanks – you saved me a lot of pain.

]]> Comment on When a Reconnect is Not Enough by KjB http://vmwise.com/2011/03/21/when-a-reconnect-is-not-enough/#comment-1492 KjB Thu, 05 Jan 2012 17:18:22 +0000 http://vmwise.com/?p=424#comment-1492 This can happen if either your ESX host never completely registered with vCenter, or if you had a partially successful removal of the host from vCenter. A full removal would remove the vpxuser account, as well as the vpxa agent and the ha agent. If you don't see the vpxuser, then that step is done for you :) -KjB This can happen if either your ESX host never completely registered with vCenter, or if you had a partially successful removal of the host from vCenter. A full removal would remove the vpxuser account, as well as the vpxa agent and the ha agent.

If you don’t see the vpxuser, then that step is done for you :)

-KjB

]]> Comment on When a Reconnect is Not Enough by shane http://vmwise.com/2011/03/21/when-a-reconnect-is-not-enough/#comment-1487 shane Thu, 05 Jan 2012 14:34:05 +0000 http://vmwise.com/?p=424#comment-1487 when I try ◦Delete the user account vCenter uses to communicate with the host. –> userdel vpxuser I get no user found?!? when I try
◦Delete the user account vCenter uses to communicate with the host. –> userdel vpxuser
I get no user found?!?

]]> Comment on When a Reconnect is Not Enough by Mike Haun http://vmwise.com/2011/03/21/when-a-reconnect-is-not-enough/#comment-1474 Mike Haun Wed, 04 Jan 2012 21:46:15 +0000 http://vmwise.com/?p=424#comment-1474 That was exactly my case here. I've learned a valuable lesson today, and thanks much for your assistance. That was exactly my case here. I’ve learned a valuable lesson today, and thanks much for your assistance.

]]> Comment on When a Reconnect is Not Enough by KjB http://vmwise.com/2011/03/21/when-a-reconnect-is-not-enough/#comment-1473 KjB Wed, 04 Jan 2012 20:48:59 +0000 http://vmwise.com/?p=424#comment-1473 Datastore loss or inaccessibility is a very common cause of a host to disconnect from vCenter. The agent is pretty low priority, as opposed to datastore checking, so an ESX host will devote many cycles to attempt to bring a datastore online, once lost, and the vpxa (vCenter agent) will suffer. If you removed access to the datastore without removing it first from ESX, that is most likely your problem. -KjB Datastore loss or inaccessibility is a very common cause of a host to disconnect from vCenter. The agent is pretty low priority, as opposed to datastore checking, so an ESX host will devote many cycles to attempt to bring a datastore online, once lost, and the vpxa (vCenter agent) will suffer. If you removed access to the datastore without removing it first from ESX, that is most likely your problem.

-KjB

]]> Comment on When a Reconnect is Not Enough by Mike Haun http://vmwise.com/2011/03/21/when-a-reconnect-is-not-enough/#comment-1472 Mike Haun Wed, 04 Jan 2012 20:17:43 +0000 http://vmwise.com/?p=424#comment-1472 In my case there were several hundred writes that were queued up in the ESXi host and retrying to a datastore that was removed yesterday afternoon! Somehow (?), this caused the disconnect and when using your technique to reconnect, the task got stuck at the 80% point and stayed there. To fix, I either bring back the removed datastore on the SAN or restart the ESXi host at the next maintenance window. Thanks again, Mike In my case there were several hundred writes that were queued up in the ESXi host and retrying to a datastore that was removed yesterday afternoon! Somehow (?), this caused the disconnect and when using your technique to reconnect, the task got stuck at the 80% point and stayed there. To fix, I either bring back the removed datastore on the SAN or restart the ESXi host at the next maintenance window.
Thanks again,
Mike

]]> Comment on When a Reconnect is Not Enough by Mike Haun http://vmwise.com/2011/03/21/when-a-reconnect-is-not-enough/#comment-1471 Mike Haun Wed, 04 Jan 2012 20:10:50 +0000 http://vmwise.com/?p=424#comment-1471 KjB, I repeated the process and this time it went perfectly, so my previous post can be ignored. Thanks again, Mike KjB,
I repeated the process and this time it went perfectly, so my previous post can be ignored.
Thanks again,
Mike

]]> Comment on When a Reconnect is Not Enough by KjB http://vmwise.com/2011/03/21/when-a-reconnect-is-not-enough/#comment-1469 KjB Wed, 04 Jan 2012 18:34:53 +0000 http://vmwise.com/?p=424#comment-1469 Typically, this error is from a version mismatch between vCenter and ESX. vCenter always has to be the latest revision in the cluster. Is that the case in your cluster? -KjB Typically, this error is from a version mismatch between vCenter and ESX. vCenter always has to be the latest revision in the cluster. Is that the case in your cluster?

-KjB

]]>