Archive for the ‘Virtualization’ category

VMware VCAP Certification Details Announced

May 24th, 2010

VMware has announced the details of their new VMware Certified Advanced Professional (VCAP)certification.  I scribbled some notes from this morning’s VCAP conference call but after visiting VMware’s official announcement page, I see they have detailed out the certification path details nicely in the exhibit I’ve borrowed and posted below:

VMW_10Q2_VCDX4_Upgrade_Path2

The VCAP in and of itself is a level of certification that fits technically between the VCP and VCDX levels of certification.  Somewhat similar to the MCSE where an individual can bolt on a specialized designation to their letters, the VCAP was launched with two designations (one or the other is required to earn the base VCAP level of certification):

  • Datacenter Administrator
  • Datacenter Design

The VCAP is directly related to VCDX4 certification in that both exams are required for candidates which are not already VCDX3 certified (also note that VCP4 is required to sit either of the two new VCAP exams).  In other words, the DCA and DCD exams are the VCDX4 version of written exams which map respectively to the Enterprise Administration and the Design exam which VCDX3 candidates would have sat.

The 41 individuals who are already VCDX3 certified must only sit the DCD exam to both upgrade to VCDX4 as well as achieve VCAP-DCD certification.  If this same person would also like the VCAP-DCA designation, he (so far the current VCDX3 pool is all fellas) must pass the DCA exam.  As a VCDX3 myself, I understand and appreciate the requirement to sit the new Design exam to upgrade to VCDX4, but I feel the additional exam requirement for a VCDX3 or VCDX4 to achieve DCA doesn’t make sense.  I see it as additional exam revenue for VMware.  Yes, technically I don’t need to become a VCAP-DCA but if that is something I’d like to add to my resume, the exam and the payment is required.  I guess I was banking too much on the rumors that individuals who already passed the Enterprise Admin exam for VCDX3 would have been grandfathered in to the new certification.  I’d write more but I need to board a plane.  Comments welcome of course. 🙂

Update 5/26/10:  According to the VMTN Roundtable podcast today, the VCAP-DCA exam will be available in July and the VCAP-DCD exam will be available in August.

VCAP Benefits:

  • Industry/Peer recognition
  • New certification logos
  • VMworld discounts
  • Allowed entry in VCAP community site (sounds like nothing more than a VMTN forum)
  • Value-add live lab content which cannot be compromised by brain dump sites

Happy Birthday vSphere!

May 21st, 2010

birthday-cake

I was reminded by today’s vCalendar page that vSphere was launched by VMware one year ago today.  Happy Birthday Buddy – you set the bar which all other hypervisors aspire to be at one day.

On this day in 2009, VMware vSphere, the next generation datacenter virtualization product and successor to Virtual Infrastructure 3 (VI3), was released boasting approximately 150 new features, new license tiers, and an amazing 350,000 I/O operations per second (IOPS). vSphere is a 64-bit only ESX host OS.

Don’t have a vCalendar yet?  Get one!

Top 10 Free vSphere ESX Tools and Utilities by KendrickColeman.com

May 19th, 2010

KendrickColeman.com has compiled a nice list of no-cost VMware vSphere utilities. A grading scale was disclosed to provide a value ranking of the utilities.  Information like this is valuable because I often see questions raised in the virtualization community about low-cost or no-cost ways to do this or that with VMware virtual infrastructure (backup is a frequent request).  I will be the first to admit that lab time is precious.  KendrickColeman.com has used their free time to install, test, and summarize each application for the benefit of the community.  Nice job and on behalf of the virtualization community, Thank You!

Speaking of free, KendirckColeman.com has also pointed to a VMTN forum member who stumbled onto a way to use a free ESXi 4.0 license key to permanently license ESX 4.0.  Interesting find there.

Minneapolis VMUG / Veterans Sock Drive Benefit Friday

May 18th, 2010

