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
Virtual Connect modules 232
Causes for INCOMPATIBLE status
When an interconnect module status is INCOMPATIBLE, details can be viewed in the System log ("System
Log (System Log) screen" on page 47). The system log provides information about why an interconnect
module is marked incompatible so that proper corrective action can be taken.
The following list provides reasons why an interconnect module might be INCOMPATIBLE and the suggested
corrective actions:
• Module adjacency
Typically, interconnect modules installed in adjacent bays must be of the same type. For more
information, see the installation guidelines in 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).
If two adjacent modules are incompatible, both modules are labeled as INCOMPATIBLE, since the rule
applies to both modules.
Corrective action: Remove the adjacent incompatible modules and replace with modules that are
compatible.
• Module replacement
If an interconnect module is being used by the domain and is physically removed, and then another
module is installed in the same bay, the new module must be the same type as the module previously
installed in the bay.
If the physically removed module was not being used by the domain, the module can be replaced with
a module of a different type.
VC-Enet modules are considered in use by the domain under the following conditions:
o Uplinks or downlinks are being used by networks/profiles.
o The module is the primary or standby module.
VC-FC Modules are considered in use by the domain under the following conditions:
o Uplink ports on the module are being used by a fabric.
o The fabric is being used by a profile connection.
Corrective action: Remove the incompatible module and replace with the previously existing module.
For more information, see "Interconnect module removal and replacement (on page 265)."
• Firmware version
Only modules with firmware versions supported by the firmware running on the primary module are
compatible. All other versions of firmware modules cause the module to be marked as INCOMPATIBLE.
Corrective action: Use VCSU to update incompatible modules to the appropriate firmware versions for
the domain. For more information on updating the firmware, see the HP BladeSystem c-Class Virtual
Connect Support Utility documentation on the Installing tab of the HP BladeSystem Technical Resources
website (http://www.hp.com/go/bladesystem/documentation).
• FC bay groups
In a multi-enclosure environment, all enclosures must have the same FC module configuration. For more
information, see "Multiple enclosure guidelines ("Multiple enclosure requirements" on page 61)."
Corrective action: Remove the incompatible module and replace it with the correct module for the
existing FC bay group.
In a c3000 enclosure, VC-FC modules are not supported in bay 2.