VMware VSphere Optimize and Scale 6.5 - Labs

Lab 1

Using vSphere Distributed

Switches

Objective: Create, configure, back up, and check a

distributed switch

In this lab, you perform the following tasks: 1 . Log In to the Student Desktop

2. Verify That the vSphere Licenses Are Valid 3. Assign Valid vSphere Licenses

4. Create a Distributed Switch

5. Add ESXi Hosts to the New Distributed Switch 6. Examine Your Distributed Switch Configuration

7. Migrate the Virtual Machines to a Distributed Switch Port Group 8. Enable the Distributed Switch Health Check

9. Back Up the Distributed Switch Configuration

10. Cause Errors on the Distributed Switch 11. Monitor the Health of the Distributed Switch

12. Restore the Distributed Switch Configuration

Lab 1 Using vSphere Distributed Switches 1

[email protected]

mcse2012.blogfa.com

Task 1 : Log I n to the Student Desktop

You access and log in to your student desktop system to perform all lab activities for this course. Use the following information from the class configuration handout:

• Student desktop user name

• Standard lab password

1 . Ask your instructor how to log in to the student desktop system in your lab environment. For example, your instructor might have you use Remote Desktop Connection to connect to the student desktop system.

2. Log in to the student desktop system, using your student desktop user name and the standard lab password.

Task 2: Verify That the vSphere Licenses Are Valid

You verify that licenses for VMware vCenter Server® and the VMware ESXi™ hosts are valid. Use the following information from the class configuration handout:

• Standard lab password

1 . Log in to the VMware vSphere® Web Client interface.

a. On the student desktop machine task bar, click the Internet Explorer shortcut. b. From the Favorites bar, select vSphere Web Clients > SA-VCSA-0 1.

c. If you receive a security exception for vSphere Web Client, click the Continue to this website (not recommended) link to open the login screen.

d. Log in with [email protected] (the vCenter Server administrator user name) and the standard lab password.

e. Point to the Home icon and select Home.

2. Verify that the licenses for the vCenter Server system and the ESXi hosts are valid. a. On the Home page under Administration, click the Licensing icon.

b. In the center pane, click the Assets tab.

c. On the vCenter Server systems tab, verify that the vCenter Server system has a valid license.

d. Click the Hosts tab.

e. Verify that all ESXi hosts have valid licenses.

f. If the vCenter Server system and the ES Xi hosts are not licensed or have licenses that are expired, go to task 3 .

g. If the licenses are valid, go to task 4.

2 Lab 1 Using vSphere Distributed Switches

[email protected]

Task 3: Assign Valid vSphere Licenses

If the vCenter Server system and ESXi hosts licenses are expired, you assign valid licenses to these VMware vSphere® components.

Use the following information from the class configuration handout: • vCenter Server license key

• vSphere Enterprise Plus license key

1 . In the center pane, click the Licenses tab.

2. Click the Create New Licenses icon (green plus sign).

The New Licenses wizard appears.

3. In the License keys (one per line) text box, enter the 1 icense keys that your instructor gave you (one per line) and click Next.

4. On the Edit license names page, enter the new license names vcenter Server and Enterprise Plus in the License Name text boxes and click Next.

5. On the Ready to complete page, click Finish.

6. Assign a vCenter Server license key to the vCenter Server instance. a. In the center pane, click the Assets tab.

b. Click the vCenter Server systems tab and click the Assign License icon.

c. In the Assign License dialog box, select the vCenter Server license key.

d. Click OK.

7. Assign the vSphere Enterprise Plus license key to the ESXi hosts.

a. In the center pane, click the Hosts tab.

b. Select all hosts by clicking the first host, holding the Shift key, and selecting the last host.

c . Click the Assign License icon.

d. In the Assign License dialog box, select the vSphere Enterprise Plus license key. e. Click OK.

8. Reconnect the ESXi hosts.

a. Point to the Home icon and select Hosts and Clusters.

b. In the Navigation pane, expand SA Datacenter and select SA Management.

c . In the center pane, click the Hosts tab.

The three ES Xi hosts have a status of Disconnected.

d. Select all three hosts by clicking the first host, holding the Shift key, and selecting the last host.

e. Right-click the host selection and select Connection > Connect. f. Verify that all three ESXi hosts have a status of Connected.

Task 4: Create a Distri buted Switch

You create a distributed switch that functions as a single virtual switch across all associated hosts in your vSphere environment.

1 . In vSphere Web Client, point to the Home icon and select Networking.

2. In the left pane, expand the inventory until you see SA Datacenter.

3. Right-click SA Datacenter and select Distributed Switch > New Distributed Switch.

4. On the Name and location page, enter dvs -Lab in the Name text box and click Next.

5. On the Select version page, leave Distributed switch: 6.5.0 selected and click Next.

6. On the Edit settings page, enter pg-SA Production in the Port group name text box, keep all other defaults, and click Next.

7. On the Ready to complete page, review the configuration settings and click Finish.

The dvs-Lab distributed switch is listed in the left pane, also called the Navigator pane.

8. Configure the pg-SA Production port group to use only Uplink 2 .

a. In the left pane, expand dvs-Lab and right-click pg-SA Production.

b. Select Edit Settings.

c. In the Edit Settings window, select Teaming and failover on the left.

d. Select Uplink 1 and click the down arrow until the uplink appears under Unused uplinks. e. Select Uplink 3 and click the down arrow to move it to the Unused uplinks section.

f. Select Uplink 4 and move it to the Unused uplinks section. Failover order Active uplinks � Uplink2 standby uplinks Unused uplinks 1Jiii!1 Uplink 1 � Uplink3 � Uplink4 g. Click OK

Task 5: Add ESXi Hosts to the New Distri buted Switch

You add ESXi hosts and physical adapters to the distributed switch.

1 . In the Navigator pane, right-click the dvs-Lab distributed switch and select Add and Manage Hosts.

2 . On the Select task page, leave Add hosts clicked and click Next.

3. On the Select hosts page, click New Hosts (the green plus sign).

4. Select sa-esxi-01.vclass.local and sa-esxi-02.vclass.local and click OK.

Do not select sa-esxi-03.vclass.local.

5. Click Next.

6. On the Select network adapter tasks page, deselect the Manage VMkernel adapters check box and leave the Manage physical adapters check box selected.

7. Click Next.

8. On the Manage physical network adapters page, assign vmnic2 to Uplink 2 on sa-esxi-0 1 . vclass.local and sa-esxi-sa-esxi-02. vclass.local.

a. Under sa-esxi-0 1 .vclass .local, select vmnic2 and click Assign uplink. Manage physical networl< adauters

Add or remove physical network adapters to this distributed switch. �Assignuplink · · '\ I 1 g 0 QViewsemngs

Hosi!Phys1oal llet.Joik Adapt.rs 1 .. In U;:e by Swl!ell

• tJ sa-esxl-01.vclass.local 0 n this SWllC h • On other swilcheslunclaimed !iii vmnicO !iii vmnic1 liiiiil vmnic2 Iii! vmnic3 • tJ sa-esxi-02.vclass.local

b. Select Uplink 2 and click OK.

ilvs-SA Oatatenter ilvs-SA Oatacenter

c. Under sa-esxi-02.vclass.local, select vmnic2 and click Assign uplink.

d. Select Uplink 2 and click OK.

e. Click Next.

9. On the Analyze impact page, verify that the status is No impact for both ESXi hosts and click Next.

1 0 . On the Ready to complete page, review your settings and click Finish.

Task 6: Examine Your Distri buted Switch Configuration

