Hitachi Compute Blade 2500, Compute Blade 500, Compute Blade 2000 Installation Manual

Download

Page 1

Hitachi Compute Blade Series

OS Installation Guide for Red Hat Enterprise Linux

Document Organization

Product Version

Getting Help

Contents

MK-99COM141-01

Page 2

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.

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 3

Preface

Intended Audience ................................................................................................. vi

Product Version ..................................................................................................... vi

Release Notes ........................................................................................................ vi

Document Organization .......................................................................................... vi

Referenced Documents .......................................................................................... vi

Document Conventions .......................................................................................... vii

Convention for storage capacity values .................................................................. viii

Getting Help .......................................................................................................... ix

Comments ............................................................................................................. ix

................................................................................................ v

1 Installation Overview ......................................................................... 1-1

Overview ............................................................................................................ 1-2

About target OS and driver ............................................................................ 1-2

Installation general flow ................................................................................. 1-2

Before installation ................................................................................................ 1-3

Preparing installation media ........................................................................... 1-3

Preparing virtual drive for CB 2500/500 .......................................................... 1-3

Preparing virtual drive for CB 2000 ................................................................. 1-5

Backing up necessary files ............................................................................. 1-6

Setting up disk .............................................................................................. 1-6

Setting up EFI for CB 2500/500 ...................................................................... 1-6

Setting up EFI for CB 2000 ............................................................................. 1-6

Other preparations ........................................................................................ 1-6

Other preparations for Logical partitioning enabled .......................................... 1-7

2 Red Hat Enterprise Linux 6 ................................................................. 2-1

Supported Kernel ................................................................................................. 2-2

OS Installation ..................................................................................................... 2-2

Precautions for OS installation on LPAR manager ............................................. 2-2

Before installation ......................................................................................... 2-3

Installation steps ........................................................................................... 2-3

Restrictions ................................................................................................... 2-9

Setting up after installation ................................................................................. 2-15

Setup procedure .......................................................................................... 2-15

iii

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 4

Setting up after installation on LPAR ............................................................. 2-19

3 Utilities

Installing Utilities ................................................................................................. 3-2

............................................................................................. 3-1

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 5

Preface

This document describes how to use the Compute Blade 2500 series, 500 series and 2000 series.

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

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

□

Preface

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 6

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 Red Hat Enterprise Linux 6.6.

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 installation overview for Red Hat Enterprise

Chapter 2, Red Hat Enterprise Linux 6

Chapter 3, Utilities Describes installation procedures of utilities for Red

Referenced Documents

•

Hitachi Compute Blade 500 Series manuals

Hitachi Compute Blade 500 Series EFI User's Guide, MK-91CB500024

Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide, MK-91CB500068

Linux.

Describes installation procedure for Red Hat Enterprise Linux 6.

Hat Enterprise Linux.

Preface

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 7

Hitachi Compute Blade 500 Series Remote Console User's Guide, MK-91CB500018

Hitachi Compute Blade 500 Series Server Blade Setup Guide, MK-91CB500012

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

Bold Indicates text on a window, other than the window

title, including menus, menu options, buttons, fields, and labels. Example: Click OK.

Preface

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

vii

Page 8

Convention Description

Italic Indicates a variable, which is a placeholder for actual

text provided by the user or system. Example: copy

source-file target-file

Note: Angled brackets (< >) are also used to

indicate variables.

screen/code

< > angled brackets Indicates a variable, which is a placeholder for actual

[ ] square brackets Indicates optional values. Example: [ a | b ]

{ } braces Indicates required or expected values. Example: { a

| vertical bar Indicates that you have a choice between two or

Indicates text that is displayed on screen or entered by the user. Example: # pairdisplay -g oradb

text provided by the user or system. Example: #

pairdisplay -g <group>

Note: Italic font is also used to indicate variables.

indicates that you can choose a, b, or nothing.

| b } indicates that you must choose either a or b.

more options or arguments. Examples: [ a | b ] indicates that you can choose a, b, or nothing. { a |

indicates that you must choose either a or b.

b }

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 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

viii

1 kilobyte (KB)

Preface

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

1,000 (103) bytes

Page 9

Physical capacity unit Value

1 megabyte (MB)

1 gigabyte (GB)

1 terabyte (TB)

1 petabyte (PB)

1 exabyte (EB)

1,000 KB or 1,0002

1,000 MB or 1,0003

1,000 GB or 1,0004 bytes

1,000 TB or 1,0005 bytes

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 MB

1 GB

1 TB

1 PB

1 EB

1,024 (210) bytes

1,024 KB or 1,0242

1,024 MB or 1,0243

1,024 GB or 1,0244

1,024 TB or 1,0245 bytes

1,024 PB or 1,0246

bytes

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: 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!

doc.comments@hds.com.

Preface

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 10

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Preface

Page 11

Installation Overview

This chapter describes installation overview for Red Hat Enterprise Linux.

Overview

□

Before installation

□

Installation Overview

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

1-1

Page 12

