Hitachi Compute Blade 500 Series OS Installation Guide for Windows Server 2008 R2 · 2019-04-23 · Preface vii Hitachi Compute Blade 500 Series OS Installation Guide for Windows

MK-91CB500019-07

Hitachi Compute Blade 500 Series OS Installation Guide

for Windows Server 2008 R2

FASTFIND LINKS

Document Organization

Product Version

Getting Help

Contents

ii

Hitachi Compute Blade 500 Series OS Installation Guide for Windows Server 2008 R2

© 2012-2014 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of 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. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at https://portal.hds.com. Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation. AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International Business Machines Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

Contents iii


Contents

Preface ................................................................................................... v Intended Audience .............................................................................................. vi Product Version ................................................................................................... vi Release Notes ..................................................................................................... vi Document Organization ....................................................................................... vi Referenced Documents ....................................................................................... vii Document Conventions ...................................................................................... viii Convention for storage capacity values ................................................................. ix Getting Help ........................................................................................................ x Comments ........................................................................................................... x

Installation overview ............................................................................. 1-1 Overview .......................................................................................................... 1-2 Before installation ............................................................................................. 1-3

OS installation ...................................................................................... 2-1 Restrictions for installation ................................................................................. 2-2 Installing Windows Server 2008 R2 ..................................................................... 2-5 Restrictions ..................................................................................................... 2-11

Driver/utility installation ........................................................................ 3-1 Installing with Compute Systems Installer ........................................................... 3-2 Installing without Compute Systems Installer ..................................................... 3-10 Other settings ................................................................................................. 3-29 After installation .............................................................................................. 3-37

Using supplied software ........................................................................ 4-1 Supplied software .............................................................................................. 4-2

LAN connection .................................................................................... 5-1 Connecting between LAN device and LAN switch module ...................................... 5-2

Using Windows Hypervisor 2.0 .............................................................. 6-1 Hyper-V 2.0 overview ........................................................................................ 6-2 Configuring system for Hyper-V 2.0 .................................................................... 6-3 Installing Hyper-V 2.0 ........................................................................................ 6-8

iv Contents


Restrictions for using Hyper-V 2.0 ..................................................................... 6-11 Turning on/off power for server blade .....................................................7-1

Turning on/off .................................................................................................. 7-2

Preface v


Preface

This document describes how to use the Compute Blade 500 series.

This preface includes the following information:

Intended Audience Product Version Release Notes Document Organization Referenced Documents Document Conventions Convention for storage capacity values Getting Help Comments

Notice: The use of Compute Blade 500 series and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data Systems.

vi Preface


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 hardware installation of computer systems.

• The reader is familiar with the location where the Compute Blade will be installed, including knowledge of physical characteristics, power systems and specifications, and environmental specifications.

Product Version • This document revision applies to Compute Blade 500 Series CB 520X.

Release Notes

Read the release notes before installing and using this product. They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document.

Document Organization The table below provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter.

Chapter Description

Chapter 1, Installation overview Describes the installing overview for Windows server 2008 R2.

Chapter 2, OS installation Describes installation procedures of Windows server 2008 R2.

Chapter 3, Driver/utility installation

Describes the installation procedures of drivers/utilities for Windows Server 2008 R2 using the Driver and Utility for Windows DVD-ROM.

Chapter 4, Using supplied software Describes the usages of software products included in this system.

Chapter 5, LAN connection Describes the LAN connection.

Chapter 6, Using Windows Hypervisor 2.0 Describes Windows Hypervisor 2.0 (Hyper-V 2.0).

Chapter 7, Turning on/off power for server blade Describes turning on/off power.

Preface vii


Referenced Documents • CB 500 User’s manuals

– EFI User’s Guide, MK-91CB500024 – Logical partitioning manager User’s Guide, MK-91CB500068 – Remote Console User’s Guide, MK-91CB500018 – Server Blade Setup Guide, MK-91CB500012

• Related documents – The following three doscuments are described as LAN Advanced

Function Manual (for * *) in this document. • Hitachi Compute Blade LAN Advanced Function Manual for Broadcom,

MK-99COM107 • Hitachi Compute Blade LAN Advanced Function Manual for Emulex,

MK-99COM082 • LAN Advanced Function Manual for Intel, MK-91CB500033

– The following two doscuments are described as MegaRAID Storage Manager Version xxx Instruction Manual in this document. • MegaRAID Storage Manager Version 8.31-01 Instruction Manual,

MK-99COM085 • MegaRAID Storage Manager Version 11.08.03-02 Instruction Manual,

MK-99COM030 – Hitachi Gigabit Fibre Channel Adapter User’s Guide (BIOS/EFI), MK-

99COM009 – OneCommandManager Guide, MK-91CB500031

viii Preface


Document Conventions This term “Compute Blade” refers to all the models of the Compute Blade, unless otherwise noted.

The Hitachi Virtualization Manager (HVM) name has been changed to Hitachi logical partitioning manager (LPAR manager, or LP). If you are using HVM based logical partitioning feature, substitute references to Hitachi logical partitioning manager (LPAR manager, or LP) with HVM.

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

< > (angled brackets) Variable (used when italic is not enough to identify variable).

[ ] (square bracket) Optional values

{ } braces Required or expected value

| vertical bar Choice between two or more options or arguments

_(underline) Default value, for example, [a | b]

Preface ix


This document uses the following icons to draw attention to information:

Icon Meaning Description

WARNING This indicates the presence of a potential risk that might cause death

or severe injury.

CAUTION This indicates the presence of a potential risk that might cause

relatively mild or moderate injury.

NOTICE NOTICE This indicates the presence of a potential risk that might cause severe damage to the equipment and/or damage to surrounding properties.

Note This indicates notes not directly related to injury or severe damage to

equipment.

Tip This indicates advice on how to make the best use of the equipment.

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 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical storage capacity values (for example, logical device capacity) are calculated based on the following values:

Logical capacity unit Value

1 block 512 bytes

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

x Preface


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]. Include the document title and number including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation.

Thank you!

https://portal.hds.com/

mailto:[email protected]

1

Installation overview 1-1


Installation overview

This chapter describes the installing overview for Windows server 2008 R2.

Overview Before installation

1-2 Installation overview


Overview

This section provides a flowchart for installing Windows Server 2008 R2.

Installation general flow

Before installation - Preparing installation media - Preparing virtual drive - Backing up necessary files - Setting up disk - Initializing EFI setting - Advance preparation

OS installation - Installing Windows Server 2008 R2 - Installing Windows Server 2008 R2 SP1

Driver/utility installation

After Installation - Updating OS using Windows Update - Setting up each component and utility - Installing other applications as necessary - Additional setting when using LP mode

Installing without Compute Systems Installer

Other settings - Checking information for driver updates - Applying patch files - Additional setting when using LP mode

Updating registry - Setting NMI Dump - Setting Disk TimeOut

Installing drivers - Installing Display driver - Installing Chipset driver - Installing LAN driver - Installing SAS driver - Installing iSCSI driver - Updating Fibre Channel driver - Installing Mezzanine card driver

Installing utilities - Installing MegaRAID Storage Manager - Installing OneCommand Manager - Installing OneCommand NIC Teaming and

VLAN Manager - Installing Mezzanine card utility

Installing with Compute Systems Installer

• Installing drivers - Installing Display driver - Installing Chipset driver - Installing LAN driver - Installing iSCSI driver - Updating Fibre Channel driver - Installing Mezzanine card driver

• Installing utilities - Installing MegaRAID Storage Manager - Installing OneCommand Manager - Installing OneCommand NIC Teaming and

VLAN Manager - Installing Mezzanine card utility

• Updating registry - Setting NMI Dump - Setting Disk TimeOut

• Setting Windows Error Recovery

Setting Windows Error Recovery



Before installation

You need to install both OS and Driver/Utility. You can install drivers and utilities with or without Compute Systems Installer. We recommend using the Compute Systems Installer for easy installation.

• Install the Driver/Utility after the OS installation, otherwise Windows Server 2008 R2 cannot operate properly.

• Use the attached CD/DVD-ROMs with the server blade for installing the OS and Driver/Utility.

• Use the specified driver in the procedure. Otherwise, the application does not work properly.

Preparing installation media

Prepare the installation media for the OS. Select appropriate Setup DVD-ROMs for your system in the following tables.

Table 1-1 Windows Server 2008 R2 Standard

Printed Name Official Name

Setup DVD DVD-ROM for Microsoft Windows Server 2008 R2 Standard, Retail Edition or Volume License

Retail package/volume license DVD-ROM for Microsoft Windows Server 2008 R2 Standard

Table 1-2 Windows Server 2008 R2 Enterprise


Setup DVD DVD-ROM for Microsoft Windows Server 2008 R2 Enterprise, Retail Edition or Volume License

Retail package/volume license DVD-ROM for Microsoft Windows Server 2008 R2 Enterprise

Connect to the server blade using the remote console for the installation. For details, see Remote Console User’s Guide.



Table 1-3 Windows Server 2008 R2 Datacenter


Setup DVD DVD-ROM for Microsoft Windows Server 2008 R2 Datacenter, Retail Edition or Volume License

Retail package/volume license DVD-ROM for Microsoft Windows Server 2008 R2 Datacenter

Table 1-4 Windows Server 2008 R2 Service Pack1


Service Pack DVD

DVD-ROM for Microsoft Windows Server 2008 R2 Service Pack 1

Preparing virtual drive

The following is the workflow for preparing virtual drive.

Inserting setup DVD-ROM

Insert the setup DVD-ROM on the CD/DVD drive of system console.

Inserting setup DVD-ROM

Starting remote console

Setting virtual drive



Starting remote console

