Step #1: Login to vCenter and Configure VMs

Now that you understand the test topology, it’s time to start. First, you will log into vCenter and access the VMs used for our performance test.

Log in to vCenter using the LaunchPad vCenter link on the left-hand navigation pane using the login information below.
- Username: ${vcenter_user_name}@${vcenter_domain}
- Password: ${sso_password}
On the left pane of the vSphere client, navigate to the Demo VM, right click, and select Rename...
On the Rename pop-up window, rename the VM to Redis-Server and hit OK.
The renamed VM should now appear on the left panel.
Next, let’s create a new VM for the client.
From the left panel, right click on host 172.16.0.11 and click on Actions -> New Virtual Machine.
Select Deploy from template and click Next.
Select Data Center, expand the options, select Benchmark-Client-Template and click Next.
Name the VM Benchmark-Client and click Next.
Ensure the 172.16.0.11 host is selected, ensure compatibility check passes, and click Next.
Select the vSAN datastore and click Next.
Leave all boxes unchecked and click Next.
Review and confirm the settings from the previous step and click the Finish button to complete the VM creation process.
After returning to the vCenter UI, in the bottom panel under the Recent Tasks tab, watch for your VM clone task to complete.
Now that the Benchmark-Client VM is created, we will ensure the correct network adapter settings are configured.
Click on the Benchmark-Client VM to select it and click on the Action button to pull down the menu and select the Edit Settings.
Click the drop-down menu next to Network Adapter 2 and select browse to select a network to attach.
- A new selector dialog will appear.
- Select the monterey-overlay-segment-100 that we created in previous lab.
Next, activate the drop-down menu next to Network Adapter 2 to see additional settings. Ensure that the adapter type is set to VMXNET 3, and most importantly, check the UPT support box to enable UPT support. Then click OK.
After the reconfigure VM task is complete and successful, power on the VM by going to Actions -> Power -> Power On from the inventory view of your virtual machines.

Note

At this point, you will see the Benchmark-Client powered on and a message that UPT is not activated on a network adapter. This is expected since we haven’t enabled UPT within our new VM yet.
Launch the Web Console for the Benchmark-Client, and login into the VM using the credentials below.
- Username: launchpad
- Password: lp!234

Navigate to the Scripts directory using the commands below.

Copy
Copied!

            
            cd Scripts/
ls -1

Run the checkVmxDriverVersion.sh script using the command below.
Copy

Copied!
```
            
            ./checkVmxDriverVersion.sh
        
```
Note

The UPT-enabled driver is not yet loaded.
Run the mkUPT.sh script using the command below. This will load the appropriate UPT-enabled driver for the VM.
Copy

Copied!
```
            
            ./mkUPT.sh
        
```
Navigate to vCenter and verify that the UPT alert associated with Benchmark-Client VM has disappeared. Your VM is now configured with UPT and ready for the performance testing.
Before we move to the next step, verify that the two VMs are powered up. Also, make sure IP addresses are assigned. The 172.x.x.x network represents the standard vSwitch. The 10.x.x.x network represents the UPT-enabled vSwitch.
- Redis-Server
- Benchmark-Client
Once successfully logged into both Server and Client VMs, you can familiarize yourself with the environment. Both VMs (Redis-Server and Benchmark-Client) have slightly different scripts installed.

Note

The Scripts directory contains the test execution scripts. The Results directory on the Benchmark-Client will contain the results from the test runs.