Overview

This section describes the OS installation flow as follows.

About target OS and driver

The following table shows the version of target OS and driver.

Model Name OS version Driver & Utility CD to use

Table 1-1 OS and driver versions

CB 520X B1

CB 520H B3

CB 520H A1/B1/B2

CB 520A A1

CB 540A A1/B1

CB 2000 RHEL6.6 32bit: X86

Notes:

1. CB 520X B1 and CB 520H B3 can boot only on EFI.

RHEL 6.5/6.6

RHEL6.6 32bit: X86

64bit: X86_64 Driver & Utility CD for Red

Hat Enterprise Linux 6

64bit: X86_64

Note:

In the case of CB 520H A1/B1/B2, CB 520A A1, and CB 540A A1/B1

For how to install RHEL6.5 or earlier, see Hitachi Compute Blade 500 Series OS Installation Guide for Red Hat Enterprise Linux.

In the case of CB 2000

For how to install RHEL6.5 or earlier, see Hitachi Compute Blade 2000 SOFTWARE GUIDE.

To know which specific 6.x versions are supported for servers that are purchased from HDS or its distribution partners, contact your server vendor's sales or support organizations.

Installation general flow

The following flow shows the installation flow.

1-2

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Installation Overview

Page 13

Figure 1-1 Installation general flow

Before installation

This section describes prerequisites for installation.

Preparing installation media

Prepare the installation media for the OS.

Preparing virtual drive for CB 2500/500

Inserting the installation DVD

Insert the Installation DVD into the CD/DVD drive of the system console.

Activating the remote console

Activate the console in the following steps:

Installation Overview

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

1-3

Page 14

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-2 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

Tip:

•

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:

1-4

http: 80

https: 443

3. Log in the Web console of the management module.

4. The following table describes the factory default account settings for the system administrator.

Table 1-3 Factory default account settings for the system

administrator

Item Factory default

User ID administrator

Password password

5. Click Resources tab on the menu screen; then, click a server blade, on which to install the OS.

6. Click the Condition

tab; then, click Server Blade Action then, click

Start remote console. This opens the Logon screen.

Installation Overview

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 15

7. The following remote console screen opens.

Note: When Logical partitioning is enabled on a server blade, power operation with remote console is disabled. Remote console is not available for powering on, forcibly powering off, and reset. With Logical partitioning enabled, use the Web console to powering on or off the server blade and starting LPARs.

Tip: A warning message may appear when the remote console is started. The message varies with the Java VM version. For details, see Hitachi

Compute Blade 500 Series Remote Console User's Guide, or Hitachi Compute Blade 2500 Series Getting Started Guide.

Setting up virtual drive

Set up a virtual drive, with which to read the installation DVD, in the following steps:

1. On the remote console screen, click Tools. Then, click Launch Virtual Media.

2. Confirm that the following virtual media screen opens.

3. Click the box in the Mapped installation.

Tip: While using the virtual drive, do not close the screen by clicking the Exit, by clicking the x

screen closes the virtual media session. This ends up in the disconnection of the drive from the server blade, eventually making it unable to recognize the drive.

button. Closing the virtual media console selection

Preparing virtual drive for CB 2000

Perform "Remote CD/DVD" from the remote console, or connect a USB CDROM drive or USB DVD-ROM drive directly to the server blade.

Tip: See Chapter 3: Connecting the System Equipment and Powering on, in Hitachi Compute Blade 2000 User's Guide for details about the remote console.

column for the CD/DVD to use for

Installation Overview

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

1-5

Page 16

Backing up necessary files

The data in the HDD or SSD is deleted when you re-install the OS. Back up data that you need in advance.

Setting up disk

Configure disks, such as RAID, referring to manuals for internal disk arrays or external disk arrays to install the OS as necessary.

Setting up EFI for CB 2500/500

Set the boot device configuration as the EFI initial setting. See Hitachi Compute Blade 500 Series EFI User's Guide,or Hitachi Compute Blade 2500 Series UEFI Setup Guide that you need.

Setting up EFI for CB 2000

On the EFI starting screen, press the [F2] key or [Delete] key to enter the EFI Setup menu. Click [Save & Exit] tab, find [Boot Override] to select the CD/DVD drive, and press the [Enter] key.

Do not select a device that starts from UEFI.

Other preparations

Start the server blade.

1-6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Installation Overview

Page 17

Note: For LPAR manager environment, see Other preparations for Logical

partitioning enabled on page 1-7

to perform the procedure.

1. Click Power

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

2. Press the <ENTER> key to begin the installation process is displayed.

Note: Do not press any key. The window immediately changes to that in step 3.

3. The countdown window will be displayed, and then press the arrow key within a minute.

The window above is an example of Red Hat Enterprise Linux 6.2.

Jump to OS Installation on page 2-2 for Red Hat Enterprise Linux 6.

Other preparations for Logical partitioning enabled

The following is the operation flow when Logical partitioning is enabled.

Set boot order on Web cosole