Friendly reminder that from 1-5pm this Friday, the Minneapolis VMware User Group will hold a quarterly meeting in Bloomington.  I expect a lot of VDI content.  The meeting details can be found here.

Location:
Hilton Minneapolis
Bloomington Ballroom Foyer A
3900 American Boulevard West
Bloomington, MN 55437

In addition…

VMware is proud to work with the Minnesota Assistance Council For Veterans (MACV) by supporting a one day SOCK DRIVE BLITZ at the VMware User Group Meeting (VMUG). 

On Friday 21 May 2010 MACV and VMware will be collecting packages of new white cotton socks (primarily men’s sizes) as part of the MACV Veterans Standdown. The socks collected will then be distributed to homeless veterans in need at the Various standdown events across Minnesota throughtout the year. 

SOCK DRIVE BENEFITTING HOMELESS VETERANS

Items Needed for donations:
Packages of new white cotton socks
(primarily men’s sizes)

Minnesota Assistance Council for Veterans (MACV) is a 501(c) 3 non-profit organization assisting veterans (and their families) in crisis throughout Minnesota for over 18 years including those who are experiencing homelessness. MACV is the only organization of its kind in the State of Minnesota completely dedicated to serving the needs of veterans, and is nationally recognized for its model and success.

P2V Milestone

May 15th, 2010

If you’re reading this, that’s good news because it means last night’s P2V completed successfully.  I took the last remaining non-virtualized physical infrastructure server in the lab and made it a virtual machine.  Resource and role wise, this was the largest physical lab server next to the ESX hosts themselves.

Resources:

  • HP Proliant DL380 G3
  • Dual Intel P4 2.8GHz processors
  • 6GB RAM
  • 1/2 TB  local storage
  • Dual Gb NICs
  • Dual fibre channel HBAs

Roles:

  • Windows Server 2003 R2 Enterprise Edition SP2
  • File server
    • binaries
    • isos
    • my documents
    • thousands of family pictures
    • videos
  • Print server
  • IIS web server
    • WordPress blog
    • ASP.NET based family web site
    • other hosted sites
  • DHCP server
  • SQL 2005 server
    • vCenter
    • VUM
    • Citrix Presentation Server
  • MySQL server
    • WordPress blog
  • Backup Sever
  • SAN management

I’m shutting down this last remaining physical server as well as the tape library.  They’ll go in the pile of other physical assets which are already for sale or they will be donated as sales for 32-bit server hardware are slow right now.  This is a milestone because this server, named SKYWALKER – you may have heard me mention it from time to time, has been a physical staple in the lab for as long as the lab has existed (circa 1995).  Granted it has gone through several physical hardware platform migrations, its logical role is historic and its composition has always been physical.  To put it into perspective, at one point in time SKYWALKER was a Compaq Prosignia 300 server with a Pentium Pro processor and a single internal Barracuda 4.3GB SCSI drive.  Before my abilities to acquire server class hardware, it was hand-me-down whitebox parts from earlier gaming rigs.

The P2V (using VMware Converter) took a little over 5 hours for 500GB of storage.  So the only physical servers remaining in the lab are the ESX hosts themselves.  2 DL385 G2s and 2 DL385s which typically remain powered down, earmarked for special projects.  A successful P2V is a great start to a weekend if you ask me.  Now I’m off to my daughter’s T-ball game. 🙂

Microsoft Exchange 2003 to Exchange 2010 Upgrade Notes

May 14th, 2010

Last weekend I successfully upgraded, ahem, migrated the lab infrastructure from Microsoft Exchange 2003 to Exchange 2010.  This upgrade has been on my agenda for quite some time but I had been delaying it mainly due to lack of time and thorough knowledge of the steps.  I had a purchased the Microsoft Exchange Server 2010 Administrator’s Pocket Consultant (ISBN: 978-0-7356-2712-3) in January and marked up a few pages with a highlighter.  However, the deeper I got in the book, the more daunting the task seemed to have become, even for a simple one-server environment like mine.  In my mind, Exchange has always been somewhat of a beast, with increasing levels of difficulty as new editions emerged.  The pocket consultant series of books are wonderfully technical, but they haven’t been able to fit in my pocket for about a decade. They contain so much content that it has become difficult to rely on them as a CliffsNotes guide for platform upgrades, especially when it comes to Exchange.

