Pre-Windows 7, I would have right-clicked the Windows taskbar for the app, selected ‘Move’, and then used the keyboard arrow keys to guide the phantom window home.  Windows 7 does not have the same Windows positioning options on a right-click to the taskbar so I had to find another way. Enter Windows shortcut keys.  Here’s how I brought the VI3 Client window back into view:

1. Make sure that the VI3 Client window is in the foreground by selecting it in the taskbar.  You’ll know that it is in the foreground when the taskbar icon gets a white glow as pictured here:
2. Press the hotkey combination: “ALT+Space, M” for Move.
3. Use the keyboard arrow keys to move the window to your active monitor, pressing “Enter” once the window is visible to commit the move.
4. If the arrow keys fail to move the window and/or you hear the Windows error sound, your VI3 Client windows is probably maximized.  The move option is not available when a window is maximized.  To work around this condition use the hotkey combination: “ALT+Space, R” for Restore.  You should now be able to move the window using steps #2 & #3 above.

If you are still really struggling, break out the trusty old registry editor and follow along:

1. Close any open VMware Infrastructure Client windows
2. Navigate to HKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences\UI
3. Locate the ApplicationLocation key.  This key provides the X-Y coordinate for the VI Client window at startup.
4. Modify the string value to 0-0.  This value will cause the VI3 client to open in the center of your primary display.
5. If you run different sized/resolution displays, you may also want to change the ApplicationMaximized or ApplicationSize keys to fit your needs.
6. Launch the VMware Infrastructure Client and get back to work.

Related posts:

1. vCenter Client Passthrough Authentication I started this blog for a couple reasons: 1.) To...
2. EMC Virtual Storage Integrator Update I upgraded my in-house VMware vSphere environment to 4.0 Update...
3. Securing Your Virtual Infrastructure Between budget cuts and New Year’s resolutions, improving your security...

Be sure to browse the catalog now so you are ready for session registration later in July.  From past experience, knowing what session and labs you want to attend before registration, and then jumping right into registration once it is available, is the best way to ensure you get a slot in the hottest sessions.

Related posts:

1. VMworld Here I Come Today is the last day for VMworld early-bird registration, and...
2. VMworld 2009 Sponsor and Exhibitor List The VMware ecosystem is rich and thriving, with partners, vendors,...
3. Microsoft and VMware Virtualization Documentation Microsoft published a document named “Getting to Know Hyper-V: A...

The system was configured with a single controller with dual GigE NIC’s.  The controller had 512MB of battery backed cache (there is also a 1GB cache upgrade option available).  I wrote off some of the poor performance to a single controller with a less-than-optimal amount of cache; blamed the SAS controller to SATA disk command translation overhead; cringed at the 6 disk RAID5 configuration; and engaged in some self doubting.  I convinced the powers that be that we were IO constrained and got some funds to fill out the 3U chassis to a full 12 SATA disks, and reconfigured the array as a RAID10.  Performance gains were almost unnoticeable with these changes.  In addition, I did some basic troubleshooting of the network environment, verifying multiple paths to the storage, setting Flow Control on the switches to receive only, and double-checked my iSCSI initiator settings.  Note: The DS3300 is only supported with the ESX software initiator.  I found documentation on the DS3300 to be lacking, but did discover that the Dell MD3000i is based on the same LSI Engenio array.  Some Googling on the Dell solution led to to the ‘SMcli’ command line interface for both arrays.   The commands are slighly different for the Dell and IBM.  The links to the IBM CLI documentation were broken, so I had to do a bit of trial and error to get the commands right.  I used the Dell documentation as a starting point.  (Rant: Seriously, IBM?  Can you make your documentation any harder to get through – is it a Redbook, is it an Engineering Whitepaper, is it a support document, is it a case study – and why can I only find these with complex Google searches, not on your own product pages, and why can’t you name for documents intelligently, not with some random string of characters).

Moving on… I received an automated alert from the DS3300 about an incomplete battery learn cycle.  Using the IBM Storage Manager GUI I generated a  Storage Subsystem Profile’ from the Support tab to check the battery status.  In the profile I discovered that while write cache was enabled, it had a status of “Enabled (Suspended)”.   Ah ha!  Now I’ve got some decent Google material that led me to this: http://communities.vmware.com/thread/195838.  Hot damn I love the VMware Community Forums!

It turns out that in a single-controller configuration the setting for cache mirroring remains enabled by default.  Because there is no 2nd controller to mirror to, the array suspends write caching.  This is probably a safety thing – loss of high availability on the controllers puts data in cache at risk should the only controller fail.  I weighed my options and decided that the poor performance I was experiencing beat HA concerns, so I enabled write cache on the array using this command:

c:\program files\ibm_ds4000\client>smcli -n <ARRAYNAME> -c “set allLogicalDrives mirrorEnabled=false;”

And then followed with this for good measure:

c:\program files\ibm_ds4000\client>smcli -n <ARRAYNAME> -p <arraypassword> -c “set allLogicalDrives writeCacheEnabled=true;”

The results were immediately noticeable:

DS3300 Performance Improvement when Write Cache is Enabled - Click for a Larger View

The screen shot is from Veeam Monitor Free Edition, taken during 4 concurrent V2V operations from Hyper-V to VMware.  With the write cache fully functional, disk usage peaked at 54MBps, latency dropped to about 6ms, and my blood pressure dropped a few notches.

While poking around the CLI I also found that you can dump performance stats from the array (performance is otherwise hard to find on the thing) using this command:

C:\Program Files\IBM_DS4000\client>smcli -n <ARRAYNAME> -c “set session performanceMonitorInterval=5 performanceMonitorIterations=120;save storageSubsystem performanceStats file=\”c:\\ds3300perfstats.csv\“;”

This will give you a 10 minute record of performance from the array which you can analyze using Excel.  The Dell Enterprise Center TechCenter Wiki has a great write-up on how to efficiently analyze the data from this command here: http://www.delltechcenter.com/page/MD3000i+Performance+Monitoring, complete with a YouTube video that walks you through the process:

I am beginning to think that the DS3300 (and MD3000i) may actually be a viable starter solution for SMB’s starting out on a virtualization project.  But I would recommend the cache upgrade, 2nd controller, SAS disks instead of SATA to eliminate the SAS-to-SATA translation overhead and more faster disks instead of fewer slower disks so you can drive throughput and IOPS to a higher level.

Have any of you deployed the DS3300 or MD3000i (or the generic LSI solution)?  Do you have any performance tuning tips for these arrays?  If so, share in the comments!

Related posts:

1. Free SAN Monitor for DS3300, MD3000i and others One of my most popular posts to date had been...
2. Storage Basics – Part V: Controllers, Cache and Coalescing My Storage Basics series has been neglected for some time...
3. Storage Basics – Part IV: Interface In parts I, II, and III of the Storage Basics...

I just built up a new laptop and couldn’t remember how to set up pass-through authentication on my VI3 Client. A quick Google search gave me the answer, courtesy of Stu Radnidge‘s post on nothing other than VirtualCenter 2.5 Passthrough Authentication.  This little gem saves the terribly tedius work of having to manually enter your login credentials each time you launch the Virtual Infrastructure 3 Client by passing through your currently logged-in credentials to the VC server.  Thanks for the tip, Stu!

Related posts:

1. Virtual Infrastructure Client Opens Off Screen A user reported an issue with one of the VM’s...
2. vCenter Database Stats Rollup Troubleshooting VMware vCenter collects performance statistics, tasks and events for historical...
3. OT: Joining a Mac to a Windows Active Directory We picked up a few new 17″ MacBook Pro’s at...