Posts Tagged ‘Lab Manager’

New VMware vCenter Lab Manager Video Tutorial Series

July 8th, 2010

VMware has started a new Lab Manager video series and has kicked things off by posting three inaugural videos:

  1. Lab Manager Introduction and Product Overview
  2. Organizations within vCenter Lab Manager
  3. Workspaces within vCenter Lab Manager

VMware states that the next videos in the series will be:

  • Managing Users and Groups within vCenter Lab Manager
  • Networking within vCenter Lab Manager

The videos are authored by Graham Daly who works for VMware out of the Cork, Ireland office.  The videos are short at well under 10 minutes each and provide introductory level information on Lab Manager components and administrative containers.  If you haven’t used Lab Manager before, it’s enough to get you curious.

KB article (1020915) is going to act as a central location or a “one-stop-shop” for tutorial style videos which will discuss and demonstrate the various different topics/aspects of the Lab Manager product. As new videos become available, they will be added to the article.

I haven’t seen any books to date on use of Lab Manager.  From a training and education standpoint, the Lab Manager installation guide and the Lab Manager user’s guide actually isn’t too bad.  Someone last night was looking for advice on Lab Manager training and I recommended printing these two .PDF documents out and sticking them in a 3-ring binder like I did.  You’ll be able to whip through them in a few hours as much of the content is repeated time and again in the user’s guide.  Beyond that, the best Lab Manager training is continuous use of the product.  As I stated last night, Lab Manager is a bit of a different animal, even for a VMware junkie (like me).

Boil down the complexity and black magic of the Lab Manager product by looking at it as a tiered application consisting of

  • virtual infrastructure (ESX(i) and vCenter, you know this already),
  • a web front end (that’s the Lab Manager server, which by the way runs great as a VM),
  • and a database (which also runs on the Lab Manager server and only on the Lab Manager server – yep, it’s local MS SQL Express, and yep, it has scaling and migration issues).

The Tomcat on Windows web interface is the front end where Lab Manager environments are built and managed.  The web interface sends tasks to the vCenter Server which in turn commands the ESX(i) hosts (ie. build this VM, register it, power it on, make a snapshot, now clone it, etc.)  State information and other configuration items are stored in the database.  For obvious reasons, the database and vCenter always need to be on the same page.  When they get of sync is where hell begins but I’ll save that discussion for a distant blog post entitled “Lab Manager: fun to build and play with, no fun to troubleshoot”. It’s a lot like Citrix Presentation Server in that respect.

Lab Manager 4 Installation Fails With vSphere VMXNET 3 NIC

November 7th, 2009

A few of the networking requirements for installing a VMware Lab Manager server are:

  1. At least one network card
  2. A static TCP/IP configuration (no DHCP)

Failure to meet the above requirements will result in error message # 5014 during the “Valid NIC Requirement” prerequisite check:

Lab Manager servers make fine virtualization candidates, therefore, it makes sense to deploy them as VMs on existing VMware virtual infrastructure so that they can take advantage of all the benefits VMware brings into the datacenter.

I ran into a new issue installing Lab Manager 4 in a vSphere VM which I configured with a VMXNET 3 virtual NIC. Already aware of the networking requirements, I had configured the virtual NIC with a static TCP/IP address, subnet mask, default gateway, and DNS servers. However, I was surprised to find out that my installation was failing the Valid NIC Requirement prerequisite.

So I resorted to what any certified professional would in this situation: GOOGLE. A quick search revealed scarce results but thankfully one solution. In this VMTN forums thread, a short discussion reveals that the VMXNET 3 virtual NIC is unexpectedly not compatible with the Lab Manager 4 installation prerequisites check. VMTN user MLaskowski012 explains:

“Talked to support and they said they are seeing the same issues. I guess nobody tested LabManager4 with the new hardware. BUT I think I figured out the trick. In device manager under NIC / Advanced if you change the Speed / Duplex from Auto Negotiation 10GB to 1GB Full, run the pre-check it will pass. Then right after you finish the install you can switch back to Auto or 10Gb. Not sure if there are any issues pass that…”

