Archive | General

This is the second of two part articles on Max Daneri’s PXE Manager.  The first article can be found by clicking here. In this article I will explain how to configure PXE Manager to boot stateless ESXi hosts.  This is a very simple process, but saves lots of time and effort when deploying hosts that have no local storage. Step1: Login to vCenter and open the PXE Manager plug-in Step2: Accept the certificate warning if prompted Step3: Select Repository and Stateless build Step4: Right click and select Add Build Step5: Select the build zip file containing the ESXi build Note: This is not an .ISO.  This is the depot.zip file that contains all the latest build and patches. This can be downloaded from VMware.com Step6: Once the file is located click Next The files are extracted from the Zip file Step7: Confirm the details are correct and click next Step8: […]

One of my colleagues in the cloud team has written a “VMware Fling” called PXE Manager for vCenter which can be found by clicking here This is one of the best plug-ins to accompany vCenter for a long time (IMHO). This blog article is part 1 of a two part series to explain how to install and configure PXE Manager.  In part 2 I will explain how to deploy stateless ESXi (4.1 Update) hosts. Note: Before beginning the installation please make sure you have read all the pre-requisites required for this application Step1: Run vgpxe-x64.exe to begin the application installation Step2: You will be prompted to run the application Step3: If you havent already you will be prompted to install .NET Framework version 3.5 Step4: Once all pre-reqs are in place, click Next to start the installation Step5: Click Next Step6: Confirm the license agreement and click Next Step7: Select […]

Voting is now closed for VMworld 2011. Please vote for my session #1264 titled “Private vCloud Architecture Technical Deep dive”. This presentation won an award at PEX 2011, and I hope that people will give me the opportunity to present this again. http://www.vmworld.com/index.jspa Session Abstract Enterprises globally are enthusiastically embracing Cloud Computing as both a way of reducing costs and improving the quality of service IT provides to its end customers. To achieve this, enterprises are looking to VMware and its partners to help them deploy VMware vCloud Director-based Private Cloud environments. For a VMware vCloud Director-based Private Cloud to be successful and operationally sustainable, an absolutely critical first step is developing a solid vCloud architecture. This session will help partners address this critical first step by exploring the proven, practical activities and considerations VMware has defined, based on experience, for developing a vCloud architecture. A participant in this session […]

For anyone out there still using ESX(i) 3.5 you will need to apply a specific patch to your hosts to be able to continue updating these after June 2011.  This patch updates a secure key which will allow future patches to be applied. Follow the links below to the VMware KB articles for further information. KB: 1030001 Critical Impact: VMware ESX 3.5, Patch ESX350-201012410-BG: Apply this patch to continue applying patches on ESX 3.5 hosts after June 2011 has been written for users of ESX. KB: 1030002 Critical Impact: VMware ESXi 3.5, Patch ESXe350-201012401-I-BG: Apply this patch to continue applying patches on ESXi 3.5 hosts after June 2011 has been written for users of ESXi.

A few people have been talking about this lately, and what it actually means. Within the vSphere 4.1 U1 release notes the following statement has been made: Memory problems occur when a host uses more than 1016 dvPorts on a vDS * Although the maximum number of allowed dvPorts per host on vDS is 4096, memory problems can start occurring when the number of dvPorts for a host approaches 1016. When this occurs, you cannot add virtual machines or virtual adapters to the vDS. Workaround: Configure a maximum of 1016 dvPorts per host on a vDS. So what does this mean exactly? If a portgroup is created with 2000 dvPorts, how would this be created on a host? Would it create 2000 dvPorts for every host in the vDS?  The Answer is NO.  A host will only have the maximum number of configured proxy ports, which by default is 256.  […]