HP Virtual Connect Enterprise Manager 7.0 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 concepts.
© Copyright 2007, 2012 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...............................................................................................8 Key features and benefits...........................................................................................................8 Key features........................................................................................................................8 Key benefits................................................................................................................
Adding or removing remote enclosures from a multienclosure domain in VC Domain Maintenance.....................................................................................................................56 Canceling a VC Domain Maintenance task................................................................................57 Resynchronizing a VC Domain with Configuration Mismatch........................................................57 Using FlexFabric modules...........................................
Performing a Server Profile Failover.........................................................................................100 7 Managing MAC and WWN addresses.....................................................101 MAC Addresses...................................................................................................................101 Tracking individual MAC addresses........................................................................................101 Creating MAC exclusion ranges.......
Unable to complete or cancel VC Domain maintenance after enabling Expanded VLAN Capacity in VC Domains........................................................................................................................123 No error message when assigning a profile to a server with two FlexNIC ports on the same physical NIC....................................................................................................................................123 VCM shows an incorrect address for VCEM..........
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..................................................139 VC Domain Maintenance operation fails when moving Ethernet networks (VLANs tagged) from a deleted shared uplink set to another........................................................................................140 14 Support and other resources..................................................
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 10) 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: • 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. • Assigns and unassigns VC Domains to 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.
upgrading to a new version of VCEM on the same CMS, data migration with the Systems Insight Manager data migration tool is not necessary. For more information, see the HP Insight Management 7.0 Installation and Configuration Guide. To install VCEM, follow the steps provided in the HP Insight Management Installer. To access HP Insight Management online help, click the ? icon in the upper right-hand corner of the window. Removing VCEM WARNING! Removing VCEM could have significant implications.
If VCEM is a stand-alone installation, click the VCEM desktop icon. The VCEM Home page appears. 3. Enter the credentials that you entered when performing the installation. The VCEM home page appears. • If an HP SIM discovery has been performed, all Virtual Connect modules appear. • If an HP SIM discovery has not been previously performed, and no Virtual Connect modules appear, perform an HP SIM discovery before continuing. 1.
NOTE: Creating exclusion ranges is optional but highly recommended to avoid MAC/WWN addresses conflicts 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. For example: VCEM exclusion ranges need to be created for MAC or WWN addresses used by other VC Domains.
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 42). 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.
In the event of an unplanned failover, it is possible that manual intervention may be required to restore full operations. If a Virtual Connect Domain reports configuration mismatch or an out-of-sync occurrence after recovering from an unplanned failover, the following actions are recommended. • Execute Mxsync in analysis mode (mysync) to determine the nature of the failure on the VC Domain during the CMS recovery phase.
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 6 VC Domains page Table 2 (page 22) lists the columns on the VC Domains page.
Table 3 VCEM status icons (continued) Status Fail to communicate to VC Domain 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 failed. • When firmware is updating, it is under maintenance. • HP Virtual Connect Ethernet IP address has changed (through DHCP or EBIPA configuration).
sets, Fibre Channel SAN fabrics, Ethernet and Fibre Channel common settings, and SNMP Ethernet and Fibre Channel alert destinations. 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: • Multienclosure VC Domains must be configured and match the minimum number of enclosures required by the VC Domain Group. The Ethernet uplinks used by each enclosure define the minimum number of enclosures.
Table 4 MAC or WWN address and serial number range compatibility 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 VCEM-defined or user-defined Yes User-defined User-defined Yes, as long as it belongs to the same User-defined range User-defined VCEM-defined Yes, if a User-defined range is created on VCEM Factory (MAC or WWN address) Factory, VCEM-defined or User-defined Yes HP-predefined
◦ Network SNMP settings: – Read Community – System Contact – IP addresses ◦ Port Throughput Statistics ◦ VLAN Capacity – • 26 Legacy VLAN capacity or Expanded VLAN capacity Fibre Channel SAN Fabric settings: ◦ Enables SMI-S ◦ Fibre Channel SNMP settings: Read Community, System Contact, and IP addresses • Network and Fibre Channel SAN Fabrics uplinks • For each single network uplink: ◦ Network name ◦ Smart link ◦ Private Network ◦ Enable VLAN Tunneling ◦ State ◦ Network port l
• • ◦ Smart Link ◦ Private network ◦ Preferred Link Connection ◦ Preferred Link Connection Speed ◦ Maximum Link Connection ◦ Maximum Link Connection Speed ◦ Network Access Groups (associated with this network) For each Fibre Channel SAN Fabric: ◦ Fabric name ◦ If the VC Domain has firmware 2.
Table 5 Supported VC firmware VC Domain/Group VC Domain Group firmware mode 3.10 VC Domain Group firmware mode 2.3x VC Domain Group firmware mode 2.1x VC firmware 3.3x Yes Yes1 Yes1 Yes1 Yes1 Yes1 VC firmware 3.15 No Yes Yes2, 3 Yes2, 3 Yes2, 3 Yes2, 3 VC firmware 3.10 No No Yes Yes4 Yes4 Yes4 VC firmware 3.0x No No No Yes Yes5 Yes VC Domain firmware 2.3x No No No No Yes Yes6 VC Domain firmware 2.
For a VC Domain to be part of a VC Domain Group with Virtual Connect firmware 3.15 – 3.18, 3.10, 3.0x, 2.3x, and 2.1x, Hybrid VLAN Tagging, Network Access Groups, Port Throughput Statistics, Custom Module Host Names, Extended Mapped VLANs, and iSCSI Boot Assistant are not supported, as follows: • Hybrid VLAN Tagging in a VC Domain is not supported. VLAN tunneling must be uniformly enabled or disabled for all networks in the domain.
To disable this feature edit all Ethernet Networks to clear the Enable VLAN Tunneling property check box, or edit all Server Profiles to ensure that no Ethernet Adapter Connections are using Multiple Networks. • Network Access Groups are not supported. Do not create Network Access Groups on the VC Domain other than the Default Network Access Group (which is always defined by Virtual Connect by default). Figure 9 VC Domain with the Default Network Access Group plus another Network Access Group configured.
• Extended Mapped VLAN is not supported. Do not configure the VC Domain to allow for expanded VLAN capacity (Extended Mapped VLAN). Figure 11 VC Domain with Extended Mapped VLAN configured IMPORTANT: The only way to disable this feature is by deleting the entire VC Domain configuration (including server profile configuration). To delete the VC Domain configuration go to the Domain Settings menu in the Virtual Connect Manager user interface, click Configuration and then click Delete.
Figure 13 VC Domain with Storage Management Credentials To disable this feature go to the Virtual Connect Manger user interface and delete all Storage Management Credentials by clicking on Delete in the Edit drop-down menu for each Storage Management Credential. Figure 14 Deleting a Storage Management Credential Virtual Connect 3.15 features that must be disabled in a VC Domain to be part of a VC Domain Group with Virtual Connect firmware 3.10, 3.0x, 2.3x, and 2.
Figure 15 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 16 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 17 Removing all FCoE connections from server profiles Multi-blade FC connections are not supported.
Figure 18 Disabling Multi-blade FC connections Virtual Connect 3.10 features that must be disabled in a VC Domain to be part of a VC Domain Group with Virtual Connect firmware 3.0x, 2.3x and 2.1x • For VC Domain Groups with firmware mode 2.3x – All Virtual Connect 3.0x features not supported by VC firmware 2.3x must be disabled. • For VC Domain Groups with firmware mode 2.1x – All Virtual Connect 2.3x features not supported by VC firmware 2.1x must be disabled.
Figure 19 Removing Flex-10 iSCSI Connections 4. Continue selecting the last Flex-10 iSCSI connection until all connections are removed. Virtual Connect 3.0x features that must be disabled in a VC Domain to be part of a 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.
Figure 20 Server Profile configured with a FC multi-blade server 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 the additional FC SAN Connections that you want to delete. 3. Right-click and select Delete Connection. • More than 32 Ethernet network connections in a server profile is not supported. To disable this feature: 1. Log on to HP Virtual Connect Manager. 2.
Figure 21 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 a VC Domain Group with Virtual Connect firmware 2.1x • 38 Enhanced SNMP configuration is not supported.
Figure 22 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 24 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 25 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. Virtual Connect Manager 2.1x does not support the HP Virtual Connect 8-Gb 20-Port Fibre Channel Module. Virtual Connect Manager first supported this module in Virtual Connect Manager 2.3x. If you have this module in a VC Domain in 2.
2. 3. 4. 5. Click Add Key and enter the key string. 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 Management. 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.
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.
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. Select the Serial Number address range type from the following options: • Logical serial number • Factory-default 9. Click OK.
the VCEM User Guide to verify the supported VC firmware versions, and 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 24). To manage multi-enclosure VC Domains in VCEM, you must perform the following steps before adding a VC Domain to a VC Domain Group: 1.
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 101) for more information. To remove one or more VC Domains from a VC Domain Group: 1.
Working with multienclosure VC Domains VCEM supports multienclosure VC Domains. A multienclosure VC Domain is a VC Domain with one local enclosure and up to three remote enclosures. VCEM supports VC Domains with up to four BladeSystem c7000 enclosures. Within each enclosure of a multienclosure domain, the Virtual Connect Ethernet Modules must follow the same configuration rules as VC Domains with single enclosures.
Figure 29 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. • Refer to the Virtual Connect documentation available at: http://www.hp.com/go/vc for details on which Virtual Connect Ethernet modules are supported for primary and secondary roles for the VC firmware revision in your environment. • 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.
◦ Multiple Networks Link Speed Settings ◦ Server VLAN Tagging Support • Shared Uplink Set • Resetting Virtual Connect Module (soft reset) • Monitoring network ports • Configuring networks • Configuring storage • Login Banner Configuration • Enclosures Configuration: ◦ Find ◦ Import ◦ Delete • Storage Management Credentials • SNMP Configuration • Network Access Groups • Link Stability Redistribution • Support Log Configuration Some of the useful network-level operations enabl
NOTE: The following information is sample base VC Domain configuration data that is replicated to all VC Domains in the VC Domain Group.
• • • 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 link ◦ Private network ◦ Enable VLAN tunneling ◦ States ◦ Network port location ◦ Speed/duplex mode ◦ Connection mode ◦ Preferred link connection ◦ Preferred link connection speed ◦ Maximum link connection ◦ Maximum link connection speed ◦ Network Access Groups (associated with this network) ◦
1. 2. Initiate the VC Domain Maintenance. Perform changes through the Virtual Connect Manager Web interface. NOTE: When a VC Domain has a status of Under maintenance, VCEM does not allow you to perform server profile operations in any VC Domains which belong to that VC Domain Group. You can only have a maximum of one VC Domain in the VC Domain Group that has a status of Under maintenance. 3. Confirm the VC Domain changes through VCEM. To perform VC Domain Maintenance from the VC Domains page: 1.
5. 6. 7. 8. browser window. The Under Maintenance status indicates that the VC Domain is temporarily unlocked for domain, network, and storage changes. Using Virtual Connect Manager: a. Log in to Virtual Connect Manager with full user rights. b. Perform the domain restoration by selecting Domain Settings→Domain Configuration, and selecting the Backup/Restore tab. c. Click Backup configuration. Wait until the backup process completes.
• Breaking the Virtual Connect lock by using the VC command line. To resolve this issue, remove the VC Domain from the VC Domain Group. • Virtual Connect fails to respond. If the VC Domain Maintenance job fails due to poor or failed VC communication, fix the communication issue and complete VC Domain Maintenance again. Using VLAN capacity CAUTION: Virtual Connect Manager implemented with firmware version 3.
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 31 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 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.
VC Domain Group firmware mode at a later time by selecting 'Upgrade Firmware Mode' on the VC Domain Groups page. • 8. Click Cancel to discard the VC Domain configuration changes. If the VC Domain is not under maintenance, clicking Cancel closes the user interface pages. The message Virtual Connect Enterprise Manager is executing the request appears with a job ID code. Click OK to go to the Jobs page and monitor job progress.
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 67). 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 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 Enclosure Identifies the enclosure name Bay Bay number A server profile defines connections for a blade server.
Table 9 VCEM features (continued) Virtual Virtual Connect Virtual Connect Connect 3.3x 3.15 3.10 Virtual Connect Virtual Virtual Connect 3.0x Connect 2.3x 2.
Creating a server profile NOTE: Keep the following server profile dependencies in mind: • Depending on the VC Domain version, the create server profile page displays a different set of configurations. To verify the available features for each VC Domain version, see “VCEM features” (page 72). • In a VC Domain Group with VC firmware 2.1x, the 8 Gb FC module appears only if VCEM detects it. If VCEM detects the 4 Gb FC module, then the maximum port speed will be 4 Gb.
Figure 34 Network selections Figure 35 Selecting a Network window 7. Select Add iSCSI Connection in the Flex-10 iSCSI connections table to add network names, port speed and boot settings.
Figure 36 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 76 Initiator Name (required) Name used for the iSCSI initiator boot system. The initiator name length is maximum of 256 characters. If the initiator name contains nonalphanumeric characters, it must be enclosed in double quotes.
Setting Description Use DHCP (optional) Click Use DHCP to enable the following: • iSCSIParamDHCP—Allows the iSCSI ROM option to retrieve iSCSI boot parameters. This attribute default is set to disable to allow for static configurations. • DHCP Vendor ID—Required if iSCSIParamDHCP is set to enable. Used to match the value in the Vendor Class ID field in the DHCP packet with retrieving either iSCSI Boot or network parameters. The Vendor ID field is restricted to 32 characters.
Figure 37 iSCSI Boot Assistant HP recommends that you use the iSCSI Boot Assistant rather than populating the iSCSI fields manually. The main goal of the iSCSI Boot Assistant is to save time. If you run the iSCSI Boot Assistant after manually populating the iSCSI fields, the values previously entered manually will be overwritten. 1. Choose a VC Domain and the Management Targets: selection box is enabled.
the last connection to the first connection. If the maximum number of FCoE connections is reached, an error message is displayed. NOTE: Keep the following in mind: • If there are no SAN fabrics using the HP VC FlexFabric 10 Gb/24-port module uplink ports, the FCoE connections can be configured as unassigned. • A server profile with boot target configurations can only have one FC, FCoE, or iSCSI primary and secondary boot types. 12. You can create a single server profile, or multiple server profiles.
NOTE: When creating multiple server profiles, boot parameters are ignored. Edit each server profile to specify the boot parameters. 14. Click OK. The Virtual Connect Enterprise Manager is executing the request message appears. 15. 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.
• VLAN Id • Color • Label The second drop-down box defaults to Contains and you can enter part of a filter such as Name or Shared Uplink Set. If you choose Color, the drop-down box defaults to Is. 3. Click the Force same VLAN mappings as Shared Uplink Set check box to enable or disable it depending on your base configuration. Figure 40 displays the options. Figure 40 Force same VLAN mappings as Shared Uplink Set options 4. 5. Click the right-arrow to add the network to your configuration.
2. (Optional) To select the desired port speed for the connection, select Custom. The Custom Port Speed windows appears. Enter the desired port speed. Figure 41 Custom Port Speed window Deleting a server profile 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.
4. (Optional) To change the network access group: 1. Choose the Network Access Group selection box. 2. Choose another network access group. A warning message similar to the following can appear if Ethernet networks, multiple, or iSCSI connections are not associated with this network access group: VCEM will unassign all Ethernet/iSCSI connections in this server profile that are assigned to a Network with no association to the selected Network Access Group [nag1].
Use the Is/Contains combination box to search by part of a word or phrase. Click on the column heading to sort the results. Label and color filters are available only in VC Domain Group firmware mode 3.3x or later. Selecting multiple networks You can filter multiple networks the same way you filter single networks. See “Selecting a single network” (page 83) for more information. Two tables are displayed. To select the networks, click the networks in the left table and transfer them to the right table.
IMPORTANT: 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. See “Supported VC firmware ” (page 28) for the latest firmware versions. 4. 5. 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.
NOTE: If a VC Domain already contains server profiles assigned to covered bays and is upgraded to VC firmware 3.15 or later, and you unassign an existing server profile from a covered bay, it is not possible to assign it to a covered bay again. This situation can exist a if a VC Domain already contains server profiles assigned to covered bays and is upgraded to VC firmware 3.15 or later. 5.
Figure 42 Moving a server profile 4. 5. 6. In the Move to Bay list, select an available bay in which to move the new server profile. Click OK. The message Virtual Connect Enterprise Manager is executing the request appears. Click OK to go to the Jobs page and monitor progress. Moving a server profile to another bay in a different VC Domain Group This feature allows you to move profiles across VC Domain Groups. VCEM ensures that moved server profiles are compatible with the target VC Domain Group.
Figure 43 Move profile prevalidation table VCEM performs five validation steps during the exportation process as displayed in Figure 43. These five steps validate source and target resources associated with the export operation. These steps also validate feature compatibility between the server profile and the target VC Domain Group as well as certifying feature compatibility specific to network and fabric features. Table 10 describes the status for each prevalidation step.
Table 10 Prevalidation status Status Description Done Step has successfully completed. Configuration VCEM will perform some changes on the server profile in order to export it to the target VC Domain Group.
• • Confirms that the target VC Domain Group that the server profile will be exported to has a status of Configuration in synch. VC Domain Groups with other statuses such as the following list cannot receive exported server profiles: ◦ Under maintenance ◦ Incompatible firmware Ensures that the target VC Domain Group virtual MAC, WWN and Serial Number range types are compatible with addresses allocated in the selected server profile. See Table 4 (page 25)) for more information.
defined in the target VC Domain Group. Otherwise Step 4 will show a warning status at the prevalidation window. • Confirms that all VLAN network names and their associated Shared Uplink Set exist in the target VC Domain Group with the following conditions: ◦ Ethernet connections are defined as Multiple Networks. ◦ Multiple networks have the Force same VLAN mapping as Shared Uplink Sets option selected.
5. Validating Fabric data—VCEM performs the following validations for fabric connections during the export process: • 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. These two conditions are mandatory in order for the server profile FC/FCoE connection be exported successfully.
4. Power up the new server. VC Server Profile Failover operations require the source and target servers to be configured to boot-from-SAN, and can be initiated from the VCEM graphical user interface (GUI) as a one-button operation or from a command line interface (CLI). When used with the automatic event handling functionality in Systems Insight Manager, VC Server Profile Failover operations can be automatically triggered based user-defined events.
For more information about using the CLI in VCEM, see the “Failover Command Line Interface Usage in VCEM” (page 117). Initiating VC Server Profile Failover through the VCEM GUI 1. 2. 3. 4. Select an assigned server profile with an acceptable spare server. (Optional) from the Filter list, select VC Domain or VC Domain Group, and click Filter. Click VC Server Profile Failover. The Virtual Connect Enterprise Manager is executing the request message appears.
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 7.0 User Guide at http://www.hp.com/go/insightmanagement/sim/docs.
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 details check box. The following table describes the additional information that will be displayed. 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 (if 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 45 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.
Figure 46 Bay status with press and hold Assigning a server profile to a bay You can assign a server profile to a bay only if the bay is not already associated with a server profile and if the server is powered down. To assign a server profile to a bay: 1. Click the Bays tab. 2. (Optional) From the Filter list, select VC Domain or VC Domain Group, and click Filter. 3. Select the bay. 4. Click Assign Server Profile. The Assign Server Profile page appears. 5. Select an unassigned server profile. 6. Click OK.
Designating spare bays 1. 2. Select one or more Spares check box for bays that do not have a server profile applied. A asterisk symbol is displayed to indicate that the spares marked with a symbol must be confirmed. To confirm the spare, click Apply Spares. You can initiate VC Server Profile Failover either through the command line interpreter (CLI) or through the VCEM graphical user interface (GUI). Designate spares according to the service level needs and the blade models being used.
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.
6. Click OK. IMPORTANT: If the exclusion range includes external addresses, these external addresses remain external, even if the exclusion range is removed. Before deleting the exclusion range, ensure 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 a custom MAC address range 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 a custom MAC address range: 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.
Tracking individual WWN addresses Individual addresses in a WWN range (HP-predefined, VCEM-defined, or user-defined) can be monitored by clicking on the Individual addresses secondary tab within the WWN Ranges List page. 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.
Figure 49 MAC exclusion ranges Figure 50 WWN exclusion ranges 106 Managing MAC and WWN addresses
Using VCEM subranges in a federated CMS environment In a federated CMS environment, it is critical to select unique pre-defined VCEM subranges during HP Insight Management DVD installation for each CMS in the federation. This prevents the different VCEM instances from using MAC or WWNs which belong to other instances. This also results in an automatic creation of VCEM exclusion ranges for MAC or WWNs which do not belong to a particular VCEM instance.
For more information, go to: http://www.hp.com/go/matrixoe/docs, select the Product Documentation Quick Link, then look in the White Papers section for the HP Matrix Operating Environment Federated CMS Overview White Paper. Deleting WWN exclusion ranges 1. 2. 3. From the VCEM home page, under the Administration heading, click the World Wide Names hyperlink. From the Select ranges to configure list, select WWN. Select a WWN address range.
Editing custom WWN address ranges Because the maximum range size is 131,072, a large range might take a few minutes to edit. You can create one custom range. 1. From the VCEM home page, under the Administration heading, click the World Wide Names hyperlink. 2. From the Select ranges to configure link, select WWN. 3. Select a WWN address range. 4. Click Edit. 5. Edit the WWN address range as necessary.
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 logical 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 52 Jobs list The following table lists and describes the job item columns in the Jobs list.
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. Reviewing job details To review the details of a particular job, click the hyperlink of the appropriate job name. The Job Details window appears. Deleting jobs To delete a particular job or multiple jobs, click Delete. Only pending, failed, or completed jobs can be deleted.
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. 114 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.
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 7.0 supports the Microsoft Internet Explorer 8 (IE8) browser, but the underlying Virtual Connect Manager versions earlier than VC FW 3.30 only support IE8 in IE7 compatibility mode. 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.x as the preferred browsers for use with VCEM.
1. 2. 3. 4. • Access the Virtual Connect Manager user interface on the VC Domain that does not have the SFP-SR connector. Edit the network with the incorrectly labeled Auto port speed to use another port speed value (for example, 1 Gb). Save the edits. Edit the network again, and set the port speed to Auto.
1. 2. 3. • Go to the Virtual Connect Manager user interface. 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.
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 on the server profile.
To correct the IP address in VCM, complete the following steps: 1. Verify that the Windows host where VCEM is installed has its network adapters bound in the correct order. The network adaptor handling communications with VCM should be first in the list. If not, re-order the network adaptors so the network adaptor handling communications with VCM is the first one in the list. 2.
To correct this issue, register the CMS in DNS or add the CMS hostname to the Windows hosts file. A job appears with Failed status A job might fail for several reasons. For more information about the reason of job failure and how to correct the issue, see the job details: 1. From the VCEM home page, click the Jobs tab. 2. Locate the job, either by its ID or its name. 3. For detailed information about the job and how you can resolve the issue, click the task name of this job. 4.
NOTE: 3. 4. 5. 6. You must have domain privileges to log in to Virtual Connect Manager. Provide the Onboard Administrator credentials, and then follow the Virtual Connect Manager instructions. In Virtual Connect Manager, restart all servers with server profiles that report a Pending status. Verify that the servers are operating correctly. Access VCEM, and complete VC Domain Maintenance.
primary VC Module. If not, run Systems Insight Manager discovery to update the reference." To correct this issue, perform an Systems Insight Manager discovery on the Onboard Administrator IP address associated with the VC module and perform the VCEM operation again. VC Domain displays Missing External Manager lock status If the VC Domain displays a status of Missing External Manager lock icon, the external manager lock has either been suspended or removed.
To correct this issue, perform any of the following: • Ethernet VC modules are not physically available or there is a connection timeout or a network problems between VCEM and VC Ethernet modules. To correct this issue, verify the Ethernet VC Modules are still available and that there are no network-related issues with the Virtual Connect Manager. From the command line at the VCEM server, ping the VC Domain IP.
• To remove the account and release the VC Domain from VCEM control, from the Virtual Connect Manager command prompt, enter: remove external-manager Username=xyz mactype= MacStart=<> MacEnd=<> wwnType= WwnStart=<> WwnEnd=<> serverIdType= serverIdStart=<> serverIdEnd=<> NOTE: The option “-quiet” is available to suppress user confirmation prompts. This option is useful for scripting operations.
Operation fails to perform in the VC Domain or VC Domain Group under maintenance status VCEM cannot perform any operations related to VC Domains in a VC Domain Group that have the Under Maintenance icon because of any of the following: • Maintenance process has not completed by clicking Complete VC Domain Maintenance or Cancel • Maintenance job is still running. • Maintenance job fails. To resolve this issue: 1. Click the VC Domains or VC Domain Groups tab. a.
Resolving an expired license status If a VC Domain has an Expired License icon, perform the following: 1. License the enclosure with a Flexible Quantity License (FQL) VCEM license. For information on purchasing licenses, see the VCEM QuickSpecs at http://www.hp.com/go/vcem. 2. Click the VC Domain tab. 3. Select the VC Domain, and then click License. 4. Click Add Key. 5. Enter a valid FQL license key, and then click OK. 6. Click Apply License. 7. Perform the failed operation again.
• Update VC firmware according VC firmware versions supported by VCEM using the Virtual Connect Manager user interface. a. Access the Virtual Connect Manager user interface. b. Using the VC Domain account with full credentials, log in to the VC Domain. c. From the left panel, click Managing Firmware, click Upload, and then enter the firmware file. d. Click Activate. To correct this issue if the VC Domain is under VCEM management, you can either: • Remove the VC Domain from the VC Domain group.
NOTE: • Depending on your operating system, the following menu options might slightly vary. From the Control Panel: 1. Double-click Add or Remove Programs. 2. Click Insight Management. 3. Click Remove. Backing up and restoring VCEM In the event of catastrophic and complete VCEM failure, all server blades continue to operate, and the integrity of the server application and data are not compromised. VCEM can be restored to an operational state after complete loss of the VCEM Application or Database.
VCEM database is inaccessible or irretrievable with no backup, or VCEM file systems are corrupt with no backup Without a backup, the VCEM cannot restore to the original point. But the network and SAN configuration and assigned server profiles can be recovered from the Virtual Connect modules. Reinstall the VCEM to a fresh system, ensuring that the backup is well prepared on VCEM and its database on the new VCEM. For more information, see “Backing up and restoring VCEM” (page 133). To resolve this issue: 1.
2. 3. 4. Select the VC Domain that has an enclosure problem. Click Remove from VC Domain Group. Wait for the job to complete successfully. Connect the new enclosure in the network. Verify the network and SAN connections wired to the new enclosure are the same as the failed one. 5. From the interconnect bays of the failed enclosure, remove the VC/FC modules and place them in the same rear-panel positions of the Interconnect Bays in the new enclosure. 6.
VC Profile Failover fails during Onboard Administrator replacement If an enclosure has two Onboard Administrators with redundancy and one fails, then the redundant Onboard Administrator might take several minutes to take over. The VC Profile Failover operation fails when source or spare bays are associated with an enclosure while the redundant Onboard Administrator is still in the process of taking over. To resolve this issue: 1. Wait until Onboard Administrator has failed over.
In such cases, VCEM changes the VC Domain status to "Mismatch Configuration," and the VC Domain Group to, "Configuration in sync." To continue managing this VC Domain with VCEM, click VC Domain Maintenance to resynchronize the VC Domain configuration and server profiles.
3. 4. 5. 6. Provide the Onboard Administrator credentials, and then follow the Virtual Connect Manager instructions. In Virtual Connect Manager, restart all servers with server profiles that present a Pending status. Verify that the servers are operating correctly. Access VCEM, and complete VC Domain Maintenance.
To prevent the issue from happening again, perform either of the following: • Verify that the Central Management Server has the minimum hardware requirements to run VCEM. • Verify that all VC Domains are correctly communicating with the Central Management Server.
4. 5. 6. In the boot target configurations table, change all the target LUN fields to be within the allowed ranges (either a three-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, assign, and failover operations with the server profile.
14 Support and other resources Contacting HP Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • See the Contact HP worldwide website: http://w
Warranty information HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management products. HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator website: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website: http://www.hp.
Key The name of a keyboard key. Return and Enter both refer to the same key. Term The defined use of an important word or phrase. User input Commands and other text that you type. Variable The name of a placeholder in a command, function, or other syntax display that you replace with an actual value. [] The contents are optional in syntax. If the contents are a list separated by |, you must choose one of the items. {} The contents are required in syntax.
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 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.
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.
Virtual Connect Enterprise Manager (VCEM) VCEM simplifies the management of multiple HP BladeSystem enclosures that use Virtual Connect to control LAN and Storage Area Network (SAN) connectivity, helping organizations increase productivity, respond more quickly to business demands, and significantly reduce operating costs. Virtual Connect Manager (VCM) The firmware embedded software provided with each Virtual Connect module.
Index A H adding a VC Domain to a VC Domain Group, 44 adding custom MAC address ranges, 103 adding custom WWN address range, 108 adding or removing VC modules to VC Domain Group configuration, 68 assigning a profile, 85 assigning a server profile, 84 assigning a server profile to a bay, 99 HP Virtual Connect Enterprise Manager key features and benefits, 8 product introduction, 8 upgrading Virtual Connect firmware after VCEM is managing VC Domains, 113 B bays assigning a server profile to a bay, 99 power
configuring the target boot LUN, 80 copying and assigning a server profile to a bay, 85 creating a server profile, 74 deleting a server profile, 82 editing a server profile, 82 moving a server profile, 86 performing a VC server Profile Failover, 92 unassigning a server profile, 85 verifying the presence of EFI partition data, 84 server profile edit operation fails when target server is powered on, 136 Server profiles are not displaying physical port mapping and allocated bandwidth information, 138 Systems
correlating VCEM operations in Systems Insight Manager and Virtual Connect logs, 69 moving Ethernet networks (VLANs tagged) from one shared uplink to another, 69 VC Domain in VC Domain Maintenance, 50 VC Domain tasks, 41 VC Domains adding a VC Domain to a VC Domain Group, 44 cancelling a VC Domain Maintenance task, 57 creating a VC Domain Group, 42 licensing an enclosure for VCEM, 41 multienclosure, 48 removing a VC Domain from a VC Domain Group, 46 requirements for adding a VC Domain to a VC Domain Group,