Viola! The trick works. Thank you MLaskowski012 for doing the legwork on this one. Unfortunately, no KB article from VMware yet on this (that I could find), but once again, as it has millions of times in the past, the VMTN community has fulfilled one of its primary purposes: technical support for the community, by the community.

Update 11/8/09: Via lab testing, the same failure and workaround applies to Lab Manager 3 installations with a VMXNET 3 virtual network adapter as well.

Lab Manager 4 and vDS

September 19th, 2009

VMware Lab Manager 4 enables new functionality in that fenced configurations can now span ESX(i) hosts by leveraging vNetwork Distributed Switch (vDS) technology which is a new feature in VMware vSphere. Before getting overly excited, remember that vDS is a VMware Enterprise Plus feature only and it’s only found in vSphere. Without vSphere and VMware’s top tier license, vDS cannot be implemented and thus you wouldn’t be able to enable fenced Lab Manager 4 configurations to span hosts.

Host Spanning is enabled by default when a Lab Manager 4 host is prepared as indicated by the green check marks below:

When Host Spanning is enabled, an unmanageable Lab Manager service VM is pinned to each host where Host Spanning is enabled. This Lab Manager service VM cannot be powered down, suspended, VMotioned, etc.:

One ill side effect of this new Host Spanning technology is that an ESX(i) host will not enter maintenance mode while Host Spanning is enabled. For those new to Lab Manager 4, the cause may not be so obvious and it can lead to much frustration. An unmanageable Lab Manager service VM is pinned to each host where Host Spanning is enabled and a running VM will prevent a host from entering maintenance mode. Maintenance mode will hang at the infamous 2% complete status:

The resolution is to first cancel the maintenance mode request. Then, manually disable host spanning in the Lab Manager host configuration property sheet by unchecking the box. Notice the highlighted message in pink telling us that Host Spanning must be disabled in order for the host to enter standby or maintenance mode. Unpreparing the host will also accomplish the goal of removing the service VM but this is much more drastic and should only be done if no other Lab Manager VMs are running on the host:

After reconfiguring the Lab Manager 4 host as described above, vSphere Client Recent Tasks shows the service VM is powered off and then removed by the Lab Manager service account:

At this time, invoke the maintenance mode request and the host will now be able to migrate all VMs off and successfully enter maintenance mode.

While Lab Manager 4 Host Spanning is a step in the right direction for more flexible load distribution across hosts in a Lab Manager 4 cluster, I find the process for entering maintenance mode counter intuitive, cumbersome, and at the beginning when I didn’t know what was going on, frustrating. Unsuccessful maintenance mode attempts have always been somewhat mysterious in the past because vCenter Server doesn’t give us much information to pinpoint the problem as far as what’s preventing the maintenance mode. This situation now adds another element to the complexity. VMware should have enough intelligence to disable Host Spanning for us in the event of a maintenance mode request, or at the very least, tell us to shut it off since it is conveniently and secretly enabled by default during host preparation. Of course, all of this information is available in the Lab Manager documentation, but who reads that, right? :)

Lab Manager Customization

August 1st, 2009

Although VMware does not support much along the lines of Lab Manager web interface customization, feature requests from VMware Partners and end users are likely to see the light of day in future versions as discussed in this thread by VMware employee Steve Kishi.

Through the examples of Hany Michael over at Hypervisor.com, there are a few changes that can be made that I think are pretty safe. I noticed in Hany’s Lab Manager 4 video (located at the link above), he had modified Lab Manager branding in a few places by dropping in his own artwork. Rather than modifying the web interface code, he merely located the image files and replaced them with his own.

At the login screen,

VMware’s generic Lab Manager branding:

8-1-2009 9-42-25 AM

