Installation guide

Chapter 5: Solution Verification
55
EMC VSPEX End-User Computing: VMware Horizon View 5.3
and VMware vSphere for up to 2,000 Virtual Desktops
Implementation Guide
Post-installation checklist
The following configuration items are critical to the functionality of the solution, and
should be verified prior to deployment into production. On each vSphere server used
as part of this solution, verify that:
 The vSwitches hosting the client VLANs are configured with sufficient ports to
accommodate the maximum number of virtual machines a host can
accommodate.
 All the required virtual machine port groups are configured and each server has
access to the required VMware datastores.
 An interface is configured correctly for vMotion. Refer to the vSphere
Networking guide for details.
Refer to the list of documents in Chapter 6 for more information.
Deploy and test a single virtual desktop
Deploy a single virtual machine to verify the operation of the solution. Ensure the
virtual machine has been joined to the applicable domain, has access to the
expected networks, and that it is possible to log in.
Verify the redundancy of the solution components
To ensure that the various components of the solution maintain availability
requirements, it is important to test specific scenarios related to maintenance or
hardware failure.
1. Restart each VNX storage processor in turn and verify that the connectivity to
the VMware datastores is maintained during the operation. Complete the
following steps:
a. Log into the control station with administrator privileges.
b. Navigate to /nas/sbin.
c. Restart SPA: use the command ./navicli -h spa rebootsp.
d. During the restart cycle, check for the presence of datastores on vSphere
hosts.
e. When the cycle completes, restart SPB: ./navicli -h spb rebootsp.
2. Perform a failover of each VNX Data Mover in turn and verify that connectivity
to the VMware datastores is maintained and that connections to the CIFS file
systems are reestablished. Use the following approach for each Data Mover;
use the Unisphere interface to restart.
a. From the control station $ prompt, execute the command server_cpu
movername -reboot, where movername is the name of the Data Mover.