VCDX: VMware Certified Design Expert
VCDX is not a follow on from VCP and is not currently a VAC or Partner program requirement, this should be seen as an advanced Certification and is only applicable to architects who have designed and deployed enterprise environments. The Enterprise Exam is available this month. Candidates can check their skills and assess their suitability for this exam online via our Certification page : http://mylearn1.vmware.com/portals/certification/ Only those who meet these qualifications will be able to attend the exams. The Design exam is now in Beta development. We expect design submissions and presentations will begin in Q308.
The BluePrint is available now, use as a tick list… all 16 pages of it. 🙂
Here’s a summary of what I know about the VCDX over the last few days….
To attain the VCDX, one needs to achieve…
2. Pass the Enterprise Exam
3. Pass the Design Exam
4. Successfully pass a grilling by your peers, most likely chaps from VMware PSO on a design and implementation plan.
Now, according to my sources, the official preparation, and non-compulsory, for the Enterprise Exam is the DSA Course:
VI3: DSA v3.5
Duration 4 days
RRP £2095 p/p
It’s upto you to decide if you really need to go on the course to pass, so a read of the blueprint will probably give you a guide as to the level that you are at.
The official preparation for the Design Exam, also non compulsory are two new, unreleased courses from VMware, the first is aptly named Design Patterns (release Q3/Q4) and the second course is an unknown at the moment.
IBM came back with a workaround to my problem,….All workarounds have been tested and work.
The workarounds then for anyone running ESX 3.5 Build 64607 on HS21 XM 7995 v1.08 with 2 x quad core CPUs:
1. Use ESXi instead (No service console, hence no PSOD. Also no mouse services in the console needed, hence no PSOD (this is the problem that I was experiencing).
2. Use ESX 3.5 Up 1 Build 82663 (Stable as of 18th April – double check your checksums!)
3. Use ESX 3.5 build 64607 but disable the gpm module, do this by entering the following on the Service Console:
chkconfig gpm off
then reboot the host, obviously you will get a PSOD but reset it and all should be well thereafter.
This is a bit of an issue. I’ve just test installed ESX 3.5 onto a HS21 XM (7995) blade BIOS v 1.07, everything is fine and the server boots fine and runs stable but everytime I reboot from the console or restart using VI-Client I get a purple screen of death.
Now I know that there is an issue with quad-core Xeons and HS21 blades, but wasn’t this fixed with the latest BIOS versions? I believe it was fixed with BIOS 1.06 on the normal HS21 but was this same fix applied to HS21 XM (7995) v 1.07?
IBM and VMware support tickets have been opened, but any working fixes out there?
It was used in “Fundamentals of Disaster Recovery in Virtualized Environments” VMware World Partner Day 2007.
In the previous post I covered the network design for a HS21 with 4 network interfaces. This post will continue with a diagrammatic representation of the interface table.
As described previously, this configuration provides full network fault tolerance on all levels: adapter, port, CAT5, switch bay and core switch.
I’m waiting for the customer to decide on whether to include the CFFv daughtercard in this phase of the project, and will update this post with the new design if required.
Next up, environmentals…
Those of you familiar with the HP c-Class blades will probably know that there is a superb tool called the HP BladeSystem PowerSizer 2.9, I’ve been trying to find an equivalent from IBM, but as yet have not found anything that comes as close. (Any pointers will be appreciated)
Instead I’ve had to resort to using data obtained from The Edison Group study titled Blade Server Power Study – IBM BladeCenter and HP BladeSystem, Nov 7 2007, document titled “BLL03002USEN.pdf“.
The results show, in summary a BladeCenter H chassis with 14 blades on full load will need 14,352.51 BTU/Hr with a peak power consumption of 4,208.80 Watts. Most modern datacenters with good power feeds will be able to accommodate that kind of load. Cooling requirements will be left to the customer to calculate.
Additionally, this single chassis will require 9 rack units and 4 power feeds due to the additional 2900W power supply modules.
Part 2…. Continued..
Thank you Aaron for your help with the power sizer.
Here is the output from the tool (not as nice as HP’s offerring by the way)
In the next part… network design for the x3650.
Well here I am, starting a new project for a new customer at a new datacenter again. This time, its a large retail organisation looking to do the usual, consolidate, virtualise, go green etc etc. They have selected IBM System X and BladeCenter H as the platforms of choice for the new VMware ESX 3 environment. So here we go with the planning….
The BladeCenter H has eight switch bays and two Advanced Management Module (AMM) bays. The two AMM act in much the same way as the Onboard Administrator on HP C Class. There are two for redundancy. Two of the eight switch bays are used for FC Switches, for this project we are using Brocade 4Gb SAN switches.
The other bays are occupied by Cisco GbE Switch Modules.
HS21s are used for the initial phase of the project. These blades can accommodate upto 6 NICs and 2 HBAs, with 2 onboard and the other 4 provided by daughtercards. The customer has elected to use 4 NICs as opposed to the 6 that I normally recommend for ESX implementations. The two extra NICs are provided by the CFFh daughtercard, this daughtercard houses 2 network adapters AND 2 Fibre Channel HBAs.
The table below (from IBM) show the interface to bay mapping.
I will be teaming Interface 0 (eth0) with Interface 3 (eth3) as opposed to the IBM table (dedicating an adapter to a service), as this will team one onboard port with one daughtercard port. Likewise eth1 will then be teamed with eth2.
* The location of the two Fibre Channel Adapters should be Daughter Card CFF-h, not v as shown in the IBM table.
The following diagram shows the correct mapping.
The table below details the network interconnects.
Interface is the network adapter inside a blade, Location is where the interface is, Chassis Bay is where the interface terminates at the rear of the BladeCenter chassis, pSwitch is the external core switch that the Chassis Bay uplinks to, vSwitch is the ESX virtual switch that the Interface provides an uplink for, vLAN is the ID that is assigned to each Port Group and Service is the type of port group assigned to a vSwitch.
Disabling the VMware DHCP Service on the Host Computer.
It is easy enough to do this on Windows hosts, this article focuses on Linux hosts.
Follow the steps shown below for your host operating system.
Linux for Workstation 5.x and VMware Server 1.x
Linux for Workstation 6
Occasionally you may want to check the state of a virtual machine, to check whether it is running or not. On the very few times that VMotion failed for one reason or another, a VM will fail to resume on the source host or start on the destination host.
From the Service Console you can check the state of running machines by typing vmware-cmd //server.vmx getstate. You can also kill the VM if it is truly in a hung state by using the procedure below.
After performing a P2V always remove the hidden physical hardware from the OS. This is particularly important for network cards that have the original IP address(es) that you want to assisgn to the new VM.
1. Click Start | Run | cmd
2. At a command prompt, type the following command , and then press ENTER:
3. Type the following command in the same command prompt window, and then press ENTER:
4. Click Show hidden devices on the View menu in Device Managers before you can see devices that are not connected to the computer.
To sync your ESX Server with an external NTP server, do the following at the ESX Server console… Basically you can do the following (replace with the IP Address of an NTP Server.)
Modify the /etc/ntp.conf file as follows:
Under the “# — OUR TIMESERVERS —–“ section create two lines as follows:
restrict mask 255.255.255.255 nomodify notrap noquery
Modify the /etc/ntp/step-tickers file and add your NTP Servers, each on their own line, to the file.
Enable the appropriate NTP client ports on the firewall.
/usr/sbin/esxcfg-firewall –enableService ntpClient
Restart the vmware-hostd process.
/sbin/service mgmt-vmware restart
To synchronize the system’s time with the NTP server
To enable the ntp daemon to autostart when the server is rebooted
/sbin/chkconfig –level 345 ntpd on
Start NTP daemon
/sbin/service ntpd start
Set the local hardware clock to the NTP synchronized local system time
Ensure the time is accurate