Becomes Hany’s own creation by replacing the .gif file at C:\Program Files\VMware\VMware vCenter Lab Manager\WebSrvr\Resources\Default\Images\Login\Login.gif:

8-1-2009 9-40-05 AM

Once inside,

The logo in upper left corner:

8-1-2009 9-42-57 AM

Is replaced by Hany’s brand by modifying the .gif file at C:\Program Files\VMware\VMware vCenter Lab Manager\WebSrvr\Resources\LM\Images\LeftNav\logo.gif

8-1-2009 9-40-58 AM

In Lab Manager 3, we can add a MOTD or splash screen message for end users or developers by modifying the image at C:\Program Files\VMware\VMware Lab Manager\WebSrvr\Resources\LM\Images\Common\login_back.gif:

8-1-2009 10-20-26 AM

Look for MOTD and branding features, as well as others mentioned in the thread above, to be implemented in future versions of Lab Manager.

Lab Manager “Valid NIC Requirement” prerequisite check fails

May 17th, 2009

If you’re installing Lab Manager 3.x and the Valid NIC Requirement prerequisite check fails, verify your Lab Manager server has a static IP address configuration and not a configuration that is assigned by DHCP.

For other Lab Manager requirements, be sure to check out the Installation and Upgrade Guide.

5-17-2009 12-32-11 PM

Lab Manager Network Port Requirements

May 13th, 2009

I need to become a VMware Lab Manager expert and so it begins.  From what I’ve seen so far, Lab Manager 3.x has made great progress since I last kicked the tires 15 months ago on Lab Manager 2.x.  The biggest news by far is that ESX hosts can be managed both by Lab Manager Server and vCenter Server with all the fixins (DRS, HA, VMotion).  Although I’ve already found that VMs connected to an internal only vSwitch remain pinned to the host due to VMotion rules.

Nothing too Earth shattering here; this information comes straight from page 20 of the Lab Manager Installation and Upgrade Guide.

Systems TCP Port UDP Port
Client browser to access Lab Manager Server system 443
Client browser to access ESX hosts 902, 903
Lab Manager Server system and ESX hosts to access SMB share

(import and export operations only)

139, 445 137, 138
ESX hosts to access NFS media datastores or NFS virtual machine datastores 2049
Lab Manager Server system to access Lab Manager agent on ESX hosts 5212
Lab Manager Server system to access ESX host agent on ESX hosts 443
Lab Manager Server system to access the VirtualCenter Server system 443
Lab Manager Server system to communicate with virtual router on some ESX hosts

(for fenced configurations)

514
Lab Manager Server system to access LDAP Server 389 LDAP

636 LDAPS

Before the installation of Lab Manager, be sure that ports above won’t conflict with an existing configuration by running the netstat -b command from the Windows command line.

VMware product name changes

December 3rd, 2008

Quick update on a news item you may have already heard about. Remember those VMware product/component decoder rings you might have started working on after the VMworld 2008 announcements? It’s time for an update. VMware announced a handful of product name changes on Monday:

  1. VMware VirtualCenter is now VMware vCenter Server
  2. VMware vCenter is the family name for all management products
  3. VMware Lab Manager is now VMware vCenter Lab Manager (since it is in the management products family)
  4. The VMware vCenter prefix applies to the other products in the management products family as well
  5. VMware View is the family name for all VDI/VDM products
  6. VMware VDI is now VMware View
  7. VMware VDM is now VMware View Manager

I’m not real fond of name changes unless there is a good reason behind it. I’ll give VMware the benefit of the doubt that there was good reason to make these changes, although not knowing myself 100% what is up VMware’s sleeve, the timing is somewhat debatable. Couldn’t they have waited until the next generation of Virtual Infrastructure to align the products and components? Citrix did this with Presentation Server when they instantly re-branded it to XenApp. It confused a lot of people, especially the newcomers. I hope confusion among VMware customers is minimized. It’s going to take a little while for these new names to become second nature for me.

What do you think of the name changes? Feedback is always welcomed here.