HP Insight Management-Software - Manual (Page 123)

5. Validating Fabric data—VCEM performs the following validations for fabric connections during
the export process:
•
Ensures that the fabric names and I/O bays exist in the target VC Domain Group. Fabric
names and I/O bays used by the server profile FC and FCoE connections must match
the fabric names and I/O bay positions defined in the target VC Domain Group.
These two conditions are mandatory for the server profile FC/FCoE connection be exported
successfully. If the fabric name exists in the target VC Domain Group and if the I/O port
in use by the fabric matches between the source and the target VC Domain Groups then
Step 5 is successful.
•
Confirms that the related I/O bay slice (horizontal adjacent pair of I/O bays containing
at least one VC FC or FlexFabric module) in use by the server profile connections exists
in the target VC Domain Group.
For example, consider server profile A with an FCoE connection defined as fabric
“FCoE_A” using I/O bay 3 in the source VC Domain Group which contains a VC
FlexFabric module, and you want to export this server profile to a target VC Domain
Group. In the target VC Domain Group, there is no fabric named “FCoE_A” and there
is no VC FlexFabric module in I/O bay 3. However the target VC Domain Group has
FCoE_B fabric using I/O bay 4 which contains a VC FlexFabric module that is the same
I/O bay slice the fabric “FCoE_A” was using in the source VC Domain Group.
If one of the fabrics from the I/O bay slice in use by the server profile connection does
not exist or is named differently in the target VC Domain Group, then the specific fabric
name is disassociated from the server profile FC or FCoE connection and
Step 5 displays
a Configuration status in the prevalidation window. In this case, after the export server
profile operation is completed you must edit the server profile in the target VC Domain
Group and assign an existing fabric to the FC or FCoE connections. You will also need
to configure boot options for any of these connections, if necessary, so that the server
profile storage data or boot connectivity continues to work properly.
NOTE: There is no loss of WWNs. The FC or FCoE connection will remain in the server
profile (and related WWNs as well) and only the fabric is dissociated from the connection.
•
Ensures that the source VC Domain Group I/O slice in use by server profile FC or FCoE
connections exists in the target VC Domain Group. If the I/O bay slice is not defined in
the target VC Domain Group, then
Step 5 displays a Warning status in the prevalidation
window. In this case, HP recommends that you edit the VC Server Profile and remove the
FC or FCoE connections from the source server profile that is related to the nonexistent
I/O bays in the target VC Domain Group.
NOTE: The WWNs are removed and after exporting the server profile, you need to
create new FC or FCoE connections which will allocate new WWNs address.
If there are no errors or post-installation tasks, the server profile move completes without intervention.
NOTE: When moving profiles that SAN-boot from a Direct Attached fabric to a different c-Class
enclosure, you must edit the boot parameters to reflect the appropriate address which the 3PAR
array presents to the new enclosure.
Performing a VC Server Profile Failover
Virtual Connect Server Profile Failover is a VCEM feature that enables the automated movement
of VC server profiles and associated network connections to customer-defined spare servers in a
VC Domain Group. The manual movement of a VC server profile requires the following steps to
complete the operation, but VC Server Profile Failover combines these separate steps into one
seamless task:
Performing a VC Server Profile Failover 123