You can set boot order using Web cosole, when all of the following firmware version are met:

Model Management module LPAR manager

CB 500 CB 520H

A1/B1

CB 520H B2 The version 01-6x or

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

The firmware version A0125 or later

Installation Overview

The version 01-0x or later

later

1-7

Page 18

Model Management module LPAR manager

CB 520A A1 The version 01-1x or

later

CB 540A A1/B1

CB 520X B1 The firmware version A0235 or

later

CB 520H B3 The version 02-05 or

CB 2500 CB 520X B1 The firmware version A0105 or

later

CB 520H B3 The version 02-05 or

The version 01-2x or later

The version 02-0x or later

later

The version 02-0x or later

later

Set boot order on guest screen

When other than above and CB2000, set boot order using guest screen. The following is operation flow.

• 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 Hitachi Compute Blade 500 Series Server Blade Setup Guide,

1-8

Installation Overview

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 19

or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide or Hitachi Compute Blade 2000 User's Guide.

•

Creating LPARs Create LPARs. For details, see Hitachi Compute Blade 500 Series Server

Blade Setup Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide or Hitachi Compute Blade 2000 User's Guide.

Tip:

For installing and using Red Hat Enterprise Linux 6, the following LPAR configuration is recommended:

Item Recommended value

Processor

Memory

Disk

Network 1 or more NICs

Notes:

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.

2 or more

2.0 GB or larger

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

• Saving configuration information Save the configuration information. For details, see Hitachi Compute

Blade 500 Series Server Blade Setup Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide

or Hitachi Compute

Blade 2000 User's Guide.

• Activating LPARs Activate the LPAR. For details, see Hitachi Compute Blade 500 Series

Server Blade Setup Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide or Hitachi Compute Blade 2000 User's Guide.

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

change the boot order.

[Used on Web console]

For details, see Hitachi Compute Blade 500 Series Web Console User's

Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide.

[Used on guest screen]

For details, see Hitachi Compute Blade 500 Series Logical partitioning

manager User's Guide, or Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide or Hitachi Compute Blade 2000 User's Guide.

Installation Overview

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

1-9

Page 20

Note: 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.

Tip: 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).

1-10

Installation Overview

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 21

Red Hat Enterprise Linux 6

This chapter describes installation procedure for Red Hat Enterprise Linux 6.

Supported Kernel

□

OS Installation

□

Setting up after installation

□

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-1

Page 22

Supported Kernel

The following table shows supported kernel.

Table 2-1 Supported kernel

Red Hat Enterprise Linux 6.5

Red Hat Enterprise Linux 6.6 2.6.32-504.el6

Note:

1. Supported kernels are security update kernels.

Servers that are purchased from HDS or its distribution partners may support a subset of these OS releases. To know which specific 6.x versions are supported, contact your server vendor’s sales or support organizations.

When using RHEL 6 on an LPAR, see 13. Updating kernel in Setting up after

installation on LPAR on page 2-19.

For how to install drivers for Emulex devices, see Hitachi Compute Blade Emulex Adapter User's Guide for Driver.

OS Installation

This section describes how to install Red Hat Enterprise Linux 6 with the Driver & Utility CD.

Supported OS

Supported kernel

32-bit x86 64-bit x86_64

2.6.32-431.20.3.el6

Tip:

The installation procedure described in this guide is an example. See the

• following Red Hat website for more details.

https://access.redhat.com/documentation/en-US/ Red_Hat_Enterprise_Linux/

Driver & Utility CD for RHEL 6, version 0650-xx, contains drivers and

• utilities for RHEL 6.5. It can be used for RHEL 6.5 setup.

Precautions for OS installation on LPAR manager

Be aware of the following precautions for LPAR manager environment.

Activating, resetting the LPAR

To activate or reset the LPAR, perform them through the LPAR manager management screen. Do not use the power button or the reset button for the operation. Also, do not use the dump command from the management module. It is because such operations are performed on the server blade, not on the LPAR; pressing the server blade buttons affect the server blade, and can damage the OS.

2-2

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 23

Using remote console

Power operation by remote console is performed to a server blade. Power operation to a server blade, where Logical partitioning is enabled, affects all LPARs managed by LPAR manager. Thus, the remote console is not available for powering on or off and reset. Use the remote console only for OS installation.

If you cannot go the shell window automatically while rebooting LPAR, select Continue

For CB 520X, install the OS on a virtual drive on the remote console. The USB port on the front panel is not available.

Before installation

For EFI boot, the following message appears before installation. Press any key before the countdown ends. If not, installation may fail.

"Press any key to enter the menu"

in the logical UEFI window.

Tip: Do not install tboot Packages in Base dialog box, and make sure that tboot package is unchecked.

Installation steps

Screenshots for Red Hat Linux Enterprise 6.2 are used in the following steps. A step may include different procedures for Legacy boot and EFI boot systems.

Follow steps shown below to install the OS.

1. Click Install system with basic video driver, and press Tab on the Legacy boot system; press a key on the EFI boot system.

