HP Virtual Connect for c-Class BladeSystem Version 4.01 User Guide
Table Of Contents
- HP Virtual Connect for c-Class BladeSystem Version 4.01 User Guide
- Abstract
- Notice
- Contents
- Introduction
- HP Virtual Connect Manager
- Virtual Connect domains
- Understanding Virtual Connect domains
- Managing domains
- Managing SNMP
- Viewing the system log
- Managing SSL configuration
- HP BladeSystem c-Class enclosures
- Virtual Connect users and roles
- Understanding VC administrative roles
- Managing users
- Local Users screen
- Configuring LDAP, RADIUS, and TACACS+
- Minimum requirements
- LDAP Server Settings (LDAP Server) screen
- LDAP Server Settings (LDAP Groups) screen
- LDAP Server Settings (LDAP Certificate) screen
- RADIUS Settings (RADIUS Server) screen
- RADIUS Settings (RADIUS Groups) screen
- TACACS+ Settings screen
- Role Management (Role Authentication Order) screen
- Role Management (Role Operations) screen
- Virtual Connect networks
- Understanding networks and shared uplink sets
- Managing networks
- Network Access Groups screen
- Define Network Access Group screen
- Ethernet Settings (Port Monitoring) screen
- Ethernet Settings (Advanced Settings) screen
- Quality of Service
- IGMP Settings (IGMP Configuration) screen
- IGMP Settings (Multicast Filter Set) screen
- Define Ethernet Network screen
- Ethernet Networks (External Connections) screen
- Ethernet Networks (Server Connections) screen
- Managing shared uplink sets
- Virtual Connect fabrics
- Virtual Connect server profiles
- Understanding server profiles
- Managing MAC, WWN, and server virtual ID settings
- Managing server profiles
- Define Server Profile screen
- Creating FCoE HBA connections for a BL890c i4
- Limited Ethernet connections when using HP Virtual Connect Flex-10/10D modules
- Creating iSCSI connections
- Flex-10 iSCSI connections
- Define Server Profile screen (multiple enclosures)
- Multiple network connections for a server port
- Defining server VLAN mappings
- Fibre Channel boot parameters
- Server Profiles screen
- Edit Server Profile screen
- Assigning a server profile with FCoE connections to an HP ProLiant BL680c G7 Server Blade
- Unassigning a server profile with FCoE connections to an HP ProLiant BL680c G7 Server Blade and deleting the SAN fabric
- General requirements for adding FC or FCoE connections
- Define Server Profile screen
- Virtual Connect and Insight Control Server Deployment
- Virtual Connect modules
- Firmware updates
- Stacking Links screen
- Throughput Statistics screen
- Enclosure Information screen
- Enclosure Status screen
- Interconnect Bays Status and Summary screen
- Causes for INCOMPATIBLE status
- Ethernet Bay Summary (General Information) screen
- Ethernet Bay Summary (Uplink Port Information) screen
- Ethernet Bay Summary (Server Port Information) screen
- Ethernet Bay Summary (MAC Address Table) screen
- Ethernet Bay Summary (IGMP Multicast Groups) screen
- Ethernet Bay Summary (Name Server) screen
- Ethernet Port Detailed Statistics screen
- FC Port Detailed Statistics screen
- FC Bay Summary screen
- Interconnect Bay Overall Status icon definitions
- Interconnect Bay OA Reported Status icon definitions
- Interconnect Bay VC Status icon definitions
- Interconnect Bay OA Communication Status icon definitions
- Server Bays Summary screen
- Server Bay Status screen
- Port status conditions
- Interconnect module removal and replacement
- Virtual Connect modules
- Upgrading to an HP Virtual Connect 8Gb 24-Port FC Module
- Upgrading to an HP Virtual Connect 8Gb 20-Port FC Module
- Upgrading or removing an HP Virtual Connect Flex-10, HP Virtual Connect FlexFabric, or HP Virtual Connect Flex-10/10D module
- Upgrading to an HP Virtual Connect FlexFabric module from a VC-FC module
- Onboard Administrator modules
- Maintenance and troubleshooting
- Appendix: Using Virtual Connect with nPartitions
- Support and other resources
- Acronyms and abbreviations
- Documentation feedback
- Index
HP BladeSystem c-Class enclosures 61
The management interfaces for all enclosure Onboard Administrators and VC modules within the same VC
domain must be on the same lightly loaded subnet and highly reliable network. Overloads or loss of
connectivity can disable configuration attempts until the connectivity is re-established and synchronized with
the domain. The Onboard Administrator IP addresses used must be configured to be static. The Onboard
Administrator user credentials for all enclosures must be consistent to enable VCSU firmware updates for VC
modules in the remote enclosures. All FC-capable modules in the same horizontally adjacent bay pair (bays
1-2, 3-4, and so on) must be of the same type and position in all enclosures.
Multi-enclosure double-dense domains require similar and compatible VC-FC modules in bays 5, 6, 7, and
8 in all enclosures if FC connectivity is required. If a multi-enclosure double-dense configuration contains
incompatible VC-FC modules in bays 5, 6, 7, or 8 in the local or remote enclosures, some or all of the
compatible VC-FC modules in the remote enclosures might be designated INCOMPATIBLE after import.
Multiple enclosure requirements
Observe the following requirements when connecting multiple enclosures:
• Each enclosure must have at least one supported VC-Enet, Flex-10, or FlexFabric module installed.
• All VC-Enet, Flex-10, or FlexFabric modules must be interconnected (redundantly stacked).
• All enclosures must have the same FC and FlexFabric module configuration. For example, if bays 1 and
2 of the Primary Enclosure contain FlexFabric modules, then bays 1 and 2 of Remote Enclosures 1, 2,
and 3 must also contain FlexFabric modules.
• All enclosures must have the same HP VC Flex-10/10D module configuration. For example, if bays 1
and 2 of the Primary Enclosure contain HP VC Flex-10/10D modules, then bays 1 and 2 of Remote
Enclosures 1, 2, and 3 must also contain HP VC Flex-10/10D modules.
• A single domain supports up to four c7000 enclosures.
• When using multiple c7000 enclosures, the number of modules supported across the enclosures within
a domain is limited. A total of 16 Ethernet and 16 VC-FC type modules can be installed, with a
maximum of 4 VC-Enet or 4 VC-FC modules per enclosure. 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.
• All Onboard Administrators and VC modules must be on the same lightly loaded and highly reliable
management Ethernet network and IP subnet.
• VC modules must be running VC v3.30 or higher.
• The VC-FC and FlexFabric FC-configured uplink port configuration must be identical across all
enclosures.
• The Onboard Administrator firmware must be version 3.50 or higher.
• All Onboard Administrators must use the same user credentials because VCSU uses the primary
credentials for the remote enclosure.
• When both Primary and Standby modules in the base enclosure are taken down for maintenance or
lose power and are no longer present in the domain, you will experience a loss of the management
capabilities in the VC domain. If network and fabric uplinks were defined on the remaining enclosures,
the servers continue to have network and storage access. Both the Primary and Standby modules in the
base enclosure must be recovered to regain management access to the VC domain.