0% found this document useful (0 votes)
141 views6 pages

VMware Test Procedures and Results

The document describes tests to validate the redundancy and failover capabilities of a VMware environment. It lists various tests including confirming remote access, network and storage redundancy during component failures, validating VMware features like vMotion, HA, and FT. The expected results are that the virtual infrastructure and VMs should continue functioning during and after simulated component failures like host reboots, power loss, storage or network failures.

Uploaded by

ashu_dwi2002
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
141 views6 pages

VMware Test Procedures and Results

The document describes tests to validate the redundancy and failover capabilities of a VMware environment. It lists various tests including confirming remote access, network and storage redundancy during component failures, validating VMware features like vMotion, HA, and FT. The expected results are that the virtual infrastructure and VMs should continue functioning during and after simulated component failures like host reboots, power loss, storage or network failures.

Uploaded by

ashu_dwi2002
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
  • Test Names
  • Test Objectives
  • Expected Results

Test Name

Blade Test Remote Console/KVM availability for all


hosts

Blade Test Reboot

Blade Test Network Redundancy

Blade Test fibre channel Redundancy

Blade complete virtual connect module failure


Redundancy

Blade loss of power from one power supply bank

VMware Auto-Deploy able to automatically deploy


hosts

VMware Test login to vCenter Servers

vDistributed switch configuration successful backup


and restore

VMware Test vMotion and Storage vMotion

VMware Test Maintenance Mode

VMware Test Standby Mode

VMware Test High Availability

VMware Test Fault Tolerance

Add and Remove a LUN/Datastore using vCenter

Deploy SOE from VMware Template with customisation

VMware Test AD Login to ESXi Host


Test VMware Update Manager successful deploy
patches

Test vCenter Operations Manager

Test vCenter Configuration Manager

Test vCenter Infrastructure Navigator


Test Objective

Confirm that all hosts are accessible with remote console/KVM

Confirm that hosts are able to boot without errors in the BIOS
level

Confirm that networks connections between virtual connect


flex modules on back of chassis and network switch are
redundant.

Confirm that fibre connections between virtual connect flex


modules on back of chassis and fibre switch are redundant.

Confirm that the chassis and underlying Hosts and ESXi hosts
are still able to function with a complete loss of one virtual
connect flex module.
In a modern datacenter all power should come from 2
separate power supply banks, usually an A and a B. This test
simulates if one of the power supply banks would fails to the
Blade chassis.
Ensure VMware Auto-Deploy is able to automatically deploy
hosts

Ensure successful login to vCenter Servers with vSphere Client


and Web Client across both datacenters and ensure VMware
SSO (Single Sign On) working

Ensure vDistributed switch configuration successful backup


and restore
Demonstrate vMotion of VM across hosts and Storage vMotion
across datastores. Perform vMotion across chassis to check
cross chassis communication is ok.
Demonstrate automatic vMotion of VM from host entering
maintenance mode, 1 in each datacenter.
Ensure ESXi host can enter standby state and resume back
(needed for DPM to work properly)

Ensure VMware HA is working in all clusters:


In HP Onboard Administrator forcefully power off the ESXi
hosts and verify in vSphere Client if the alerts are raised and
the test VM has been restarted on another host.

Demonstrate VMware Fault Tolerance

Test Add and Remove a LUN/Datastore using vCenter 3Par


plugin
Demonstrate successful deployment of a VM from a Template
with customisation of IP and other details.
Demonstrate AD authentication on ESXi host level
Demonstrate VMware Update Manager is correctly installed

Demonstrate VMware vCenter Operations Manager

Demonstrate VMware vCenter Configuration Manager

Demonstrate VMware Infrastructure Navigator


Expected Results

All hosts should be accessible with remote console/KVM

All hosts should be reboot without any errors or warnings

With disabled Ethernet ports on virtual connect flex module


A or virtual connect flex module B, all hosts management
interfaces should respond to ping successfully, without
packet lost
With disabled fibre ports on virtual connect flex module A or
virtual connect flex module B, all hosts should still able to
connect and browse the underlying datastores on the
storage array

Even with a disabled virtual connect flex module the


infrastructure should be not affected.

Even with 50% disabled power to the chassis the


infrastructure should continue to work

VMware Auto-Deploy should be able to automatically deploy


hosts

Both vCenter servers should be accessible after login to


each of them as they are setup in Linked Mode

vDistributed switch configuration successful backup and


restore

VM should be able to live migrate across hosts and


datastores

VM should be evacuated from host and host should enter


maintenance mode

Host should enter standby mode and power back on

vSphere should detected Host failure and raise alarm.


VMware HA successfully restarted VM on another host in the
cluster.

Fault Tolerance copy of test VM should still be running when


host running primary test VM is powered off

Add and Remove a LUN/Datastore using vCenter 3Par plugin


should be successful
Working VM based on template with guest customisations
should be completed successfully
AD user should be able to log in to DCUI
Scanning and Remediating (patching) should work correctly

vCenter Operations Manager interface access through the


VIclient or vSphere web client in both sites should be
working
Login to vCenter Configuration Manager interface via
[Link] should be successful
Navigator box shows up in the vSphere web client

Test Name
Blade Test Reboot
Blade Test Network Redundancy
Blade Test fibre channel Redundancy
Blade loss of power from one po
Test vCenter Operations Manager
Test vCenter Configuration Manager
Test vCenter Infrastructure Navigator
Test VMware Update M
Test Objective
Confirm that all hosts are accessible with remote console/KVM
Demonstrate VMware Fault Tolerance
Demonstrate A
Demonstrate VMware Update Manager is correctly installed
Demonstrate VMware vCenter Operations Manager
Demonstrate VMware vCe
Expected Results 
All hosts should be accessible with remote console/KVM
All hosts should be reboot without any errors or war
Scanning and Remediating (patching) should work correctly
Navigator box shows up in the vSphere web client
vCenter Operations

You might also like