[Legacy boot mode]

package. Click Base System > Base to show the

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-3

Page 24

[EFI boot mode]

2. For CB2500/500 When the boot option appears, add dd blacklist=isci to the end. [Legacy boot mode]

2-4

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 25

[EFI boot mode]

For CB2000 Press the [Tab] key to display options, and type "dd".

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-5

Page 26

Note: Make sure to type the correct command. If you proceed with an incorrect command, the installation may fail.

3. The message, Do you have a driver disk? is displayed, and then click Yes.

2-6

4. The following window is displayed.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 27

5. Uncheck Mapped in the virtual media console dialog box, and then remove the Installation DVD from the DVD drive.

6. Insert the Driver and Utility CD in the DVD drive. Check Mapped in the virtual media console dialog box.

7. Click OK on the window shown in step 4.

8. The following window is displayed.

9. Uncheck Mapped in the virtual media console dialog box, and then remove the Driver and Utility CD from the DVD drive.

10. Insert the Installation DVD in the DVD drive. Check Mapped media console dialog box.

11. Click No on the window in step 8.

Follow the wizard to continue the installation.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

in the virtual

2-7

Page 28

Note: Do not install the "freeipmi-bmc-watchdog" package. If this package is installed to RHEL 6, the system will auto restart periodically. System Management > System Management > Optional packages > freeipmi-bmc-watchdog-x.x.x-x.xx.xx

For CB 520X server blade, CB 520H B3 server blade, do not install tboot package (tboot-x.xx-x.el6.x86_64.rpm/ tboot-x.xx-x.el6.i686.rpm). Click Base System > Base sure that tboot package is unchecked.

Tip: When a message "Please select the nearest city in your time zone" is displayed, select a time zone, uncheck "System clock uses UTC", and click

Next.

Note: For CB 2000, do not configure network settings for a device using the

e1000e driver* which requires to be disabled after the installation. *: Intel Corporation 82567LF-2 The device with the last one of the three consecutive MAC addresses.

Note: For CB 2000, the device on this system does not support [FCoE Storage Client]. Do not check [FCoE Storage Client] on the following window in installation. If you continue to install the OS with [FCoE Storage Client] checked, the installation may not be completed.

to show the Packages in Base dialog box, and make

2-8

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 29

Restrictions

When you installed Red Hat Enterprise Linux 6.5/6.6, there are cases where Call Trace is taken. However, this will not affect system operation.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-9

Page 30

Internal RAID controllers and CB 520X/CB 520H B3 server blade

This section describes restrictions for the following RAID controller and the systems.

•

LSI SAS2008 RAID board (Internal SAS RAID controller)

• Internal SATA RAID controller for CB 520A A1 server blade

• CB 520X server blade

• CB 520H B3 server blade

Restrictions

• PCI path-through function in KVM guest environment PCI path-through function in KVM guest environment (SR-IOV) is not

supported. Do not use this function.

• tboot package Do not install tboot package (tboot-x.xx-x.el6.x86_64.rpm/ tboot-x.xx-

x.el6.i686.rpm). Click Base System > Base to show the Packages in Base dialog box, and make sure that tboot package is unchecked.

When installing tboot package (tboot-x.xx-x.el6.x86_64.rpm/ tboot-x.xxx.el6.i686.rpm) by mistake, change the setting for /boot/grub/grub.conf referring to 4. Customizing /boot/grub/grub.conf,

page 2-15, Setting up after installation on page 2-15.

Setup procedure on

Deleting boot options:

1. Press any key when the following boot loader message appears.

2. Press E key when the following window appears.

2-10

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 31

3. Select the underscored line and press E

4. Boot option setting menu appears. Delete "intel_iommu=on" and "amd_iommu=on" from the boot option,

and press Enter.

5. Enter B key when the following window appears.

key.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-11

Page 32

6. OS starts up. Change the setting for /boot/grub/grub.conf referring to 4. Customizing /

boot/grub/grub.conf, Setup procedure on page 2-15, Setting up after

installation on page 2-15.

•

CB 520H B3 : Disable xHCI of USB configuration on UEFI setup menu for Red Hat Enterprise Linux 6.5/6.6.

1. In the Resources tab of the Web console, from the tree view under

Modules, select the target server blade, and then in the EFI tab, click Edit.

2. Click Device and I/O Ports.

3. In Device and I/O Ports setting dialog box, select Disabled on xHCI of USB Configuration, and click Confirm.

4. In Confirm dialog box, click OK.

5. Wait for EFI settings.

CB 2000 server blade

• Time Required for X Logout With X logout, it may take about 5 to 10 minutes to complete the logout

which has no effect on the system behavior.

• MTU Setting for ixgbe driver on 32-bit x86 kernel When using ixgbe driver on 32-bit x86 kernel, use the default value: 1500

for MTU (maximum transmission unit).If MTU is more than 1500, a kernel panic may occur.

• System Log Messages related to mcelog The following messages may be dumped in the system log (/var/log/

messages). They do not affect the behavior.

