It’s been a while since I’ve worked with VMware to any serious nature but for the last two weeks, I’ve been working with a customer to deploy vSphere 5.5 on a new Dell Vrtx chassis. I’ve seen the Dell Vrtx on display at VMUG conferences gone by and it sure is an interesting proposition but this is the first time I’ve had a chance to work with it real world.
All in all, the Dell Vrtx is a really nice system, everything seems to be well planned and thought out. The web interface for managing the chassis works but it is slow at times to open pages and refresh information, bearable. The remote KVM console to the blades themselves is Java based so results may vary whether it works or not; I really dislike Java based systems and wish more vendors would start to use HTML5 for their interfaces. There is an apparent lack of information on the Dell Website about the Vrtx system. There is a wealth of configuration guides and best practice documents for the Vrtx but all of these seem be so highly pitched that they lack actual technical details. Another issue is the Dell parts catalogue doesn’t really acknowledge the existance of the Vrtx system; I was talking to someone about extending the system with some Fibre Channel HBAs for FC storage connectivity but of all of the FC HBAs for sale on the Dell website, only a single port 4Gbps HBA is listed as supported which I can’t believe for one minute given the PCIe slots in the Vrtx are, well, PCIe slots. Disk performance on the Shared PERC controller is pretty impressive but networking needs to be taken with caution. If you are using the PowerEdge M620 half-height blade, it only exposes two 1GbE Ethernet interfaces to the internal switch plane on the chassis whereas the full height PowerEdge M520 blade exposes four 1GbE Ethernet interfaces and I would have really liked to have seen all four interfaces on the half-height blade, especially when building virtualization solutions with VMware vSphere or Microsoft Windows Server Hyper-V.
I haven’t really worked with VMware too much since vSphere 5.0 and working with vSphere 5.5, not an awful lot has changed. After talking with the customer in question, we opted to deploy the vCenter Server Appliance (vCSA). vCSA in previous releases of vSphere was a bit lacklustre in it’s configuration maximums but in 5.5, this has been addressed and it can now be used as a serious alternative to a Windows Server running vCenter. The OVA virtual appliance is 1.8GB on disk and deploys really quickly, and the setup is fast and simple. vSphere Update Manager (VUM) isn’t supported under Linux or on the vCSA so you do still need to run a Windows Server for VUM but as not everyone opts to deploy VUM, that’s not a big deal really. What I would say to the vCSA though is if you plan to use local authentication and not the VMware SSO service with Active Directory integration then I would still consider the Windows Server. Reason for this being that with the vCSA, you cannot provision and manage new users and password via the vSphere Web Client and instead you have to SSH onto the appliance and manage the users from the VI CLI. With the Windows Server then we can obviously do this with the Users and Groups MMC Console which is much easier if you are of the Microsoft persuasion. If you are using the VMware SSO service and Active Directory integration then this will not be a problem for you though.
Keeping it on the VMware train, I’m looking forward to a day out to the VMware UK User Group Conference VMUG in Coventry in two weeks. I’ve been for the last three years and had a really good and informative day every time I’ve been.
Being so busy on the customer project and with my head buried in VMware, I’ve been really slow on the uptake of TechEd Europe news which bothers me but fear not, thanks to Channel 9, I’ve got a nice list of sessions to watch and enjoy from the comfort of my sofa but with there being so many sessions that I’m interested in, it’s going to take me a fair old chunk of time to plough through them.
It’s been over 18 months since I last sat an IT Pro exam of some description and frankly that was far, far too long. I should really have taken my TOGAF 9 exams last year as a minimum as the Architecting the Enterprise course I attended in London in May included the vouchers for the combined TOGAF exam, but it just never happened.
Today though, I finally broke the duck on my exam sitting and took my VMware Certified Professional 5 Datacenter Virtualization (VCP5-DV) exam and passed it. Maximum score for the exam is 500 and the minimum passing score is 300. I scored 380 which works out to be just shy of 80%. I wasn’t thrilled with the result, but I was happy to pass it first time round.
I got lots of questions on VMware FT which is probably my weakest area of the product after spending a lot of time researching iSCSI and NFS to square up on my existing Fibre Channel knowledge to cover all the storage topics. Although I’ve now passed the exam, I’m going to continue my research to try and brush up more of Fault Tolerance.
Next up? Well, my Cisco CCENT qualification expires in April this year, so I’ve got three months to pass my ICND2 exam to gain my CCNA or I lose the earlier CCENT and have to sit both exams again. Luckily, my networking knowledge has grown a lot since the first time I sat ICND2 and failed it about two and a half years ago, so I’m confident with some new research and studying into serial connections, IPv6 and a few other bits, I will be able to pass that exam.
Onwards and upwards…..
Yesterday, I had the chance to stand up a VMware Data Protection (VDP) appliance virtual machine. This is the replacement for VDR in vSphere 5.0 and upwards and is based on the EMC Avamar product.
When configuring the VDP appliance for the first time using the https://hostname:9543/vdp-configure URL, you are asked for credentials to connect to vCenter. The interface tells you that this is used to register with vCenter, but what it doesn’t tell you is that this account is actually then used for on-going access to vCenter and creating and deleting the snapshots on the VMs it is backing up. Therefore, make sure you use a service account and not your own account.
There is also a requirement for this account to be directly permissioned in vCenter and not via a nested group membership, so make sure you do this before attempting the registration.
Having just finished the course for vSphere 4.1 today, it’s going to be all hands on deck revising this stuff for VCP for the next week or so. Here is a list of useful links for vShpere and ESX/ESXi related knowledge which will liekyl help others along with myself in my quest to obtain VCP.
I will be updating this list on an on-going basis with all of the resources I come across.
Lastly, I cannot and will not vouch for any of these sites. These are merely just sites I have found to be useful for me.
As the title suggests, its a busy week this week all round. On Monday, I started the five day journey on the road to VCP while I attend the VMware vSphere 4.1 course with Gloval Knowledge, and with VMware currently running their own version of Microsoft Second Shot, hopefully I can have a chance if sitting the exam soon.
The wife, Nicky, Sat her final exam for her foundation course, Access to Higher Education for Midwifery, which means she now has the nervous wait to find out her final graded.
Me personally, I went to the doctors yesterday about my ongoing knee problems post-running and have now been referred to a physiotherapist for possible treatment.
As I write all this from my Windows Phone WordPress application, sitting in the car while Nicky runs into Tesco, we are about to go out for dinner with the girls to celebrate Layla’s birthday with another family, Gary and Amy and Joe’s birthday too.
VirtualBox looks to be the first on the top of the virtualization pile with this one:
VirtualBox 3.0 Beta 1 has added Direct3D and OpenGL 2.0 support to their virtualization product, which means that those Windows Vista and Windows 7 virtual machines will finally be able to enjoy the Windows Aero UI that they so deserve.
For me, I think this could be a real driver for VDI (Virtual Desktop Infrastructure) as I think that main hold-back up until now has been the visual appearance of VDI (or rather the lack of).
I was rather hoping Microsoft could have managed Direct3D in Server 2008 R2 Hyper-V or Hyper-V Server R2 but obviously not as they use a graphics card much in common with VMware’s offering.
Hopefully this advance from VirtualBox will move them both along because we all know once one jumps the other will follow.
So I know that Windows 7 is Release Candidate now, but that doesn’t mean people don’t still want to install Windows Vista, and what a better time to rebuild your Vista box if you don’t fancy the step to 7 than now?
I spent a few hours last night working on my Vista image on my WDS (Windows Deployment Server) and I’m really happy with it. I’ve never really meddled with the Vista DVD much in the past because I got confused by the Windows Image format and how to service it initially but once you get your head round it, it’s really easy.
I’ve now got a Vista DVD with the following integrated:
- Service Pack 2 RTM
- Internet Explorer 8 RTM
- Remote Server Administration Tools
If your using VMware on a laptop or a monitor which is widescreen you’ll probably realize by now that VMware doesn’t like you much because the video driver it installs is a SVGA driver and you can’t configure that, however I found out today you can configure the GPU RAM size and the resolution it uses.
To force this enter the following additional lines into your VMX file. If you don’t know how to edit VMX files, then open the file with Notepad and all will become clear.
svga.maxHeight = 900
svga.maxWidth = 1440
mks.enable3d = “TRUE”
svga.vramSize = “134217728”
The maxHeight and maxWidth lines specify the resolution whilst mks.enable3d although I can’t confirm if this line does anything is supposed to improve performance for Direct3D.
Finally, the vramSize value specifies the GPU RAM size that will be displayed to the guest OS. 134217728 represent 128MB Ã¢â‚¬â€œ The value is in bytes (Divide by 1024 twice to get Megabytes).