You examine the configuration of the distributed switch uplink, which is bound to the associated physical interfaces on the ESXi hosts. You also examine other distributed switch features, including the maximum transmission unit (MTU) value, VLAN capabilities, LACP aggregation groups, NetFlow, and VMware vSphere® Network 110 Control.

1 . In the Navigator pane, select the dvs-Lab distributed switch.

2. In the center pane, click the Configure tab and select Topology on the left.

3. In the distributed switch topology diagram, click the arrow next to Uplink 2 to expand the view. � pg-SA Production 8

�

Ii; Uplink 1 (0 NIC Adapters)

..- Uplink 2 (2 NIC Adapters)

O vmnic2 sa-esxi-02.vclass.local 8

O vmnic2 sa-esxi-01.vclass.local 8 Uplink 3 (0 NIC Adapters)

� Uplink 4 (0 NIC Adapters)

4. Verify that for both ESXi hosts the vmnic2 is attached and appears under Uplink 2.

5. In the center pane, click Properties on the left and verify the settings.

• Network I/O Control is enabled.

• Number of uplinks is 4.

• The MTU size is 1500 bytes.

• The Cisco Discovery Protocol is implemented.

6. Click each additional configuration link on the left and verify the settings. • LACP LAG is not defined.

• Private VLAN is not defined. • NetFlow collector is not defined. • Port mirroring is not configured. • Health check is not enabled.

7. In the Navigator pane, select the pg-SA Production port group. 8. Click the Configure tab and select Properties on the left. 9. Verify the distributed port group settings.

• Port binding is set to static binding. • Port allocation is set to elastic.

• The number of ports is eight.

Task 7: Mig rate the Virtual Machines to a Distributed Switch Port Group You move the virtual machines from the pg-SA Management port group on the dvs-SA Datacenter distributed switch to the pg-SA Production port group on the dvs-Lab distributed switch.

Use the following information from the class configuration handout:

• Standard lab password

1 . In the Navigator pane, right-click the dvs-Lab distributed switch and select Migrate VMs to Another Network.

The Migrate VMs to Another Network wizard appears.

2. Migrate the virtual machines from pg-SA Management on the dvs-SA Datacenter distributed switch to the pg-SA Production network on the dvs-Lab distributed switch.

a. On the Select source and destination networks page, leave Specific network clicked for the Source network and click Browse.

b. Select pg-SA Management and click OK. c. For the Destination network, click Browse.

d. Select pg-SA Production and click OK.

e. Click Next.

f. On the Select virtual machines to migrate page, select the All virtual machines check box.

A warning message states that the destination network is inaccessible for one or more virtual machines and that these virtual machines are not selected for migration.

g. Click OK.

The LAB-VC S-0 1 virtual machine is dimmed. You cannot migrate this virtual machine, because it is hosted on the sa-esxi-03 .vclass. local host, which is inaccessible to the pg-SA­ Production port group.

h. Click Next.

3 . On the Ready to complete page, review the settings and click Finish.

4. Verify your distributed switch configuration.

a. In the Navigator pane, select dvs-Lab and click the Hosts tab in the center pane.

b. Verify that sa-esxi- 0 1 .vclass.local and sa-esxi-02.vclass. local are connected to the distributed switch.

The state of the ES Xi hosts should be Connected.

c. Click the VMs tab and verify that your virtual machines are listed.

If the virtual machines are listed, then they reside on the new distributed switch.

d. Click the Ports tab and verify that pg-SA Production is listed in the Port Group column and that an uplink port group is created for the distributed switch.

You can expand the Port Group column so that you can view the full name of the uplink port group.

5. In vSphere Web Client, point to the Home icon and select Hosts and Clusters.

6. Power on LinuxO 1 and log in to its console.

a. In the Navigator pane, expand SA Datacenter and expand the SA Management cluster.

b. Right-click LinuxOl and select Power > Power On. c . Right-click LinuxOl and select Open Console.

d. If you receive a security exception, click the Continue to this website (not recommended) link to continue.

Wait for the virtual machine to finish booting.

e . Log in as user root and use the standard lab password.

7 . Verify that the virtual machine has full network connectivity.

