HP Virtual Connect Enterprise Manager 6.2 User Guide
Table Of Contents
- HP Virtual Connect Enterprise Manager 6.2 User Guide
- Table of Contents
- 1 Introduction
- 2 Installing and configuring VCEM
- 3 Managing VC Domains
- Requirements for adding a VC Domain to a VC Domain Group
- Mixed Virtual Connect firmware versions and compatibility in a VC Domain Group
- Virtual Connect 3.10 features that must be disabled in a VC Domain to be part of the VC Domain Group with Virtual Connect firmware 3.0x, 2.3x and 2.1x
- Virtual Connect 3.0x features that must be disabled in a VC Domain to be part of the VC Domain Group with Virtual Connect firmware 2.1x and 2.3x
- Virtual Connect 2.3x features that must be disabled in a VC Domain to be part of the VC Domain Group with Virtual Connect firmware 2.1x
- VC Domain tasks
- VCEM cabinet licensing
- Creating a VC Domain Group
- Adding a VC Domain to a VC Domain Group
- Removing a VC Domain from a VC Domain Group
- Working with multienclosure VC Domains
- VC Domain Maintenance
- Replicating VC Domain Group configurations to other VC Domains during VC Domain Maintenance
- Performing VC Domain Maintenance
- Backing up and restoring domain configurations through VC Domain Maintenance
- Changes in Virtual Connect Manager that might affect completing VC Domain Maintenance
- Working with HP Virtual Connect 8Gb Fibre Channel Module for c-Class BladeSystem
- Adding or removing remote enclosures from a multienclosure domain in VC Domain Maintenance
- Canceling a VC Domain Maintenance task
- Resynchronizing a VC Domain with Configuration Mismatch
- Requirements for adding a VC Domain to a VC Domain Group
- 4 Managing VC Domain groups
- Creating a VC Domain Group
- Maintaining a VC Domain from the VC Domain Groups page
- Canceling a VC Domain Group maintenance task
- Upgrading VC Domain Group firmware mode
- Deleting a VC Domain Group
- Adding or removing VC modules to VC Domain Group configuration
- Moving Ethernet networks (VLANs tagged) from one shared uplink to another
- Correlating VCEM operations in Systems Insight Manager and Virtual Connect logs
- 5 Managing server profiles
- Creating a server profile
- Configuring the target boot LUN
- Configuring multiple networks
- Configuring Network Port Speed
- Deleting a server profile
- Editing a server profile
- Assigning a server profile
- Unassigning a server profile
- Copying and assigning a server profile to a bay
- Moving a server profile
- Performing a VC Server Profile Failover
- 6 Managing enclosure bay assignments
- 7 Managing MAC and WWN addresses
- MAC Addresses
- Tracking individual MAC addresses
- Creating MAC exclusion ranges
- Deleting MAC exclusion ranges
- Reclaiming external MAC addresses
- Adding custom MAC address ranges
- Editing custom MAC address ranges
- Removing custom MAC address ranges
- WWN Addresses
- Tracking individual WWN addresses
- Creating WWN exclusion ranges
- Deleting WWN exclusion ranges
- Allocating WWN addresses
- Reclaiming external WWN addresses
- Adding custom WWN address ranges
- Editing custom WWN address ranges
- Deleting custom WWN address ranges
- 8 Working with Logical Serial Numbers
- 9 Tracking VCEM job status
- 10 Upgrading Virtual Connect firmware after VCEM is managing VC Domains
- 11 Removing an external manager account
- 12 Command Line Interface usage in VCEM
- 13 Troubleshooting VCEM
- MAC, WWN, and Serial Number management
- Adding or removing VC modules to VC Domain Group Configuration
- Unauthorized error when trying to access the VCEM home page
- A job appears with Failed status
- Enclosure has two Onboard Administrators, and one fails
- VCEM is prompting for Onboard Administrator credentials on a configured VC Domain
- Virtual Connect Manager does not accept Onboard Administrator credentials
- Unable to add VC Domain to a VC Domain Group
- Unable to add an unconfigured VC Domain to a VC Domain Group
- Cannot access VC Domain from Virtual Connect Manager after a data migration has been performed
- Cannot manage a VC Domain when VC module failover is taking place
- VC Domain displays Missing External Manager lock status
- VC Domain displays Configuration Mismatch status
- VC Domain displays Connectivity failure status
- Cannot resynchronize VC Domain that is in Configuration Mismatch state
- Operation fails to perform in the VC Domain or VC Domain Group under maintenance status
- Remove from VC Domain Group job is successful but with errors
- Resolving expired License status
- Resolving database operation errors
- Errors occur while loading VCEM pages
- Failed to execute VCEM operation because VC firmware not supported
- Creating a server profile or adding a VC Domain to a VC Domain Group fails
- Uninstalling VCEM
- Backing up and restoring VCEM
- No HP-predefined ranges for MAC and WWN addresses in VC Domain Groups
- Cannot change the MAC/WWN/Serial Number ranges in Virtual Connect Manager when there are server profiles
- VCEM database is inaccessible or irretrievable with no backup, or VCEM file systems are corrupt with no backup
- Enclosure has a hardware failure and must be replaced
- Replace VC modules in a VC Domain managed by VCEM
- Failover fails to initiate with an ERROR (30) - Could not initiate failover; nested exception is: java.net.SocketTimeoutException: Read timed out
- VC Profile Failover fails during Onboard Administrator replacement
- VCEM cannot power down ProLiant server model BL465 G1
- After a VC Domain is removed from a VC Domain Group in VCEM, a profile with external-managed status cannot be edited through Virtual Connect Manager
- Server profile edit operation fails when target server is powered on
- VC Domain status is "Mismatch Configuration" after cancel a VC Domain Maintenance operation fails
- Server profile job completed successfully but changes have not occurred
- Systems Insight Manager customizations for VCEM have not taken place
- After a server profile failover, some connections defined in the server profile are not functional
- Server profiles are not displaying physical port mapping and allocated bandwidth information
- VCEM page displays "Communication with the Systems Insight Manager server has been lost"
- VC Domain not discovered by Systems Insight Manager
- Create VC Domain Group or Add VC Domain to VC Domain Group operations fail and the message "An invalid boot LUN was entered. Check the storage arrays for the proper LUN number" appears
- Profile move, assign, or failover operations fail and the message "An invalid boot LUN was entered. Check the Storage arrays for the proper LUN number" appears
- VC Domain Maintenance operation fails when moving Ethernet networks (VLANs tagged) from a deleted shared uplink set to another
- 14 Support and other resources
- Glossary
- Index
Requirements for adding a VC Domain to a VC Domain Group
To add a configured VC Domain to a VC Domain Group, the following requirements must be met:
• The VC Domain must have the minimum number of enclosures required by the VC Domain
Group. For more information, see “Working with multienclosure VC Domains” (page 42).
• VC Domain names must not already exist in VCEM.
• Server profile names must not already exist in VCEM.
• MAC or WWN addresses or serial numbers that are assigned to a server profile must not be
in use by VCEM or in a VCEM exclusion list. If the MAC or WWN addresses or serial numbers
are user-defined, then you must define an address range in VCEM.
• If the VC Domain contains server profiles, the MAC addresses, WWNs, and the serial numbers
allocated must be compatible with the MAC, WWN, and serial number range types of the
VC Domain Group:
— A VC Domain containing server profiles with factory-default addresses can be added to
a VC Domain Group with VCEM-defined range types, and user-defined range types. To
add a VC Domain to a VC Domain Group with factory-default range types, all server
profiles of the VC Domain must be configured with factory-default addresses.
NOTE: Keep the following upgrade requirements in mind:
After upgrading from VCEM 1.20 or 1.3x to VCEM 6.2, VC Domain Groups that
were using HP-predefined ranges for MAC and WWN addresses will start using
VCEM-defined ranges for new server profiles. VCEM 6.0 and later does not use
HP-predefined ranges for MAC and WWN addresses.
If the VC Domain or VC Domain Group screen is displaying an incompatible firmware
status after upgrading from an older VCEM version, upgrade the VC firmware for
the affected VC Domains in order to make changes. See “Upgrading incompatible
firmware modes and versions” (page 24) for more information.
— A VC Domain containing server profiles with addresses allocated as user-defined range
type can be added to a VC Domain Group with a user-defined or VCEM-predefined
range type. A user-defined (custom) MAC and WWN range that includes all addresses
allocated to server profiles within the VC Domain must be defined in VCEM before adding
the domain to the VC Domain Group.
— A VC Domain containing server profiles with addresses allocated as HP-predefined range
type can be added to a VC Domain Group with an VCEM-predefined or a user-defined
range type.
— An unconfigured VC Domain without server profiles has no range type restrictions when
adding in a VC Domain to a VC Domain Group.
Table 3-3 “MAC or WWN address and serial number range compatibility” summarizes MAC or
WWN addresses, and serial number range type compatibility when adding a VC Domain to a
VC Domain Group.
Table 3-3 MAC or WWN address and serial number range compatibility
VCEM-supported
MAC or WWN or serial number in VC
Domain Group
VC Domain server profiles with MAC
or WWN addresses or serial number
allocated as:
YesVCEM-defined or user-definedVCEM-defined
YesVCEM-defined or user-definedUser-defined
YesFactoryFactory (MAC address or WWN
address)
YesVCEM-defined or user-definedFactory
Requirements for adding a VC Domain to a VC Domain Group 27