2-12

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 33

mcelog: failed to prefill DIMM database from DMI data

mcelog: mcelog read: No such device

ACPI Warning shown in the dmesg file

• The following messagex may be dumped by the dmesg command and in

the system log (/var/log/dmesg). They do not affect the behavior. "ACPI Warning: FADT (revision 5) is longer than ACPI 2.0 version,

truncating length 0x10C to 0xF4 (20090903/tbfadt-288)"

• Intel(R)I/OAT shown in the dmesg file The following message may be dumped by the dmesg command

depending on the system configuration. "Intel(R) I/OAT DMA Engine init failed" To avoid this problem, add the following kernel option to /boot/grub/

grub.conf.

• Using Kdump When using Kdump on Red Hat Enterprise Linux, you may not be able to

use the dump function due to OS limitations if specifying the following devices to store the dump file.

Hitachi 16 Gb 1-port Fibre Channel adapter (GV-CC2N161X1-Y) Hitachi 16 Gb 2-port Fibre Channel adapter (GV-CC2N162X1-Y) Emulex 16 Gb 2-port Fibre Channel adapter (GV-CC2N163X1-Y) If without an I/O slot expansion unit connected, you can avoid this

problem by the following OS setting. Add "blacklist igb" to the last line of /etc/kdump.conf file.

LPAR manager environment

Be aware of the following restrictions for LPAR manager environment.

Basic operation on and changing settings for Red Hat Enterprise Linux 6

After starting Red Hat Enterprise Linux 6 on the LPAR manager LPAR, perform basic operations and change settings for the OS, when needed, by using SSH or terminal software or by using the remote console.

Shared NICs/virtual NICs

If the shared NICs/virtual NICs are not recognized as network devices after starting the OS first time, retry restarting the OS.

Network

You cannot bond virtual NICs and physical NICs with hbonding/bonding.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-13

Page 34

Tag VLAN

If you use Tag VLAN, the communication performance may not improve even if you enable the TCP segmentation off load function.

Pasting character strings on the guest screen

Attempting to paste a long character string onto the guest screen may not paste the intended length of the string, or it may cause Linux hang-up, or it may result in an unexpected screen operation. The maximum length of a string that can be pasted without fail is 16. To paste strings longer than that, use the virtual COM console or a terminal connected to the server blade.

System log messages

The system log below may be found, but it does not affect the operation.

Message

warning: many lost ticks.

mtrr: type mismatch for ef200000,100000 old: write-back new: write-combining

Message at OS boot

The following message may be displayed at OS boot, but operation is not affected.

Message

microcode: CPUX update to revision 0xXX failed.

Message for physical processor shortage

When the total number of logical processors, which are assigned to LPARs, are more than that of physical processors on the server blade, the following message may be displayed. Operation is not affected. When the processor is assigned as dedicated, rarely but the following message may be displayed. This will not affect the operation.

Message

hrtimer: interrupt took XXXXXXX ns

Message at TPM error

When tboot package is installed on Red Hat Enterprise Linux 6, the following message may be displayed at OS boot. Operation is not affected.

2-14

Message

TBOOT: Error: write TPM error: 0xX

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 35

MTU value

When Jumbo Frame is used in the virtual NIC and shared NIC, the following MTU (maximum transfer unit) sizes are supported by LPAR manager.

•

Up to 9000 bytes

CB 520X

Install OS on the internal RAID in CB 520X where a single virtual drive is created. If creating multiple virtual drives, make sure to install the OS on virtual drive 0.

Setting up after installation

This section describes the settings after Red Hat Enterprise Linux 6 is installed.

Note: For LPAR manager environment, see Setting up after installation on

LPAR on page 2-19

Setup procedure

to perform the setup procedure.

Note: When having installed tboot package (tboot-x.xx-x.el6.x86_64.rpm/ tboot-x.xx-x.el6.i686.rpm) with LSI SAS 2008 RAID board (Internal SAS RAID controller) or Internal SATA RAID controller for CB 520A A1 server blade or CB 520X server blade or CB 520H B3 server blade change the setting for /boot/grub/grub.conf referring to Restrictions on page 2-9.

Follow steps shown below to set up the OS after installation.

1. Disabling TCP Checksum Offload function TCP Checksum Offload is a function that checks TCP packets in the LAN

controller. If TCP Checksum Offload is enabled, packet data may be destroyed when the LAN controller fails.

Targeted drivers

tg3 driver

igb driver Values: off or on (off: disabled; on: enabled) Perform the ethtool command to disabling TCP Checksum Offload for both

receive and transmit. Add as same number of ethtool command lines as the number of LAN

controllers to /sbin/ifup-pre-local file as shown below, and reboot the OS. The new settings are automatically configured at the OS boot.

Example: To disabling two LAN controllers Add the following line to /sbin//ifup-pre-local file on condition that the OS

recognizes them as network devices eht0 and eth1.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-15

Page 36

