Virtual Connect Enterprise Manager Quick Start Implementation Guide

77
In this test, we assume that enclosure 1 has H/W issues and we want to move the server configuration
from enclosure 1 to enclosure 2. We will use VCEM GUI to manually trigger a server profile failover from
enclosure 1 bay 1 server to enclosure 2 bay 3 server. By doing this, users can quickly boot up a new
server in another enclosure with the same LAN/SAN connectivity and OS contents. In our case, we have
a Windows 2008 R2 server running in enclosure 1 bay 1 and it is set up as boot from SAN, we’ll verify
after profile failure if the same image is loaded through SAN.
Please note, there are several conditions to meet before profile failover happens:
 In the VCEM domain group, users need to select idle servers as SPARE servers so VCEM has a
pool of idle servers to choose when users want to issue a profile failover
 Spare servers need to be powered off to be ready for server profile assignment
 Boot from SAN from the server is required if users want the spare server boots up with the same
OS image source server was using. VCEM will only move server identity like VLAN/MAC/WWN
from the source server to the spare server using the server profile concept. It’s the admin job to
make sure the source and spare servers have the same LAN/SAN connectivity and that they
have set up BFS correctly.
During profile failover, the following events will happen