Check out my interview with Nicci Fagan here:
A backup administrator’s job is like that of a pilot—hours and hours of utter boredom, followed by moments of sheer adrenaline. Let’s face it. We all know that backup isn’t sexy – but it’s absolutely necessary. In some cases, it’s the last line of defense from ever-increasing malware, ransomware and just plain human error.
The most significant part of VMware PEX, for me this year, was the Solutions Exchange floor and the rather small number of vendors. My focus was on convergence of compute and storage resources. This appears to be a popular path. There were a few things along the way, other than cheap swag, that caught my eye. One interesting conversation involved FusionIO. They validated that many customers concentrate more on storage space instead of performance and that this is not good. Some more progressive enterprises are very focused on performance. For instance, eBay actually measures costs based on url per kilowatt.
I have been attending various VMware Partner Exchange (PEX) and VMworld events since around 1996. Typically, I prefer to attend PEX over VMworld. The number of attendees is significantly smaller and access to the VMware brain trust is easier. There is usually a good mix of NDA roadmaps and decent technical information. The Solutions Exchange floor is less crowded and the vendors are able to spend more time with you. The hands on labs are the same top-quality as VMworld, but typically with no lines.
I did not attend VMworld 2013, but I did attend PEX 2014 last week. Sadly, I was a little bit underwhelmed again this year, as I was last year too. There was no real feeling of innovation. No buzz. Just ho-hum. There seemed to be fewer exhibitors on the Solutions Exchange floor as compared to previous years. I did have some very educational conversations with some vendors that I will detail later.
Despite all of the drama around Veeam and Nutanix being missing in action, there was no mention of VMTurbo. The people at the Cisco booth had nothing about Whiptail or Insieme.
The push is bundled suites of software, which will offer a single management point and a common interface. But many parts of these suites will likely end up as shelf-ware to many. Let’s face it, many enterprises will need to change significantly in order to fully utilize the vCloud suite. If it is not a top down directive, either the networking silo or storage silo is going to protest over lack of control. Try explaining to network engineers that you need a pool of VLANs and associated IP addresses that will be out of their control and probably will be difficult to integrate with the many manual processes that are used. Try telling a storage administrator that we can now do self-service provisioning of a storage array, including all of the parts in the middle, like zoning and masking. Like VDI, they see that ROI is heavy on “soft costs.” Try explaining how you save on labor costs without reducing workforce in this economy where IT shops are already understaffed. Many people don’t get it when it comes to Cloud, which suddenly became Software Defined Data Center (SDDC) and now Software Defined Enterprise (SDE). But that can be the subject of a future post.
There was a little video before the keynote on Tuesday morning that hammered it home. Think about VMware in its first ten years. No one “got” virtualization. But VMware persisted and stuck to its guns. Now it has become standard issue in a data center. VMware is taking the same approach to the Software Defined Data Center. They are even starting to call it Software Defined Enterprise instead. Their stance is that, with persistence, the SDDC message will be heard and will become the norm. There is a constant struggle between the people that deliver IT and the people that consume IT. The fundamental ideas of SDDC help calm that struggle.
Right now, Microsoft appears to be hot on the tail of VMware and I see many people seriously reconsidering their method of delivery. I think the biggest things that VMware has going for it right now are vCenter Operations Manager (vCOPS) and Site Recovery Manager (SRM). I think that SRM is possibly the only thing keeping some enterprises on VMware for business critical applications. VMware is trying to display an air of non concern. Possibly, they are ignoring the “Evil Empire.” When many enterprises are already paying for Windows Datacenter Edition and System Center, there needs to be justifications to keep vSphere. I see Hyper-V taking a foothold, especially in SMB and branch offices and in places where basic server virtualization is good enough.
It is interesting to see some of the visions play out over the course of time. I remember back in 2007 or 2008, when PEX was still Technical Solutions Exchange (TSX). I remember Carl Eishenbach (http://www.vmware.com/company/leadership/carl-eschenbach.html) announcing the VCDX program. I remember he said that there would be about 200 of us by the end of 2008. Back then, customers needed someone to design their greenfield environment and assist with migration from physical to virtual. I don’t find myself needing to prove that vMotion works any more. Although there are likely many greenfield opportunities out there, most of my design expertise is now spent assisting with creating higher consolidation ratios and helping customers deliver a more optimized datacenter that may not always have vSphere at the top of the list. I have seen VMware go from a stand alone hypervisor to centrally managed solution to the defacto standard then to what I describe as “meh.” There is no pop anymore. No excitement. Maybe I am getting too pessimistic in my old age.
Stay tooned! I have more to come on the interesting finds on the Solutions Exchange floor.
A few weeks ago, I had the privilege of returning to the customer that was the subject of my VCDX Design Defense.
First, let’s travel back into time. It was mid-December, 2008. I was a VMware Delivery Engineer for my company at the time. The customer engagement was a VMware Plan and Design delivery. I had the audacity to design a virtual datacenter running ESXi 3.5.0 Update 2 on HP BladeSyStem servers booting from USB sticks. The Virtual Center server was a VM. This was my fourth or fifth Plan and Design engagement with my company, so it was a piece of cake to me.
I’ve been meaning to write this post since May 2010! Never got around to it but I am starting to see and hear about it again. The costs of Windows Server systems become important if you are renewing licenses or you are in a consolidation project. I find that many businesses will purchase server hardware with a Windows OEM license. The problem with an OEM license is that it CANNOT be transferred to a different server. Some people find this out the hard way during P2V conversions.
Interesting that I stumbled on this right after I posted a How-To for the free vSphere Hypervisor.
Mike Adams over at VMware wants to know if you are using the free vSphere Hypervisor. If so, he would like you to complete a very short survey so he can understand how you are using it. Check out his post on the VMware blog.
One of the things that some of the Microsoft Hyper-V users tout is that Hyper-V is free. Sometimes, like in smaller offices or branch locations, it may even make sense to use Hyper-V where there are four or less VMs on a host. The Windows 2008 Server Enterprise Edition license will allow for the base Hyper-V installation and up to four Windows 2008 Server VMs on the hardware. But there are many valid reasons to run VMware’s vSphere Hypervisor, the free version of ESXi in your datacenter.
NOTE: This is no longer required in vCD 5.1 & above!
This is one of those situations where I really start to hate computers! I was working with vCloud Director with a goal of having a winders VM run through guest customization, change the name, get a fixed IP from the network pool, join an Active Directory Domain and move to a specific OU in the AD.
There is a spot in the VM properties to specify a domain to join. You can use the settings specified in the organization or enter the domain information directly.
This post includes an important security “gotcha” that I recently uncovered with vCloud Director 1.5 running on vSphere 5. If you are using vCloud Director, you should check your settings.
The BIG Security Issue
The PAVMUG session on Sept 22nd, 2011 that seemed to have the second most active audience was the session where I discussed vSphere 5 licensing and some of the design considerations. There were several good questions that I would like to re-address here and share some helpful links that I promised during the session. There is a great PowerCLI script and a tool that VMware themselves offer.
For the September 2011 PAVMUG all day meeting, I participated in four sessions. To me, the session with the most audience participation was about virtualizing business critical applications. My session really dug deep into Microsoft Exchange but also covered some basics around SQL and Oracle. I wanted to expand some of the ideas that were discussed during the session and post the presentation slides.
Welcome to Tech-Tap, where we adjust things with a ball peen hammer. Thanks for checking us out!
If you have ever wanted to give something a “technical tap” with a ball peen hammer, then you have come to the right place.
Below, please find archives of posts from my previous blogs. New posts are coming soon, so check back in or subscribe to our RSS feed.
I was doing some research for session I am presenting at an upcoming PAVMUG session about vSphere remote management when I came across an apology by one of the PowerGUI guys. Essentially, he was apologizing for something that VMware changed in the functionality of PowerCLI that affects how the PowerGUI Virtualization Powerpack interacts with it.
If you didn’t know it yet, VMware announced a while back that future releases of VMware will not include the “traditional” ESX Server. From their site:“VMware vSphere 4.1 and its subsequent update and patch releases are the last releases to include both ESX and ESXi hypervisor architectures. Future major releases of VMware vSphere will include only the ESXi architecture.”
If you are in a “24/7/365” shop then the applications running in your private cloud should currently be in virtual data centers (vDC) that are contained in DRS/HA clusters and the migration can be completed with no downtime to the applications. However, there are still other systems, such as development and test systems or possibly some minor infrastructure services applications that may not benefit from vSphere’s availability features. I know many people have scheduled outages, shutdowns, etc. during the upcoming holidays. It may the best time to migrate to ESXi…
A Little Bit About ESXi 4.1
I have actually been pushing ESXi since version 3.5. In every plan and design engagement where I have been involved, I have always started with ESXi as the version to be used unless there was a compelling reason NOT to use ESXi. I think the only thing right now that requires ESX is HP’s Matrix. I have yet to find anyone that uses that behemoth. There have been many improvements to the features of ESXi since version 4.0. VMware has a nice “Why ESXi” web page to explain these new features. The biggest thing is that ESXi has a smaller footprint and has fewer security updates needed than the “traditional” ESX Server. For instance, the latest round of patches has 11 for ESX and only two for ESXi. The small footprint allows ESXi to be installed on a USB stick, an SDHC or just on less disk space. There is also a nice VMware KB article explaining all of the differences between the current version of ESX and ESXi.
Here are some other things that I like about ESXi:
Treat the ESXi Server like it is an appliance
The ESXi installation should be treated as firmware. It is even called firmware in Update Manager. This means that there is no actual upgrade. The firmware is installed fresh every time. This also brings the idea of having stateless servers at some point in time. More on that later.
Really, there are three methods for a mass deployment. One is to use Host Profiles, but this requires manual steps and the extra costs associated with Enterprise Plus licenses. A second method is to install a base install of ESXi using the method I outlined in a previous post and then use PowerCLI or the vSphereCLI to customize the server. The new preferred method is good ‘ol Kickstart.
Several Boot Options
Now, you can boot from local disk, SAN Disk, a USB Key or an SDHC Card. One of the arguments some have against booting from USB or SDHC is the dreaded single point of failure (SPOF). My answer has always been that HA will cover this. And, if you think about it, an internal array controller is a SPOF as well. But, now you can boot from SAN if you wish. Just remember to create a space for logs and core dumps if you go the route of USB or SDHC.
Active Directory Integration
ESXi servers can now become members of a Micro$oft Active Directory Domain so that administrators can authenticate to the directory. Setting this up is done through the vSphere Client under the configuration tab. It appears that you can call the administrators group anything you want in AD as long as it is “ESX Admins”. Maybe that will change in future versions.
You can just do away with SNMP monitoring and use the Common Information Model (CIM) providers. The stock version comes with some basic CIM monitoring, but the major hardware companies provide custom baked versions of ESXi with OEM-specific CIM providers for more granular monitoring. Rather than setting up your monitoring software for SNMP, you just point it to the ESXi server and set it up for CIM or WBEM. If you are not using a monitoring server, you can use the vCenter server to handle alerts and alarms.
Enhanced Tech Support Mode and vCLI Operations
Using Tech Support Mode, formerly known as “Unsupported Mode,” is now supported. You can log in as an administrative user and all commands run in TSM are logged. The biggest reason many people went into TSM was to kill a stuck VM. There is now a vCLI operation that will allow this.
The Migration Path to ESXi
Here is the “Super Dave Method” for migrating to ESXi. Like I mentioned before, if you have at least ESX Clusters with vMotion enabled, this will be a relatively painless process, with no downtime. Obviously, if you are also upgrading from a previous version, there will be reboots required for VMware Tools and possibly to upgrade the VM Hardware to version 7.
TEST TEST TEST
Yeah, you heard me. Take some time to familiarize yourself with the differences between ESX and ESXI by setting up at least one test system so you can hammer it before changing your production systems. The nice thing is that you don’t need hardware to do this. You can set up a VM and run ESXi as a VM.
vMA, vCLI and PowerCLI – Oh My
If you are already familiar with doing things from the ESX console, the vCLI will be very familiar to you. If you are a Winders guy, you should already know PowersHell, so the PowerCLI will be familiar. Also, get to know the vSphere Management Appliance (vMA). The vMA is a RHEL5 based VM Appliance that is pre-configured with the Perl SDK and vCLI. It also includes vi-fastpass command, which allow you to pass authentication through to the hosts and to vCenter. It also includes vilogger, which allows you to create a (very) poor man’s syslog server. I think you are better served using Splunk! or phplogcon. Either will allow you to parse the syslog entries eisier if you need to do any troubleshooting or forensics. If you want a nice guide to the vMA, head over to the vGhetto for some nice tips and tricks. If you are already a Linux shop and RHEL is not your cup of tea, then you can bake your own vMA with the Perl SDK and vCLI, but you will lose the vi-fastpass and vilogger capabilites. vi-fastpass is not a huge loss and you can set up your home baked vMA to include syslogd and phplogcon.
Create a Kickstart Script
The most efficient way of performing an installation on more than one server is to script it. VMware now supports using Kickstart. Test your KickStart script on the test ESXi server, weather it is physical or virtual, you should be able to test most of the functionality. Check out the nifty “DryRun” setting too. I am not going to rehash what has already been done or said regarding Kickstart, so here are some decent links:
- The VMware ESXi Kickstart Documentation Page
- The VMware in SMB Blog
- The vGhetto
- Kendrick Coleman’s Guide
- vMA and AD Troubleshooting Guide
Take a look at this VMware Labs Fling if you want to create a nice deployment server that automates the ENTIRE process. This brings up the idea of having stateless ESXi servers. As each one is inserted into the vDC, ESXi is automatically set up for you. All the “important stuff” is stored on shared disk.
If you decide to go the route of using PowerCLI, take a look at this nice post.
Back up EVERYTHING!
Back up EVERYTHING! ‘Nuff said? There is no better feeling when the shit hits the fan than to have a good backup. Make sure you back up the vCenter database and capture the configuration settings of all of the ESX servers. If you have Enterprise Plus, capture a host profile for each server. Take screen shots of the configurations settings in the vSphere Client. Include networking and all of the tabs in the vSwitches. Include storage and all of the tabs of any iSCSI initiators. Don’t forget the IQNs! Check the advanced settings for any tweaks. Document the whole thing.
Pick the First Victim and Move Your VMs
If you are using DRS and HA, disable HA. Then place the first victim host in Maintenance Mode. This should automagically move the VMs to other hosts in the cluster if DRS is working. Or you can manually (*GASP*) vMotion your VMs. If they are on local storage, set up an iSCSI server – OpenFiler is free. You can then use Storage vMotion to move the VMs to the iSCSI storage.
Remove from inventory
Yep! If the server is a part of a cluster, remove it from the cluster. Before removing it from inventory, unassign the license. Then, remove it from inventory. Once it has been disassociated from the vCenter Server, shut it down.
Now is a good time to update the BIOS, device firmware, etc. Blow out the dust. Perform some hardware TLC. If you do not trust yourself, disconnect it from the SAN. If you are using software iSCSI initiators or NFS, no worries because you will need to reconfigure this stuff after the install.
Now is the time to actually perform your first ESXi installation. Go ahead, we’ll wait.
Once ESXi is installed, you can add it back to the vCenter Server, add the license and perform any post configuration steps like apply the host profile or run your PowersHell script for post configuration. Once the post configuration is completed, confirm that all of the settings are correct and match what you documented previously. If all is good, add it back to the original cluster. If you want to set up Enhanced vMotion Compatability (EVC) and it’s not currently set up in the original cluster, you can create a new cluster for the ESXi Servers with EVC enabled.
Repeat the process for each server. If you decided to create a new cluster, start moving VMs to the new cluster.
If you are installing ESXi to a USB Stick or an SDHC card:
- Make sure the stick or card is supported by the hardware manufacturer.
- Set up a syslog server. This is very important.
- If you don’t set up a syslog server, make sure you have a swap partition on the centralized storage. If you do not do this, the logs are deleted on reboot. Then set up a syslog server.
Make sure that during the test phase you understand how to set up authentication, syslog settings and nay required custom settings. Also make sure you know your way around the DCUI and the Tech Support Mode console.
Yesterday, I took the VCAP4-DCD beta exam (VDCD410), like many others have done this week. There is a thread started already in the communities forum. Just like previous beta exams with VMware, I had to take the exam at a Pearson-owned facility. There are a few within an hour of me, so I didn’t need to fly anywhere. It’s funny, Jason Boche mentions that he couldn’t take coffee into the testing center. The person at the facility where I took the exam said no food, drink, candy, etc. The center where I usually take exams is more laid back and are OK with coffee as long as there is a lid. In fact, they offer to sell you bottled water to take in with you. VMware only requires a finger print scan and a photo with the two forms of ID. I noticed some people were getting their hand vein patterns recorded. Crazy.
Passing the VCAP4-DCD exam is one of the requirements for anyone, including a VCDX3, to achieve the VCDX4 certification. So passing this exam is very important to me.
The beta exam was 131 questions/tasks with four hours to complete. (There was a guy before me that was taking a test that lasts 630 minutes!) I would think that some of these may get cast off as improper, too easy or too hard. If all of the questions prove to be OK, then VMware has a nice, fair pool of design questions. I would also think that the “GA” exam will only be a portion of these questions.
There are three types of questions or tasks: The standard multiple guess questions, a few “match the object to a category” drag and drop tasks and a few diagramming tasks.
Exam Content – What You Need to Know!
I am under countless NDAs on this, so there will be no “scoops” here. I can say that the exam is true to the Blueprint. Rather than giving a direct link to the PDF, which could change, I will tell you to go to www.vmware.com/go/vcap. Click on the “Datacenter Design” tab. There is a link to the current blueprint there. It was just changed to fix an issue with broken hyperlinks. There are also links to a FAQ, the VCAP Communities landing page and a link to a demo of the diagramming tool.
Make sure you read and understand all of the documents and web pages that are linked in the blueprint. VMware leaves no stone unturned. I would not advise trying to memorize all of the content listed in the blueprint, your head would explode. Just comprehend what you read. Much of this is conceptual and revolves around the methodology and best practices GUIDANCE that VMware chooses to publish.
Make sure you take a look at the VCAP4-DCD Exam UI Demo. This is the exam version of a Visio tool. One of my complaints about the VI3 Design Exam was the quality of the diagramming tool. It is greatly improved in this exam. In the VCAP4-DCD beta exam, there were more than one diagramming task. I don’t think VMware is looking for the Mona Lisa. This is more of a “show your work” kind of thing. The diagramming tasks are not that complex and will only cover a few design criteria in each task.
Since this is a DESIGN exam, there are plenty of scenarios that involve capacity planning. Since you will not have any tools available to do your work, you will need to understand the math involved in capacity planning. There is a simple calculator available via a link at the top of the screen. You will also need to understand the math involved with calculating HA, DRS, reservations, shares and limits.
Finally, with the beta, there was a time constraint. I think I had about 10 or 15 minutes left when I was done. Make sure you manage your time. There was no “back” button and there was no way to mark questions or tasks for review in the beta exam. This may or may not hold true for the “GA” exam. Remember: If there is no “back” button or way to mark a question, make sure you are OK with your answer before clicking the “next” button. I clicked it a few times as I was thinking “Maybe I should read that again….”
My Soapbox Moment
I don’t want to “toot my own horn” or sound arrogant here, but I purposely did not “study” for this exam. I did read the blueprint and skim some of the documents. The hyperlinks were broken in the 1.2 version and I didn’t try to find them too hard. I didn’t study for the VCAP4-DCA exam either (I passed by the skin of my teeth!). In my (humble) opinion, the exams require that you have EXPERIENCE in the subject of the exam. I don’t think VMware intends to have “paper VCAPs” although I am sure there will eventually be some out there.
If you want to pass the VCAP4-DCA exam, you should have experience managing a vSphere environment. If you want to pass the VCAP4-DCD exam, you should have experience in designing at least one vSphere environment. You need to go through the thought processes involved in the ASSESS – DESIGN – IMPLEMENT – MANAGE cycle. I am sure that the design workshop will assist you in gaining the knowledge and some experience in designing a vSphere environment, but it won’t give you everything you need for passing this exam. Certainly, if you want to progress to the final step and submit and defend a design, you will need EXPERIENCE. This is why there is such a high fail rate for the design defense.