Then two things happened miraculously at the same time.  First, I was invited to a private beta test of a virtualization related iPad application.  As part of this test, I needed to be able to send email from my iPad.  I had been unsuccessful thus far in getting Microsoft Exchange ActiveSync to work with the iPad (even after following Stephen Foskett’s steps) and could only assume that it was due to several years of wear and tear on my Exchange 2003 Server.  I needed to get that upgrade to Exchange 2010 done quickly.  Second, the May 2010 issue of Windows IT Pro magazine showed up in my mailbox.  To my delight, it was chock full of Exchange 2010 goodness, including a cover story of “Exchange 2003 to Exchange 2010 Step-by-Step Exchange Migration”. I’m pretty sure this was divine intervention with the message being “Get it done this weekend, you can do this.”

The upgrade article by Michael B. Smith started on page 26 and was 100% in scope.  The focus was a single server Exchange environment upgrade from 2003 to 2010.  I read the seven page artile in its entirety, marking up key “to-do” steps with a highlighter.  Following are some things I learned along the way:

  1. Naturally the Exchange server is virtualized on VMware vSphere.
  2. My Exchange environment is built upon a foundation that dates back as far as Exchange 5.5 (pre-Active Directory).  There would be no in place upgrades.  Exchange hasn’t provided an upgrade since Exchange 2003.  That suited me just fine as the Exchange 2003 server has been through so much neglect, although it had gotten pretty slow, it’s a miracle it was still functional.  The Exchange migration will consist of bringing up a fresh OS with a new installation of Exchange, and then migrating the mailboxes and services, and then retiring the old Exchange Server.  Microsoft calls this a migration rather than an upgrade.
  3. Exchange must be running in Native mode.  Not a problem, I was already there.
  4. Pre-migration, there exists a hotfix from Microsoft which is recommended to be installed on the Exchange 2003 server.  http://support.microsoft.com/kb/937031/
  5. The Schema Master mast be running Windows Server 2003 SP1 or higher.
  6. There needs to be at least one Global Catalog server at Windows Server 2003 SP1 or higher in the Exchange site.
  7. The AD forest needs to be at Server 2003 Forest Functional Level or higher.
  8. The AD domain needs to be at Server 2003 Domain Functional Level or higher.
  9. For migration flexibility purposes, Exchange 2003 and Exchange 2010 both support DFL and FFL up to Server 2008 R2.
  10. Exchange 2010 requires 64-bit hardware.  No problem, that requirement was met with vSphere .
  11. Exchange 2010 can be installed on Windows Server 2008 or Windows Server 2008 R2.  I naturally opted for R2.  No sense in deploying a two-year old OS when a more current one exists and is supported.  Plus, I personally need more exposure to 2008 and R2… 2003 is getting long in the tooth.
  12. Copy the Exchange DVD to a data/utility drive on the server.  Reason being, you can drop the most recent rollup available into the \Updates\ folder and basically perform a slipstream installation of Exchange with the most recent rollup applied out of the gate.  As of this writing, the most current is Rollup 3.
  13. Here’s a big time saver, install the server roles and features Exchange 2010 requires using the provided script on the DVD:
    \scripts\ServerManagerCmd -ip Exchange-Typical.xml -restart
    Other sample pre-requisite installer scripts can be found here.
  14. The 2007 Office System Converter: Microsoft Filter Pack (x64) is required to be installed.  This is downloadable from Microsoft’s website.  A little strange, but I’ll play along.  It’s required for the Exchange full-text search engine to search Office format documents.
  15. Run the following commands for good measure. It may or may not be required depending on what’s been done to the server so far:
    sc config NetTcpPortSharing start= auto
    net start NetTcpPortSharing
  16. Setup logs for Exchange are found in C:\ExchangeSetupLogs\  The main one is ExchangeSetup.log.  Hopefully you won’t have to rely on these logs and you are blessed with a trouble-free installation.
  17. There are the usual Active Directory preparatory steps to expand the Schema which seem to have increased in quantity but I could be hallucinating:
    1. setup.com /PrepareLegacyExchangePermissions
    2. setup.com /PrepareSchema
    3. setup.com /PrepareAD
    4. setup.com /PrepareAllDomains
  18. Installation can be invoked by CLI with setup.com /mode:install /roles:ca,ht,mb however, I chose a GUI installation which was more intuitive for me.
  19. The article stated the installation would take at least 20 minutes on fast hardware.  My installation took less than 15 minutes on a VM hosted by four year old servers attached to fibre channel EMC Celerra storage – bitchin.
  20. A Send connector is required before Exchange 2010 will route mailto the internet.
  21. Exchange 2010 ships with two Receive connectors but they must be configured before they will accept anonymous email from the internet.
  22. Exchange 2010 is managed by the Exchange Management Console which is called the EMC for short.  That will be easy to remember.
  23. Exchange 2010 is also managed by PowerShell scripts (also called an Exchange Management Shell, or EMS for short).  There are some configuration tasks which can only be made via PowerShell script and not via the EMC.
  24. Lend your end users and Helpdesk staff a hand by creating a meta-refresh document in C:\inetpub\wwwroot\ which points to https://<mail_server_fqdn>/owa effectively teleporting them into Outlook Web App (did you catch the name change? no more Outlook Web Access)
  25. Mailboxes are no longer moved online due to their potential size and problems which may occur if a mailbox is accessed during migration.  Mailbox migrations are now handled via EMC by way of a Move Request (either local [same org] or remote[different org]).  When a move request is submitted, the process begins immediately but may take some time to complete obviously based on the size of the mailbox as well as the quantity of mailboxes multiple selected for the move request.  Tony Redmond wrote a decent article on how this is done.  Scheduled move requests can be instantiated via PowerShell script.
  26. One of the final steps of a successful migration is properly decommissioning the old Exchange 2003 environment.  This is where things got a little hairy, and I half wasn’t surprised.  Upon attempting to uninstall Exchange 2003 to properly remove its tentacles from Active Directory and the Exchange organization, I was greeted by two errors in the following message:
    5-9-2010 9-16-31 PM
    In the legacy Exchange 2003 System Manager, there are two Recipient Update policies which exist.  Going from memory, one was for the domain which I was able to remove easily, and one was an Enterprise policy which cannot be removed via the System Manager.  Follow the instructions near the end of this article for the procedure to modify Active Directory with adsiedit.
    The second error message deals with removal of the legacy Routing Group Connector.  There were actually two which needed to be removed.  The only way to remove the Routing Group Connector is via PowerShell and it is also described towards the end of this article.
  27. After addressing the issues above, the uninstaller ran briefly and then failed for an unknown reason.  Upon attempting to re-run the uninstall, I noticed the ability uninstall Exchange 2003 via Add/Remove Programs in the Control Panel had disappeared, as if it was successfully uninstalled. Clearly it was not as the Exchange services still existed, were running, and I could launch System Manager and manage the organization.
  28. ActiveSync doesn’t work out of the box on privileged administrator level accounts due to security reasons.  If you accept the risk, this behavior can be changed by enabling the inheritance checkbox on the user account security property sheet.

