HP Virtual Connect Enterprise Manager Software - Manual (Page 17)

NOTE: The LANs associated with each uplink port and the attributes of the Virtual Connect server profile
remain exactly the same; only the location of the profile has changed.
When a Virtual Connect server connection profile is moved, the associated MAC, WWN, boot from SAN
parameters and related workload always move with the profile.
From the VCEM GU,I server profiles can be moved manually or scripted using the profile failover capability
to a user-defined spare server. A server profile can be moved within the same VC Domain or to any other
Domain in the same Virtual Connect Domain Group, whether it is in the same rack, across the datacenter
or at another location. The profile movement and failover functionality provided by VCEM can be used to
provide cost-effective server blade recovery, perform proactive hardware maintenance with reduced
downtimes, and control rapid server repurposing to meet changing workload and application priorities.
When moving Virtual Connect server profiles, the fastest completion times are achieved when the
corresponding source and target servers are configured to boot-from-SAN. The automated profile failover
functionality delivered in VCEM requires a boot-from-SAN environment.
Figure 1-4 VC profile movement example
Setup and configuration summary
To set up and configure VCEM into an existing HP BladeSystem environment running Virtual Connect:
Setup and configuration summary 17