Page 1 Hitachi Compute Blade HVM Navigator User's Guide - Migration A ST IN D IN KS Document organization Product version Getting help Contents MK-99COM024-12...
Page 2 Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication.
Page 3 Contents Preface ....................ix Intended audience ....................x Product version ..................... x Release notes ....................... x Document organization ..................xi Referenced documents ..................xi Document conventions ..................xii Convention for storage capacity values ..............xiii Getting help ......................xiv Comments ......................xiv Overview ....................
Page 4 Procedure for Concurrent Maintenance mode ..........3-28 Confirming if Concurrent Maintenance mode finished normally...... 3-43 Recovering LPAR ..................3-45 Rolling back WWNs ..................3-51 Policy migration ....................3-56 Procedure to create migration policy ............3-57 Procedure to execute Policy migration ............3-62 Procedure to interrupt Policy migration ............
Page 5 Restoring HVM configuration ................ 5-5 Initialization of HVM configuration (DC command of management module) .... 5-6 Changing HVM system time on destination HVM ........... 5-7 Operation deterrence ..................5-7 Exchanging NIC or FC HBA switches while server blade is in operation ....5-7 Setting network segment assigned to activated LPARs as migration path ....
Page 6 N+M Failover during Migration ................5-26 Migrating LPAR form the standby server blade after Cold standby switching ..5-27 Test of Configuring N+M Cold Standby .............. 5-28 Cold standby switching after migration ............... 5-28 Combined use with Uninterruptible Power Supply (UPS) ........5-28 Suppression of HVM auto shutdown during migration .........
Page 7 Detailed error information detected by Migration Management Server ... 6-33 Detailed error information detected by Migration Management Server thread module ....................6-39 Detailed error information detected by LPAR Mover module ......6-40 Detailed error information detected by Recovery module ......6-41 Detailed error information detected by the source HVM ........
Page 8 viii Contents HVM Navigator User's Guide - Migration...
Page 9 Convention for storage capacity values  Getting help  Comments  Notice: The use of Compute Blade and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data Systems. Preface HVM Navigator User's Guide - Migration...
Page 10: Intended Audience
Intended audience This document is intended for the personnel who are involved in planning, managing, and performing the tasks to prepare your site for Compute Blade installation and to install the same. This document assumes the following:  The reader has a background in installation and operation of software. (Firmware, Driver for Hardware, Operating System and Applications) ...
Page 11: Overview
Compute Blade documents:  Hitachi Compute Blade 2000 USER'S GUIDE  Hitachi Compute Blade 320 USER'S GUIDE  Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide  Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide ...
Page 12: Document Conventions
Document conventions This document uses the following typographic conventions: Convention Description Regular text bold In text: keyboard key, parameter name, property name, hardware labels, hardware button, hardware switch. In a procedure: user interface item Italic Variable, emphasis, reference to document title, called-out term Screen text Command name and option, drive name, file name, folder name, directory name, code, file content, system and application output, user input...
Page 13 Convention for storage capacity values Physical storage capacity values (for example, disk drive capacity) are calculated based on the following values: Physical capacity unit Value 1 kilobyte (KB) 1,000 (10 ) bytes 1 megabyte (MB) 1,000 KB or 1,000 bytes 1 gigabyte (GB) 1,000 MB or 1,000 bytes...
Page 14: Getting Help
Getting help The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: https://portal.hds.com Comments Please send us your comments on this document: [email protected].
Page 15 Overview This chapter describes the overview of LPAR migration. Overview HVM Navigator User's Guide - Migration...
Page 16 LPAR migration is the function to transfer an LPAR from a server blade to another one. You can execute LPAR migration to maintain server blades and use resources such as CPU, memory, NIC, and FC HBA efficiently. By executing LPAR migration, you can transfer MAC addresses and WWNs, accompanying logical NICs and HBAs assigned to the LPAR to migrate, along with other kinds of configuration data, namely, you can reconfigure the LPAR briefly on the destination server blade without reconfiguring any settings for...
Page 17 Table 1-1 Exchangeable hardware and software with Concurrent Maintenance mode Hardware/software Operator HVM firmware User SD card CPU indicating issues Memory indicating issues NIC/FC HBA switch which doesn’t support exchanging while the server blade is in Maintenance crew operation EFI/BIOS firmware BMC firmware server blade The application requirements and the kinds of configuration data to migrate,...
Page 18 Also, the kinds of configuration data to migrate or be exchanged are different between Shutdown mode and Concurrent Maintenance mode. For the kinds of configuration data to migrate or be exchanged in both Shutdown mode and Concurrent Maintenance mode, see the following table. Note that you can confirm if you can set each item manually in the “Setting”...
Page 19 Migration to destination Grouping Item Setting Concurrent Shutdown Maintenance USB auto attachment Logical FC HBA Slot number Shared FC# Slot#/Port# Relative slot Logical PCI address number Virtual WWN Exchanged between the source and destination vfcID (The smallest available number is assigned.) Whereas, when the HBA Core Dedicated Mode is enabled, “Yes”.
Page 20 Migration to destination Grouping Item Setting Concurrent Shutdown Maintenance LPAR Time Logical RTC information (CMOS timer) HVM internal information System (Physical RTC information) (The time difference Time between the source and destination server blades is migrated.) Physical RTC Time SEL Time Time Mode Date and Time Time Zone...
Page 21 Migration to destination Grouping Item Setting Concurrent Shutdown Maintenance CA certificate Setting Security strength Verify certificate -: No case You cannot change the setting on HVM firmware version 58-2x/78-2x or earlier, or 17-4x or earlier. Whereas, you can change the setting on HVM firmware version 58-4x/78-4x or higher, 17- 61 or earlier, any HVM firmware version for CB500, or any HVM firmware versions for CB2500.
Page 22 Overview HVM Navigator User's Guide - Migration...
Page 23: Usage Environments
Usage environments This chapter describes the usage environments. Environment  Time period for migration  Application requirements  Usage environments HVM Navigator User's Guide - Migration...
Page 24: Environment
Environment Environment for Shutdown mode The requisite hardware, firmware and software to execute LPAR migration in Shutdown mode are shown in the following tables. Take note that when you execute LPAR migration in Shutdown mode on any of the certain versions of HVM, old versions of HVM Navigator are not available.
Page 25 Table 2-2 Available version of HVM Navigator (BS 1000, CB 2000, CB 320) Platform HVM firmware version Available version of HVM Navigator BS1000 CB2000 Standard 58-70 or earlier V02-01 or earlier Server Blade 58-72 or higher V02-02 or higher 59-0x or higher V03-00/A or higher 59-1x to 59-20 V03-00/E or higher...
Page 26 Table 2-3 Available version of HVM Navigator (CB 500 and CB 2500) Platform HVM firmware version Available version of HVM Navigator CB500 CB520H 01-0x V02-04/A or higher Server Blade 01-1x V03-00/B or higher A1, A2, B1, B2 01-2x V03-00/D or higher model 01-3x V03-00/E or higher...
Page 27 02-05 or higher V03-06 or higher 02-1x or higher V03-07 or higher CB2500 CB520H 02-05 or higher V03-06 or higher Server Blade 02-1x or higher V03-07 or higher B3 model CB520X 02-00 or higher V03-05 or higher Server Blade 02-05 or higher V03-06 or higher B1 model 02-1x or higher...
Page 28: Environment For Concurrent Maintenance Mode
Environment for Concurrent Maintenance mode The requisite hardware, firmware and software to execute LPAR migration in Concurrent Maintenance mode are shown in the following tables. Take note that you cannot execute LPAR migration in Concurrent Maintenance mode on old versions of HVM. For available combinations of HVM and HVM Navigator, see Table 2-5 and 2-6.
Page 29 Table 2-5 Available version of HVM Navigator (BS 1000, CB 2000, and CB 320) Platform HVM firmware version Available version of HVM Navigator BS1000 CB2000 Standard 59-1x to 59-20 V03-00/E or higher Server Blade 59-2x or higher V03-01 or higher 59-51 or higher V03-02 or higher 59-6x or higher...
Page 30 Table 2-6 Available version of HVM Navigator (CB 500, and CB 2500) Platform HVM firmware version Available version of HVM Navigator CB500 CB520H 01-3x or higher V03-00/E or higher Server Blade 01-4x or higher V03-01 or higher A1, A2, B1, B2 01-6x or higher V03-02 or higher model...
Page 31 CB520X 02-00 or higher V03-05 or higher Server Blade 02-05 or higher V03-06 or higher B1 model 02-1x or higher V03-07 or higher CB520X 02-1x or higher V03-07 or higher Server Blade B2 model - : No version You must fulfill the following requirements to execute LPAR migration in Concurrent Maintenance mode.
Page 32: Time Period For Migration
Time period for migration The time required for an LPAR to migrate in Shutdown mode and that required for an LPAR to migrate in Concurrent Maintenance mode are different. Time period for Shutdown mode It takes about 5 minutes that an LPAR migrates in Shutdown mode though the time period varies depending on what type of guest OS running on the LPAR, what application programs running on the guest OS, and other factors.
Page 33 OS to the HVM system time by executing Adjust LPAR time, instead. For Adjust LPAR time, see "Hitachi Compute Blade 2000 USER'S GUIDE", "Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide", or “Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide”.
Page 34: Application Requirements
Application requirements This section describes the application requirements for LPAR migration. Confirm if you execute LPAR migration on your system. The following figure shows a system with the source and destination server blades. Server Blade Server Blade Source Destination Server Server Chassis Chassis...
Page 35 Confirm the following two items. – Requirements of LPAR to migrate Confirm if the configuration of the LPAR to migrate fulfills the requirements to execute LPAR migration. – Requirements of the source and destination server blades Confirm if the configurations of the source and destination server blades fulfill the requirements to execute LPAR migration.
Page 36  Requirements of the source and destination server blades The requirements of the source and destination server blades for both Shutdown and Concurrent Maintenance mode are shown in the following table. When the following requirements are fulfilled, you don’t need to confirm “Application requirements of source and destination server blades for Shutdown mode”...
Page 37 Requirement Item Shutdown Concurrent Maintenance FC HBA The number of vfcIDs assigned to the LPAR to migrate is available on the destination server blade. HVM system time zone The HVM system time zones are matched between the source and destination HVMs. HVM system time When the HVM system times are synchronized on the source and synchronization with NTP...
Page 38: Application Requirement For Shutdown Mode
LPAR is migrated. When you see this message, see "LPAR Memory Fragmentation" in Hitachi Compute Blade 2000 USER'S GUIDE, Hitachi Compute Blade 320 USER'S GUIDE or Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide.
Page 39: Server Blade
Shutdown LPAR status The following requirements shown in the following table must be fulfilled. Table 2-11 Requirements of LPAR status LPAR Status Migratable Act (Activated) Yes* Dea (Deactivated) Fai (Failure) * You must set the item for remote shutdown when you desire to execute LPAR migration in Shutdown mode.
Page 40 Shutdown Chassis type The chassis types where the source and destination server blades are inserted, such as CB2000, CB320, CB500, or CB2500, are matched. Server blade model The server blade models between the source and destination server blades must be matched. However, you cannot execute LPAR migration in Shutdown mode in some cases even when server blade model is the same between the source and destination server blades.
Page 41 Shutdown  CB320 Table 2-15 Combination of Server Blades (CB320) Destination Source Yes* * See the following (2).  CB500 CB520H server blade Table 2-16 Combination of server blades (CB500 CB520H server blade) Destination Source  CB500 CB520A server blade Table 2-17 Combination of server blades (CB500 CB520A server blade) Destination Source...
Page 42 Shutdown  CB500 CB520X server blade Table 2-19 Combination of server blades (CB500 CB520X server blade) Destination Source When you execute LPAR migration in Shutdown mode between CB520X server blades, see (4).  CB2500 CB520H server blade Table 2-20 Combination of server blades (CB2500 CB520H server blade) Destination Source ...
Page 43 Shutdown (1) Processor types of CB2000 standard server blade A2 model The following two types of CB2000 standard server blade A2 model are released. – Server blades with Intel Nehalem-EP processor E5503s – Server blades with Westmere-EP processor(Xeon the 5600s number)s Confirm whether you can execute LPAR migration in Shutdown mode in your environment in the following table.
Page 44 * When you execute LPAR migration on HVM firmware version 17-70 or higher, you must set [Main]-[Advanced Processor Options]-[AES Support] to "Disabled" in the BIOS. For the setting, see Hitachi Compute Blade 320 USER'S GUIDE. (3) SMP configurations of CB2000 high-performance server blade...
Page 45 Shutdown (4) SMP configurations of CB520X server blade You can execute LPAR migration in Shutdown mode only when the server blade configurations between the source and destination server blades are the same. Confirm the combinations of the configurations of the source and destination server blades between which you can execute LPAR migration in Shutdown in the following table.
Page 46 Shutdown Configuration of NIC and FC HBA The NIC and FC HBA configurations between the source and destination server blades must be matched.  Requirements for NIC configuration – A NIC card with the same number of ports is installed on each slot with the same PCI Device number on the source and destination server blades.
Page 47 Shutdown EFI/BIOS EFI/BIOS version The BIOS versions between the source and destination server blades must be matched. Also, the EFI versions between the source and destination server blades must be compatible. The combinations of compatible versions are shown in the following tables. Table 2-29 Combination of compatible EFI versions (CB2000 standard server blade) Destination...
Page 48 Shutdown Table 2-31 Combination of compatible EFI versions (CB500 CB520H server blade A1, B1) Destination 01-xx 02-xx 03-xx 04-xx 05-xx 06-xx 07-xx Source 01-xx 02-xx 03-xx 04-xx 05-xx 06-xx 07-xx Table 2-32 Combination of compatible EFI versions (CB500 CB520H server blade A2, B2) Destination 10-xx Source...
Page 49 Shutdown Table 2-35 Combination of Compatible EFI versions (CB540A Server Blade) Destination 01-xx 02-xx Source 01-xx 02-xx Table 2-36 Combination of compatible EFI versions (CB500 CB520X server blade B1) Destination 06-xx 07-xx Source 06-xx 07-xx Table 2-37 Combination of compatible EFI versions (CB500 CB520X server blade B2) Destination 09-xx...
Page 50 Shutdown Table 2-40 Combination of compatible EFI versions (CB2500 CB520X server blade B2) Destination 09-xx Source 09-xx Setting of EFI/BIOS The settings of EFI and BIOS between the source and destination server blades must be the same. 2-28 Usage environments HVM Navigator User's Guide - Migration...
Page 51 Shutdown HVM firmware version Each of the following tables shows the combinations of HVM firmware versions for each server blade model where you can execute LPAR migration in Shutdown mode. Note that the reference column shows the combinations of migratable HVMs between the source and destination server blades in the following table.
Page 52 Shutdown  1-1 CB2000 standard server blade A1 model Table 2-42 Combination of HVM on CB2000 standard server blade A1 model Destination Between Between 58-70 or earlier 59-21 or higher Source 58-71 and 58-72 58-80 and 59-11 58-70 or earlier Between 58-71 and 58-72 Between 58-80 and 59-11 59-21 or higher...
Page 53 Shutdown  1-3 CB2000 standard server blade R3 model Table 2-44 Combination of HVM on CB2000 standard server blade R3 model Destination Between 59-21 or higher Source 59-00 and 59-11 Between 59-00 and 59-11 Yes* 59-21 or higher Yes* * See “Note on expansion of VNIC System No.” ...
Page 54 Shutdown  1-7 CB2000 high-performance server blade A1 model Table 2-48 Combination of HVM on CB2000 high-performance server blade A1 model Destination Between Between 78-70 or earlier 79-21 or higher Source 78-71 and 78-72 78-80 and 79-11 78-70 or earlier Between 78-71 and 78-72 Between 78-80 and 79-11 79-21 or higher...
Page 55 Shutdown  2-2 CB320 P5 model Table 2-51 Combination of HVM on CB320 P5 model Destination Between 17-61 or earlier 17-80 or higher Source 17-70 and 17-72 17-61 or earlier Between 17-70 and 17-72 1, 2 17-80 or higher Notes: 1.
Page 56 Shutdown  3-3 CB500 CB520H server blade A2 model Table 2-54 Combination of HVM on CB500 CB520H server blade A2 model Destination Between 02-01 or higher Source 01-60 and 01-90 Between 01-60 and 01-90 02-01 or higher  3-4 CB500 CB520H server blade B2 model Table 2-55 Combination of HVM on CB500 CB520H server blade B2 model Destination...
Page 57 Shutdown  3-7 CB500 CB540A server blade A1 model Table 2-58 Combination of HVM on CB500 CB540A Server Blade A1 Model Destination Between Between 02-01 or higher Source 01-02 and 01-30 01-40 and 01-90 Between 01-02 and 01-30 Yes* Between 01-40 and 01-90 Yes* 02-01 or higher * See “Note on assigning NIC ports”...
Page 58 Shutdown  4-1 CB2500 CB520H server blade B3 model Table 2-62 Combination of HVM on CB2500 CB520H server blade B3 model Destination 02-05 or higher Source 02-05 or higher  4-2 CB2500 CB520X server blade B1 model Table 2-63 Combination of HVM on CB2500 CB520X server blade B1 model Destination 02-01 or higher...
Page 59 Shutdown Note on expansion of VNIC System No.  CB2000 When you execute LPAR migration in Shutdown mode between HVM firmware 59-11/79-11 or earlier and 59-21/79-21 or higher, and the VNIC System No. set for the HVM firmware 59-21/79-21 or higher is 129 or greater, you cannot execute LPAR migration in Shutdown mode.
Page 60 Shutdown Note on assigning NIC ports When Hvm Operating Mode is set to Standard on an HVM for CB2000 or CB320, an LPAR with shared NICs assigned to in any of the following ways cannot migrate. Also, an LPAR on HVM firmware version 58-70 or earlier, 78-70 or earlier, or 17-72 or earlier cannot migrate regardless a value of Hvm Operating Mode.
Page 61 Shutdown Case3: When a segment is assigned two or more times to an LPAR. Ex) "1a" is assigned seven times to Virtual NIC Number #0 through #6. Figure 2-4 A segment is assigned two or more times to an LPAR Case4: When only some of the segments belonging to a controller with multiple ports is assigned to an LPAR.
Page 62 Shutdown Note on selecting VNIC Device Type  CB2000 You can select VNIC Device Type when you operate HVM firmware version 59- 00/79-00 or higher. However, when you set VNIC Device Type to NIC2 on the source HVM and you set Hvm Operating Mode to Standard on the destination HVM, you cannot have LPARs migrate on the source HVM to the destination HVM.
Page 63 Before LPARs have migrated to HVM firmware version 01-01 on a server blade over the number of times shown in the following table, you must reboot the server blade or execute "Force Recovery" according to Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide.
Page 64: Application Requirement For Concurrent Maintenance Mode
Concurrent Maintenance Application requirement for Concurrent Maintenance mode The application requirements for Concurrent Maintenance mode are described in this subsection. Requirement of the LPAR to migrate LPAR name The following requirements must be fulfilled. – LPAR Name is not "NO_NAME". –...
Page 65 Concurrent Maintenance Guest OS You can confirm the supported kinds of guest OS to execute LPAR migration in Concurrent Maintenance mode in the following tables. “HVM firmware version” column shows the HVM firmware versions which support each guest OS. Table 2-73 Supported OS (CB 2000 standard server blade) HVM firmware version Guest OS E55A1...
Page 66 Concurrent Maintenance Table 2-74 Supported OS (CB 2000 high-performance server blade) HVM firmware version Guest OS E57A1/E57E1 E55A2/E57E2 server blade server blade Red Hat Enterprise Linux 79-10 or higher 79-10 or higher 79-51 or higher 79-51 or higher 79-31 or higher 79-31 or higher 79-31 or higher 79-31 or higher...
Page 67 Concurrent Maintenance Table 2-75 Supported OS (CB 500) HVM firmware version CB 520H CB 520H CB 520H CB 520A CB 540A CB 520X Guest OS server server server server server server blade blade blade blade blade blade A1, B1 A2, B2 Red Hat Enterprise Linux...
Page 68 Concurrent Maintenance Table 2-76 Supported OS (CB 2500) HVM firmware version CB 520H CB 520X CB 520X Guest OS server blade server blade server blade Red Hat 02-05 or higher 02-01 or higher Enterprise 02-06 or higher 02-06 or higher 02-10 or higher Linux Windows...
Page 69 Concurrent Maintenance Requirement of source and destination server blades Management module version You can execute LPAR migration in Concurrent Maintenance mode regardless of management module version. Dictionary version When you execute LPAR migration in Concurrent Maintenance mode between CB2000's, the Dictionary version must be 00075 or higher. When the Dictionary version is 00074 or earlier, some messages are not displayed properly.
Page 70 Concurrent Maintenance Server blade model The server blade models between the source and destination server blades must be matched. However, you cannot execute LPAR migration in Concurrent Maintenance mode in some cases even when server blade model is the same between the source and destination server blades.
Page 71 Concurrent Maintenance  CB500 Table 2-80 Combination of server blades (CB520H server blade) Destination Source Table 2-81 Combination of server blades (CB520A server blade) Destination Source Table 2-82 Combination of server blades (CB540A server blade) Destination Source Table 2-83 Combination of server blades (CB520X server blade) Destination Source When you execute LPAR migration in Concurrent Maintenance mode between...
Page 72 Concurrent Maintenance  CB2500 Table 2-84 Combination of server blades (CB520H server blade) Destination Source Table 2-85 Combination of server blades (CB520X server blade) Destination Source When you execute LPAR migration in Concurrent Maintenance mode between CB520X server blades, see (3). 2-50 Usage environments HVM Navigator User's Guide - Migration...
Page 73 Concurrent Maintenance (1) Processor typea of CB2000 standard server blade A2 model The following two types of CB2000 standard server blade A2 model are released. – Server blades with Intel Nehalem-EP processor E5503s – Server blades with Westmere-EP processor(Xeon the 5600s number)s Confirm whether you can execute LPAR migration in Concurrent Maintenance mode in your environment in the following table.
Page 74 Concurrent Maintenance (3) SMP configurations of CB520X server blade You can execute LPAR migration in Concurrent Maintenance mode only when server blade configuration is the same between the source and destination server blades. Confirm the combination of configuration on the source and destination server blades between which you can LPAR migration in Concurrent Maintenance in the following table.
Page 75 – The relative slot number where each FC HBA card on the source and destination server blades is located is matched. – One of the Hitachi Fibre channel firmware versions listed in the following table is installed on the source and destination server blades respectively.
Page 76 Concurrent Maintenance – One of the Hitachi Fibre channel driver versions listed in the following table is installed on the source and destination server blades respectively. Table 2-91 Supported Hitachi Fibre channel driver version Guest OS Hitachi Fibre channel driver version Red Hat 5.6 or earlier...
Page 77 Concurrent Maintenance Application software for HVM management You must use any of the versions shown in the following table. Table 2-92 Version of SC Product name Supported version SC/BSM ServerConductor/Blade Server Manager 08-xx 08-90 or higher * ServerConductor/Blade Server Manager 09-xx 09-53-/A or higher * SC/Agent ServerConductor/Agent...
Page 78 Concurrent Maintenance HVM firmware version Each of the following tables shows the combinations of HVM firmware versions for each server blade model where you can execute LPAR migration in Concurrent Maintenance mode. Note that the reference column shows the combinations of migratable HVMs between the source and destination server blades in the following table.
Page 79 Concurrent Maintenance  1-1 CB2000 standard server blade A1 model Table 2-94 Combination of HVM on CB2000 standard server blade A1 model Destination 59-11 or earlier 59-21 or higher Source 59-11 or earlier Yes* 59-21 or higher * See “Note on expansion of VNIC System No.” ...
Page 80 Concurrent Maintenance  1-5 CB2000 standard server blade R4 model Table 2-98 Combination of HVM on CB2000 standard server blade R4 model Destination 59-51 or higher Source 59-51 or higher  1-6 CB2000 standard server blade S4 model Table 2-99 Combination of HVM on CB2000 standard server blade S4 model Destination 59-51 or higher...
Page 81 Concurrent Maintenance  3-1 CB500 CB520H server blade A1 model We don’t support LPAR migrations to HVM firmware version 01-60 from another HVM firmware version. Table 2-102 Combination of HVM on CB500 CB520H server blade A1 model Destination 01-40 Between Source 01-30 01-60...
Page 82 Concurrent Maintenance  3-3 CB500 CB520H server blade A2 model We don’t support LPAR migrations to HVM firmware version 01-60 from another HVM firmware version. Table 2-104 Combination of HVM on CB500 CB520A server blade A2 model Destination Between 01-60 02-01 or higher Source 01-70 and 01-90...
Page 83 Concurrent Maintenance  3-6 CB500 CB520A server blade A1 model We don’t support LPAR migrations to HVM firmware version 01-60 from another HVM firmware version. Table 2-107 Combination of HVM on CB500 CB520A server blade A1 model Destination 01-40 Between Source 01-30 01-60...
Page 84 Concurrent Maintenance  3-8 CB500 CB540A server blade B1 model We don’t support LPAR migrations to HVM firmware version 01-60 from another HVM firmware version. Table 2-109 Combination of HVM on CB500 CB540A server blade B1 model Destination 01-40 Between Source 01-30 01-60...
Page 85 Concurrent Maintenance  4-1 CB2500 CB520H server blade B3 model Table 2-112 Combination of HVM on CB2500 CB520H server blade B3 model Destination 02-05 or higher Source 02-05 or higher  4-2 CB2500 CB520X server blade B1 model Table 2-113 Combination of HVM on CB2500 CB520X server blade B1 model Destination 02-01 or higher...
Page 86 Concurrent Maintenance HVM model The following tables show the HVM models with which an LPAR can migrate between the source and destination server blades. Table 2-115 HVM model (CB2000) HVM model Supported Essential Enterprise Table 2-116 HVM model (CB500) HVM model Supported Essential Advanced...
Page 87 Concurrent Maintenance Security strength An LPAR configuration is transferred in plain text format through migration paths in an LPAR migration in Concurrent Maintenance mode. Any TLS communication settings cannot be applied in an LPAR migration in Concurrent Maintenance mode even if you have configured any TLS communication settings for ordinary communications.
Page 88 Concurrent Maintenance Note on expansion of VNIC System No.  CB2000 When you execute LPAR migration in Concurrent Maintenance mode between HVM firmware 59-11/79-11 or earlier and 59-21/79-21 or higher, and the VNIC System No. set for the HVM firmware 59-21/79-21 or higher is 129 or greater, you cannot execute LPAR migration in Concurrent Maintenance.
Page 89 Concurrent Maintenance  CB500 When you execute LPAR migration in Shutdown mode between HVM firmware 01-30 or earlier and 01-40 or higher, and the VNIC System No. set for the HVM firmware 01-40 or higher is 129 or greater, you cannot execute LPAR migration in Shutdown mode.
Page 90: Storage Device
Concurrent Maintenance Storage device Setting of FC HBA You can confirm the FC HBA connection configurations to execute Concurrent Maintenance mode in the following table. Table 2-121 FC HBA connection configurations for Concurrent Maintenance mode Adapter type Connection configuration 4Gbps Fibre 8Gbps Fibre channel adapter channel adapter...
Page 91 Concurrent Maintenance Migration path A migration path is used to transfer the configuration data of the source LPAR and the memory data of the guest OS on the source LPAR, to the destination HVM. You must set a shared NIC port with the theoretical bandwidth greater than or equal to 1 Gbps (the actual bandwidth greater than or equal to 900 Mbps) to execute LPAR migration in Concurrent Maintenance mode.
Page 92 Concurrent Maintenance The recommended network configurations, which fulfill the above requirements, are shown in the following figures. Configure migration paths according to the following network configurations. The recommended network configuration for each server configuration varies depending on the kind of NIC set as a migration path to be used during a migration and other factors.
Page 93 Concurrent Maintenance  When you set a port of the onboard NIC or a mezzanine NIC exclusively as the migration path to be used Figure 2-7 Recommended network configuration (Path configuration 2) Usage environments 2-71 HVM Navigator User's Guide - Migration...
Page 94 Concurrent Maintenance  When you set a port of a PCI card in use as the migration path to be used Figure 2-8 Recommended network configuration (Path configuration 3) 2-72 Usage environments HVM Navigator User's Guide - Migration...
Page 95 Concurrent Maintenance  When a port of a PCI card is set exclusively as the migration path to be used Figure 2-9 Recommended network configuration (Path configuration 4) Usage environments 2-73 HVM Navigator User's Guide - Migration...
Page 96 Concurrent Maintenance Note on assigning NIC ports When Hvm Operating Mode is set to Standard on an HVM for CB2000, an LPAR with shared NICs assigned to in any of the following ways cannot migrate. Also, an LPAR on HVM firmware version 58-70 or earlier, 78-70 or earlier, cannot migrate regardless a value of Hvm Operating Mode.
Page 97 Concurrent Maintenance Case3: When a segment is assigned two or more times to an LPAR. Ex) "1a" is assigned seven times to Virtual NIC Number #0 through #6. Figure 2-12 A segment is assigned two or more times to an LPAR Case4: When only some of the segments belonging to a controller with multiple ports is assigned to an LPAR.
Page 98 Concurrent Maintenance Note on selecting VNIC Device Type  CB2000 You can select VNIC Device Type when you operate HVM firmware version 59- 00/79-00 or higher. However, when you set VNIC Device Type to NIC2 on the source HVM and you set Hvm Operating Mode to Standard on the destination HVM, you cannot have LPARs migrate on the source HVM to the destination HVM.
Page 99 Before LPARs have migrated to HVM firmware version 01-01 on a server blade over the number of times shown in the following table, you must reboot the server blade or execute "Force Recovery" according to Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide.
Page 100 2-78 Usage environments HVM Navigator User's Guide - Migration...
Page 101: Migration Procedures
Migration procedures This chapter describes the migration procedures. Shutdown mode  Concurrent Maintenance mode  Policy migration  Return migration  Exchanging or updating hardware or software  Saving and backing up HVM configuration  Registering/removing migration WWN  Migration procedures HVM Navigator User's Guide - Migration...
Page 102: Shutdown Mode
Shutdown mode The mode to shut down the guest OS on an LPAR and have the LPAR migrate to another server blade, is introduced in this section. You can confirm a result of migration more easily by having only one LPAR migrate at a time. Therefore, when you have an LPAR which hasn’t migrated in the current system configuration migrate, we recommend that you have the LPAR migrate in Shutdown mode.
Page 103: Procedure For Shutdown Mode
Procedure for Shutdown mode Operate some tools according to the following procedure when you have an LPAR migrate in Shutdown mode. Operation on Operation on HVM Navigator Web console for CB 500 Web console for CB 2500 SC/BSM Save HVM configurations on source and destination server blades.
Page 104 Operate the HVM Navigator according to the following procedure to have an LPAR migrate in Shutdown mode after you start HVM Navigator and then register the source and destination HVMs to the HVM Navigator according to the procedure shown in Hitachi Compute Blade HVM Navigator User’s Guide— Getting Started. ...
Page 105 3. Click Update button. 4. Select Shutdown radio button in Mode Selection group box and then click Migration button in Migration Menu group box. Migration procedures HVM Navigator User's Guide - Migration...
Page 106 Migration [Shutdown] window is displayed and HVMs for CB2000, CB320, CB500, or CB2500 which are registered to HVM Navigator appear in Source group box and Destination group box. 5. Select the source LPAR in Source group box and the destination LPAR in Destination group box.
Page 107 When you select source and destination LPARs with combo boxes: Uncheck Tree view check box in Target Selection group box in Migration [Shutdown] window. Then, the combo boxes to select source and destination chassis, HVMs, LPARs are displayed. Besides, in destination group box, the combo box to select processor group.
Page 108 When you want the destination LPAR to be selected automatically: Check Auto check box in Target Selection group box in Migration [Shutdown] window. Then the function which selects the destination LPAR automatically is enabled. When you check Auto check box and then select an HVM in Destination group box, the LPAR with the youngest LPAR number is selected as the destination LPAR automatically.
Page 109 When you select a processor group for the destination LPAR: a. Check Group check box in Target Selection group box in Migration [Shutdown] window. b. Select an HVM in Destination group box. c. Select a processor group in Destination group box. d.
Page 110 6. Click Migration Execute button. If necessary, change the settings in Migration Setting group box in Migration [Shutdown] window. If you check Shutdown Guest OS (Source) check box varies depending on the LPAR status of the LPAR to migrate. When the LPAR status is Act (Activated), you must check Shutdown Guest OS (Source) check box and set the items in Guest OS Information (for remote shutdown) group box.
Page 111 7. Confirmation window is displayed. Confirm the content and then if the content has no problems, click OK button. 8. When executing LPAR migration in Shutdown mode, Migration Progress window is displayed. You can confirm the progress in Migration Progress window.
Page 112 9. When LPAR migration finishes normally, “Migration completed!” message is displayed in Migration Progress. Click Close button. 3-12 Migration procedures HVM Navigator User's Guide - Migration...
Page 113: Recovering Lpar
Recovering LPAR Operate HVM Navigator according to the following procedure if there are LPARs necessary to be recovered. Operation on HVM Navigator Recover an LPAR. Are there the other LPARs necessary to be recovered? The migrated LPAR is running. Figure 3-2 Operation flow to recover LPAR When there are LPARs which have failed to be recovered on an HVM, restore the HVM configuration with the backup file retrieved before migration.
Page 114 Event When LPAR migration fails because of an error or cancelled because of resource shortage or any other cause on the destination, an error message is displayed in Migration Progress window and recovering LPAR is often executed automatically. However, there are some cases which are recovered automatically depending on the kind of errors or the states of HVM or LPAR configurations in a momentary time which the error occurs.
Page 115 Solution 1. Click Update button. 2. When one or more LPARs necessary to be recovered exist, the number of the LPARs is shown at Target Selection group box in Migration [Shutdown] window in the form of “LPARs requiring recovery: x LPARs” where x means the number of the LPARs.
Page 116 4. Confirmation window is displayed. Confirm the content and then click OK button. 3-16 Migration procedures HVM Navigator User's Guide - Migration...
Page 117 Migration Progress window is displayed. You can confirm the progress of recovering an LPAR. 6. When recovering an LPAR finishes normally, “Recovery completed!” message is displayed in Recovery Progress window. Click Close button. Migration procedures 3-17 HVM Navigator User's Guide - Migration...
Page 118 As mentioned before, the number of LPARs necessary to be recovered is shown in Target Selection group box in Migration window in the form of “LPARs requiring recovery: x LPARs” where x means the number of the LPARs. Recover all LPARs necessary to be recovered. If the recovery process fails, the error cause may not be removed.
Page 119: Concurrent Maintenance Mode
Concurrent Maintenance mode The mode to have an LPAR migrate to another server blade with the guest OS on the LPAR running, is introduced in this section. You can confirm a result of migration more easily by having only one LPAR migrate at a time. Prerequisite setting Set the following items to execute LPAR migration in Concurrent Maintenance mode.
Page 120 In advance, start HVM Navigator and then register the source and destination HVMs to HVM Navigator according to Hitachi Compute Blade HVM Navigator User’s Guide—Getting Started. 1. Register the migration WWPNs assigned to the LPAR to migrate to the host group to which the WWPNs assigned to the LPAR to migrate are already registered.
Page 121 2. Set FC zonings for SAN switches connected with the LPAR to migrate. a. When you set port zonings You don’t need to set anything to execute an LPAR migration in Concurrent Maintenance mode. b. When you set WWPN zonings An example of WWPN zoning configuration including a migration WWPN is shown in the following figures.
Page 122 [Typical wrong configuration] FCSW Storage device Guest OS Zone OS WWN_D WWN_OS WWN_OS WWN_D WWN_OS_Mig WWN_OS_Mig WWN_OS: WWPN on an FC port on a guest OS WWN_OS_Mig: migration WWPN on an FC port on a guest OS : Zone with WWPN (Zone OS) [Typical wrong configuration] Zone with WWPN (Zone OS)
Page 123 3. Select Migration tab. 4. Click Update button. Set at least one migration path for each of the source and destination HVMs. Be sure to confirm "Migration path" in "Application requirement for Concurrent Maintenance mode" in "Usage environments" before moving onto the following steps.
Page 124 3-24 Migration procedures HVM Navigator User's Guide - Migration...
Page 125 Migration Path Setting window is displayed. 6. Select the source or destination HVM in HVM Selection group box and then click Add Row button in Migration Path List group box. Next, check the check box in Primary Use column and input a name for the migration path in Name column.
Page 126 7. Scroll the horizontal bar to the right in Migration Path List group box. Next, input an IPv4 address in the IP address column and then input a subnet mask in the Subnet Mask column. Note that any IPv6 addresses do not work as migration paths.
Page 127 9. Click OK button. 10. Save window is displayed. Click OK button. 11. Click Close button. Migration procedures 3-27 HVM Navigator User's Guide - Migration...
Page 128: Procedure For Concurrent Maintenance Mode
Concurrent Maintenance mode after you start HVM Navigator and then register the source and destination HVMs to the HVM Navigator according to the procedure shown in Hitachi Compute Blade HVM Navigator User’s Guide—Getting Started. Operation on HVM Navigator...
Page 129 Fig. 3-38 Check the application requirements for Concurrent Maintenance mode. (Migration Config Viewer window) Take measures for errors. Are there no error? Execute LPAR migration in Shutdown mode. (Migration [Shutdown] window) Check LPAR migration in progress. (Migration Progress window) Check LPAR migration completion. (Migration Progress window) Are there LPARs which Recover LPARs.
Page 130 Microsoft Failover Cluster as the source LPAR, release the source server blade from the clustering configuration. 3. Confirm the following items according to Hitachi Compute Blade HVM Navigator User’s Guide—Monitoring. – CPU usage ratio on each of the source and destination HVMs is over 80%.
Page 131 4. Select Migration tab. 5. Click Update button. Migration procedures 3-31 HVM Navigator User's Guide - Migration...
Page 132 6. Select Concurrent Maintenance radio button in Mode Selection group box and then select Migration button in Migration Menu group box. Migration [Concurrent Maintenance] window is displayed and HVMs for CB2000, CB320, CB500, or CB2500 which are registered to HVM Navigator appear in Source group box and Destination group box.
Page 133 7. Select the source LPAR in Source group box and select the destination LPAR in Destination group box. Migration procedures 3-33 HVM Navigator User's Guide - Migration...
Page 134 When you select the source and destination LPARs with combo boxes: Uncheck Tree view check box in Target Selection group box in Migration [Concurrent Maintenance] window. Then, the combo boxes to select the source and destination chassis, HVMs, LPARs are displayed. Besides, in the destination group box, the combo box to select a processor group.
Page 135 When you want the destination LPAR to be selected automatically: Check Auto check box in Target Selection group box in Migration [Concurrent Maintenance] window. Then the function which selects the destination LPAR automatically is enabled. When you check Auto check box and then select an HVM in Destination group box, the LPAR with the youngest LPAR number is selected as the destination LPAR automatically.
Page 136 When you select a processor group for the destination LPAR: a. Check Group check box in Target Selection group box in Migration [Concurrent Maintenance] window. b. Select an HVM in Destination group box. c. Select a processor group in Destination group box. d.
Page 137 8. Click Show System Logs button. 9. Confirm the following items in HVM System Logs screen in HVM Console window. – There are no errors for the source and destination HVMs. – FC HBA ports installed on the source and destination server blades are stable.
Page 138 10. Click Show Config button. 3-38 Migration procedures HVM Navigator User's Guide - Migration...
Page 139 11. Confirm that no Error icons are shown in Migration Config Viewer window and then click Close button. If you find one or more Error icons in Migration Config Viewer window, the configuration requirements aren't fulfilled. Fulfill all configuration requirements, and then execute LPAR migration in Concurrent Maintenance mode.
Page 140 12. Click Migration Execute button. 13. Click OK button. 3-40 Migration procedures HVM Navigator User's Guide - Migration...
Page 141 LPAR migration in Concurrent Maintenance mode starts. 14. When executing LPAR migration in Concurrent Maintenance mode, Migration Progress window is displayed. You can confirm the progress in Migration Progress window. Migration procedures 3-41 HVM Navigator User's Guide - Migration...
Page 142 15. When LPAR migration finishes normally, “Migration completed!” message is displayed in Migration Progress. Click Close button. 3-42 Migration procedures HVM Navigator User's Guide - Migration...
Page 143: Confirming If Concurrent Maintenance Mode Finished Normally
Confirming if Concurrent Maintenance mode finished normally Confirm if no errors have occurred in HVM System Logs screen in HVM Console window. If no errors have occurred, you can see that LPAR migration in Concurrent Maintenance mode finished normally. Operate HVM Navigator according to the following procedure to display HVM System Logs screen.
Page 144 2. Confirm if no errors have occurred on the source and destination HVMs. 3-44 Migration procedures HVM Navigator User's Guide - Migration...
Page 145: Recovering Lpar
Recovering LPAR Operate HVM Navigator according to the following procedure if there are LPARs necessary to be recovered. Operation on HVM Navigator Recover an LPAR. Are there the other LPARs which need to be recovered? A migrated LPAR is running. Figure 3-5 Operation flow to recover LPAR When there are LPARs which have failed to be recovered on an HVM, restore the HVM configuration with the backup file retrieved before migration.
Page 146 Event When LPAR migration fails because of an error or cancelled because of resource shortage or any other cause on the destination, an error message is displayed in Migration Progress window and recovering LPAR is often executed automatically. However, there are some cases which are recovered automatically depending on the kind of errors or the states of HVM or LPAR configurations in a momentary time which the error occurs.
Page 147 Solution 1. Click Update button. 2. When one or more LPARs necessary to be recovered exist, the number of the LPARs is shown at Target Selection group box in Migration [Shutdown] window in the form of “LPARs requiring recovery: x LPARs” where x means the number of the LPARs.
Page 148 3. In the Source or Destination group box, each LPAR necessary to be recovered is indicated by a pin icon ( ). Select the first one with a mouse click and then click Recovery Execute button. (If you check Show the LPARs check box, only the LPARs necessary to be recovered are shown.) 4.
Page 149 5. Migration Progress window is displayed. You can confirm the progress of recovering an LPAR. 6. When recovering an LPAR finishes normally, “Recovery completed!” message is displayed in Recovery Progress window. Click Close button. As mentioned before, the number of LPARs necessary to be recovered is shown in Target Selection group box in Migration window in the form of “LPARs requiring recovery: x LPARs”...
Page 150 If the recovery process fails, the error cause may not be removed. Eliminate the error cause and retry. Also confirm the HVM because HVM possible to has a hardware failure. If the recovery process fails even though removed the error cause and retry, reactivate the HVM using back-up configuration information.
Page 151: Rolling Back Wwns
Rolling back WWNs Operate HVM Navigator according to the following procedure if there are LPARs with WWNs necessary to be rolled back. Operation on HVM Navigator Recover an LPAR. Are there the other LPARs which need to be recovered? A migrated LPAR is running.
Page 152 When LPAR migration in Concurrent Maintenance mode have failed, confirm if there are LPARs with WWNs necessary to be rolled back. If there are such LPARs, you must roll back WWNs assigned to all the LPARs. You cannot have all LPARs migrate on an HVM where LPARs with WWNs necessary to be rolled back are located without rolling back WWNs for the LPARs.
Page 153 Rollback WWN window is displayed. 2. Select an LPAR with WWNs necessary to be rolled back and then click Rollback Execute button. Migration procedures 3-53 HVM Navigator User's Guide - Migration...
Page 154 3. Click OK button. 4. Click OK button again after rolling back has completed. 3-54 Migration procedures HVM Navigator User's Guide - Migration...
Page 155 5. The LPAR which you have rolled back disappear from WWN Status List group box. Roll back the other LPARs with WWNs necessary to be rolled back in the same way. Roll back WWNs for all LPARs with WWNs necessary to be rolled back. If you don't roll back WWNs for any or all of the LPARs, you cannot have all LPARs migrate on an HVM where LPARs with WWNs necessary to be rolled back are located.
Page 156: Policy Migration
Policy migration Policy migration is the method which one or more LPAR migrations are executed in order in a migration policy (a package to execute one or more LPAR migrations in order) with registering the LPAR migrations to the migration policy. (Every registered LPAR migration is called "entry" in the following explanations.) We recommend that you execute a migration policy with only entries which you have already executed individually.
Page 157: Procedure To Create Migration Policy
Procedure to create migration policy Operate HVM Navigator according to the following procedure to create a migration policy. 1. When HVMs to be the source and destination HVMs fulfill the first of the above notes, save HVM configurations on the HVMs and then back up the HVM configuration.
Page 158 4. New Policy window is displayed. Input a name for a migration policy and then click OK button. 5. Input a memo in Comment text box in Policy Information as needed and then click Add [Shutdown] button or Add [Concurrent Maintenance] button.
Page 159 6. Add Concurrent Maintenance window is displayed. Select the source LPAR in Source group box and select the destination LPAR in Destination group box. Confirmation window is displayed. Confirm the contents in Confirmation window and then Click OK button. Migration procedures 3-59 HVM Navigator User's Guide - Migration...
Page 160 7. Add entries to a migration policy by repeating the above (5) operation. 8. Confirm entries in the created migration policy in Migration Policy window and then click Save button. 3-60 Migration procedures HVM Navigator User's Guide - Migration...
Page 161 9. Click OK button. You can create a migration policy according to the above procedure. When you need another migration policy, create it according to the above procedure. Migration procedures 3-61 HVM Navigator User's Guide - Migration...
Page 162: Procedure To Execute Policy Migration
Procedure to execute Policy migration Operate HVM Navigator according to the following procedure to execute Policy migration. 1. Select a migration policy in the combo box in Migration Policy window. When you execute Policy migration after creating or editing a migration policy, click Release button.
Page 163 2. The entries registered in selected migration policy are displayed. Confirm the entries and then click Execute button. 3. Confirmation window is displayed. Confirm the contents and then click OK button. Migration procedures 3-63 HVM Navigator User's Guide - Migration...
Page 164 Migration Progress window is displayed. When a migration policy has completed, "Migration completed!" is displayed and is displayed in each row for an entry in Migration Policy window. 3-64 Migration procedures HVM Navigator User's Guide - Migration...
Page 165 4. Click Close button. Migration procedures 3-65 HVM Navigator User's Guide - Migration...
Page 166: Procedure To Interrupt Policy Migration
Procedure to interrupt Policy migration Operate HVM Navigator according to the following procedure to interrupt Policy migration. 1. Click Stop button in Migration. Policy migration is interrupted after the entry which is in progress when you click Stop button finishes. (Policy migration isn't interrupted while an entry is in progress.) 2.
Page 167: Procedure To Edit Policy Migration
Procedure to edit Policy migration You can add or delete entries. Also, you can create a new migration policy with the same entries by changing the name for a migration policy. Procedure to add entry Operate HVM Navigator according to the following procedure to add an entry to a migration policy.
Page 168 3. Add Concurrent Maintenance window is displayed. Select the source LPAR in Source group box and select the destination LPAR in Destination group box. Then, click Add button. Confirmation window is displayed. Confirm the contents and then click OK button. 3-68 Migration procedures HVM Navigator User's Guide - Migration...
Page 169 The procedure to add entries is similar to the one to create migration policy. So, for the detail of the procedure, see "Procedure to create migration policy" in "Policy migration" in "Migration procedures". 4. Confirm the entries in the changed migration policy in Migration Policy window and then click Save button or Save as button.
Page 170 Procedure to delete entry Operate HVM Navigator according to the following procedure to delete an entry from a migration policy. 1. Select a migration policy in the combo box in Migration Policy window and then click Modify button. 2. Select an entry and then click Delete button. 3-70 Migration procedures HVM Navigator User's Guide - Migration...
Page 171 3. Confirm the entries in the changed migration policy in Migration Policy window and then click Save button or Save as button. When you click Save as button, Save as Policy window is displayed. Input the name for a migration policy and then click OK button. 4.
Page 172 Procedure to change the order to execute entries Operate HVM Navigator according to the following procedure to change the order to execute entries. 1. Select a migration policy in the combo box in Migration Policy window and then click Modify button. 2.
Page 173 3. Click Save button or Save as button. When you click Save as button, Save as Policy window is displayed. Input the name for a migration policy and then click OK button. 4. Confirmation window is displayed. Click OK button. Migration procedures 3-73 HVM Navigator User's Guide - Migration...
Page 174: Return Migration
Have all LPARs on HVM 1 migrate to HVM 2. procedures Hitachi Compute Blade HVM Version Upgrade/Revision Update Guide Hitachi Compute Blade 500 Series Management Update HVM firmware. Module Setup Guide Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide Return all LPARs to HVM 1.
Page 175: Saving And Backing Up Hvm Configuration
Saving and backing up HVM configuration Save HVM configurations on the source and destination server blades when you have changed HVM firmware versions or the HVM configurations. Also, back up HVM configurations on the source and destination server blades together when you have changed any or both of the HVM configurations. The expression in BSM/SC may vary depending on the version.
Page 176 2. Select the Chassis where the source or the destination HVM is located and then right-click on the HVM. Next, click [Save to HVM(S)…]. 3. Click Yes button. The following window is being displayed while saving HVM configuration. When this window closes, it tells that saving HVM configuration is completed.
Page 177: Backing Up Hvm Configuration
Backing up HVM configuration The procedure to back up HVM configuration is as follows. 1. Select [HVM Management(M)]-[HVM Configuration Management(H)] in Server Conductor/Blade Server Manager window. 2. Select the Chassis where the source or the destination HVM is located and then right-click on the HVM.
Page 178 3. Click Browse… button and then set the folder to output a backup file and the file name. Next, click OK button. 4. Click OK button. 3-78 Migration procedures HVM Navigator User's Guide - Migration...
Page 179  You can restore an HVM configuration through an SC/BSM, the web console for CB500, or the web console for CB2500. When you restore HVM configuration, don't restore only either one on the source or destination server blade. It may cause MAC address to be duplicated. So, absolutely restore HVM configurations on the source and destination server blades together.
Page 180: Registering/Removing Migration Wwn
The way is supported in the following combination of storage devices and Storage Navigator Modular 2 CLI. Table 3-2 Supported storage device and Storage Navigator Modular 2 CLI Supported version of Supported storage device Hitachi Storage Navigator Modular 2 CLI 9500V AMS 200 AMS 500 Version 11.50 or higher...
Page 181: Flow To Register/Remove Migration Wwn
Flow to register/remove migration WWN Operate HVM Navigator according to the following procedure. Operation of HVM Navigator Start HVM Navigator. Register "Storage Navigator Modular 2 CLI" folder to HVM navigator. (Option window) Click Update button (Main window) Register migration WWPNs to host groups (Storage Password Setting window, Register Migration WWN Setting window) Setting migration paths for source and...
Page 182: Prerequisite Setting
Storage Navigator Modular 2 CLI version 11.50 or higher on the management server. The other versions aren't supported. For installing Storage Navigator Modular 2 CLI, see Hitachi Unified Storage Command Line Interface Reference Guide. ...
Page 183 1. Start HVM Navigator. For starting HVM Navigator, see Hitachi Compute Blade HVM Navigator User’s Guide Getting Started. 2. Select Setting > Option in the menu bar in Main window. Migration procedures 3-83 HVM Navigator User's Guide - Migration...
Page 184 3. Select Migration Option in the left pane. 4. Click Open button in Storage Navigator Setting. 3-84 Migration procedures HVM Navigator User's Guide - Migration...
Page 185 5. Select Storage Navigator Modular 2 CLI folder and then click OK button. 6. Click Apply button or OK button. Migration procedures 3-85 HVM Navigator User's Guide - Migration...
Page 186 7. Select Migration tab. 8. Click Update button. 3-86 Migration procedures HVM Navigator User's Guide - Migration...
Page 187 9. Check Concurrent Maintenance radio button in Mode Selection group box. Migration procedures 3-87 HVM Navigator User's Guide - Migration...
Page 188 10. Click WWN Setting button in Migration Menu group box. 11. Input the IP address for a port on a storage device: You should input the IP address for the port to access the host group to which the WWPN created with the same vfcID is already registered.
Page 189 12. Click Search button. 13. Select the IP address for a port on the storage device to register to HVM Navigator and then click Add button. Migration procedures 3-89 HVM Navigator User's Guide - Migration...
Page 190 14. Click OK button. Storage Password Setting window is displayed. Set the following parameters for security in this window.  Administration Mode: The security parameter on the Storage Navigator Modular 2 CLI  Password Protection: One of the security parameters on a storage device ...
Page 191 The same values as those set on the Storage Navigator Modular 2 CLI and each storage device should be set for each of the above parameters in this window. Otherwise, you may not be able to register migration WWPNs through HVM Navigator.
Page 192 In the following procedure, as an example, the setting when Administration Mode is set on the Storage Navigator Modular 2 CLI and Account Authentication is set on a storage device is explained. When Storage Password Setting window is displayed, not only rows for the storage devices which you have registered in the previous steps but also those for the storage devices which have been registered in advance are displayed.
Page 193 17. Select Account Authentication in Security Type column. 18. Input a user ID in User ID column and a password in Password column. Migration procedures 3-93 HVM Navigator User's Guide - Migration...
Page 194 19. Click OK button. When you register, change, or remove a user ID for Password Protection or Account Authentication, the window showing that an execution file in Storage Navigator Modular 2 CLI folder is being executed after you click OK button on the following Confirm window.
Page 195 21. Register Migration WWN Setting window is displayed. Confirm if the storage devices which you have registered to HVM Navigator in the previous steps are displayed. 22. Confirm registration status of WWPNs, such as what WWPNs are registered, what host groups the WWPNs are registered to, and so on. For the icons displayed in State (Vfc) column and State (Mig) column, see “List of icons”.
Page 196: Registering Migration Wwn To Host Group
Registering migration WWN to host group Register migration WWPNs to host groups according to the following procedure. 1. Check the check boxes for the migration WWPNs to register to host groups: you can check the check boxes for the migration WWPNs which the icon in State (Vfc) is and the one in State (Mig) is 2.
Page 197 3. Click OK button. 4. Click OK button. 5. Confirm that the icons in both Last Status column and Status (Mig) column Migration procedures 3-97 HVM Navigator User's Guide - Migration...
Page 198: Removing Migration Wwn From Host Group
Removing migration WWN from host group Remove migration WWPNs to host groups according to the following procedure. 1. Check the check boxes for the migration WWPNs to remove from host groups: you can check the check boxes for the migration WWPNs which the icon in State (Vfc) is and the one in State (Mig) is 2.
Page 199 3. Click OK button. 4. Click OK button. 5. Confirm that the icon is in Last Status column and the one is Status (Mig) column. Migration procedures 3-99 HVM Navigator User's Guide - Migration...
Page 200: Giving Migration Wwn A Nickname
Giving migration WWN a nickname Give migration WWPNs a nickname according to the following procedure. 1. Check the check boxes for the migration WWPNs to give migration WWPNs a nickname: you can check the check boxes for the migration WWPNs which the icon in State (Vfc) is and the one in State (Mig) is 2.
Page 201 3. Click Default button. 4. Click Execute button. Migration procedures 3-101 HVM Navigator User's Guide - Migration...
Page 202 5. Click OK button. 6. Click OK button. 7. Select Multiple Rows radio button. 3-102 Migration procedures HVM Navigator User's Guide - Migration...
Page 203 8. Confirm that the icon is in Last Status column and the nickname is displayed in Migration WWPN Nickname column. Migration procedures 3-103 HVM Navigator User's Guide - Migration...
Page 204: Exporting Csv File
Exporting CSV file Export a CSV file where the registration status of WWPNs and migration WWPNs is recorded according to the following procedure. 1. Click Export CSV button. 2. Select the folder to export the CSV file and then click Save button. 3-104 Migration procedures HVM Navigator User's Guide - Migration...
Page 205 3. Click OK button. Migration procedures 3-105 HVM Navigator User's Guide - Migration...
Page 206: Adding Storage Device
Adding storage device Add storage devices according to the following procedure. 1. Click Update button. 2. Check Concurrent Maintenance radio button in Mode Selection group box. 3-106 Migration procedures HVM Navigator User's Guide - Migration...
Page 207 3. Click WWN Setting button in Migration Menu group box. When one or more storage devices are registered, Storage Password Setting window are displayed. 4. All storage devices which are registered to HVM Navigator are displayed in Storage Password Setting window. Of the storage devices, you should input values for only the storage devices which you are managing;...
Page 208 5. Click OK button. 6. Click Add Storage button. 3-108 Migration procedures HVM Navigator User's Guide - Migration...
Page 209 7. Input the IP address for a port on a storage device: You should input the IP address for the port to access the host group to which the WWPN created with the same vfcID is already registered. 8. Click Search button. Migration procedures 3-109 HVM Navigator User's Guide - Migration...
Page 210 9. Select the IP address for the port on the storage device to register to HVM Navigator and then click Add button. 10. Click OK button. 3-110 Migration procedures HVM Navigator User's Guide - Migration...
Page 211 11. Confirm that the storage devices have been added to HVM Navigator in Storage Selection group box. 12. Click Password Setting button. Migration procedures 3-111 HVM Navigator User's Guide - Migration...
Page 212 13. Input the same values as those set on each of the added storage devices for them. For the parameters in Storage Password Setting window, see "Prerequisite Setting" in "Registering/removing migration WWN". 14. Click OK button. 15. Register Migration WWN Setting window is displayed. Confirm that the added storage devices are displayed.
Page 213: Commands For Storage Navigator Modular 2 Cli Executed From Hvm
Commands for Storage Navigator Modular 2 CLI executed from HVM Navigator The commands for Storage Navigator Modular 2 CLI which is executed from HVM Navigator are shown in the following table. Table 3-5 Setting for Password Protection and Account Authentication Command Use on HVM Navigator auunitref...
Page 214 Command Use on HVM Navigator auaccountenv -set -uid 001 -authentication -unit [array unit Set account data onto a storage device. name] auaccountenv -rm Remove account data from a storage device. 3-114 Migration procedures HVM Navigator User's Guide - Migration...
Page 215: Other Functions And Settings
Other functions and settings This chapter describes some of the other functions and settings of migration. Functions and settings for Shutdown and Concurrent Maintenance modes  Functions and settings for Shutdown mode  Functions and settings for Concurrent Maintenance mode ...
Page 216: Functions And Settings For Shutdown And Concurrent Maintenance Modes
Functions and settings for Shutdown and Concurrent Maintenance modes Confirming applicable conditions before migration execution You can confirm applicable conditions on your selections before executing LPAR migration in Shutdown mode or in Concurrent Maintenance mode. Follow the procedure below. 1. When you are to execute LPAR migration in Shutdown mode or in Concurrent Maintenance mode, select the source LPAR and the destination LPAR in the “Migration [Shutdown]”...
Page 217 When you are to execute Policy migration, select the target migration policy and the entry in the target migration policy in the “Migration Policy” window, and then click Show Config button in the same window. 2. In the Migration Configuration Viewer window, confirm if the source and the destination values are identical in the group boxes of Server Configuration, HBA Configuration, and NIC Configuration.
Page 218: Specifying Lan Port (Ip Address) For Management Server
HVM access and it should be registered as a BSM IP address on HVM. To specify LAN port IP address to access HVM, see Hitachi Compute Blade HVM Navigator User’s Guide Getting Started for details. Other functions and settings...
Page 219: Tracing Back Migration History On Lpars
Tracing back Migration History on LPARs Migration history on LPARs by means of Migration functions is displayed in Migration History list available on Migration tab in the “Main” window. By tracing back this list, you can find the history and results of migration on the target server.
Page 220 The “Migration History” window specifically shows migration history items (HVM ID, LPAR number, date and time of migration) by LPAR name per migration instance represented as follows:  “Now”: Information on the target LPAR on the HVM where the target LPAR is running.
Page 221: Functions And Settings For Shutdown Mode
Functions and settings for Shutdown mode Automatic shutdown of source LPAR Prerequisite setup To execute automatic shutdown, prerequisite setups depending on OS type shown below are required. OS type: Windows To shut down Windows, prerequisite setups shown below are required. Setup1: Setting up Windows Firewall "Allow (inbound) remote administration exception"...
Page 222: Automatic Shutdown Setup
You are required to Install plink.exe on the management server installing HVM Navigator and specify the path installing plink.exe in. For the setup procedure, see Hitachi Compute Blade HVM Navigator User’s Guide Getting Started. Linux is shut down by executing shutdown command in SSH connection.
Page 223 2. Click Save button inside Guest OS Information (for remote shutdown) subgroup. The setting above attempts log-in to the specified IP address with the specified user ID and password. Accordingly, the HVM-Navigator-installed management server must be provided with a physical path to the source server always accessible by the specified user, while the source server must be set to accept access from the specified user.
Page 224: Changing Setting Of Cpu, Memory And Service Ratio On Destination
Changing setting of CPU, memory and service ratio on destination The function which changes the settings of CPU, memory, service ratio and so on automatically isn't supported on the destination HVM. To change the settings, there are the following two ways. ...
Page 225: Functions And Settings For Concurrent Maintenance Mode
Functions and settings for Concurrent Maintenance mode Executing Rehearsal You can execute Rehearsal to confirm if the resources such as CPU, memory, NIC, FC HBA and so on assigned to an LPAR are available on the destination HVM. Operate HVM Navigator according to the following procedure to execute Rehearsal.
Page 226 2. Confirmation window is displayed. Click OK button. Rehearsal starts. 4-12 Other functions and settings HVM Navigator User's Guide - Migration...
Page 227 3. Migration Progress window is displayed. Confirm the progress of Rehearsal. 4. When Rehearsal finishes, "Migration completed!" is displayed. Click Close button. Other functions and settings 4-13 HVM Navigator User's Guide - Migration...
Page 228: Executing Connectivity Test
Executing Connectivity Test You can execute Connectivity Test to confirm if the communication through migration paths for the source and destination HVMs is available. Operate HVM Navigator according to the following procedure to execute Connectivity Test. 1. Select the source LPAR in Source group box and select the destination LPAR in Destination group box and then click Connectivity Test button in Rehearsal Execute group box.
Page 229 Connectivity Test starts. 3. Migration Progress window is displayed. Confirm the progress of Connectivity Test. Other functions and settings 4-15 HVM Navigator User's Guide - Migration...
Page 230 4. When Connectivity Test finishes, "Connectivity Test completed!" is displayed. Click Close button. 4-16 Other functions and settings HVM Navigator User's Guide - Migration...
Page 231: Extending Timeout Period For Lpar Migration In Concurrent Maintenance
Extending timeout period for LPAR migration in Concurrent Maintenance mode When memory size assigned to an LPAR to migrate is big, or memory load is high and you cannot reduce the memory load, you can extend a timeout period for LPAR migration in Concurrent Maintenance mode. A timeout period for LPAR migration in Concurrent Maintenance mode is set to 900 seconds as default.
Page 232 2. Extend window is displayed. Click OK button. The extended timeout period is displayed in Progress Detail group box. 4-18 Other functions and settings HVM Navigator User's Guide - Migration...
Page 233: Canceling Lpar Migration
Canceling LPAR migration When you see that the LPAR migration in progress won't succeed because transferring all memory data assigned to the LPAR to migrate doesn’t complete within a timeout period for LPAR migration in Concurrent Maintenance mode and so on, you can cancel the LPAR migration. You can cancel LPAR migration in progress in Migration Progress window only while memory data on the source LPAR are being transferred.
Page 234 When Canceling LPAR migration has completed, "Progress : Migration completed!" is displayed in Migration Progress window. 4-20 Other functions and settings HVM Navigator User's Guide - Migration...
Page 235: Monitoring Memory Transfer
Monitoring memory transfer You can monitor memory size remaining on the source LPAR and transfer rate of memory date to the destination LPAR. You can monitor them only while memory data on the source LPAR are being transferred. Operate HVM Navigator according to the following procedure to monitor memory size remaining on the source LPAR and transfer rate of memory date to the destination LPAR.
Page 236 2. Migration Monitor Status window is displayed. Monitor memory size remaining on the source LPAR and transfer rate of memory date to the destination LPAR. 3. Take any of the measure to extend a timeout period for LPAR migration in Concurrent Maintenance mode and the one to cancel LPAR migration depending on the memory transfer state.
Page 237: Usage Notes
Usage notes This chapter describes the usage notes. Backing up and restoring HVM configuration  Initialization of HVM configuration (DC command of management module)  Changing HVM system time on destination HVM  Operation deterrence  Exchanging NIC or FC HBA switches while server blade is in operation ...
Page 238 Memory high-load on guest OS on the LPAR to migrate  Clock on guest OS on the LPAR to migrate in Concurrent Maintenance mode  Network setting on Linux OS on the LPAR to migrate  Confirming if the states of FC HBA ports are stable ...
Page 239 Confirm the applicable notes for each of Shutdown mode and Concurrent Maintenance mode in the following table. Table 5-1 Notes for each of Shutdown mode and Concurrent Maintenance mode Concurrent Item Shutdown Maintenance Backing up and restoring HVM configuration  ...
Page 240 Concurrent Item Shutdown Maintenance Values of Processor Node and Memory Node     HVM Navigator Guide to resolution of slow update  Display in Source and Destination group box Policy migration   Executing migrations by operating multiple HVM Navigators ...
Page 241: Backing Up And Restoring Hvm Configuration
Backing up and restoring HVM configuration When there are LPARs which have failed to be recovered, backed up HVM configuration is necessary. So, back up HVM configurations on the source and destination server blades before and after executing LPAR migration. In addition, do not back up an HVM configuration through an SC/BSM, the web console for CB500, or the web console for CB2500 while saving the HVM configuration or executing LPAR migration because a defective HVM...
Page 242: Initialization Of Hvm Configuration (Dc Command Of Management Module)
Initialization of HVM configuration (DC command of management module) There is a menu item to initialize HVM configuration in DC command of management module. Pay attentions to the following notes when HVM configurations are initialized in the environment which you execute LPAR migration in. ...
Page 243: Changing Hvm System Time On Destination Hvm
Changing HVM system time on destination HVM When you change HVM system time on the destination HVM while executing LPAR migration, the clock on the guest OS running on the LPAR to migrate is not transferred accurately because the changed HVM system time influences the clock on the guest OS.
Page 244: Setting Network Segment Assigned To Activated Lpars As Migration Path
Setting network segment assigned to activated LPARs as migration path When you set any of the network segments such as 1a, 1b, and so on assigned to one or more activated LPARs as migration paths for the source and destination HVMs and execute LPAR migration in Concurrent Maintenance mode, the network load caused by LPAR migration in Concurrent Maintenance mode affects the network performance on the activated LPARs.
Page 245: Migration To Destination With Difference On Connection To Storage Device
(1), (3) - connection directly to storage devices) For the settings on EFI driver, see Hitachi Compute Blade CB2000 User's Guide, Hitachi Compute Blade CB320 User's Guide, Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide.
Page 246: Been Executed
Changing VNIC System No. on the system environment where LPAR migration has been executed MAC addresses assigned to shared NIC ports and virtual NIC ports on LPARs on an HVM may be duplicated, when you set a VNIC System No., which has been set for another HVM, for the HVM on the system where LPAR migration has been executed.
Page 247: Service Ratio After Migration
Service ratio after migration Migration functions of HVM Navigator carry the existing service ratio value, which is used for allocation of shared CPU resources to an LPAR, from the source LPAR to the destination LPAR as it is. Attention has to be paid, however, that the service ratio value after the migration means the ratio relative to the service ratios already allocated to the other LPARs on the same destination HVM.
Page 248: Migration Of Lpar Enabling Vc (Virtual Com) Console
When such an LPAR migrates, confirm the network settings. For virtual NICs, see Hitachi Compute Blade CB2000 User's Guide, Hitachi Compute Blade CB320 User's Guide, Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide.
Page 249: Migration Of Usb Assignment State
Migration of USB assignment state Scheduling mode of assigned USB is dedicated  When you have an LPAR migrate in Shutdown mode When you have an LPAR to which a dedicated USB device is assigned migrate in Shutdown mode, operate the LPAR as follows. –...
Page 250: Scheduling Mode Of Assigned Usb Is Exclusive Shared
Scheduling mode of assigned USB is exclusive shared  When you have an LPAR migrate in Shutdown mode – HVM firmware version 17-71 or earlier on source server blade When an LPAR on HVM firmware version 17-71 or earlier migrates, the USB device of PCI Device #1 is assigned on destination server blade, that is, the status of USB device of PCI Device #1 becomes “A (assigned)”...
Page 251 LPAR to migrate becomes "A (assigned)". However, When an LPAR which assigned state is "R (running)" does not exist, the assigned state of the LPAR to migrate becomes "R (running)". For USB Auto Allocation, see Hitachi Compute Blade CB320 User's Guide, Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide.
Page 252: Certain Fc Hba Port Is Changed From Shared To Dedicated
Certain FC HBA port is changed from shared to dedicated When an LPAR on the source or destination server blade which the shared FC HBA port whose vfcID is "1" is assigned migrates, the following problems occur. Duplication of displayed or retrieved WWN When the FC HBA port set to shared mode is changed to dedicated mode, WWN of the FC HBA port are displayed or retrieved wrongfully in the following windows and by the following command.
Page 253: Shutting Down Or Rebooting Guest Os On The Lpar To Migrate
Setup2: Setting up local accounts For the prerequisite setups' procedures, see “Procedure for Shutdown mode”. Note2: Failure on Remote Shutdown of Windows Server 2008 When Forced shutdown check box inside Guest OS Information (for remote shutdown) subgroup of Migration Setting group box is not checked while Shutdown Guest OS (Source) check box inside migration option subgroup of the same group box is checked in the “Migration”...
Page 254 Figure 5-1 Migration Progress window 5-18 Usage notes HVM Navigator User's Guide - Migration...
Page 255: Migrating Lpar Where Efi Shell Is Running
Migrating LPAR where EFI Shell is running Do not have an LPAR where EFI Shell is running migrates. If you have an LPAR migrate where EFI Shell is running, LPAR migration would fail. Figure 5-2 Migration Progress window Packet-lost during LPAR migration While suspending an LPAR while the LPAR is migrating in Concurrent Maintenance mode, packets sent to the LPAR with UDP communication are lost.
Page 256: Clock On Guest Os On The Lpar To Migrate In Concurrent Maintenance Mode
LPAR to migrate, you can adjust the clock of the guest OS to HVM system time by executing “Adjust LPAR Time” in Date and Time screen in HVM screen, instead. For “Adjust LPAR Time”, see Hitachi Compute Blade 2000 USER’S GUIDE, Hitachi Compute Blade 500 Series Logical partitioning manager User’s Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide.
Page 257: Confirming If The States Of Fc Hba Ports Are Stable
Confirming if the states of FC HBA ports are stable When you execute LPAR migration in Concurrent Maintenance mode or roll back WWNs, confirm if all of the states of FC HBA ports installed both on the source and destination server blades are stable. If any of the states are unstable, wait a while without executing LPAR migration in Concurrent Maintenance mode or rolling back WWNs.
Page 258 Figure 5-3 HVM Console window 5-22 Usage notes HVM Navigator User's Guide - Migration...
Page 259: Guide To Resolution Of Slow Update
HVM firmware versions which don't support LPAR migration. icons are displayed for all the LPARs on the HVMs which don't support LPAR migration. For the HVM firmware versions which support LPAR migration, see Hitachi Compute Blade HVM Navigator User’s Guide—Getting Started. Usage notes...
Page 260: Policy Migration
Policy migration You cannot register entries for both Shutdown mode and Concurrent Maintenance mode together in a migration policy. Executing migrations by operating multiple HVM Navigators Do not migrate LPARs from or to an HVM by operating the HVM in multiple HVM Navigators simultaneously.
Page 261: Sc/Bsm Alerts For Shutdown Mode
SC/BSM alerts for Shutdown mode You can confirm the events of Migration functions of HVM Navigator in SC/BSM alert messages. An alert message classified “Information” is taken at every start and end of Migration functions of HVM Navigator at the source and at the destination.
Page 262: Sc/Bsm Display After Migration With Windows Server 2008 R2
SC/BSM Display after Migration with Windows Server 2008 When a server running Windows Server 2008 R2 and using NIC teaming migrates by means of Migration functions of HVM Navigator, SC/BSM display of partitions and LPAR numbers after such migration may sometimes remain unchanged.
Page 263: Migrating Lpar Form The Standby Server Blade After Cold Standby Switching
Migrating LPAR form the standby server blade after Cold standby switching When you have an LPAR migrate from the standby server blade to another server blade after "Cold standby switching" and then you execute "Recover to active system", 2 LPARs with the same configuration are created on 2 server blades: the standby server blade and another server blade.
Page 264: Test Of Configuring N+M Cold Standby
Test of Configuring N+M Cold Standby Do not execute the alert for test of configuring N+M cold standby during migration and execute LPAR migration during test of configuration N+M cold standby because the LPAR to migrate might disappear or MAC addresses and WWNs might be duplicated.
Page 265: Suppression Of Hvm Auto Shutdown During Migration
Suppression of HVM auto shutdown during migration Each HVM in the system equipped with UPS is set to execute auto shutdown, which causes the HVM to shut down itself automatically when all LPARs on the HVM become deactivated (power-off state). On the other hand, migration of LPARs needs to be executed while the HVM is active.
Page 266 5-30 Usage notes HVM Navigator User's Guide - Migration...
Page 267: Troubleshooting
Troubleshooting This chapter describes the troubleshooting. Troubleshooting flow  Taking action when LPAR activation has been disabled  Taking action when Policy migration failed  Troubleshooting FAQs  Error information  Collecting failure information  Troubleshooting HVM Navigator User's Guide - Migration...
Page 268: Troubleshooting Flow
HVM Navigator files for HVM Navigator in Main window. in Main window. : For retrieving Technical Information files, see Hitachi Compute Blade HVM Navigator User's Guide - Getting Started. Figure 6-1 Troubleshooting flow Troubleshooting HVM Navigator User's Guide - Migration...
Page 269: Taking Action When Lpar Activation Has Been Disabled
Taking action when LPAR activation has been disabled Event When the execution of Migration functions has failed, activation (power-on) of the source LPAR or the destination LPAR may sometimes be disabled. HVM screen shows “The specified LPAR has corrupted in an LPAR migration, please try to recover the LPAR.”...
Page 270 Solution 1. Confirm the error content in the error-stopped Migration Progress window. Figure 6-3 Migration Progress window 2. Inspect the error-stopped migration entry in the “Migration Policy” window. Click Show Config button to open the “Migration Config Viewer” window. Figure 6-4 Migration Policy window Troubleshooting HVM Navigator User's Guide - Migration...
Page 271 3. Inspect the configuration items of the source and destination LPARs in Migration Config Viewer window. Figure 6-5 Migration Config Viewer window Troubleshooting HVM Navigator User's Guide - Migration...
Page 272 4. Take the following actions depending on your finding:  If the error displays and your configuration confirming results have identified the error cause and retry seems possible, eliminate the error cause and then click Retry button in the confirmation window. Figure 6-6 Confirmation window ...
Page 273: Troubleshooting Faqs
Troubleshooting FAQs Error message “Failed Get Migration List (mms: ls)” popped up Event When you click Update button or Migration button, the error window below opens. Figure 6-7 Migration window When this event occurs, there are three suspect causes:  JRE (Java Runtime Environment) is not installed or the installed JRE is not in an applicable version.
Page 274 Solution 1: When JRE is not installed or the installed JRE is not in an applicable version 1. From the menu bar in the “Main” window, click Setting and select Option. Figure 6-8 Main window 2. In the “Option” window opened, select Migration Service in the left pane. Figure 6-9 Option window Troubleshooting HVM Navigator User's Guide - Migration...
Page 275 Set or correct the environment variable to the installed JRE according to Hitachi Compute Blade HVM Navigator Installation Manual. Solution 3: When communication between HVM Navigator and HVM is lost 1. Confirm if the HVM registered to be managed by HVM Navigator is up and normally running through HVM screen, host management window of SC/BSM, or HVM configuration management window of SC/BSM.
Page 276: Remote Shutdown Of Server Has Failed
Remote shutdown of server has failed Event An LPAR migration has failed with a message including “Process: Guest OS Shutdown” or “Shutdown waiting”. Figure 6-11 Migration Progress window Solution 1. Click Update button in the “Main” window. Figure 6-12 Main window 6-10 Troubleshooting HVM Navigator User's Guide - Migration...
Page 277 For Linux, confirm if “SSH Component Not Found” message is shown in the status bar. If it is, the path to the installation folder of Plink is not correctly specified. Specify the correct path according to Hitachi Compute Blade HVM Navigator User’s Guide—Getting Started.
Page 278 Waiting TimeOut Limit text box, and click Apply or OK button. Figure 6-14 Option window For installing plink.exe and specifying the path pointing at the folder where Plink.exe is installed, see Hitachi Compute Blade HVM Navigator User’s Guide— Getting Started. 6-12 Troubleshooting...
Page 279: Migration Has Failed With "The Source Lpar Is Activated" Message
Migration has failed with “The source LPAR is activated” message Event An LPAR migration has failed with message “The source LPAR is activated” displayed, though the LPAR has started migrating with the icon showing the LPAR status of the LPAR indicating “deactivated” in “Migration” window. Figure 6-15 Migration Progress window This event occurs when the actual state of an LPAR is different from the one recognized by HVM Navigator (e.g., “Update”...
Page 280 Solution 1. Click Update button in the “Main” window. Figure 6-16 Main window 2. In the “Migration” window, confirm the state of the error-stopped LPAR. If the source server turns out to be in the Activate state, shut down it and retry migration.
Page 281: Migration Has Failed With "The Specified Blade Is Busy" Message
Migration has failed with “The specified blade is busy” message Event Although there is no problem in the HVM and LPAR configuration in the source and the destination, or successful migration of like instances in the past is proven, a migration execution error-stopped with “The specified blade is busy” message.
Page 282: Source And Destination Panes Show "Un-Registration" Chassis
Source and destination panes show “Un-registration” chassis Event When Update or Update Cancel button is clicked in the “Main” window, Source and Destination panes in the “Migration” window show “Un- registration” chassis. Figure 6-18 Migration [Shutdown] window Solution Reopen the “Migration” window by the following procedure. 1.
Page 283: Migration Has Failed By Response Timeout
Migration execution error-stopped by Response Timeout. Figure 6-19 Migration Progress window Solution Reset the time out period for connection with HVMs longer according to Hitachi Compute Blade HVM Navigator User’s Guide—Getting Started. However, if LPAR migration fails with this message in Refresh HVM Information process, you could clear this error by clicking Update button in Main window.
Page 284: Migration Has Failed With "Error Occurred During Initialization Of Vm" Message
Migration has failed with “Error occurred during initialization of VM” message Event Migration execution error-stopped with “Error occurred during initialization of VM, java lang Class Not Found Exception: error in opening JAR file” message. Figure 6-20 Migration Progress window Solution Terminate unnecessary application to reserve enough physical memory and retry migration.
Page 285: Cannot Access Guest Os
Cannot access guest OS Event The management server might not access the guest OS on migrated LPARs because Windows Firewall/Internet Connection Sharing(ICS) service does not start on the guest OS on destination server blade after migration. This issue is introduced on Microsoft support page. http://support.microsoft.com/kb/922918 Solution See the web page as shown above and take measures as needed.
Page 286: Migration Has Failed With "Transferring Device Data Cannot Be Completed Within An Lpar Suspension Period." Message
Migration has failed with “Transferring device data cannot be completed within an LPAR suspension period.” message Event LPAR migration has failed with “Transferring device data cannot be completed within an LPAR suspension period.” This error occurs because a migrated LPAR cannot boot on the destination server blade within LPAR suspension time.
Page 287: Migration Has Failed With "Connection Refused (Hvm-Hvm)" Message
Migration has failed with “Connection refused (HVM-HVM)” message Event LPAR migration has failed with “Connection refused (HVM-HVM)”. This error occurs because there is something wrong with the network connection between the source and the destination server blade or the management path connected with the destination server blade. Figure 6-22 Migration Progress window Solution Confirm if errors for management paths and or migration paths on the source...
Page 288: Message
Migration has failed with “Wait until another operation is completed, and retry.” message Event LPAR migration has failed with “Wait until another operation is completed, and retry.” This error occurs because you execute the LPAR migration while a popped up display in HVM screen is being displayed.
Page 289: Migration Has Failed With "Hvm Access Error" Message
So, be sure that the timeout may occur again though you take this measure. For setting a timeout period for connection with HVMs, see Hitachi Compute Blade HVM Navigator User’s Guide—Getting Started. However, if LPAR migration has failed with this error after Migration process, you can clear this error by clicking Update button in Main window.
Page 290: Intensive." Message
Migration has failed with “LPAR Migration process was canceled Memory write is intensive.” message Event LPAR migration has failed with “LPAR Migration process was canceled Memory write is intensive”. This error shows that transferring memory data on the guest OS on the LPAR to migrate to the destination server blade hasn’t completed within a timeout period for LPAR migration in Concurrent Maintenance mode.
Page 291: Migration Has Failed After Migration Process Had Been Completed
2. When you find out one or more errors in HVM System Logs screen in HVM screen, retrieve HVM dump files and Technical Information files for HVM Navigator in Main window. For retrieving Technical Information files, see Hitachi Compute Blade HVM Navigator User's Guide - Getting Started. Troubleshooting...
Page 292: Emg000000003004006:000000000000003B:0000000000000030:(0):Hvm(S Rc):Internal Error."
1. Retrieve HVM dump files and Technical Information files for HVM Navigator in Main window. For retrieving Technical Information files, see Hitachi Compute Blade HVM Navigator User's Guide - Getting Started. 2. Execute the LPAR migration in Concurrent Maintenance mode again.
Page 293: Emg000000002Ab4006:000000000000003E:0000000000000030:(0):Hvm(S Rc):Internal Error. The Hvm Detected An Fc Error."
Migration has failed with "EMG000000002ab4006:000000000000003e:0000000000000030:( 0):HVM(SRC):Internal error. The HVM detected an FC error." Event LPAR migration has failed with “EMG000000002ab4006:000000000000003e:0000000000000030:(0):HVM(SR C):Internal error. The HVM detected an FC error.” This error shows that I/O load on the HVM has been too high to execute LPAR migration in Concurrent Maintenance mode because of the I/O requests from the guest OS.
Page 294: Migration Wwn)."
=(the time period set in “Login Delay Time” textbox in “Storage Login Setting” in “Option” window) * 2 + 5 seconds For changing the timeout period to log into storage device, see Hitachi Compute Blade HVM Navigator User's Guide - Getting Started.
Page 295: Error."
Migration has failed with "HVM(SRC):Internal error. The HVM detected an FC error." Event LPAR migration has failed with “HVM(SRC):Internal error. The HVM detected an FC error.” This error shows that LPAR migration has failed due to the zoning configuration for the guest OS to migrate. (Confirm the error code shown in Migration Progress window not to identify the error as another one.
Page 296: Emg0000000000003005:0000000000000000:0000000000000222:(1):Lpar Mover(Dst):Unknown Error"
Migration has failed with "EMG0000000000003005:0000000000000000:0000000000000222 :(1):LPARMover(DST):Unknown error" Event LPAR migration has failed with "EMG0000000000003005:0000000000000000:0000000000000222:(1):LPARM over(DST):Unknown error" When this error occurs, the scheduling modes of the NIC controllers assigned to the source LAR as VF NICs and the ones of the NIC controllers mounted on the same slot locations where the NIC controllers assigned to the source LPARs are mounted on the source server blade may be different.
Page 297: Error Information
Error information Error information shown in the top area of the “Migration Progress” window provides error message (error code) in red large characters and suggested actions in black normal characters. Basically, you are expected to follow such actions suggested. For errors detected by the execution modules of Migration functions, also see the detailed error information in detail field explained in the subsections below.
Page 298: Detailed Error Information Detected By Migration Management Client
Detailed error information detected by Migration Management Client Format “EMG” op1 : don’t_care : don’t_care : (don’t_care) : ”MMC” : message  “EMG”: Fixed characters meaning error message.  “MMC”: Fixed characters meaning Migration Management Client.  don’t_care: Values at this position are negligible. ...
Page 299: Detailed Error Information Detected By Migration Management Server
Detailed error information detected by Migration Management Server Format “EMG” op1 : op2 : don’t_care : (op3) : ”MMS” : message  “EMG”: Fixed characters meaning error message.  “MMS”: Fixed characters meaning Migration Management server.  don’t_care: Values at this position are negligible. ...
Page 300 Message [interpretation] Suggested action 0x00 00000006 0020 02 0x0000 0000 0000 0000 0x01 The specified LPAR is Recover the LPAR and damaged (Migration LPAR). retry. Recover the LPAR. 0x00 00000006 0040 02 0x0000 0000 0000 0000 0x01 Connection refused (MMS- Check if the source HVM is SrcHVM) connected to the network...
Page 301 Migration process was of source and destination canceled. server blades and retry. 0x00 00001011 0080 02 0x0000 0000 0000 0000 0x01 This F/W version of the HBA Install Hitachi Fibre channel card is not support LPAR firmware version supporting Migration. Concurrent Maintenance mode.
Page 302 Message [interpretation] Suggested action 0x00 1******* 0030 02 0x0000 0000 0004 ffff 0x01 The MMS could not define an Reserve enough amount of LPAR because there is not free memory in the enough memory in the destination HVM and then destination blade.
Page 303 Message [interpretation] Suggested action 0x00 4******* 0030 02 0x 4-byte_BusDevFunc 0x01 The destination blade does Check if the destination 0000 0000 not have an installed shared HVM has a physically FC device installed FC that (Bus#:Dev#.Func# = corresponds to the FC port 00:03.4) to define an LPAR.
Page 304 Message [interpretation] Suggested action 0x00 80000003 0031 02 0x0000 0000 0000 0000 0x01 The MMS could not activate Resolve the fragmentation the LPAR because of memory in the destination HVM and then retry migration. fragmentation. [Could not reserve memory required to activate LPAR at the destination due to memory fragmentation.] 0x00 80000004 0030 02 0x0000 0000 0020 000b...
Page 305: Module
Detailed error information detected by Migration Management Server thread module Format “EMG” op1 : don’t_care : don’t_care : (op3) : ”MMS Thread” : message  “EMG”: Fixed characters meaning error message.  “MMS Thread”: Fixed characters meaning Migration Management Server thread module that executes migration.
Page 306: Detailed Error Information Detected By Lpar Mover Module
Detailed error information detected by LPAR Mover module Format “EMG” op1 : don’t_care : don’t_care : (op3) : ”LPAR Mover” : message  “EMG”: Fixed characters meaning error message.  “LPAR Mover”: Fixed characters meaning LPAR Mover module that executes migration on HVM side.
Page 307: Detailed Error Information Detected By Recovery Module
Detailed error information detected by Recovery module Format “EMG” op1 : don’t_care : don’t_care : (op3) : ”Recovery” : message  “EMG”: Fixed characters meaning error message.  “Recovery”: Fixed characters meaning Recovery module.  don’t_care: Values at this position are negligible. ...
Page 308: Detailed Error Information Detected By The Source Hvm
0x 00000000 0200 40 06 detected. 0x 00000000 02aa 40 06 0x0000 0000 0000 003d 0x30 LPAR Migration was canceled. Check Hitachi Fibre channel Guest OS is in boot process driver versions on source 0x 00000000 02ab 40 06 or FC-HBA Driver does not...
Page 309: Collecting Failure Information
Collecting failure information When you cannot resolve a failure which has occurred on HVM Navigator, see Hitachi Compute Blade HVM Navigator User's Guide - Getting Started. Troubleshooting 6-43 HVM Navigator User's Guide - Migration...
Page 310 6-44 Troubleshooting HVM Navigator User's Guide - Migration...
Page 311 List of icons This chapter describes the icons which are displayed in the windows. List of icons HVM Navigator User's Guide - Migration...
Page 312 The icons showing states of HVMs in the tree view in the “Migration” or “Add Migration” window are shown in Table 7-1. Table 7-1 Icons representing statuses of HVMs Icon Showing An HVM that succeeded in the last status update. (Normal state.) An HVM that has failed in the last status update.
Page 313 The icons showing the state of LPAR migration in the “Migration Progress” or “Migration Policy” window are shown in Table 7-3. Table 7-3 Icons representing execution statuses of migration Icon Showing The process normally ended. The process is in progress. The process is in the execution queue and waiting for execution.
Page 314 List of icons HVM Navigator User's Guide - Migration...
Page 315 HVM Navigator User's Guide - Migration...
Page 316 Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com Regional Contact Information Americas +1 408 970 1000 [email protected] Europe, Middle East, and Africa +44 (0) 1753 618000 [email protected] Asia Pacific +852 3189 7900 [email protected] MK-99COM024-12...

Hitachi NVM Navigator v03-07 User Manual

Quick Links

Troubleshooting

Related Manuals for Hitachi NVM Navigator v03-07

Summary of Contents for Hitachi NVM Navigator v03-07

Table of Contents