HP Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem - Manual (Page 9)

Introduction 9
domain, any server blade can access any LAN or SAN connected to a VC module, and a server blade can
be used as a spare for any server blade within the same enclosure.
By stacking (cabling) the Ethernet or FlexFabric modules within the domain and connecting the FC or
FlexFabric modules to the same set of FC SANs, every server blade in the domain can be configured to
access any external network connection. With this configuration, the administrator can use Virtual Connect
Manager to deploy and migrate a server blade profile to any server in the Virtual Connect domain without
changing external LAN or SAN configurations.
Using multiple enclosures
Multiple enclosure support enables up to four c7000 enclosures to be managed within a single Virtual
Connect domain for a total of 128 servers, if double-dense support is enabled. Multiple enclosure domains
are not supported on c3000 enclosures. The VC-Enet or FlexFabric modules use stacking cables between
enclosures so that network traffic can be routed from any server Ethernet port to any uplink within the VC
domain.
By stacking (cabling) the Ethernet or FlexFabric modules within the domain, every server blade in the domain
can be configured to access any external network connection. Fibre Channel or FlexFabric modules within
different enclosures are each connected directly to the same set of FC SANs. With this configuration, the
administrator can use Virtual Connect Manager to deploy and migrate a server blade profile to any server
in the Virtual Connect domain without changing external LAN or SAN configurations.
When using multiple c7000 enclosures, there is a limit to the number of modules supported across the
enclosures within a domain. A total of 16 Ethernet and 16 VC-FC type modules can be installed. A FlexFabric
module counts as 1 Ethernet and 1 VC-FC module. Thus, up to 16 FlexFabric Modules or combinations of
FlexFabric, VC-Enet, and VC-FC modules are allowed as long as the 16-module limit for each module type
(Ethernet and FC) is not exceeded in the domain.
The management interfaces for all enclosure OAs and VC modules within the same VC domain must be on
the same lightly loaded subnet. The OA IP addresses used must be configured to be static. OA User
credential for all enclosure must be consistent to allow VCSU firmware updates for VC modules in the remote
enclosures.
Multi-enclosure double dense domains require similar and compatible FC modules in bays 5, 6, 7, and 8 in
all enclosures. If a multi-enclosure double dense configuration contains incompatible FC modules in bays 5,
6, 7, or 8 in either the local or remote enclosures, some or all of the compatible FC modules in the remote
enclosures might be designated INCOMPATIBLE after import.
Command line overview
The HP Virtual Connect Manager Command Line Interface can be used as an alternative method for
managing the Virtual Connect Manager. Using the CLI can be useful in the following scenarios:
• HP Management Applications (for example, Systems Insight Manager or Insight Control tools) can
query the Virtual Connect Manager for information these tools need to present a complete management
view of HP BladeSystem enclosures and devices. This interface is also used by the Management tools to
execute provisioning and configuration tasks to devices within the enclosure.
• Users can develop tools that utilize Virtual Connect Manager functions for data collection and for
executing provisioning and configuration tasks.
• When no browser is available or you prefer to use a command line interface, you can access
management data and perform configuration tasks.