a. At the command prompt, ping 1 72.20 . 1 0. 1 0 (the domain controller's IP address) to verify the virtual machine 's network connectivity.

p ing 1 7 2 . 2 0 . 1 0 . 1 0

The p i ng command should be successful.

b. If the ping command is successful, press Ctrl+C to end the pi ng command.

c. If the ping command is not successful, enter the service network restart command to ensure that your virtual machine has a valid DHCP-assigned IP address.

d. Try the p ing command again.

e . I f the ping command is successful, press Ctrl+C to end the pi ng command.

8. Close the LinuxOl virtual machine console tab.

Task 8: Enable the Distri buted Switch Health C heck

You enable the health check service on the dvs-Lab distributed switch.

1 . In vSphere Web Client, point to the Home icon and select Networking.

2. In the Navigator pane, select the dvs-Lab distributed switch.

3. In the center pane, click the Configure tab and select Health check on the left.

4. Click Edit.

5. Set VLAN and MTU to Enabled. 6. Set Teaming and failover to Enabled.

7. Click OK

Task 9: Back U p the Distrib uted Switch Configuration

You save a backup of the dvs-Lab distributed switch configuration. 1 . In the Navigator pane, right-click the dvs-Lab distributed switch.

2 . Select Settings > Export Configuration.

3 . In the Export Configuration dialog box, leave Distributed switch and all port groups clicked and click OK.

4. When prompted, click Yes to save the exported configuration.

5. Save the distributed switch configuration to the desktop of the student desktop machine, using the default bac kup . zip filename.

Task 1 0: Cause Errors on the Distrib uted Switch

You purposely cause errors by configuring an inval id VLAN ID on the pg-SA Production port group and setting the MTU value to 9000 on the dvs-Lab distributed switch. These misconfigurations are reported by the distributed switch health check service.

I M PORTANT

Use only the dvs-Lab distributed switch for this task. Do not try to cause errors on the dvs-SA Datacenter distributed switch.

1 . Configure an invalid VLAN ID on the distributed port group.

a. In the Navigator pane, right-click pg-SA Production and select Edit Settings. b. In the Edit Settings window, click VLAN on the left.

c . From the VLAN type list, select VLAN.

d. In the VLAN ID box, enter 37.

VLAN ID 37 is not a valid VLAN ID because the physical switch is not configured for VLAN 37. An invalid VLAN ID causes an error after you save the configuration. e. Click OK.

2. Misconfigure the distributed switch by setting the MTU value to 9000.

a. In the Navigator pane, right-click the dvs-Lab distributed switch and select Settings > Edit Settings.

b. In the Edit Settings dialog box, select Advanced on the left. c . In the M T U (Bytes) box, change the value to 9000 .

This setting causes an error after you save the configuration because jumbo frames are not configured in your environment.

d. Click OK.

Task 1 1 : Mon itor the Health of the Distrib uted Switch You check the health of the dvs-Lab distributed switch.

1 . In the Navigator pane, select the dvs-Lab distributed switch.

2. In the center pane, click the Monitor tab and click Health.

3. Select the first ESXi host in the list.

4. View the VLAN tab at the bottom of the page.

The VLAN configuration status might take a few minutes to update. 5. Wait for the VLAN configuration status to change to Not Supported.

You might need to click the Refresh icon a few times in the vSphere Web Client interface to update the status.

6. Click the MT U tab at the bottom of the page.

The MTU configuration status might take a few minutes to update. Until then, the configuration status is Unknown.

7. Wait for the MTU configuration status to change to Not Supported.

You might need to click the Refresh icon a few times in the vSphere Web Client interface to update the status.

Task 1 2: Restore the Distri buted Switch Configuration

You restore the dvs-Lab distributed switch configuration to reset any configuration change made since the configuration was saved.

1 . In the Navigator pane, right-click the dvs-Lab distributed switch and select Settings > Restore Configuration.

The Restore Configuration wizard appears.

2. On the Restore switch configuration page, click Browse, select the backup.zip file, and click

Open.

3. Leave Restore distributed switch and all port groups clicked and click Next.

4. On the Ready to complete page, review the settings and click Finish.

5 . If you lose connection to vSphere Web Client, restart the Internet Explorer browser. 6. After the switch configuration is restored, verify the configuration.

a. View the Health panel and verify that the overall health of the dvs-Lab distributed switch is back to normal.

You might need to click the Refresh icon in the vSphere Web Client interface to update the status.

b. View the VLAN settings of the pg-SA Production port group and verify that no VLAN is configured.

c. View the advanced settings of the dvs-Lab distributed switch and verify that the MTU value is 1 500.

7. Point to the Home icon and select Home.

Lab 2

Using Port Mirroring

Objective: Configure port mirroring and capture network

traffic on a distributed switch

In this lab, you perform the following tasks: 1 . Prepare to Capture Mirrored Network Traffic 2. Configure Port Mirroring on the Distributed Switch 3. Verify That Port Mirroring Is Capturing Traffic

Task 1 : Prepare to Capture Mi rrored Network Traffic

You use the LinuxO l virtual machine to capture and monitor mirrored traffic. 1. If you are logged out of vSphere Web Client, log back in.

a. Open a new tab in Internet Explorer.

b. From the Favorites bar, select vSphere Web Clients > SA-VCSA-0 1.

c. Log in with [email protected] (the vCenter Server administrator user name) and

the standard lab password.

2. In vSphere Web Client, point to the Home icon and select Hosts and Clusters.

3 . In the left pane, expand SA Datacenter and expand the S A Management cluster.

4. In the left pane, log in to the LinuxO 1 virtual machine console. a. Right-click LinuxOl and select Open Console.

b. If prompted, click the Continue to this website (not recommended) link to continue. You should be logged in to LinuxO l as root.

c. If you are not logged in, then log in as user root with the standard lab password.

5. In the LinuxO 1 console, monitor ICMP network traffic.

tcpdump -nn i cmp

lrnntfllor,1lhw,t ·Ill trpciump nn 1rmp

tr:pc1ump vr-rhosc 011tp11t ·�11pprr::-;scc1, 11sc v nr vv for fu 11 protoco 1 c1croc1(' ]10.k111114 u11 t:llil'J, l111k t4µe ENHIMB Ull1t:r·11t'll, Lcl]JlllrT 0.1;.::t· 'JG b4lt·s

6. Monitor the command output for a few seconds and verify that ICMP traffic is not being captured.

tcpdump output remains silent until ICMP traffic is detected on the network.

7. Leave the console window open, with the tcpdump command running uninterrupted.

8. In the Internet Explorer window, click the vSphere Web Client tab.

9. Power on the Linux02 virtual machine and log in to its console.

a. In the left pane, right-click Linux02 and select Power > Power On.

b. Right-click Linux02 and select Open Console.

c. If prompted, click the Continue to this website (not recommended) link to continue. Wait for the virtual machine to finish booting.

d. Log in as user root and use the standard lab password.

The Linux02 virtual machine is used as the traffic source to be monitored.

10. At the Linux02 command prompt, ping 1 72.20. 1 0 . 1 0 (the default router IP address).

p ing 1 7 2 . 2 0 . 1 0 . 10

1 1 . If the ping command does not work, enter service network restart and repeat step 10. 1 2 . After the p ing command begins working, click the LinuxO l console tab.

1 3 . In the LinuxO 1 console window, verify that the running tcpdump command output remains silent and has not captured any ICMP traffic .

Task 2: Configure Port Mi rroring on the Distrib uted Switch

You configure port mirroring so that the port connected to the Linux02 machine is the mirror source and the port connected to the LinuxO 1 machine is the mirror destination. All the traffic present on the Linux02 port is forwarded to the LinuxO 1 port for examination.

1 . In the Internet Explorer window, click the vSphere Web Client tab. 2. Point to the Home icon and select Networking.

3. In the Navigator pane, select the dvs-Lab distributed switch.

4. In the center pane, click the Configure tab and select Port mirroring on the left.

5. In the Port mirroring panel, click the New icon. The Add Port Mirroring Session wizard appears.

6. On the Select session type page, leave Distributed Port Mirroring clicked and click Next.

When you select this session type, distributed ports can only be local. If the source and destination ports are on different hosts, port mirroring between them does not work. The LinuxO I and Linux02 virtual machines both reside on sa-esxi-01 .vclass.local.

7. On the Edit properties page, configure the port mirroring session.

a. Select Enabled from the Status drop-down menu.

b. Select Allowed from the Normal 1/0 on destination ports drop-down menu. c. Keep the rest of the defaults and click Next.

8. On the Select sources page, configure the port mirroring source. a. Click the Select distributed ports icon.

Select sources

Select the source distributed po

�

Port ID Host

b. In the Select Ports dialog box, select the check box for the row with a connected entity of

Linux02 and click OK.

c. Click Next.

9. On the Select destinations page, configure the port mirroring destination.

a. Click the Select distributed ports icon.

b. In the Select Ports dialog box, select the check box for the row with a connected entity of LinuxO I and click OK.

c. Click Next.

1 0 . On the Ready to complete page, review the settings and click Finish.

Task 3: Verify That Port Mirroring Is Capturing Traffic

With mirroring between ports configured, you view the t cpdump command output and verify that

any ICMP traffic appearing on the Linux02 port is duplicated on the LinuxO 1 port. 1 . In the Internet Explorer window, click the Linux02 console tab.

2 . Verify that the ping command is still reaching the default router IP address. 3 . Click the LinuxOl console tab.

4. In the LinuxO 1 console, examine the tcpdump output in the terminal window. The output looks similar to the screenshot.

Linux01

11 : 1.:1: /.H. 'i 13'J'JH Ip 1'?1. . /.H. 11 ./.H1 > 1'?1. ./.H .1H .1H: ICMP P.cho r�f(llf-".'St 1 i<I :nH4H, SF.

'I �-}7.1 , lc1111th f14

1 J : I. J : /. ll . '.1 144 '? ') II' 1'?1. . /.H. 1H. 1H > Ul..1.H. 11 . /.H 1 : ICM!' (!t:hll I' qll lJ , id :L!H41l, SCC{

'.124, Icnqth 64

Ll:/.J:2'J.'.,14b21l II' UZ.ZH.11./.Hl > li/..ZH.lH.lU: ICM!' echo re4uest, id JJH4U, se

ci '1/.�1, Icnuth h4

U:2J:?.'J.�1l�>l'.16 IP 1'12./.H.lU.lU > U2.2H.11.2Ul: ICMP t:cho repltJ, id :UU4B, se11 '1/.'1, I e1111 th f14

5 . Record the local address that appears in the captured traffic.

The local address begins with 1 72.20. 1 1 .

----6. In the LinuxO l console window, press Ctrl+C to stop the tcpdump command.

7. In the Internet Explorer window, click the Linux02 console tab.

8. In the Linux02 console window, press Ctrl+C to stop the p ing command. 9. At the Linux02 command prompt, examine the IP configuration.

i fc o n f i g

10. Using the command output, verify that the Linux02 IP address matches the address that you recorded in step 5.

l l . Close the LinuxOl and Linux02 console tabs. 1 2 . Shut down LinuxO l and Linux02.

a. Point to the Home icon and select Hosts and Clusters.

b. In the left pane, right-click LinuxOl and select Power > Shut Down Guest OS. c. In the pop-up window, click Yes to confirm the shutdown operation.

d. Repeat steps b and c to shut down Linux02. 1 3 . Point to the Home icon and select Home.

Lab 3

Policy-Based Storage

Objective: Use policy-based storage to create tiered

storage

In this lab, you perform the following tasks:

1 . Add Datastores for Use by Policy-Based Storage

2 . Use vSphere Storage vMotion to Migrate a Virtual Machine to the Gold Datastore 3 . Configure Storage Tags

4. Create Virtual Machine Storage Policies 5 . Assign Storage Policies to Virtual Machines

Task 1 : Add Datastores for Use by Policy-Based Storage

You create two small datastores for use by your vCenter Server instance as simple tiered storage. Each datastore is approximately 8 GB in size.

1 . If you are logged out of vSphere Web Client, log back in.

2. Point to the Home icon and select Storage.

3 . Create a datastore named Gold.

a. In the Navigator pane, right-click SA Datacenter and select Storage > New Datastore. The New Datastore wizard appears.

b. On the Location page, click Next.

c . On the Type page, leave VMFS clicked and click Next.

d. On the Name and device selection page, enter Gold in the Datastore name text box.

e. In the Select a host to view its accessible disks/LUNs list, select sa-esxi-02.vclass.local.

f. In the disk/LUN l ist, select the entry for the lowest LUN number attached to an iSCSI device.

Local drives are labeled as Local VMware Disk. Do not select these drives.

g. If iSCSI devices are not present, ask the instructor for instructions on how to add them.

h. Click Next.

1. On the VMFS version page, leave VMFS 6 clicked and click Next.

J. On the Partition configuration page, keep the defaults and click Next. k. On the Ready to complete page, review the settings and click Finish.

I. Verify that the Gold datastore appears in the Navigator pane. 4. Create a datastore named Silver.

a. In the Navigator pane, right-click SA Datacenter and select Storage > New Datastore. The New Datastore wizard appears.

b. On the Location page, click Next.

c. On the Type page, leave VMFS clicked and click Next.

d. On the Name and device selection page, enter Si lver in the Datastore name text box.

e. In the Select a host to view its accessible disks/LUNs list, select sa-esxi-02.vclass.local. f. In the disk/LUN list, select the entry for the lowest LUN number attached to an iSCSI

device and click Next.

Local drives are labeled as Local VMware Disk. Do not select these drives.

g. On the VMFS version page, leave VMFS 6 cl icked and click Next.

h. On the Partition configuration page, keep the defaults and click Next.

1. On the Ready to complete page, review the settings and click Finish. J. Verify that the Silver datastore appears in the Navigator pane.

Task 2: Use vSphere Storage vMotion to Mig rate a Virtual Machine to the Gold Datastore

Use VMware vSphere® Storage vMotion® to migrate the VMO l virtual machine to the Gold datastore.

1 . Power on VMO l .

a. Point to the Home icon and select Hosts and Clusters. b. Right-click VMOl and select Power > Power On.

c . When VMO l i s powered on, go to the next step.

2. In the Navigator pane, right-click VMOl and select Migrate. The Migrate wizard appears.

3. On the Select the migration type page, click Change storage only and click Next.

4. On the Select storage page, select the Gold datastore, leave all other settings at their default

values, and click Next.

5. On the Ready to complete page, click Finish.

6. In the Recent Tasks pane, monitor the migration task to completion. 7. Verify that the migration was successful.

You might have to refresh vSphere Web Client to see that the migration has completed.

a. In the left pane, select VMOl.

b. In the center pane, click the Datastores tab and verify that the Gold datastore is listed.

Task 3: Configure Storage Tags

You create the tags necessary to implement simple tiering. The Storage Tiers tag category contains the Gold and Silver identifier tags associated with individual datastores.

1 . Point to the Home icon and select Tags & Custom Attributes from the list. 2. In the center pane, click the Tags tab.

3. Configure a new tag category and the Gold Tier identifier tag. a. In the Tags panel, click the New tag icon.

[

1

J

b. From the Category drop-down menu, select New Category.

The dialog box expands to include both tag and category configuration options. Categories can be created only as part of the identifier tag creation process. c . In the Name text box, enter Gold Tier.

d. In the Category Name text box, enter Storage Tiers.

e. Keep the default values for the remaining settings and click OK.

4. Create a Silver Tier identifier tag.

a. In the center pane, click the New Tag icon.

b. In the Name text box, enter Silver Tier.

c. Select Storage Tiers from the Category drop-down menu and click OK. 5. Assign the Gold Tier tag to the Gold datastore.

a. Point to the Home icon and select Storage.

b. In the left pane, right-click the Gold datastore and select Tags & Custom Attributes >

Assign Tag.

c . Select the Gold Tier tag and click Assign.

d. In the left pane, select the Gold datastore .

e . In the center pane, click the Summary tab.

f. In the Tags panel, verify that the Gold Tier tag is associated with the Gold datastore.

6. Assign the Silver Tier tag to the Silver datastore .

a. Right-click the Silver datastore and select Tags & Custom Attributes > Assign Tag. b. Select the Silver Tier tag and click Assign.

c . In the left pane, select the Silver datastore.

d. In the center pane, click the Summary tab.

e. In the Tags panel, verify that the Silver Tier tag is associated with the Silver datastore .

Task 4: C reate Virtual Machine Storage Policies

You assign storage policies to virtual machines and specify the configuration settings to be enforced. 1 . Point to the Home icon and select Policies and Profiles.

2. In the left pane, click VM Storage Policies. 3 . Create a Gold Tier storage policy.

a. In the VM Storage Policies panel, click the Create VM Storage Policy icon.

§3 VM storage Policies

VM storage Policies Storage Po lie\

�Create

Storage

The Create New VM Storage Policy wizard appears.

b. On the Name and description page, enter Gold Tier Policy in the Name text box and click Next.

c. On the Policy structure page, review the information and click Next. d. On the Common rules for data services provided by hosts page, click Next.

e. On the Rule-set 1 page, select Tags from category from the <Add rule> list.

f. From the Tags from category <Select category> drop-down menu, select Storage Tiers.

g. Click Add tags, select the Gold T ier check box, and click OK. h. Click Next.

1. On the Storage compatibility page, verify that the Gold datastore is listed under Compatible storage and click Next.

J. On the Ready to complete page, click Finish.

4. Repeat step 3 to create a Silver Tier policy, using the Silver Tier tag.

Task 5: Assign Storage Policies to Vi rtual Machi nes

You assign the Gold and Silver storage policies to individual virtual machines and mitigate compliance issues.

1 . Power off VMO 1 .

A storage policy can be assigned to a virtual machine while the virtual machine is either powered on or powered off.

a. Point to the Home icon and select Hosts and Clusters. b. Right-click VMOl and select Power > Power Off.

c . Click Yes to confirm the power-off operation.

2. Apply the Gold Tier storage policy to the VMO 1 virtual machine.

a. In the left pane, right-click VMOl and select VM Policies > Edit VM Storage Policies.

b. In the Edit VM Storage Policies dialog box, select Gold T ier Policy from the VM storage policy drop-down menu and click Apply to all.

c. In the list, verify that the Gold Tier policy is assigned to VM home and Hard disk 1 and click OK

d. In the left pane, select VMOl.

e. In the center pane, click the Summary tab.

f. In the VM Storage Policies panel, verify that Gold Tier Policy appears and that VMO l is compliant.

The VMO 1 virtual machine is compliant because it was already moved to a policy­ appropriate datastore .

.,. VM storage Policies D

VM Storage Policies �Gold Tier Policy

VM Storage Policy Compliance � Compliant

Last Checked Date 111312016 2 59 PM

22 Lab 3 Policy-Based Storage

3. Apply the Silver Tier storage policy to the VM02 virtual machine.

a. In the left pane, right-click VM02 and select VM Policies> Edit VM Storage Policies.

b. In the Edit VM Storage Policies dialog box, select Silver Tier Policy from the VM storage policy drop-down menu and click Apply to all.

c. In the list, verify that the Silver Tier policy is assigned to VM home and Hard disk 1 and click OK

d. In the left pane, select VM02.

e. In the center pane, click the Summary tab.

f. In the VM Storage Policies panel, click the Check Compliance link.

g. Verify that Silver Tier Policy appears and that VM02 is not compliant.

The VM02 virtual machine is noncompliant because its virtual disk is stored on a datastore that is not tagged as a part of the assigned policy.

... VM S1orage Policies D

VM Storage Policies ijj Silver Tier Policy

VM Storage Policy Compliance O Noncompliant Last Checked Date 11!3!2015 3:02 PM

Check Compliance

4. Remediate the compliance issue for VM02. .:::t

a. In the left pane, right-click VM02 and select Migrate. The Migrate wizard appears.

b. On the Select the migration type page, click Change storage only and click Next.

c. On the Select storage page, select the Silver datastore in the datastore list and click Next.

With a virtual machine storage policy assigned to the VM02 virtual machine, datastores are listed as either Compatible or Incompatible.

d. On the Ready to complete page, review the migration details and click Finish. e. In the Recent Tasks pane, monitor the migration task to completion.

The migration must complete successfully. 5. Verify that VM02 is reported as compliant.

a. In the center pane, click the Check Compliance link in the VM Storage Policies panel. b. Verify that the status changes to Compliant.

6. Point to the Home icon and select Home.

Lab 4

Managing Datastore Clusters

Objective: Create a datastore cluster and work with

vSphere Storage DRS

In this lab, you perform the following tasks:

1 . Create a Datastore Cluster with vSphere Storage DRS Enabled 2 . Evacuate a Datastore Using Datastore Maintenance Mode

3. Run vSphere Storage DRS and Apply Migration Recommendations 4. Clean Up for the Next Lab

Task 1 : C reate a Datastore Cluster with vSphere Storage DRS Enabled

You create a datastore cluster that is enabled for VMware vSphere® Storage DRS™. The Gold and Silver datastores are reused as members of the cluster.

1 . If you are logged out of vSphere Web Client, log back in.

2. Point to the Home icon and select Storage.

3. In the left pane, right-click SA Datacenter and select Storage> New Datastore Cluster.

The New Datastore Cluster wizard appears.

4. On the Name and location page, name the datastore cluster and enable vSphere Storage DRS. a. In the Datastore cluster name text box, enter Cluster-DRS.

b. Leave the Turn ON Storage DRS check box selected and click Next.

5. On the Storage DRS Automation page, view the automation settings. a. Leave No Automation (Manual Mode) selected.

b. Keep the rest of the defaults and click Next.

6. On the Storage DRS Runtime Settings page, keep the defaults and click Next.

7. On the Select Clusters and Hosts page, select the SA Management check box on the Filter tab and click Next.

8. On the Select Datastores page, select the datastores for the datastore cluster.

a. Select Show all datastores from the drop-down menu.

b. Select the Gold and Silver check boxes and click Next.

9. On the Ready to Complete page, review the configuration summary and click Finish.

In a production environment, the best practice is to select datastores that are connected to all hosts in the cluster and to group them by storage capabilities.

10. In the left pane, expand Cluster-DRS and verify that the Gold and Silver datastores appear .

...

IJ

..,.. JIT3. SA Data center

..,.. �Cluster-DRS §I Gold

§I Silver

11. View information about the Gold datastore. a. In the left pane, select the Gold datastore . b. In the center pane, click the VMs tab.

c. Verify that the datastore contains only one virtual machine. 12. View information about the Silver datastore.

a. In the left pane, select the Silver datastore. b. In the center pane, click the VMs tab.

c. Verify that the datastore contains only one virtual machine.

1 3 . View information about the datastore cluster.

a. In the left pane, select Cluster-DRS.

b. In the center pane, click the Configure tab and click Storage DRS on the left.

c . In the vSphere Storage DRS panel, expand each item and verify the settings. • Cluster automation level is set to No Automation (Manual Mode). • Space threshold is 80 percent.

• 1/0 metrics for vSphere Storage DRS recommendations are enabled. • Imbalances are checked every 8 hours.

• Minimum space utilization difference is 5 percent.

Task 2: Evacuate a Datastore Using Datastore Mai ntenance Mode

You place a datastore in maintenance mode to demonstrate the capabilities of vSphere Storage DRS. 1 . Put the Silver datastore in maintenance mode.

a. In the left pane, right-click the Silver datastore.

b. Select Maintenance Mode > Enter Maintenance Mode.

c . In the SDRS Maintenance Mode Migration Recommendations dialog box, read the provided recommendation description.

d. Click Apply Recommendations.

e. If prompted to apply recommendations despite warnings, click Yes. The VM02 virtual machine is migrated to the Gold datastore .

f. In the Recent Tasks pane, monitor the migration task to completion. 2. In the left pane, verify that the Silver datastore is in maintenance mode.

�

�r

�

·

1

!2.

I

�

I

3 . Click the Refresh icon in the vSphere Web Client interface.

4. View information about the Silver and Gold datastores.

a. Select the Silver datastore.

b. In the Details panel of the Summary tab, verify that zero virtual machines are stored on the Silver datastore.

c . Select the Gold datastore.

d. In the Details panel of the Summary tab, verify that two virtual machines are stored on the Gold datastore.

5 . Take the Silver datastore out o f maintenance mode.

a. Right-click the Silver datastore and select Maintenance Mode> Exit Maintenance Mode. b. Verify that the Silver datastore icon no longer indicates maintenance mode.

6. Point to the Home icon and select Hosts and Clusters.

7. Power on the VMO l and VM02 virtual machines.

Task 3: Run vSphere Storage DRS and Apply Migration Recommendations

You configure vSphere Storage DRS to maintain a balance in usage across all datastores in a cluster. The cluster imbalance is mitigated by using vSphere Storage DRS recommendations.

1 . Point to the Home icon and select Storage. 2. In the left pane, select Cluster-DRS.

3. In the center pane, click the Configure tab and select Storage DRS on the left.

4. Configure vSphere Storage DRS so that recommendations are reported. a. In the vSphere Storage DRS panel, click Edit.

b. In the Edit Storage DRS Settings dialog box, expand the Storage DRS Automation

section.

c. Next to Space Threshold, drag the Utilized Space slider to the far left to set the threshold to 50 percent.

The imbalance between the Gold and Silver datastore util ization is detected at a 50 percent space threshold trigger.

d. Click OK.

5. Run vSphere Storage DRS and review recommendations.

a. In the center pane, click the Monitor tab and click Storage DRS.

b. Select Recommendations on the left and click Run Storage DRS Now. A vSphere Storage DRS recommendation appears in the recommendation list. c. Review the recommendation and reason.

vSphere Storage DRS recommends the migration of the VM02 Hard disk 1 . 6. Examine the vSphere Storage DRS recommendation alarm.

a. In the center pane, click the Summary tab and find the yellow vSphere Storage DRS recommendation alarm.

The administrator can reset the recommendation alarm manually. The vSphere Storage DRS recommendation alarm is reset when the recommendation is applied.

7. Apply the vSphere Storage DRS recommendation. a. In the center pane, click the Monitor tab.

b. In the bottom-right corner of the Storage DRS Recommendations panel, click Apply Recommendations.

c. In the Recent Tasks pane, monitor the migration task to completion. 8 . In the center pane, click the Summary tab and verify that no alarms appear. 9. Review vSphere Storage DRS history.

a. In the center pane, click the Monitor tab.

The Storage DRS panel should appear.

b. Below the Recommendations link, click the History link.

c. Verify in the vSphere Storage DRS history that Hard disk 1 for VM02 was migrated from Gold to Silver.

d. Verify in the vSphere Storage DRS history that Hard disk 1 for VM02 was migrated from Silver to Gold.

This migration occurred when the Silver datastore was placed in maintenance mode.

Task 4: Clean U p for the Next Lab

You remove the vSphere Storage DRS cluster to prepare for the next lab. 1 . Point to the Home icon and select Hosts and Clusters.

2. Power off the VMO l and VM02 virtual machines. 3. Delete the vSphere Storage DRS cluster.

a. Point to the Home icon and select Storage.

b. In the left pane, right-click Cluster-DRS and select Delete. c . When prompted, click Yes to delete the datastore cluster.

d. After the cluster is deleted, verify that the Gold and Silver datastores appear in the left pane, directly under the data center.

4. Point to the Home icon and select Home.

Lab 5

Working with Virtual Volu mes

Objective: Configure N FS- and iSCSl-backed virtual

volumes

In this lab, you perform the following tasks:

1 . Register the Storage Provider

2 . Create a NAS-Backed Virtual Volume Datastore 3. Create an iSCSI-Backed Virtual Volume Datastore

Task 1 : Register the Storage Provider

You register the storage provider, and you confirm its URL and version. You also view the storage systems that are made available by the storage provider.

1 . In vSphere Web Client, point to the Home icon and select Hosts and Clusters.

2. At the top of the left pane, select sa-vcsa-01.vclass.local (your VMware vCenter® Server Appl iance™ instance).

3. In the center pane, click the Configure tab and select Storage Providers on the left side.

4. In the center pane, click the Register a new storage provider icon.

Storage Providers

5. In the New Storage Provider dialog box, configure the VASA storage provider.

Option Action

Name Enter VASASource.

URL Enter https : I /1 72 . 2 0 . 10 . 97 : 8 4 4 3 /vasa/version . xml .

User name Enter u sername .

Password Enter password.

6. Click OK.

7. Click Yes to acknowledge and accept the self-signed certificate warning.

8 . Validate that the VASASource storage provider appears in the Storage Providers list.

Q1. In the storage providers window, what is the storage provider URL for VASASource?

Q2. Which version of vSphere API for Storage Awareness appears in the VASA API Version column?

Q3. Which types of storage systems are listed for this storage provider?

Task 2: Create a NAS-Backed Vi rtual Vo lume Datasto re

You mount a virtual volume datastore by using an NFS protocol endpoint. 1 . Create a virtual volume datastore by using the NFS container.

a. Point to the Home icon and select Hosts and Clusters.

b. In the left pane, right-click sa-esxi-01.vclass.local and select Storage > New Datastore.

The New Datastore wizard appears.

c . On the Type page, click VVol and click Next.

d. On the Name and container selection page, enter SA-NAS -VVol in the Datastore name

text box.

e. From the Backing Storage Container l ist, select SA-NFS -vVol and click Next.

f. On the Ready to complete page, click Finish.

2. Validate the new datastore by creating a folder in it.

a. Point to the Home icon and select Storage.

b. In the left pane, select the SA-NAS -VVol datastore. c. In the center pane, click the Files tab.

d. In the center pane, click the Create a new folder icon.

� I >C

e. In the Create a new folder window, enter SA-NAS in the Enter a name for the new folder text box and click Create.

The creation of the folder validates that the datastore is available.

Task 3: Create an iSCSl -Backed Virtual Vol ume Datastore You create a virtual volume datastore that is backed by an iSCSI protocol endpoint.

1 . Create a virtual volume datastore that uses the iSCSI storage container.

a. In the left pane, right-click SA Datacenter and select Storage> New Datastore. The New Datastore wizard appears.

b. On the Location page, click Next.

c . On the Type page, click VVol and click Next.

d. On the Name and container selection page, enter SA- iSCS I -VVol in the Datastore name

text box.

e. In the Backing Storage Container list, select SA-iSCSI-vVol and click Next.

f. On the Select hosts accessibility page, select the sa-esxi-0 1.vclass.local check box and click Next.

g. On the Ready to complete page, click Finish.

2. In the Recent Tasks pane, monitor the Create Virtual Volume datastore task to completion. 3. After the task completes, click the Refresh icon in vSphere Web Client.

4. In the left pane, verify that SA-iSCSI-VVol appears in the list.

After a short while, the datastore is marked as inactive.

Q1 . Why is the virtual volume datastore that is backed by the iSCSI container marked as inactive?

5. Create a folder on the datastore and validate that the folder is not available.

a. In the left pane, select the SA-iSCSI-VVol datastore.

b. In the center pane, click the Files tab.

c . In the center pane, click the Create a new folder icon.

d. In the Create a new folder window, enter SA- iSCSI in the Enter a name for the new folder text box and click Create.

The folder creation fails, validating that the datastore is not accessible. e . Close the folder creation failure alert.

6. Add the Storage Provider as a target to the host's iSCSI storage adapter. a. Point to the Home icon and select Hosts and Clusters.

b. In the left pane, select sa-esxi-0 1.vclass.local.

c. In the center pane, click the Configure tab and select Storage Adapters on the left.

d. Scroll through the Storage Adapters list until the iSCSI software adapter is visible.

e. Select vmhba##, the iSCSI software adapter. f. In the Adapter Details panel, click the Paths tab. g. Scroll through the list.

Several paths appear in the 1 ist. h. Click the Targets tab and click Add.

1. In the Add Send Target Server window, enter 1 7 2 . 2 0 . 1 0 . 97 in the iSCSI Server text box.

1 72.20. 1 0.97 is the IP address of the VASA storage provider.

J. Click OK

k. In the center pane, click the Rescan all storage adapters icon.

storage Adapters

l. In the Rescan Storage window, click OK.

m . In the Adapter Details panel, click the Paths tab. n. Verify that LUN 260 appears in the list.

LUN 260 is the LUN on which the SA-iSCSI-VVol datastore is located.

7. Point to the Home icon and select Storage.

8 . In the left pane, verify that the SA-iSCSI-VVol datastore i s not inactive.

9. If the datastore appears as inactive, click the Refresh icon in vSphere Web Client. 1 0 . Verify that the datastore is accessible.

a. In the left pane, select the SA-iSCSI-VVol datastore.

b. In the center pane, click the Create a new folder icon on the Files page.

c. In the Create a new folder window, enter SA- iSCSI in the text box and click Create. The creation of the folder validates that the datastore is available.

1 1 . Point to the Home icon and select Home.

Lab 6

Creating a Content Library

Objective: Create a multisite content library

In this lab, you perform the following tasks: 1 . Create a Content Library

2 . Upload Data to the New Content Library 3. Create a Subscriber Content Library 4. Clone a Template to the Source Library 5. Synchronize the Content Libraries

6. Deploy a Virtual Machine from the Library

Task 1 : Create a Content Library

You configure a local content library that you publish externally for other content libraries to subscribe to.

1 . In vSphere Web Client, point to the Home icon and select Content Libraries.

2. In the center pane, click the Objects tab and click the Create a new content library icon. f§J Content Libraries

G etti ng Started Objects

3. On the Name and location page, name the content library and verify the vCenter Server location.

a. In the Name text box, enter SA-Source.

b. In the vCenter Server drop-down menu, verify that sa-vcsa-01.vclass.local is selected and click Next.

4. On the Configure content library page, configure a local content library. a. Leave Local content library selected.

b. Select the Publish externally check box. c. Select the Enable authentication check box.

d. In the Password and Confirm password text boxes, enter the standard lab password.

e. Click Next.

5. On the Add storage page, select the datastore to use for the content library.

a. Click Select a datastore.

b. Click SA-Source and click Next.

6. On the Ready to complete page, click Finish.

7. Verify that the content library appears in the list.

Task 2: U pload Data to the New Content Library

You upload an Open Virtualization Format (OVF) file from your student desktop to the new content library.

1 . In the center pane, right-click the SA-Source library and select Import Item.

2. In the Import Library Item window, click Local file and click Browse. 3. In the Choose File to Upload window, click the Desktop icon on the left bar.

4. Double-click the Class Materials and Licenses folder and double-click the Downloads folder.

5 . In the Downloads folder, double-click the SampleVM folder. 6. Double-click SampleVM.ovf.

7. In the Select referenced files window, click Browse.

8 . Select the SampleVM-1 .vmdk file, click Open, and click OK.

9. Click OK.

1 0 . View the Recent Tasks pane to monitor the task to completion.

1 1 . After the task is complete, click the name of the content library in the center pane to open the content library.

1 2 . In the left pane, click the Templates link.

The uploaded SampleVM template is listed in the left pane.

Task 3: Create a Su bscri ber Co ntent Library

You configure a content library that is subscribed to the first library.

1 . At the top of the left pane, click the navigation back arrow until the Content Libraries center pane appears.

2 . Copy to the clipboard the link to the local content library.

a. In the center pane, click the SA-Source link.

b. In the center pane, click the Summary tab and scroll down until the Publication panel appears.

c . In the Publication panel, click Copy Link.

3. Point to the Home icon and select Content Libraries. 4. In the center pane, click Create a new content library.

The New Content Library wizard appears.

5. On the Name and location page, name the content library and verify the vCenter Server location.

a. In the Name text box, enter SA-Subscriber.

b. In the vCenter Server drop-down menu, verify that sa-vcsa-01.vclass.local is selected.

c. Click Next.

6. On the Configure content library page, configure a subscribed content library. a. Click Subscribed content library.

b. Click the Subscription URL text box and press Ctrl+V.

The subscription URL is pasted into the text box. If Ctrl+ V does not work, you must enter the URL manually.

c. Select the Enable Authentication check box.

d. In the Password text box, enter the standard lab password.

e . Click Download library content only when needed. f. Click Next.

7. On the Add storage page, select the SA-Subscriber datastore and click Next.

8 . On the Ready to complete page, click Finish.

9. View the Recent Tasks pane to monitor the task to completion. 1 0 . View the contents of the content library subscriber.

a. In the left pane, select the SA-Subscriber library. b. In the center pane, click the Templates tab.

c. On the Templates tab, verify that the SampleVM template is present.

This virtual machine template is the same one that is in the source content library. d. Verify that the Stored Content Locally column indicates No.

The SA-Subscriber library is configured to download library content only when needed. As a result, only the template 's metadata has been synchronized. The actual template has not been synchronized with the SA-Subscriber library, because it is not needed yet.

1 1 . Turn off enable automatic synchronization.

a. In the center pane, click the Summary tab.

b. In the Subscription panel, click the Edit Settings link.

c. Deselect the Enable automatic synchronization with the external content library check box.

d. Even though the Password text box appears to be populated, reenter the standard lab password.

Otherwise, the process fails.

e. Click OK.

f. In the Subscription panel, verify that automatic synchronization is off.

Task 4: Clone a Template to the Source Library

You use vSphere Web Client to clone a virtual machine template into the published content l ibrary. 1 . Point to the Home icon and select Hosts and Clusters.

2. In the left pane, right-click the VMOl virtual machine and select Clone > Clone to Template in Library.

The Clone to Template in Content Library window appears.

3. In the Filter tab, select the SA-Source library.

4. Append -Library to the virtual machine name in the Template name text box and click OK.

5. In the Recent Tasks pane, view the tasks that start up and monitor the tasks to completion. 6. View the template list in both libraries.

a. Point to the Home icon and select Content Libraries.

b. In the left pane, select the SA-Source library.

c. In the center pane, click the Templates tab and verify that both templates are listed.

d. In the left pane, select the SA-Subscriber library.

e. In the center pane, view the Templates tab and verify that only the original template is listed.

Task 5: Synch ronize the Content Libraries

You use vSphere Web Client to synchronize the content libraries. 1 . In the center pane at the top, click the Synchronize icon.

�

@

Getti n g Started S u m m a ry C o ntlgure Templates

I

2 . In the Recent Tasks pane, monitor the task to completion.

The synchronization might take a few minutes to complete. You might need to press the synchronization icon a few times before you see both files.

3 . Verify that both the virtual machine templates appear in the SA-Subscriber library.

Task 6: Dep loy a Virtual Machine from the Library

You use vSphere Web Client to deploy a new virtual machine from the VMO I -Library template available in the SA-Subscriber library.

I . In the left pane, select the SA-Subscriber library.

2. In the center pane, right-click VMOl-Library and select New VM from T his Template.

The New Virtual Machine from Content Library wizard appears.

3. On the Select name and location page, name the virtual machine and select the inventory tree location.

a. In the Name text box, enter VM03 . b. Select SA Datacenter and click Next.

4. On the Select a resource page, expand SA Management, select sa-esxi-01.vclass.local, and click Next.

5. On the Review details page, click Next.

6. On the Select storage page, configure the virtual disk format and select a datastore.

a. Select Thin provision from the Select virtual disk format list.

b. Select None from the VM storage policy list.

c. In the Filter > Datastores tab, click SA-Shared-01 -Remote and click Next. 7. On the Select networks page, keep the default and click Next.

8 . On the Ready to complete page, click Finish.

9. View the Stored Content Locally column.

The column value changed to Yes because this template is now needed because it is used to deploy a virtual machine.

1 0 . In the Recent Tasks pane, view the tasks that are started and monitor the tasks to completion. 1 1 . Verify that the virtual machine is deployed.

a. Point to the Home icon and select Hosts and Clusters.

b. In the left pane, verify that the VM03 virtual machine is displayed in the inventory. 1 2 . Point to the Home icon and select Home.

Lab 7

Host Profiles

Objective: Use host profiles and manage compliance

In this lab, you perform the following tasks: 1 . Create and Export a Host Profile 2 . Import a Host Profile

3. Attach an ESXi Host to the Imported Host Profile

4. Run an Initial Compliance Check 5. Introduce a Configuration Drift

6. Run a Compliance Check and Remediate the Configuration Drift 7. Detach the Host Profile

Task 1 : Create and Export a Host Profile

A host profile is a configuration template that is applied to any or all ESXi hosts in a cluster to verify and enforce specific configuration rules. Normally, a host profile has a reference host.

You export a profile for importation. The imported profile lacks a reference host. 1 . In vSphere Web Client, point to the Home icon and select Policies and Profiles.

2. In the left pane, select Host Profiles.

3. Extract a host profile from an ESXi host.

a. In the Objects panel, click the Extract profile from a host icon (green plus sign).

The Extract Host Profile wizard appears.

b. On the Select Host page, click sa-esxi-0 1.vclass.local and click Next.

c. On the Name and Description page, enter Local-Profile in the Name text box and click

Next.

d. On the Ready to complete page, click Finish.

e . In the Recent Tasks pane, monitor the task to completion.

4. Export the host profile to a file.

a. In the center pane, right-click the new profile and select Export Host Profile.

b. In the warning message box, click Save.

c. Navigate to the desktop of the student machine and save the profile as pro f i l e . vp f .

Task 2: Im port a Host Profi le

You import the host profile that you exported in task 1 . Because host profiles do not store the reference host, host profiles can easily be imported and exported.

1 . At the top of the Objects panel, click the Import Host Profile icon.

Objects

'--�����������-+ Extract proL

I

1

� Loc a l- P rofile 0

2. In the Import Host Profile dialog box, import the host profile that you previously saved.

a. Click Browse, navigate to the desktop of the student machine, select the profile.vpf file, and click Open.

b. Enter Imported- Profile in the Name text box and click OK.

c. In the Recent Tasks pane, monitor the task to completion.

Task 3: Attach an ESXi Host to the Im ported Host Profile

Hosts and clusters can be attached or detached from a host profile in the host profiles view or in the Hosts and Clusters inventory.

1 . In the Objects panel, click the Imported-Profile link to navigate to that object. 2. In the center pane, click the Configure tab.

You can review and edit the comprehensive list of configuration settings that define the host profile.

3 . Select Attach/Detach Hosts and Clusters from the Actions drop-down menu. IJJ-Imported-Profile 'HJ rn ilJ' � � {§}Actions ...

Getting Started Summ ary Monitor Configun 11'.J Actions - Imported-Profile � Check Host Profile Compliance

.� Remediate.

Settings View:

q

�

The Attach/Detach Hosts and Clusters wizard appears.

4. On the Select hosts/clusters page, attach sa-esxi-0 1 .vclass.local to the host profile. a. In the Host/Cluster list, expand the SA Management cluster and select

sa-esxi-01. vclass.local.

b. Click Attach> to move the selected host to the list on the right and click Next.

A list of settings that can be customized for the first ESXi host appears. The customized values are prepopulated based on information extracted from the selected host.

c. Review the host customization settings and click Finish.

d. In the Recent Tasks pane, monitor the task to completion.

Task 4: Run an Initial Compliance Check

You run a compliance check to verify the attached host configuration against all the settings that are specified by the host profile.

1 . In the center pane, click the Monitor tab and click Compliance.

2. Select sa-esxi-01.vclass.local and click the Check Host Profile Compliance icon.

Getting Started Summary Monitor C o nfigure H o sts

[

I

r

1

�

�

�

[f

H ost/C I usle r H ost C o m p l i a nce

I�

3 . In the Recent Tasks pane, monitor the compliance check to completion.

4. Select the ESXi host and view the compliance information near the bottom of the panel .

The host is not compliant, because the IPv6 vmknic gateway configuration does not match the specification.

5 . Resolve the IPv6 configuration issue occurring on the ESXi host.

a. In the center pane, click the Configure tab.

b. Click Edit Host Profile.

The Edit Host Profile wizard appears.

c. On the Name and description page, click Next.

d. On the Edit host profile page, expand Networking configuration > Host virtual NIC.

e. Expand dvs-SA Datacenter: pg-SA Management: management.

f. Select IP address settings.

g. In the right pane, from the Vnic Default gateway for 1Pv6 routing list, select User must explicitly choose the policy option and click Finish.

h. In the Recent Tasks pane, monitor the task to completion.

6. Check the ESXi host for compliance.

a. In the center pane, click the Monitor tab.

b. Select the ESXi host and click the Check Host Profile Compliance icon.

c. In the Recent Tasks pane, monitor the compliance check to completion. d. View the Compliance panel.

e. Verify that the host is compliant.

Task 5: I ntrod uce a Configuration Drift

You test host profile compliance verification and remediation by introducing a noncompliant change on the host. The noncompliant change is that you remove the vmnic2 adapter from the dvs-Lab distributed switch.

1 . Point to the Home icon and select Networking.

2. In the left pane, right-click the dvs-Lab distributed switch and select Add and Manage Hosts.

The Add and Manage Hosts wizard appears.

3. On the Select task page, select Manage host networking and click Next. 4. On the Select hosts page, click Attached hosts.

5. In the Select member hosts window, select the sa-esxi-0 1.vclass.local check box and click OK. 6. Click Next.

7. On the Select network adapter tasks page, deselect the Manage VMkernel adapters check box and click Next.

8 . On the Manage physical network adapters page, unassign the vmnic2 adapter on sa-esxi-0 1 .vclass.local.

a. Under the sa-esxi-0 1 . vclass.local, select vmnic2 and record the attached uplink.

b. Click Unassign adapter and click Next.

c. Click OK in the warning message dialog box. 9. On the Analyze impact page, click Next.

1 0 . On the Ready to complete page, click Finish.

Task 6: Run a Compl iance C heck and Remed iate the Configuration Drift You run a compliance check to detect noncompliant configuration changes that were made to hosts attached to a host profile.

1 . Point to the Home icon and select Policies and Profiles.

2 . In the left pane, select Host Profiles.

3. In the left pane, select Imported-Profile.

4. In the center pane, click Monitor > Compliance.

5. Select the ESXi host and click the Check Host Profile Compliance icon.

6. In the Recent Tasks pane, monitor the compliance check to completion. 7. In the Compliance panel, review the compliance categories.

Q1. How do the resu lts of the compliance check differ from the compl iance check performed in task 4?

Q2. In the new category, does the specific issue reported relate to the configuration change made in task 5?

8 . Remediate the host.

a. Click the Remediate host based on its host profile icon.

Getting Started Summ ary Monitor C 1

[

I

f

1

Host/Cluster

Ii

The ESXi host is listed on the Ready to complete page .

b. Click Pre-check Remediation.

The precheck remediation takes several seconds to complete.

Q3. Will the host be put in maintenance mode?

For the host to enter maintenance mode, the virtual machines on this host must be powered off or moved to another host. All virtual machines on this host are currently powered off. c . Expand the ESXi host to review the host customization tasks to b e performed.

d. Click Finish.

9. In the Recent Tasks pane, monitor the remediation and subsequent compliance check tasks to completion.

1 0 . Verify that the host is now compliant. 1 1 . Verify the action taken by host remediation.

a. Point to the Home icon and select Networking.

b. In the left pane, select the dvs-Lab distributed switch.

c . In the center pane, click the Configure tab and click Topology on the left.

d. Verify that remediation automatically reconnected vmnic2 on sa-esxi-0 1 . vclass.local to the appropriate uplink.

Task 7: Detach the Host Profi le

Detach the host profile from sa-esxi-01 .vclass. local.

1 . Point to the Home icon and select Policies and Profiles.

2. In the left pane, click Host Profiles. 3. In the left pane, select Imported-Profile.

4. In the center pane, select Attach/Detach Hosts and Clusters from the Actions drop-down menu.

The Attach/Detach Hosts and Clusters wizard appears.

5. On the Select hosts/clusters page, detach sa-esxi-0 1 .vclass.local from the host profile.

a. In the Host/Cluster list on the right, select sa-esxi-0 1.vclass.local.

b. Click < Detach to move the selected host to the list on the left.

c. Click Next.