In my previous post I noted my excitement about the upgrades in the future that will not require SSH access and running .rpm files as VMware is now doing updates much like vC Ops. While I think this is magnificent, it isn’t my favorite new feature within the new release. I would have to say that the direct integration to have ESXi logs sent directly to vCenter Log Insight 1.5 with configuration done through the appliance is my most welcome new feature. I am sure others will argue that some of the new features in the Dashboard for storage are their favorite new features, but the ability to configure ESXi hosts directly through the appliance is certainly my favorite new feature (if it existed before I am still excited as it is super simple now. Simply access the Administration of the appliance and then select vSphere below Integration. One then checks the box for ESXi hosts and most of the magic is done for you (you must click Save for the magic to happen and sorry for not stating that directly, but if you are reading this you probably figured something like that out already). If you want to see what hosts are configured you can select “View ESXi syslog configuration details…” to see what hosts are configured resolve any issues with configuration. Sorry for the lack of screenshots, but I thought of this posting after already going through the motions. If anyone has questions please feel free to reach out to me.
I am scared and happy to announce that I won the “Tell Your Story” contest that VMware held for the opportunity to tell the story of implementing VMware vCenter Operations Manager at my largest client (contest). It will be fun to tell the story of how implementing this product has helped …. you will have to be at VMworld for the session (CIM1775) 🙂
This week I came across an error while trying to upgrade VMware vCenter Operations manager to the latest version (5.0.2). After downloading the .pak upgrade file I tried to login to the appliance at https://URL2vCops/admin/. I used the User Name and Password that I setup the appliance with and could not authenticate. I then went out to KeePass to verify that I remembered the password correctly and I was correct. I tried again to authenticate and could not. At this point I decided to get on the console of the UI VM and see if I could authenticate using the root account. After authenticating with root I tried su admin to log the admin user onto the console. I had to enter su admin twice and was able to authenticate with the documented password. Pretty annoyed right now as I again tried to login to the admin portal and failed to do so using a username and password that are working on the console. I used my Google Ninja Search skills to find this KB from VMware regarding resetting user accounts including the admin account. I downloaded the script and followed the directions and received an error that the password could not be changed. I followed the included link regarding automatic lockout (KB) and was not experiencing the issues it described.
I then thought back to a day when there were issues logging into the UI to view data. That day it was discovered through trials and tribulations that the vAPP had run out of space. The application could not be used because the vAPP was out of diskspace, but did not indicate this to be the issue anywhere. After powering the vAPP off and adding an additional .vmdk file I powered the vApp back on and magically could use the vAPP. I thought that while the issues were very similar that quite possibly the would be unrelated and was wrong. After powering the vAPP off and adding an additional .vmdk I powered it back on. I could again authenticate.
This has been very frustrating to deal with as the vAPP does not give indication that while I cannot authenticate it is only due to the fact that the vAPP is now out of usable diskspace. I hope that VMware does create KBs soon for this.