It has been always a problem to match LUNs on ESX to LUNs on a storage. Eventually I wrote a short script to make this work way easier
Yes, it happened to me too: I forgot my vCenter SSO master password, the one that used for the admin@System-Domain account. VMware KB 2034608 clearly says that “The master password is stored in the database and can only be changed by re-installing vCenter Single Sign-On 5.1 with a fresh back-end database”. It did not give me extra optimism in resolving the issue, but Ingmar Verheij gave me a hope. His article, which you can find here, describes in full details how to reset the SSO master password. My text is just an instruction, so I strongly recommend to read Ingmar’s page first.
Here’s another issue I have faced today. I needed to log into one of our vSphere farms, but the only thing I got using any accounts was this:
I upgraded ESXi host from version 5.1 to version 5.5 and found out that could not vMotion any VMs from the other hosts to the upgraded one. Pretty quick investigation showed that vmk1 interface was missing on the host.
My upgrade from ESXi 4.1 to ESXi 5.5 stuck again (see the post Error26002. Setup failed to register vCenter Server). This time it was the host installation. It stuck after loading all the modules at the message “Relocating modules and starting up the kernel…”
During the new installation of VMware vCenter 5.5, I received an error 26002 while it was trying to register with Inventory Service. The solution was pretty simple, thank you the article that I found here: http://www.petenetlive.com/KB/Article/0000941.htm. Even thought I copied the SSL folder from the previous version of vCenter (as the upgrade document says), it did not work. Actually, the SSL folder should be copied from C:\Program Data\VMware\Infrastructure\Inventory Service to C:\Program Data\VMware\VMware Virtual Center before vCenter installation. So, you need to create the C:\Program Data\VMware\VMware Virtual Center folder first.