Category Archives: VMware

VCAP exams on vSphere 5 – worth waiting for?

At the London VMUG yesterday there was a presentation about VMware certification by Scott Vessey, a well known VMware trainer (@vmtraining or http://vmwaretraining.blogspot.com/). After his presentation one question raised was whether it’s worth taking the vSphere 4 track or maybe delaying a while and jumping straight to the upcoming vSphere 5 track. Scott said this was a common question so I thought I’d add my thoughts on why I wouldn’t wait;

  • vSphere 5 (as it’s commonly known but not it’s final name) is slated for release around July/August this year (according to this article from the recent VMware Partner Exchange).  Even assuming they hit this deadline that means waiting another six months. Once the next version is released it’ll take a while for the exams to be updated, especially in the case of the VCAP-DCA track which requires live labs. vSphere 4 was released in May 2009 but the VCP exams took another 3 months to be released after that. Allowing a bit longer for the VCAP tracks, let’s say 4 months. That makes it a ten month wait from today.
  • Are you prepared to take the exams without help or study guides from the blogosphere, Twitter, and the experience of those who’ve gone before? If you know your stuff and are happy to be among the first then you’ve probably already taken the VCAP exams so waiting isn’t an option! If you find other’s experiences and suggestions helpful then you’re talking an extra three to six months for that to filter down.
  • If you’re not on the vSphere 5 beta you can’t start learning the new features until July/August at the earliest, compared to vSphere 4 which is available today, is widely adopted and documented.
  • Traction/demand from employers. This argument depends on why you ‘re after certification – if it’s to progress your career then bear in mind that while recruiters will add any new certification to their wanted (or mandatory) list almost immediately it takes longer for the value of a given certification to be respected (or not) in the marketplace. Back in the day the Microsoft MCSE had a good reputation to start with which quickly became tarnished. The RHCE took a few years to establish itself as a tough certification worth asking for and the VCAP-DCA may be the same. If you’re doing it for the technical challenge then this is obviously irrelevant.
  • How different will the VCAP-DCA on vSphere 5 really be? I know of many IT pros who skipped the MCSE 2003 track because if you already had the MCSE2000 that was fine – having the 2003 wasn’t really going to open up new jobs to you. You could wait for the VCAP-DCA on vSphere 5 to find that the two are treated interchangeably in the market and you simply waited longer to qualify.

For all these reasons I’m not going to wait. Whether I actually find time to take the exams before they release v5 is another question but my intention is clear!

There are plenty of people planning on taking the VCAP exams – what do you all think?

VCAP-DCA Study notes – 4.4 vCentre Server Heartbeat

If you work your way through the vCSHB Reference Guide you’ll have covered every objective in the VCAP-DCA blueprint, so that’s where I’d recommend you start. If you have time, view the VMworld sessions for a bit of background and reinforcement. I went into a bit more detail on this objective as it’s something I wanted to evaluate for my company, so there’s some ‘real world’ issues covered which I doubt you’ll need for the exam.

Knowledge
  • Identify the five protection levels for vCenter Server Heartbeat
  • Identify the three server protection options for vCenter Server Heartbeat
  • Identify supported cloning options
Skills and Abilities
  • Install and configure vCenter Server Heartbeat
  • Determine use cases for and execute a manual switchover
  • Recover from a failover
  • Monitor vCenter Server Heartbeat and communication status
  • Configure heartbeat settings
  • Configure shutdown options
  • Configure application protection
  • Add/Edit Services
  • Add/Edit Tasks
  • Edit/Test Rules
  • Install/Edit Plug?ins
  • Add/Remove Inclusion/Exclusion Filters
  • Perform Full System and Full Registry checks
  • Configure/Test Alerts
  • Troubleshoot common vCenter Server Heartbeat error conditions
Tools & learning resources

Continue reading VCAP-DCA Study notes – 4.4 vCentre Server Heartbeat

VCAP-DCA study notes–4.1 Complex HA solutions

HA basics

Requirements;

  • shared storage
  • Common networks
  • Ideally similar (or identical) hardware for each host

A good way to check that all hosts have access to the same networks and datastores is to use the ‘Maps’ feature. Select your cluster then deselect every option except ‘Host to Network’ or ‘Host to Datastore;

Maps help determine cluster validity

As you can see in this diagram the ’15 VLAN’ portgroup is not presented to every host (it’s slightly removed from the circle) and at least one VM in the cluster has a network assigned (in the top right) which isn’t available in this cluster at all.

Clusters consist of up to 32 hosts. The first five hosts in a cluster will be primaries, the rest secondaries. You can’t set a host to primary or secondary using the VI client, but you can using the AAM CLI (not supported, see how in this Yellow bricks article). One of the primaries will be the ‘active primary’ which collates resource information and places VMs after a failover event.

Heartbeat options and dependencies

Heartbeats are used to determine whether a host is still operational

Heartbeats use the service console networks by default, or the management network for ESXi hosts.

They’re sent every second by default. Can be amended using das.failuredetectioninterval

Primaries send heartbeats to both other primaries and secondaries, secondaries only send to primaries.

After no heartbeats have been received for 13 seconds the host will ping its isolation address.

HA operates even when vCentre is down (the AAM agent talks directly from host to host), although vCentre is required when first enabling HA on a cluster.

Diagnosing issues with heartbeats – see VMware KB1010991

Continue reading VCAP-DCA study notes–4.1 Complex HA solutions

VCAP-DCA Study notes–9.2 Plan and execute scripted ESX builds

The blueprint for this section seems to refer mainly to ESX but I’ve described both ESX and ESXi on the assumption the lab environment used for the exams will move to v4.1 sooner rather than later.

NOTE: Weasel is VMware’s scripted installer. It’s similar to Kickstart as used with Linux, but not identical.

A summary for a scripted install;

  • Decide on the bootloader source
  • Configure a media repository to hold your source files and scripts
  • Create an install script (either from scratch or from a previously built host)
  • Perform the scripted install

Use cases for scripted installations

Reasons to use a scripted install;

  • Reduce deployment time
  • Ensure consistency, reduce human error
  • Remove need for local media (when using PXE boot. Very useful for blade and remote environments)
  • Delegate installations to junior staff who don’t know how to configure ESX

Along with knowing why you might use a scripted install in the first place you should consider the various types of scripted install and when to use each one. Factors to consider;

  • Maintainability. Over time you’ll want to update your install for new releases of ESX, patches, post install steps etc. While a custom CD has the least dependencies it’s harder to maintain compared to a network media repository.
  • Dependencies. I created an NFS based install only to find that most of the time the host’s physical networking hasn’t been completed when we want to build the OS, rendering this method useless. I had to convert it to a custom CD instead which was mounted via ILO (it was a blade environment). Another example is USB flash – it’s easier than CD to amend/update but may not be as useful for remote installs.
  • Continue reading VCAP-DCA Study notes–9.2 Plan and execute scripted ESX builds

VCAP-DCA Study notes – 9.1 Installing ESX with custom settings

While the blueprint only refers to installing ESX (not ESXi) I’ve covered both in anticipation of the VCAP-DCA labs going to 4.1.

When to use a customised installation

There are plenty of reasons to use some advanced installations;

  • Your hardware isn’t supported in the ‘out of the box’ setup so you need custom drivers
  • You want to streamline the deployment process by building a custom install CD, including some post configuration steps, or utilising PXE boot etc
  • You want to gain maximum performance from every host, which means performance and configuration tweaks (vmKernel parameters, service console memory settings etc)

Installing ESX/ESXi

  • Interactive installations can be done via the GUI or text mode.
  • The installer can be located on CD/DVD, USB flash or via a PXE boot. While PXE is typically used for scripted builds it can be used as a source of installation files for an interactive build.
  • Scripted methods (PXE boot using HTTP, FTP, NFS are covered in section 9.2.
    NOTE: Scripted installs of ESXi were only added to v4.1 – prior to that only ESX classic could be scripted.
  • To install a virtual ESX host on ESX (for lab testing) you need some specific configuration tweaks – see the article at vCritical for full details.
  • For 64 bit guests you must have a 64 bit chip with Intel-VT support enabled or an AMD chip of revision E or later. Wikipaedia has details and you can check using VMware’s CPU Identification Utility. You cannot run nested 64 bit VMs.
  • Boot from SAN is now supported for ESXi (4.1 onwards). This includes iSCSI and FCoE for a limited set of supported adapters.
  • Both ESX and ESXi v4.0 will erase all local partitions by default, including existing ESX installs and VMFS partitions (if you’re upgrading an older ESX version for example).

Continue reading VCAP-DCA Study notes – 9.1 Installing ESX with custom settings