Month: November 2013

8 weeks of #VCAP – Section 3 scenario – CPU Affinity!

Thanks once again to Tom Verhaeg for this great scenario. The voice team has recently setup Cisco Unity. The VoIP administrator sends you an e-mail. To comply with Cisco best practices, the Cisco Unity VM needs to have CPU affinity set. You really don’t like this, but the VoIP administrator and your boss insist. Make it happen…….. Damn, this really isn’t a fun thing to do. CPU affinity restricts a VM only to run on specific cores / processors that you specify. There may be some requirements for this (such as the above), but overall you shouldn’t do it. This breaks NUMA architecture, and more important, Fully Automated DRS! To support this, the DRS level should either be manual or partially automated. The process itself isn’t that complicated. Edit the settings of the VM and go to the resources tab. Under advanced CPU, you find the option for CPU affinity. If you do not see the Scheduling Affinity piece on a DRS-Cluster host, you are running DRS in fully automated mode. You can set DRS to manual for this VM by going to the cluster settings, and under DRS select Virtual Machine options. Set the DRS mode for this VM to either disabled, manual or partially automated....

Read More

8 weeks of #VCAP – More Networking Scenarios by Tom!

Another top notch scenario built by Tom Verhaeg! (blog/twitter)  Thanks Tom! Your recent work on the new portgroup was top notch! Now, the network administrators have some new requirements. You currently use one vNIC for the DvS. A second pNIC has been connected to the network and you have been tasked with adding it to the DvS. Also ensure that the DvS_StorageNetwork Port Group only uses the new pNIC and does VLAN tagging on VLAN ID 20. Another networking objective. Whoohoo! Allright, let us first check out the current network adapters available on the host: Allright, so vmnic2 is the one that we can add to the DvS_AMS01. Go over to the networking view (Ctrl + Shift + N) and edit the settings of your DvS. We first need to check if the DvS allows for 2 uplinks, instead of just 1. And check this out! It’s still set to 1. This is a good one to remember for the exam, on the DvS object itself, you configure the maximum number of physical adapters (also called uplink ports) per host. So set that one to 2 and let’s continue with adding vmnic2 to the DvS. Since the host is already connected to the DvS, click the DvS and select Manage Hosts. You will find your host, and you can add the second nic. You could also do this from the hosts and clusters view,...

Read More

8 weeks of #VCAP – Network Scenario by @tomverhaeg

First off I want to thank Tom Verhaeg (blog/twitter) for providing this scenario.  Tom had gotten in contact with myself and wanted to do what he can to help our with the 8 weeks of #VCAP series as he is going through a similar type process as me in studying for the VCAP5-DCA.  So props to Tom for taking the time and initiative to give back.  Hopefully we see more from him in the coming weeks!  Even better for myself as I can run through some scenarios that I didn't make up πŸ™‚  Be sure to follow Tom on Twitter and check out his blog  Thanks for the help Tom!!! Your company leverages the full Enterprise Plus licensing and has set up a Distributed vSwitch. Recently, the number of ports needed on a particular portgroup exceeded the number configured. You are tasked with creating a new Portgroup, called DvS_ProductionNetwork which only connects the running VM’s and also functions when vCenter is down. Off we go again. So, let’s recall. There are 3 different options of port binding on a DvS.  Static binding – Which creates a port group with a manual set number of ports. A port is assigned whenever a vNIC is added to a VM. You can connect a vNIC static binding only through vCenter. Dynamic binding (Deprecated in vSphere 5.0!) – A port is assigned to a...

Read More

PHD Virtual provides free Recovery Time Calculator

Have you ever wondered what your plan of attack will be in the event you need to recover your virtual infrastructure and the applications running on it?  How long before users will be able to resume their work?  Well, PHD Virtual, makers of PHD Virtual Backup have put the power in your hands to figure out just what that number is.  Today they have released a free, yes FREE tool dubbed the RTA calculator which can provide visibility into your organizations recover time will be. The tool itself runs on Windows, and simply points to your vCenter instance.  From there you have a wizard driven interface where you select which VMs you would like to analyze and set a boot order.  Now the magic happens.  RTA will take a snapshot of the selected VMs and utilizes link clones to create a copy of of these.  Lastly, it calculates the total time it will take for you to boot that group of VMs, leaving you with a nice estimate on your RTA (Recovery Time Actual). You can go and grab your free copy of the RTA calculator here – and for those that may be interested in seeing it in action there's a pretty cool video embedded...

Read More

8 weeks of #VCAP – Storage Scenarios (Section 1 – Part 2)

Hopefully you all enjoyed the last scenario based post because you are about to get another one πŸ™‚  Kind of a different take on covering the remaining skills from the storage section, section 1.  So, here we go! Scenario 1 A coworker has come to you complaining that every time he performs storage related functions from within the vSphere client, VMware kicks off these long running rescan operations.  He's downright sick of seeing them and wants them to stop, saying he will rescan when he feels the need to, rather than having vSphere decide when to do it.  Make it happen! So, quite the guy your coworker, thinking he's smarter than the inner workings of vSphere but luckily we  have a way we can help him.  And also the functions we are going to perform are also part of the VCAP blueprint as well – coincidence?  Either way, the answer to our coworkers prayers is something called vCenter Server storage filters and there are 4 of them, explained below… RDM Filter (config.vpxd.filter.rdmFilter) – filters out LUNs that are already mapped as an RDM VMFS Filter (config.vpxd.filter.vmfsFilter) – filters out LUNs that are already used as a VMFS datastore Same Hosts and Transports Filter (config.vpxd.filter.sameHostsAndTransporstFilter) – Filters out LUNS that cannot be used as a datastore extent Host Rescan Filter (config.vpxd.filter.hostRescanFilter) – Automatically rescans storage adapters after storage-related management functions...

Read More