HP Virtual Connect Enterprise Manager 6.3 User Guide Abstract This document is intended to be used by technical professionals who manage multiple HP BladeSystem enclosures and use HP Virtual Connect Manager to control network connectivity. HP assumes that you have installed Virtual Connect, are familiar with the embedded Virtual Connect Manager web console, and have read the HP Virtual Connect for c-Class BladeSystem User Guide and understand its concept.
© Copyright 2007, 2011 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.
Contents 1 Introduction...............................................................................................7 Key features and benefits...........................................................................................................7 Key features........................................................................................................................7 Key benefits................................................................................................................
Using FlexFabric modules........................................................................................................49 Adding FlexFabric modules to an existing VCEM managed VC Domain....................................49 Replacing VC Ethernet modules in interconnect bays one or two with FlexFabric modules in an existing VCEM managed VC Domain...................................................................................
Adding custom MAC address ranges........................................................................................90 Editing custom MAC address ranges.........................................................................................90 Removing custom MAC address ranges.....................................................................................91 WWN Addresses...................................................................................................................
Failed to execute VCEM operation because VC firmware not supported.......................................115 Creating a server profile or adding a VC Domain to a VC Domain Group fails.............................115 Uninstalling VCEM................................................................................................................116 Backing up and restoring VCEM.............................................................................................
1 Introduction HP Virtual Connect Enterprise Manager (VCEM) 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 increase productivity, respond faster to workload and infrastructure changes, and reduce operating costs.
Key benefits • Centrally manage connectivity and workloads for hundreds of Virtual Connect Domains and thousands of HP BladeSystem server blades.
Table 1 (page 9) lists all available VCEM licenses, including Virtual Connect hardware and VCEM packaged options.
• Allows network assignments to be pre-provisioned even to empty server bays - enables rapid server deployment and limits configuration errors. • Separates server administration from LAN and SAN administration. • Enables system administrators to be self-sufficient—Add, replace, or modify servers in minutes to meet changing workload and business requirements without impacting production networks. • Relieves LAN and SAN administrators from server-centric maintenance.
• Fibre Channel boot from SAN parameters • Logical serial numbers An important benefit of Virtual Connect is that server connection profiles and associated attributes are assigned to BladeSystem enclosure bays and not hard wired to individual servers. The physical server in each bay uses the MAC and WWN assignments in the associated server connection profile instead of its default burned-in network interface (NIC) or host bus adapter (HBA) addresses.
• Create VC Domain Groups. • Assign and unassign VC Domains to VC Domain Groups. • Define server profiles and link to available LAN and SAN network resources. • Assign server profiles to BladeSystem enclosures, enclosure bays, and VC Domain Groups. • Change, move, or automatically failover server profiles to spare servers. • Rapidly install new bare-metal HP BladeSystem enclosures by assigning to a VC Domain Group.
Figure 3 Virtual Connect Enterprise Manager architecture overview Using VCEM, system administrators can quickly deploy, replace and recover servers and their associated workloads by simply assigning or reassigning the Virtual Connect server connection profile to an enclosure bay. The example in Figure 4 illustrates a server profile movement operation from “Server A” to “Server C” using VCEM.
Figure 4 VC server profile movement example VCEM home page features Virtual Connect Enterprise Manager uses a dedicated graphical user interface to access and control Virtual Connect operations, which includes the following core tasks: 14 • Discovers and imports existing VC Domains without system downtime. • Assigns and administers connection addresses for LANs (MAC) and SANs (WWN) from a central address repository. • Creates VC Domain Groups.
2 Installing and configuring VCEM This chapter describes how to install and configure VCEM. IMPORTANT: This guide assumes that you have previously installed Virtual Connect using the integrated Virtual Connect Manager, have read the HP Virtual Connect for c-Class BladeSystem User Guide, and understand its concepts. Preparing for a VCEM installation If you have VCEM 1.10 or earlier, you must first upgrade to VCEM 1.
1. 2. Choose from one of the following options: • Select Start→All Programs→ HP Insight Software→Uninstall HP Insight Software and select HP Virtual Connect Enterprise Manager. • From the Control panel, click Add or Remove Programs, select HP Insight Software, and click HP Virtual Connect Enterprise Manager. Confirm the removal. After removing HP Virtual Connect Enterprise Manager, some files might not be removed. Manually removing such files might cause an access denied error message.
NOTE: VCEM 6.3 does not support VC firmware 1.3x , 1.2x or 2.0x. If you have these versions of VC firmware, an incompatible firmware icon is displayed and VCEM may prevent some VC Domain, VC Domain group, and server profile operations. You must upgrade to at least 2.1x. See “Upgrading incompatible firmware modes and versions” (page 19) for more information.
NOTE: Creating exclusion ranges are optional but highly recommended to avoid MAC/WWN addresses conflicts in the same network. The exclusion ranges are necessary when there are VC Domains not under the control of VCEM in the same network. HP highly recommends using exclusion ranges in the following scenarios: • When VC Domains are not VCEM controlled and are using other user-defined MAC or WWN addresses that overlap with VCEM user-defined MAC or WWN ranges.
11. Create a new VC Domain Group, and then add one or more already licensed VC Domains to it. For more information on creating a new VC Domain Group, see “Creating a VC Domain Group” (page 34). IMPORTANT: In a new environment when adding VC Domains to into the VC Domain Group you must have one configured VC Domain. Any additional VC Domains can remain non-configured as they are automatically configured by VCEM.
3 Managing VC Domains This chapter describes how to use VCEM to manage VC Domains. On the VC Domains page, you can filter the VC Domain list by VC Domain Group. The default filter shows all VC Domains. Figure 5 VC Domains page Table 2 (page 20) lists the columns on the VC Domains page.
Table 3 Status icons (continued) Status Connectivity failure Icon Description Failed to connect to the VC Domain. Possible causes include: • Connection times out. • Ethernet VC Module is physically not available. • Virtual Connect Manager is failing. • VC Domain firmware is updating. • HP Virtual Connect Ethernet IP address has changed (through DHCP or EBIPA configuration). Missing external manager lock VCEM is unable to obtain the necessary permissions for External Manager user.
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 39). • VC Domain names must not already exist in VCEM. • Server profile names must not already exist in VCEM.
Table 4 MAC or WWN address and serial number range compatibility (continued) VC Domain server profiles with MAC or WWN addresses or serial number allocated as: MAC or WWN or serial number in VC Domain Group VCEM-supported VCEM-defined, HP-predefined, or user-defined VCEM-defined or user-defined Yes VCEM-Defined, HP-predefined, or user-defined Factory No The VC Domain configuration must be identical to the VC Domain Group configuration.
• ◦ Network name ◦ Smart link ◦ Private Network ◦ Enable VLAN Tunneling ◦ State ◦ Network port location ◦ Speed/duplex mode ◦ Connection mode ◦ Preferred Link Connection ◦ Preferred Link Connection Speed ◦ Maximum Link Connection ◦ Maximum Link Connection Speed • Number of networks configured in the VC Domain • For each shared network uplink: ◦ Uplink set name ◦ Network port location ◦ Speed/duplex mode ◦ Connection mode ◦ Number of VLANs tagged associated to the shared
To add an unconfigured VC Module to a VC Domain Group, the following items must be identical: • Interconnect bays location and model • Enclosure model • Uplinks of the network and Fibre Channel SAN Fabric • Power state of the VC Modules Mixed Virtual Connect firmware versions and compatibility in a VC Domain Group VCEM enables firmware compatibility using current and future versions of Virtual Connect firmware.
Figure 6 Server Profile configured with multiple FCoE connections To disable this feature: 1. Log on to HP Virtual Connect Manager. 2. Expand Server Profiles in the navigation pane and select the server profile with Multiple FCoE connections per I/O bay that you want to delete. 3. Right-click and select Delete Connection until only one connection per I/O bay remains. NOTE: Deleting connections until only one connection per I/O bay remains applies to FC connections as well as FCoE connections.
Figure 7 Deleting SAN fabrics configured with uplink ports for FCoE capable modules 5. 6. Expand Server Profiles in the navigation pane and select the server profile with FCoE connections. Right-click the last FCoE connection and select Delete Connection as displayed in the following figure: Figure 8 Removing all FCoE connections from server profiles Multi-blade FC connections are not supported.
Figure 9 Disabling Multi-blade FC connections 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 NOTE: To disable any of the FC SAN or Flex-10 iSCSI features, the last connection in the feature table must be deleted first. Flex-10 iSCSI Connections are not supported. To disable this feature: 1. Log on to HP Virtual Connect Manager. 2.
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 NOTE: Keep the following in mind: • VC 3.0x features must be disabled in order for the firmware to reside in the same groups as VC 2.3x or 2.1x firmware versions. • All Virtual Connect 2.3x features not supported by VC firmware 2.1x must be disabled. • Multi-blade FC servers are not supported.
3. Right-click on the last Ethernet connection and select Delete Connection as displayed in the following figure: Figure 12 Server profiles with more than 32 Ethernet network connections 4. Continue selecting and deleting the last connection until you have a maximum of 32 Ethernet connections. 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 • 30 Enhanced SNMP configuration is not supported.
Figure 13 Enhanced SNMP configuration Do not configure the VC Domain using the enhanced SNMP configuration. If necessary, disable the enhanced SNMP configuration by following these steps: 1. Do not configure more than five SNMP trap destinations. 2. Verify that all SNMP trap destinations follow these rules: a. The Destination Name must be in the following format: __<0 for VC-Enet and 1 for VC-FC> (for example, 192.168.1.1_public_1) b. c.
Figure 15 Disabling trap severities e. Trap categories must equal Other for either VC-Enet traps or VC-FC traps. Do not select both. From the Add a SNMP Trap Destination page, click Advanced, click More, and then select either of the following: ◦ On the VC-Enet Traps box, select Other, as shown in the following figure. ◦ On the VC-FC Traps box, select Other. Figure 16 Selecting trap categories f.
3. • Do not modify the SNMP configuration for VC Domain level. The default SNMP configuration for VC Domain level is Enabled with the Community String equaling Public. This is only available through the Virtual Connect Manager Command line interface. Fibre Channel Port Speed cannot be set to 8Gb for a HP Virtual Connect 8-Gb 20-Port Fibre Channel Module. Select any value other than 8Gb as the uplink configuration speed when defining a SAN Fabric for a HP Virtual Connect 8 Gb 20 Port Fibre Channel Module.
3. 4. 5. Select one or more unlicensed VC Domains. Click Apply License. Click OK to validate the key string. NOTE: License key fields are case-sensitive If the key string is valid, the key is added to HP Insight Software. 6. • Click Next to provide VC Domain credentials. For existing VC Domain Groups: 1. Select the VC Domain from the VC Domains page, and then click License. The License Enclosure page appears. 2. 3. Click Add Key. Enter the license key string, and then click OK.
The FC module can become incompatible in the following situations: • An HP Virtual Connect 4Gb FC module replaces an HP Virtual Connect 8Gb 24-port FC module. • An HP Virtual Connect 8Gb 24-port FC module replaces a HP Virtual Connect 4Gb FC module. • HP Virtual Connect 8Gb 24-port FC modules and HP Virtual Connect 4Gb FC modules share the same I/O bay slice (for example, an HP Virtual Connect 4Gb FC module in I/O Bay 3, and an HP Virtual Connect 8Gb 24-port FC module in I/O Bay 4.
NOTE: You cannot change any of the range types after creating the VC Domain Group. You can only select the User-Defined option for the MAC range type if a MAC custom range is defined. 7. Select the WWN address range type from the following options: • VCEM-defined • User-defined • Factory-default You can only select the User-Defined option for the WWN range type if a WWN custom range is defined. 8.
The for the and • operation cannot be performed because the VC firmware version the selected VC Domain(s) is not supported by VCEM. Refer to VCEM User Guide to verify the supported VC firmware versions, then update the VC Domain(s) firmware to a supported version. The VC Domain as well as the VC Domain Group configuration for the configured VC Domains meet the minimum requirements . For the complete list of configuration checks, see “Requirements for adding a VC Domain to a VC Domain Group” (page 22).
4. 5. 6. 7. 8. 9. Enter the user name and password for each unconfigured VC Domain. Ensure you provide VC Domain credentials with full privileges. VC Domains appear as: • Unconfigured domains, which appear in the System Name column with the unassigned name, VCD_name • Configured domains, which appear in the System Name column with their previously assigned name Enter the user name and password for the Onboard Administrator of each unconfigured VC Domain.
NOTE: Removing the VC Domain out of the VC Domain Group does not cause any changes to the MACs or WWNs currently in use in the VC Domain. Any new MACs or WWNs assigned through VCM after the VC Domain has been removed from the VC Domain Group will be assigned from the ranges designated when the VC Domain was removed from the VC Domain Group. See “Managing MAC and WWN addresses” (page 88) for more information. To remove one or more VC Domains from a VC Domain Group: 1.
Within each enclosure of a multienclosure domain, the Virtual Connect Ethernet Modules must follow the same configuration rules as VC Domains with single enclosures. However, each enclosure within the VC Domain might have a different configuration of Ethernet modules. Stacking links must enable Ethernet packets to reach all Ethernet modules within the VC Domain. All enclosures in a multienclosure VC Domain must have the same Virtual Connect Fibre Channel Module configuration.
Figure 20 VC Domain Group with VC Domains that have different numbers of enclosures A multienclosure domain can only be configured as follows: • The enclosure must be a c7000 enclosure. • Primary and secondary Virtual Connect Ethernet modules must be either the HP 1/10Gb-F Virtual Connect Ethernet Module or the HP Virtual Connect Flex-10 10Gb Ethernet Module running VC firmware 2.1x or later. • FC modules in every enclosure must match the model and disposition.
VC Domain Maintenance VC Domain Maintenance is a useful way to perform updates on a particular VC Domain without removing it from a VC Domain Group, and apply the common domain, network and storage configuration changes automatically to all other VC Domains that belong to the same VC Domain Group. VCEM accomplishes this task by temporarily enabling domain, network, and storage changes through the local Virtual Connect Manager for the selected domain.
Some of the useful storage level operations enabled during VC Domain Maintenance include changing storage configuration. VCEM detects the presence of logical server managers or upper level managers. When performing selected tasks, a prompt dialog message appears and explains the impact of performing that task from outside the logical server manager or upper level manager. The following message appears: IMPORTANT: VCEM has detected you may be using other products, such as HP Insight Dynamics – VSE.
◦ • • • 44 Maximum Link Connection – Maximum Link Connection Speed Network SNMP settings: – Enable SNMP – Read Community – System Contact – Each SNMP trap defined community and IP address Fibre Channel SAN fabric settings: ◦ Enable SMI-S ◦ Fibre Channel SNMP settings: – Enable SNMP – Read Community – System Contact – Each SNMP trap Community and IP address For each Fibre Channel fabric: ◦ • – Fabric name For each network uplink: ◦ Name ◦ State ◦ Connection mode ◦ Smart
• ◦ Native VLAN ◦ Number of VLANs tagged associated to the shared network uplinks For each uplink set name: ◦ Connection Mode ◦ Network Port Location Performing VC Domain Maintenance The VC Domain that maintenance operation comprises these steps: 1. Initiate the VC Domain Maintenance. IMPORTANT: While one VC Domain in a VC Domain Group is in maintenance mode, profile operations are prohibited for all VC Domains that are contained in that VC Domain Group.
Domain-level operations (not recommended through VC Domain Maintenance): • Configuration restoration for backup configurations performed out of VCEM control • Domain deletion To perform these domain-level operations, remove the VC Domain from VCEM, make the needed changes, and then re-import the VC Domain to VC Domain Group. Backing up and restoring domain configurations through VC Domain Maintenance 1. 2. 3. 4. 5. 6. 7. 8. Go to the VC Domains tab.
IMPORTANT: The domain configuration backup file created during VC Domain Maintenance and is valid for restoration while the VC Domain is in the VC Domain Group. The domain configuration file is not valid after the VC Domain is removed from the VC Domain Group.
Canceling a VC Domain Maintenance task Canceling a VC Domain Maintenance discards domain, network, and storage configuration changes that you have performed until now, and returns the VC Domain to the configuration that is shared by all VC Domains within a VC Domain Group.
Figure 22 Job details Using FlexFabric modules This section describes scenarios to add or replace existing Ethernet and FC modules with FlexFabric modules. Adding FlexFabric modules to an existing VCEM managed VC Domain This scenario describes how to add two extra FlexFabric modules in an existing VC Domain with Ethernet and FC modules. It also describes how to start using FlexFabric functionality in existing or new server profiles. 1. Remove the VC Domain from the existing VC Domain Group "A". 2.
2. 3. Upgrade the VC Domain firmware to the latest version for FlexFabric support. Save the configuration. IMPORTANT: HP recommends that you save the configuration so that if there is a problem with the VC firmware upgrade you can restore the system to the last configuration snapshot. 4. Unassign any Flex-10 NICs with profile connections that are attached to the interconnect bays being replaced. This can be done by unassigning the Ethernet connection in the profile.
12. Edit an existing server profile and an iSCSI connection and boot option that uses the FlexFabric uplink port. 13. Create a new server profile and add a network connection that uses the FlexFabric uplink port. 14. Create a new server profile and add a iSCSI connection and iSCSI boot that uses the FlexFabric uplink port.
9. 10. 11. 12. 13. Remove the existing modules that are not FlexFabric from both horizontally adjacent bays three to eight. Add the two existing VC modules in both horizontally adjacent bays three and four with appropriate FC SFP+ transceivers. Create new networks with FC SAN fabrics linked to the new FlexFabric module uplink ports. Reassign the Ethernet connections in server profiles or add new connections to the server profiles, depending on what was selected in Step 4 and Step 7.
4 Managing VC Domain groups This section describes the management of Virtual Connect (VC) Domain Groups using VCEM. A VC Domain consists of an HP BladeSystem enclosure, a set of associated Virtual Connect Ethernet and Fibre Channel interconnect modules, and server blades that are managed together by a single instance of Virtual Connect Manager. The VC Domain contains specified networks, server profiles, and user accounts that simplify the setup and administration of server connections.
Table 8 (page 54) describes VC Domain Group icons and status on the page. Table 8 Group icons and status Status Icon Description Configuration in synch All VC Domains that belong to this VC Domain Group share the same domain configuration Under maintenance VC Domain is unlocked for domain, network, and storage changes through the Virtual Connect Manager. After completing the domain, network and storage changes, you must confirm the new VC Domain configuration in VCEM.
4. 5. Find and import the necessary remote enclosures in the correct order through Virtual Connect Manager. Go to Systems Insight Manager and perform a manual discovery on Onboard Administrator IP address of all related VC Domain enclosures. If you are using the HP VC FlexFabric 10 Gb 24-port module, ensure that the module status is compatible. If the module is incompatible, an error message appears. VCEM cannot manage a VC Domain that has one or more FC modules in an Incompatible state.
8. 9. From the Select MAC range type list, select whether the MAC address range type is VCEM-defined, user-defined, or factory-default. You can only select the user-defined option for MAC range type if a MAC custom range is defined. From the Select WWN range type list, select whether the WWN address range type is VCEM-defined, user-defined, or factory-default. You can only select the user-defined option for WWN range type if a WWN custom range is defined. NOTE: After upgrading from VCEM 1.20 or 1.
Connect Enterprise Manager is executing the request appears with a job ID code. 8. Click OK to go to the Jobs page and monitor job progress. Canceling a VC Domain Group maintenance task To cancel a VC Domain Group maintenance task: 1. From the VC Domain Groups page, select the VC Domain Group with status Under Maintenance. 2. Click VC Domain Maintenance. The VC Domain Group Maintenance page appears. 3. Click Cancel.
Deleting a VC Domain Group IMPORTANT: If you delete a VC Domain Group, then all unassigned server profiles within that VC Domain Group will be posted to one of the VC Domains that were part of the deleted VC Domain Group. To verify which VC Domain contains the unassigned server profiles after the VC Domain Group deletion job is completed, look at the report generated by the related job in the VCEM event.
4. Perform the following actions for each VC Domain that uses HP-predefined or user-defined ranges within the VC Domain Group that you want to remove. Factory-default MAC and WWN ranges are released back to Virtual Connect Manager as Factory-default. If factory-default MAC or WWN addresses or serial numbers are not being used, address ranges must be specified for each removed VC Domain. These address ranges must be unique and distinct to prevent assignment of duplicate addresses.
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 58). 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.
5. Search for the log entries based on timestamp. Be sure to take the time difference between the CMS and VC Domain into account. There is no specific marker for VCEM operations. VCEM operations usually are bracketed by “VCM user login” and “VCM user logout” entries for the user name “A@.” For example, CMS IP 16.84.195.136 appears in the VC log entry as a reference to “(A1684195136@16.84.195.136)” because VCEM runs on the CMS system.
5 Managing server profiles This section describes how to create and manage server profiles for use with VCEM. A Virtual Connect server profile is a logical grouping of attributes related to server connectivity that can be assigned to a server bay. A server profile can be assigned to any server bay within the VC Domain Group. VCEM requires the server to power down for any server profile operations such as create, delete, unassign, copy, move, and edit.
Item Description Cabinet Identifies the cabinet type Bay Bay number A server profile defines connections for a blade server.
Table 9 VCEM features (continued) Virtual Connect 3.15 Virtual Connect 3.10 Virtual Connect 3.0x • • • Add extended FC • connections for multi-blade systems • • Add or remove Flex-10 iSCSI connections • • iSCSI boot for Flex-10 • • Add or remove • FCoE connections • Feature Add up to 128 Ethernet connections Virtual Connect 2.3x Virtual Connect 2.
2. From the Member of VC Domain Group menu, select the VC Domain Group to which the server profile will belong. The Create New Server Profile information appears below the server profiles list. 3. In the server profile name box, enter a unique server profile name. Figure 25 displays the server profile options. Figure 25 Server profile options 4. 5. Select Single Profile. You can either leave the profile unassigned or click Select Location to make an assignment.
7. Select Add iSCSI Connection in the Flex-10 iSCSI connections table to add network names, port speed and boot settings. The following figure displays iSCSI boot settings Figure 26 iSCSI boot settings If you enter an incorrect field format, an error message with the appropriate format is displayed. The following table describes iSCSI boot setting attributes and field formatting. Setting Description iSCSI Boot Configuration Initiator Name (required) Name used for the iSCSI initiator boot system.
Setting Description None Default selection for the authentication method. CHAP or CHAPM user names and passwords Click CHAP or CHAPM to enable the following: • CHAP or CHAPM user name—Required if the authentication method is CHAP or CHAPM. This is the user name for authentication. The user name length is a maximum of 223 characters. If the user name contains nonalphanumeric characters, it must be enclosed in double quotes. • CHAP or CHAPM Secret—Required if the authentication method is CHAP or CHAPM.
Figure 27 If a server profile is not assigned to a server bay or fails to assign to a server bay, then that server profile becomes unassigned to a VC Domain Group. 12. Click OK. The Virtual Connect Enterprise Manager is executing the request message appears. 13. Click OK to go to the Jobs page and monitor job progress. NOTE: To create server profiles for Integrity Blades that boot from SAN, you must manually configure the SAN boot entries in the blade server EFI console.
To specify the LUN and a 16-digit hexadecimal number format, place the desired hexadecimal number preceded by leading zeros as shown in the following examples: • 1023 can be represented in 16-digit hexadecimal format as 00000000000003ff or 00000000000003FF (not case-sensitive). • 18446744073709551615 is represented in 16-digit hexadecimal format as ffffffffffffffff or FFFFFFFFFFFFFFFF.
5. (Optional) You can create vNet mappings based on a Shared Uplink Set. To perform this task, select Force same VLAN mappings as Shared Uplink Sets. Figure 30 Force same VLAN mappings as Shared Uplink Sets check box Configuring Network Port Speed When creating or editing a server profile, you can configure the network speed of an Ethernet network connection. You can select network speeds of 1Gb, 2Gb, 4Gb, and 8Gb, or Auto. 1.
Editing a server profile NOTE: In a VC Domain Group with VC firmware 2.1x, the 8Gb FC module appears only if VCEM detects it. If VCEM detects the 4Gb FC module, then the maximum port speed will be 4Gb. VCEM detects the presence of logical server managers or upper level managers. When performing this task, a prompt dialog message appears and explains the impact of performing that task from outside the logical server manager or upper level manager.
1. 2. 3. From the Server Profiles page, filter the server profiles by the VC Domain Group that has the unassigned server profiles. In the server profiles list, click the Assign link, or select a server to assign, and then click Assign. The Server Profile Assignment page appears. Select an available server bay to which the server profile is assigned. IMPORTANT: For VC firmware versions 3.15 and later, you are not able to assign a server profile to a covered bay.
NOTE: Boot Settings for Flex-10 iSCSI Connections or FCoE Boot Parameters are displayed if the VC Domain Group contains VC Domains with the required firmware version (3.1x or later) and VC interconnect modules with enabled FCoE and iSCSI features. • 6. 7. FCoE Boot Parameters Click OK. The message Virtual Connect Enterprise Manager (VCEM) is executing the request appears. Click OK to go to the Jobs page and monitor job progress.
4. Select the VC Domain from the VC Domain Group target in which to export the server profile and click OK. The following message is displayed: The Virtual Connect Enterprise Manager is executing the request. 5. Click OK and browse to the Jobs page to monitor the progress. If VCEM detects any errors during export or requires post-configuration steps, the Export Profile Prevalidation window opens and displays step status and further actions to take. Figure 32 displays the export prevalidation table.
1. Source resource validations—VCEM performs the following source resource validations: • Ensures that if the source server profile is assigned to a server, that the server is powered off before the export operation. NOTE: If the source server is not powered off, you must power it off and perform the export operation again. • Confirms that the source VC Domain Group that the server profile belongs to has a status of Configuration in synch.
connection using Multiple Networks, then the target VC Domain Group firmware mode must support the server VLAN mapping feature, otherwise Step 4 displays an error status in the prevalidation window (Export profile prevalidation table (page 74)). • Ensures that the Ethernet networks used in the selected server profile exist in the target VC Domain Group.
5. Validating Fabric data—VCEM performs the following validations related to the fabric connections data exportation: • Ensures that the fabric names and I/O bays exist in the target VC Domain Group. Fabric names and I/O bays used by the server profile FC and FCoE connections must match the fabric names and I/O bay positions defined in the target VC Domain Group. The two conditions are mandatory in order for the server profile FC/FCoE connection be exported successfully.
When selecting a target server from a pool of defined spare systems, VC Server Profile Failover automatically chooses the same server model as the source server. System administrators can use VC Server Profile Failover to perform the rapid and cost effective recovery of physical servers within the same VC Domain Group with minimal administrator intervention. IMPORTANT: When you perform a VC Server Profile Failover, no reference is provided to the VC Domain from Systems Insight Manager.
Initiating VC Server Profile Failover through the VCEM GUI 1. 2. Select an assigned server profile with an acceptable spare server. Click VC Server Profile Failover. The Virtual Connect Enterprise Manager is executing the request message appears. NOTE: For VC firmware versions 3.15 and later, you are not able to assign a server profile to a covered bay. An error message similar to the following is displayed: Cannot assign server profile because the selected bay is covered. 3.
For more information about VC Server Profile Failover, see the failover white paper at http:// www.hp.com/go/vcem. For more information about Automatic Event Handling, see the HP Systems Insight Manager User Guide at http://www.hp.com/go/hpsim.
6 Managing enclosure bay assignments Only the bays that are inside a VC Domain Group appear on the Bays page. Bays can be filtered by selecting one of the following entries in the Filter list: • All—Select this option to display all bays. • VC Domain—Select this option to display all bays that exist in a specified VC Domain. The second list can be used to select a specific VC Domain to use as a filter. • VC Domain Group—Select this option to display all bays that exist in a specific VC Domain Group.
To see more information about bays, select the Show more info check box. The following table lists the additional information that appears on the screen. Item Description Server model Model of server Power Server is powered-up or powered-down UID Reports if the identification light on the device is powered-up or powered-down To see server bay status and blade server information in case there is a server in a selected bay, click the bay number, then a status window appears.
Powering down a bay To view a window displaying the power status of a bay, click the number in the Bay# column. You can power down and power up the server inside that bay by clicking the buttons. Figure 34 Window displaying the power status of a bay To remotely power down a bay: 1. Click the Bays tab. 2. To determine the power status of the bay, click the bay number. A status window appears.
3. Depending on the power status of the bay, perform one of the following steps: • If the bay is currently powered down, then proceed to the Assigning a server profile to a bay procedure section. • If the bay is currently powered up, then click Momentary Press, which automatically powers down the bay. • If the bay is currently powered up and clicking Momentary Press does not power down the bay, then click Press and Hold.
2. 3. 4. 5. 6. (Optional) From the Filter list, select VC Domain or VC Domain Group. Select the bay for which you want to unassign a server profile. Click Unassign server profile. You are prompted to confirm the unassignment. Click OK. The Virtual Connect Enterprise Manager is executing the request message appears. Click OK to go to the Jobs page and monitor job progress. Designating spare bays 1. 2. Select one or more Spares check box for bays that do not have a server profile applied.
level manager. It is recommended to use the upper level manager to edit this Server Profile. Type YES to proceed with this operation. To proceed, you must type YES, and then click OK. VCEM does not proceed if you cut and paste YES into the field. Preconditions for VC Server Profile Failover • Source and designated spare servers must be part of the same VC Domain Group. • Source and designated spare servers must be part of the same VC Domain. • Designated spare servers are powered off.
The two custom tools can be deleted from the Systems Insight Manager or VCEM installation with no impact other than the inability to configure automatic event handling. IMPORTANT: Enabling automated failover actions can impact other operations in a data center. Before using this feature, you must fully review potential implications to other system resources and data center services, and ensure compatibility with any other applications designed to perform automatic event handling.
7 Managing MAC and WWN addresses MAC Addresses NOTE: A "VCEM-defined” range has been reserved, from which VCEM allocates MAC addresses. VCEM no longer uses the “HP Pre-defined” range for MAC address allocation. However, server profiles created before VCEM 1.40 will continue to use the HP Pre-defined addresses already assigned to them. When using VCEM-assigned MAC addresses, you can choose between VCEM-defined MAC address ranges or user-defined MAC address ranges.
The following table lists and describes the MAC address status at Individual address page. Item Description Free Address available to use in VCEM. In use Address currently used by a server profile in VCEM. External Address Addresses used by server profiles in a VC Domain that have been released back to Virtual Connect Manager and no longer managed by VCEM. Excluded Addresses Addresses that reside in a VCEM Exclusion range list. VCEM will not allocate any address that is marked as excluded.
IMPORTANT: If the exclusion range includes external addresses, these external addresses remain external, even if the exclusion range is removed. To avoid conflicts, make sure all addresses within this range are not being used by any other VC Domain or VCEM instance on your network. Reclaiming external MAC addresses External MAC addresses are generated when a VC Domain containing server profiles is removed from a VC Domain Group configured to use user-defined MAC address ranges.
Removing custom MAC address ranges NOTE: Removing a custom MAC address range also removes its defined exclusion ranges. You must verify there are no addresses already in use for this range. To remove custom MAC address ranges: 1. From the Virtual Connect Enterprise Manager home page, under the Administration heading, click the MAC addresses hyperlink. 2. From the Select ranges to configure list, select MAC. 3. Select the custom MAC address range. 4. Click Delete. You are prompted to confirm your choice.
The following table lists and describes the WWN address status at Individual address page. Item Description Free Address available to use in VCEM. In use Address currently used by a server profile in VCEM. External Address Addresses used by server profiles in a VC Domain that has been released back to Virtual Connect Manager and no longer managed by VCEM. Excluded Addresses Addresses that reside in a VCEM Exclusion range list. VCEM will not allocate any address that is marked as excluded.
1. Plan how to divide the VCEM-Defined range between the multiple VCEM instances running in each CMS environment (primary and secondary). “VCEM exclusion ranges ” (page 93) displays VCEM-defined MAC and WWN address range parameters. Table 11 VCEM exclusion ranges 2. 3. Parameter MAC addresses WWN addresses Range size 131072 131072 Start address 00–21–54–98–00–00 50:01:43:80:02:A3:00:00 Stop address 00-21-5A-9C-FF-FF 50:01:43:80:02:A4:FF:FF Log on to each VCEM instance.
• Exclusion_range_WWN_1 is equal to 50:01:43:80:02:A3:00:00 to 50:01:43:80:02:A3:AA:A9 • Exclusion_range_WWN_2 is equal to 50:01:43:80:02:A4:55:54 to 50:01:43:80:02:A4:FF:FF For CMS #3, create one MAC and one WWN exclusion range for other VCEM-Defined addresses in use: • MAC_Exclusion_Range is equal to 00-21-54-9B-00-00 to 00-21-54-9C-55-53 • WWN_Exclusion_Range is equal to 50:01:43:80:02:A3:00:00 to 50:01:43:80:02:A4:55:53 Deleting WWN exclusion ranges 1. 2. 3.
Figure 40 WWN Ranges List page 3. 4. 5. Select a WWN address range. The exclusion range must be contained within the address range to which the exclusion range belongs. Valid WWN ranges cannot contain all 0s or all Fs and cannot have an F within either of the first two octets. Click the Exclusion ranges tab. To create the exclusion range, click New.
Adding custom WWN address ranges Because the maximum range size is 131,072, a large range might take a few minutes to create. You can create one custom range. To add WWN custom address ranges: 1. From the Virtual Connect Enterprise Manager home page, under the Administration heading, click the World Wide Names hyperlink. 2. From the Select ranges to configure link, select WWN. 3. Click Add custom. The Add Custom WWN Address Range information appears. 4. Enter the custom WWN address range. 5. Click OK.
8 Working with Logical Serial Numbers This section describes how to view logical serial numbers that exist in server profiles being managed by VCEM. These numbers are displayed for informational purposes. Logical serial numbers move with a server profile. The virtual serial number is a 10-character string.
9 Tracking VCEM job status Jobs The Jobs list provides detailed information about jobs that have occurred and are related to VCEM. To view these jobs, click the Jobs tab. The Jobs list appears. From this list, you can perform the following tasks: • Review a summary of jobs • Select and review details of jobs • Select and delete jobs Figure 42 Jobs list The following table lists and describes the job item columns in the Jobs list.
Job status message window When a function is performed, a job is created. A message window appears displaying the Job ID. Details of the job can be viewed in the Jobs tab. When jobs are created, events might also be created in Systems Insight Manager. VCEM limits the number of jobs that it displays to 65,000. If the limit is reached, then only the most recent 65,000 jobs are viewable. To keep the list smaller, you can select the jobs to be deleted, and then click Delete.
10 Upgrading Virtual Connect firmware after VCEM is managing VC Domains The process for upgrading Virtual Connect (VC) firmware requires extra steps when VCEM is managing the VC Domain. VCEM gains exclusive access to managed domains. However, using the VC Domain Maintenance capability, the Virtual Connect Manager can be used to upgrade VC firmware while the VC Domain is being managed by VCEM.
6. 7. To apply the changes, click Complete VC Domain Maintenance. The Virtual Connect Enterprise Manager is executing the request message appears with a job ID code. Click OK to go to the Jobs page and monitor job progress.
11 Removing an external manager account For VCEM to manage VC Domains (using the Virtual Connect Manager, the embedded software in a Virtual Connect Ethernet module) VCEM uses programmatic interfaces with each Virtual Connect Manager. VCEM automatically creates an external manager account in each Virtual Connect Manager for subsequent authentication. NOTE: VCEM uses a Secure Sockets Layer (SSL) connection provided by Systems Insight Manager.
3. To disable the account, from the Virtual Connect Manager command prompt, enter set external-manager Username=xyz Enabled=false If the VC Domain firmware is 2.
12 Failover Command Line Interface Usage in VCEM VCEM provides support for two types of command line interfaces: • Failover Command Line Interface—Performs several failover-related functions and is addressed in this chapter. These same functions are also available in the VCEM GUI. • The HP Virtual Connect Enterprise Manager Command Line Interface (VCEMCLI)—Can be used as an alternate method for managing common Virtual Connect operations.
Internal VCEM Error Code: 5058 Internal VCEM Error Message: Enclosure name contains too many characters - limit is 32 Performing VC Profile Failover on the specified VC Domain Bay Server... ERROR (30) - Could not initiate VC Profile Failover Internal VCEM Error Code: 5009 Internal VCEM Error Message: Invalid format for IP address - it must be: [0-255].[0-255].[0-255].
Show CLI usage online help This CLI command can be used to display brief usage help on the screen. >vcem -help Several CLI option keywords provide for abbreviated alternatives – that is, {-failover | -fo}.
13 Troubleshooting VCEM IMPORTANT: VCEM 6.3 supports the Microsoft Internet Explorer 8 (IE8) browser, but the underlying Virtual Connect Manager does not currently provide the same level of support. Using IE8 to perform VCEM Domain Maintenance tasks that access Virtual Connect Manager might result in failed or incomplete operations. HP recommends Microsoft Internet Explorer 7 (IE7) or Firefox 3.0 or 3.5 as the preferred browsers for use with VCEM.
2. 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 Virtual Connect 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.
Virtual Connect Manager does not accept Onboard Administrator credentials If a VC Domain is being managed by VCEM, and the Onboard Administrator is brought out of Virtual Connect Mode, the following error message appears the next time you log into Virtual Connect Manager: The HP Virtual Connect has lost its login credentials for the HP Onboard administrator (OA). The OA may have been replaced or reset to factory defaults. To ensure proper operation, these credentials must be reestablished.
1. 2. Telnet in to the Virtual Connect Manager using an SSH connection such as SSH Administrator@xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the VC Domain IP address. To determine the user name of the external manager account, enter show external-manager in the Virtual Connect Manager Command User Interface. The status of the external manager name appears. For more information, see the HP Virtual Connect Command Line Interface User Guide.
3. To disable the account, from the Virtual Connect Manager command prompt, enter set external-manager Username=xyz Enabled=false. If the VC Domain firmware is 2.
4. • You must also rediscover the Onboard Administrator related to this VC Domain again by selecting Systems Insight Manager menu Options→Identify System or Options→Discovery. Verify firmware update is in progress and wait a few minutes until the update is completed. Log into the Virtual Connect Manager (https://), and verify the VC Domain firmware status, click Domain Settings→Firmware Management.
00-21-5A-9B-00-03. In this example, the profile will be using four MAC addresses from 00-21-5A-9B-00-00 to 00-21-5A-9B-00-03. To resolve this issue: 1. Access Virtual Connect Manager for the VC Domain that is in Mismatch Configuration state. 2. Verify the server profiles inside the VC Domain searching for MAC, WWN, or VSN (Virtual Server Number) addresses that are: • Already in use by VCEM—In this case, delete the server profiles that have addresses that are reported as in use by VCEM.
2. 3. To determine the user name of the external manager account, from the Virtual Connect Manager command prompt, enter show external-manager. For this example, assume the user name returned was xyz. To disable the account, from the Virtual Connect Manager command prompt, enter set external-manager Username=xyz Enabled=false. If the VC firmware is version 2.
1. 2. 3. 4. Check if Systems Insight Manager service is up and running. Select Start→Control Panel→Administrative Tools→Services. Check the Systems Insight Manager service status. If the service is not running, right-click, and then select Start. Failed to execute VCEM operation because VC firmware not supported If the VC firmware version you have is not supported, then VCEM operations might fail to execute. For more information about supported Virtual Connect firmware, see http://www.hp.com/go/ vcem.
4. Perform the operation again. Uninstalling VCEM If there is one or more VC Domains that are being managed, then VCEM uninstall does not proceed. In this case, the VCEM uninstaller fails and a button appears in HP Insight Software. You can click the button to open an error log that instructs you of the corrective action to take. To uninstall VCEM: • Select Start→All Programs→Insight Software→Uninstall HP Insight Software.
No HP-predefined ranges for MAC and WWN addresses in VC Domain Groups After upgrading VCEM 1.40, 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 1.40 and later do not use HP-predefined ranges for MAC and WWN addresses.
NOTE: If the previous configuration used custom MAC, WWN, and Serial Number ranges, then add the same ranges to the new setup before proceeding. 4. Create new VC Domain Groups mirroring the prefail configuration specifying the currently working credentials. NOTE: Unassigned server profiles, external MAC and WWN addresses, and serial numbers are not recovered with this procedure.
7. 8. 9. Perform an Systems Insight Manager discovery against the Onboard Administrator IP address. From the VCEM home page, click the VC Domains tab. Select the same VC Domain, and then click Add to VC Domain Group. Wait for the job to complete successfully. Verify that the VC Domain meets the requirements for adding a VC Domain to a VC Domain Group. For more information, see “Requirements for adding a VC Domain to a VC Domain Group” (page 22).
Server profile edit operation fails when target server is powered on If you edit a server profile in VCEM and add, remove, or change an Ethernet network connection, add, remove, or change Fibre Channel SAN connections or change the server profile name, the edit server profile job might fail with the following message in the job details: Error during Edit server profile [Profile Name]. Details: This action could not be performed because the server is powered on.
In addition, after logging in to the Virtual Connect Manager user interface, the following warning message might appear: The HP Virtual Connect has lost its login credentials for HP Onboard Administrator (OA). OA may have been replaced or reset to factory defaults. To ensure proper operation, these credentials must be reestablished.
2. 3. Expand the Server Profiles Assigned Server Profiles left navigation panel and click the desired server profile. The Physical Port Mapping and Allocated Bandwidth information is presented inside the Ethernet Network Connection table.
NOTE: VCEM validates the format of the target LUN but does not verify that it is actually bootable. 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 VCEM requires the boot target LUN configuration and server profiles to be either a three-digit decimal between 0–255, or a 16-digit hexadecimal value between 0 and FFFFFFFFFFFFFFFF.
5. 6. 7. 8. 124 Click the VC Domains tab, for each VC Domain with "Configuration Mismatch" status, click VC Domain Maintenance. To confirm the resynchronization of the selected VC Domain with the VC Domain Group configuration, click OK. Repeat steps 1 and 2 for the VC Domain where the changes were made. In the Virtual Connect Manager user interface, create the Ethernet networks (VLANs tagged) in the desired shared uplink set.
14 Support and other resources Contacting HP Before you contact HP Be sure to have the following information available before you call contact HP: • Technical support registration number (if applicable) • Product serial number • Product model name and number • Product identification number • Applicable error message • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level HP contact information For the name of the nearest HP authorized reselle
form or on physical media as they are made available from HP. (Customers who purchase an electronic license to use are eligible for electronic updates only.) With this service, customers benefit from expedited problem resolution as well as proactive notification and delivery of software updates. For more information about this service, see http://www.hp.
Documents • HP Insight Software Quick Installation Guide • HP Insight Software Support Matrix • HP Virtual Connect Enterprise Manager Release Notes • HP Virtual Connect Enterprise Manager Command Line Interface 6.3 User Guide For more information about Virtual Connect Manager see: • BladeSystem c-Class Solution Overview • HP Virtual Connect for c-Class BladeSystem User Guide • HP Virtual Connect Manager Release Notes Websites For more VCEM resources see: http://www.hp.
NOTE 128 Support and other resources A note contains additional information to emphasize or supplement important points of the main text.
Glossary bays A device bay where the server blade is connected. HP BladeSystem c7000 Enclosure has a total of 16 device bays and HP BladeSystem c3000 Enclosure has a total of 8 device bays. blade server A server that is located in a rack or enclosure. See also enclosure, racks. central management server (CMS) A system in the management domain that executes the Systems Insight Manager software. All central operations within HP Insight Control are initiated from this system.
free Address available for VCEM allocation. full configuration rights user A user who is automatically authorized for the All Tools toolbox on all systems, including the CMS. This type of user has been given special privileges to administer the HP Insight Control software. hardware status The operating state of SNMP-based systems. A hardware status is determined by polling SNMP information from the system. Status is defined as: • Critical. HP Insight Control can no longer communicate with the system.
faster to deploy, and easier to adapt to growth and change than traditional rack-mounted or tower servers. See also enclosure, racks. shared uplink port An Ethernet uplink port that carries the traffic for multiple Virtual Connect networks. Each associated Virtual Connect network is mapped to a specific Virtual Local Area Network (VLAN) on the external connection, and appropriate VLAN tags are removed or added as Ethernet packets enter or leave the VC Domain.
Version Control Agent (VCA) An agent that is installed on a server to enable you to see the HP software installed on that server. The VCA can be configured to point to a VCRM agent, enabling easy version comparison and software update from the repository.
Index A F adding a VC Domain to a VC Domain Group, 36 adding custom MAC address ranges, 90 adding custom WWN address range, 96 adding or removing VC modules to VC Domain Group configuration, 59 allocating WWN addresses, 94 assigning a profile, 72 assigning a server profile, 71 assigning a server profile to a bay, 84 features key, 7 B J bays assigning a server profile to a bay, 84 performing a VC Server Profile Failover, 85 powering down a bay, 83 unassigning a server profile from a bay, 84 benefits ke
S the Storage arrays for the proper LUN number" appears, 123 Remove from VC Domain Group job is successful but with errors, 113 Replace VC modules in a VC Domain managed by VCEM, 118 server profile edit operation fails when target server is powered on, 120 Server profiles are not displaying physical port mapping and allocated bandwidth information, 121 Systems Insight Manager customizations for VCEM have not taken place, 121 unable to add an unconfigured VC Domain to a VC Domain Group, 110 unable to add VC
maintaining a VC Domain from the VC Domain Groups page, 56 upgrading VC Domain Group firmware mode, 57 VC Domain Groups adding or removing VC modules to VC Domain Group configuration, 59 correlating VCEM operations in Systems Insight Manager and Virtual Connect logs, 60 moving Ethernet networks (VLANs tagged) from one shared uplink to another, 60 VC Domain in VC Domain Maintenance, 42 VC Domain tasks, 33 VC Domains adding a VC Domain to a VC Domain Group, 36 cancelling a VC Domain Maintenance task, 48 creat