I’m pretty happy with the results.  The process took took quite a few steps but I am nonetheless pleased.  Careful work following a very nicely outlined procedure by Michael B. Smith has yielded both a snappy-fast Exchange 2010 server on Windows Server 2008 R2 as well as ActiveSync integration with my iPad.  Exchange 2010 is a beast.  I can’t imagine tackling an Exchange project for anything larger than the smallest of environments.  I’m not sure how I can have so many years experience managing my own small Exchange environment yet still lack the confidence in the technology.  I guess it mostly runs itself and as I said earlier, it’s quite resilient meaning it doesn’t require much care and feeding from me.  And thank God for that.

NetApp disk replacement – so easy a caveman and his tech savvy neighbor can do it

May 13th, 2010

The NetApp filer in the lab recently encountered a failed disk.  With the failed disk confirmed dead and removed, and the replacement disk added, I made my first attempt at replacing a failed disk in a NetApp filer.

fas3050clow*> disk assign 0a.29
disk 0a.29 (S/N 3HY0T1GG00007342W9NJ) is already owned by system cr2conffd03 (ID
 84173417).
disk assign: Assign failed for one or more disks in the disk list.

Detour.  The following parsed output confirmed this disk had ownership information from a previous filer in its DNA:

fas3050clow*> disk show -a
  DISK       OWNER                  POOL   SERIAL NUMBER