If there is no /sbin/ifup-pre-local file, create a new file with the file privilege 755 and add the setting above. When the file exists, add the command lines above to the file. Then reboot the OS or the network device with the new setting, which the new setting takes an effect.

When you are enabling TCP Checksum Offload, replace each value off with on for tx/rx parameter in the above example.

Note: Do not use NetworkManager service. When NetworkManager service is started, it has been shown that the following problem occurred.

DNS server information registered in /etc/resolv.conf may be deleted.

2. Setting NetworkManager service to off Perform the following commands to set NetworkManager service to off.

a. Perform the following command to stop NetworkManager service.

# service NetworkManager stop

b. Perform the following command to set NetworkManager service to off.

# chkconfig NetworkManager off

c. Perform the following command to check that NetworkManager

service is off.

# chkconfig | grep NetworkManager

The following message is shown. NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off

3. Customizing /etc/sysctl.conf Validate the magic SysRq key to collect information when a problem

occurs. Edit or add the following line.

2-16

Add a setting to induce kernel panic when NMI occurs, with which you can quickly detect a failure in hardware and drivers. Edit or add the following lines.

Add or edit the following line to set the console log level to 3. By changing the level, you can avoid the console overload, which can result in significant deterioration of applications or in Linux hang-up.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 37

4. For CB 2500/500 Customizing /boot/grub/grub.conf (For EFI boot, /boot/efi/EFI/redhat/grub.conf) Edit /boot/grub/grub.conf on a text editor to add an appropriate kernel

option and delete inappropriate one. For Red hat Enterprise Linux 6 (x86, x86_64):

Adding the kernel option above configures the following settings.

Disabling nmi watchdog to use a parameter that stops the system when hardware fails. (nmi_watchdog=0)

A setting for avoiding Aero from working (pci=noaer)

Kernel option parameters to delete (only when tboot package is installed)

Delete the following parameters: intel_iommu=on

amd_iommu=on For CB 2000 Add the following kernel option.

Adding the kernel option above configures the following settings.

Disabling nmi_watchdog to use a parameter that stops the system

when hardware fails

A setting of kernel panic for avoiding the OS malfunction when MCA

interrupts occur

A setting for avoiding Aero from working If selecting tboot package in RHEL installation, delete the following option

to disable the TXT function.

5. Applying 8 Gb Fibre Channel board (GG-CC3M8G1X1-Y) driver

Mount the Driver & Utility CD on a directory and copy

"Hitachi_workaroud/elx/lpfc" folder to a folder. Grant execute

permission for "elpfc_install.sh" in the copied folder. The following

shows an example of mounting "/media/cdrom" folder and copying "/

root" folder.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-17

Page 38

Move to the directory where "elpfc_install.sh" exists, and then execute "elpfc_install.sh" script.

Delete the created folder.

6. Installing LSI Software RAID When using LSI Software RAID, make sure to install LSI Software RAID

following the steps in Installing Utilities on page 3-2.

Note: When using LSI Software RAID, make sure to execute this setting. If you don't, the RAID setting is incomplete and the utility may not work properly.

Menu items for LSI Software RAID setting utility:

LSI S/W RAID setting – 01 (Set the RAID setting)

LSI S/W RAID setting – 02 (Set the blacklist file)

7. Customizing /etc/modprobe.d/blacklist.conf For CB2000, add the following to the last line. This setting blocks loading drivers to prevent unnecessary devices from

being detected.

8. Reflecting the new settings Reboot the OS to reflect the settings configured from step 1 through step

9. Adding/Updating Hitachi drivers Installing RHEL 6 using the Driver & Utility CD will add or update some

drivers. If with the following condition, install the driver to load tools required for

operation. Connected to the Hitachi disk array system with the hfcldd driver: Reinstall the driver contained in the Driver & Utility CD attached to the

HITACHI Gigabit Fibre Channel Adapter.

10. Updating drivers You can confirm the driver version using the following command.

#modinfo driver name

Download and utilize the latest driver.

11. Updating kernel

2-18

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 39

When using Red Hat Enterprise Linux 6.5, download the kernel security update from the Red Hat web page referring to the following table, and then apply the kernel security update.

Table 2-2 Updating kernel

Model name Supported OS

CB 520X

CB 520H B3

Red Hat Enterprise Linux 6.5 2.6.32-431.20.3.el6

Red Hat, Inc

https://rhn.redhat.com/

The setting up after installation is completed. Perform

page 3-2.

Setting up after installation on LPAR

This section describes the further settings and driver update required for running Red Hat Enterprise Linux 6 on the LPAR. If the settings are already made, setting repetition is not required. If the setting values are different from those shown in the following table, the guest OS may not work properly.

Table 2-3 Setting items and values after OS installation

Item (file) Value (required)

/etc/inittab Change it to id:3:initdefault:

Supported kernel

32bit: X86 64bit: X86_64

Installing Utilities on

Offload option settings See Table 2-6 Offload option settings on page

2-23.

/etc/sysctl.conf Add the following:

kernel.printk=3 4 1 7

kernel.sysrq=1

