HP Virtual Connect Enterprise Manager 6.
© Copyright 2007, 2010 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About this document......................................................................................9 Intended audience..................................................................................................................................9 Publishing history....................................................................................................................................9 Related documents.....................................................................
Backing up and restoring domain configurations through VC Domain Maintenance.............................45 Changes in Virtual Connect Manager that might affect completing VC Domain Maintenance...............46 Working with HP Virtual Connect 8Gb Fibre Channel Module for c-Class BladeSystem........................46 Adding or removing remote enclosures from a multienclosure domain in VC Domain Maintenance........46 Canceling a VC Domain Maintenance task.......................................................
Reclaiming external MAC addresses...................................................................................................74 Adding custom MAC address ranges..................................................................................................75 Editing custom MAC address ranges..................................................................................................75 Removing custom MAC address ranges............................................................................
A job appears with Failed status...................................................................................................98 Enclosure has two Onboard Administrators, and one fails................................................................98 Cannot access VC Domain from Virtual Connect Manager after a data migration has been performed.................................................................................................................................
List of Figures 1-1 1-2 1-3 1-4 2-1 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 4-1 5-1 5-2 5-3 5-4 5-5 5-6 6-1 6-2 6-3 7-1 7-2 7-3 8-1 9-1 13-1 HP Virtual Connect technology..........................................................................................................14 Virtual Connect Enterprise Manager homepage .................................................................................16 Virtual Connect Enterprise Manager architecture overview...............................................
About this document Intended audience 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.
1 Introduction HP Virtual Connect Enterprise Manager (VCEM) centralizes network connectivity 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.
• Add, change, and failover servers and their workloads across the data center in minutes without impacting production networks. • Increase productivity and server-to-administrator ratios. • Release LAN and SAN administrators from routine server-centric tasks. • Scalable across small and large data centers. What's new VCEM 6.1 adds new features and support for the latest Virtual Connect hardware and firmware which includes: Virtual Connect firmware v3.
License type Part number Description VCEM software licenses 459864-B21 HP VCEM BL-c7000 Single enclosure license 459865-B21 HP VCEM BL-c7000 Single flexible quantity license – covers multiple enclosures 459866-B21 HP VCEM BL-c7000 Tracking license – quantity license used only with a current Activation Key Agreements (AKA) T9094AAE HP VCEM BL-c7000 E-LTU – Electronically delivered license (email) that can cover single or multiple c7000 enclosures 459867-B21 HP VCEM BL-c3000 Single enclosure lice
Figure 1-1 HP Virtual Connect technology The Virtual Connect architecture is integrated into every BladeSystem c-Class enclosure and built on industry standards, allowing operations with a broad range of switch brands that includes Cisco, Brocade, Juniper, BNT and HP ProCurve. Virtual Connect functionality is delivered using high performance Virtual Connect Ethernet and Fibre Channel modules that plug into the standard BladeSystem c-Class enclosure interconnect bays.
self-sufficient, so they can add, replace, and modify servers in minutes without affecting LAN and SAN availability or burdening network administration staff. Managing HP Virtual Connect To configure and manage Virtual Connect resources, HP provides options for both small and large Virtual Connect environments.
Figure 1-2 Virtual Connect Enterprise Manager homepage The following figure summarizes the Virtual Connect Enterprise Manager architecture. Figure 1-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 Virtual Connect server connection profile to an enclosure bay.
NOTE: The LANs associated with each uplink port and the attributes of the Virtual Connect server profile remain exactly the same; only the location of the profile has changed. When a Virtual Connect server connection profile is moved, the associated MAC, WWN, boot from SAN parameters and related workload always move with the profile. From the VCEM GU,I server profiles can be moved manually or scripted using the profile failover capability to a user-defined spare server.
1. 2. Verify that the Virtual Connect module and HP Onboard Administrator firmware for all VC Domains to be managed by VCEM meets the minimum requirements. For a complete list of hardware, firmware, and software requirements, see Installing and configuring VCEM.. Install the VCEM software on a host system running a supported operating system using the HP Insight Software DVD. Insight Software media can be downloaded from http://www.hp.com/go/insight. 3. 4. 5.
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.
Hypervisor Guests Services Browsers Database • Microsoft Windows Server 2008 Hyper-V SP2 • Microsoft Windows Server 2008 R2 Hyper-V • Microsoft Hyper-V Server 2008 SP2 • Microsoft Hyper-V Server 2008 R2 • VMware ESX 3.5 Update 5 • VMware ESX 4.0 Update 1 • NET 3.0 Framework or later • Simple Network Management Protocol (SNMP) • TCP/IP with DNS • Microsoft iSCSI Software Initiator 2.06, 2.07 or 2.08 • iSCSI 6.0.6001.18000 (Only required for iSCSI environments) • Mozilla Firefox 3.
HP BladeSystem Integrity server • HP ProLiant BL260c • HP ProLiant BL2x220c • HP ProLiant BL460c • HP ProLiant BL465c (G7 model supported only with Virtual Connect Flex-10) • HP ProLiant BL480c • HP ProLiant BL490c • HP ProLiant BL495c • HP ProLiant BL680c • HP ProLiant BL685c (G7 model supported only with Virtual Connect Flex-10) • HP ProLiant xw460c Blade Workstation • HP Integrity BL860c / 860c i2 • HP Integrity BL870c / 870c i2 • HP Integrity BL890c i2 Installing VCEM For serv
1. 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. If this occurs, reboot the server where VCEM is installed, and then remove the files. 2. The removal operation does not remove the following VCEM folder. C:\Program Files\HP\Virtual Connect Enterprise Manager\ The VCEM folder does not cause any system damage or prevent VCEM from future reinstallation. 3.
older firmware versions, both VCEM and the HP Management System Software Wizard will not prevent you from licensing these older firmware versions. 4. (Optional) Configure the MAC addresses to match the needs in the data center. a. From the VCEM Home page, click the Home tab. In a stand-alone VCEM installation, to return to the Home page, click the Home link on the upper right-hand corner of the screen. b. Click the MAC Addresses hyperlink. c. To create a custom range, click Add custom.
Upgrade to a supported VC firmware by performing the following steps: 1. 2. 3. 4. Select the VC domain with an incompatible status and click VC Domain Maintenance. Upgrade the managed VC Domains to the minimum VCEM 6.1 supported VC firmware version. See the HP Insight Software Support Matrix for the VCEM supported VC firmware versions. Click Complete VC Domain Maintenance to close the operation. Upgrade the VC Domain Group firmware mode to the minimum VCEM supported VC firmware.
3 Managing VC Domains VC Domains This section 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 3-1 VC Domains page The following table lists and describes the columns on the VC Domains page.
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). VCEM checks the VC Domain connectivity before executing any operation that involves Virtual Connect Manager.
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. • VC Domain names must not already exist in VCEM. • Profile names must not already exist in VCEM.
VC Domain configuration must be identical to the VC Domain Group configuration.
• 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 network uplinks • Number of shared networks configured in the VC Domain • For each VLAN-tagged associated to the shared network uplink: • • • Network name • Network state • VLAN ID • Native • Smart Link • Pr
1 2 Virtual Connect 3.0x features must be disabled for VC Domains to be in the same group as Virtual Connect 2.1x or 2.3x. Virtual Connect 2.3x features must be disabled for VC Domains to be in the same group as Virtual Connect 2.1x. NOTE: If you have a VC Domain Group 2.1x and all the VC Domains have been upgraded to Virtual Connect 2.3x, the group will not automatically function as a VC Domain Group 2.3x. To enable Virtual Connect 2.3x functionality, see Upgrading VC Domain Group Firmware Mode.
Figure 3-2 Server profiles with more than 32 Ethernet network connections 4. Continue selecting and deleting the last connection until you have a total amount 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 • Enhanced SNMP configuration is not supported.
Do not configure the VC Domain using the enhanced SNMP configuration. If necessary, disable the enhanced SNMP configuration by following these steps: 1. 2. Do not configure more than five SNMP trap destinations. 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. Select the “ipv4” option.
Figure 3-6 Selecting trap categories f. To disable Virtual Connect Manager traps, from the Add a SNMP Trap Destination page, click Advanced, and then click More. The right side must be empty, as shown in the following figure. Figure 3-7 Disabling Virtual Connect Manager traps 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.
Figure 3-8 Select any value other than 8Gb as uplink and downlink configuration speeds Select any value other than 8Gb as the downlink configuration speed when assigning a SAN Fabric for a HP Virtual Connect 8-Gb 20-Port Fibre Channel Module.
1. 2. 3. 4. 5. 6. 7. Select the VC Domain from the VC Domain page and click License. The License Enclosure page is displayed. Click Add Key. Enter the license key string, and then click OK. If the license key is valid, it is added to HP SIM. The License Enclosure page reappears displaying the number of available licenses Select the VC Domain to which you want to apply the VCEM license. Click Apply License. The VC Domain list page reappears, displaying the updated status of VC Domains.
(Optional) You can provide a new name for the unconfigured VC Domains. Valid VC Domain Group names are alphanumeric, hyphens (-), underscore (_), and cannot exceed 64 characters. 2. 3. Enter the username and password for each VC Domain. Ensure you provide VC Domain credentials with full privileges.
Adding a VC Domain to a VC Domain Group You can select the Add to VCD Group button if there is at least one VC Domain Group created, and the current selection contains VC Domains that do not belong to VC Domain Groups, and that have a valid license. Ensure that the VC Domains you select have a valid VC firmware version.
7. 8. 9. VC Domain(s) without server profiles will be overwritten by selected base VC Domain configuration defined for the VC Domain Group. In this case, VCEM validates that the selected VC Domain configurations match the VC Domain Group configuration. VC Domains that are already configured and have server profiles are not affected. Select the VC Domain Group name to which you want to add the selected VC Domains. Click OK. The Virtual Connect Enterprise Manager is executing the request message appears.
3. Perform the following actions for each VC Domain that uses HP-predefined or user-defined ranges that you want to remove from the VC Domain Group. Factory-default MAC, WWN, and serial number 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 avoid assignment of duplicate addresses.
Figure 3-9 Valid configuration of Ethernet and Fibre Channel Virtual Connect modules As in earlier versions of VCEM, all VC Domains within a VC Domain Group must have the same hardware configuration. VCEM enables each enclosure within a VC Domain with multiple enclosures to have a different Virtual Connect Ethernet module configuration, but it requires the same Virtual Connect Ethernet Module configuration across the VC Domain Group members.
Figure 3-10 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.
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.
VC Domain Group configuration replicated to other VC Domains during VC Domain Maintenance IMPORTANT: The VC Domain, network, and storage configuration changes performed during VC Domain Maintenance are automatically replicated to all other VC Domains that belong to the same VC Domain Group when the VC Domain that maintenance operation is confirmed or discarded.
• • • 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 For each shared network: • Uplink Set Name • State • Smart Link • External VLAN ID • Native VLAN • Number of VLANs tagged associated to the shared network uplinks For each uplink set name: • Connection Mod
IMPORTANT: When a VC Domain is put in VC Domain Maintenance, operations such as backup and restore Virtual Connect configurations are allowed. Restoring Virtual Connect configurations require additional care. If an old configuration is restored, verify that the configuration of this specific VC Domain remain compatible with VC Domain Group, otherwise the VC Domain will be incompatible with VCEM.
IMPORTANT: The domain configuration backup file created during VC Domain Maintenance and is valid for restoration while the VC Domain is in VC Domain Group. The domain configuration file is not valid after the VC Domain is removed from VC Domain Group.
IMPORTANT: For more information on the domain, network, and storage configurations that VCEM can replicate during completion of VC Domain Maintenance, or discard in case of a failure or cancellation of the VC Domain Maintenance operation, see VC Domain Group configuration replicated to other VC Domains during VC Domain Maintenance. To cancel a VC Domain Maintenance from the VC Domain page: 1. 2. 3. 4. Select the VC Domain with status under maintenance. Click VC Domain Maintenance.
4 Managing VC Domain Groups 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.
Item Description # of Domains Identifies the number of domains in the group The following table lists and describes VC Domain 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.
VCEM cannot manage a VC Domain that has one or more FC modules in an Incompatible state. 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. • If HP Virtual Connect 8Gb 24-port FC modules and HP Virtual Connect 4Gb FC modules share the same IO bay slice.
11. Click OK to go to the Jobs page and monitor job progress. 12. (Optional) After creating a VC Domain Group, from the HP SIM User and Authorization page, select the user authorization privileges for that VC Domain Group. See Creating a VC Domain Group” for more information. Maintaining a VC Domain from the VC Domain Group page To perform VC Domain maintenance from the VC Domain Group page: 1. 2. 3. 4. 5. 6. 7. Select the VC Domain Group on which you want to perform maintenance.
later than the current VC Domain Group firmware version. Otherwise, the upgrade firmware mode for the VC Domain Group will not be allowed. Upgrade VC Domain Group Firmware Mode enables you to upgrade the VC firmware mode of VC Domain Group according to the VC firmware versions of VC Domains that belong to the VC Domain Group. To upgrade the VC Domain Group firmware mode to a later version: 1. 2. 3. 4. 5. Select to the VC Domain Group to be upgraded.
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.
3. For each VC Domain released from the VC Domain Group, insert or remove VC modules in the corresponding enclosure, and perform the necessary domain, network, and storage configuration changes in the VC Manager user interface. Before VC module removal, remove the VC module uplink ports from all existing Network or Shared Uplink settings from VC Domain configuration.
5 Managing server profiles Profiles This section describes how to create and manage 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 profile operations such as create, delete, unassign, copy, move, and edit. For more information on this procedure, see "Bays.
A server profile defines connections for a blade server. Server profiles can include the following information: • Profile name • Logical serial number and logical UUID • Ethernet network connections and PXE settings • MAC addresses • Fibre Channel fabric connections • WWN addresses • Server boot configuration • BIOS settings Newer VC Domain versions provide a broader configuration set in the server profile.
power off the server blade to perform server profile operations with VC firmware 2.1x. However, in VC firmware 2.3x or 3.0x, you can perform these operations with the server blade powered on. Creating a profile NOTE: Keep the following profile dependencies in mind • Depending on the VC Domain version, the create profile page displays a different set of configurations. To verify the available features for each VC Domain version, see the feature set table earlier in this section.
NOTE: To create profiles for Integrity Blades that boot from SAN, you must manually configure the SAN boot entries in the blade server EFI console. Configuring the target boot LUN When creating or editing server profiles, you can specify a target boot LUN for the FC SAN connections designated as Primary and Secondary in the boot priority column. Target boot LUN values must be compliant with proper ranges.
Figure 5-4 Copying a profile using the Copy from button 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 5-5 Force same VLAN mappings as Shared Uplink Sets checkbox Configuring Network Port Speed When creating or editing a 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. 2.
Deleting a 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. The following message appears: IMPORTANT: VCEM has detected you may be using other products, such as HP Insight Dynamics – VSE.
1. 2. 3. 4. 5. 6. From the Profiles page, select the profile to be verified. Click Edit. The Edit Profile information appears below the profile table. In the Profile Information table, click the question mark icon. If EFI partition data is present in the profile, the EFI icon appears as well as the option to clean up the data. (Optional) To clean up the partition data, check the Remove EFI partition attached to profile checkbox and click OK.
6. 7. 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. Moving a 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.
Preconditions for VC Profile Failover • Source and designated spare servers must be part of the same VC Domain. • Designated spare servers are powered off. • A spare server must be the same model as the source server. Designating spare bays For more information about designating spare bays, see Designating spare bays. Initiating VC Profile Failover through the VCEM CLI You can initiate VC Profile Failover through the VCEM CLI or GUI.
services, and ensure compatibility with any other applications designed to perform automatic event handling. Unintended failover scan results in the loss of data and unnecessary system downtime. To set up automated VC Profile Failover: 1. 2. 3. 4. 5. 6. 7. 8. Enable HP SIM automatic discovery by selecting Options→Discovery. Discovery must be enabled to discover servers within the environment. Enable active event handling by selecting Options→Events→Automatic Event Handling→New Task.
6 Managing enclosure bay assignments Bays 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.
Item Description UID Unique identifier that tells if the 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. The following table lists the additional information that appears.
1. 2. 3. Click the Bays tab. To determine the power status of the bay, click the bay number. A status window appears. 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 profile to a bay procedure section. • If the bay is currently powered up, then click Momentary Press, which automatically powers down the bay.
1. 2. 3. 4. 5. 6. Click the Bays tab. (Optional) From the Filter list, select VC Domain or VC Domain Group. Select the bay for which you want to unassign a profile. Click Unassign 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 checkboxes for bays that do not have a profile applied.
Preconditions for VC Profile Failover • Source and designated spare servers must be part of the same VC Domain. • Designated spare servers are powered off. • A spare server must be the same model as the source server. Designating spare bays For more information about designating spare bays, see Designating spare bays. Initiating VC Profile Failover through the VCEM CLI You can initiate VC Profile Failover through the VCEM CLI or GUI.
1. 2. 3. 4. 5. 6. 7. 8. Enable HP SIM automatic discovery by selecting Options→Discovery. Discovery must be enabled to discover servers within the environment. Enable active event handling by selecting Options→Events→Automatic Event Handling→New Task. This step launches a wizard to aid in the creation of a task. Use the wizard to select a name for the event handler. To monitor the selected CPU and memory-related failures, select the Profile Failover Trigger Events event collection.
7 Managing MAC and WWN addresses This section describes how to manage MAC and WWN addresses using VCEM. 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, profiles created before VCEM 1.40 will continue to use the HP Pre-defined addresses already assigned to them.
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.
5. 6. 7. 8. From the Filter list, select External. Select the external addresses to be reclaimed. Click Reclaim External. You are prompted to confirm your choices. Click OK. Adding custom MAC 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 custom MAC address ranges: 1. 2. 3. 4. 5. From the VCEM home page, under the Administration heading, click the MAC addresses hyperlink.
user-defined WWNs. You can use the HP-predefined range only for import profiles or profiles created on previous versions of VCEM. To access WWN addresses from the VCEM home page, click the World Wide Names hyperlink. The WWN Ranges List page appears. Figure 7-2 WWN Ranges List page 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.
3. 4. 5. Select a WWN address range. The exclusion range must be contained within the address range to which the exclusion range belongs. Select the Exclusion ranges tab. To create the exclusion range, click New. IMPORTANT: External addresses that are included in a WWN exclusion range remain external addresses. The status of an external address does not change if it is included in a WWN exclusion range. 6. Select a HP-predefined address range, or manually enter the address range to exclude.
Figure 7-3 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. Reclaiming external WWN addresses External WWN addresses are generated when a VC Domain containing server profiles is removed from a VC Domain Group.
To add WWN custom address ranges: 1. 2. 3. 4. 5. From the Virtual Connect Enterprise Manager home page, under the Administration heading, click the World Wide Names hyperlink. From the Select ranges to configure link, select WWN. Click Add custom. The Add Custom WWN Address Range information appears. Enter the custom WWN address range. Click OK. 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.
8 Working with Logical Serial Numbers 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 9-1 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.
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.
12 Command Line Interface usage in VCEM VCEM provides support for a command line interface (CLI) to perform several failover-related functions. These same functions are also available in the VCEM GUI. Perform VC profile failover on specified VC Domain bay server This CLI command initiates a VC profile failover operation.
>vcem –list –details –job JobNumber If the CLI List Job Details command is successful, the exit code from the CLI is zero, and the following example output appears (through stdout) on the screen. >vcem –list –details –job 1 Listing details for specified VCEM Job...
CLI exit and error codes The CLI returns a numeric value that either indicates success or a particular error or failure. The CLI also displays an associated error message (through stdout). A zero numerical returned value indicates success. Some returned value greater than zero indicates an error or failure. The following list shows all possible exit and error codes and messages that might be returned by the VCEM CLI.
13 Troubleshooting VCEM When you are upgrading to a new and different CMS, or are moving to a 64-bit CMS, then you might need to migrate your data by using the HP SIM data migration tool. If you are upgrading to a new version of VCEM on the same CMS, data migration with the HP SIM data migration tool is not necessary. For more information, see the Data migration of an existing MS Windows CMS to a new Insight Software 6.0 system white paper on the HP SIM Information Library at http://h18013.www1.hp.
requirements for adding a VC Domain to a VC Domain Group. For more information, see “Requirements or adding a VC Domain to a VC Domain Group”. Also, a VC Domain might fail to add to the VC Domain Group for the following reasons: • Network issues • Invalid IP address • Insufficient credentials permission • Another VCEM external manager exists To correct this issue: • Verify that you can ping from the command line of the VCEM server and log in the Virtual Connect Manager using the browser.
For information on enclosure problems, see Enclosure has a hardware failure and must be replaced. • In a redundant environment, the failover between active and standby Virtual Connect module is taking place. To correct this issue: 1. 2. 3. 4. • Verify that the failover between the active and standby Virtual Connect module is taking place. Wait a few minutes until the failover completes, and then try again. Log into the Virtual Connect Manager (https://).
one of these addresses appears in the user interface. When checking if a server profile is using an address, you must consider both the displayed address and the hidden address. When considering the hidden addresses, add 1 to the addresses that are being displayed. For example, if a profile is using two Ethernet connections with MAC addresses 00-21-5A-9B-00-00 and 00-21-5A-9B-00-02 then the hidden addresses will be 00-21-5A-9B-00-01 and 00-21-5A-9B-00-03.
6. 7. Click Apply License. Perform the failed 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.
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. 2. 3. 4. From the VCEM home page, click the Jobs tab. Locate the job, either by its ID or its name. For detailed information about the job and how you can resolve the issue, click the task name of this job. (Optional) Job details might appear to be truncated when the appended exceeds 256 characters.
1. 2. 3. 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 username 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.
Error on database operation occurs Errors might occur during database operations if: • VCEM tables are missing; that is, Database Administrator deleted some VCEM tables. • HP SIM database is not running. To resolve this issue: 1. 2. 3. If VCEM tables are missing, then you must restore the VCEM database backup. For more information, see Backing up and restoring VCEM. Check the HP SIM database server status: • If the database server is remote, then log in to the database server.
Creating a server profile or adding a VC Domain to a VC Domain Group fails Attempting to create a profile or adding a VC Domain to a VC Domain Group might fail if any of the following occur: • VCEM does not have enough free MAC or WWN addresses. • Some MAC or WWN addresses are already being used by another server profile. • The MAC or WWN addresses in use by the VC Domain are not defined as custom ranges in VCEM. To resolve this issue: 1. 2. 3. 4. Verify VCEM has enough free MAC and WWN addresses.
3. 4. 5. 6. 7. 8. 9. Click Remove from VC Domain Group. Wait for the job to complete successfully. Replace the VC modules from the enclosure reader interconnect bays. Verify that the network and SAN connections that are wired to the new VC modules are the same as the old connections. If the primary VC Ethernet module was replaced, then you must configure the VC Domain again through virtual Connect.
server profiles, you must bring the VC Domain again to VCEM control and then update the server profile through the VCEM profile editor.
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. This situation occurs because VCEM relies on proper communication from the Virtual Connect Manager to the Onboard Administrator to retrieve and change configurations, statuses of the physical devices inside the enclosure, and perform server power all on and off operations.
Create VC Domain Group or Add VC Domain to VC Domain Group operations fail and the message "An invalid boot LUN was entered. Check the storage arrays for the proper LUN number" appears 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. 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.
1. 2. Install VCEM 6.1 in a fresh machine. Break the external manager lock in all VC Domains that were previously managed by VCEM 1.20. To remove the external manager account: a. 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. b. To determine the username of the external manager account, from the Virtual Connect Manager command prompt, enter show external-manager.
14 HP services and technical support HP offers a number of software support services, many of which are provided to our customers at no additional charge. • Software Technical Support and Update Service—VCEM includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP technical resources for assistance in resolving software implementation or operations problems.
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 Systems Insight Manager are initiated from this system.
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 Systems Insight Manager 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. Systems Insight Manager can no longer communicate with the system.
shared uplink port set A set of Ethernet uplinks that are used together to provide improved throughput and availability to a group of associated Virtual Connect networks. Each associated Virtual Connect network is mapped to a specific VLAN on the external connection and appropriate VLAN tags are removed or added as Ethernet packets enter or leave the VC Domain. Simple Network Management Protocol (SNMP) One of the management protocols supported by Systems Insight Manager.
Index A adding a VC Domain to a VC Domain Group, 37 adding custom MAC address ranges, 75 adding custom WWN address range, 78 adding or removing VC modules to VC Domain Group configuration, 54 allocating WWN addresses, 77 assigning a profile, 63 assigning a profile from a key, 69 B bays assigning a profile from a key, 69 performing a VC Profile Failover, 70 powering down a bay, 68 unassigning a profile from a key, 69 C canceling a VC Domain Group maintenance task, 52 cancelling a VC Domain Maintenance task
moving a profile, 64 moving Ethernet networks (VLANs tagged) from one shared uplink to another, 55 enclosure has two Onboard Administrators, and one fails, 98 error on database operation occurs, 100 errors occur while loading VCEM pages, 100 failed to execute VCEM operation because VC firmware not supported, 100 failover fails to initiate with an ERROR (30) - Could not initiate failover; nested exception is: java.net.
upgrading incompatible firmware modes and versions, 23 upgrading VC Domain Group firmware mode, 52 upgrading Virtual Connect firmware after VCEM is managing VC Domains, 85 performing firmware update using the VC Domain Maintenance capability, 85 preparation checklist, 85 V VC Domain Group canceling a VC Domain Group maintenance task, 52 creating a VC Domain Group, 50 deleting a VC Domain Group, 53 maintaining a VC Domain from the VC Domain Group page, 52 upgrading VC Domain Group firmware mode, 52 VC Domai
