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

2. Select the desired VC Domain Group where you want to add or remove VC modules, and
then click Delete.
For more information, see “Deleting a VC Domain Group” (page 56).
3. For each VC Domain released from the VC Domain Group, insert or remove VC modules in
the corresponding enclosure, and perform the necessary domain, network, and storage
configuration changes in the VC Manager user interface.
Before VC module removal, remove the VC module uplink ports from all existing Network or
Shared Uplink settings from VC Domain configuration.
For VC module removal, from the VC Manager user interface, click Hardware
Overview→Enclosure_Name→Interconnect Bays, select the VC module at the bay you
want to remove, then click Remove from Domain.
4. Return to VCEM, click the VC Domain Groups tab, and click New. For more information
about creating a VC Domain Group, see “Creating a VC Domain Group” (page 37). At step
1, select the VC Domains to add to the new VC Domain Group. Wait until the job operation
completes. As a result, the new VC Domain Group created contains an updated configuration
reflecting the new VC modules.
NOTE: Existing server profiles cannot see new Fibre Channel SAN connections added using
these steps. However, if the fabrics were created on VC Manager, you can see the Fibre Channel
SAN connections. For more information, see “Editing a server profile” (page 68).
Moving Ethernet networks (VLANs tagged) from one shared uplink to
another
1. Click the VC Domains tab, and select a VC Domain.
2. Click VC Domain Maintenance, and enable VC Domain Maintenance by clicking Make
changes via VC Manager.
3. In Virtual Connect Manager user interface, delete the desired shared uplink sets or delete
desired Ethernet networks (VLANs tagged) from the shared uplink sets.
4. Go back to VCEM and complete VC Domain Maintenance by clicking Complete VC Domain
Maintenance.
5. Repeat steps 1 and 2.
6. In Virtual Connect Manager user interface, create Ethernet networks (VLANs tagged) to any
shared uplink set.
7. Go back to VCEM, and complete VC Domain Maintenance by clicking Complete VC Domain
Maintenance.
Correlating VCEM operations in Systems Insight Manager and Virtual
Connect logs
All VCEM operations are logged in Systems Insight Manager Audit log and provide a reference
to the VC Domain being managed. The VCEM operations related to a managed VC Domain are
also logged by Virtual Connect Manager in its system log. In an audit process for VCEM operations,
you must correlate Systems Insight Manager in Virtual Connect Manager logs. To perform this task:
1. Look for VCEM entries in Systems Insight Manager Audit Log by clicking Tasks & Logs→View
HP Systems Insight Manager Audit log.
2. Search for a VCEM operation that is starting: “Virtual Connect Enterprise Manager (VCEM) -
Starting job.”
3. You can find timestamp, VCEM operation (Job number#, Job details, Job title, VC Domain
name), and user name. For most VCEM operations you can find the related name of VC
Domain.
58 Managing VC Domain groups