Setup and Install

Installation 34
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 enables you to establish an open communication path between two or more enclosures.
You can also directly associate 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 communicate with each other by a dedicated uplink port or a shared uplink port
defined on each enclosure. These uplinks on the two enclosures can be “teamed” using LACP because both
domains run LACP active. The link between 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.
Virtual Connect FIPS mode of operation
Beginning with version 4.30, Virtual Connect supports FIPS 140-2 Level 1 security requirements. Enabling
FIPS mode requires the use of secure protocols, standards, and procedures within the VC domain. The Virtual
Connect FIPS certification is currently based on the standards described in Federal Information Processing
Standards Publication 140-2 (http://csrc.nist.gov/publications/PubsFIPS.html).
The term FIPS mode is used throughout this document to describe the feature, not the validation status. For
information about current FIPS status of this or any other firmware version, see the following documents:
• Cryptographic Module Validation Program FIPS 140-1 and FIPS 140-2 Modules In Process List
(http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140InProcess.pdf)
• FIPS 140-1 and FIPS 140-2 Vendor List
(http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401vend.htm)
FIPS mode information and guidelines
Before enabling FIPS mode, observe the following information:
• The OA should be enabled with FIPS mode before VCM.
If FIPS mode cannot be set on the OA, perform the following procedures before enabling FIPS mode on
VCM:
o If it exists, delete the VC domain.
o Clear the VC mode from the OA.
A partial VC domain state is created when VCM discovers the local OA in VC mode. Be sure to clear
the partial VC domain state by powering off and then powering on the primary VC Enet module.
• When entering or exiting FIPS mode, the VC domain is deleted.
• The firmware must be updated to version 4.30 or higher before FIPS mode can be enabled.
• A rollback or downgrade to firmware earlier than 4.30 is not supported once the domain is in FIPS
mode.
• VC Fibre Channel modules are incompatible and cannot be configured for FIPS mode.