kernel.unknown_nmi_panic=0

kernel.panic_on_unrecovered_nmi=1

Add the following:

kernel.panic_on_io_nmi=1

Kernel line in /boot/grub/grub.conf

(For EFI boot, /boot/efi/EFI/redhat/ grub.conf)

Add the following:

nmi_watchdog=0

vga=792

Delete the following:

quiet

rhgb

Add the following:

nmi_watchdog=0

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-19

Page 40

Item (file) Value (required)

mce=0

pci=noaer

no_timer_check

When using Kdump, change to the following:

crashkernel=[arbitrary value]M@[ arbitrary value ]M

Note:

1. Add this parameter if LPAR manager version is 59-41/79-41 or later for CB 2000.

Add this parameter if LPAR manager version is 01-60 or later for CB 2500/500.

Table 2-4 Setting items and values after OS installation (for Serial console)

Item (file) Value (required)

/boot/grub/grub.conf

(For EFI boot, /boot/efi/EFI/ redhat/grub.conf)

/etc/sysconfig/init Change BOOTUP as follows:

Comment out the following line in splashimage=(hd0,0)/ grub/splash.xpm.gz:

(Before) splashimage=(hd0,0)/grub/splash.xpm.gz

(After) #splashimage=(hd0,0)/grub/splash.xpm.gz

Add the following two lines between hiddenmenu line and the title line:

CB 2000 serial --unit=0 --speed=115200

CB 2500/500 serial --unit=1 --speed=115200

terminal --timeout=10 serial console

Add the following at the end of the kernel line:

CB 2000 console=ttyS0,115200

CB 2500/500 console=ttyS1,115200

(Before) BOOTUP=color

(After) BOOTUP=serial

Table 2-5 NIC device name and type of LAN drivers

NIC scheduling

mode

Device name LAN driver

2-20

Shared NIC and virtual NIC

Dedicated NIC

VF NIC

Intel ® 1 Gbps Ethernet

Broadcom 1 Gbps Ethernet tg3 LAN driver

Intel ® 10 Gbps Ethernet

Emulex 10 Gbps Ethernet be2net LAN driver

igb LAN driver

ixgbe LAN driver

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 41

NIC scheduling

mode

Note:

1. Supported device and LAN driver depend on the NIC installed in a server blade.

Device name LAN driver

To set up files and update drivers, follow these steps:

1. Customizing /etc/inittab Open the /etc/inittab

file, and change the value in the file from "id:

5:initdefault:" to "id:3:initdefault:" and save it.

2. Customizing offload option For the value of offload option settings, see Table 2-6 Offload option

settings on page 2-23.

Customizing /sbin/ifup-pre-local file Setting the following in the file sets the use of offload option for guest

OS boot. If you enable the TCP Checksum Offload function in the LAN controller, it can cause a LAN controller failure, which eventually damage packets.

Be sure to configure offload settings according to the procedure in Case a, b, or c.

a. Using shared NIC and virtual NIC

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-21

Page 42

b. Using Intel ® 1 Gbps Ethernet or Broadcom 1 Gbps Ethernet as

dedicated NIC

c. Using Intel ® 10 Gbps Ethernet as dedicated NIC

2-22

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 43

Confirm that the offload settings configured according to the procedure in Case a, b, or c are the same as the values in the following table.

Table 2-6 Offload option settings

NIC

scheduling

mode

Shared NIC and virtual NIC

Dedicated NIC

VF NIC

Notes:

1. A NIC when the SR-IOV functionality is enabled.

2. The default value is "on", but "off" might be automatically set depending on the environment.

However, even if this value remains "off", no problems exist with operations.

Device name

Intel® 1 Gbps Ethernet

Intel® Ethernet

Broadcom 1 Gbps Ethernet

Intel® 10 Gbps Ethernet

Emulex 10 Gbps Ethernet

1 Gbps

rx tx tso sg ufo gso gro lro

off on on on off on

off off off

on on on on off on off off

on on on on off on on off

Offload value

off on

off

Note: Do not use NetworkManager service. When NetworkManager service is started, it has been shown that the following problem occurred.

DNS server information registered in /etc/resolv.conf may be deleted.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-23

Page 44

3. Setting NetworkManager service to off Perform the following commands to set NetworkManager service to off.

a. Perform the following command to stop NetworkManager service.

# service NetworkManager stop

b. Perform the following command to set NetworkManager service to off.

# chkconfig NetworkManager off

c. Perform the following command to check that NetworkManager

service is off.

# chkconfig | grep NetworkManager

The following message is shown. NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off

4. Customizing etc/sysctl.conf Set the following three:

a. Changing the console log level to 3.

This parameter sets the console log level to 3. By changing the level, you can avoid guest screen overload, which can result in significant deterioration of applications or in Linux hang-up.

Add the following line:

b. Enabling the Magic SysRq key

Edit or add the following.

Set this command to gather information when problem occurs.

c. Setting the NMI interrupt

Edit or add the following.

