HP Virtual Connect for c-Class BladeSystem Version 3.00 Setup and Installation Guide for HP Integrity BL8x0c i2 Series Server Blades

Installation 45
The following illustration shows an invalid FC bay configuration. Bay 4 in Remote Enclosure 1 is empty,
and Bay 3 of Remote Enclosure 2 has an Ethernet module present.
Directly connecting VC domains
In a multi-enclosure domain configuration with properly installed stacking cables, each network defined in
the domain is available to all server profiles in the domain without requiring any additional uplink ports.
This configuration allows you to establish an open communication path between two or more enclosures.
A user can also directly connect the uplinks from two enclosures from different domains so that servers in
the two domains attached to the networks configured for those uplinks can communicate with one
another. This configuration establishes a private communication path between the two enclosures.
However, the communication path is public for all of those servers and applications associated with it.
Traffic would not flow from an upstream switch over that direct connection.
The two enclosures can be connected to each other by a dedicated uplink port or a shared uplink port
defined on each enclosure. Uplinks connecting the two enclosures can be “teamed” using LACP because
both domains run LACP active. The link connecting the two enclosures cannot have any additional active
links connected to other targets. Only networks defined for that link can be shared between the two
enclosures.