Start a remote console. Perform following procedure for starting the remote console. 1. Start a new web browser from the system console. 2. Enter the URL of management module web console (enter

“https://192.168.0.1/” when factory default setting) into the address field box of the browser.

Table 1-5 Factory default account settings for the system administrator

Item Factory default

IP address of management module 192.168.0.1

URL of Web console https://192.168.0.1

• The above URL indicates the default IP address of management module, and port number is not entered since using default number. If you changed the IP address of management module, and the port number of web console, enter the corresponding URL for your environment.

• The URL is configured in the following form: http://< IP address>:< port number> or https://< IP address>:< port number>

• The default port number: – http: 80 – https: 443

3. Login the Web console of the management module. 4. The following table describes the factory default account settings for the

system administrator.

Table 1-6 Factory default account settings for the system administrator

Item Factory default

User ID administrator

Password password



5. Click the Resources tab > the target server blade from the menu tree. 6. Click the Condition tab > Start Remote Console from the Server blade

Action pull down menu.

7. The remote console window is displayed.

Power operation through the remote console is disabled while using the server blade in the LP mode. You cannot operate turning on power, turning off power forcibly, and resetting. Execute server blade power operation and LPAR booting operation through the Web console in the LP mode.

• A warning message may appear when the remote console is started. The message varies with the Java VM version. For details, see Remote Console User’s Guide.

• CB 520H A1/B1 server blades with BMC 01-27 or earlier will display the login screen of Web console. For details, see Remote Console User’s Guide.

Setting virtual drive

To set up the virtual drive for reading the setup DVD-ROM. Perform following procedure for setting the virtual drive. 1. Click Tools > Launch Virtual Media on the menu of remote console. 2. Virtual Media Session window is displayed.



3. Check Mapped in the CD/DVD drive for setup.

Don't close the Virtual Media Session window while using the virtual CD/DVD by pressing the [Exit] or [x] button. If you close the window, the virtual media session is terminated and the drive(s) is(are) disconnected from the server blade.

Backing up necessary files

To back up data that you need in advance.

NOTICE The data in the HDD or SSD is deleted when you re-install the OS.

Setting up disk

When you need to install internal disk arrays or external disk array devices, see those manuals to create RAID and configure disks.

Initial setting of EFI

Set the boot device configuration as the EFI initial setting. See EFI User’s Guide that you need.



Advance preparation

The server blade is turned on.

For operating the server blade in the LP mode, see Using LP mode. .

1. Click Power > Power On in the tool bar of the remote console.

2. Press any key to boot from CD or DVD is displayed, and then press any key immediately.

• When pressing a key with a pause, the existing OS may start instead of booting from the DVD-ROM. In that case, shut down the OS, and then go back to step 1.

• When pressing a key more than once, Windows Boot Manager may start. In that case, select Windows Setup [EMS Enabled] and continue the installation.



Using LP mode

The following is the workflow for advance preparation.

Other operation procedure is different according to the management module firmware version. Boot order setting procedure is also different according to version. See the procedure of your management module firmware version.

[Earlier than version A0125 [Version A0125 or later] and CB 520X]

• Setting up LPAR manager

Select a LPAR manager firmware, initialize LPAR manager, activate LPAR manager, and then, save the LPAR creation and configuration data. For details, see Server Blade Setup Guide.

• Creating LPARs

Create LPARs. For details, see Server Blade Setup Guide.

For installing and using Windows Server 2008 R2, the following LPAR configuration is recommended:

Item Recommended value

Processor 2 or more 1

Memory 2.0GB or larger 2

Disk The LPAR on which to install OS requires 40GB or larger capacity. 3

Network 1 or more NICs

1. Required to be no less than 1.

2. Required to be no less than 1.0 GB of memory per processor.

3. Required to be no less than 23 GB.

Setting up LPAR manager

Creating LPARs

Setting up boot order

Saving configuration information

Activating LPARs

Setting up LPAR manager

Creating LPARs

Setting up boot order

Saving configuration information

Activating LPARs



• Saving configuration information

Save the configuration information. For details, see Server Blade Setup Guide.

• Activating LPARs

Activate the LPAR. For details, see Server Blade Setup Guide.

• Setting up boot order

Set up boot order for the LPAR; then, create boot option. You can also change the boot order.

[Earlier than version A0125 and CB 520X]: For details, see Logical partitioning manager User’s Guide.

[Version A0125 or later]: For details, see Server Blade Setup Guide.

You can use only an FC expansion card as the boot device. For precautions about the use of FC, see Hitachi Gigabit Fibre Channel Adapter User’s Guide (BIOS/EFI) in advance.

If you use a shared fibre channel as a boot device, boot may not complete depending on the number of LPARs assigned to the shared fibre channel. To solve this problem, you can set a longer time for the LOGIN DELAY TIME, which is the parameter that controls the operation of the FC-SW module, although it may not work in some cases. For details, see Hitachi Gigabit Fibre Channel Adapter User’s Guide (BIOS/EFI).

OS installation 2-1


2

OS installation

This section describes installation procedures of Windows server 2008 R2.

Restrictions for installation Installing Windows Server 2008 R2 Restrictions

2-2 OS installation


Restrictions for installation

Make sure to note the following points when installing and configureing Windows Server 2008.

• The OS installation partition Install the OS in first partition of boot disk. The application and data of partition are deleted in the disk when installing. You may select an incorrect disk as the OS installation target when installing in the disk that has multiple SATAs or RAID disks. Do not select an incorrect disk as the OS installation target. For more details, see the following Microsoft website.

http://support.microsoft.com/kb/937251/en

• Creating partition When you use Drive Option (advanced) to create a partition, installing the OS in the partition with less than 40 GB may fail. Therefore, we strongly recommend that a partition with greater than 40 GB should be created for OS installation.

• Logical capacity of the install drive Set up the logical drive capacity of installing OS to less than 2 TB. OS does not recognize the capacity of over 2 TB on the logical drive.

• Multiple disks (LU) When multiple disks (LU) are installed in the system unit, multiple disks are displayed as the candidates of the OS installation. The disk number and the displayed order of disks are unstable and always change. We recommend that performing the installation in the single disk environment, and then adding a data disk except a system disk after OS installation. When performing the installation in the multiple disks environment, determine the target disk for installation by its size not by the order or its number. Therefore, configure each disk (LU) with different capacity. If there are some disks with the same size, follow the steps in the Tip of page 2-11 to find out a target disk. If choosing other disk or partition by mistake, the existing partition (existing data) may be deleted. See the following URL for more details about finding out a target disk. http://support.microsoft.com/kb/937251/en

• Installing OS into the external disk array – Set 'one path' to the target disk (LU) before installing the OS. If

the multiple paths are set to the target disk (LU), the installation fails. Use the management utility of the external disk array device for setting 'one path' configuration. See the external disk array documents for the detail. If required, install multiple path software after the OS installation, and then cancel the one-path setting.

– Set the external disk array device to use LUN0 for OS. For details, see the manual of the external disk array device.



OS installation 2-3


• Connecting the external disk array that is not installed OS When external disk array device or mezzanine card is connected, turn off the device power before starting the installation. Otherwise, the target hard disk may not be recognized correctly.

• Server Core Server Core is not supported. Do not select Server Core Installation.

• DVD-ROM ejection Press the eject button of the DVD drive only when changing the DVD-ROM media. Otherwise, you must re-install the OS if press the eject button while accessing CD/DVD-ROM.

• Precaution for using the server blade in the LP mode Confirm the following precaution when using the server blade in the LP mode. The following precaution has priority when the precaution overlaps.

– Using remote console The server blade is performed the power operation through the remote console. For the power operation of server blade in the LP mode, all LPARs that managed by LP mode are influenced. Therefore, turning on/off operation or reset operation are disabled in the remote console. Operate the remote console only when OS installation. If the shell window is not moved automatically while rebooting LPAR, select Continue in the logical UEFI window.

– Product key When entering the product key is requested while OS installation, using the product key for the virtual environment.

Usually, the alphabetical letter of the DVD drive name is after the HDD. If the HDD is the c: drive, the DVD drive comes to the d: drive. In the following steps, the d: indicates the DVD drive name.

2-4 OS installation


• Setting procedures for the memory more than 1 TB When install Windows Server 2008 R2 Enterprise/Datacenter on the server blade that has 1 TB or more of memory using the OS installation media without SP1, decrease in size less than 1 TB memory. Apply SP1 or KB980598 (http://support.microsoft.com/kb/980598) after OS installation, and then return the memory size. When decrease the memory size in CB 540A model, use the memory redundant function. Perform the followings: 1. Click the EFI tab of target server blade in the Web console. 2. Click Edit > Memory. 3. Select Mirroring in Memory Mode, and click Confirm. 4. The confirmation window is displayed, and then click OK. 5. Install OS and SP1 as this guide. 6. Reboot OS. 7. Click the EFI tab of target server blade in the Web console. 8. Click Edit > Memory. 9. Select Independent in Memory Mode, and click Confirm. 10. The confirmation window is displayed, and then click OK. 11. Confirm that 1 TB or more of memory is recognized in OS.

If install OS without decreasing the memory size, the installation may not be completed due to hang up during OS installation.

http://support.microsoft.com/kb/980598

OS installation 2-5


Installing Windows Server 2008 R2

This section describes how to install and configure Windows Server 2008 R2.

For Windows Server 2008 R2

This subsection describes describes how to install Windows Server 2008 R2.

1. Windows is loading files and soon after Install Windows window is displayed, customize the items as necessary, and then click Next.

• The Step 2 may not be displayed in the server install DVD-ROM or something, go to step 3.

• When Windows RE (Recovery Environment) need to start, see Repairing the computer.

2. Click Install now. 3. The Select the operating system you want to install window is

displayed. Click the edition you need to install, and then click Next. 4. Please read the license terms is displayed, read the contents, click

I accept the license terms if you agree to the terms, and then click Next.

The Step 5 may not be displayed in the server install DVD-ROM or something, go to step 6.

2-6 OS installation


5. Which type of installation do you want? is displayed, and then click Custom

(advanced).

6. Where do you want to install Windows? is displayed, and then click Load Driver.

7. The Load Driver window is displayed. 8. Uncheck Mapped in the Virtual Media Session window, and then remove

the Setup DVD-ROM from the DVD drive. 9. Insert the Driver and Utility for Windows DVD-ROM in the DVD drive. Check

Mapped in the Virtual Media Session window.

10. Click Browse. 11. Browse for Folder is displayed. Select an appropriate location described

in the following bullets, and then click OK.

(a) Installing in the internal disk array connected with SAS RAID (on-board) in the server blade or storage expansion blade. d:\GC0x1\Win2008R2\Drivers\RAID\LSI_SAS_01\x64\

(b) Installing in the internal disk array connected with SAS RAID (mezzanine card) in the server blade: CA3RCD2X1, CA3RCD3X1 or CA3RCD4X1 d:\GC0x1\Win2008R2\Drivers\RAID\MegaSAS_01\x64\

(c) Installing in the external disk array connected with the Hitachi Fibre Channel mezzanine card: CC3M8G2X1 or CC3M8G2X2 d:\GC0x1\Win2008R2\Drivers\FibreChannel\HFC_01\x64\

(d) Installing in the external disk array connected with the Emulex Fibre Channel mezzanine card: CC3M8G1X1 d:\GC0x1\Win2008R2\Drivers\FibreChannel\Emulex_01\x64\Drivers\Storport\x64\HBA\

(e) Installing in the external disk array (iSCSI connection) connected with onboard CNA (iSCSI function is enabled) or the CNA mezzanine card (iSCSI function is enabled): CN3MXG2X1 d:\GC0x1\Win2008R2\Drivers\iSCSI\Emulex_01\x64\Drivers\Storport\x64\Win2008R2\

OS installation 2-7


12. Select the driver to be installed. is displayed, select a driver based on the following bullets, and then click Next.

(a) Installing in the internal disk array connected with SAS RAID (on-board) in the server blade or storage expansion blade. d:\GC0x1\Win2008R2\Drivers\RAID\LSI_SAS_01\x64\lsi_sas2.inf

(b) Installing in the internal disk array connected with SAS RAID (mezzanine card) in the server blade: CA3RCD2X1 ,CA3RCD3X1 or CA3RCD4X1 d:\GC0x1\Win2008R2\Drivers\RAID\MegaSAS_01\x64\megasas2.inf

(c) Installing in the external disk array connected with the Hitachi Fibre Channel mezzanine card: CC3M8G2X1 or CC3M8G2X2 d:\GC0x1\Win2008R2\Drivers\FibreChannel\HFC_01\x64\hfcwdd.inf

(d) Installing in the external disk array connected with the Emulex Fibre Channel mezzanine card: CC3M8G1X1 d:\GC0x1\Win2008R2\Drivers\FibreChannel\Emulex_01\x64\Drivers\storport\x64\HBA\elxfc.inf

(e) Installing in the external disk array (iSCSI connection) connected with onboard CNA (iSCSI function is enabled) or the CNA mezzanine card (iSCSI function is enabled): CN3MXG2X1 d:\GC0x1\Win2008R2\Drivers\iSCSI\Emulex_01\x64\Drivers\Storport\x64\Win2008R2\be2iscsi.inf.

13. Where do you want to install Windows? is displayed. 14. Uncheck Mapped in the Virtual Media Session window, and then remove

the Driver and Utility for Windows DVD-ROM from the DVD drive.

15. Insert the Setup DVD-ROM in the DVD drive. Check Mapped in the Virtual Media Session window.

16. Click Refresh in the Where do you want to install Windows?. 17. Follow the instruction on the window to click an appropriate partition from

the window, and then click Next.

2-8 OS installation


18. Installing Windows… is displayed. The all procedures are finished, and

then OS setup will be completed.

19. To boot the OS on the first time after the installation. The user’s password must be changed before logging on the first time. is displayed, and then click OK.

20. Enter any Administrator password into New password and Confirm password, and then click button.

21. Your password has been changed is displayed, and then click OK.

OS Installation is completed.

• If there are some disks with the same size, follow the steps below to find out a target disk. 1. Press Shift + F10 keys. The command prompt will be displayed. 2. Enter the following command in the command line to start the diskpart.

>diskpart 3. Enter the following command in the diskpart.

>select disk=system. Disk n is selected. is displayed.

4. Install the OS in an appropriate partition in the disk n displayed in the previous step.

• The Delete key of the dynamic disk The Delete key cannot be used to partitions in the dynamic disk. See the following URL for more details about partitions in the dynamic disk. http://support.microsoft.com/kb/926190/en

• To specify the size of an installed partition, click Drive Options (advanced). When you select a disk without specifying the partition size and click Next, or you click OK when Another partition may be added for the system file to work all functions of Windows properly. is displayed, another 100 MB partition is created. This partition is called “system partition”. For more details about the system partition, see the following URL. http://technet.microsoft.com/en-us/library/dd799232(WS.10).aspx

A password is required to satisfy the following conditions. • Combine at least 3 characters among the followings:

English capital letters (A to Z); English lower case (a to z); numbers (1 to 9); comma, and period.

• Do not contain 3 or more consecutive letters from the user name or full name.


http://technet.microsoft.com/en-us/library/dd799232(WS.10).aspx

OS installation 2-9


For Windows Server 2008 R2 SP1

The following table shows the supported service pack of each model.

Table 2-2 OS service pack

Model Name Windows Server 2008 R2

No SP SP 1

CB 520H A1 √ √

CB 520H B1 √ √

CB 520H B2 - √

CB 520A A1 √ √

CB 540A A1 √ √

CB 540A B1 √ √

√: Supported

SP: Service pack

• Update module You must apply the update module KB2487426 before installing Windows Server 2008 R2 SP1. An application error occurs in 32-bit applications when you do not apply the update module. The update module KB2487426 (Windows6.1-KB2487426-x64.msu) is stored in a root folder of SP1 DVD-ROM. Download the SP1 installer in the following Microsoft web site, if the SP1 DVD-ROM is not attached to the sever blade. http://support.microsoft.com/kb/2487426/en


2-10 OS installation


Confirm that all applications are supported for the SP1 when installing the SP1.

1. Turn on the system unit, start Windows, and log on as Administrator. 2. Insert the Service pack DVD-ROM into the DVD drive. 3. Check Mapped in the Virtual Media Session window. 4. Click Start > Run. 5. Enter d:\setup.exe, and then click OK.

Welcome to Windows Server 2008 R2 Service Pack1 is displayed.

6. Click Next.

License Agreement Terms is displayed.

7. Read the license agreement, and then click Yes if you agree. 8. Welcome to Windows Server 2008 R2 Service Pack1 is displayed. 9. Remove checkmark from Reboot the computer automatically as needed,

and then click Install. Installation proceeds. Soon after the system unit is rebooted. When you log on, Windows Server R2 Service Pack 1 has been successfully installed is displayed

10. Click Close to close the window. 11. Uncheck Mapped in the Virtual Media Session window. 12. Remove the Service pack DVD-ROM from the DVD drive.

Windows Server 2008 R2 SP1 Installation is completed.

OS installation 2-11


Restrictions

This section describes restrictions for using Windows Server 2008 R2 correctly.

Restrictions for using of Windows Server 2008 R2

This subsection describes restrictions on Windows Server 2008 R2.

Datacenter

The following advanced usability functions are not supported:

• Hot Replace Memory

• Hot Add Processors

• Hot Replace Processors

Shutting down Windows Server

If you shut down Windows while the services registered to start at the boot are still activated, the shut down may not operate normally. Wait more than five minutes after booting Windows before shutting down.

Repairing the computer

Step 2 of the installation procedure may not be displayed in some OS installation media. When this happens, Repair your computer in the step 2 window is not displayed, so that Windows Recovery Environment (Windows RE) cannot be started.

See the following URL for more details about the problem. http://support.microsoft.com/kb/951495/en

Start Windows RE as follows, if necessary.

1. Perform installation until the step 10, according to Installing Windows Server 2008 R2.

2. Press Shift + F10 keys. The command prompt will be displayed. 3. Enter the following in the command prompt to execute recenv.exe.

d:\GC0x1\Win2008R2\Tools\WinRE\WinRE.cmd Driver and Utility for Windows (ver. 01-01 or later): d:\GC0x1\Win2008R2\Tools\WinRE\WinRE_en.cmd

4. Windows RE starts.




Making backup file

Windows Server Backup does not support backing up to the tape media. When backing up data to a tape device, purchase the backup software.

Backing up to the DVD-ROM is not also supported.

Displaying window

After switching the window display for changing tasks, the previous display may remain depending on the timing. In such a case, redraw the point in question to display properly.

Depending on the status of use, the message box may be hidden behind other windows.

To change the display color, terminate the application. Otherwise, it can cause strange display of the application. In such a case, redraw by switching the window for proper display.

When changing the refresh rates, confirm that your monitor can display a window properly.

A window may remain displayed after stopping the movie on some movie applications. When this happens, change the windows such as by maximizing another window.

Functioning power saving

Do not select System Standby, Hybrid Sleep, and Hibernate. These three functions are not supported.

Among power supply options, you can only change the time-out period before the display shutdown.

If you fail to observe two restrictions above, the monitor may not operate properly.

Setting recovery operation after system shutdown

We recommend that the Automatically restart check box should be unchecked.

The procedure is as follows: 1. Click Start > Management Tool > Server Manager, and then open

Server Manager 2. Click Change System Property, and open System Property. 3. Click Details Setting tab > Set in Start and Recovery. Start and

Recovery window is displayed.



4. Remove the check mark in Automatically restart, and click OK.

Getting complete memory dump of physical memory exceeding 2 GB

When Windows is set on a system unit installed with greater than 2 GB memory, Complete Memory Dump cannot be selected from Write Debug Information in Start and Recovery. Perform the following procedure to show Complete Memory Dump in an environment where greater than 2 GB physical memory is installed.

1. Insert the Driver and Utility for Windows DVD-ROM into the DVD drive.

2. Click Run in the Start menu, enter following file name, and then click OK. d:\GC0x1\Win2008\Tools\Dump\PMDE.bat

Driver and Utility for Windows (ver. 01-01 or later): d:\GC0x1\Win2008\Tools\Dump\PMDE_en.bat

3. Press any key when the following message appears. Change the setting to get Complete Memory Dump. Press any key to continue the operation. Press the Ctrl + C keys to cancel the setting.

4. Set virtual memory size. For more details about virtual memory size, see the following Setting virtual memory size.

When starting Startup and Recovery and clicking OK after Step 2, the dump format will be changed to the one selected in Write Debug Information. If you mistakenly clicked OK, repeat Step 2.



Setting virtual memory size

When set virtual memory to get the complete memory dump, set the virtual memory file size to a size greater than the physical memory size. If you try to set the file size of the virtual memory smaller than the physical memory, a warning message If the paging file is disabled or the virtual memory's initial page size: is smaller than xxx MB, system error can occur and useful information to identify the problem cannot be saved. Do you like to continue? is displayed. If you select this xxx MB, the complete memory dump may not be obtained correctly. Set the file size to greater than xxx +400 MB.

When set virtual memory to get the kernel memory dump, set enough size for the virtual memory. Otherwise, the kernel memory dump may not be properly collected. See the following URL for more details about setting the virtual memory size for kernel memory dump.

http://support.microsoft.com/kb/949052/en-us

1. Click Start > Management Tool > Server manager.

2. Click Change System Property, and then open System property.

3. Click Details > Setting in Performance pane.

4. Click Details > Setting in Virtual Memory pane.

5. Remove the check mark in Manage automatically all the drive paging file sizes box.

6. Click Custom Size, and then enter the value greater than <xxx+400>MB to Initial size and Maximum size boxes.

The Maximum size must be greater than Initial size.

7. Reboot the server blade.




Checking System Event viewer logs

The following error logs may be recorded in the System event log.

Table 2-3 Error logs

Event type

Event ID

Event source Description Effects Remarks

Error 10 VDS Dynamic Provider

The provider failed while storing notifications from the driver. The virtual Disk Service should be restarted. Hr=xxxxxxx

See the following URL and restart the Virtual Disk service if necessary.


Error 49 volmgr Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Recommended file size by Windows is different depending on the physical memory. When the c: drive capacity or space cannot satisfy the recommended size, this event is recorded. No problem in the usual OS operation. But complete memory dump cannot be obtained. When large physical memory is required, set the c: drive to a larger size.

It may happen immediately after the OS installation.

Setting c: drive to larger size is recommendable before installing physical memory with large capacity.

Error 4202 Microsoft-Windows-Iphlpsvc

The IP address on Isatap interface isatap.{8E208284-65BF--43D8-92DD-89FFAAF47DF0} could not be updated. Update type: 0; Error code: 0x57. A figure in {} (GUID) may be different depending on the environment.

Ignore this event.

Error 7026 Service Control Manager Event log provider

The following boot-start or system-start driver(s) failed to load: cdrom

Ignore this event if recorded in the environment where a CD-ROM or DVD-ROM drive is connected through USB.

Error 7030 Service Control Manager

The RAID Monitor service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.

Ignore this event.






The following error logs might be recorded in the System event log at the OS boot when an iSCSI disk array device is connected to the system.

Table 2-4 Error logs

Event type

Event ID

Event source Description Effects Remarks

Error 5 iScsiPrt Failed to setup initiator portal. Error status is given in the dump data.

Ignore this event if recorded at the OS boot.

See the following URL for details:


Restriction on changing the network adapter parameter When the network adapter setting has been changed, communication may not be done properly through the changed adapter.

Check the network adapter with the changed setting in the Device Manager. If “!” mark is displayed, right-click the changed adapter, disable it, and the enable it again. When rebooting OS, the adapter can communicate properly.

Updating firmware of external disk array When using an external disk array with Windows Server 2008 R2, updating the firmware or change the settings for Windows Server 2008 R2 may be required.

See the documents of the using disk array for more details about the updates.

Confirming SAN Storage Manager availability A disk array that supports VDS (Virtual Disk Service) is necessary to use SAN storage manager.

See the documents of the using disk array for more details about the support status of VDS.

Displaying file properties Details of File Properties by Explorer may not display the File Version, Product Information, or Product Version. Reboot the OS or change the screen resolution or number of the color bits, and then not-displayed items may be displayed.

Displaying event log of network adapter

\DEVICE \354C76B6-E426-4CEB-8015-BF991BA8D75F\ may be displayed instead of a network adapter name such as Emulex OneConnect OCm11104-F2-HI, NIC/TOE in the event log describing the network adapter. This occurs due to the specification, which is not affected the operation.

The network adapter name and the number enclosed by \\ (GUID) may be different depending on your environment.

Display of Network Adapter Connection Network Connection or task tray status may not be quickly updated at the network adapter linkup. To find the state, select View in Network Connections. Then select Latest Update to update the connection.






Confirming network adapter event log at OS boot

Error event may occur in the network adapter at the system boot. The network adapter may be linked down. Click Network Connections, and then confirm that the targeted network adapter is connected.

A linkup event may be recorded at the system boot in whatever the link status of the network adapter. Click Network Connections, and then confirm the link status of the network adapter.

Confirming physical memory capacity

Microsoft recommends that Windows Server 2008 R2 should have 2 GB memory. If the memory is not enough, processing may not be completed by the time expected or may be interrupted due to resource shortage at the overload.

Disabling Windows RE (Recovery Environment)

With Windows Server 2008 R2, when the system unit restarts due to a failure during the OS startup, a message appears, saying that the computer failed to start and that Windows will attempt to repair it. With no operation, Windows RE (Recovery Environment) starts 30 seconds later instead of Windows Server 2008 R2.

When Windows RE starts up, you need to start Windows Server 2008 R2 manually. If you manage the system with a setting, which automatically restart the system with Windows Server 2008 R2 after a failure is detected during the OS startup, the startup of Windows RE can be troublesome. We recommend you that you should disable the setting because features provided by Windows RE are available by booting up from the installation media. For the procedure to disable it, see Setting Windows Error Recovery.

Disabling multipath of external disk

When a multipath (access route) is assigned to a disk (LU) of an external disk array where to install the OS, change it to a single path before installing the OS. With multiple paths assigned to the disk (LU), the installation fails. Install the OS with a single path, install multipath software, and then release the single path.

When a multipath (access route) is assigned to the disk (LU) of an external disk array where the OS has been installed, change it to a single path routing before restoring the OS from the backup files. With multiple paths assigned to the disk (LU), the restoration may fail. Check notes on the backup software referring to the manual beforehand.

It is usual to change a multipath to a single path from the management utility for each external disk array. See the documents of the external disk array.



Using USB flash drive

With a USB flash drive (FK804G) connected, do not power on the system unit or perform reboot-up. Boot the OS and then connect the USB flash drive. After that, confirm that drive letters of other drives are not changed.

Using BitLocker Drive Encryption

BitLocker Drive Encryption is supported when using Trusted Platform Module (TPM). TPM is disabled by default, therefore you should set TPM enabled before installing. See EFI User’s Guide for the details about the setup.

You should install the following patch program in Windows Server 2008 R2 (non SP1) after setting BitLocker Drive Encryption.


BitLocker Drive Encryption encrypts the drive, therefore the some middleware and some application may not be supported this function. You may follow operating suggestions of the middleware and application as need. Ask your reseller about the more details.

You should set BitLocker Drive Encryption disabled before the hardware maintenance work or extension work.

Keep a recovery password for avoiding lost password. If you lose the recovery password, the OS may not start properly or the data may not be accessed. The hardware maintenance work or extension work may not be executed. When the BitLocker Drive Encryption is enabled, overhead is occurred such as the encryption or the decoding process. When use the BitLocker Drive Encryption in the database, which demanded high performance, or the virtual environment, the BitLocker Drive Encryption may not perform as you expected. Confirm the performance, such as validating, in advance.

Restrictions for using of Windows Server 2008 R2 SP1

This subsection describes restrictions on Windows Server 2008 R2 SP1.

Confirming event viewer The following event may be recorded in the system event log when Windows Server 2008 R2 SP1 is adapting. There, however, is no problem.

Event ID: 10128

Event source: Microsoft-Windows-WinRM

Event Level: Error

Description:





The WinRM service is not listening for HTTP requests because a failure occurred during the binding to the URL (http://+:47001/wsman/) in HTTP.sys.

User action:

Use netsh http to check ACL for URL (http://+:47001/wsman/) is set to Network Service.

Additional information:

The error code received from HTTP.sys is 5: %%5

This event is negligible.

The following event is recorded in the system event log after adapting Windows Server 2008 R2 SP1 during OS boot up.

Event ID: 10

Event source: VDS Basic Provider

Event Level: Error

Description:

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in the namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

See the following Website for further details.


This event is negligible.

The following event may be recorded in the system event log when connecting to a USB device.

Event ID: 1

Event source: VDS Basic Provider

Event Level: Error

Description:

An unexpected error occurred. Error code: 32@01000004

This event is no problem when displaying this event while connecting to a USB device.

http://+:47001/wsman/





Restrictions for using LP mode

When using the server blade in the LP mode, confirm the following restrictions after confirming Restrictions for using of Windows Server 2008 R2 and Restrictions for using of Windows Server 2008 R2 SP1.

Disabled functions

The following functions supported by Windows Server 2008 R2 cannot be used on LPAR manager guest OSs.

• Hyper-V2.0/VMware/Xen

• Hot Add Memory

• Hot Add Processors

• Hot Replace memory

• Hot Replace processors

• Power supply options

Network

• We recommend that you configure a team with dedicated NICs when using ALB.

• For teaming, shared NICs/virtual NICs and dedicated NICs cannot be included in the same team.

• For teaming, different types of drivers cannot be included in a team. Create a team with the same type of drivers.

• When distinguishing between the shared NIC/virtual NIC and the dedicated NIC use the following method which distinguishes them with a part of the network adapter name. – Shared NIC/Virtual NIC: Network adapter name beginning with “Intel®

82576 Gigabit” – Dedicated NIC: Network adapter name beginning with “Broadcom” or

“Emulex”

Remote console

The remote console can access only one session at the same time, therefore the remote console cannot use multiple LPARs at the same time. When accessing multiple LPARs, perform the remote desktop connection.



Maximum MTU size

The following table describes MTU size and support in LPAR manager while using Jumbo Frame in the shared NIC or virtual NIC.

Table 2-1 Maximum MTU size

Guest OS MTU size Support in LPAR manager

Windows Off (1500 byte) √

9014 byte √

16128 byte -

√: supported

-: not supported

Shared NIC and Virtual NIC

The shared NIC and virtual NIC may not be recognized as a network device at the first OS boot after setup. The virtual NIC can be recognized correctly by the OS reboot.

Changing LPAR configuration

• With Windows, when you change from uni-processor configuration to multi-processor configuration and boot the computer, a message to ask to reboot the computer may appear. Then, follow the message to reboot the computer, which allows executing operation in the multi-processor configuration.

• When hardware configuration is changed with Windows Server 2008, re-authentication of Windows license may be required for managing Windows license. In this case, execute the Windows license authentication again. See OS help or documents related to OS for Windows license authentication.

Network adapter

• Link Speed and Diagnostics are not available in the Link Speed tab. You cannot change the link speed: 1 Gbps even if changing it. For Diagnostics, performing Diagnostics causes Error.

• In Power Management tab, use default values for all setting items. Even if you change values of items in Power Management tab, newly set values will not affect behavior of shared NICs and virtual NICs.



3

Driver/utility installation 3-1


Driver/utility installation

This chapter describes the installation procedures of drivers/utilities for Windows Server 2008 R2 using the Driver and Utility for Windows DVD-ROM.

Installing with Compute Systems Installer Installing without Compute Systems Installer Other settings After installation

3-2 Driver/utility installation


Installing with Compute Systems Installer

Compute Systems Installer enables you to easily install drivers and utilities required for the system operation.

Compute Systems Installer, which is included in the Driver and Utility for Windows DVD-ROM, enables you to easily install drivers/utilities required for the system operation.

Install Compute Systems Installer before installing drivers/utilities following to the next steps.

1. Turn on the system unit, start Windows, and then log on as Administrator.

2. Insert the Driver and Utility for Windows DVD-ROM in the DVD drive. Check Mapped in the Virtual Media Session window.

3. Click Start > Run.

4. Type the following and click OK.

d:\HInstall.exe

Compute Systems Installer Installation window is displayed.

• Do not operate Device Manager and not connect to another USB device except when the computer systems installer requires for it during the setup with Compute Systems Installer.

• The Compute Systems Installer can be used only to install English version OS, not any other language version OSs such as Japanese or multi-language. When installing other language version OSs, perform Installing without Compute Systems Installer.



5. Click Yes.

Compute Systems Installer will start automatically after installation.



Installing Drivers/Utilities

Install drivers and utilities with Compute Systems Installer.

When you have installed Compute Systems Installer in the previous steps, Compute Systems Installer starts automatically. If you have installed Compute Systems Installer in the previous steps, jump to the following step 3.

1. Click Start > Run. 2. Enter the following, and then click OK.

c:\Hitachi\S-INST\SysInst2.exe

3. Compute Systems Installer window is displayed, and then click OK.

When you start Compute Systems Installer with Found New Hardware window is displayed, the installer may not proceed. If Found New Hardware window is displayed, click Cancel in the window to exit from the window.



4. A window that prompts to select installation type is displayed. When installing all components, click Default installation.

We recommend the Default installation. When selecting components to install, click Custom installation, click the components following to the directions in the window, and then click Next.

5. Click Next.



Click Yes.

Preparation for installation start, and then click Next. Follow the instructions on the windows to proceed. You may be prompted to change the DVD-ROM during installation. A setup completion window is displayed at the end of the installation. When reboot is prompted, go to step 6; when reboot is not prompted, jump to step 9.

You may be prompted to enter something at setting up utilities. See the document of each utility for the details about installation procedures. See Supplied software for the location of each document.



6. The Setup completed. window is displayed.

7. Uncheck Mapped in the Virtual Media Session window, and then remove the DVD-ROM from the DVD drive.

8. Click Reboot Now, and then click OK.

9. The server blade is rebooted. 10. Log on as Administrator after reboot.

Compute Systems Installer automatically reboots to continue processing. Repeat step 5 to step 10 as necessary.



11. Click Done. Compute Systems Installer finishes.

Removing Compute Systems Installer

When drivers and utilities have been installed, remove Compute Systems Installer. Reboot is required for removing Compute Systems Installer.

1. In the finish window for Compute Systems Installer, check Never launch the program on startup, and then check Uninstall this program.



2. Compute Systems Installer Deletion window is displayed. Click Yes.

3. Click Done.

Compute Systems Installer is removed.

The above installation is completed. Go on to Other settings and After installation.



Installing without Compute Systems Installer

When setting up drivers and utilities without Compute Systems Installer, install the following drivers, utilities, and registry update respectively.

When the LAN mezzanine card is installed in the system and the OS is set up in an external disk array device connected through iSCSI, setup without Compute systems Installer is not available. See Installing with Compute Systems Installer, and then perform the setup using Compute Systems Installer.

Required registry, driver, and utility

Perform the followings when turn on the system unit, start Windows, and log on as Administrator.

• Driver – Display driver – Chipset driver – LAN driver – SAS driver – iSCSI driver (only with no OS installed in an external disk array

device connected through iSCSI, when iSCSI function is available in a onboard CNA)

– Fibre Channel driver updating (Only with OS installed in an external disk array device connected with Fibre channel mezzanine card)

– Mezzanine card driver • Utility

– MegaRAID Storage Manager (only using the internal RAID) – OneCommand Manager – OneCommand NIC Teaming and VLAN Manager – Mezzanine card utility

• Updating registry – NMI Dump – Disk TimeOut

• Setting Windows Error Recovery



Installing drivers

This subsection describes how to install drivers.

Installing Display driver

Install the Display driver using following steps.

Do not install the Display driver when using the server blade in the LP mode.

1. Insert the Driver and Utility for Windows DVD-ROM into the DVD drive. Check

Mapped in the Virtual Media Session window.

2. Click Start > Run. 3. Enter the following, and click OK.

d:\GC0x1\Win2008R2\Drivers\SVGA\Matrox_01\x64\Setup.exe 4. Complete the installation following to the instructions in the window. 5. Uncheck Mapped in the Virtual Media Session window. Remove the DVD-ROM

from the DVD drive. 6. Reboot the server blade. 7. Change the screen resolution to a value that you like within the range of your

display specifications.



Installing Chipset driver

Install the chipset driver using the following steps.

When rebooting OS in the LP mode after deleting the Chipset driver, the USB may not be used. If the USB is not used, perform detach for the USB device at once, and perform attach for the USB device again.

1. Insert the Driver and Utility for Windows DVD-ROM into the DVD drive. Check Mapped in the Virtual Media Session window.

2. Click Start > Run. 3. Input the following words, and then click OK.

d:\GC0x1\Win2008R2\Drivers\Chipset\INTEL_01\infinst_autol.exe 4. The Welcome to the Setup Program window is displayed, and then click

Next.



5. License Agreement is displayed. Read the license agreement, and then click Yes if you agree.

Install the chipset driver following to the instructions in windows. Setup Is complete is displayed in the end of the installation. Click Finish.


7. If the reboot required dialog box is displayed, reboot the OS in accordance with the requirement.



Installing LAN driver

Install LAN driver using the following steps.

In the LP mode, the setting procedure is different for the LAN driver. For the setting procedure in the LP mode, see Installing LAN driver in LP mode.

1. Insert the Driver and Utility for Windows DVD-ROM into the DVD drive. Check

Mapped in the Virtual Media Session window. 2. Click Start > Run.

3. Enter the following, and then click OK. d:\GC0x1\Win2008R2\Drivers\LAN\EmulexXG_01\x64\APInstall.exe

4. Install the LAN driver automatically, and AutoPilot Installer is displayed on the task bar. The installation is completed when AutoPilot Installer is disappeared on the task bar.




Installing LAN driver in LP mode

Install LAN driver in the LP mode using the following steps.


2. Click Start > Administrative Tools > Server Manager.



3. The Server Manager window is displayed. Click Diagnostics > Device Manager > Network adapters.

4. Right-click on the network adapter that is not updated for the LAN driver, and then clicks Update Driver Software.



5. The Update Driver Software window is displayed. Click Browse my computer for driver software.

6. Enter the following in the Search for driver software in this location: box. d:/GC0x1/Win2008R2/Drivers/LAN/INTEL_01/x64 Check out in the Include subfolders box. Click Next.



7. Confirm that Windows has successfully updated your driver software is displayed, and then click Close.

8. Right-click on the network adapter that is updated for the LAN driver, and then clicks Uninstall.

Do not delete the network adapter that is not updated for the LAN driver, otherwise the LAN driver cannot be applied and operated correctly.



9. The Confirm Device Uninstall window is displayed, and then click OK.

Do not check the Delete the driver software for this device, otherwise the LAN driver cannot be applied or operated correctly.

10. Repeat step 4 to step 9 for all network adapters.

11. Update and delete the LAN driver for all network adapters. Click any device from the Device Manager, and then click Scan for hardware changes. All network adapters are detected automatically, the LAN driver is applied.



Scan for hardware changing may spend several minutes. Do not perform other application while updating the display of Device Manager.

A message that a driver cannot be installed normally may be displayed on the task tray while the LAN driver is applied on the network adapter automatically. If this message is displayed, open the property of each network adapter through the Device Manager to confirm that the driver is applied correctly after rebooting the server blade.


13. The OS is rebooted.

• A message that this hardware cannot be start may be displayed while installing the LAN driver. If this message is displayed, reboot the server blade to perform normally. Confirm that the device is operated normally by the device manager.

• An error event log may be occurred on the network adapter when every starting the system unit. The linkdown may be possibly occurred in the network adapter. Confirm that the target network adapter is connected in the Network dialog box. When installing the Intel® PROSet, click Device Manager > Network Adapters. Right-click the target network adapter, and then click Property from the menu. Click the Link speed tab (“Link tab” may be displayed depend on the version of Intel® PROSet) > Link status to confirm the status.

• Updating the network property or the network status of task tray may take time while performing the linkup. Click View > Refresh in the Network dialog box to update the network status.



Installing SAS driver

Install SAS driver using the following steps when using the storage expansion blade.


2. Click Device Manager > Storage controllers in the Computer Management window. Right click on LSI Adapter, SAS2 2008 Falcon under Storage controllers. And then click Update Driver Software….



3. The Update Driver Software window will be displayed. And then click Browse my computer for driver software.

4. Enter the following in the Search for driver software in this location: pane. \GC0x1\Win2008R2\Drivers\RAID\LSI_SAS_01\x64



5. Driver installation will start.

6. The following window will be displayed, and then installation is completed

Click Close.




8. Reboot the OS.

Installing iSCSI driver

Install iSCSI driver using the following steps.



d:\GC0x1\Win2008R2\Drivers\iSCSI\Emulex_01\x64\APInstall.exe 4. Install the iSCSI driver automatically, and AutoPilot Installer is displayed on

the task bar. The installation is completed when AutoPilot Installer is disappeared on the task bar.


Updating Fibre Channel driver

(Only with OS installed in an external disk array device connected with Fibre channel mezzanine card)

Update Fibre Channel driver using the following steps.



d:\GCOx1\Win2008R2\Drivers\FibreChannel\Emulex_01\x64\APInstall.exe 4. Install the Fibre channel driver automatically, and AutoPilot Installer is

displayed on the task bar. The installation is completed when AutoPilot Installer is disappeared on the task bar.


Installing Mezzanine card drivers

There may be some drivers to be installed to use installed expansion cards. See the mezzanine card user’s manual for details, and install components as necessary.



Installing utilities

For details and installation procedures of each utility, see Supplied software.

Installing MegaRAID Storage Manager

MegaRAID Storage Manager is a utility to monitor a server blade/internal disk array of storage expansion blade.

• If this utility is not installed, double fault may occur because the hard disk failure cannot be detected, and also the failure cannot be analyzed correctly.

• Do not install the MegaRAID Storage Manager when using the server blade in the LP mode.

Installing OneCommand Manager

OneCommand Manager is a utility to manage an onboard CNA, a CNA mezzanine card, and a Fibre Channel mezzanine card.

Installing OneCommand NIC Teaming and VLAN Manager The OneCommand NIC Teaming and VLAN Manager is a utility providing LAN advanced functions such as the LAN mirroring or VLAN.

Installing Mezzanine card utility

There may be some utilities to be installed to use installed expansion cards, and install components as necessary.



Updating registry

This subsection describes how to update registries.

Setting NMI Dump

With the Driver and Utility for Windows DVD-ROM in the DVD drive, execute the following steps. Set registry to gather dump when NMI issued.



d:\GC0x1\Win2008\Tools\NMIDump\ NMIDump.bat For Driver and Utility for Windows (ver. 01-01 or later): d:\GC0x1\Win2008\Tools\NMIDump\NMIDump_en.bat

4. Press any key to continue batch processing.

5. Uncheck Mapped in the Virtual Media Session window, and then remove the

DVD-ROM from the DVD drive.

6. Reboot the OS after the steps to enable the setting item.



Setting Disk TimeOut Install Disk TimeOut using the following steps.



d:\GC0x1\Win2008\Tools\TimeOutValue\TimtOutValue.bat For Driver and Utility for Windows (ver. 01-01 or later): d:\GC0x1\Win2008\Tools\TimeOutValue\TimtOutValue_en.bat


5. Uncheck Mapped in the Virtual Media Session window, and then remove the

DVD-ROM from the DVD drive.




Setting Windows Error Recovery

Set Windows Error Recovery using the following steps.



d:\GC0x1\Win2008R2\Tools\WinRE\WinRE.cmd For Driver and Utility for Windows (ver. 01-01 or later): d:\GC0x1\Win2008R2\Tools\WinRE\WinRE_en.cmd




Reboot the OS after the steps to enable the setting item. The above installation is completed. Go on to the Other settings and After installation.



Other settings

Execute the following after installing drivers and utilities.

Checking information for driver updates Some mezzanine cards or devices have DVD-ROM that includes the latest driver, or you can download the latest driver from the website. Apply the latest driver referring to the mezzanine card document.

Applying service packs/patch files Install Windows update patches, such as the security patch, as necessary. Some server blade or mezzanine cards may have prerequisite patches. Ask your reseller about the patch information.

See For Windows Server 2008 R2 SP1 for the detail of service pack, as necessary.

Additional setting when using LP mode

When using the server blade in the LP mode, perform Checking information for driver updates and Applying service packs/patch files above. Then, perform the TCP/IP Checksum Offload function setting of Network Adapter.

Uncheck Internet Protocol Version 6 (TCP/IPv6) in Local Area Connection Properties. If checking Internet Protocol Version 6 (TCP/IPv6), the OS may not boot correctly. Execute the following procedure to uncheck Internet Protocol Version 6 (TCP/IPv6). 1. Click Start > Control Panel > Network and Internet Connections >

Network and Sharing Center. 2. Click Local Area Connection x. (x: appropriate number) 3. Click Properties. 4. Uncheck Internet Protocol Version 6 (TCP/IPv6). 5. Click OK.

The compute systems installer may not recognize the driver installation status correctly when new driver is applied. When updating the driver manually, update after removing Compute Systems Installer.



TCP/IP Checksum Offload function setting of Network Adapter

The onboard CNA and the LAN mezzanine card have a function that performs the checksum calculation through the LAN controller. However, use the checksum calculation as standard feature of the OS without using the LAN controller. When the checksum calculation of the OS is set to use, you can configure more reliable system due to performing consistency confirmation that the received packet data from network in the final stage of OS protocol treatment. Change the network adapter setting as the following procedure when changing the checksum calculation of the OS.

If using 10 Gbps LAN mezzanine card as dedicated NIC, however, set the default value to checksum offload. When calculation is set to the OS, load on CPU may increase, which causes transmission speed lower than expected.

The following table shows settings for shared NIC and virtual NIC. Check the setting values are all Disabled.

Setting item Setting value (essential)

IPv4 checksum offload Disabled

IPSec offload Disabled

TCP checksum offload (IPv4) Disabled

TCP checksum offload (IPv6) Disabled

UDP checksum offload (IPv4) Disabled

UDP checksum offload (IPv6) Disabled

Receive Side Scaling Disabled

Large send offload (LSO) (IPv4) Disabled

Large send offload (LSO) (IPv6) Disabled

Proceed to the offload setting procedure below.




2. The Server Manager window is displayed.

Click Diagnostics > Device Manager > Network Adapters.



3. Right-click on the any network adapter, and then click Properties.

4. Properties window is displayed.

Click the Advanced tab.



5. Set each offload following to the steps shown below. Click TCP/IP Offloading Options > Properties.

•

6. Uncheck IPv4 Checksum Offload, IPSec Offload, TCP Checksum Offload

(IPv4), and TCP Checksum Offload (IPv6).



7. Scroll Offload these tasks to the adapter: and then display and uncheck UDP Checksum Offload (IPv4) and UDP Checksum Offload (IPv6).

8. Click Receive Side Scaling, and select Disabled in Value.



9. Click Large send offload (LSO) (IPv4), and select Disabled in Value.

10. Click Large send offload (LSO) (IPv6), and select Disabled in Value.



11. Click OK.

12. Repeat step 3 to step 11 for each network adapter. 13. When setting of the network adapter is complete, reboot the OS.

The following table shows default values when 10 Gbps LAN mezzanine card is used as dedicated NIC.

Setting item Setting value (essential)

IPv4 Checksum IP Checkusum Offload Rx & Tx Enabled

TCP Checkusum Offload Rx & Tx Enabled

UDP Checkusum Offload Rx & Tx Enabled

Large Send Offload v1 Enabled

Large Send Offload V2 (IPv4) Enabled

Recv Segment Coalescing (IPv4) Disabled

TCP Connection Offload Disabled

IPv6 Checksum TCP Checkusum Offload Rx & Tx Enabled

UDP Checkusum Offload Rx & Tx Enabled

Large Send Offload V2 (IPv6) Enabled

Recv Segment Coalescing (IPv6) Disabled



After installation

This section describes the procedure after installation Windows Server 2008 R2.

• Updating the OS using Windows update. Prepare and apply the update program using Windows Update.

• Setting up each component and utility. Set up each component and utility as necessary.

• Installing other applications. Install other applications as necessary.

• Additional setting when using LP mode. When using the server blade in the LP mode, perform the following settings after performing the above settings, “Updating the OS using Windows Update”, “Setting up each component and utility”, and “Installing other applications”. – Serial console setting

When using virtual COM console, you need to configure serial console. Perform the following command in the command prompt on Windows and reboot the OS.

bcdedit /ems ON bcdedit /emssettings EMSPORT:2 EMSBAUDRATE:115200

*You can use serial console on the guest screen. This allows you to use serial console on the guest screen. You can move only to the OS on an active LPAR from the LPAR manager screen. For the LPAR manager screen operation, see Logical partitioning manager User’s Guide.

– Boot order changing For the setting that start the guest OS boot through the boot order, see Logical partitioning manager User’s Guide.

– Teaming setting We recommend that the proving, which is created by team, of adapter is disabled while the event viewer record a lot of switching events when making teams with AFT, SFT, ALB, or something in the virtual NIC or the shared NIC. Team switching opportunity is only occurring linkdown. For probe of disability procedure, see LAN Advanced Function Manual (for **) *in the Internal Flash Memory. (***: Intel, Broadcom, or Emulex) For the Intel® 82576 function (AFT, SFT, or ALB) and use conditions, see LAN Advanced Function Manual (for ***) in the Internal Flash Memory. (***: Intel, Broadcom, or Emulex)



4

Using supplied software 4-1


Using supplied software

This chapter describes the usages of software products included in this system. Supplied software

4-2 Using supplied software


Supplied software

This section describes software supplied with the system unit.

Installing MegaRAID Storage Manager

MegaRAID Storage Manager is a utility to monitor the internal disk array of server blade/storage expansion blade. When using the internal disk array of server blade/storage expansion blade, you must install this utility.

For the detail of installation and restrictions, see MegaRAID Storage Manager Version xxx Instruction Manual in the Driver and Utility for Windows DVD-ROM.

d:\GCOx1\MANUAL\MSM\MSManager.pdf

If this utility is not installed, double fault may occur because the hard disk failure cannot be detected, and also the failure cannot be analyzed correctly.

The following figure shows the location of RAID controller names. To show Storage expansion blade properties, select Storage expansion blade.

The order of RAID controllers depends on the type of blade. Identify a specific one by the controller name.

Half-wide blade / Full-wide blade*

Storage expansion blade

Using supplied software 4-3


Installing OneCommand Manager

OneCommand Manager is a utility to monitor an onboard CNA, a CNA mezzanine card [CN3MXG2X1], LAN mezzanine card [CN3M1G2X1/CN3M1G3X1] and a Fibre Channel mezzanine card [CC3M8G1X1/CC3M8G2X1/CC3M8G2X2]. For the detail of installation and restrictions, see OneCommand Manager Manual in the Internal Flash Memory.

Installing OneCommand NIC Teaming and VLAN Manager The OneCommand NIC Teaming and VLAN Manager is a utility providing advanced functions such as the fault tolerance or VLAN. For the detail of installation and restrictions, see LAN Advanced Function Manual (for **).

4-4 Using supplied software


5

LAN connection 5-1


LAN connection

This chapter describes the LAN connection. Connecting between LAN device and LAN switch module

5-2 LAN connection


Connecting between LAN device and LAN switch module

When confirming which LAN switch module connects with each port of the LAN device, check the on-board status of LAN device using the Web console. Check the PCI path and function number on the OS, and then determine which LAN switch module connects with.

The LAN devices are as follows: • On-board LAN (CB 520H B1/CB 520H B2/CB 540A B1 model) • Broadcom 1 Gb 4-port LAN mezzanine card • Broadcom 1 Gb 4-port LAN and LSI SAS2008 RAID mezzanine card • Broadcom 1 Gb 8-port LAN mezzanine card • Broadcom 1 Gb 8-port LAN and LSI SAS2008 RAID mezzanine card • Emulex 10 Gb 4-port converged network mezzanine card • Emulex 10 Gb 4-port LAN mezzanine card

LAN connection 5-3


Confirming on-board status

Operate the following procedure to confirm the on-board status of LAN device using the Web console.

1. Select the target server blade from the menu tree on the Resources tab of Web console.

2. Click the Hardware tab. Confirm I/O card and Onboard LAN to check the installed LAN device.

5-4 LAN connection


Confirming connection

Confirm the connection between each port of the LAN device connects and the LAN switch module. You can determine from checking the on-board status (see Confirming on-board status) and checking the PCI path and function number on the OS.

The confirming procedure of the PCI path and function number is as follows:


2. The Server Manager window is displayed. Click Diagnostics > Device Manager > Network Adapters.

LAN connection 5-5


3. Right-click the target network adapter, and then click Property.

4. Confirm the PCI path and function on the General tab.

Confirm which LAN switch module /LAN path through module connected, and see the following examples as below.

The PCI path number is different depending on the system unit configuration. The PCI path numbers of following examples are displayed in alphabetical order. (Small: A -> B -> C -> D -> E: large)

CB 520H model

• Onboard LAN Mezzanine card 2: Emulex 10 Gb 4-port

Item Physical port

No.* PCI path Function Connection

Onboard LAN 0 A 0 Switch module slot #0

1 1 Switch module slot #1

Emulex 10 Gb 4-port 0 B 0 Switch module slot #2

(Mezzanine card 2) 2 C 0

1 B 1 Switch module slot #3

3 C 1

* Physical port number that actually exists in the system unit

• Mezzanine card 1: Broadcom 1 Gb 4-port Mezzanine card 2: Broadcom 1 Gb 8-port

Item Physical port


Broadcom 1 Gb 4-port 0 A 0 Switch module slot #0

(Mezzanine card 1) 2 2


3 3

Broadcom 1 Gb 8-port 0 B 0 Switch module slot #2


4 C 0

6 2


3 3

5 C 1

7 3


5-6 LAN connection


• On-board LAN (Port partitioning) Mezzanine card 2: Broadcom 1 Gb 4-port

Item Physical port


Onboard LAN 0 A 0 Switch module slot #0

(Port partitioning) 2

4

6


3

5

7




3 3


CB 520A model

• Mezzanine card 1: Emulex 10 Gb 4-port Mezzanine card 2: Emulex 10 Gb 4-port

Item Physical port

No. * PCI path Function Connection

Emulex 10 Gb 4-port 2 D 0 Switch module slot #0

(Mezzanine card 1) 0 B 0

3 D 1 Switch module slot #1

1 B 1

Emulex 10 Gb 4-port 0 A 0 Switch module slot #2

(Mezzanine card 2) 2 C 0

1 A 1 Switch module slot #3

3 C 1


LAN connection 5-7



Item Physical port No. *

PCI path Function Connection

Broadcom 1 Gb 4-port 0 C 0 Switch module slot #0



3 3



0 A 0

2 2


7 3

1 A 1

3 3



Item Physical port No. *

PCI path Function Connection



4 C 0

6 2


3 3

5 C 1

7 3




3 3


5-8 LAN connection


CB 540A model

• Onboard LAN 1 Mezzanine card 2: Broadcom 1 Gb 4-port

• Onboard LAN 2 Mezzanine card 4: Broadcom 1 Gb 4-port

Item Physical port


Onboard LAN 1 0 A 0 Switch module slot #0





5 3

Onboard LAN 2 6 C 0 Switch module slot #0


Broadcom 1 Gb 4-port 8 D 0 Switch module slot #2



11 3


• Mezzanine card 1: Emulex 10 Gb 4-port Mezzanine card 3: Emulex 10 Gb 4-port

Item Physical port


Emulex 10 Gb 4-port 0 A 0 Switch module slot #0

(Mezzanine card 1) 2 B 0


3 B 1

Emulex 10 Gb 4-port 4 C 0 Switch module slot #2

(Mezzanine card 3) 6 D 0

5 C 1 Switch module slot #3

7 D 1


LAN connection 5-9



Item Physical port




4 B 0

6 2


3 3

5 B 1

7 3

Broadcom 1 Gb 8-port 8 C 0 Switch module slot #0


12 D 0

14 2


11 3

13 D 1

15 3


5-10 LAN connection


• Onboard LAN (Port partitioning) Onboard LAN (Port partitioning)

Item Physical port


Onboard LAN 1 0 A 0 Switch module slot #0


4

6


3

5

7

Onboard LAN 2 2 B 0 Switch module slot #0


D 4

6


3

D 5

7


6

Using Windows Hypervisor 2.0 6-1


Using Windows Hypervisor 2.0

This chapter describes Windows Hypervisor 2.0 (Hyper-V 2.0). Hyper-V 2.0 overview Configuring system for Hyper-V 2.0

Installing Hyper-V 2.0 Restrictions for using Hyper-V 2.0

6-2 Using Windows Hypervisor 2.0


Hyper-V 2.0 overview Windows Hypervisor 2.0 (Hyper-V 2.0) is a virtualization function provided as a part of Windows Server 2008 R2. Hyper-V 2.0 allows you to run multiple Windows OS on a physical hardware, which can improve efficiency of a physical hardware and reduce IT costs.

Hyper-V2.0 cannot be used when using the server blade in the LP mode.

Hypervisor Hyper-V 2.0 adopts the hypervisor-based virtualization architecture. Hypervisor is a software layer between hardware and OS.

Figure 1-1: Hyper-V 2.0 overview

Terms used in this guide is defined as follows: • Physical hardware:

Physical hardware such as server blade • Virtual machine:

Virtual hardware that operates virtually on a physical hardware • Management OS:

Operating system installed in a physical hardware for managing Hyper-V 2.0 • Guest OS:

Operating systems installed in a virtual machine

Physical Hardware

Windows Hypervisor

Management

OS

Virtual

Machine

Guest OS

Virtual

Machine

Guest OS

Virtual Machine

Guest OS

Server Blade

Management



Accessing further information for Hyper-V 2.0 Access the following URL for further details of Hyper-V 2.0.

http://www.microsoft.com/windowsserver2008/en/us/hyperv-main.aspx

Configuring system for Hyper-V 2.0

This section describes the system configuration to use Hyper-V 2.0.

Requirements for software configuration

Following software requirements should be satisfied to configure Hyper-V 2.0.

Requirements for Software

1. Windows Server 2008 R2 Standard/Enterprise/Datacenter for the management OS.

2. Windows Server 2008 R2 SP1 Standard/Enterprise/Datacenter for the management OS.

Requirement for physical hardware configuration

In addition to the system requirements for Windows Server 2008 R2, the following hardware requirements should be satisfied to use Hyper-V 2.0.

Requirements for Hardware

• Data Execute Prevention (DEP): DEP settings of the server blade are all enabled by default. Use it as is.

• Intel 64 (x64-based processor): All CPUs mounted in the server blade support Intel x64 features. Use it as is.

• Intel Virtualization Technology (Intel VT): Intel VT settings of the server blade are all enabled by default. Use it as is.

• We recommend that the server blade should use the physical hardware that satisfies the requirements shown below or more for configuration. See Guaranteed virtual machine configuration as well.

– Number of CPU core: In addition to the total number of CPUs to be assigned to each guest OS running simultaneously, at least one CPU for the management OS is required.

– Memory capacity: In addition to the total capacity of the memory, which is recommended by Microsoft to each guest OS running simultaneously, at least another 2 GB for the management OS is required.

– Partitions: Separate partitions are required for the management OS and the virtual hard disk file (.vhd) of a virtual machine.

http://www.microsoft.com/windowsserver2008/en/us/hyperv-main.aspx



Guaranteed virtual machine configuration

Hitachi confirmed that the following guest OSs ran properly on the server blade.

Windows 2000 Server with Service Pack 4

Windows 2000 Advanced Server with Service Pack 4

Windows Server 2003, Standard Edition with Service Pack 2 (including R2)

Windows Server 2003, Enterprise Edition with Service Pack 2 (including R2)

Windows Server 2003, x64 Standard Edition with Service Pack 2 (including R2)

Windows Server 2003, x64 Enterprise Edition with Service Pack 2 (including R2)

Windows Server 2008 Standard 32-bit

Windows Server 2008 Enterprise 32-bit

Windows Server 2008 Datacenter 32-bit

Windows Server 2008 Standard 64-bit

Windows Server 2008 Enterprise 64-bit

Windows Server 2008 Datacenter 64-bit

Windows Server 2008 Standard 32-bit with Service Pack 2

Windows Server 2008 Enterprise 32-bit with Service Pack 2

Windows Server 2008 Datacenter 32-bit with Service Pack 2

Recommendations above are just general standards and do not guarantee that the system will work well at any conditions. They may be insufficient depending on an application to run on the guest OS. Give the system test run and check if it works properly beforehand.

Recommendations above are just general standards. When using the system for a specific purpose such as a test environment, it may not necessarily satisfy the recommended requirements. Examine the configuration depending on your purpose.






Windows Server 2008 R2 Standard

Windows Server 2008 R2 Enterprise

Windows Server 2008 R2 Datacenter

Windows Server 2008 R2 Standard with Service Pack 1

Windows Server 2008 R2 Enterprise with Service Pack 1

Windows Server 2008 R2 Datacenter with Service Pack 1

Windows XP Professional x86 Edition +Service Pack 3

Windows Vista Business x86 Edition +Service Pack 2

Windows Vista Enterprise x86 Edition +Service Pack 2

Windows Vista Ultimate x86 Edition +Service Pack 2

Windows 7 Professional x86 Editions

Windows 7 Enterprise x86 Editions

Windows 7 Ultimate x86 Editions

Windows 7 Professional x64 Editions

Windows 7 Enterprise x64 Editions

Windows 7 Ultimate x64 Editions

Windows 7 Professional x86 Edition +Service Pack 1

Windows 7 Enterprise x86 Edition +Service Pack 1

Windows 7 Ultimate x86 Edition +Service Pack 1

Windows 7 Professional x64 Edition +Service Pack 1

Windows 7 Enterprise x64 Edition +Service Pack 1

Windows 7 Ultimate x64 Edition +Service Pack 1



• Guest OSs, not included in the list above but supported by Microsoft, can be installed in the server blade. However, we do not support the installation and operation. We recommend that virtual machine should be configured in the server blade better than Microsoft recommend to a guest OS.

• The virtual hard disk file (.vhd) has three forms such as fixed-size, variable-size, and differentiating vhds. In the variable-size or differentiating vhds, the file size of the virtual hard disk file expands dynamically according to the using capacity of the virtual machine. If the size cannot be expanded due to the capacity shortage of the physical disk, the virtual machine is halted. Confirm that the capacity of the physical disk is sufficient in the production environment. Otherwise, the virtual machine may stop unexpectedly. We recommend that the virtual hard disk should be configured with the fixed-size in the production environment.

• The two types of virtual network adapters, the “network” adapter or “legacy network adapter”, is selectable. Select the “network adapter” for the blade server. When setting up the integrated service in Windows 2000 described in Applying patch programs for Windows 2000 or applications specify the using of a legacy network adapter, use the legacy network adaptor for that purpose.



See the following URLs for the system requirements for each OS recommended by Microsoft. • Windows 7

http://windows.microsoft.com/en-US/windows7/products/system-requirements

• Windows Vista http://windows.microsoft.com/en-us/windows-vista/products/system-requirements

• Windows XP http://support.microsoft.com/kb/314865/en

• Windows Server 2008 R2 http://technet.microsoft.com/en-us/windowsserver/bb414778

• Windows Server 2008 http://www.microsoft.com/windowsserver2008/en/us/WS08-system-requirements.aspx

• Windows Server 2003 (See Windows Server 2003 R2.)] http://www.microsoft.com/Windowsserver2003/sbs/evaluation/sysreqs/default.mspx

• Windows 2000 Server http://support.microsoft.com/kb/304297/en

• Windows 2000 Advanced Server http://support.microsoft.com/kb/304297/en

The maximum number of processors that can be assigned depends on a guest OS. One processor can be assigned to Windows 2000 Server guest OS; Maximum two processors for Windows Server Vista/Windows XP SP3/Windows Server 2003 R2/Windows Server 2003; Maximum four processors for Windows 7/Windows Server 2008 R2/Windows Server 2008, respectively.



http://windows.microsoft.com/en-us/windows-vista/products/system-requirements

http://windows.microsoft.com/en-us/windows-vista/products/system-requirements


http://technet.microsoft.com/en-us/windowsserver/bb414778

http://www.microsoft.com/windowsserver2008/en/us/WS08-system-requirements.aspx

http://www.microsoft.com/windowsserver2008/en/us/WS08-system-requirements.aspx

http://www.microsoft.com/Windowsserver2003/sbs/evaluation/sysreqs/default.mspx

http://www.microsoft.com/Windowsserver2003/sbs/evaluation/sysreqs/default.mspx





Installing Hyper-V 2.0

This section describes how to install Hyper-V 2.0.

Installing management OS

Follow the steps shown below to install Hyper-V 2.0.

1. Boot the server manager on the management OS.

Click Start > Server Manager.

2. Add the Hyper-V role.

Click Roles > Roles Summary > Add Roles to boot the Add Roles Wizard. Click Hyper-V, and then proceed to the completion of the wizard following to the instructions in the Server Roles windows.

3. When prompted, reboot the OS to complete the installation.

• Always log on to the management OS with the administrator privilege. • See Configuring system for Hyper-V 2.0 before the installation. • For the details of how to use the Hyper-V 2.0 manager, see the

management OS help.

The following event is recorded in the system event when you add Hyper-V roles. The event is negligible. • Event ID: 6004

Source: Winlogon Event Level: Warning Description: The Winlogon notification subscriber <TrustedInstaller> failed a critical notification event.



Installing virtual hard disk

Install the virtual hard disk following to the steps shown below.

1. Click Start > Administrative Tools > Hyper-V Manager.

2. Click Action > New > Hard Disk to open the new Virtual Hard Disk wizard.

3. Create a new virtual hard disk following to the wizard.

Installing virtual machine

Install a virtual machine following to the steps shown below.

1. Click Start > Administrative Tools > Hyper-V Manager.

2. Click Action > New > Virtual Machines to open the new Virtual Machine wizard.

3. Create a new virtual machine following to the wizard.

While executing Connect Virtual Hard Disk, Click Use an existing virtual hard disk, and then click the hard disk created in Installing virtual hard disk.

4. When completing the wizard, add hardware if needed. For the details such as the procedure, see the management OS help.

Installing guest OS

Install a guest OS following to the steps shown below in the virtual machine created in Installing virtual hard disk.

We recommend you that the virtual hard disk should be configured with the fixed-size for the production environment. See Guaranteed virtual machine configuration for further details.

• For the recommended virtual machine configuration for the server blade, see Guaranteed virtual machine configuration.

• There are restrictions on OS media to be used as a guest OS. See Restrictions of guest OS.

• To use the virtual DVD drive as DVD drive. For setting the virtual DVD drive, see Setting virtual drive.



1. In the Virtual Machines section of Hyper-V Manager, right-click a virtual machine name to install a guest OS. Click Connect to open Virtual Machine Connection.

2. Insert the OS setup media into the DVD drive that is configured in the virtual machine.

3. Click Action > Start. The virtual machine starts.

4. Boot up from the OS setup media, proceed to install the guest OS following to the instructions in the windows.

5. After completing the guest OS installation, click Action > Insert Integration Services Setup Disk in the Virtual Machine Connection when the guest OS is running.

6. Install the integrated service following to the window instructions. See Help for the details of how to install the integrated service.

If a DVD drive is not included in the virtual machine, configure a DVD drive in the virtual machine. For the procedure, see the management OS help. To configure it, for example, click Media > DVD Drive > D: Capture in Virtual Machine Connection.

• For Windows 2000, see Applying patch programs for Windows 2000 to apply patch program if needed before installing the integrated service.

• For Windows 2000, execute step 5 after setting up Service Pack 4. • For Windows Server 2003 including R2, execute step 5 after setting up Service

Pack 2.



Restrictions for using Hyper-V 2.0

This section describes Restrictions for using Hyper-V 2.0 correctly.

General Restrictions

Planning maintenance

As advancing the integration using the virtual environment, multiple tasks and environments run in a single machine. Make a plan for the schedule management including to ensure the maintenance work. Maintenance tasks include applying security patches, updating application and drivers, and installing service packs for virtual machines and management OS.

Functioning Server Core

Installation of Windows Server 2008 R2 Server Core is not supported.

Using application programs

Some application or middleware may have notice when using with Hyper-V 2.0. See the documents of application distributor from which you have bought it for more details.

Configuring cluster

• When configuring a cluster using Hyper-V 2.0, we strongly recommend you to configure Windows Failover Cluster (WSFC) between the management OSs. See the management OS Help for configuring a cluster between management OSs.

• Cluster configuration between a guest OS and a physical machine is not supported.

• Cluster configuration between guests OS requires a storage device through iSCSI. Windows 2000 Server or Windows Server 2003 as the guest OS does not support cluster configuration.

• Cluster failover is executed when connection failure, such as FC cable disconnection, occurs between the management OS and a shared disk, but the failover may be unsuccessful when the shared quorum disk access fails because of the overload to the disk by guest OSs.

Proceeding live migration

• When a series of live migrations is done in a short period, it may fail. Perform a series of live migration at the intervals of a few minutes.



• When setting a virtual LAN ID (VLAN ID) to a virtual machine for which performing live migration, select the target virtual machine for Service and Applications in Failover Cluster Manager, right-click Virtual machine xxxxx in Overview of xxxxx, and select Settings to open a window for virtual machine setting. Then configure the VLAN ID. xxxxx is a target virtual machine name. If you set VLAN IDs with each Hyper-V Manager, those VLAN IDs settings may disappear after Live Migration, which may cause communication not to be available.

Monitoring events related to physical hardware

Monitor events related to the physical hardware on the management OS, not on the guest OS.

Shutting down and rebooting management OS

We recommend you to shut down all guests OS explicitly before rebooting and shutting down the management OS. Especially when multiple guests OS are running, shutting down the management OS at the same time puts high workload on CPU. This may cause trouble such as too much time to take or improper shutdown.

Using dynamic memory

Dynamic Memory is available when you install Windows Server 2008 R2 SP1 or later as the management OS.

Hitachi confirmed that the following guest OSs ran properly.

Windows Server 2003, Standard Edition with Service Pack 2 (including R2)

Windows Server 2003, Enterprise Edition with Service Pack 2 (including R2)

Windows Server 2003, x64 Standard Edition with Service Pack 2 (including R2)

Windows Server 2003, x64 Enterprise Edition with Service Pack 2 (including R2)




When using VLAN ID in Hyper-v, see LAN Advanced Function Manual (for **).






Windows Server 2008 R2 Standard with Service Pack 1

Windows Server 2008 R2 Enterprise with Service Pack 1

Windows Server 2008 R2 Datacenter with Service Pack 1

Windows Vista Enterprise x86 Edition with Service Pack 2

Windows Vista Ultimate x86 Edition with Service Pack 2

Windows 7 Enterprise x86 Edition with Service Pack 1

Windows 7 Ultimate x86 Edition with Service Pack 1

Windows 7 Enterprise x64 Edition with Service Pack 1

Windows 7 Ultimate x64 Edition with Service Pack 1

When you use following OSs as the guest OS, you must adapt the update module before activating dynamic memory.



For more details about update module, see the following website:


Other restrictions

Search in the following URL Microsoft Help and Support using Hyper-V as a keyword.

http://support.microsoft.com/






Restrictions of management OS

Not installing software products on the management OS

We recommend you not to install task application (middleware), such as a database or application server, on the management OS with Hyper-V enabled.

Enabling role

We recommend you to disabling any role but Hyper-V in Windows Server 2008 R2 on the management OS with Hyper-V enabled.

Restrictions of guest OS

Saving VM status

When click Action > Save in the management window of the virtual machine, the virtual machine status is saved and the virtual machine halts. To restart the virtual machine from the halting point, click Action > Start. However, this operation is different from the guest OS shutdown and reboot. Applications communicating with the outside may detect an error.

Notes for Active Directory on the guest OS

Microsoft Help and Support provides Considerations when hosting Active Directory domain controller in virtual hosting environments in the following URL. Access the following URL and read it in advance.


Configuring Network Load Balancing (NLB) on guest OS

Configuring NLB cluster on the guest OS is not supported. We recommend that tasks that require NLB are done on a physical machine.

Installing 32-bit OS installation media

When using Windows Server 2003 32-bit with Service Pack2 as a guest OS, use the OS media to which Service Pack 1 or 2 has been applied. Otherwise, the guest OS may display the STOP error and halt during installation.

Using snapshot

We do not recommend that you use the snapshot in the production environment. If using the snapshot, performance overhead or inconsistency may occur where multiple servers combined.




We also do not recommend that you use snapshot in the guest OS where Active Directory is configured. If using the snapshot, inconsistency in database may occur.

Using virtual hard disk file (.vhd)

When multiple virtual hard disk files (.vhd) are on a physical hard disk, IO bottleneck may occur depending on processes on the guest OSs. This may affect the entire guest OS processes.

When using multiple guest OSs in the production environment, execute careful test runs in advance. We recommend you to deploy virtual hard disk files (.vhd) on separate physical disks if necessary.

Installing virtual SCSI controller

A guest OS cannot be installed in a virtual hard disk connected to a virtual SCSI controller. With Windows 2000 Server as a guest OS, the virtual SCSI controller connected to a virtual machine is not available. Connect all virtual hard disks to the virtual IDE controller with Windows 2000 Server as a guest OS.



Applying patch programs for Windows 2000

When using Windows 2000 with service pack 4, in which the integrated service has been installed, and applying the following patch programs to the guest OS, stop code 0xCE is displayed and the guest OS may halt.

Apply following programs before setting up the integrated service if necessary.

Since programs KB891861 and KB922582 are prioritized in Windows update programs, perform Windows update before the integrated service. When programs KB891861 and KB922582 have been applied, there is no problem if you perform the integrated service and then Windows updates.

Use the legacy network adapter as a virtual network adapter on a virtual machine before setting up the integrated service. After setting up the integrated service, delete the legacy network adapter from the virtual machine and use a network adapter.

If trouble occurs, the guest OS may have to be re-installed.

KB891861 http://support.microsoft.com/kb/891861/en



Sound playback with a guest OS

When playing back sounds with a guest OS, you cannot play them on Hyper-V manager. If you need to play a sound, connect to the guest OS using an application such as a remote desktop client from a PC with a sound device to play the sound.

When using a remote connecting application which cannot play a sound if some connecting destinations have no physical sound device, you cannot replay a sound even though using remote connection. See your application manual for details.







7

Turning on/off power for server blade 7-1


Turning on/off power for server blade

This chapter describes turning on/off power. Turning on/off

7-2 Turning on/off power for server blade


Turning on/off

This section describes how to turn on and off a server blade.

Turning on power

This subsection describes how to turn on a server blade.

1. Turn on the Power of peripheral units such as a display unit. 2. Press the POWER button on the server blade.

Start Logon window is displayed.

Do not press the keys repeatedly when booting the system. Otherwise, an error message may be displayed.

It may take about 10 minutes to display the Start Logon window.

3. Press Ctrl + Alt + Delete keys. Logon Information is displayed.

In case of operating by the remote console, click Macros > Ctrl-Alt-Del on the tool bar.

4. Enter your user name and password, and then click Enter. Windows boots itself and the Desktop window is displayed.



Turning off power

This subsection describes how to turn off a server blade.

WARNING

• Do not rashly press the Power button on the server blade to turn off the power. It may cause data loss or Windows not to start.

• Perform the shutdown process before turning off the power.

1. Click Start > > Shutdown.

The Shutdown Windows dialog box is displayed.



2. Select a reason for shutdown from Option: in Shutdown Event Tracker.

When you click Other in the Option: box for shutdown, enter the reason in the Comment: box.

3. Click OK. The server blade is powered off.

Turn off the power of peripheral units after turning off the power of the server blade.



Resetting Application/System forcibly

When the system function fails during it is processing applications, resetting the system, which includes terminating applications forcibly or rebooting the server blade forcibly, may effect to regain the system for the normal operation.

Terminating Application forcibly

Right-click the task bar and click Task Manager of the shortcut menu. Click the Application, select an application you want to terminate, and then click End Task.

Turning off the server blade power forcibly

When Windows runs abnormally, press POWER button on the server blade for more then four seconds to turn off the power. You may be required formatting the HDD or SSD to enabling the system.

Do not press the POWER button again until the Windows reboot is completed except emergency. When resetting, boot up and terminate Windows properly, and then reboot it.




MK-91CB500019-07

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]

http://www.hds.com/