For early detection of device or driver failure, this command brings the Kernel into a panic state in the event of NMI.

5. Customizing /boot/grub/grub.conf (For EFI boot, /boot/efi/EFI/redhat/grub.conf) Set the following in grub.conf:

Comment out "splashimage=(hd0,0)/grub/splash.xpm.gz". When "splashimage=(hd0,0)/grub/splash.xpm.gz" is commented

out for EFI boot in RHEL 6.5, however, the login prompt will not appear on the remote console. If you use the remote console, move the string before the line "title Red Hat Enterprise Linux (2.6.32-220.el6.x86_64)" without commenting out the string. In

2-24

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 45

this case, perform the grub menu on the remote console because the grub menu is not displayed at the Linux boot.

Example:

For CB 2000, add "serial --unit=0 --speed=115200". For CB 2500/500, add "serial --unit=1 --speed=115200".

Add "terminal --timeout=10 serial console".

Delete "quiet rhgb" from the Kernel line.

For CB2000, add the ending of the Kernel line as follow: nmi_watchdog=0 mce=0 pci=noaer no_timer_check

console=ttyS0,115200 For CB2500/500, add the ending of the Kernel line as follow: nmi_watchdog=0 mce=0 pci=noaer no_timer_check

console=ttyS1,115200

For CB 2000, add "vga=792" as well if LPAR manager version is

• 59-41/79-41 or later.

For CB 2500/500, add "vga=792" as well if LPAR manager version is 01-60 or later.

The following shows an example of grub.conf setting for Red Hat Enterprise Linux 6.5:

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-25

Page 46

Installing tboot package is not recommendable because TPM is not available. If you install tboot package on your environment, set the following in grub.conf.

Comment out "kernel /tboot.gz logging=vga,serial,memory".

Change the first "module" to "kernel" in the line starting with "module /vmlinuz".

Delete "intel_iommu=on amd_iommu=on".

Change the first "module" to "kernel" in the line starting with "module /initramfs".

The following text contains settings above.

Note: Do not use "hashdist=1 mem=mem=1024G" command in the Kernel parameter because using the option can cause the Red Hat Enterprise Linux 6.2 boot fail.

2-26

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 47

6. Changing the crashkernel setting If you use kdump or LTD (Linux Tough Dump), change the crashkernel

setting in the /boot/grub/grub.conf boot, /boot/efi/EFI/redhat/grub.conf)

crashkernel=[Arbitrary value]M@[ Arbitrary value]M (Example: crashkernel=256M@48M) The value differs depending on the memory installed and the number of

ports on the FC expansion card.

7. Customizing /etc/sysconfig/init Change BOOTUP=color to the following:

8. Restarting the system Type in the following and press Enter.

9. Checking the console log level After starting the system, type in the following and press Enter.

Kernel line as follows. (For EFI

10. Checking the NMI interrupt setting After starting the system, type in the following and press Enter.

11. Updating the Hitachi driver Installation using the Driver & Utility CD adds and updates some drivers.

The following case, however, requires installing additional drivers. To connect Hitachi disk array subsystem using the hfcldd driver, reinstall the driver in the Driver & Utility CD attached to the HITACHI Gigabit Fibre Channel Adapter.

12. Updating drivers Installation using the Driver & Utility CD adds and updates some drivers.

13. Updating kernel When using Red Hat Enterprise Linux 6.5, download the kernel security

update from the Red Hat web page referring to the following table, and then apply the kernel security update.

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

2-27

Page 48

Table 2-7 Updating kernel

Supported OS

32bit: X86 64bit: X86_64

Red Hat Enterprise Linux 6.5 2.6.32-431.20.3.el6

Supported kernel

Red Hat, Inc

https://rhn.redhat.com/

14. Using onboard CNA/CNA mezzanine card as iSCSI boot device, or using iSCSI as data device

Kernel panic rarely occurs while shutting down after getting a memory dump by kdump. If a kernel panic occurs, select Hard Reset

from the remote console menu to reboot the server blade. You can get memory dump even if a kernel panic occurs.

For details of Hard Reset, see Hitachi Compute Blade 500 Series Remote

Console User's Guide, or Hitachi Compute Blade 2500 Series Getting Started Guide.

2-28

Red Hat Enterprise Linux 6

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 49

Utilities

This section describes installation procedures of utilities for Red Hat Enterprise Linux.

Installing Utilities

□

Utilities

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

3-1

Page 50

Installing Utilities

Install Utilities referring to Support_EN.html contained in "Driver & Utility CD".

For the detail of installation, see the manual of each utility in the Flash Memory in the server chassis.

Note: Install packages (library) required for each utility before installing the utility by referring to the each manual.

3-2

Utilities

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 51

Hitachi Compute Blade Series OS Installation Guide for Red Hat Enterprise Linux

Page 52

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

info@hds.com

Europe, Middle East, and Africa

+44 (0)1753 618000

info.emea@hds.com

Asia Pacific

+852 3189 7900

hds.marketing.apac@hds.com

MK-99COM141-01