———— ————-          —–  ————-
0a.29        cr2conffd03(84173417)   Pool0  3HY0T1GG00007342W9NJ

Quick help from the community set me in the right direction.  A few commands accomplished the required task:

fas3050clow*> priv set advanced
fas3050clow*> disk assign 0a.29 -s unowned -f
Note: Disks may be automatically assigned to this node, since option disk.auto_a
ssign is on.
fas3050clow*> disk assign 0a.29
Thu May 13 13:30:56 CDT [fas3050clow: diskown.changingOwner:info]: changing owne
rship for disk 0a.29 (S/N 3HY0T1GG00007342W9NJ) from unowned (ID -1) to fas3050c
low (ID 101175198)
Thu May 13 13:30:56 CDT [fas3050clow: HTTPPool00:warning]: HTTP XML Authenticati
on failed from 192.168.110.71.
fas3050clow*> Thu May 13 13:30:56 CDT [fas3050clow: diskown.RescanMessageFailed:
warning]: Could not send rescan message to fas3050clow. Please type disk show on
 the console of fas3050clow for it to scan the newly inserted disks.
Thu May 13 13:30:56 CDT [fas3050clow: raid.assim.label.upgrade:info]: Upgrading
RAID labels.
Thu May 13 13:30:57 CDT [fas3050clow: disk.fw.downrevWarning:warning]: 1 disks h
ave downrev firmware that you need to update.
Thu May 13 13:31:00 CDT [fas3050clow: monitor.globalStatus.ok:info]: The system’
s global status is normal.

Shortly after, the firmware on the replacement disk was automatically upgraded:

Thu May 13 13:31:18 CDT [fas3050clow: dfu.firmwareDownloading:info]: Now downloa
ding firmware file /etc/disk_fw/X274_SCHT6146F10.NA16.LOD on 1 disk(s) of plex [
Pool0]…

I confirmed via NetApp System Manager (my GUI crutch), that the replaced disk is now a spare for the two aggregates configured on/owned by the head.  I then updated the storage array spreadsheet I maintain which tracks disks, spares, arrays, luns, aggregates, volumes, exports, groups, pools, etc. for the various lab storage.

One additional item I learned from a NetApp Engineer is that spares are not to remain static.  Rather, the role is designed to float around to different disks as failures can and will occur.  This is a habit I’m learning to break which contradicts management of older storage arrays where spares instantiated to active duty were later deactivated when a failed disk was replaced.

As Erick Moore suggests in the comments, don’t forget to exit privileged mode when done:

fas3050clow*> priv set

Jason Langer, the spreadsheet is really nothing special. Merely a tool I use to keep track of the storage configurations. Following is a screenshot:

SnagIt Capture