HP Virtual Connect Enterprise Manager 6.
© Copyright 2007, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents HP Virtual Connect Enterprise Manager Overview...............................................................................5 Supported VCEM components...............................................................................................................5 Minimum versions of supported platforms...........................................................................................6 Enhancements.....................................................................................
HP Virtual Connect Enterprise Manager Overview HP Virtual Connect Enterprise Manager (VCEM) version 6.2 centralizes network connection management and workload mobility for HP BladeSystem servers that use Virtual Connect to access local area networks (LANs), storage area networks (SANs), and converged network environments. VCEM helps organizations to increase productivity, respond faster to workload and infrastructure changes, and reduce operating costs.
Product Hardware platform, operating system software, or language Virtual Connect Manager firmware • • • • • 2.1x 2.3x 3.00 and 3.01 (3.0x) 3.10 3.xx (compatibility) Operating system languages • • • • • • English Japanese German French Italian Spanish IMPORTANT: For compatibility and correct VCEM operation, the HP Virtual Connect Manager and associated firmware on all managed domains must be versions 2.1x, or later. For more information about supported Virtual Connect firmware, see http://www.hp.
• New Virtual Connect profile functionality for: — Flex-10 iSCSI connections — Flex-10 iSCSI boot — TCP offload • Support for VCEM 6.2 installations on a new server or updates to existing installations of VCEM 1.20 through 6.1. NOTE: VCEM is delivered on Insight Software media 6.2, which can also be downloaded from: www.hp.com/go/vcem Prerequisites VCEM 6.2 can be installed as a new console or used to update existing installations of VCEM 1.20, 1.3x, 1.40, 6.0 or 6.
(Optional) Edit the FCoE Connections column and the FCoE Boot parameters table as necessary. You can add up to 8 connections per slice, for a maximum of 4 slices and 32 connections. If you enter the maximum connections allowed, Add is disabled and an error message is displayed.
Resolving removal of the last VC Domain from a VC Domain Group If existing unassigned profiles targeted to be deleted from a VC Domain Group reaches 1600 addresses (MAC or WWN) and the last VC Domain has lost connection with VCEM, the last domain will not be deleted. Select one of the following options to resolve this situation: • • Reestablish the VC Domain connection and try to remove the last VC Domain from VC Domain Group again.
In addition, the screenshots accompanying this text were also updated since the publication of the user guide. These changes will be reflected in future editions of the HP Virtual Connect Enterprise Manager User Guide. • If, after performing data migration, you are running Virtual Connect Manager and try to access a VCEM-managed VC Domain, the following error message appears: VC Domain locked by Virtual Connect Enterprise Manager . To resolve this issue: 1. 2. 3.
2. 3. • Select values for the Speed/Duplex of Ethernet Uplink Ports according to VC Domain Group Ethernet Uplink Port values. Go to VCEM and re-add the VC Domain to the same VC Domain Group. VCEM cannot create a VC Domain Group or add a VC Domain to a VC Domain Group when a backup VC module is discovered or if a failover of a VC module occurred in a redundancy environment. The following error message appears: The VC Domain [] cannot be managed by VCEM.
3. 4. 5. 6. Click Edit. In the boot target configurations table, change all the target LUN fields to be within the allowed ranges (either a 3-digit decimal between 0-255, or a 16-digit hexadecimal between 0 and FFFFFFFFFFFFFFFF). Click OK. Monitor the job progress until it is complete. After the operation completes, you can perform move and failover operations would be server profile. Moving Ethernet networks (VLANs tagged) from one shared uplink to another 1. 2. 3. 4. 5. 6. 7.
• • • HP Systems Insight Manager Release Notes HP Systems Insight Manager User Guide HP Systems Insight Manager Readme For more information about HP BladeSystem Integrated Manager: • • • http://h18013.www1.hp.com/products/servers/management/bsme/index.