Technical data

Validating the Solution
VMware Horizon View 5.3 and VMware vSphere for up to 2,000 Virtual
Desktops Enabled by Brocade Network Fabrics, EMC VNX, and EMC Next-
Generation Backup
187
Post-install checklist
The following configuration items are critical to 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 it can host.
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 using the material
in the vSphere Networking guide. Refer to the list of documents in
Appendix C of this document for more information.
Deploy and test a single virtual desktop
Deploy a virtual machine to verify the operation of the solution and the
procedure completes as expected. 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 VMware datastores is maintained during the
operation. Complete the following steps:
a. Log into control station with administrator privileges
b. Navigate to /nas/sbin
a. Restart SPA: use command ./navicli -h spa rebootsp
b. During the restart cycle, check for the presence of datastores
on vSphere hosts
c. 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 VMware datastores is maintained and that
connections to CIFS file systems are reestablished. For simplicity, use
the following approach for each Data Mover; use the Unisphere
interface to restart.