Left to Right: VCP#1, VCP#2712
This is VMware history.
It has been a long wait but last night (and to my surprise) vSphere was finally released and from what I’ve seen so far, it was well worth the wait. Not that VI3 isn’t a great product, but the new features vSphere boasts are absolutely amazing. Whereas with VI3 VMware put any resemblance of competition to shame, vSphere totally and completely annihilates it.
With the vSphere NDA embargo lifted a while back for bloggers, there has already been plenty of coverage on most of the new features so I’m not going to go into each of them in great detail here. I’ll just touch on a few things that have caught my attention. There is plenty more to digest on other blogs and of course VMware’s site.
First of all, let me get this out of the way: By far the best and most complete collection of vSphere resources on the internet can be found at Eric Siebert’s vSphere-land site. If you can’t find what you’re looking for there, it doesn’t exist.
Now, a few of my favorite and notable observations thus far:
There are boatloads of new goodies in vSphere. It’s going to be around for a long time so take your time to learn it. No need to rush or be the first datacenter to run vSphere for bragging rights. Watch the blogs and the bookstores. There will be new vSphere content gushing from all angles for many months and even years to come. Be sure to share your findings with the VMware virtual community. Collaboration and networking makes us strong and successful.
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.
Introducing Hyper9 Virtualization Mobile ManagerTM Beta
Mobile Monitoring and Support
Hyper9 knows VI administrators. We understand their challenges, which is why we’ve removed so much complexity, risk and cost from virtualization management. But we also know about something else VI admin’s need – freedom. Freedom from the infrastructure. Freedom to leave at the end of the day without concern. Freedom to take lunch, or even a vacation, without looking back. It’s why we created Virtualization Mobile Manager (VMM).
What’s New in VMM?
VMM offers administrators remote monitoring and support – browser-based management that works on a wide variety of mobile devices. VMM now supports VMware, Xen and Hyper-V and useless features and complexity don’t bog down VMM. Affordable, easy to use, and workable even on simple cell phones.
Developed by virtualization infrastructure expert Andrew Kutz, VMM enables remote network control, extended scalability and multi-platform support, all within a mobile display designed for optimal efficiency. It’s all part of our commitment to providing VI administrators with the tools they need to work smarter and take action right away.
Take Me To My People Program
The VMM beta is available to the entire VI admin universe today – but as usual, true believers get something extra. The first 15 to sign up through boche.net will receive the following perks:
There’s no question that VMM is the ticket to higher intelligence for VI administrators.
Here are some of the details that just may make a believer out of you:
For more information, to join the beta and download the product, please see visit this link. Be sure to tell them boche.net – VMware Virtualization Evangelist sent you. Remember, only the first 15 to register are eligible for the Take Me To My People Program benefits.
If you’d prefer, you can send me your information via email (your name and email address) and I will connect you with a Hyper9 representative so that you may take advantage of this limited time offer.
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)
|Lab Manager Server system to access LDAP Server||389 LDAP
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.
I’ve been experimenting with vSphere’s memory hot add and CPU hot plug features to determine its usefulness with Windows Server operating systems. I came up with mixed results depending on the version and architecture of the OS.
A few notes about the results:
Here is the table of results I came up with:
|Windows Server 2003 STD x86|
|Windows Server 2003 STD x64|
|Windows Server 2003 ENT x86|
|Windows Server 2003 ENT x64|
|Windows Server 2008 STD x86||*|
|Windows Server 2008 STD x64||*||*|
|Windows Server 2008 ENT x86|
|Windows Server 2008 ENT x64||*|
|Windows Server 2008 DC x86|
|Windows Server 2008 DC x64|
|Windows Server 2008 R2 DC x64
(experimental support only)
|* Reboot of guest OS required to recognize added hardware|