HP Virtual Connect Flex-10 10Gb Ethernet Module for c-Class BladeSystem - Manual (Page 147)

Virtual Connect fabrics 147
To mix FabricAttach and DirectAttach fabrics, you must create two different VC SAN fabrics because a VC
SAN fabric can only contain uplink ports of one type.
Bay groups
In a multi-enclosure environment, all enclosures must have the same VC-FC and FlexFabric module
configuration. For example, if the local enclosure has VC-FC modules in bays 3 and 4, each remote
enclosure must also have VC-FC modules in bays 3 and 4. This is called an FC bay group. The concept of the
FC bay group is applicable to both the FabricAttach and DirectAttach VC SAN fabric. This ensures that the
profile mobility rules are preserved when a server profile is moved between enclosures within the same VC
domain. For more information, see the HP Virtual Connect for c-Class BladeSystem Setup and Installation
Guide on the Installing tab of the HP BladeSystem Technical Resources website
( http://www.hp.com/go/bladesystem/documentation ).
When creating a FabricAttach VC SAN fabric in the multi-enclosure environment, consider the following:
• All VC-FC modules and FC-capable uplinks on the VC FlexFabric modules within the same bay group
must be connected to the same SAN fabric.
• All modules within the same bay group must be of the same module type and have identical cabling on
the uplink ports.
When creating a DirectAttach VC SAN fabric in the multi-enclosure environment, consider the following:
• All VC FlexFabric modules must be connected to the same 3PAR storage system(s).
• Server profile migration of a SAN-booted server between enclosures is not supported.
• For domains managed by VCEM, a server profile migration of a SAN-booted server between
enclosures within the same VCDG or between different VCDGs is not supported.