PrintNumber	ErrorLocation	Error	Correction	DateAdded
1	Whole book	Book was sent to a second proofreader who marked up book and added numerous grammer/punctuation corrections. These will not be individually added in DB, but a list on correction side will show all affected pages. All author corrections (technical in nature) will be noted seperately on next entry. I will also upload the marked-up PDF to DCTM.	ii, xxi, xxii, xxiv	10/3/2012
1	whole book	First Printing, August 2012 Author corrections fixed on pages: 46, 69, 74, 77, 78, 145, 146, 149, 188, 209, 233, 257, 262, 266, 277, 296, 344, 351, 353, 356, 357, 360, 362, 367, 373, 374, 386, 407, 422, 450, 460, 478, 484, 488, 500, 514, 537 These correction’s Word Doc is on the InformIT page.	Second Printing, October 2012	10/9/2012
2	p82	Adding/Configuring/Removing vmnics on a vSphere Standard Switch As mentioned earlier, you might not want to create a new switch every time you need a new connection. In fact, you will make better use of your resources by adding to a current switch and thereby leveraging NIC teaming. In this section, I discuss how to add new vmnics to a switch that you already have. In addition, I discuss configuring vmnics and VMkernel ports on switches, including changing the IP address, VLAN, and so on. Finally, you learn how to remove a vmnic from a switch if you no longer require it. To add a new vmnic to an existing switch, you should not click Add Networking! As you might remember, clicking Add Networking takes you into a wizard that adds a new switch, not just into the networking properties of a switch you already have. So, if you don’t click Add Networking, what do you do? Well, if you think about it, what you really want to do is edit the configuration of a switch. For example, if you want to add a new vmnic to an existing switch to be used for vMotion, follow the steps outlined in Activity 2-3. Activity 2-3 Adding a vmnic to a Switch 1. Log on to your vSphere Client. 2. Select Home and then Hosts and Clusters. 3. Select the ESX host on which you want to edit the vSS. 4. Click the Networking link under Hardware. 5. Click the Properties link next to the switch that you want to edit, as shown in Figure 2-8.	Adding/Configuring/Removing vmnics on a vSphere Standard Switch As I mentioned earlier, you may not want to create a new vSwitch every time you need a new connection. In fact, you will make better use of your resources by adding to a current switch and thereby leveraging port groups and NIC teaming. In this section, I will discuss how to add new vmnics to a switch that you already have. I will also discuss how to remove a vmnic from a switch if you no longer require it. To add a new vmnic to an existing switch, you should not click on Add Networking! So if you don’t click on Add Networking, then what do you do? Well, if you think about it, what you really want to do is edit the configuration of a switch. For example, if you wanted to add a new vmnic to your existing vSwitch named vSwitch1, then you should do the following: Activity 2-3 Adding a vmnic to a Switch 1. Log on to your vSphere Client. 2. Select Home and then Hosts and Clusters. 3. Select the ESX host on which you would like to edit the vSS. 4. Click the Networking link under Hardware. 5. Click the Properties link next to the switch that you want to edit, as shown in Figure 2-8.	3/6/2013
2	p83	6. On the Properties dialog box for the switch, click Add, as shown in Figure 2-9. Replace Figure 2.9 7. On the Connection Type of the Add Network Wizard, select VMkernel and click Next, as shown in Figure 2-10. Repalce Figure 2.10 Figure 2-10 Selecting the VMkernel Connection Type	6. On the Properties dialog box for the switch, click on the Network Adapters tab and click Add, as shown in Figure 2-9. New Figure. 7. On the Adapter Selection dialog box, choose the vmnic (or vmnics) that you want to add and click Next; as shown in Figure 2.10. Note that the adapters are categorized as unclaimed or as already connected to a vSwitch. New figure. Figure 2-10Selecting the new vmnic	3/6/2013
2	p84	8. From VMkernel > Connection Settings, enter the Network Label and optionally the VLAN, as shown in Figure 2-11. (The Network Label should generally indicate the purpose of the switch or port group. In this case, you might use “vMotion” and enable it for vMotion.) Click Next. Replace Figure 2.11 Figure 2-11 Entering a Network Label 9. From VMkernel > IP Connection Settings, enter the IP address, subnet mask, and VMkernel default gateway to be used for the switch, as shown in Figure 2-12, and then click Next. Replace 2.12 Figure 2-12 Entering IP Information	Set the desired failover order and whether you want your new adapter to be active or just standby; then select Next; as shown in Figure 2.11 New figure Figure 2-11Choosing vmnic order and use 9. On the Adapter Summary page, review the list of adapters that you are adding, and select Finish. In this case, we are only adding vmnic3. New figure Figure 2-12 Adapter Summary page	3/6/2013
2	p85	10. In Ready to Complete, review your configuration settings and click Finish. Note As you might have noticed, after you select Add and Edit, the rest of the steps are much the same whether you are creating a new switch for the port or just adding a port to an existing switch. This is not just a coincidence in this case; it is always true. You will sometimes need to change the settings of a vmnic that you have already configured for a vSS. For example, you might want to edit the physical configuration such as the speed and duplex settings to match those of a physical switch to which your ESXi host is connected. To edit the physical configuration of the vmnic, follow the steps outlined in Activity 2-4. Replace Figure 2.13 Figure 2-13The Properties Link	10. To remove a vmnic when you no longer need it, simply select the vmnic in the Network Adapters list, select Remove, and confirm your selection; as shown in Figure 2.13. New Figure Figure 2-13 Removing a vmnic There will be cases when you need to change the settings of a vmnic that you have already configured for a vSS. For example, you might want to edit the physical configuration such as the speed and duplex settings to match those of a physical switch to which your ESXi host is connected. To edit the physical configuration of the vmnic, follow the steps outlined in Activity 2-4.	3/6/2013
2	p226	Review the most important topics from inside the chapter, noted with the Key Topic icon in the outer margin of the page. Table 3-2 lists these key topics and the page numbers where each is found. Know the main differences between vSSs and vDSs and the port groups on each. Understand how to create, configure, edit, and delete these components and policies.	Review the most important topics from inside the chapter, noted with the Key Topic icon in the outer margin of the page. Table 3-2 lists these key topics and the page numbers where each is found. Know the main differences between storage types, such as VMFS and NFS. Understand the differences between storage technologies, such as Fibre Channel, iSCSI, and NAS. Know how to create, configure, expand, and delete datastores.	3/6/2013
3	piv	Third Printing December 2012	Fourth printing: May 2013	4/30/2013
3	p189-190	Your physical networking hardware requirements will vary depending on whether you have chosen two hosts or three hosts for your cluster. For a VSA with 2 hosts, you will need 11 static IP addresses that are in the same subnet. If your cluster contains 3 hosts, you will need at a minimum 14 static IP addresses in the same subnet. All addresses must be in same subnet as the vCenter Server.	Your physical networking requirements will vary depending on whether you have chosen two hosts or three hosts and depending on whether you are using a DHCP server to assign some addresses. For a VSA with two hosts, you will need 11 static IP addresses that are in the same subnet if you do not use a DHCP server but only 9 if you do use a DHCP server. If your VSA cluster contains three hosts, you will need at a minimum 14 static IP addresses in the same subnet if you do not use a DHCP server but only 11 if you do use a DHCP server. All addresses must be in same subnet as the vCenter Server.	4/30/2013