Today HP made an announcement in regards to their storage products that made many across IT yawn a little bit. It sounds like the EVA line has been consolidated into the 3PAR products. The new product is the HP 3PAR StoreServ 7000. HP claims a “guaranteed” 50% savings in efficiency using hardware enabled thin technology and autonomic tiering without performance tradeoffs. HP claims “effortless” administration without the need for a storage expert while reducing management time by 90%. Autonomic management utilizing self configuring, self optimizing, and self provisioning techniques are the terms used in the “effortless” administration of the new product. HP claims to eliminate inflexibilities and boundaries that block the changing business needs with the new “bulletproof” storage system.
HP claims to have Tier 1 features now in economy size allowing businesses to double their VM capacity without doubling their storage capacity. The virtually limitless scale makes the new product future proof by providing the ability to upgrade pieces of technology within the product at any time. Where the announcement becomes interesting is the claim by HP that this eliminates the distinction between mid-range and Tier 1 class storage. The new product can be delivered for less than $40,000 at a Tier 1 level. Now HP has a single architecture that can deliver common Tier 1 data services from the redefined mid-range of $25,000 to the high end and newly named HP 3PAR StoreServ 10800. HP has essentially eliminated class distinction between mid-range and Tier 1 storage by delivering common services across the board.
I will watch the announcements and look for further information in the future to write about. While this announcement isn’t ground breaking, it is a great move by HP to allow customers to grow as their storage needs increase. I think the HP online import for EVA is one of the best pieces of the announcement allowing customers to “easily” migrate EVA data to their new 3PAR storage.
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.
I had a frustrating time a while back trying to do VMware vSphere admin work on an iMac. I run a Windows 7 VM using VMware Fusion. The issue I ran into was building nested VMware ESXi hosts and pressing F11. Pressing F11 natively turns up the volume, and does so also while in the Windows 7 VM. I thought to press the FN key with F11 to find out now my windows all disappear taking me to the desktop (probably some OS X term that I should know since people call me a fanboy, but not coming to mind now). I solved the issue initially by booting my MacBook Air to a BootCamp’d version of Windows 7 and doing the install there as it was quick and dirty. Today after pressing many key combinations I finally figured out the magic. After work I decided to start working on the build of a lab for Indy VMUG Demo Days 2012. I would really like to put together a lab to show off the vSphere Replication piece of VMware Site Recovery Manager 5. I think the technology to migrate to a new datacenter with unlike hardware on the other end is valuable. Well building this lab requires a few nested ESXi hosts and will require a few presses of F11. The magic key combination is COMMAND + FN + F11.
*update* it was brought to my attention to use the menu and follow Virtual Machine > Send Key > F11. For some reason or other my memories are of it not working. I will have to try it again this evening. Other articles out there say to use FN + F11, which I believe works on the Bluetooth keyboard, however with my iMac I use the full keyboard and it does not work and requires COMMAND + FN + F11
*update 2* I have verified that using the Virtual Machine > Send Key > F11 does in fact work. I prefer the keystrokes, but to each his own.