b7fh-5591-01en

1

PRIMERGY BX620 S4 Server Blade User’s Guide

3

Areas Covered

Before Reading This Manual

This section explains the notes for your safety and conventions used in this manual. Make

sure to read this section.

Chapter 1 Overview

This chapter explains component names of this Server Blade as well as an overview of the

software provided with this Server Blade. In addition, the workflow, from placing the server

to starting the operation, is also described.

Chapter 2 Checking before OS Installation

This chapter explains the preparation on the server and cautions necessary before OS

installation. Please read this chapter before starting installation.

Chapter 3 OS Installation using ServerStart

This chapter explains how to install the OS in the server using ServerStart.

Chapter4 Manual OS Installation

This chapter explains how to install the OS on the server without using ServerStart.

Chapter5 Operations after OS Installation

This chapter explains the operations to be performed after OS installation. Be sure to perform

those operations before operating the server.

Chapter 6 High Reliability Tools

For stable PRIMERGY server operations, we recommend that high reliability tools be

installed. This chapter explains the installation and necessary settings of high reliability tools.

Chapter 7 Installing Internal Options

This chapter explains how to install internal options on this Server Blade.

Chapter 8 Hardware Configuration/Utilities

This chapter explains how to make the environment settings necessary to operate the Server

Blade.

Chapter 9 Operation and Maintenance

This chapter explains the maintenance to be performed after server operations start.

Appendix

This appendix explains the specifications for the server and internal options. It also covers

how to recycle the products.

2

Before Reading This Manual

� Trademarks

Microsoft, Windows, and Windows Server are trademarks or registered trademarks of Microsoft Corporation in the United States and other countries. Intel and Xeon are registered trademarks or trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a trademark or registered trademark of Linus Torvalds in the United States and other countries. Red Hat and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries. Other product names used are trademarks or registered trademarks of their respective manufacturers. Other products are copyrights of their respective manufacturers.

Copyright FUJITSU LIMITED 2008

Screen shot(s) reprinted with permission from Microsoft Corporation.

For Your Safety

This manual contains important information, required to operate this product safely.

Thoroughly review the information in this manual before using this product. Especially note the points under "Safety Precautions" provided

with the Chassis or Server Blade, and only operate this product with a complete understanding of the material provided.

This manual and "Safety Precautions" should be kept in an easy-to-access location for quick reference when using this product.

Data Backup

To protect data stored in this product (including basic software such as the operating system and application software), perform backup and

other necessary operations. Note that data protection is not guaranteed when repairs are performed. It is the customer's responsibility to

maintain backup copies in advance.

In case of data loss, Fujitsu assumes no liability for data maintenance or restoration and damages that occur as a result of the data loss for any

reason, except for items covered under warranty.

High Safety

This product is designed, developed and manufactured as contemplated for general use, including without limitation, general office use,

personal use, household use, and ordinary industrial use, but is not designed, developed and manufactured as contemplated for use

accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death, personal injury, severe physical

damage, or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility,

aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system. You

shall not use this Product without securing the sufficient safety required for the High Safety Required Use. If you wish to use this product for

High Safety Required Use, please consult with our sales representatives in charge before such use.

Problems may occur with this product in the event of an instantaneous voltage drop of the power supply due to lightning, etc. To prevent an

instantaneous voltage drop of the power supply, we recommend that you use an uninterruptible power supply system.

3


Content of this manual

This Server Blade cannot be installed on chassis other than PRIMERGY BX600 S2/BX600 S3.

This manual explains about installing the Server Blade on a PRIMERGY BX600 S3 Chassis.

If installing it on a PRIMERGY BX600 S2 chassis, the following restrictions are imposed.

• Read "BX600 S2 Blade Server System Unit Hardware Guide" before use. (Refer to the Document &

Tool CD provided with the chassis.)

• Do not install on the chassis Server Blades slot 4 and slot 10.

If installed on chassis Server Blades slot 4 and slot 10, the device may not operate correctly.

• Four internal LAN ports out of six of this Server Blade cannot be used.

• Do not install the Server Blade slot with 4 Gbit/s FC I/O Module (PG-FCD201) installed on BX600

S2 chassis. This will cause a failure.

When installing a Server Blade with a FC expansion board installed on the BX600 S2 chassis, use the

4 Gbit/s FC I/O Module (PG-FCD102).

• Management Blade firmware may be required to be updated.

For information about the combination of supported firmware, refer to the Fujitsu PRIMERGY

website (http://primergy.fujitsu.com), and download or update an appropriate firmware.

If an appropriate firmware is not applied, this product may not operate properly.

http://primergy.fujitsu.com

4

Remarks

� Warning descriptions

Various symbols are used throughout this manual. These are used to emphasize important points for your

safety and that of others. The following are the symbols and their meanings. Fully understand these

symbols when reading this manual.

The following symbols are used indicate the type of warning or caution being described.

� Symbols

Symbols used in this manual have the following meanings: Expressions Meaning

� Key descriptions / Operations

Keys are described by their representative characters instead of their exact key face appearance, as show

below.

E.g. [Ctrl] key, [Enter] key, [→] key, etc.

The following indicate pressing several keys at once:

E.g. [Ctrl] + [F3] key, [Shift] + [↑] key, etc.

� DVD-ROM drive descriptions

In this manual, a DVD-ROM drive is described as CD/DVD drive.

Failure to observe this warning may cause serious injury or death, and/or destroy the system.

Failure to observe this warning may lead to injury, destruction of the system, or loss of data.

A triangle mark emphasizes the urgency of the WARNING and CAUTION. Details are

described next to the triangle.

A barred circle ( ) warns against certain actions (Do Not). Details are described next to the

circle.

A black circle indicates actions that must be taken. Details are described next to the black

circle.

These sections explain prohibited actions and points to note when using this device. Make

sure to read these sections.

These sections explain information needed to operate the hardware and software properly.

Make sure to read these sections.

→ This mark indicates reference pages or manuals.

5


� Entering commands (Keys)

Command entries are displayed in the following way:

• At each blank in a command line (as pointed out above), press the [Space] key once.

• When using Windows, commands are not case sensitive.

• CD/DVD drive names are shown as [CD/DVD drive]. Enter your drive name according to your

environment.

[CD/DVD drive]: \setup.exe

� Screen shots and figures

Screen shots and figures are used as visual aids throughout this manual. Windows, screens, and file

names may vary depending on the OS, software, or configuration of the server used. Figures in this

manual may not show cables that are actually connected for convenience of explanation.

� Consecutive operations

Consecutive operations are described by connecting them with "–".

� Abbreviations

The following expressions and abbreviations are used throughout this manual.

Example: Procedure of clicking the [Start] button, pointing to [All Programs], and clicking [Accessories]

↓

Click [Start] – [All Programs] – [Accessories].

table: Abbreviations of Product names

Product names Expressions and abbreviations

PRIMERGY BX600 This server or the server (Refers to the entire blade server.)

PRIMERGY BX600 S3 Blade Server System Unit Chassis

PRIMERGY BX620 S4 Server Blade BX620 S4 Server Blade or Server Blade

PRIMERGY BX600 Switch BladeSwitch Blade

Network Blade

Cisco Catalyst Blade Switch 3040

GbE Pass-Thru Blade

FC Switch Blade

FC Pass-Thru Blade

PRIMERGY BX600 Management Blade Management Blade

PRIMERGY SX650 Storage Blade Storage Blade

6

*1: Unless otherwise specified, Windows Server 2003 can also mean Windows Server 2003 x64.

Microsoft® Windows Server® 2008 Standard Windows Server 2008 Standard,

Windows Server 2008 Standard (32-

bit), or Windows Server 2008

Standard (64-bit)

Windows

Server 2008,

Windows

Server 2008

(32-bit), or

Windows

Server 2008

(64-bit)

Windows

Microsoft® Windows Server® 2008

Standard without Hyper-V™

Microsoft® Windows Server® 2008 Enterprise Windows Server 2008 Enterprise,

Windows Server 2008 Enterprise (32-

bit), or Windows Server 2008

Enterprise (64-bit)

Microsoft® Windows Server® 2008

Enterprise without Hyper-V™

Microsoft® Windows Server® 2003,

Standard Edition

Windows Server 2003,

Standard Edition

Windows

Server 2003


Enterprise Edition

Windows Server 2003,

Enterprise Edition

Microsoft® Windows Server® 2003 R2,

Standard EditionWindows Server 2003 R2


Enterprise Edition


Standard x64 EditionWindows Server 2003 x64 *1


Enterprise x64 Edition


Standard x64 EditionWindows Server 2003 R2 x64


Enterprise x64 Edition

Microsoft® Windows® 2000 Server Windows 2000 Server

Microsoft® Windows® Preinstallation Environment Windows PE

Microsoft® Windows Vista® Business Windows Vista

Microsoft® Windows® XP Professional Windows XP Professional

Microsoft® Windows® 2000 Professional Windows 2000 Professional

Microsoft® Windows Server® 2003 Service Pack

Service PackMicrosoft® Windows Server® 2003 x64 Service

Pack

Red Hat Enterprise Linux ES (v.4 for x86)

Linux

Red Hat Enterprise Linux ES (v.4 for EM64T)

Red Hat Enterprise Linux AS (v.4 for x86)

Red Hat Enterprise Linux AS (v.4 for EM64T)

Red Hat Enterprise Linux 5 (for x86)

Red Hat Enterprise Linux 5 (for Intel64)

table: Abbreviations of Product names

Product names Expressions and abbreviations

7


Reference Information

� Server Blade types

Server Blade types are described as follows.

� Software manuals

The software manual contains other reference information and cautions for ServerStart not described in

this manual. Please read it before using ServerStart.

The software manual is contained as a "README.TXT" file in the root folder on the PRIMERGY

Startup Disc. Use a text editor to read it.

� Latest information about software provided with this server

For the latest information regarding ServerStart, ServerView and other software provided with this

server, refer to the Fujitsu PRIMERGY website (http://primergy.fujitsu.com).

Warning and Caution Labels

Warning and caution labels are found on the server.

Do not remove or stain these labels.

table: Server Blade types

Expression and abbreviation Description

Diskless type Servers without an internal hard disk


8

9


1

2

3

4

5

6

7

8

9

Contents

Chapter 1 Overview

1.1 BX600 Blade Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.2 Supplied Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1.2.1 Setup Support Tool - ServerStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

1.2.2 High Reliability Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

1.2.3 Installing High Reliability Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

1.3 Component Names and Functions . . . . . . . . . . . . . . . . . . . . . . . 27

1.3.1 Front View of Server Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

1.3.2 Internal View of Server Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

1.3.3 Baseboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

1.4 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


2.1 Preparation on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

2.1.1 Installing Internal Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

2.1.2 Hardware Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

2.2 Selecting the Installation Method . . . . . . . . . . . . . . . . . . . . . . . . 39

2.2.1 Supported OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

2.2.2 Installation Modes of ServerStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

2.3 Precautions on Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2.3.1 Installation Partition Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

2.3.2 Notes on Configuring RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

2.3.3 Notes on a Multiple LAN Adapter Configuration . . . . . . . . . . . . . . . . . . . .43

2.3.4 Cautions for Using ServerStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

2.3.5 Onboard Controller and Expansion Cards Supported by ServerStart . . .45

2.3.6 Cautions for Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45


3.1 Quick Installation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2 Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.2.1 Starting Up the Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

3.2.2 Disk Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

3.2.3 OS Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

3.2.4 Application Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

3.2.5 Starting OS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Chapter 4 Manual OS Installation

4.1 Creating Driver Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

10

4.1.1 Required Driver Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4.1.2 How to Create Driver Disks [FloppyBuilder Function] . . . . . . . . . . . . . . . . 72

4.2 Starting Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.2.1 Installing Windows Server 2008 (Full) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.2.2 Installing Windows Server 2008 (Server Core) . . . . . . . . . . . . . . . . . . . . . 79

4.2.3 Installing Windows Server 2003 x64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4.2.4 Installing Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4.2.5 Installing Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

4.3 Installing the LAN Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4.3.1 Installing the LAN Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4.4 Installing the Fibre Channel Driver . . . . . . . . . . . . . . . . . . . . . . . 94

4.4.1 For Windows Server 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

4.4.2 For Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.5 Installing SAS RAID Ctrl Driver . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 5 Operations after OS Installation

5.1 Memory Dump/Paging File Setting . . . . . . . . . . . . . . . . . . . . . . 100

5.1.1 How to Obtain Memory Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

5.2 Creating Backup Data for System Recovery . . . . . . . . . . . . . . 107

5.2.1 Windows Server 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

5.2.2 Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

5.3 Storing the System Setting Information . . . . . . . . . . . . . . . . . . 110

5.3.1 How to Store the BIOS Information with Server Management Tools . . . 111

5.3.2 How to Recover the BIOS Information with Server Management Tools . 112

5.4 Creating Maintenance Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

5.4.1 Installing ServerStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

5.4.2 Creating "Server Management Tools" Disk . . . . . . . . . . . . . . . . . . . . . . . 116

5.4.3 Creating a DOS Floppy Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

5.5 Notes Before Operating the Server . . . . . . . . . . . . . . . . . . . . . 117

5.5.1 Auto-run Function from CD/DVD Drives . . . . . . . . . . . . . . . . . . . . . . . . . 117

5.5.2 Drive Letter Assignment in Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . 117

5.5.3 Notes on Advanced Uninterruptible Power Supply (UPS) . . . . . . . . . . . 118

5.5.4 Using Network Startup (PXE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

5.5.5 Changing the system drive size (only for Windows Server 2008) . . . . . 119

5.5.6 Other Notes on Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

5.6 LAN Driver Advanced Setup [BACS] . . . . . . . . . . . . . . . . . . . . 123

5.6.1 BACS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

5.6.2 Teaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

5.6.3 VLAN Setup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

5.7 LAN Driver Advanced Setup [Intel® PROSet] . . . . . . . . . . . . . 151

5.7.1 Intel® PROSet Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

5.7.2 Notes on Referring to the Intel® PROSet Help Topics . . . . . . . . . . . . . . 152

5.7.3 Teaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

11


1

2

3

4

5

6

7

8

9

5.7.4 VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

5.7.5 Local Address Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

5.7.6 Jumbo Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162


6.1 RAID Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

6.1.1 Before starting operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

6.2 Server Monitoring Tool [ServerView] . . . . . . . . . . . . . . . . . . . . 165

6.2.1 Installing ServerView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

6.2.2 Setting Required after Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

6.3 Maintenance Support Tool [HRM/server] . . . . . . . . . . . . . . . . . 168

6.3.1 Installing HRM/server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

6.3.2 How to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

6.4 Solving Problems Early [DSNAP] . . . . . . . . . . . . . . . . . . . . . . . 169

6.4.1 Installing DSNAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

6.4.2 How to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169


7.1 Before Installing Internal Options . . . . . . . . . . . . . . . . . . . . . . . 172

7.2 Removing and Attaching the Top Cover . . . . . . . . . . . . . . . . . . 174

7.2.1 How to Remove the Top Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174

7.3 Installing a CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

7.3.1 Location of CPU Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

7.3.2 Available CPUs and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

7.3.3 How to Install a CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178

7.3.4 Defective CPU Disconnection Function . . . . . . . . . . . . . . . . . . . . . . . . .181

7.4 Installing Memory Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

7.4.1 Location of Memory Module Installation . . . . . . . . . . . . . . . . . . . . . . . . .183

7.4.2 Available Memory Modules and Notes . . . . . . . . . . . . . . . . . . . . . . . . . .183

7.4.3 How to Install/Remove Memory Module . . . . . . . . . . . . . . . . . . . . . . . . .186

7.4.4 Defective Memory Disconnection Function . . . . . . . . . . . . . . . . . . . . . .187

7.5 Installing an Expansion Card . . . . . . . . . . . . . . . . . . . . . . . . . . 188

7.5.1 Location of Expansion Card Installation . . . . . . . . . . . . . . . . . . . . . . . . .188

7.5.2 Available Expansion Card Slot Modules/Expansion Cards and Notes .189

7.5.3 How to Install an Expansion Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

7.6 Installing an Expansion Board . . . . . . . . . . . . . . . . . . . . . . . . . 194

7.6.1 Location of Expansion Board Installation . . . . . . . . . . . . . . . . . . . . . . . .194

7.6.2 Available Expansion Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

7.6.3 How to Install an Expansion Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

7.7 Installing an Internal Hard Disk Unit . . . . . . . . . . . . . . . . . . . . 197

7.7.1 Location of Internal Hard Disk Units Installation . . . . . . . . . . . . . . . . . . .198

7.7.2 Available Internal Hard Disk Units and Notes . . . . . . . . . . . . . . . . . . . . .198

7.7.3 How to Install the Internal Hard Disk Unit . . . . . . . . . . . . . . . . . . . . . . . .199

12

7.8 BIOS Setting with Expansion Card Installed . . . . . . . . . . . . . . 201

7.9 Connection Examples of an External Option Device . . . . . . . 202

7.9.1 Connection of a Backup Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

7.9.2 Connection of Storage Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202


8.1 Switch Block Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

8.1.1 Switch Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

8.2 BIOS Setup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

8.2.1 Starting and Exiting the BIOS Setup Utility . . . . . . . . . . . . . . . . . . . . . . . 205

8.2.2 Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

8.2.3 Advanced Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

8.2.4 Peripheral Configuration Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

8.2.5 PCI Configuration Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

8.2.6 CPU Configuration Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

8.2.7 Security Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

8.2.8 Server Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

8.2.9 ASR&R Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

8.2.10 CPU Status Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

8.2.11 Memory Status Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

8.2.12 Console Redirection Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

8.2.13 System Information Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

8.2.14 Boot Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

8.2.15 Boot Device Priority Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

8.2.16 Exit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226


9.1 Daily Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

9.1.1 Checking the Server Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

9.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

9.2.1 Hardware Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

9.2.2 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

9.2.3 Software Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

9.3 System Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

9.3.1 Server Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

9.3.2 Starting and Exiting Server Management Tools . . . . . . . . . . . . . . . . . . . 244

9.3.3 Viewing/Saving/Deleting the System Event Log . . . . . . . . . . . . . . . . . . 246

9.4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

9.4.1 Hardware Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

9.4.2 Security against Unauthorized Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

9.4.3 Security When Disposing of the Server . . . . . . . . . . . . . . . . . . . . . . . . . 250

9.5 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

9.5.1 Importance of Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

13


1

2

3

4

5

6

7

8

9

9.5.2 Backup Devices, Software and Their Operations . . . . . . . . . . . . . . . . . .251

9.6 Restoring the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

9.6.1 For Windows Server 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

9.6.2 For Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256

9.7 Reinstalling the OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

9.7.1 Checking before OS Reinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

9.8 Maintenance Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

9.8.1 Maintenance Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258

9.8.2 Contacting Maintenance Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259

9.9 Maintenance & Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

9.9.1 Operations after Replacement of a SAS Module or an Expansion Card Slot

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

Appendix

A Server Blade Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

B Specifications for Internal Options . . . . . . . . . . . . . . . . . . . . . 264B.1 CPU Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

B.2 Memory Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265

B.3 Internal Hard Disk Unit Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . .265

B.4 Expansion Card Slot Module Specifications . . . . . . . . . . . . . . . . . . . . . . .266

C External Floppy Disk Drive (USB) Notes on Usage . . . . . . . . 267

D About Switch Blade (PG-SW107) Connection . . . . . . . . . . . . . 268

E Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

14

15

Chapter 1

Overview

This chapter explains the component names of

this Server Blade as well as an overview of the

software provided with this Server Blade.

In addition, the workflow, from placing the Server

Blade to starting the operation, is also described.

1.1 BX600 Blade Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.2 Supplied Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1.3 Component Names and Functions . . . . . . . . . . . . . . . . . . 27

1.4 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

16

Chapter 1 Overview

1.1 BX600 Blade Server

This blade server has the following features.

� High performance / High integration

PRIMERGY BX600 is a blade server that consists of a Chassis and multiple blades.

It is a sophisticated high-performance blade server that enables you to efficiently install a Server Blade,

monitoring device, LAN switching hub, power supply unit, fan, fibre channels, and so on in a 7U

(height: approx. 31 cm) Chassis due to its high-performance and highly-integrated design.

The blade server consists of the following components:

� Chassis (or Case)

The following blades can be installed on the 7U-size Chassis:

• Server Blades (Max.10)

• Storage Blades (Max. 5)

• Network Blade (external connection device) (Max.4)

• Management Blade (Monitoring device) (2 installed as standard)

[Front] Server Blade/Storage Blade

[Rear]

Switch Blade/

GbE Pass-Thru Blade/

FC Pass-Thru Blade, etc.

Power Supply Unit

Power Supply Unit

Management Blade

Switch Blade/GbE Pass-Thru Blade, etc.

17


� BX620 S4 Server Blade

This Server Blade contains a CPU, memory, and a hard disk in the unit (42 × 476 × 286mm).

� Storage Blade

This is a blade type storage subsystem in which up to 5 hard disks can be installed.

Install the Storage Blade in the chassis' Server Blade slot, and connect to the SAS RAID Ctrl that is

installed in the Server Blade to the left side of the Storage Blade using an exclusive cable.

� Network Blade

This is an option that can be connected to LAN port and Fibre Channel devices.

Refer to each Network Blade manual for details about Network Blades that are not described in this

manual.

• Switch Blade

This is a LAN switching hub that supports a Gigabit LAN.

• Fibre Channel Switch Blade

This is a Switch Blade that enables fibre channel connection. The Switch Blade supports a Brocade

Fabric Operating System (Fabric OS) and is compatible with all SilkWorm products.

• GbE Pass-Thru Blade

The GbE Pass-Thru Blade is used to connect the internal LAN ports (including a LAN Expansion

Board) in a Server Blade to the external LAN ports at a ratio of 1:1.

• FC Pass-Thru Blade

FC Pass-Thru Blade is used to connect between the ports of the Fibre Channel Expansion Board

(optional) that is installed in the Server Blade and the external Fibre Channel ports at a ratio of 1:1.

� Management Blade (monitoring device)

This blade is used to monitor the power supply, fan, and temperature in each blade and the Chassis.

It is equipped with a dedicated CPU, LAN, and serial ports. This blade is independent of the Server

Blade, ensuring stable system operation.

The Management Blade also enables you to remotely control and monitor each blade from a

management terminal via a LAN or serial port.

� High reliability

� Redundant function

This server enables a redundant configuration for fan, power supply unit (optional), and Management

Blade.

The Management Blade supports the standard redundant configuration in which one unit manages the

entire system in the master mode and another one is on standby in the slave mode. In this configuration,

if the master Management Blade causes a failure, the slave blade takes over management without

interrupting system operations.

18

Chapter 1 Overview

� Monitoring and remote operations using the Management Blade

The Management Blade enables you to monitor blades and the power supply unit, fan, and temperature

in the Chassis.

You can also turn on the Chassis and Server Blades remotely from the management terminal via the

Management Blade.

� Compact design and scalability

� Space-saving design

The server, display device, keyboard, and external SCSI options fit in a 19-inch rack, which saves the

installation space.

� BX620 S4 Server Blade

� High performance and space saving features

The BX620 S4 Server Blade supports up to two Quad Core Intel® Xeon® processors or Dual Core Intel®

Xeon® processors as well as a SAS (Serial Attached SCSI) interface and fibre channel interface

(optional).

Up to 10 Server Blades can be installed in the PRIMERGY BX600 S3 Blade Server System Unit

depending on system configurations.

� High-speed processing

• Quad Core Intel® Xeon® Processors or Dual Core Intel® Xeon® Processors

The server supports up to two Quad Core Intel® Xeon® processors or Dual Core Intel® Xeon®

processors for high-speed data processing.

A Quad Core processor functions as four physical CPUs, a Dual Core processor functions as two

physical CPUs.

A Quad Core Processor does the same work as four physical CPUs and a Dual Core Processor does

the same work as two physical CPUs.

• PCI-Express (x8) Expansion board slot is used.

• A PCI-Express/PCI-X Expansion card slot is used.

When the Expansion card slot module (PG-CS104) is installed, PCI-Express (x4) buses can be used.

When the Expansion card slot module (PG-CS103) is installed, PCI-X buses with a maximum data

transfer speed of 1.06Gbps can be used.

• SAS

When using a SAS interface in the onboard controller, the maximum data transmission rate is 3Gbps.

• Server blade and LAN Network Blade are connected through the six LAN ports that has a high-speed

data transfer capability (1Gbps).

19


� High scalability

This Server Blade has high-density functions, ensuring the configuration of a large-capacity and

extensible system.

• Up to 32 GB of memory can be installed for each Server Blade.

• Up to two 2.5-inch internal hard disk units can be installed in each Server Blade.

When using a Storage Blade, up to five more hard disks can be connected to the Server Blade.

• Each Server Blade can be connected to the backup device via an external SCSI (can be connected via

the SCSI card when the expansion card slot module (PG-CS103) is installed).

• Using the Fibre Channel Expansion Board (optional), a fibre channel system (SAN) can be

configured.

• When the expansion card slot module (PG-CS103 or PG-CS104) is installed, network extension from

an expansion card and connection to the backup device are enabled.

� High reliability

• You can specify a password so that only a specific person can use the Server Blade.

• The server supports the Single Device Data Connection (SDDC) function using PC2-5300-compliant

memory (DDR2 667 SDRAM) and the memory mirror function (depending on the memory

configuration) to enable data recovery in the event of a memory error.

• A storage system (RAID1) can be configured using an onboard SAS array controller.

When installing SAS RAID Ctrl (MegaRAID SAS), a storage system (RAID0/RAID1/RAID1+0/

RAID5/RAID6) can be configured in a Storage Blade that is an external option.

• The ServerView's Automatic Server Reconfiguration & Restart (ASR& R: automatic restart) function

enables you to quickly recover a server error.

• The ServerView action function enables you to view system event log (SEL) during OS operation.

• High reliability tools offer stable system operation. For information about high reliability tools, refer

to "1.2.2 High Reliability Tools" (�pg.23).

20

Chapter 1 Overview

1.2 Supplied Software

The following software is supplied together with the server. ServerStart supports

setting up the system and high reliability tools prevent troubles while server system is

running.

1.2.1 Setup Support Tool - ServerStart

ServerStart is an initial setup support tool for PRIMERGY. It offers simple procedures for setup and

proper installation for recommended drivers.

� Setting up with ServerStart

When performing the OS installation with ServerStart, drivers which are corresponding to the

automatically recognized expansion cards will be installed by ServerStart. In addition, high reliability

tools and array controller management tools are automatically installed. It prevents the related errors.

It is recommended to perform the OS installation with using ServerStart.

ServerStart

Auto setup

Using ServerStart

Automatic RAID configuration

Automatic installation of recommended drivers

Automatic installation of high reliability tools

are available.

Example:

Automated operations such as OS installation.

Complicated hardware settings such as RAID configuration

User definition, access policies and network settings

Manual settings for each item

resulting in leading mistakes and taking time for server installation.

Install

Not using ServerStart

Example:

IP address settings, creation of user,

registration of computer name, and etc.

&Setup

21


� Some operations such as a license window and media replacements are required to be performed

manually.

� High reliability tools are software with comprehensive strength for stable system operation of the

server management.

� Merit with ServerStart setup

� Network configuration

ServerStart can configure a network on server installation. For details on available network patterns,

refer to "Using ServerStart to Configure the Network".

� Automatic driver installation

This function installs the recommended drivers for such as automatically recognized expansion cards on

the server installation. It is preventative for mismatch driver installations, such as previous version or

incompatible drivers.

� Automatic RAID configuration

Without RAID utility, disk array can be configured by specifying a RAID type and number of hard disk

unit.

22

Chapter 1 Overview

� Intuitive user interface

The intuitive user interface allows you to easily set the necessary information.

� Main window

When ServerStart starts up, the following window appears. The window and tool bar differ, depending

on the mode.

� Tool bar

For the expert mode

� While the wizard is running, do not click the icon to move to the previous or next window or

to upper tree level. To move to a different window, click the [Previous], [Up], or [Next] button at the

bottom of the wizard window.

Goes to the

next page.

Returns to

the main screen.

Ends ServerStart.

Changes the size

of icons.Returns to the

previous page.

Resets the status

function.

Goes to one tier

upper.

23


� Wizard window

Clicking a wizard displays a wizard window.

Set each item in the wizard window. To move to a step in the next wizard window, click the operation

button at the bottom of the window. Clicking [help] displays an explanation for setting the item.

1.2.2 High Reliability Tools

High reliability tools provide comprehensive supports for stable system operations of the server. The

following tools have individual management function through normal operations to restoration from

errors:

• Server monitoring tools

• System diagnosis support tool

• LAN driver advanced setup tools

� Server monitoring tools

The server monitoring tools monitor the hardware status and notify the event of an error when irregular

status occurs.

� Early detection of a server failure [ServerView]

ServerView monitors the server status to protect important server resources. The server hardware keeps

under observation all the time and a potential irregular status will be notified in timely manner when it is

detected. A corrective action can be taken in early stage and eliminate the system error before growing a

serious matter.

24

Chapter 1 Overview

� For notes of security for ServerView, refer to "● Security" in Section "1.1.7 Note", ServerView User’s

Guide.

� Maintenance support tool [HRM/server]

HRM/server performs the server maintenance operation promptly and surely to retain stable system

operation.

� Early detection of a disk problem [RAID Management Tool]

RAID Management Tool monitors a configured disk array performance. When an event occurs, it leaves

an event log in the event viewer's application logs. At the same time, a pop-up window indicates a hard

disk failure, rebuild status, etc.

� System diagnosis support tools

The system diagnosis support tools boost device management in order to perform stable server

operation.

� Early solution to problems [DSNAP]

DSNAP is a command line utility for collectively acquiring failure analysis information. Command line

operation makes easy to set the configuration information of the system file and major registries, and

collect the event log. When a problem occurs in your Windows Server 2003 system, DSNAP is used for

a support engineer to understand your system software configuration and settings correctly and to

promote research smoothly. Provide this with memory dump to your support engineer.

� LAN driver advanced setup tools

These tools set details on the LAN, including the use of teaming (load balance) function and VLAN

configuration.

� Broadcom Advanced Control Suite (BACS)

BACS is a tool for setting details on the onboard LAN.

� Intel® PROSet

Intel® PROSet is a tool for setting details on the LAN card in case such as using teaming function

between LAN cards or onboard LAN and LAN card, and configuring a VLAN with LAN card.

25


1.2.3 Installing High Reliability Tools

Collective installation of all high reliability tools, provided with PRIMERGY, may be made by

specifying them in "Application Wizard".

The following high reliability tools are installed with ServerStart.

I: Installed automatically

N: Installed if selected (Not selected by default)

S: Installed if selected (Selected by default)

M: Install manually

*1: For Windows Server 2003, ServerView Agent is not displayed in the menu.

*2: Not supported in Windows Server 2008 Server Core installation.

� Linux do not support batch installation with ServerStart.

� ServerView is required configuration after installation even when the high reliability tools have been

installed at once with ServerStart. Refer to "Chapter 6 High Reliability Tools" (�pg.163).

� When using ServerStart to install the OS, RAID Management Tool and ServerView Console are

installed together. These cannot be selected individually.

� To use all functions of ServerView, "Java2 Runtime Environment Standard Edition" and "Web server"

are required. When using ServerStart to install the OS, "Java2 Runtime Environment Standard Edition"

is installed automatically. For Web server, you can use either of the following by selecting a menu.

• ServerView Console (for Apache)

Install ServerView Web-Server (Web server for ServerView, Apache for Win32 base) and install

ServerView configuring to use this Web server.

• ServerView Console (for IIS)

Install Microsoft Internet Information Server (IIS) supplied with Windows separately. ServerView is

installed with the setting to operate using IIS installed on the system.

table: High reliability tools installation

High reliability tool

ServerStart installation

Quick

Installation

mode

Expert mode

RAID Management Tool / ServerView Console (for Apache) I S

RAID Management Tool / ServerView Console (for IIS) M N

ServerView Agent *1 I I

HRM/server I N

DSNAP I S

Broadcom Advanced Control Suite (BACS) *2 I I

Intel® PROSet *2 I I

26

Chapter 1 Overview

� When IIS is not found in the system, ServerView Web-Server is installed even if "ServerView Console

(for IIS)" is selected.

ServerView Console (for Apache) is selected by default. To install ServerView Console (for IIS), select

"RAID Management Tool / ServerView Console (for IIS)".

If "RAID Management Tool / ServerView Console (for IIS)" is selected, ServerView Console (for

Apache) is not installed.

ServerView Console (for IIS) cannot be installed in Quick installation mode.

For Windows Server 2008, ServerView Console (for IIS) cannot be installed.

� For Windows Server 2003, it is not possible to release both the ServerView Console (for IIS) and the

ServerView Console (for Apache). However, it is possible for Windows Server 2008.

In Windows Server 2008 Server Core installation environment, ServerView Console (for Apache) is not

supported.

� Intel® PROSet will be installed only when an optional LAN card is installed properly and the driver is

applied correctly.

� If the OS is installed on other than drive C using ServerStart, Intel® PROSet will not be installed. In this

case, install Intel® PROSet manually. For details, refer to "5.7.1 Intel® PROSet Installation" (�pg.151).

27


1.3 Component Names and Functions

This section explains the component names and functions of the Server Blade.

1.3.1 Front View of Server Blade

a Release latch

This latch is used when installing/removing a Server Blade.

b 2.5-inch storage bay

Install the hard disk unit. Up to two hard disk units can be installed in this Server Blade.

c Hard disk status LED

Indicates the state of the internal hard disk unit installed where the LED is located. The meanings

of each LED is as follows.

• Hard disk access LED (Left)

This LED lights green when data is being written to or read from the hard disk.

b

a

c

d

f

h

j

i

k

e

g

28

Chapter 1 Overview

• Hard disk status LED (Right)

This LED lights or blinks depending on the hard disk status described below.

d Server blade power LED ( )

It is lit or blinks depending on the Server Blade power status as follows.

e Server blade power switch

Press this switch to turn the Server Blade on.

For the procedure to turn the Server Blade on/off, refer to the "BX600 S3 Blade Server System

Unit Hardware Guide".

� When the hard disk access display LED lights, do not turn off the power. Data in the hard disk

may be damaged.

f KVM select LED ( )

It is lit or blinks depending on the KVM status as follows.

table: Hard disk status LED

LED status Description

Off Normal mode

Lights amber Error detected in the hard disk

Flashes amber Displaying the running hard disk using SAS BIOS Utility

Flickers amber Rebuilding

table: Server blade power LED


Off The power is not supplied to the Server Blades.

(The Chassis power is not turned on.)

Lights green The power is turned on.

Lights amber The power is turned off. (Standby)

Blinks green Blinks when an error is detected in the Server Blade or the Server Blade

identification function is used while the power is turned on.

If an error occurs, contact an office listed in the "Contact Information" of

"Start Guide" or device administrator.

Blinks amber Blinks when an error is detected in the Server Blade or the Server Blade

identification function is used while the power is turned off.

If an error occurs, contact an office listed in the "Contact Information" of

"Start Guide" or device administrator.

Blinks green-amber Standby mode. (ACPI function)

The Server Blade does not support this mode.

table: KVM select LED


Off KVM is not selected.

Lights green KVM is selected.

Blinks amber Blinks when a BMC *1 error was detected without KVM selected, or when

the maximum installable number for the Server Blades was exceeded.

In this case, contact an office listed in the "Contact Information" of "Start

Guide" or device administrator.

29


*1:BMC (Baseboard Management Controller): micro controller which manages temperature, voltage sensor, etc. on the baseboard

g KVM select switch

Pressing this switch enables operation of the display, keyboard, and mouse, which are connected

to the KVM module, in the Server Blade.

When this switch is pressed twice for 5 seconds or longer, the maintenance switch function (NMI

function) can be used.

� When the following operations are performed, the same function as the maintenance switch

can be used.

1. Press the KVM select switch for 5 seconds or longer.

The KVM select LED is lit.

2. Press the KVM select switch again within 3 seconds, and wait for 5 seconds or longer.

The NMI function can be used.

h Expansion board active link display LED ( )

This LED is on, depending on the expansion board status as follows.

i LAN active link display LED ( )

It is lit or blinks depending on the LAN status as follows.

j Display / USB extension connector ( )

Display device or USB-connected peripheral devices are connected using a Display/USB

Extension Cable.

k Expansion Card Slot

The SAS controller with array function is installed standardly.

When the optional expansion card slot module is installed, a PCI-Express or PCI-X expansion

card can be installed. The type of card that can be installed varies depending on the type of the

expansion card slot module.

Blinks green-amber Blinks when a BMC *1 error was detected with KVM selected, or when the

maximum installable number for the Server Blades was exceeded.

In this case, contact an office listed in the "Contact Information" of "Start

Guide" or device administrator.

table: Expansion board active link display LED


Lights green One of two ports is establishing a link.

table: LAN active link display LED


Lights green One of six LAN ports is establishing a link.

Blinks green Data is currently transferred or received through a LAN.

table: KVM select LED


I/O

30

Chapter 1 Overview

1.3.2 Internal View of Server Blade

a Expansion Card Slot

b Chassis connector

Various interface signals are connected to the chassis connector.

c Expansion board slot

Install an expansion board.

d Port 1 for I/O expansion board and port 2 for I/O expansion board

Ports (Max. 2 ports) for I/O expansion board (Fibre Channel Expansion Board/LAN Expansion

Board). These ports are connected to the Network Blade (NET 3/4) on the rear of the Chassis via

the mid plane.

e Memory slots

A memory module (Add-on RAM module) is installed in the memory slot.

f CPU sockets

Install the CPU.

One socket is installed by default. Up to two sockets can be installed.

g 2.5-inch storage bay

fg

c

d

e

a

b

[Front] [Rear]

31


1.3.3 Baseboard

a Expansion board slot

b Switch block

For details about switch settings, refer to "8.1 Switch Block Settings" (�pg.204).

c Memory slots

d CPU sockets

e SAS connector 1

This connector is connected to 2.5-inch storage bay 1.

f SAS connector 2

This connector is connected to 2.5-inch storage bay 2.

g Connector for expansion card slot module

When an expansion card slot module is installed, this connector is connected to the expansion

card slot module.

a b

cd

e

f

g

[Front] [Rear]

32

Chapter 1 Overview

1.4 Workflow

Use the following workflow from server installation to start of operation.

Installing the serverReferring to "Safety Precautions" and "Start Guide", install the server to a suitable place.

Preparing the server- Install Internal options- Set hardwareReferring to "BX600 S3 Blade Server System Unit Hardware Guide", the manual of the network blade to use, "BX600 Management Blade Hardware Guide" and "2.1 Preparation on the server", "Chapter 7 Installing Internal Options", "Chapter 8 Hardware Configuration/Utilities" in this manual.

Selecting the installation method

Referring to "2.2 Selecting the Installation Method", decide what installation method to use.ServerStart, a software product that enables everything from OS installation/setup to the installation of high reliability tools to be performed in one operation, can be used in this server. It is recommended that ServerStart is used to perform installation.

Checking precautions on installationBefore installing the OS, check the precautions on installation by referring to "2.3 Precautions on Installation".

Procedures before operationBefore operating the server, refer to "Chapter 5 Operations after OS Installation".

High reliability tool installation

Start operations

Installing Internal optionsReferring to "Chapter 7 Installing Internal Options", install the Internal options.

Using ServerStartReferring to "Chapter 3 OS Installation Using ServerStart", perform OS installation.

Manual installationReferring to "Chapter 4 Manual OS Installation", perform OS installation.

When the OS is installed manually, it is necessary to install high reliability tools. ServerView requiressettings before server operation. For installation method and details about each high reliability tool, refer to "Chapter 6 High Reliability Tools".

OS installation

33

Chapter 2

Checking before OS Installation

This chapter explains the preparation on the

server and cautions necessary before OS

installation. Please read this chapter before

starting installation.

2.1 Preparation on the Server . . . . . . . . . . . . . . . . . . . . . . . . 34

2.2 Selecting the Installation Method . . . . . . . . . . . . . . . . . . . 39

2.3 Precautions on Installation . . . . . . . . . . . . . . . . . . . . . . . . 42

34


2.1 Preparation on the Server

Before starting installation, install internal options to the server and perform

necessary hardware settings.

2.1.1 Installing Internal Options

Before installing internal options, refer to each option manual and be sure to read the notes.

Install the internal options in the Server Blades, and install the blades and options in the Chassis. For

details on the internal options, refer to the following:

• Installing internal options to Server Blades

→ "Chapter 7 Installing Internal Options" (�pg.171)

• Installing blades, Power Supply Unit, and Fan Unit in the Chassis

→ "Chapter 4 Installing Options" in "BX600 S3 Blade Server System Unit Hardware Guide"

� Cautions for installing a Storage Blade

If an array has already been configured in the internal hard disk unit that is installed in the Storage

Blade, delete the array configuration when installing the OS.

Set an array configuration again after OS installation.

� Cautions for installing an external storage system

When installing an external storage system such as the ETERNUS series in the Chassis, make sure to

turn the external storage system power on after the OS installation has completed.

Make sure the power is not turned on when installing the OS by taking precautions such as

disconnecting the power cable.

� LAN cable

Be sure to connect the LAN cable when the server is not connected to the Internet.

� Connecting to the Internet during setup can cause security problems. Do not connect to the Internet

until the setup completes.

If the OS is installed or applications are automatically installed without connecting the LAN cable, an

error may be recorded in the event viewer after the setup process finishes.

� Cautions for installing an expansion card

When using an expansion card, read the notes on the expansion card.

35


� USB floppy disk drive and USB CD/DVD drive

To use the PRIMERGY Startup Disc, connect the USB floppy disk drive and USB CD/DVD drive to the

Server Blade to be installed. Use the Display/USB Extension Cable to connect them before turning the

power on the Server Blade.

It is strongly recommended that only products listed on the Fujitsu PRIMERGY website (http://

primergy.fujitsu.com) are connected to the server.

� Do not install or remove USB devices unless specified in procedures.

� Cautions for installing a memory module

The available memory size of the server depends on the OS. Furthermore, since the server uses part of

the memory as PCI resources, the maximum available size is limited.

The following shows the maximum installable size and the maximum available size.

*1: The installed memory size can become usable memory by setting PAE on each OS. For the procedure for setting PAE on each OS, refer to the Microsoft website.

*2: When installing 8GB or more of memory in a server, apply the hotfix module (KB907892) provided from Microsoft. The hotfix module is also stored in the ServerStart CD/DVD.

*3: The usable memory varies depending on the OS that is used.

table: Maximum Installable Size and Maximum Available Size

OSInstalled

memory sizeAvailable memory size

Windows Server 2008 Standard (32-bit)

Windows Server 2003, Standard Edition

Windows Server 2003 R2, Standard Edition

Up to 3GB Same as the installed memory size

3GB to 4GB Depends on the [Execute Disable Bit]

setting in the [CPU Configuration]

submenu under the Advanced menu of

the BIOS Setup Utility.

• Disabled: 3GB*1

• Enabled: Same as the installed

memory size

Windows Server 2008 Enterprise (32-bit)

Windows Server 2003, Enterprise Edition*2

Windows Server 2003 R2, Enterprise Edition*2

Up to3GB Same as the installed memory size

3GB to installed

memory size*3Depends on the [Execute Disable Bit]

setting in the [CPU Configuration]

submenu under the Advanced menu of

the BIOS Setup Utility.

• Disabled: 3GB*1

• Enabled: Same as the installed

memory size

Windows Server 2008 Standard (64-bit)

Windows Server 2008 Enterprise (64-bit)

Windows Server 2003, Standard x64 Edition*2

Windows Server 2003, Enterprise x64 Edition*2

Windows Server 2003 R2, Standard x64 Edition*2

Windows Server 2003 R2, Enterprise x64

Edition*2

Installed

memory size*3Same as the installed memory size

Linux



36


� Cautions applicable when the OS is Windows Server 2003 R2 / Windows Server 2003, Standard Edition / Windows Server 2003, Enterprise Edition

When installing 4GB or more of memory in a server, the /PAE option in the "Boot.ini" file must be

specified. For the procedure for editing the "Boot.ini" file, refer to the Microsoft website.

� The "Boot.ini" file is an important file for the system. If the file is edited improperly, the system may not

start up. Edit it carefully.

2.1.2 Hardware Settings

Before starting installation, set necessary hardware, such as the BIOS Setup Utility.

� Switch block settings

Perform and confirm physical setting for the switch block of the Server Blade. An improper setting will

cause the Server Blade not to run or malfunction.

�"8.1 Switch Block Settings" (pg.204)

� BIOS Setup Utility

The BIOS Setup Utility must be set in the following cases. For details on how to set the BIOS Setup

Utility, refer to "8.2 BIOS Setup Utility" (�pg.205).

� The contents set with the BIOS Setup Utility are recorded in CMOS and NVRAM in the Server Blade.

This CMOS stores information with the built-in battery. When a setup message is displayed during

POST even after setup was performed normally, the setup contents may not be stored in CMOS. The

built-in battery may be drained. Contact an office listed in the "Contact Information" of the "Start

Guide".

� Do not modify the item indicated "Unchangeable" in "8.2 BIOS Setup Utility" (�pg.205). The device

may not run normally.

� Changing the boot drive

To change the boot drive, start up the BIOS Setup Utility, and set the boot drive in the [Boot Device

Priority] submenu.

�"8.2.15 Boot Device Priority Submenu" (pg.225)

� Specifying a password

To specify a password, start the BIOS Setup Utility, select "Change Supervisor Password" or "Change

User Password", and enter your password.

�"8.2.7 Security Menu" (pg.214)

37


� Setting the time synchronization function with the Management Blade

To set the time synchronization function with the Management Blade, select "Sync RTC with Mgnt.

Blade" in the [Main] menu on the BIOS Setup Utility, and specify the time synchronization function.

�"8.2.2 Main Menu" (pg.208)

� Using an USB CD/DVD drive (change of device priority sequence)

When using the USB CD/DVD drive, change the device priority sequence in the [Boot] menu of the

BIOS Setup Utility.

For more details about changing the boot drive, refer to "8.2.15 Boot Device Priority Submenu"

(�pg.225).

� Booting the Server Blade with PXE

Before Booting the Server Blade with PXE, use the following procedures to enable network startup

(PXE). In addition, check the MAC address.

� When booting the Server Blade with PXE, turn on the Server Blade power one minute or more after the

main power of the Chassis was turned on. Turning on the Server Blade power just after the main

power was turned on may cause PXE not to boot due to the Switch Blade not having been started.

� The PXE boot function is not available for the LAN port of the 1 Gbit/s Ethernet I/O Module.

1 Take the following steps in the BIOS Setup Utility.

Set PXE (IBA CE slot nnnn v) to the highest level in the boot priority sequence.

For more details about changing the boot drive, refer to "8.2.15 Boot Device Priority Submenu"

(�pg.225).

� The boot priority sequence can be changed from Web UI or CLI for the Management Blade.

Refer to "BX600 Management Blade Hardware Guide".

2 Check the MAC address.

After BIOS setup, start up the server from the network.

After POST was completed, the MAC address is displayed as shown below.

3 Turn off the server.

� You can confirm that the server is turned off using "Deployment Parameter" for Web UI and

CLI, and "Server Blade MAC Address Table" for CLI of the Management Blades. For details,

refer to "BX600 Management Blade Hardware Guide".

1st Boot Device [Y-E USB-FDU]

2nd Boot Device [CENERIC CDR****]

3rd Boot Device [#520 ID00 LUN0 ***] (When an expansion card slot

module is not installed)

4th Boot Device [IBA CE Slot **** v]

5th Boot Device [IBA CE Slot **** v]

CLIENT MAC ADDR: ** ** ** ** ** **

38


� When installing Windows Server 2008 (64-bit) using ServerStart

When installing Windows Server 2008 (64-bit) using ServerStart, and when saving the configuration file

to a floppy disk, the boot priority must be changed as follows using the BIOS Setup Utility at ServerStart

startup.

� If the boot priority is not changed, the automatic installation stops in the middle. Make sure to change

it.

1 Turn the Server Blade on, and start the BIOS Setup Utility.

�"8.2.1 Starting and Exiting the BIOS Setup Utility" (pg.205)

2 Select the [Main] menu – [Boot] submenu, and press the [Enter] key.

The [Boot Settings] window appears.

3 Select [Boot Device Priority], and press the [Enter] key.

The [Boot Device Priority] submenu appears.

4 Set the Boot device to put [Hard Disk Drives] before [Removable Drives].

Set it as follows.

[Removable Drives] and [CD/DVD Drives] are displayed when connecting the USB device.

1 CD/DVD Drives

2 Hard Disk Drives

3 Removable Drives

5 Exit the BIOS Setup Utility, and turn the server's power off.

39


2.2 Selecting the Installation Method

When installing the OS for the first time, there are multiple installation methods. Refer

to the following to decide on the method.

Refer to "3.2 Expert Mode" and perform

installation.

* If you follow the wizard, setup will be performed

correctly.

Linux

No

Windows Server 2003 R2 x64

Windows Server 2003 x64Windows Server 2003 R2

Windows Server 2003

No

Yes

Yes

For the use of Linux, refer to the Fujitsu

PRIMERGY website (http://primergy.fujitsu.com).

Installation is performed manually.Refer to "4.2 Starting Manual Installation" and

perform installation.

Refer to "3.1 Quick Installation Mode" and begin

the install. By setting the minimum settings the

install will start quickly.

Do you want to use

the default settings?

Will you use ServerStart?

What OS will you use?

Windows Server 2008 x64Windows Server 2008

40


2.2.1 Supported OS

The supported OS varies depending on the ServerStart version.

� ServerStart V7.804

For ServerStart V7.804, the following OSes can be installed.

• Microsoft® Windows Server® 2008 Standard

• Microsoft® Windows Server® 2008 Enterprise

• Microsoft® Windows Server® 2008 Standard without Hyper-V™

• Microsoft® Windows Server® 2008 Enterprise without Hyper-V™

� ServerStart V6.711

For ServerStart V6.711, the following OSes can be installed.

• Microsoft® Windows Server® 2003, Standard Edition

• Microsoft® Windows Server® 2003, Enterprise Edition

• Microsoft® Windows Server® 2003, Standard x64 Edition

• Microsoft® Windows Server® 2003, Enterprise x64 Edition

• Microsoft® Windows Server® 2003 R2, Standard Edition

• Microsoft® Windows Server® 2003 R2, Enterprise Edition

• Microsoft® Windows Server® 2003 R2, Standard x64 Edition

• Microsoft® Windows Server® 2003 R2, Enterprise x64 Edition

� ServerStart does not support OS installation of Linux.

� Any of unsupported OS can not be installed.

41


2.2.2 Installation Modes of ServerStart

� Quick installation mode

This mode completes the OS installation by executing plain settings. Select this mode when you want to

install the OS quickly and simply.

When installing Windows Server 2008 in Quick installation mode, perform full installation.

To install while maintaining the established RAID environment, the quick installation mode must be

selected to install the OS.

Select [Logical Disk0] in the [Select the Boot Controller and Boot Disk] window and install the OS.

� Expert mode

In this mode, start up Disk Manager and format the partition where your OS is installed prior to

installation of the OS. Select the expert mode only when installing the OS while maintaining the existing

partitions.

Windows Server 2008 cannot be installed in Expert mode.

Also, when using ServerStart while maintaining the existing partitions, start up Disk Manager, format an

installation partition and install the OS.

42


2.3 Precautions on Installation

Read the following notes before starting OS installation.

2.3.1 Installation Partition Size

For installation using ServerStart, the installation partition size can be set as follows.

• Maximum size: 2TB

• Minimum size: 2200MB

� Notes

• When you want to set the OS and BOOT partitions in different partitions, specify the partition size

directly.

• In either of the following cases, specify a partition size up to 2TB.

• When the same partition is specified as the OS and BOOT partitions

• When different partitions are specified as the OS and BOOT partitions

• The OS cannot be installed in a partition larger than 2TB.

� The BOOT partition is a partition for booting. Minimum information that is necessary for booting such

as "ntldr" is set.

The OS partition is a partition for installing the OS.

2.3.2 Notes on Configuring RAID

When configuring RAID, check the following beforehand.

� Internal hard disk unit

• Up to two internal hard disk units can be installed in the Server Blade, and up to five internal hard

disk units can be installed in the Storage Blade.

• Internal hard disk units that can be installed in the Server Blade or Storage Blade vary depending on

the RAID level. For details, refer to the manuals in the Array Controller Document & Tool CD.

• Be sure to use hard disk units of the same model and with the same capacity.

43


� RAID configuration

Array controllers to be used vary. For RAID configuration, refer to the respective manuals.

� When using an onboard SAS Ctrl (Integrated Mirroring SAS)

Configure RAID with an internal hard disk unit which is connected to a SAS Ctrl.

The array controller to be employed is "Integrated Mirroring SAS" and available RAID level is

"RAID1" only. For details, refer to "Integrated Mirroring SAS User's Guide" in the Array Controller

Document & Tool CD.

� When using a SAS RAID Ctrl (MegaRAID SAS)

Configure RAID with a Storage Blade which is connected to a SAS RAID Ctrl.

The array controller to be employed is "MegaRAID SAS" and available RAID level is "RAID0 /

RAID1/ RAID1+0 / RAID5/ RAID6".

For details, refer to "MegaRAID SAS User's Guide" in the Array Controller Document & Tool CD.

2.3.3 Notes on a Multiple LAN Adapter Configuration

Using the OS installation wizard of ServerStart, you can configure multiple LAN adapters (network

adapters) on the system. However, there are the following limitations.

� Adapter numbers

To configure multiple LAN adapters (PG-2861L/PG-LND201, etc.), select the adapter numbers in order

of Adapter 1 and Adapter 2, and enter settings for each adapter. Note that the order of adapter numbers is

not necessarily the same as the onboard LAN port numbers. This means that the setting for Adapter 1 is

not always applied to LAN port 1 of the onboard LAN. After installing the OS, check the LAN adapters

to make sure that they are configured as intended.

2.3.4 Cautions for Using ServerStart

Observe the cautions described below when the OS installation is performed with ServerStart.

� Operating ServerStart

Mainly, a mouse is used for ServerStart operations. In some cases, operation with the [Tab] key or cursor

are not available. Be sure to use a mouse while operating ServerStart.

44


� Configuration file (SerStartBatch.ini)

A configuration file stores the server setup and client information configured in ServerStart. To create a

configuration file, use the ServerStart floppy disk. Store only one file on each floppy disk. Do not set the

ServerStart floppy disk to the write-protected state. You can use any name for the configuration file.

However, the file must be installed in the server as "SerStartBatch.ini". When installing the

configuration file, make sure to save it as "SerStartBatch.ini" on the ServerStart floppy disk. Start up

ServerStart, insert the ServerStart floppy disk containing "SerStartBatch.ini", and click [Start] to install

the server

� Ejecting PRIMERGY Startup Disc

Do not eject PRIMERGY Startup Disc while ServerStart is running. If the PRIMERGY Startup Disc is

ejected and inserted again, ServerStart starts up in multiple windows, and settings you have made may

be lost.

� Exiting ServerStart

After operation in the expert mode, exiting ServerStart restarts the system. Remove discs from the

floppy disk and CD/DVD drives and click [OK]. When the display on the screen disappears, turn off the

system.

� License for use of system for ServerStart

"License for Use of System for ServerStart" linked from the ServerStart startup window is a license for

use of Windows PE contained in ServerStart of the PRIMERGY Startup Disc. Windows PE for starting

up ServerStart can be only used for installing Windows Server 2008, Windows Server 2003 R2, and

Windows Server 2003, provided under a separate legal license.

� Display of onboard LAN

Display of an onboard LAN on your OS is as below when OS installation performs with ServerStart.

� Adapter numbers

For ServerStart, onboard multiple LAN adapters (network adapter) may be configured on OS

installation wizard.

To configure multiple LAN cards, select the adapter numbers in order of Adapter 1 and Adapter 2, and

enter settings for each adapter. Note that the order of adapter numbers is not necessarily the same as the

order of slots for the installed LAN adapters. This means that the setting for Adapter 1 is not always

applied to the onboard LAN. After installing the OS, check the LAN adapters to make sure that they are

configured as intended.

� Setting up the printer

ServerStart does not support setup of printers. Perform installation after setup is completed.

table: Display of Onboard LAN

LAN Port Property on My Network LAN Device Name

Onboard LAN Local Area Connection BroadcomNetXtreme Gigabit Ethernet

45


� Caution when installing the LAN expansion board (PG-LND201)

When installing an OS using ServerStart in a device which contains a LAN expansion board (PG-

LND201), the Connection Name and IP address settings that are set in the network protocol screen of the

OS installation wizard will not be set.

Allocate the Connection Name and IP address in the LAN expansion board (PG-LND201) manually

after the OS installation.

2.3.5 Onboard Controller and Expansion Cards Supported by ServerStart

ServerStart supports automatic driver installation for the following expansion cards.

2.3.6 Cautions for Manual Installation

� Checking onboard array controller setting

Disk array configuration on the onboard array controller must be completed before the OS is installed.

For more details, refer to the manual in the Array Controller Document & Tool CD.

� Free space required for installation

The partition where the OS is installed must have enough free space for obtaining memory dump. For

more details, refer to "5.1 Memory Dump/Paging File Setting" (�pg.100).

� Cautions on restarting

In the course of installation, a message appears to indicate that the setup program restarts. Wait until it

restarts.

For more details on background operations, refer to the manual in the Array Controller Document &

Tool CD.

table: Automatic Expansion Card Driver Installation

Name Model Bus

Onboard SAS (array) controller - PCI-E

Onboard LAN - PCI-E

Onboard VGA - PCI

SAS RAID Ctrl PG-248EL PCI-E

Eth. Ctrl 2x1Gbit PCI-E 1000-BASE-T lp PG-2861L PCI-E

SCSI Ctrl U160 lp PG-1301L PCI-X

1Gbit/s Ethernet I/O Module PG-LND201 PCI-E

2Gbit/s FC I/O Module PG-FCD102 PCI-X

4Gbit/s FC I/O Module PG-FCD201 PCI-E

46


47

Chapter 3

OS Installation using ServerStart

This chapter explains how to install the OS in the

server using ServerStart.

3.1 Quick Installation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2 Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

48


3.1 Quick Installation Mode

In this quick installation mode, the OS is installed after configuring minimum required

settings. To install the OS quickly and easily, use the quick installation mode.

� When installing Windows Server 2008, perform "Full installation".

� When installing Windows Server 2008 (64-bit) using ServerStart, and when saving the configuration

file to a floppy disk, the boot priority must be changed as follows using the BIOS Setup Utility at

ServerStart startup. For the procedure for changing the boot priority, refer to "� When installing

Windows Server 2008 (64-bit) using ServerStart" (�pg.38)

1 Connect the USB CD/DVD drive and USB floppy disk drive to the Server Blade.

Use the Display/USB Extension Cable to connect the USB CD/DVD drive and USB floppy disk

drive. For more information on the connection procedure, refer to "Start Guide".

2 Turn on the server and insert PRIMERGY Startup Disc immediately.

� When installing Windows Server 2003, use "PRIMERGY Startup Disc". When installing Win-

dows Server 2008, use "PRIMERGY Startup Disc for Windows Server 2008".

ServerStart starts up. The select-media window for the configuration file appears.

49


3 Insert the ServerStart floppy disk. Make sure that "on local drive (floppy/USB

stick)" and "A:" are selected and click [Continue].

� Set the ServerStart floppy disk in the write-enabled state.

� When installing the OS without using the ServerStart floppy disk, select [No status backup],

and click [Next]. [No status backup] cannot be selected in the following cases.

•When configuring RAID using ServerStart

•When installing Windows Server 2003 x64

•When installing Windows Server 2008

The [Initialization of ServerStart core running] window appears and the ServerStart initialization

process starts. Depending on hardware configuration, this process may take a few minutes. After

completion, the license agreement window appears.

50


4 Click [Accept].

The [Welcome to ServerStart] window appears.

5 Select [Quick Installation] and click [Next].

The [Select the Boot Controller and Boot Disk] window appears.

51


6 Set configuration of the RAID and disks and click [Next].

To install the OS while maintaining the established RAID environment

Select [Logical Disk 0] and specify partition size to be created.

One partition can be created. Select [Logical Disk 0] even if the RAID is not required to be

created.

To configure RAID

Select [create new RAID array with one partition] and specify the RAID level to be configured

and the size of the partition.

All existing RAID will be deleted. Also, only one partition can be created.

� When [Auto] is selected, the RAID is configured with the following levels, depending on the

number of the installed disk units.

•When two hard disk units are installed: RAID1

•When three hard disk units are installed: RAID5

•When more than three hard disk units are installed: RAID5 with hot spare function

� The configurations of the created partitions are as follows.

•Volume label: system

•File system: NTFS

•Partition configuration: Boot/OS

The [Please select the OS to install] window appears.

52


7 Select the OS to be installed and click [Next].

The [Configure your unattended Windows Installation] window appears.

8 Set the items and click [Next].

The [Summary] window appears.

9 Confirm the settings and click [Start Installation].

10 Click [Start now].

Installation starts.

1. If a message prompts you to insert Array Controller Document & Tool CD, insert the

CD and click [OK].

2. For Windows Server 2003 x64, a message appears and prompts you to insert

PRIMERGY Startup Disc Win64 and restart the system. Insert PRIMERGY Startup

Disc Win64.

11 When a message prompts you to insert the OS CD/DVD, insert the CD/DVD

and click [OK].

For Windows Server 2008

1. Insert the OS CD/DVD (Installation disc).

Copying files starts.

After files are copied, a message prompts you to eject the CD/DVD and floppy disk.

� For Windows Server 2008 (64-bit), a message appears and prompts you to insert the PRIM-

ERGY Startup Disc again. Insert PRIMERGY Startup Disc. After files are copied, a message

prompts you to eject the CD/DVD and floppy disk.

53


For Windows Server 2003 / Windows Server 2003 x64


The license agreement window appears.

2. Click [Accept].


For Windows Server 2003 R2 / Windows Server 2003 R2 x64

1. Insert the OS CD/DVD (Installation disc) Disc 1.


2. Click [Accept].

After files are copied, a message prompts you to insert the Disc 2.



12 Eject the CD/DVD and floppy disk and click [OK].

The system is restarted.

The system continues the installation operation after restart.

Setup of OS GUI and installation of LAN utility, Service Pack, and Active Directory are

performed automatically.

13 When a confirmation message to restart appears, click [Restart].

The system restarts and installs high reliability tools.

� Thus the Command Prompt windows may appear and disappear during installation of

ServerView, the installation process is properly proceeding.

� When using Microsoft media, the screen to input a product key may be displayed during OS

installation. When the input screen is displayed, input the product key again.

14 When a message notifies completion of installation, restart the system.


The system automatically restarts when a message notifies completion of installation.

After restarting, enter the set password to log in.


Press the [Enter] key when a message notifies completion of installation.

Click [Start] – [Shutdown] to restart the system.

After restarting, enter the specified password to login.

15 Perform settings for the RAID management tool (ServerView RAID).

For details, refer to the manuals in the Array Controller Document & Tool CD.

For the manual of the SAS RAID Ctrl to be used, refer to "2.3.2 Notes on Configuring RAID"

(�pg.42).

• Setting an array administrator account

A Windows user account is required when using ServerView RAID. Create the group "raid-

adm", and create an account with any name for an array administrator in this group.

• Setting the HDD check scheduler

When using the SAS RAID Ctrl (MegaRAID SAS), change the settings for the HDD check

scheduler according to the operation that is required. It is set to 12:00 everyday as default.

54


16 Perform settings for ServerView.

Refer to "2.4 Checking after Installation" in "ServerView User's Guide" to perform the necessary

settings.

The server setup and OS installation have been completed.

Refer to "Chapter 5 Operations after OS Installation" (�pg.99) and perform necessary procedures before

starting server operations.

55


3.2 Expert Mode

In the expert mode, start up Disk Manager, format the installation partition, and install

the OS. Use this mode only when you want to perform installation while maintaining

the existing partitions.

� Windows Server 2008 cannot be installed in Expert mode.

3.2.1 Starting Up the Expert Mode

Start up the expert mode.




2 Turn on the server and insert PRIMERGY Startup Disc immediately.

ServerStart starts up. The select-media window for the configuration file appears.

56


3 Set the ServerStart floppy disk, and ensure that "Removable media" and "A:"

are selected. Click [Continue].

The [Initialization of ServerStart core running] window appears and the ServerStart initialization

process starts. Depending on hardware configuration, this process may take a few minutes. After

completion, the license agreement window appears.

4 Click [Accept].


57


5 Select [Expert Installation] and click [Next].

The [Create a ServerStart Floppy Disk] window appears.

6 Click [Build a ServerStart Floppy Disk].

Creation of a ServerStart floppy disk starts. When the creation is completed, the "Floppy disk has

been created." message appears.

7 Click [OK].

The [Please Select your Keyboard] window appears.

8 Select your keyboard language from the drop-down list and click [OK].

The subsequent start procedure may take several minutes.


58


9 Click [Click here to prepare and/or initiate an operating system installation].

The [Select the operating system to be installed] window appears.

Click [Special Hints on Operating System Installation] and observe them carefully. Important

information such as limitations on configuration of hard disk units is described.

10 Click [MS Windows Operating Systems].

The [Microsoft Windows Operating System Installation] window appears.

11 Click [Install MS Windows Server 2003 or MS].

The [Installation of MS Windows Server 2003] window appears.

12 Click [Install MS (OS) interactively (expertise required)].

The expert mode starts.

Start up the configuration tools to set items. Exiting a tool returns to the display to the expert

mode window.

� Make sure to open the menu of each wizard and confirm the settings.

59


3.2.2 Disk Manager

Start up Disk Manager and format the installation partition.

1 Click [Use Disk Manager to partition and format your disk drives].

Disk Manager starts up.

2 Format the OS installation partition. Select the OS installation partition and click

the [Partition] menu – [Format].

The [Format Partition] window appears.

� Be sure to set the active partition on drive C.

3 Set items and click [Format].

The partition is formatted.

4 When the formatting is completed, click the [File] menu – [Exit].

Disk Manager closes and the display returns to the expert mode window.

60


3.2.3 OS Installation Wizard

Set computer information, user information, and the network protocol.

ServerStart can configure multiple network patterns. When configuring a domain controller, refer to

"Using ServerStart to Configure the Network".

� The setup windows vary depending on the OS to be installed. For example, operation on Server 2003

R2 is given below. Server 2003 R2 is corresponding to your OS to be installed.

1 Click [Installation Wizard for MS Windows Server 2003].

A message prompts you to specify the configuration file.

2 Click [No].

The [Windows Installation] window appears.

3 Enter the password in [Password for Administrator account] and [Please repeat

Password] and click [Next].

� If the passwords of [Password for Administrator account] and [Please repeat Password] are

not identical, an error message occurs. Enter the password correctly.

61


The [Computer Identification] window appears.

4 Set items and click [next].

The [Installation Directory and Time Zone] window appears.

62



The [User Name] window appears.


The [Display Settings] window appears.


The [Network Protocol] window appears.

63



The [Software Components] window appears.

� If Windows Server 2003 R2 is selected at the Computer Identification, R2 components are

always copied to the hard disk. To install the components, click [Properties] and check t box of

the components to be installed.

64



The [Services] window appears.

� Simple Network Management Protocol is always installed. Click [Properties] to change the set-

tings.

10 Set items and click [leave wizard].

The display returns to the expert mode window.

65


3.2.4 Application Wizard

Set configurations for installation of high reliability tools. Open those windows and confirm the settings

carefully.

1 Click [Application Wizard: Select additional software components].

The application wizard appears.

2 From the list in [Installable applications], select application software to be

installed and click [>>].

Set all applications to be installed on the [Selected applications] list.

� Although the selection can be released in the expert mode, it may take a long time to restore

the system when errors occur without the management tools. Be sure to install these tools.

•DSNAP

•Broadcom Advanced Control Suite

•RAID Management Tool

•ServerView (for Apache)

•ServerView (for IIS)

� Service Pack 1 or Service Pack 2 can be installed with ServerStart.

3 Click [leave wizard].

The application wizard closes.

66


3.2.5 Starting OS Installation

Install the OS to the server.

Notes on the Installation

� When the installation partition is not empty, a confirmation message appears. Unless otherwise

considered as problem, click [OK] to continue the installation procedure.

� If an incorrect setting (such as the CD key) is found during installation, an error window will appear.

Enter the correct values in the window to continue the installation procedure. However, corrections

made here are not reflected on the configuration file.

1 Click [Click here, to Start the Installation of (OS)].

A confirmation window asking whether you want to save the current settings appears.

2 Click [Yes].

The following window appears.

3 Enter the file name and click [Save As].

Installation starts automatically.

1. If a message prompts you to insert Array Controller Document & Tool CD, insert the

CD-ROM and click [OK].

2. If a message prompts you to insert the Service Pack CD-ROM, insert the CD-ROM

and click [OK].

3. For Server 2003 x64, a message prompts you to insert PRIMERGY Startup Disc

Win64 and restart the system. Insert PRIMERGY Startup Disc Win64.

67


4 When a message prompts you to insert the OS CD/DVD, insert the CD/DVD

and click [OK].

For Windows Server 2003 / Windows Server 2003 x64



2. Click [I agree].


For Windows Server 2003 R2 / Windows Server 2003 R2 x64



2. Click [I agree].

After files are copied, a message prompts you to insert the Disc 2.

3. Insert the Disc 2 of OS CD/DVD (Installation disc).


5 Eject the CD/DVD and floppy disk and click [OK].

The system is restarted. The system continues the installation operation after restart.

Setup of OS GUI and installation of LAN utility, Service Pack, and Active Directory are

performed automatically.

6 When a confirmation message to restart appears, click [Restart].

The system restarts and installs high reliability tools.

� Thus the Command Prompt windows may appear and disappear during installation of

ServerView, the installation process is properly proceeding.

7 Press the [Enter] key when a message notifies completion of installation.

8 Restart the system.

Click [Start] – [Shutdown] to restart the system.

After restarting, enter the specified password to login.


For details, refer to the manual in the Array Controller Document & Tool CD.


(�pg.42).







10 Perform settings for ServerView.

Refer to "2.4 Checking after Installation" in "ServerView User's Guide" to perform the necessary

settings.

68


The server setup and OS installation have been completed. Refer to "Chapter 5 Operations after OS

Installation" (�pg.99) and perform necessary procedures before starting server operations.

69

Chapter 4

Manual OS Installation

This chapter explains how to install the OS

without using ServerStart.

4.1 Creating Driver Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4.2 Starting Manual Installation . . . . . . . . . . . . . . . . . . . . . . . 76

4.3 Installing the LAN Driver . . . . . . . . . . . . . . . . . . . . . . . . . 89

4.4 Installing the Fibre Channel Driver . . . . . . . . . . . . . . . . . . 94

4.5 Installing SAS RAID Ctrl Driver . . . . . . . . . . . . . . . . . . . . 97

70


4.1 Creating Driver Disks

When installing the OS manually, it is necessary to create driver installation disks

beforehand. Also, driver disks must be created when you add an expansion card

during server operation.

4.1.1 Required Driver Disks

You need floppy disks for driver disks. A floppy disk is necessary for each driver.

Required driver disks vary with the OS.

� Standard driver provided with the OS is installed automatically at the OS installation.

� You need a PRIMERGY Startup Disc to install the driver provided with the PRIMERGY Startup Disc.

Prepare for it in advance.

� For Windows Server 2008 (32-bit/64-bit)

table: Drivers Required for Installing Windows Server 2008 (32-bit/64-bit)

Expansion board / onboard controller Driver

Chipset OS standard

Onboard VGA Driver provided with the PRIMERGY Startup Disc

Onboard LAN controller Driver provided with the PRIMERGY Startup Disc

Onboard array controller OS standard

Eth. Ctrl 2x1Gbit PCI-E 1000-BASE-T lp (PG-2861L)

1 Gbit/s Ethernet I/O Module (PG-LND201)

Driver provided with the PRIMERGY Startup Disc

2Gbit/s FC I/O Module Driver provided with the PRIMERGY Startup Disc


SCSI Ctrl U160 lp (PG-1301L) OS standard

SAS RAID Ctrl (PG-248EL) OS standard

71


� For Windows Server 2003 x64

*1: Create using the ServerStart FloppyBuilder function.

� For Windows Server 2003

*1: Create using the ServerStart FloppyBuilder function.

table: Drivers Required for Installing Windows Server 2003 x64


Chipset Driver provided with the PRIMERGY Startup Disc



Onboard array controller PRIMERGY BX620 S4 Onboard SAS/RAID

Driver for Windows Server 2003 x64

V1.25.05.00 *1







SAS RAID Ctrl (PG-248EL) Driver provided with the PRIMERGY Startup Disc

table: Drivers Required for Installing Windows Server 2003


Chipset Driver provided with the PRIMERGY Startup Disc



Onboard array controller PRIMERGY BX620 S4 Onboard SAS/RAID Driver

for Windows Server 2003 V1.25.05.00 *1







SAS RAID Ctrl (PG-248EL) Driver provided with the PRIMERGY Startup Disc

72


4.1.2 How to Create Driver Disks [FloppyBuilder Function]

Driver disks are created from the PRIMERGY Startup Disc using the ServerStart FloppyBuilder

function. The FloppyBuilder function is available in the following environments.

• Starting up the ServerStart system on a client computer (Recommended)

• Starting up the system from the PRIMERGY Startup Disc on the server

� When creating driver disks on a client computer, it is necessary to install ServerStart on the client

computer beforehand, referring to "5.4.1 Installing ServerStart" (�pg.113).

If a different version of ServerStart has been installed, uninstall it and install the proper version. For

details on how to uninstall ServerStart, refer to "� Uninstalling ServerStart" (�pg.115).

� Starting ServerStart

If ServerStart has already been started, it is not necessary to restart it. If it has not, start it up according to

the following procedures:

� For creation on a client computer

1 Set the PRIMERGY Startup Disc to the client computer.

Once "PRIMERGY Startup Disc" window appears, exit the window.

2 Click [Start] − [All Programs] − [Fujitsu Siemens ServerStart] – [ServerStart

(Start from DVD)].

ServerStart starts up and the [Welcome to ServerStart] window appears.

73


� For creation on the server




2 Turn on the power of the Server Blade and set PRIMERGY Startup Disc.

ServerStart starts up and select media window for the configuration file appears.

3 Insert the ServerStart floppy disk. Make sure that "on local drive (floppy/USB

stick)" and "A:" are selected and click [Continue].

The [Initialization of ServerStart core running] window appears and the initialization operation

launches. In some cases, initialization operation may take a few minutes, depending on hardware

configuration. After completion, the license agreement window appears.

4 Click [Accept].


74


5 Click [Expert Installation] and click [OK].


6 Eject the ServerStart floppy disk.

� Creating driver disks

Start up ServerStart and confirm that the [Welcome to ServerStart] window is displayed.

1 Click [FloppyBuilder].

The [ServerStart FloppyBuilder] window appears.

2 Select [Drivers Diskettes (for OS)].

The [FloppyBuilder Driver Disk] window appears.

3 Click the type of the driver you want to create.

75


4 Click the driver disk you want to create.

Follow the message and insert a floppy disk.

5 Perform the subsequent operations according to the messages on the window.

The floppy disk will be formatted automatically and file copying will start.

The driver disk is automatically created. When a message appears indicating that creating the

disk is completed, click [OK] and eject the floppy disk.

76


4.2 Starting Manual Installation

This section explains the procedures for installing the OS manually.

� Using the USB CD/DVD drive / USB floppy disk drive

It is strongly recommended that only products listed on the following website are connected to the

server.

Fujitsu PRIMERGY website (http://primergy.fujitsu.com)

4.2.1 Installing Windows Server 2008 (Full)

� Installation procedure

1 Create driver disks.

Prepare the necessary drivers before installing Windows Server 2008.

Some drivers are created from the PRIMERGY Startup Disc. For details about how to create

driver disks, refer to "4.1 Creating Driver Disks" (�pg.70).




3 Turned on the Server Blade and configure RAID.

Turn on the Server Blade to display the following message and press the [Ctrl] + [C] key to start

up the BIOS Utility.

If RAID is not required to be configured, proceed to step 4.

The array system is configured by using BIOS Utility. For more details, refer to the manual in the

Array Controller Document & Tool CD.

Turn off the Server Blade after configuring the array system.

4 Turn the Server Blade on again, and insert the Windows Server 2008 DVD-

ROM into the CD/DVD drive.

There are two DVD-ROMs, for 32bit and for 64bit. Check them before inserting the DVD-ROM.

When the active area is specified on the hard disk, the following message appears.

Pressing any key while this message is displayed boots the system from the DVD-ROM.

Press Ctrl C to start LSI Logic Configuration Utility

Press any key to boot from CD or DVD...


77


5 Setup window for Windows Server 2008 installation appears. Set each item

according to the window.

6 Click [Next].

Continue installation procedures according to the setup window.

The OS selection window appears.

78


7 Select the OS to be installed.

Select "Windows Server 2008 Standard (full installation)".


8 After reading through its contents, check [Accept] and click [Next].

OS installation is automatically performed by the setup program (reboot will occur a few times).

9 Proceed to the installation procedure following the setup program instructions.

If a message stating that the driver has not passed the Windows logo test to verify convertibility

with Windows is displayed while installing, select [Yes] to proceed with the installation.

10 Install the display driver.

1. Click [Start] – [Administrative Tools] – [Computer Management].

2. Click [Device Manager] from the displayed list.

3. Double-click [Standard VGA Graphics Adapter] under [Display Adapters] to display

the property window.

4. Click the [Driver] tab and click [Updating Driver]. The [Update Driver Software]

window appear.

5. Click [Browse my computer for driver software].

6. Insert PRIMERGY Startup Disc, and click [Browse] to select the following folder.

• Windows Server 2008 Standard (32-bit)

[CD/DVD drive]: \VGA_8.24.50.3\Driver\XP_INF


[CD/DVD drive]: \VGA_8.24.50.3\Driver\XP6A_INF

When driver installation has completed, the following message is displayed.

7. Reboot the server.

� VGA chip installation cannot be performed by using the installer.

11 Install the LAN driver.

Install the LAN driver using the PRIMERGY Startup Disc. For details, refer to "4.3 Installing the

LAN Driver" (�pg.89).

12 Install the Fibre Channel Driver.

When the Fibre Channel Expansion Board has been installed, install the Fibre Channel Driver

using the PRIMERGY Startup Disc.

For details, refer to "4.4 Installing the Fibre Channel Driver" (�pg.94).

13 Install high reliability tools.

To ensure stable server operation, refer to "Chapter 6 High Reliability Tools" (�pg.163) and

install high reliability tools.

Driver software installation for this device has completed: ATI

ES1000

79





(�pg.42).







The installation of Windows Server 2008 is completed.

� Before starting operation

After OS installation, refer to "Chapter 5 Operations after OS Installation" (�pg.99) and perform

necessary operations.

4.2.2 Installing Windows Server 2008 (Server Core)



Prepare the necessary drivers before installing Windows Server 2008 Server Core.

Some drivers are created from the PRIMERGY Startup Disc. For details about how to create

driver disks, refer to "4.1 Creating Driver Disks" (�pg.70).




3 Turned on the Server Blade and configure RAID.

Turn on the Server Blade to display the following message and press the [Ctrl] + [C] key to start

up the BIOS Utility.

If RAID is not required to be configured, proceed to step 4.





80


4 Turn the Server Blade on again, and insert the Windows Server 2008 DVD-

ROM into the CD/DVD drive.

There are two DVD-ROMs, for 32bit and for 64bit. Check them before inserting the DVD-ROM.

When the active area is specified on the hard disk, the following message appears.

Pressing any key while this message is displayed boots the system from the DVD-ROM.

5 The setup window for Windows Server 2008 installation appears. Set each item

according to the window.

Press any key to boot from CD or DVD...

81


6 Click [Next].

Continue the installation procedure according to the setup window.

The OS selection window appears.

7 Select the OS to be installed.

Select "Windows Server 2008 Standard (Server Core installation)".


8 After reading through its contents, check [Accept] and click [Next].

OS installation is automatically performed by the setup program (reboot will occur a few times).

9 Set a password for the Administrator.

Click "Other Users" when it is displayed.

The user ID and password entry window appears. Enter "Administrator" as the ID, leave

password empty and click [→].

The window where the password can be changed appears.

10 Install SNMP service.

1. Execute the following command (case-sensitive).

>start /w ocsetup SNMP-SC

2. Execute the following command to check that SNMP is installed properly.

>oclist | findstr SNMP

When the following message is displayed, it is installed properly.

Installed: SNMP-SC

82






Install the Fibre Channel Driver using the PRIMERGY Startup Disc. For details, refer to "4.4

Installing the Fibre Channel Driver" (�pg.94).

13 Install the ServerView Agent.

For the procedure for installing, refer to "ServerView User's Guide (For Windows Agent)".

� For Windows Server 2008 Server Core, ServerView Console and ServerView RemoteCon-

trolService cannot be installed. Another system is required for installation.




(�pg.42).







The installation of Windows Server 2008 Server Core is completed.




83


4.2.3 Installing Windows Server 2003 x64



Prepare the necessary drivers before installing Windows Server 2003 x64.

Some drivers are created from the PRIMERGY Startup Disc, or download file from the Fujitsu

PRIMERGY website (http://primergy.fujitsu.com). For details about how to create driver disks,

refer to "4.1 Creating Driver Disks" (�pg.70).




3 Turned on the Server Blade and configure RAID. If RAID is not required to be

configured, proceed to step 4.

Turn on the server to display the following message and press the [Ctrl] + [C] key to start up the

BIOS Utility.




4 Insert the Windows Server 2003 x64 CD/DVD (installation disc).

Turn on the Server Blade after checking there are no floppy disks in the floppy disk drive, and

insert the Windows Server 2003 x64 CD/DVD immediately into the CD/DVD drive. When the

active area is specified on the hard disk, the following message appears.

Pressing any key while this message is displayed boots the system from the CD/DVD.

5 After the [Windows Server 2003 x64 Setup] window appears, press the [F6]

key.

Immediately, the following message appears at the bottom of the window. Press the [F6] key.

� This message will be displayed for a short time after the setup window (blue screen) appears.

Press the [F6] key immediately after the window turns blue.


Press any key to boot from CD...

Press F6 if you need to install a third party SCSI or RAID driver...


84


6 Install the Drivers for onboard array controller manually.

1. When the following message appears, press the [S] key.

2. When the "Please insert the disk labeled Manufacturer-supplied hardware support

disk into Drive A:" message appears, insert the driver disk created from the driver’s

CD and press the [Enter] key.

The following message appears.

3. Select following item and press the [Enter] key.


5. Follow the instructions in the window to perform installation

The message which prompts you to set the floppy disk appears during the installation, insert

the driver disk and push the [Enter] key.

7 Follow the instructions from the setup program to continue the installation

procedures.

If a message indicating that the driver has failed in the Windows logo test for validating the

compatibility with Windows appears, select [Yes] to continue the installation procedure.

8 Install the ChipSet driver.

1. Insert the PRIMERGY Startup Disc into the drive of the server.

When the ServerStart window appears, exit ServerStart.

2. Execute the following command on the PRIMERGY Startup Disc.

[CD/DVD drive]: \DRIVERS\ChipSet\Intel\5000P\infinst_autol.exe

The installation wizard starts up.

3. Click [Next]. Follow the instructions in the window to perform installation.

4. When the "InstallShield® wizard has completed" message appears, eject the

PRIMERGY Startup Disc from the CD/DVD drive and click [Finish] to restart the

system.

To specify additional SCSI adapters, CD-ROM drives, or special disk

controllers for use with Windows, including those for which you

have a device support disk from a mass storage device manufacturer,

press S.

You have chosen to configure a SCSI Adapter for use with Windows,

using a device support disk provided by an adapter manufacturer.

Select the SCSI Adapter you want from the following list, or press

ESC to return to the

previous screen.

LSI Logic Fusion-MPT SAS Driver(Server 2003 x64)

The driver you provided seems to be newer than the Windows default

driver.

85






[CD/DVD drive]: \DRIVERS\VIDEO\ES1000\Setup.exe



4. When the installation is completed, eject the PRIMERGY Startup Disc from the CD/

DVD drive and click [Finish] to restart the system.






using the PRIMERGY Startup Disc. For details, refer to "4.4 Installing the Fibre Channel Driver"

(�pg.94).







(�pg.42).







The installation of Windows Server 2003 x64 is completed.




86


4.2.4 Installing Windows Server 2003


Prepare necessary drivers before installing Windows Server 2003.

Some drivers are created from the PRIMERGY Startup Disc. For how to create driver disks, refer

to "4.1 Creating Driver Disks" (�pg.70).




3 Turned on the Server Blade and configure RAID. If RAID is not required to be

configured, proceed to step 4.

Turn on the server to display the following message and press the [Ctrl] + [C] key to start up the

BIOS Utility.




4 Insert the Windows Server 2003 CD/DVD.

Turn on the Server Blade and insert the Windows Server 2003 CD/DVD immediately into the

CD/DVD drive. Check there are no floppy disks in the floppy disk drive. When the active area is

specified on the hard disk, the following message appears.

Pressing any key while this message is displayed boots the system from the CD/DVD.

5 The [Windows Server 2003 Setup] window appears.

Immediately, the following message appears at the bottom of the window. Press the [F6] key.

� This message will be displayed for a short time after the setup window (blue screen) appears.

Press the [F6] key immediately after the window turns blue.


Press any key to boot from CD...

Press F6 if you need to install a third party

SCSI or RAID driver...

87


6 Install the Drivers for onboard array controller manually.


2. When the "Please insert the disk labeled Manufacturer-supplied hardware support

disk into Drive A:" message appears, insert the driver disk created and press the

[Enter] key.

The following message appears.

3. Select following item and press the [Enter] key.


5. Follow the instructions in the window to perform installation

The message which prompts you to set the floppy disk appears during the installation, set

the driver disk and push the [Enter] key.

7 Follow the instructions from the setup program to continue the installation

procedures.

If a message indicating that the driver has failed in the Windows logo test for validating the

compatibility with Windows appears, select [Yes] to continue the installation procedure.

8 Apply Windows Server 2003 Service Pack.

For details, refer to the description in the window.

9 Install the ChipSet driver.



2. Execute the following command on the CD/DVD.

[CD/DVD drive]: \DRIVERS\ChipSet\Intel\5000P\infinst_autol.exe



4. When the "InstallShield® wizard has completed" message appears, eject the

PRIMERGY Startup Disc from the CD/DVD drive and click [Finish] to restart the

system.

To specify additional SCSI adapters, CD-ROM drives, or special disk

controllers for use with Windows, including those for which you

have a device support disk from a mass storage device manufacturer,

press S.

You have chosen to configure a SCSI Adapter for use with Windows,

using a device support disk provided by an adapter manufacturer.

Select the SCSI Adapter you want from the following list, or press

ESC to return to the

previous screen.

LSI Logic Fusion-MPT SAS Driver(Server 2003 32-bit)

The driver you provided seems to be newer than the Windows default

driver.

88






[CD/DVD drive]: \DRIVERS\VIDEO\ES1000\Setup.exe


3. Click [Next]. Follow instructions in the window to perform installation.

When the installation is completed, the completion window appears.

4. Eject the PRIMERGY Startup Disc from the CD/DVD drive, click [Finish], and

restart the system.


Use the PRIMERGY Startup Disc to install the LAN driver. For more details, refer to "4.3

Installing the LAN Driver" (�pg.89).



using the PRIMERGY Startup Disc. For details, refer to "4.4 Installing the Fibre Channel Driver"

(�pg.94).







(�pg.42).







The installation of Windows Server 2003 has completed.




4.2.5 Installing Linux

For the use of Linux, refer to the Fujitsu PRIMERGY website (http://primergy.fujitsu.com).


89


4.3 Installing the LAN Driver

This section explains the procedure for installing the driver.

� For the latest drivers, refer to the Fujitsu PRIMERGY website (http://primergy.fujitsu.com).

4.3.1 Installing the LAN Driver

Perform the following procedures to install the LAN driver. The procedures are the same for the full

installation and the Server Core installation.

� For Windows Server 2008 (32-bit)

� For Onboard LAN

1 Insert the PRIMERGY Startup Disc.

2 Execute the following file.

\DRIVERS\LAN\Broadcom\Onboard\w2k8\setup.exe

3 Click [Next].

4 Select [I accept the license agreement] and click [Next].

5 Click [Install].

Driver installation starts.

6 Click [Finish].

7 Eject the PRIMERGY Startup Disc and restart the Server Blade.

� For Eth. Ctrl 2x1Gbit PCI-E 1000-BASE-T lp (PG-2861L)



\DRIVERS\LAN\Intel\APPS\PROSETDX\Vista32\DxSetup.exe

The message "Welcome to InstallShield Wizard for Intel® Network Connection" is displayed.

Proceed with the installation by following the instructions displayed in the window.

Also, only check the following for program functions to be installed on the [Setup Options]

window. For Server Core system, only drivers can be installed.

• Driver


90


• Intel® PROSet for Windows device manager

• Advanced Network Service

� For 1Gbit/s Ethernet I/O Module (PG-LND201)



\DRIVERS\LAN\Broadcom\Ext\w2k8\setup.exe

3 Click [Next].

4 Select [Modify], and click [Next].

5 Click [Next].

6 Click [Install].


7 Click [Finish].


� For Windows Server 2008 (64-bit)

� For Onboard LAN



\DRIVERS\LAN\Broadcom\Onboard\w2k8x64\setup.exe

3 Click [Next].


5 Click [Install].


6 Click [Finish].


91





\DRIVERS\LAN\Intel\APPS\PROSETDX\Vistax64\DxSetup.exe

The message "Welcome to InstallShield Wizard for Intel® Network Connection" is displayed.


Also, only check the following for program functions to be installed on the [Setup Options]

window. For Server Core system, only drivers can be installed.

• Driver

• Intel® PROSet for Windows device manager

• Advanced Network Service




\DRIVERS\LAN\Broadcom\Ext\w2k8x64\setup.exe

3 Click [Next].

4 Select [Modify], and click [Next].

5 Click [Next].

6 Click [Install].


7 Click [Finish].



� For Onboard LAN



\DRIVERS\LAN\Broadcom\Onboard\DrvInst\x64\setup.exe

3 Click [Next].


4 Click [Finish].

92






\DRIVERS\LAN\Intel\APPS\PROSETDX\Winx64\DxSetup.exe

The message "Welcome to InstallShield Wizard" is displayed.


Also, only select [Drivers, Intel® PROSet, and Advanced Network Services] for program

functions to be installed.




\DRIVERS\LAN\Broadcom\Ext\W2K3x64\DrvInst\setup.exe

3 Click [Next].


4 Click [Finish].



� For Onboard LAN



\DRIVERS\LAN\Broadcom\Onboard\DrvInst\IA32\setup.exe

3 Click [Next].


4 Click [Finish].


93





\DRIVERS\LAN\Intel\APPS\PROSETDX\Win32\DxSetup.exe

The message "Welcome to InstallShield Wizard" is displayed.


Also, only select [Drivers, Intel® PROSet, and Advanced Network Services] for program

functions to be installed.




\DRIVERS\LAN\Broadcom\Ext\W2K3\DrvInst\setup.exe

3 Click [Next].


4 Click [Finish].


94


4.4 Installing the Fibre Channel Driver

This section explains how to install a fibre channel driver when the 2Gbit/s FC I/O

Module (PG-FCD102) is extended.

When 4Gbit/s FC I/O Module (PG-FCD201) is extended, refer to the option manual.

� The latest drivers, refer to the Fujitsu PRIMERGY website (http://primergy.fujitsu.com).

4.4.1 For Windows Server 2008

� For Windows Server 2008 (Full installation)

1 Click [Start] – [All Programs] – [Administrative Tools] – [Computer

Management].

2 Click [Device Manager].

Two fiber channel adapters of the 2Gbit/s FC I/O Module are displayed with the name below.

• [QLogic Fibre Channel Adapter] under [Storage controllers]

Double-click the fibre channel controller and perform the following Steps 3 to 12 on all fibre

channel ports.

3 Double-click the icon or name of the fibre channel controller.

The properties window appears.

4 Insert the PRIMERGY Startup Disc into the server.

5 Click the [Driver] tab and click [Update Driver].

The [Update Driver Software] window appears.

6 Select [Browse my computer for driver software].

7 Select [Let me pick from a list of device drivers on my computer].

8 Click [Have Disk].


95


9 Enter the following folder name in [Copy manufacturer's files from] and click

[OK].

• Windows Server 2008 (32-bit)

[CD/DVD drive]: \DRIVERS\FCD\Qlogic\W2K8

• Windows Server 2008 (64-bit)

[CD/DVD drive]: \DRIVERS\FCD\Qlogic\W2K8x64

10 Click [Next].


11 Click [Close].

Detected drivers are displayed.

12 Click [Close].

� For Windows Server 2008 (Server Core installation)


2 Move to the directory where the driver is stored using command prompt, and

execute the following command.

>pnputil -i -a ql2x00.inf

3 The following message is displayed.

<x> differs depending on the installation order.

Processing inf : ql2x00.inf

Successfully installed the driver on a device on the system.

Driver package added successfully.

Published name : oem<x>.inf

96



1 Click [Start] – [Programs] – [Administrative Tools] – [Computer Management].

2 Click [Device Manager].

Two ports of the fibre channel, which is installed in the 2Gbit/s FC I/O Module, are displayed

with the names below.

• [Fibre Channel Controller] under [Other Devices]

• [QLogic Fibre Channel Adapter] under [SCSI and RAID controller]

Double-click these fibre channel controllers and perform the following Steps 3 to 12 on all

fibre channel ports.

3 Double-click the icon or name of the fibre channel controller.

The properties window appears.


5 Click the [Driver] tab and click [Update Driver].

The [Welcome to the Hardware Update Wizard] window appears.

6 Select [Install from the list or specified location] and click [Next].

7 Select [Not searching, and select installation driver], and click [Next].

8 Click [Have Disk].

9 Enter the following folder name in [Copy files from manufacture] and click [OK].

• Windows Server 2003 x64

[CD/DVD drive]: \DRIVERS\FCD\Qlogic\W2K3x64

• Windows Server 2003

[CD/DVD drive]: \DRIVERS\FCD\Qlogic\W2K3

10 Click [Next].


11 Click [Finish].

Detected drivers are displayed.

12 Click [Exit].

97


4.5 Installing SAS RAID Ctrl Driver

This section explains how to install a driver when adding SAS RAID Ctrl (PG-248EL).

Use the PRIMERGY Array Controller Document & Tool disk to install (update) the SAS RAID Ctrl

driver.


98


99

Chapter 5

Operations after OS Installation

This chapter explains the operations to be

performed after OS installation. Be sure to

perform these operations before operating the

server.

5.1 Memory Dump/Paging File Setting . . . . . . . . . . . . . . . . . . 100

5.2 Creating Backup Data for System Recovery . . . . . . . . . . . 107

5.3 Storing the System Setting Information . . . . . . . . . . . . . . 110

5.4 Creating Maintenance Tools . . . . . . . . . . . . . . . . . . . . . . 113

5.5 Notes Before Operating the Server . . . . . . . . . . . . . . . . . 117

5.6 LAN Driver Advanced Setup [BACS] . . . . . . . . . . . . . . . . 123

5.7 LAN Driver Advanced Setup [Intel® PROSet] . . . . . . . . . . 151

100


5.1 Memory Dump/Paging File Setting

Before start operating this server, configure the setting for obtaining memory dump.

The setting procedure varies between Windows Server 2003 and Windows 2000

Server.

� Memory dump

If memory dump is set, debugging information will be automatically saved when a STOP error (fatal

system error) occurs in the system. Using the saved memory dump, error cause can be analyzed.

If the amount of installed memory is large, pay special attention when setting the memory dump file.

The settings for obtaining memory dump should be configured after installing the files to be used for

operations (OS, applications, etc.).

5.1.1 How to Obtain Memory Dump

Check the following settings before starting configuration to obtain memory dump.

� Checking hard disk free space

To obtain memory dump, sufficient hard disk capacity is required for creating paging files and memory

dump files.

The obtainable dump types and required hard disk capacity are as follows:

� Complete memory (full) dump (recommended)

When the system unexpectedly stops, contents of the whole system memory are recorded. The file is

stored in the directory displayed in the [Dump file] box.

• Paging file: Installed physical memory + 11MB (Recommended: Installed physical memory × 1.5)

• Memory dump file: Same amount as installed physical memory

� When collecting a complete memory dump on a computer where there is 2GB or more of memory

installed, use the registry editor to set the registry as follows.

For details, refer to Microsoft information (http://support.microsoft.com/kb/274598/).

HKEY_LOCAL_MACHINE¥SYSTEM¥CurrentControlSet¥Control¥CrashControl-

CrashDumpEnabled = 1 (complete memory dump)

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

101


� Kernel memory dump

Information of only kernel memory space is recorded. The file is stored in the directory displayed in the

[Dump file] box. Capacity required for kernel memory dump is as follows:

• Paging file: Depending on installed physical memory amount

For memory of 256 to 1,373MB - Installed physical memory × 1.5

For memory of 1,374MB or more - 32-bit system: 2GB + 16MB

For 64-bit system - RAM size + 128MB

• Memory dump file: Depending on the used amount of kernel-mode address space during STOP

� Minimum memory dump

Minimum amount of useful information for problem identification is recorded. If this option is specified,

a new file is created each time the system unexpectedly stops.

History of such files is stored in the directory displayed in [Small dump directory].

• Paging file: 2MB or more

• Memory dump file: 64KB or 128KB

� Memory dump file setting

Set up the memory dump file according to the following procedures:

1 Log on to the server with administrator privileges.

2 Check free space of the drive where the memory dump file is to be stored.

Check the required amount of free space according to "� Checking hard disk free space"

(�pg.100).

If the drive has no free space, refer to "� Cannot collect the memory dump" (�pg.240).

3 Display the [System Properties] window.


1. Click [Start] – [Control Panel].

Control Panel appears.

2. Double-click the [System] icon.

System Control Panel appears.

3. Select [Advanced system settings] from the tasks.

The [System Properties] window appears.


1. Click [Start] – [Control Panel] – [System].


102


4 Click the [Advanced] tab and click [Settings] in [Startup and Recovery].

The [Startup and Recovery] window appears.

5 Perform the following setting procedures.

1. In the [Write debugging information] section, select the memory dump file type.

• Complete memory dump (Recommended)

The whole system memory information is recorded to the memory dump file.

• Small memory dump (64KB)

Minimum information is recorded to the memory dump file.

Each time a fatal error occurs, a new file is created in the directory specified in [Small

dump directory].

• Kernel memory dump

Only kernel memory is recorded to the memory dump file.

2. In [Dump file] or [Small dump directory], specify the directory to save the memory

dump file, with its full path.

In case of kernel memory dump or complete memory dump, if [Overwrite any existing file]

is checked, debugging information is overwritten to the specified file every time.

6 Click [OK] to close the [Startup and Recovery] window.

7 Click [OK] to close the [System Properties] window.


The setting is enabled after the system is restarted.

103


� Paging file setting

Set up the paging file according to the following procedures:


2 Check free space of the drive where the system is installed.

Check the required amount of free space according to "� Checking hard disk free space"

(�pg.100).

If the drive has no free space, refer to "� Cannot collect the memory dump" (�pg.240).

3 Display the [System Properties] window.


1. Click [Start] – [Control Panel].

Control Panel appears.

2. Double-click the [System] icon.

System Control Panel appears.

3. Select [Advanced system settings] from the tasks.



1. Click [Start] – [Control Panel] – [System].


4 Click the [Advanced] tab and click [Settings] in [Performance].

The [Performance Options] window appears.

104


5 Click the [Advanced] tab.



105


6 Click [Change] in the [Virtual memory] section.

The [Virtual Memory] window appears.


� If [Automatically manage paging file size for all drivers] is checked, uncheck it.


7 Specify the drive where the paging file is to be created.

In [Drive], select the drive where the system is installed.

The selected drive is displayed in [Drive] in [Paging file size for selected drive].

106


8 Select [Custom size] and enter a value in [Initial size].

The value depends on the type of the set dump file.

Specify a value larger than the value shown in [Recommended] in [Total paging file size for all

drives].

� When a smaller value is specified for the paging file size, performance may be affected. For

maximum system efficiency, be sure to set [Initial size] with a value larger than the [Recom-

mended] size described in [Total paging file size for all drives]. The recommended size is total

memory installed in the system x 1.5. However, if a program consuming a large amount of

memory is regularly used, set a larger size as required.

9 Enter a value in [Maximum size].

Specify a value larger than the [Initial size].

10 Click [Set].

The settings are saved, and the value specified is displayed in [Paging File Size] of [Drive].

11 Click [OK] to close the [Virtual Memory] window.

12 Click [OK] to close the [Performance Options] window.

13 Click [OK] to close the [System Properties] window.



� Rebooting after OS dump setting

Rebooting may not be executed when the server fails even if rebooting has been set after obtaining

dumping.

Immediate provision may be required when the server fails. However, configure the settings of

rebooting with the Watchdog, when continuous operation is required. For details and configuration

procedures for the software, the Watchdog, refer to "3.4 Serious Error Handling (ASR)" in "ServerView

User’s Guide".

107


5.2 Creating Backup Data for System Recovery

After OS installation is complete, create backup data for system recovery, which

enables the system to be recovered if en error occurred.

� When store the backup data in a floppy disk or CD/DVD, use the Display/USB Extension Cable to

connect the USB floppy disk drive or USB CD/DVD drive. For more information on the connection

procedure, refer to "Start Guide".

� After OS installation or changing the system configuration, make sure to perform this procedure to

create backup data.

5.2.1 Windows Server 2008

When installing Windows Server 2008, backup whole server configuration to media such as a shared

folder or DVD.

Windows Server backup function

� For Windows Server 2008, backup and restoration of the whole system can be performed using the

[Windows Server Backup] function.

After installation, perform a full backup for the whole system configuration only once. Incremental

backup can be specified to be automatically performed to only store changed data. Set or operate it

according to the operation configuration.

� Windows Server backup does not support a tape device. When using a tape device, use software for

tape backup.

� If setting up Windows Server 2008 Server Core, backup via the MMC console and Windows

PowerShell are not supported. Only command line (Wbadmin command) backup is supported.

� Installing a backup component

In Windows Server 2008 default settings, backup components are not installed. Install it in advance.

1 Click [Start] – [Administrative Tools] – [Server Manager].

Server Manager starts.

2 Check [Windows Server Backup Features] in [Add Features] to install.

108


� Creating backup data

Perform backup for the whole server configuration according to the following procedure.

1 Click [Start] – [Administrative Tools] – [Windows Server Backup].

2 Select [Backup Once] from the operation menu.

3 Select [Full server] in [Select backup configuration].

4 Select [Remote shared folder] in [Specify destination type].

� Specify a shared folder or DVD drive on a server other than the device's server as a backup

destination.

5 Select the options as required, and start backup.

When backup has completed, the status (succeeded or failed) is displayed in the message part of

the [Windows Server Backup] window.

5.2.2 Windows Server 2003

When installing Windows Server 2003, create the Automated System Recovery (ASR) set. To create it,

an unused formatted floppy disk and media to store the backup file are required.

� Only system information can be restored by using the Automated System Recovery (ASR) set that is

created in this procedure. Data such as files created by customers are not included. Regular data

backup using a backup device is recommended. For backup, refer to "9.5 Backup" (�pg.251).

1 Click [Start] – [All Programs] – [Accessories] – [System Tool] – [Backup].

The [Backup or Recovery Wizard] window appears.

2 Click [Next].

The [Backup or Recovery] window appears.

3 Select [Create a backup of files and settings], and then click [Next].

The [Items to Create Backups] window appears.

4 Select [All the information in this computer], and then click [Next].

The [Backup Type, Destination and Name of the Backup File] window appears.

5 Enter a name and a destination for the backup file, and then click [Next].

The [Backup or Recovery Wizard Complete] window appears.

109


6 Click [Finish].

Backup process starts.

7 If a message prompts you to insert a floppy disk, insert the floppy disk and click

[OK].

Automated system recovery disk is created.

8 When the process is completed, a message appears. Eject the floppy disk

according to the message and put a label on it.

Label example: Windows Automated System Recovery Disk: Backup.bkf, Created at 12:00 04/

01/2003

9 Click [OK] to exit [Backup Utility].

10 Click [Close] to close the [Backup Progress] window.

An automated system recovery set has been created.

Store the automated system recovery set just created just in case.

110


5.3 Storing the System Setting Information

Before starting operations, store the configuration information of the BIOS Setup

Utility. By storing this information, the system can be recovered with the stored

information in case of a system failure (such as when the information is deleted due

to the drain of the built-in battery). Use Server Management Tools for storing and

recovering the system configuration information.

� The Management Blade has the similar function, which collectively manages the backup of multiple

Server Blade setting information items.

For details, refer to "BX600 Management Blade Hardware Guide".

� Since the system configuration information is significant in maintaining the server, be sure to store the

BIOS information after the following operations. In addition, save the stored data.

• When the information is changed with the BIOS Setup Utility

• When the hardware configuration of this server is changed (e.g. a CPU, memory, internal hard disk

unit or expansion card is added, removed or changed)

� As the stored system configuration information will be used during maintenance, etc., send it to your

maintenance personnel.

� Preparation for using Server Management Tools

Use the Display/USB Extension Cable to connect to the USB floppy disk drive to the Server Blade.

For the procedure to create "Server Management Tools" disk, refer to "5.4.2 Creating "Server

Management Tools" Disk" (�pg.116)

� Cautions

• Server Management Tools are for this Server Blade only. Do not use those tools on other systems. If

they are used, the system can be damaged.

• Only the information that is configured with the BIOS Setup Utility can be stored/recovered with

Server Management Tools. The BIOS information in internal RAID devices cannot be stored/

recovered.

• Make sure to start up the Server Blade with the "Server Management Tools" disk before running

Server Management Tools. Do not run Server Management Tools on the server started from the hard

disk or by the other floppy disks. Otherwise, the system may be corrupted.

• Do not eject a floppy disk while the floppy disk access LED is on. Such an action may lead not only

to corruption of the floppy disk data but also an unstable state of the system.

• If an error message appears while running Server Management Tools, respond to the message

according to "� Server Management Tools error messages" (�pg.236).

111


5.3.1 How to Store the BIOS Information with Server Management Tools

Store the BIOS information according to the following procedures:

� Before operating, if the ServerView "OS Boot Monitoring" function is enabled, disabled it (it is

"Disabled" by default).

If you start up the system while the "OS Boot Monitoring" function remains effective, the operation of

the server may become unpredictable at such times as an abrupt power interruption or restart.

If it is necessary to operate the server with the "OS Boot Monitoring" function enabled, enable the

function after storing the BIOS information.

For details of ServerView, refer to "ServerView User's Guide".

1 Turn on the server and insert the "Server Management Tools" disk into the

floppy disk drive.

The window for selecting a keyboard appears.

2 Select a keyboard.

Select "1" for the Japanese keyboard or "2" for the English keyboard. The Japanese keyboard is

selected by default.

3 When the DOS prompt window appears, enter the following command and

press the [Enter] key.

A:\SMT>read.bat

� If storing has already been performed with Server Management Tools, the stored file must exist

in the floppy disk. In this case, overwriting the file may lead to incompletion of BIOS information

recovery. Move the file to another floppy disk, rename the file, or delete it by executing the fol-

lowing command.

A:\SMT\>deldat.bat [Enter]

4 If the BIOS information is stored correctly, the following message appears.

5 Check that the storing information file is created.

Enter the following command and press the [Enter] key.

A:\SMT\>dir

Check that "SAVECMOS.BIN" and "nvram.enu" are created.

Storing procedure is completed. The server can now be turned off safely.

Please select:

1 = JP Keyboard

2 = US Keyboard

Your selection

NORMAL END

112


5.3.2 How to Recover the BIOS Information with Server Management Tools

If the information configured with the BIOS Setup Utility was deleted due to a drain of the built-in

server battery, etc., restore the BIOS information according to the following procedures:

� Do not turn off the server during a program run.

� Before starting the system, if the ServerView "OS Boot Monitoring" function is enabled, disable it (it is

"Disabled" by default).

If you start up the system while the "OS Boot Monitoring" function remains effective, the operation of

the server may become unpredictable at such times as an abrupt power interruption or restart.

If the server is operated with the "OS Boot Monitoring" function enable, enable the function again

before resuming operation. For details of ServerView, refer to "ServerView User's Guide".


floppy disk drive.







A:\SMT\>dir

Check that BIOS save information files "SAVECMOS.BIN" and "nvram.enu" are stored in the

floppy disk.

4 Enter the following command and press the [Enter] key to recover BIOS

information.

A:\SMT\>write.bat

5 If the BIOS information is recovered correctly, the following message appears.

6 The BIOS information will be enabled after the next system restart. Restart the

server.

Perform Step 1 to display the DOS prompt window. The recovery procedure has been completed.

The server can now be turned off safely.

Please select:

1 = JP Keyboard

2 = US Keyboard

Your selection

NORMAL END

113


5.4 Creating Maintenance Tools

This section explains how to create tools for maintaining the server.

Maintenance tools are created with the FloppyBuilder function of ServerStart.

With the FloppyBuilder function of ServerStart, you can create the following tools:

• "Server Management Tools" disk

• DOS floppy disks

The FloppyBuilder can be used under environments such as:

• the ServerStart system started on a client computer (recommended)

• the system started on the server using the PRIMERGY Startup Disc

� When creating the tools on a client computer, install ServerStart on the computer beforehand.

If ServerStart of a different version is installed in the computer, make sure to uninstall the ServerStart.

Then perform installation again. For details on how to uninstall ServerStart, refer to "� Uninstalling

ServerStart" (�pg.115).

5.4.1 Installing ServerStart

Install ServerStart on a client computer when creating a drive disk using FloppyBuilder function.

� System requirements for client computers

Client computers must satisfy the following requirements.

Using ServerStart on the server

� ServerStart can be installed to the server, Windows Server 2008 (32-bit) or Windows Server 2003

employed. Install ServerStart in accordance with this chapter.

Note that ServerStart is not available to the server where Windows Server 2008 (64-bit) or Windows

Server 2003 x64 is installed.

1 Insert the PRIMERGY Startup Disc into the client computer.

The [PRIMERGY Startup Disc] window appears.

Hardware Personal computers operated with Windows Vista or Windows XP Professional

(A DVD drive and minimum 10MB free disk space are required.)

Software Microsoft® Internet Explorer 5.5 or later

114


2 Click [ServerStart Vn.nnn].

The ServerStart version currently being used is displayed in "Vn.nnn".

The [Fujitsu Siemens ServerStart] window appears.

� The massage "Do you want to run or save this file?" may appear depending the OS in use. Fol-

low as below.

1. Click [Run].

A massage appears that "The publisher could not be verified. Are you sure you want to

run this software?"

2. Click [Run].

Execute "SeStSetup.exe" in the disk when [Fujitsu ServerStart Setup] window is not

displayed.

3 Check the checkbox of [Classic] only and click [OK].

The Setup window appears.

4 Click [Next].

The [License Agreement] window appears.


The [User Information] window appears.

115


6 Enter the user information of the software and click [Next].

The [Destination Folder] window appears.

7 Specify the installation folder and click [Next]. To change the installation folder,

click [Browse] and select the folder.

The [Ready to Install the Application] window appears.

8 Click [Next].

Installation is executed.

� If a message prompts you to restart the system before or after installation, eject the disc and

restart the system according to the message. When the system restarts, insert PRIMERGY

Startup Disc and start installation again.

If the "This program does not respond." message appears during restart operation, click [Exit]

to continue the restart operation.

When the installation is completed, the completion window appears.

9 Click [Exit].

ServerStart has been installed to the client computer.

� Uninstalling ServerStart

Uninstall ServerStart on the client computer according to the following procedure when necessary.

1 Click [Start] – [All Programs] – [Fujitsu Siemens ServerStart] – [Uninstall

ServerStart].

2 Click [OK].

When the uninstallation is executed successfully, ServerStart is deleted.

116


5.4.2 Creating "Server Management Tools" Disk

Start up ServerStart and confirm that the FloppyBuilder window is displayed.

1 Click [Server Management Tools].

2 Click the tool to be created.

Insert the prepared floppy disk by following the message.



The respective tools will be created automatically. When a message appears indicating that the

disk is created, click [OK] and eject the disk.

4 Fill the following items on the label of the floppy disk.

• The model of the server

• Version and Level of the Server Management Tools

• Date of the floppy disk created

5.4.3 Creating a DOS Floppy Disk

For DOS data stored into the floppy disk, refer to the file in the following folder of the PRIMERGY

Startup Disc.

[CD/DVD drive]: \FreeDOS

To create a DOS floppy disk, you need an unused floppy disk. Prepare it in advance.

1 Click [FloppyBuilder].

For details on procedures for starting up ServerStart, refer to "� Starting ServerStart" (�pg.72).

2 Click [DOS Diskette].

Insert the prepared floppy disk by following the message.



The DOS floppy disk will be created automatically.

When a message appears indicating that creating the disk is completed, click [OK] and eject the

disk.

117


5.5 Notes Before Operating the Server

This section explains the settings required before starting to operate the server.

For details on the settings, refer to the following URL.

http://www.microsoft.com/technet/prodtechnol/exchange/2003/Library/default.mspx

� If a LAN card or 1 Gbit/s Ethernet I/O Module was added, install a driver according to "4.3 Installing the


� To connect optional SCSI devices, refer to "Chapter 7 Installing Internal Options" (�pg.171).

� For the settings for the installed High Reliability Tools, refer to "Chapter 6 High Reliability Tools"

(�pg.163) and the manuals of each application.

� For notes on ServerView security, refer to "Security" in "1.1.7 Note" in the "ServerView User's Guide".

5.5.1 Auto-run Function from CD/DVD Drives

Perform the following procedures to change the settings of the auto-run function from the CD/DVD

drives after server installation:

1 Make the registry editable, and change the value of AutoRun of the following

registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\CDRom

To enable auto-run, set the value of AutoRun to "1", and to disable auto-run, set the value to "0".



5.5.2 Drive Letter Assignment in Expert Mode

In expert mode, you cannot specify a drive letter to a particular partition arbitrarily. Drive letters

specified with Disk Manager in expert mode will be sequentially assigned from the first partition with

"C, D, E..." when installation is completed, and an unused drive letter will be assigned to the CD-ROM

drive.

To change the drive letter, perform the following procedures after installation.

� You cannot change the drive letters for the system and boot drive.

http://www.microsoft.com/technet/prodtechnol/exchange/2003/Library/default.mspx

118



1 Click [Start] – [Administrative Tools] – [Computer Management].

2 Click [Disk Management].

3 Right-click the partition to change the letter and click [Change Drive Letter and

Path].

The [Change Drive Letter and Path] window appears.

4 Click [Edit].

The [Change Drive Letter or Path] window appears.

5 Change the drive letter.

5.5.3 Notes on Advanced Uninterruptible Power Supply (UPS)

Note the following points when using an advanced uninterruptible power supply (referred to as UPS

afterward).

� UPS shutdown time setting

Specify enough time for the UPS power-off time (time from the shutdown direction to the actual power-

off). If this time is set insufficiently, the power will be cut off before system shutdown, which may result

in destruction of data. For more details, refer to the manuals for UPS and UPS management software.

� Power supply control by UPS

The following settings are required to power the server on automatically using the UPS management

software (PowerChute Network Shutdown, PowerChute Business Edition) at power recovery or during

scheduled operation. For details, refer to the manuals for UPS and UPS management software.

1 Start ServerView, and click [Recovery] – [ASR] in the [ServerView] window.

The [ASR] window appears.

2 Click the [Restart Settings] tab and set [Action After Power Failure] to [Always

Restart Server].

For details of the setting procedure, refer to "3.4 Serious Error Handling (ASR)" in "ServerView

User's Guide".

119


5.5.4 Using Network Startup (PXE)

The Server Blade obtains a boot image via network, and supports PXE (Preboot eXecution

Environment) to be booted.

For more details on setting, refer to "� Booting the Server Blade with PXE" (�pg.37).

� Be sure to install ServerView to control the power supply via a LAN.

� When booting the Server Blade with PXE, turn on the Server Blade power one minute or more after the

main power of the Chassis was turned on. Turning on the Server Blade power just after the main

power was turned on may cause PXE not to boot due to the Switch Blade not having been started.

� The PXE boot function is not available for the LAN port of the 1 Gbit/s Ethernet I/O Module.

5.5.5 Changing the system drive size (only for Windows Server 2008)

For Windows Server 2008, the partition size can be extended or reduced after installation has completed.

� Extending the partition size of a system drive

To extend the partition size of a system drive, perform the following procedure.


2 Click [Start] – [All Programs] – [Administrative Tools] – [Server Manager].


3 Double-click [Storage] – [Disk Management].

The [Disk Management] window appears.

4 Right-click the volume to be extended in [Disk Management], and click [Extend

Volume].

The [Welcome to the Extend Volume Wizard] window appears.

120


5 Click [Next].

The [Select Disks] window appears.

6 Specify the desired size in [Select the amount of space in MB].

� The total value of the current partition size and the value that is specified in [Select the amount

of space in MB] is displayed in [Total volume size in megabytes (MB)]. Specify the value so that

the total of the volume sizes becomes a partition size to be created.

� The maximum value that can be specified in [Select the amount of space in MB] is displayed in

[Maximum available space in MB].

7 Click [Next].

The [Completing the Extend Volume Wizard] window appears.

8 Check the disk size and click [Finish].


9 Click [Exit] in the [File] menu.

Server Manager finishes.

� Reducing the partition size of system drive

When reducing the partition size of system drive, perform the following procedures.


2 Click [Start] – [All Programs] – [Administrative Tools] – [Server Manager].


3 Double-click [Storage] – [Disk Management].


121


4 Right-click the volume to be reduced, and click [Shrink Volume].

The [Shrink <Selected volume>:] window appears.

� Size of available shrink space can be restricted if snapshots or pagefiles are enabled on the

volume.

5 Specify the desired size in [Enter the amount of space to shrink in MB].

� The partition size after changing is displayed in [Total size after shrink in MB].

Specify the value so that the total size after reduction becomes the desired partition size.

� The maximum value that can be specified in [Enter the amount of space to shrink in MB] is dis-

played in [Size of available shrink space in MB].

� Click [Shrink] to start the shrinking process. Make sure to check whether the proper value is

specified in [Total size after shrink in MB] before clicking [Shrink].

6 Click [Shrink].

Shrinking is executed, the [Disk Management] window appears.

7 Click [Exit] in the [File] menu.

Server Manager finishes.

122


5.5.6 Other Notes on Operation

� Unnecessary files

After OS installation is completed, folders named Runonce and Runonce 2 may be left in the drive

where the OS is installed. Delete these folders since you do not need them for the system operation.

� Notes on 24-hour operation

� Automated system operation

To provide an extra margin of safety against unintentional damage, introduce disaster-prevention

measures in the office and keep disaster prevention personnel (such as a security guard or janitor) in the

building.

� Unintentional power-off prevention

We recommend the installation of a special power supply device (such as a distribution board) to prevent

unplanned power shut-offs.

� Notes on KVM switch

• After the KVM switching, you may not be able to enter the first key entry using the keyboard. Enter

the key entry again.

• In the Windows or Linux system, if the KVM switch is operated while the [NumLock], [CapsLock],

and [ScrollLock] LEDs are on by pressing their keys on the keyboard connected to the Chassis, those

LEDs may go off. To return the LEDs lamps to the normal state, press the [NumLock], [CapsLock],

and [ScrollLock] keys again.

• If KVM switch is operated frequently during Linux booting, the keyboard or mouse may not be used

after booting, without being recognized. Reboot the server so that the keyboard or mouse will operate

properly. When either the keyboard or mouse cannot be used, log on remotely via the network, then

reboot the server.

• If KVM switching is frequently performed during Windows booting, the keyboard or mouse may be

recognized improperly, and i8042prt.sys may generate error logs in the event viewer system log. If

the keyboard and mouse operate properly, those logs can be ignored. If they do not operate properly,

restart the system and they will be recognized normally.

123


5.6 LAN Driver Advanced Setup [BACS]

BACS is an integrated GUI application consisting of programs such as BASP

(Broadcom Advanced Server Program) that provides the load balancing feature, etc.,

by teaming up multiple adapters.

BACS is used in the following situations:

• Create a Team using an onboard LAN and 1Gbit/s Ethernet I/O Module (PG-

LND201)

• Perform advanced setup for an onboard LAN and 1Gbit/s Ethernet I/O Module

(PG-LND201)

Use of Intel® PROSet

� Use Intel® PROSet (�pg.151) to perform the following setup for LAN cards (PG-2861L)

• Use the Teaming function between LAN cards (PG-2861L)

• Setup a VLAN using LAN cards (PG-2861L)

• Use the Jumbo frame using LAN cards (PG-2861L)

• Perform other advanced settings for LAN cards (PG-2861L)

5.6.1 BACS Installation

If [Broadcom Control Suite 2] or [Broadcom Control Suite 3] is not displayed in the [Control Panel],

install BACS according to the following installation procedures:


1 Execute the following file contained in the PRIMERGY Startup Disc.

For Windows Server 2008 (32-bit)

[CD/DVD drive]: \DRIVERS\LAN\Broadcom\Onboard\MgmtApps\w2k8\setup.exe


[CD/DVD drive]: \DRIVERS\LAN\Broadcom\Onboard\MgmtApps\w2k8x64\setup.exe

The installer starts up.

2 Click [Next].

License agreement window appears.

3 Select [I accept the terms in the license agreement] and click [Next].

Custom Set up window appears.

4 Check that [Control Suite] and [BASP] are selected, and click [Next].

Proceed with the installation by following the instructions in the window.

124




[CD/DVD drive]: \DRIVERS\LAN\Broadcom\Onboard\MgmtApps\x64\setup.exe


2 Click [Next].

License agreement window appears.

125


3 Click [I accept the terms in the license agreement] and click [Next].

Custom Set up window appears.

4 Click [Next].

Proceed the installation by following the window instructions.

126



� If the OS is installed using ServerStart, "BACS" is already installed with the driver. If the OS is installed

manually, BACS will not be installed.


[CD/DVD drive]: \DRIVERS\LAN\Broadcom\Onboard\MgmtApps\IA32\setup.exe


2 Proceed the installation by following the window instructions.

When the window below appears during the installation procedure, check [BASP] and click

[Next].

127


5.6.2 Teaming

In this Server Blade, teaming is possible with any Intel/Broadcom adapter.


� Creating a team

1 Log in with Administrator or same privileges.

2 Click [Start] – [All Programs] – [Broadcom] – [Broadcom Control Suite 3].

Broadcom Control Suite 3 starts.

3 Click [Team Management].

128


4 Click [Create a Team] in the [Teams] menu.

The [Welcome to the Broadcom Teaming Wizard] window appears.

5 Click [Next].

The [Creating/Modifying a Team: Team Name] window appears.

129


6 Enter a team name, and click [Next].

The [Creating/Modifying a Team: Team Name: Team Type] window appears.

7 Select the team type, and click [Next].

The following is an explanation for when selecting [Smart Load Balancing (TM) and Failover

(SLB)] as an example. The [Creating/Modifying a Team: Assigning Team Members] window

appears.

8 Select the adapter to be incorporated in the Team from the [Available Adapters]

list, and click [Add].

The selected adapter is added in the [Team Members] list.

130


9 Click [Next].

The [Creating/Modifying a Team: Designating a Standby Member] window appears.

10 Set for the standby member, and click [Next].

The [Creating/Modifying a Team: Configure LiveLink] window appears.

� Auto-Fallback can be selected when using the Team as a standby member.

� LiveLink does not support Auto-Fallback.

LiveLink detects loss of network connectivity beyond the switch and routes traffic only through

team members that have a live link.

131


11 Specify whether or not to configure LiveLink, and click [Next].

The operation varies between " When selecting [Yes]" (�pg.131) and " When selecting [No]"

(�pg.131).

When selecting [No]

The [Creating /Modifying a VLAN: Configure VLAN Support] window appears.

Go to Step 12.

When selecting [Yes]

The [Configure LiveLink(TM) attributes] window appears.

Perform the following procedure.

132


1. Enter values for the following setting items, and click [Edit Target IP Address...].

• Probe interval (seconds)

Specify the probe interval (seconds) between 1 to 60.

• Probe maximum retries

Specify the Probe maximum retries between 1 to 10.

• Probe VLAN ID

When setting tag VLAN for probe of LiveLink, specify the value between 0 to 4096.


2. Specify the Target IP address, and click [OK].

Returns to the [Configure LiveLink(TM) attributes] window.

� Entering an IP address for Target1 is required. Up to four Targets can be specified.

3. Click [Next].

The [Configure the IP address for each team member] window appears.

4. Select the team member to specify the IP address on the [Team Members] list.

133


5. Click [Edit Member IP Address...].


6. Enter the IP address of the team member for LiveLink in [IP address], and click

[OK].

Returns to the [Configure the IP address for each team member] window.

7. Set IP addresses repeating Steps 4 to 6 for all team members on the [Team

Members] list.

8. Click [Next].

The [Creating /Modifying a VLAN: Configure VLAN Support] window appears.

134


12 Specify whether or not to create a VLAN, and click [Next].

If creating, create a VLAN by following the instructions displayed in the window.

When not creating, the following completion window appears.

13 Click [Finish].


135


14 Click [Yes].

The window returns to the initial window.

When the team settings have completed, the multiple adapters that were selected above are

displayed as one virtual adapter. Set the IP address in this virtual adapter.

� Deleting a team

1 Click [Start] – [All Programs] – [Broadcom] – [Broadcom Control Suite 3].

Broadcom Control Suite 3 starts.

2 Select [Teams] – [Delete Team].


3 Click [Yes] to delete the selected team.

136


� Saving a team

1 Create a team.

�"� Creating a team" (p.127)

2 Click [File] – [Team Save As].

3 Click [Yes] to save the created team.

� Restoring a team

1 Call the saved team by clicking [File] – [Team Restore].


2 Click [Apply / Exit].


3 Click [Yes] to restore the team.

137



� Creating a team

1 Click [Start] – [All Programs] – [Broadcom] – [Broadcom Control Suite2].

Broadcom Control Suite2 starts.

2 Click [Tools] – [Create a Team].

The [Broadcom Teaming Wizard] window appears.

138


3 Click [Next].

The [Creating/Modifying a Team: Team Name] window appears.

4 Assign your team a unique name, and click [Next].

The [Creating/Modifying a Team: Team Type] window appears.

139


5 Select the type of team you want to create, and click [Next].

An explanation for when [Smart Load Balancing (TM) and Failover (SLB)] is selected is

explained in the example.

The [Creating/Modifying a Team: Assigning Team Members] window appears.

6 Specify which adapters to include in the team, and click [Next].

The [Creating/Modifying a Team: Designating a Standby Member] window appears.

140


7 Specify whether you want a standby member for the team, and click [Next].

The [Creating/Modifying a Team: Configuring LiveLink] window appears.

� You can select Auto-Fallback Disable Mode if you use the member as a standby member.

� LiveLink feature is not supported if Auto-Fallback Disable Mode is enabled.

LiveLink detects loss of network connectivity beyond the switch and routes traffic only through

team members that have a live link.

8 Specify whether you want LiveLink, and click [Next].

The [Creating/Modifying a VLAN: Configure VLAN Support] window appears.

141


9 Specify whether or not to create a VLAN, and click [Next].

When creating, create a VLAN by following the instructions displayed in the window.

When not creating, the following completion window appears.

10 Click [Finish].


11 Click [Yes].


142


12 Click [OK].

Returns to the initialization screen.

Some adapters that have been selected are displayed as one virtual adapter when completing the

team settings.

� Deleting a team

1 Click [Start] – [All Programs] – [Broadcom] – [Broadcom Control Suite2].

Broadcom Control Suite2 starts.

2 Click [Tools] – [Delete a Team] to delete a Team.

� Saving a team

1 Create a Team.

�"� Creating a team" (p.137)

2 Click [File] – [Team Save As] to save a Team you have created by now.

� Restoring a team

1 Click [File] – [Team Restore] to open a Team you restored before.

2 And click [File] – [Apply] to complete a Team restore.

143


5.6.3 VLAN Setup Procedure


1 Click [Start] – [Control Panel] – [Broadcom Control Suite 3].

BACS starts.

2 Right-click a LAN adapter or the Team name of a Teamed Up adapter, and click

[Add VLAN] from the displayed menu.


� A LAN adapter is displayed with a mark.

� The Team name of a Teamed Up adapter is displayed with a mark.

144


3 Click [Next].

The [Creating/Modifying a VLAN: Naming] window appears.

4 Specify a VLAN name, and click [Next].

The [Creating/Modifying a VLAN: Tagging] window appears.

� A VLAN Name that has already been used cannot be used. Enter another name.

145


5 Select the VLAN type to be set, and click [Next].

When selecting [Untagged]

The [Creating/Modifying a VLAN: Additional VLANs] window appears.

Go to Step 6.

When selecting [Tagged]

The [Creating/Modifying a VLAN: Tag Value] window appears.

1. Specify the tag value of VLAN between 1 to 4094, and click [Next].

2. Click [OK].


146


6 When creating more VLANs, click [Yes]. When finished adding VLANs, select

[No] and click [Next].


Repeat Steps 3 to 5.

When selecting [No]


7 When adding teams has completed, select the process in the window above

and click [Finish].


8 Click [Yes].

147



1 Click [Start] – [Control Panel] – [Broadcom Control Suite 2].

BACS starts.

2 Right-click a LAN adapter or the Team name of a Teamed Up adapter, and click

[Add VLAN] from the displayed menu.


� A LAN adapter is displayed with a mark.

� The Team name of a Teamed Up adapter is displayed with a mark.

148


3 Click [Next].

The [Creating/Modifying a VLAN: Naming] window appears.

4 Enter the VLAN Name, click [Next].

The [Creating/Modifying a VLAN: Tagging] window appears.

� You cannot use a "VLAN Name" that has already been used. Enter another set value.

149


5 Select the VLAN type to be set, and click [Next].

When selecting "Untagged"

The [Creating/Modifying a VLAN: Additional VLANs] window appears. Skip to the Step 7.

When selecting "Tagged"

The [Creating/Modifying a VLAN: Tag Value] window appears.

1. Specify the VLAN tag value (1 to 4094), and click [Next].

2. Click [OK].


6 Select [Yes] when adding another VLAN or select [No] when adding additional

VLANs has completed, and click [Next].


Repeat the Step 3 through Step 5.

150


When selecting [No]


7 When adding a team has completed, select the procedure in the above window,

and click [Finish].


8 Click [Yes].


9 Click [OK].

151


5.7 LAN Driver Advanced Setup

[Intel® PROSet]

"Intel® PROSet" is a tool for configuring details on the LAN driver. This is used in the

following cases.

• Use the Teaming function between LAN cards (PG-2861L)

• Setup a VLAN using LAN cards (PG-2861L)

• Use the Jumbo frame using LAN cards (PG-2861L)

• Perform other advanced settings for LAN cards (PG-2861L)

5.7.1 Intel® PROSet Installation

If the tabs such as [Link], [Teaming] and [VLANs] are not displayed in the property of LAN adapters

which can be selected from the [Device Manager], install Intel® PROSet according to the following

installation procedures:


1 Execute the following file in the PRIMERGY Startup Disc.


[CD/DVD drive]: \Drivers\LAN\Intel\APPS\PROSETDX\Vistax64\DxSetup.EXE


[CD/DVD drive]: \Drivers\LAN\Intel\APPS\PROSETDX\Vista32\DxSetup.EXE

2 Click [Next].


4 Confirm only the following two items are checked and click [Next].

• Intel® PROSet for Windows Device Manager

• Advanced Network Services

5 Click [Install].

6 Click [Finish].

152



1 Execute the following file in the PRIMERGY Startup Disc.

For Windows Server 2003 x64

[CD/DVD drive]: \Drivers\LAN\Intel\APPS\PROSETDX\Winx64\DxSetup.EXE


[CD/DVD drive]: \Drivers\LAN\Intel\APPS\PROSETDX\Win32\DxSetup.EXE

2 Click [OK].

3 Click [Next].

4 Click [Accept].

5 Confirm only the following two items are checked and click [Next].

• Intel® PROSet for Windows Device Manager

• Advanced Network Services

6 Click [Install].

7 Click [Close].

5.7.2 Notes on Referring to the Intel® PROSet Help Topics

When referring to help topics, note the following points.

• Do not use the driver downloaded from the Intel Corporation online service page on this server.

• If the descriptions in the help and this manual vary, give priority to this manual.

• The LAN cards names in Help corresponds to the cards as follows:

• The controller used for each device is as follows:

table: LAN cards names in Help

LAN cards names in Help Corresponding LAN devices

PRO/1000 Server PG-2861L

PRO/1000 Adapter PG-2861L

PRO/1000 Copper Adapter PG-2861L

table: Controller being used

LAN device Controller being used

Eth. Ctrl 2x1Gbit PCI-E 1000-BASE-T lp

(PG-2861L)Intel® 82546EB

153


5.7.3 Teaming

� Teaming types

Teaming has the following types.

• Adapter Fault Tolerance (AFT)

Adapter Fault Tolerance (AFT) is a technology to make the link between the server and switches

redundant by using multiple LAN ports. When a failure occurs in the link being used (Primary Link),

the communication continues by switching the process to the standby link (Secondary Link) without

interrupting. For AFT, all ports in the team must be connected to the same switch.

• Adaptive Load Balancing (ALB)

Adaptive Load Balancing (ALB) is a technology that distributes the sending and receiving data to

multiple LAN ports to improve the performance in addition to redundancy function of AFT (When

"Receive Load Balancing (RLB)" in Advanced setting is set to "Disabled", the reception is done only

in the Primary Link). For ALB, all ports in the team must be connected to the same switch as well as

AFT.

• Switch Fault Tolerance (SFT)

Switch Fault Tolerance (SFT) is a redundancy function equal in configuration to AFT when LAN

ports are connected to a separate switch. SFT switches the link to be used between LAN ports and

switches that are connected to the LAN ports when a failure occurs. However, a failure in links

outside of the switches (←, ↓, and → in the figure below) cannot be detected.

• Static link aggregation

Select this mode when connecting a team to a Cisco FEC/GEC compliant switch or a switch that

supports IEEE802.3ad-Draft Static. Switch settings are also necessary. All ports in the team must be

connected to the same switch.

• IEEE802.3ad dynamic link aggregation (only for Windows Server 2008)

Select this mode when connecting a team to a switch which supports IEEE802.3ad compliant Link

Aggregation Control Protocol (LACP).

In this mode, all adapters must run at the same speed, and all ports in the team must be connected to

the same switch.

Also, this mode is only available for Teaming on the LAN card.

PRIMERGY

Switch

← →

Switch↓

154


� Notes

When using the Teaming function, note the following points.

• For AFT/ALB/Static link/Dynamic link type, up to four LAN ports can be incorporated into one team

and two ports for a SFT type team.

• Once a Team is created, virtual adapters (Team:(Team Name)) will be created in the [Device

Manager] and [Network and Dial-up Connections] of the system. Do not disable or delete this virtual

adapter from the [Device Manager] or [Network and Dial-up Connections]. When deleting a virtual

adapter, make sure to use "Intel® PROSet".

• When the Teaming function is being used, only the following protocols can be used:

• For AFT/SFT/Static link/Dynamic link type: IP, NetBEUI, IPX (NCP), IPX (NetBIOS)

• For ALB type: IP, IPX (NCP)

• When the Teaming function is being used, Windows Load Balancing Service (WLBS) and Network

Load Balancing (NLB) cannot be used.

• If Static link type is selected, only the switch for link aggregation can be used.

• When adding/deleting a Static link type member, perform such operation in a linked down state.

� Only a link down error between a LAN card (onboard LAN) and the switch it connects with, and the

equivalent errors lead to switching of the route. Therefore, if only the switch or LAN card (onboard

LAN) is partially damaged and the route being used is normal at the link level, the route will not be

switched in the team, but the communication using team may become an error.


� Creating a team

1 Click [Start] – [Administrative Tools] – [Computer Management] to start Intel®

PROSet.

2 Click [Network adapters] under [Device Manager] and double-click a LAN

adapter to be incorporated in a team.

3 Click the [Teaming] tab, select [Team with other adapters] and click [New

Team].

4 Enter a team name and click [Next].

5 Check the only LAN adapter to be incorporated in the Team and click [Next].

6 Select a Teaming type with which a Team will be created, and click [Next].

Select the following depending on the Teaming type:

• AFT type: "Adapter fault tolerance"

• ALB type: "Adaptive load balancing"

• SFT type: "Switch fault tolerance"

• Static link type: "Static link aggregation"

155


• Dynamic link type: "IEEE802.3ad dynamic link aggregation"

7 Click [Finish].

8 Click [OK] to close the property window of the created Teaming adapter.

9 Click [OK] to close the property window of the LAN adapter.

When the Teaming setting is complete, the following virtual adapter will be created.

• "Team: (Team Name)"

Upper protocols will be bound with the main virtual adapter.

They cannot be bound with the LAN card included in a Team.

The IP address can be set in the main virtual adapter.

� Deleting a team

When deleting a team, use Intel® PROSet according to the following procedure.


PROSet.

2 Click the [Setting] tab, and click [Delete Team].

The confirmation message appears.

3 Click [Yes].

4 Restart the Server Blade.


� Creating a team

Follow the steps below to create a Team.

1 Log on to the Server Blade with administrator privileges.

2 Click [Start] – [Settings] – [Control Panel] – [Intel® PROSet Wired], and start

Intel® PROSet.

3 Select a LAN adapter to incorporate in a Team and right-click it.

4 Click [Create New Team] in [Add to Team].

[Teaming Up Wizard] appears.

5 Select a Teaming type with which you want to create a Team.

• AFT type: "Adapter fault tolerance"

• ALB type: "Adaptive load balancing"

• SFT type: "Switch fault tolerance"

156


• Static link type: "Static link aggregation"

Do not select other team types.

6 Click [Next].

7 Select a LAN adapter to incorporate in a Team and click [Next].

8 Click [Finish].

9 Click [OK] to exit Intel® PROSet.

When the Teaming setting is completed, a virtual adapter "Intel® Advanced Network Services

Virtual Adapter" will appear.

Upper protocols will be bound with this virtual adapter.

You cannot bind them with the LAN card consisting of a Team.

The IP address should be specified in this virtual adapter.


� Deleting a team

Follow the steps below to delete a Team.


2 Click [Start] – [Settings] – [Control Panel] – [Intel®PROSet Wired], and start

Intel® PROSet.

3 Select the OS to delete.

4 Click [Delete team].


5 Click [OK].



� Creating an AFT, ALB, or SFT team in Windows Server 2003 causes a virtual adapter (Intel®

Advanced Network Service Virtual Adapter) to be created in [Device Manager], [Network and Dial-up

Connections], or [Network Connection] of the system. However, do not disable or delete the virtual

adapter from [Device Manager], [Network and Dial-up Connections], or [Network Connection]. When

deleting the virtual adapter, make sure to use Intel® PROSet.

157


� Event logs

When AFT, ALB, or SFT is used, the following event logs will be generated (source: i ANSMiniport).

� Notes

• When the teaming function normally starts running, event logs (ID = 6 to 8) are stored at boot of the

system. This is not a problem; no action is required.

• Once a Team is setup, plural warning logs (ID = 11) and event logs (ID =15, etc.) may be stored in

the system log of the event viewer at boot of the system. This is not a problem; no action is required.

table: Event log messages

ID Type Message

6 Information The primary adapter has been initialized: (Adapter name)

7 Information The adapter has been initialized: (Adapter name)

8 Information (Team name): The team has been initialized.

10 Information The current primary adapter is changed from the next adapter: (Adapter name)

11 Warning The next adapter link is not connected: (Adapter name)

12 Information The secondary adapter has a priority: (Adapter name)

13 Warning (Adapter name) has been disabled with a team.

14 Information The secondary adapter has been added to a team again: (Adapter name)

15 Information The next adapter link is connected: (Adapter name)

16 Error (Team name): The last adapter has been unlinked. Network connection has failed.

17 Information (Team name): The adapter has established a link again. The network connection has been

recovered.

18 Information The primary adapter at the next priority level has been detected: (Adapter name)

19 Information The secondary adapter at the next priority level has been detected: (Adapter name)

20 Information The primary adapter at the next priority level is preferentially handled: (Adapter name)

21 Information The secondary adapter at the next priority level is preferentially handled: (Adapter name)

22 Warning The primary adapter could not detect the next probe: (Adapter name) Cause: The team

may be divided into groups.

35 Warning (Team name) without one adapter is initialized. Confirm that all adapters exist and

function.

38 Information (Adapter name) has been deleted from the team.

42 Warning (Adapter name) is not specified properly. The adapter cannot process the remote

management function while being a network team.

158


5.7.4 VLAN

A Virtual LAN (VLAN) is a collection of devices to connect to LAN, which are grouped in logical mode

not physically. VLAN can specify a network segment that is available to a device. This enhances

network performance and security.

A VLAN has a function that logically groups users and devices, simplifying a network management

between buildings.

A VLAN is usually controlled by switch setting. A device can belong to only one VLAN for each LAN

card. This driver enables you to configure multiple VLANs on one LAN card. This driver also supports

the VLAN defined in IEEE802.1Q.

� Notes

When using a VLAN, note the following points.

• When adding or deleting a VLAN, always use "Intel® PROSet". Do not disable or delete a VLAN

from the [Device Manager] or [Network and Dial-up Connections].

• Up to ten VLANs can be set to a LAN port.

• Up to four VLANs whose "NetBIOS over TCP/IP" is enabled can be set in the whole system.

• On a VLAN, only use TCP/IP protocols.

• When LLC and the LNDFC protocols are installed by the Fujitsu communication control service,

these protocols are bound (connected) unconditionally. Therefore, release the bind of VLAN and

these protocols in the system where these protocols and VLAN are installed at the same time.


� Creating a VLAN


PROSet.

2 Click [Network adapters] under [Device Manager] and double-click a LAN

adapter to setup a VLAN.

3 Click the [VLANs] tab, and click [New...].

Switch(IEEE802.1Q support)

VLAN30VLAN20VLAN10

PRIMERGY Server

LAN cardVLAN10,20,30

ClientClient

ClientClient

ClientClient

159


4 Specify [VLAN ID] and [VLAN Name]. Then click [OK].

The [VLAN ID] should be identical to the switch setting. 1 to 4094 can be specified.

Any name can be specified as the [VLAN Name].

5 Click [OK] to close the property window for the LAN adapter.

When setup of the VLAN is complete, the following virtual adapter will be created.

• "(LAN Adapter Name)-VLAN:(VLAN Name)"

Upper protocols will be bound with the main virtual adapter. They cannot be bound with the LAN

card configuring a VLAN. The IP address should be specified in the main virtual adapter.

� Deleting a VLAN

Follow the steps below to delete a VLAN.


2 Click [Start] – [Settings] – [Control Panel] – [Intel® PROSet for Wired

Connections] to start Intel® PROSet.

3 Select the VLAN to be deleted and click it.

4 Click [Delete VLAN].


5 Click [OK].

When an attempt is made to delete the last VLAN, the message will be displayed. Click [OK].




� Creating a VLAN

Follow the steps below to create a VLAN.


2 Set the port of the Switch Blade connected to each LAN port or the port of an

external switching hub, so that a VLAN tag frame can be transferred.


Intel® PROSet.

160


4 Select a LAN adapter to set up a VLAN and right-click it.

A VLAN cannot be set to an adapter composing a team.

5 Click [Add VLAN].

6 Specify [ID] and [Name]. Then click [OK].

The [ID] should be identical with the switch setting. The allowable range is 1 to 4094.

The [Name] does not need to be identical with the switch setting.

When the confirmation message appears, select [Yes].

7 Repeat Steps 4 through 6 to set respective VLANs.


When configuring a VLAN is completed, a virtual adapter "Intel® Advanced Network Services

Virtual Adapter" will appear.

Upper protocols will be bound with this virtual adapter.

You cannot bind them with the LAN card consisting a team.

The IP address should be specified in this virtual adapter.


� Deleting a VLAN

Follow the steps below to delete a VLAN.



Intel® PROSet.

3 Select the VLAN to delete and click it.

4 Click [Delete VLAN].


5 Click [OK].

When an attempt is made to delete the last VLAN, the message will be displayed. Click [OK].



161


5.7.5 Local Address Setting

Follow the steps below to specify a local address.



2 Click [Start] – [Administrative Tools] – [Computer Management], select [Device

Manager], and then double-click Network Adapter.

3 Double-click the LAN adapter to be set, and click the [Advanced] tab.

4 Specify the local address to be set for [Locally Administered Address].

Enter 12 hexadecimal characters beginning with "02".



� When returning to a global address, delete the value specified in step 4.




Intel® PROSet.

3 Select a LAN adapter to set the local address and click the [Advanced] tab.

4 Specify a local address in [Locally Managed Address].

Enter 12 hexadecimal characters beginning with "02".



� When returning to a global address, delete the value specified in step 4.

162


5.7.6 Jumbo Frame


Gigabit Ethernet supports Jumbo Frame. When using Jumbo frame, construct the Jumbo frame network

using only devices that support Jumbo frame, and apply the settings that will enable Jumbo frame.

Configure setting for Jumbo frame according to the following procedures.


2 Click [Start] – [Administrative Tools] – [Computer Management], select [Device

Manager], and then double-click Network Adapter.

3 Double-click the LAN adapter to be set, and click the [Advanced] tab.

4 Specify the value to be used for [Jumbo Packets].






Intel® PROSet.

3 Select a LAN adapter to perform configuration and click the [Advanced] tab.

4 Set to the required value in [Jumbo Frame].



163

Chapter 6

High Reliability Tools

For stable PRIMERGY server operations, we

recommend that high reliability tools be installed.

This chapter explains the installation and

necessary settings of high reliability tools.

6.1 RAID Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . 164

6.2 Server Monitoring Tool [ServerView] . . . . . . . . . . . . . . . . 165

6.3 Maintenance Support Tool [HRM/server] . . . . . . . . . . . . . 168

6.4 Solving Problems Early [DSNAP] . . . . . . . . . . . . . . . . . . . 169

164


6.1 RAID Management Tool

RAID Management Tool is software that performs array configuration, disk

initialization and disk array monitoring. Refer to the manual in the Array Controller

Document & Tool CD for installation procedures and use.

For the manual of the SAS RAID Ctrl to be used, refer to "2.3.2 Notes on Configuring

RAID" (�pg.42).

OS installation using ServerStart

� If the OS is installed using ServerStart, RAID Management Tool is installed with the OS and other high

reliability tools.

6.1.1 Before starting operation

After installing the OS in the server, perform the following settings. For details, refer to the manual in

the Array Controller Document & Tool CD.

� Setting for an array administrator account

Set an array administrator account for the RAID management tool (ServerView RAID).

A Windows user account is required when using ServerView RAID.

Create the group "raid-adm", and create an account with any name for an administrator of the array in

this group.

� Setting for the HDD check scheduler

When using the SAS RAID Ctrl (MegaRAID SAS), change the setting for the HDD check scheduler

according to the operation as required. It is set to 12:00 for everyday as default.

165


6.2 Server Monitoring Tool [ServerView]

ServerView constantly monitors the status of the servers' hardware in the network

and provides a console with which the administrator can check the status of all the

servers at a glance. When using ServerView, the server hardware is monitored all the

time. If an error that could cause trouble is detected, the administrator is notified in

real-time. This allows the server administrator to remove a system error early and

avoid trouble.

� For notes on ServerView security, refer to "Security" in "1.1.7 Note" in the "ServerView User's Guide".

� Importance of monitoring the server with ServerView

For safe operation of the server, always monitor the server using ServerView. Even if the server is

operated in the redundancy configuration, overlooking or neglecting errors could result in a system stop

or data loss. As soon as one constituent part of the redundancy configuration fails, the corresponding

countermeasures must be taken. For that reason, monitoring the server with ServerView is necessary.

If ServerView is not applied, the following very serious problems may occur.

� RAID error monitoring

ServerView notifies of the RAID errors. In an environment where ServerView is not applied, the

administrator is not notified of the RAID errors. Leaving the RAID error unattended may lead to a

system stop with multiple dead drives.

� Memory monitoring

ServerView monitors the memory. In an environment where ServerView is not applied, a memory

single-bit error cannot be detected during operation. In order to detect the error, the server must reboot to

run the BIOS Setup Utility or the Server Management Tools. Leaving this error unattended may lead to

multiple-bit errors and a system stop.

� Fan monitoring

ServerView monitors the fan. In an environment where ServerView is not applied, fan irregularities

(failure/stop) cannot be detected during operation. In order to detect the problem, the server must reboot

to run the BIOS Setup Utility or the Server Management Tools. Leaving the fan problem unattended

may lead to overheating inside the server and a system stop.

166


� Temperature monitoring

ServerView monitors the temperature. In an environment where ServerView is not applied, the increased

temperature inside the server, due to the fan problem described above, cannot be detected and the system

stop cannot be prevented. In order to detect the problem, the server must reboot to run the BIOS Setup

Utility or the Server Management Tools.

� Voltage monitoring

ServerView monitors the voltage. In an environment where ServerView is not applied, voltage

irregularities cannot be detected during operation. In order to detect the problem, the server must reboot

to run the BIOS Setup Utility or the Server Management Tools. As leaving the voltage surges, the server

may malfunction or data loss may occur.

� Power supply monitoring

ServerView monitors the power supply. In an environment where ServerView is not applied, power

supply irregularities cannot be detected during operation. In order to detect the problem, the server must

reboot to run the BIOS Setup Utility or the Server Management Tools. System stops due to power supply

failures cannot be prevented.

6.2.1 Installing ServerView

� When installed using ServerStart

If the OS is installed using ServerStart, ServerView will be installed at once with the OS and other high

reliability tools.

� When installed manually (Linux)

ServerView cannot be installed using ServerStart. To install ServerView manually into a Linux system,

refer to "Installation" in "ServerView User’s Guide".

� Be sure to install SNMP service before installing ServerView.

� When an error screen appears after ServerView installation (Windows Server 2003 only)

If Windows Server 2003 Service Pack 1 is applied, the following message may appear on restarting after

installing/uninstalling ServerView.

There is no problem with operations. Click [Close Message] to close the message.

In order to protect the computer, this program is terminated by

Windows.

Name: SNMP Service

167


6.2.2 Setting Required after Installation

Perform necessary operations after ServerView installation referring to "2.4 Checking after Installation"

in "ServerView User’s Guide".

� Boot monitoring setting

We recommend enabling the "Boot Monitoring" function after ServerView is installed. For setting

procedures and explanation on the function, refer to "[Restart Settings] Tab" of "3.4 Serious Error

Handling (ASR)" in "ServerView User’s Guide".

168


6.3 Maintenance Support Tool [HRM/server]

HRM/server is software that supports quick and proper maintenance work to ensure

stable system operation.

6.3.1 Installing HRM/server

� When installed using ServerStart

If the OS is installed using ServerStart, HRM/server will be installed at once with the OS and other high

reliability tools.

� When installed manually (Linux)

HRM/server cannot be installed using ServerStart.

To install HRM/server manually into a Linux system, refer to "HRM/server for PRIMERGY (Windows/

Linux)" at the following location of the PRIMERGY Startup Disc.

[CD/DVD drive]: \PROGRAMS\Japanese2\HRM\iasv_hrm_install.pdf

� It is necessary to install ServerView to use HRM/server.

6.3.2 How to use

For system requirements for HRM/server or usage information, refer to "HRM/server for PRIMERGY

(Windows/Linux)" at the following location of the PRIMERGY Startup Disc.

[CD/DVD drive]: \PROGRAMS\Japanese2\HRM\iasv_hrm_install.pdf

169


6.4 Solving Problems Early [DSNAP]

DSNAP is a tool for collectively acquiring failure investigation information such as

server environment information.

OS installation using ServerStart

� If the OS is installed using ServerStart, DSNAP is installed with the OS and other high reliability tools.

6.4.1 Installing DSNAP

Copy the following file stored in the PRIMERGY Startup Disc into the server's hard disk.

• For Windows Server 2008 (64-bit)

[CD/DVD drive]: \PROGRAMS\Japanese\DSNAPx64\DSNAP.EXE

• For Windows Server 2008 (32-bit)

[CD/DVD drive]: \PROGRAMS\Japanese\DSNAP\x86\DSNAP.EXE

• For Windows Server 2003 x64

[CD/DVD drive]: \PROGRAMS\Japanese\DSNAPx64\DSNAPx64.EXE

• For Windows Server 2003

[CD/DVD drive]: \PROGRAMS\Japanese\DSNAP\DSNAP.EXE

6.4.2 How to Use

Refer to the following file stored in the PRIMERGY Startup Disc. Use a text editor to open it.


[CD/DVD drive]: \PROGRAMS\Japanese\DSNAP\README_JP.TXT

• For Windows Server 2003 x64

[CD/DVD drive]: \PROGRAMS\Japanese\DSNAPx64\README_JP.TXT


[CD/DVD drive]: \PROGRAMS\Japanese\DSNAP\README_JP.TXT

170


171

Chapter 7

Installing Internal Options

This chapter explains how to install internal

options on this Server Blade.

7.1 Before Installing Internal Options . . . . . . . . . . . . . . . . . . . 172

7.2 Removing and Attaching the Top Cover . . . . . . . . . . . . . . 174

7.3 Installing a CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

7.4 Installing Memory Modules . . . . . . . . . . . . . . . . . . . . . . . 182

7.5 Installing an Expansion Card . . . . . . . . . . . . . . . . . . . . . . 188

7.6 Installing an Expansion Board . . . . . . . . . . . . . . . . . . . . . 194

7.7 Installing an Internal Hard Disk Unit . . . . . . . . . . . . . . . . . 197

7.8 BIOS Setting with Expansion Card Installed . . . . . . . . . . . 201

7.9 Connection Examples of an External Option Device . . . . . 202

172


7.1 Before Installing Internal Options

The following types of internal options can be installed on this Server Blade.

• When installing or removing internal options, make sure to remove the Server

Blade from the Chassis. Failure to do so may cause electric shock.

For details on how to remove the Server Blade from the Chassis, refer to

"BX600 S3 Blade Server System Unit Hardware Guide".

• Do not install unauthorized third party internal options. Doing so may cause a

device failure, fire, or electric shock.

• Do not damage or modify internal cables or devices. Doing so may cause a

device failure, fire, or electric shock.

Internal hard disk units

Expansion card slot module

Expansion board

CPU

Memory modules

173


� When installing or removing devices, make sure to use the removed screws on the same location and

devices that were last installed or removed. Failure to do so may damage the device.

� The types of installable options described in this manual are subject to change without notice.

� For secure use of PRIMERGY, use the product shown in the system configuration diagram when

installing optional products (such as internal/external optionals and USB devices etc). Note that

FUJITSU does not guarantee any server operations if any third party optional devices are used.

• The internal components such as the radiation fin remain hot just after the

Server Blade was removed from the Chassis. When installing or removing

internal options, turn the Server Blade off, and wait for a while to begin

operations. In the array system configuration (RAID1), you can replace the

internal hard disk unit without turning the power off.

• The circuit boards and soldered parts of internal options are exposed. They

can be damaged by static electricity. Before handling them, first touch a metal

part of the Chassis to discharge static electricity.

• Do not touch the circuitry on boards or soldered parts. Hold the metallic areas

or the edges of the circuit boards.

• If devices are installed using the methods other than those outlined in this

chapter or disassembled, the warranty will be invalidated.

174


7.2 Removing and Attaching the Top Cover

This section explains how to remove and attach the top cover.

7.2.1 How to Remove the Top Cover

1 Turn off the server.

→"3.3 Turning Off the Server" in "BX600 S3 Blade Server System Unit Hardware Guide"

2 Touch a metal part of the Chassis to discharge static electricity.

3 Remove the target Server Blade from the Chassis.

→"4.2 Installing Server Blades/Storage Blades" in "BX600 S3 Blade Server System Unit

Hardware Guide"

4 While pressing the buttons, slide the top cover a little backward, and carefully

pull it up.

• When installing or removing the top cover, make sure to remove the Server

Blade from the Chassis. Failure to do so may cause electric shock.



• Use tip preventive stabilizers when installing the rack. Pulling the Server Blade

out of the rack without installing stabilizers may cause the rack to tip over.

Buttons

175


� How to attach the top cover

To attach the top cover, simply reverse the removal procedures.

� Make sure that no tools or unnecessary components were left inside the Server Blade before attaching

the top cover back into place.

� Before turning on the Server Blade, make sure that the top cover is attached.

176


7.3 Installing a CPU

This Server Blade can have up to two CPUs by adding an optional CPU.

7.3.1 Location of CPU Installation

CPU socket 1 is installed with a CPU as standard.

CPUs must be installed in the order of the socket numbers.

• When installing or removing the CPU, make sure to remove the Server Blade

from the Chassis. Failure to do so may cause electric shock.



• Do not install unauthorized third party CPUs. Doing so may cause failures.

• Do not use CPUs that differ in frequency/cache capacity.

An error message appears on the BIOS screen.


can be damaged by static electricity.

Before handling them, first touch a metal part of the Chassis to discharge static

electricity.



[Front] [Rear]

CPU socket 1

(standard)

CPU socket 2

(optional)

Baseboard

177


7.3.2 Available CPUs and Notes

� Available CPUs

The following optional CPU types can be used for this Server Blade.

As the additional CPU(s), install CPUs of the same model.

Packaged items of the optional CPU

� Before installing a CPU, refer to "Appendix B.1 CPU Specifications" (�pg.264) to check the contents

of the optional package.

table: List of Available CPUs

Product name Model Remarks

Processor Xeon E5205 (1.86GHz/6MB) PG-FG43G 1.86GHz/6MB, Dual core

Processor Xeon X5260 (3.33GHz/6MB) PG-FG43H 3.33GHz/6MB, Dual core

Processor Xeon E5405 (2GHz/12MB) PG-FG43J 2GHz/12MB, Quad core

Processor Xeon E5420 (2.5GHz/12MB) PG-FG43K 2.5GHz/12MB, Quad core

Processor Xeon X5460 (3.16GHz/12MB) PG-FG43L 3.16GHz/12MB, Quad core

Processor Xeon L5410 (2.33GHz/12MB) PG-FG43P 2.33GHz/12MB, Quad core

178


7.3.3 How to Install a CPU

1 Turn off the Server Blade.

→ "3.3 Turning Off the Server" in "BX600 S3 Blade Server System Unit Hardware Guide"


3 Remove the Server Blade from the Chassis to install a CPU.

→ "4.2 Installing Server Blades/Storage Blades" in "BX600 S3 Blade Server System Unit

Hardware Guide"

4 Remove the top cover.

�"7.2 Removing and Attaching the Top Cover" (pg.174)

5 Remove the dummy CPU cover.

6 Pull up the tab of the CPU slot cover to remove the cover.

Dummy CPU cover

Loosen the screws

CPU slot cover

Tab

179


7 Release the socket lever and the CPU fastener.

1. Unhook the socket lever, and pull it up carefully.

2. Press the CPU fastener tab with an index finger to open the CPU fastener.

Be careful not to touch the CPU socket pin, etc.

8 Install the CPU.

1. Remove the cover attached to the CPU.

2. Check the marking (small triangle) on the CPU and on the CPU socket.

3. Hold the parts shown in ellipses on the CPU in the following figure, and align the

markings and carefully insert the CPU.

• When opening the CPU fastener, be careful not to bend any pins in the CPU

socket. Doing so may cause failures.

• Do not touch the CPU electrode. Doing so may cause a failure.

• When installing the CPU in the socket, be careful not to bend any pins in the

CPU socket.

(1)

Socket leverCPU fastener

Tab

After pulling up the CPU fastener,

open it from this part being careful

not to touch other parts.

(2)

Marking

Hold these parts

180


9 Return the CPU fastener and the socket lever to their original positions, and

fasten the CPU.

1. Close the CPU fastener.

2. Close the socket lever to fasten the CPU.

10 Attach the heat sink.

Remove the grease cover on the back before attaching the heat sink.

� Carefully tighten the heat sink screws in a cross pattern.

11 Attach the top cover.


12 Install the Server Blade to the Chassis.


Hardware Guide"

13 Turn on the Server Blade and check the BIOS Setup Utility settings.

Start the BIOS Setup Utility and select the [Server] menu – the [CPU Status] submenu to check

that [CPUn Status] (n: slot number) is set to [Enabled]. If the CPU is set to [Disabled], change the

setting to [Enabled]. For more details, refer to "8.2.8 Server Menu" (�pg.216).

(2)

CPU fastener

Socket lever

(1)

Tighten screws

Tighten screws

Heat sink

181


� How to remove a CPU

To remove a CPU, simply reverse the installation procedures.

7.3.4 Defective CPU Disconnection Function

This server is equipped with the defective CPU disconnection function.

This function disconnects the CPU judged to be defective (abnormal) during Power On Self Test

(POST) to start the server. On two CPU servers, if one CPU is defective, the other CPU starts up the

server.

The failed CPU can be checked using the information displayed during POST or from [CPUn Status] (n:

slot number) in the [CPU Status] submenu of the [Server] menu in the BIOS Setup Utility (�"8.2.10

CPU Status Submenu" (pg.220)).

� Removing the defective CPU

1 Turn on the server and check the location of the defective CPU by the message

displayed during POST.

2 Replace the defective CPU with a new CPU according to "7.3.3 How to Install a

CPU" (�pg.178).

3 Turn on the server and start the BIOS Setup Utility.


4 Select [CPU Status] on the Server menu and check that the item corresponding

to the replaced CPU is set to [Enabled].

If it is set to [Failed] or [Disabled], change the status to [Enabled].

�"8.2.10 CPU Status Submenu" (pg.220)

� If the setting is not changed to [Enabled], the server will start with the new CPU still marked as

defective and always disconnected. By changing the setting to [Enabled], the defective CPU

status is cancelled and the new CPU can be used at the next start of the server.

182


7.4 Installing Memory Modules

Additional memory will help to increase the amount of data to read at a time and

improve the server processing capability.

• When installing or removing the memory modules, make sure to remove the

Server Blade from the Chassis. Failure to do so may cause electric shock.



• Do not install unauthorized third party memory modules. Doing so may cause

electric shock, a fire, or failures.

• Wait for a sufficient period of time after server shutdown before installing or

removing memory. Failure to do so may cause burns.

• When installing or removing memory modules, make sure to remove the

screws on the specified points only. There is chance of injury if screws other

than those on the specified points are removed.

It may also damage the server.

• Touch only the specified part of the printed circuit board.

Failure to do so may cause injury. It may also damage the server.




• Do not insert and remove memory modules repeatedly. Doing so may cause

failures.

• Hold the edge of the memory module as shown below. Do not touch the part

with gold wire (terminal) or memory chip.

Memory chip

Memory module

Do not touch this part.

183


7.4.1 Location of Memory Module Installation

Install memory modules to the memory slots in the Server Blade.

Each memory bank consists of slot 1/2, 3/4, 5/6, and 7/8 on this Server Blade.

To add more memory, install memory modules in pairs, each having the same capacity, to the

corresponding slots in the sequence of Bank 1, Bank 2, Bank 3, and Bank 4, in ascending order of their

capacity.

Memory bank 1 has memory modules as the standard.

7.4.2 Available Memory Modules and Notes

� Available memory modules

Memory of this Server Blade consists of two the Dual In-Line Memory Modules (DIMM) in pairs and

memory modules are extended in pairs.

The following memory module types can be used on this Server Blade.

Packaged items of optional memory

� Before installing memory modules, refer to "Appendix B.2 Memory Specifications" (�pg.265) to check

the contents of the optional package.

table: List of Available Memory Modules


Memory Module-1GB PG-RM1CJ 512MB-DDR2 DIMM ×2

Memory Module-2GB PG-RM2CJ 1GB-DDR2 DIMM ×2



[Front] [Rear]Baseboard

Memory Slot 1 (Standard)Memory Slot 5 (Optional)Memory Slot 2 (Standard)Memory Slot 6 (Optional)Memory Slot 3 (Optional)Memory Slot 7 (Optional)

Memory bank 1

Memory bank 2

Memory bank 3

Memory Slot 4 (Optional)Memory Slot 8 (Optional)

Memory bank 4

184


� Notes on installing memory modules

� Identifying memory modules

Make sure to install a pair of DIMMs, each having the same capacity. Check that the number beginning

with "CA" (e.g., CA05946-E101) printed on the label is same on the two DIMMs. Be sure to use a pair

of modules with the same number.

If the DIMMs have identification labels, be sure to install a pair of DIMMs with the same capacity with

the label placed on the same location.

• Identification label location

• Identification label patterns

When a memory module is viewed with the corner circled in the above figure to the lower left,

identification labels are applied in any of the following patterns.

table: Identification Label Patterns

Pattern Label A Label B Label C

1 Not applied Not applied Not applied

2 Applied Not applied Not applied

3 Not applied Applied Not applied

4 Not applied Not applied Applied

5 Applied Applied Not applied

6 Applied Not applied Applied

7 Not applied Applied Applied

8 Applied Applied Applied

Identification label A Identification label B Identification label C

185


� Memory redundancy function

The memory redundancy function (memory mirroring function) can be set for this Server Blade. When

the memory redundancy function is enabled, a mirrored set containing two identical memory banks is

configured. When data is saved, it is written to both memory banks. This means that the available

memory capacity (logical capacity) is half that of the physical capacity during memory redundancy.

When a memory error occurs, the memory bank in which the error occurred will be automatically

disconnected, and the other memory bank will take over operations. After replacing the failed memory

or the failed memory bank, the mirrored set is automatically restored.

� Installation conditions

Install the memory module according to the following conditions.

I: Install memory module.

-: Do not install memory module.

� Install memory modules of the same model to the four slots that make up one mirror set.

� The capacity of two mirror sets can be different.

� BIOS settings

After installing the memory module, perform the following settings.

1 Start the BIOS Setup Utility.


2 From the [Server] menu - the [Memory Status] submenu, change the [Memory

Mirror] setting to [Mirror].

�"8.2.11 Memory Status Submenu" (pg.221)

3 Save the setting and exit the BIOS Setup Utility.


table: Conditions when using the memory mirroring function

Mirror set #1 Mirror set #2

Bank 1 Bank 2 Bank 3 Bank 4

Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8

I I I I − − − −

I I I I I I I Ι

186


7.4.3 How to Install/Remove Memory Module

This section explains how to install and remove memory modules.




3 Remove the Server Blade from the Chassis to install a memory module.


Hardware Guide"



5 Install or remove memory modules.

When installing

Insert a memory module properly into the memory slot. The levers close. If the levers are not

closed completely, push them with your fingers.

When removing

Open the levers on both ends.

6 Check that the memory module is inserted all the way.



• Make sure not to open the clips outward too quickly because the memory

module may pop up, which could cause damage.

• An improperly engaged memory module could cause a fire. Do not insert the

memory module on the wrong side.

Lever

Alignnotch

187




Hardware Guide"

7.4.4 Defective Memory Disconnection Function

This Server Blade is equipped with the defective memory (RAM module) disconnection function.

This function disconnects memory blocks (two DIMMs) judged to be defective (abnormal) during

Power On Self Test (POST) to start the Server Blade. When POST is executed, if the memory capacity is

discovered to be smaller than the capacity of the memory installed, there is a possibility of memory

defect.

From POST error messages or the system event log, you can check the slot location that has defective

memory.

�"9.2.2 Error Messages" (pg.234)

�"9.3 System Event Log" (pg.243)

If defective memory is discovered, replace it, and then restart the Server Blade.

� Replacing the defective memory

Replace the defective memory with a new one according to "7.4.3 How to Install/Remove Memory

Module" (�pg.186).

� After replacing the memory module, start the BIOS Setup Utility and select the [Server] menu - the

[Memory Status] submenu to check that [DIMM n,n] (n is the number of the replaced memory module)

for the replaced memory module is set to [Enabled]. If the item is set to [Disabled], change the setting

to [Enabled]. If it is not set to [Enabled], the server will start with the memory module recognized as

being defective and constantly disconnected.

To use a new memory module, set the item to [Enabled] for releasing the failed memory status at the

next startup.


188


7.5 Installing an Expansion Card

This Server Blade can be equipped with one expansion card using the expansion

card slot module.

This section explains the types of expansion card, installation procedures, and notes

on expansion cards.

7.5.1 Location of Expansion Card Installation

Insert an expansion card in a PCI slot of the expansion card slot module, and then install the slot module

in the expansion card slot of the Server Blade.

• When installing or removing an expansion card, make sure to remove the









• Expansion cards are susceptible to static electricity. Place them on conductive

pads or keep them in their packaging as long as they are not necessary.

Expansion card slot

PCI slot

[Expansion card slot module]

[Server Blade (Front view)]

189


7.5.2 Available Expansion Card Slot Modules/Expansion Cards and Notes

� Available expansion card slot modules

� Available expansion cards and installable expansion card slot modules

I: Installable

-: Not installable

� For the latest information of the expansion card supported in this Server Blade, refer to

Recommendation Options in the Fujitsu PRIMERGY website (http://primergy.fujitsu.com).

� Notes on installing expansion cards

� Drivers

For details on each expansion card driver, refer to "2.3.5 Onboard Controller and Expansion Cards

Supported by ServerStart" (�pg.45).

� Notes on each card

Before installing an expansion card, refer to the notes in the expansion card manual.

� SCSI card

• Connection of a SCSI device

Connect the SCSI device supported by this server to the SCSI card. Operations of unsupported SCSI

devices are not guaranteed.

table: Available expansion card slot module


Expansion Card Slot Module PG-CS103 64bit 133MHz, PCI-X

Expansion Card Slot Module PG-CS104 PCI-Express (x4)

table: List of available expansion cards and corresponding slot modules

Product name (model)Expansion card slot module

Remarks PG-CS103 PG-CS104

SCSI Ctrl U160 lp (PG-1301L)Ι −

PCI-X, Ultra160 SCSI, For connection with

external backup devices

Eth. Ctrl 2 x 1Gbit PCI-E 1000-

BASE-T lp (PG-2861L)− Ι

PCI-Express, 1000BASE-T, Dual Port

SAS RAID Ctrl (PG-248EL)− Ι

PCI-Express, For connection with Storage

Blade


190


� Notes when adding an Expansion Card Slot Module

When using an onboard array controller in this Server Blade and replacing the SAS module that is

installed standardly with an Expansion Card Slot Module (PG-CS103/PG-CS104), initialization of the

logical drive of the array controller may be performed after replacing the module.

This is due to the fact that information about data consistency, which is used to record whether write data

is correctly written to the internal hard disk unit in the past, is stored on the standard SAS module.

When the information is lost by replacing the module, initialization is automatically executed to ensure

data consistency.

For details about initialization, refer to the manual in the Array controller Document & Tool CD.

7.5.3 How to Install an Expansion Card

To install the PCI-X and PCI-Express cards, perform the same procedures.



2 Touch the metal part of the Chassis to discharge static electricity.

3 Remove the Server Blade to install an expansion card slot module in, from the

Chassis.


Hardware Guide"



5 Remove the standard SAS module from the Server Blade.

Remove the screw, and remove the standard SAS module.

Screw

SAS module

191


6 Remove the slot cover of the expansion card slot module.

Remove the screw, and remove the slot cover.

� Make sure to keep the removed slot cover for later use.

7 Install the expansion card to the expansion card slot module.

1. Securely insert the expansion card in the PCI slot.

Insert the expansion card with its circuitry side facing downwards.

2. Secure the expansion card using the screw.

Secure the expansion card using the screw removed in step 6.

Screw

Slot cover

(1)

Screw

PCI slot

(2)

192


8 Install the expansion card slot module in the Server Blade.

Insert the expansion card slot module in the connector for the expansion card slot module and

close the cover to make sure that it is fully inserted.

9 Secure the expansion card slot module.

Secure the module using the screw removed in Step 5.



11 Install the Server Blade in the Chassis.


Hardware Guide"


Referring to "7.8 BIOS Setting with Expansion Card Installed" (�pg.201), confirm whether the

setting satisfies card installation conditions. If the setting does not satisfy those installation

conditions, change the setting.

Expansion card slotmodule connector

Cover

Screw

193


� How to remove an expansion card

To remove the expansion card, simply reverse the installation procedures.

194


7.6 Installing an Expansion Board

One expansion board can be installed in this Server Blade. When the expansion

board is installed, you can connect to external devices, etc. through the Network

Blade.

7.6.1 Location of Expansion Board Installation

Install the expansion board in the expansion board slot in the Server Blade.

• When installing or removing an expansion board, make sure to remove the





can be damaged by static electricity.

Before handling them, first touch a metal part of the Chassis to discharge static

electricity.



• Expansion boards are susceptible to static electricity. Place them on

conductive pads or keep them in their packaging as long as they are not

necessary.

Expansion board slot

195


7.6.2 Available Expansion Boards

The table below lists the expansion boards available on this Server Blade.

*1: If installing this expansion board, it cannot be installed in a BX600 S3 Chassis.

7.6.3 How to Install an Expansion Board




3 Remove the Server Blade from the Chassis to install an expansion board.


Hardware Guide"



5 Install the expansion board.

Check that the expansion board is securely inserted to the slot.

table: Available Expansion Boards

Product name Model

4Gbit/s FC I/O Module PG-FCD201

2Gbit/s FC I/O Module PG-FCD102 (*1)

1Gbit/s Ethernet I/O Module PG-LND201

Expansion board

Expansion board slot

[Rear]

196


6 Fix the expansion board using the screws supplied with the board.





Hardware Guide"

� To connect the expansion board to a fibre channel device, install the Fibre Channel expansion

board in the Server Blade and the FC Network Blade in the Chassis, then install the SFP mod-

ule (option) in the FC Network Blade. For details, refer to "BX600 S3 Blade Server System Unit

Hardware Guide".


Referring to "7.8 BIOS Setting with Expansion Card Installed" (�pg.201), confirm whether the

setting satisfies card installation conditions. If the setting does not satisfy those installation

conditions, change the setting.

� How to remove an expansion board

To remove an expansion board, simply reverse the installation procedures.

Screws

197


7.7 Installing an Internal Hard Disk Unit

This section explains how to install internal hard disk units.

• When installing or removing the units, make sure to remove the Server Blade

from the Chassis. Failure to do so may cause electric shock.



In the array system configuration (RAID1), you can replace the internal hard

disk unit without turning the power off.

• Rough handling of the hard disk unit can damage the stored data. To cope with

any unexpected problems, always back up important data. When backing up

data to another hard disk unit, you should make backups on a file or block

basis.

• Use the unit in a dry place with low airborne dust levels.

• Use the device on a shock-and-vibration free surface.

• Keep the device away from direct sunlight, radiators or other heat sources.

• Do not use the unit in a place where the temperature is extremely high or low,

or experiences extreme temperature changes.

• Do not disassemble the hard disk unit.

• Take great care so that you do not hit the hard disk or bring it into contact with

metallic objects.






198


7.7.1 Location of Internal Hard Disk Units Installation

Install the internal hard disk unit in the order of bay numbers (1 – 2).

7.7.2 Available Internal Hard Disk Units and Notes

� Available internal hard disk units

The following internal hard disk units can be installed in this Server Blade.

Package items of optional internal hard disk unit

� Before installing the internal hard disk unit, refer to "Appendix B.3 Internal Hard Disk Unit

Specifications" (�pg.265) to check the contents of the optional package.

� Notes on using the onboard array controller

When manually installing the OS, the array must be configured under the onboard array controller

before installation. To enable the RAID1 array configuration, the array must be initialized after its

configuration is completed.

For more details on how to create the array configuration and initialize the array, refer to the manual in

the Array controller Document & Tool CD.

table: Available Internal Hard Disk Units

Product name Model Overview

HDD SAS 10k 73GB hot plug 2.5inch PG-HDD71B 73.4GB, 10,025rpm, SAS 2.5inch, hot-pluggable



[Server Blade (Front view)]

2.5-inch storage bay 2 2.5-inch storage bay 1

199


7.7.3 How to Install the Internal Hard Disk Unit




3 Remove the dummy unit from the bay to accommodate an internal hard disk

unit.

A dummy unit is inserted into a bay not occupied by an internal hard disk unit. Pull the dummy

unit out towards you with its tabs being pressed inward.

Be sure to keep the removed dummy units for later use.

4 Install the internal hard disk unit into the Server Blade.

1. Fully insert the internal hard disk unit in the bay while the cover of the internal hard

disk unit is open.

2. Close the cover of the internal hard disk unit securely, and lock the tab.

Tabs

Tab

(2)

Cover

(1)

200


� How to remove the internal hard disk unit




3 Remove the internal hard disk unit.

While pressing the tab, open the cover, and pull out the internal hard disk unit.

To remove the internal hard disk unit, use both hands to pull it out.

4 Install a new internal hard disk unit or a dummy unit.

�"7.7.3 How to Install the Internal Hard Disk Unit" (pg.199)

� Replacing the failed internal hard disk unit

When RAID (RAID1) is configured with this server, a failed hard disk unit can be replaced and the

restoration can be performed without turning off the server and peripheral devices (hot swappable/hot

pluggable).

For more details on the replacement procedure, refer to the manual in the Array controller Document &

Tool CD.

For more details on the RAID, also refer to the manual in the Array controller Document & Tool CD.

Tab

Cover

(1)

(2)

201


7.8 BIOS Setting with Expansion Card Installed

In this Server Blade, the settings of the BIOS Setup Utility must be changed

according to installation conditions when installing the following expansion boards or

cards.

• 4Gbit/s FC I/O Module (PGFCD201)

• 2Gbit/s FC I/O Module (PG-FCD102)

• 1Gbit/s Ethernet I/O Module (PG-LND201)

• Eth. Ctrl 2 x 1Gbit PCI-E 1000-BASE-T lp (PG-2861L)

• SCSI Ctrl U160 lp (PG-1301L)

• SAS RAID Ctrl (PG-248EL)

For a device that starts the OS, use the BIOS Setup Utility to set the optional ROM (OPROM) to

[Enabled].

For more details on the setting procedures, refer to "8.2.5 PCI Configuration Submenu" (�pg.212) in the

[Advanced] menu.

� Refer to the "PRIMERGY BX620 S2 Server Blade User's Guide" or "PRIMERGY BX620 S3 Server

Blade User's Guide" when performing 2Gbit/s FC I/O Module (PG-FCD102) settings.

202


7.9 Connection Examples of an External Option Device

This section explains the connection modes of external optional devices.

7.9.1 Connection of a Backup Cabinet

Connect the backup cabinet to the SCSI card installed in the expansion card slot module.

The following shows a connection example:

7.9.2 Connection of Storage Blade

Connect the Storage Blade to the SAS RAID Ctrl installed in the expansion car slot module.

The following shows a connection example:

BaseboardMid-plane

SCSI Cable(PG-CBLS001 / PG-CBLS002 : Sold separately)

PRIMERGY SX10Backup cabinet(PG-R1BC4)

Internal hard disk units

SCSI Ctrl U160 lp (PG-1301L)Expansion Card Slot Module (PCI-X) (PG-CS103)

Server Blade

Chassis[Front]

Baseboard

Server Blade

Midplane

Expansion Card Slot Module (PG-CS104)

SAS cable(provided with PRIMERGY SX650 Storage Blade)

SAS RAID Ctrl (PG-248EL)

Chassis [Front]

PRIMERGY SX650Storage Blade (PG-B6ADC1)

203

Chapter 8

Hardware Configuration/ Utilities

This chapter explains how to make the

environment settings necessary to operate the

Server Blade.

8.1 Switch Block Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

8.2 BIOS Setup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

204


8.1 Switch Block Settings

This section explains how to set the switch block.

8.1.1 Switch Block

This section explains how to set the switch block ("b" in �"1.3.3 Baseboard" (pg.31)) on the baseboard.

The following table shows the description of each switch.

• When setting the switch block, be sure to turn the Server Blade off, and then

remove the Server Blade from the Chassis. Failure to do so may cause electric

shock.



table: Switch Block Settings

Switch No. Description

Switch 1 Sets whether or not to delete a password.

• ON: Deletes the password.

• OFF: Does not delete the password. (Default)

Switch 2 Sets whether or not to clear the information stored on the CMOS.

• ON: Clears the information stored on the CMOS.

• OFF: Maintains the information stored on the CMOS. (Default)

Switch 3 Always keep in OFF position.

Switch 4 Always keep in OFF position.

Switch 5 Always keep in ON position.

Switch 6 Always keep in ON position.

OFF

ON

3 41 2 5 6

205


8.2 BIOS Setup Utility

This section explains settings for the BIOS Setup Utility and items regarding each

setting.

8.2.1 Starting and Exiting the BIOS Setup Utility

The following explains how to start and exit the BIOS Setup Utility.

� How to start the BIOS Setup Utility

1 Turn on the main power of the Chassis.

→ "3.2 Turning On the Server" in "BX600 S3 Blade Server System Unit Hardware Guide"

2 Turn the Server Blade on.

→ "3.2 Turning On the Server" in "BX600 S3 Blade Server System Unit Hardware Guide"

3 After the memory capacity is displayed, if "Press F2 to run Setup Press F12 for

BBS POPUP" appears on the screen, press the [F2] key.

The [Main] menu appears.

BIOS Version nnnnBMC F/W Version nnnn

System Time [hh:mm:ss]System Date [xxx mm/dd/yyyy]

Sync RTC with Mgmt. Blade [Enabled]

System Memory Size 3072MB

v0n.nn (C)Copyright 1985-2004, American Megatrends, Inc.

BIOS SETUP UTILITY

Main Advanced Security ExitBootServer

System Overview

AMIBIOSVersion 08.00.12Build Date mm/dd/yy

Use [ENTER],[TAB]or [SHIFT-TAB] toselect a field.

Use [+] or [-] toconfigure system Time.

F1

Esc

Select ItemSelect Screen

Change Option+-

General Help

ExitF10 Save and Exit

Tab Select Field

206


� Key operations with the BIOS Setup Utility

The roles of the keys used for setting the BIOS Setup Utility are as follows:

� How to exit the BIOS Setup Utility

1 Use the [←] [→] keys to display the [Exit] menu.

table: List of Key Operations on the BIOS Setup Utility Window

Key Role

[F1] Displays help information.

[Esc] When a submenu window is displayed, exits it and returns to the previous menu.

When the menu window is displayed, displays the [Exit] menu.

[←] [→] Switches between menus.

[↑] [↓] Scrolls through the menu option list.

[Page Up] [Page Down] Moves the cursor to the beginning or end of an item.

[Enter] Selects a set item. For items displayed with , displays the submenu. When a

submenu is displayed, pressing the [Esc] key returns to the menu window.

[−][+] Changes the value of an item.

[F2] [F3] Changes the color of the BIOS setting window.

[F7] Sets the set values of all the items to the stored values.

[F9] Sets all the items to the initial values.

[F10] Saves the settings and exits the BIOS Setup Utility.

Save Changes and ExitDiscard Changes and ExitLoad Previous Value

Get Default Values


BIOS SETUP UTILITY


Exit Options Exit system setupafter saving thechanges.

F10 key can be usedfor this operation.

F1

Esc


Change Option+-

General Help


Tab Select Field

207


2 Use the [↑] [↓] keys to select the exit mode.

To save configuration changes before exiting:

Move the cursor to [Save Changes and Exit] and press the [Enter] key.

The message "Save configuration changes and exit setup?" is displayed.

To exit without saving configuration changes:

Move the cursor to [Discard Changes and Exit] and press the [Enter] key.

The message "Discard changes and exit setup?" is displayed.

3 Use the [←] [→] keys to move the cursor to [OK] or [Cancel], and press the

[Enter] key.

When selected [Save Changes and Exit]:

Select [OK] to exit. After saving changes to settings, the BIOS Setup Utility closes and the server

restarts.

To return to the BIOS Setup Utility without exiting this program, select [Cancel].

When selected [Discard Changes and Exit]:

Select [OK] to exit without saving the settings. The BIOS Setup Utility closes and the OS starts.

To return to the BIOS Setup Utility without exiting this program, select [Cancel].

208


8.2.2 Main Menu

The [Main] menu window is initially displayed when you start the BIOS Setup Utility.

Settings for time and date and for the drives are configured in the [Main] menu window.

table: Items on the Main Menu

Item Setting Description

Version - Displays the AMIBIOS version.

Build Date - Displays the date that the AMIBIOS is built.

BIOS Version - Displays the BIOS version of the Server Blade.

BMC F/W Version - Displays the BMC firmware version of the Server

Blade.

System Time Present time The system time is set in "hours:minutes:seconds"

format. The hours should be based on a 24-hour

clock.

For example, 6:30:00 P.M. is set as "18", "30",

"00".

This can be set when [Sync RTC with Mgmt.

Blade] is set to [Disabled].

Note:

� Repeat the procedure until the correct time

is set.

� If a highly precise system time is necessary,

install a network synchronized time system

(NTP, etc.).

System Date Present date The system date is set in "month:day:year" format.

For example, April 20, 2008 is set as "04", "20",

"2008".

This can be set when [Sync RTC with Mgmt.

Blade] is set to [Disabled].

Sync RTC with Mgmt.

Blade

• Disabled

• Enabled (Initial value)

Sets whether or not to synchronize the time

between the Management Blade and RTC.

System Memory Size - Displays the size of the installed memory.

BIOS Version nnnnBMC F/W Version nnnn

System Time [hh:mm:ss]System Date [xxx mm/dd/yyyy]

Sync RTC with Mgmt. Blade [Enabled]

System Memory Size 3072MB


BIOS SETUP UTILITY


System Overview

AMIBIOSVersion 08.00.12Build Date mm/dd/yy

Use [ENTER],[TAB]or [SHIFT-TAB] toselect a field.

Use [+] or [-] toconfigure system Time.

F1

Esc


Change Option+-

General Help


Tab Select Field

209


8.2.3 Advanced Menu

This menu configures the server management and peripheral devices.

table: Items on the Advanced Menu


Reset Configuration Data • No (Initial value)

• Yes

Sets the initialization of the Extended System

Configuration Data (ESCD) where the system

resources are recorded.

This setting is changed to [No] whenever the

system is restarted.

Peripheral Configuration - Configures a serial port. Press the [Enter] key to display the submenu.

�"8.2.4 Peripheral Configuration Submenu"

(pg.210)

PCI Configuration - Configures the PCI device. Press the [Enter] key to display the submenu.

�"8.2.5 PCI Configuration Submenu" (pg.212)

CPU Configuration - Configures CPU. Press the [Enter] key to display the submenu.

�"8.2.6 CPU Configuration Submenu" (pg.213)

Exit

Reset Configuration Data [No]

CPU Configuration

Peripheral Configuration PCI Configuration


BIOS SETUP UTILITY


Configure the MPSpecification revisionlevel. Some operatingsystems will require1.1 for compatibilityreasons.

Advanced Settings

WARNING: Setting wrong values in below sections may cause system to malfunction.

F1

Esc


Change Option+-

General Help


Tab Select Field

210


8.2.4 Peripheral Configuration Submenu

This submenu appears when [Peripheral Configuration] is selected from the Advanced menu.

It configures a serial port.

table: Items on the Peripheral Configuration Submenu


Serial Port1 Address • Disabled

• 3F8/IRQ 4 (Initial value)

• 2F8/IRQ 3

• 3E8/IRQ 4

• 2E8/IRQ 3

Sets the I/O port address and IRQ level of the serial

port.

USB Configuration - Configure the USB device. Press the [Enter] key to display the submenu.

�"� USB Configuration Submenu" (p.211)

Main Security ExitBootServer

Peripheral Configuration

Serial 1Serial Port1 Address [3F8/IRQ4]


BIOS SETUP UTILITY

Advanced

USB Configuration

Allows BIOS to Select Serial Port1 Base Addresses.

F1

Esc


Change Option+-

General Help


Tab Select Field

211


� USB Configuration Submenu

table: Items on the USB Configuration Submenu


Module Version - Displays the USB code version of the AMI

BIOS.

USB Devices Enabled - Displays the number of the connected USB

devices.

USB Functions 4 USB Ports

(Unchangeable)

Sets whether or not to use the hardware

conforming to the USB standard.

USB 2.0 Controller Enabled (Unchangeable) Sets whether or not to enable the USB-based

controller (standard 2.0).

This item appears when [USB Functions] is set to

[4 USB Ports].

Legacy USB Support Auto (Unchangeable) Sets whether or not to use the USB-connected

keyboard and mouse.

This item appears when [USB Functions] is set to

[4 USB Ports].

USB Mass Storage Device

Configuration

- Press the [Enter] key to display the [USB Mass

Storage Device Configuration] submenu. This

item appears when the device is connected via

USB.

USB Mass Storage Reset

Delay

20Sec (Unchangeable) Sets the number of seconds to wait for a response

after USB Mass Storage Device has been

initialized during POST.

Device #1 - Displays the connected device.

Emulation Type

(Device #1)

Auto (Unchangeable) Sets the type of the connected device. This item

appears when a USB Mass Storage Device is

connected.

Device #2 - Displays the connected device.

Emulation Type

(Device #2)

Auto (Unchangeable) Sets the type of the connected device. This item

appears when a USB Mass Storage Device is

connected.

212


8.2.5 PCI Configuration Submenu

This submenu appears when [PCI Configuration] is selected from the Advanced menu.

It configures the PCI device.

table: Items on the PCI Configuration Submenu


Onboard Disk OPROM • Disabled


Sets whether or not to initialize the extended ROM

of each device.

Note:

� Change the setting of the device that is used

for booting to [Enable].

Onboard LAN1 OPROM • Disabled


Onboard LAN2 OPROM to Onboard LAN6 OPROM

• Disabled (Initial value)

• Enabled

PCI slot OPROM • Disabled (Initial value)

• Enabled

Daughter Board OPROM • Disabled (Initial value)

• Enabled

Exit



BIOS SETUP UTILITY

Advanced

PCI Configuration

Onboard Disk OPROM [Enabled]Onboard LAN 1 OPROM [Enabled]Onboard LAN 2 OPROM [Disabled]Onboard LAN 3 OPROM [Disabled]Onboard LAN 4 OPROM [Disabled]Onboard LAN 5 OPROM [Disabled]Onboard LAN 6 OPROM [Disabled]PCI slot OPROM [Disabled]Daughter Board OPROM [Disabled]

Has to be enabled, forbooting from internalSATA or SAS- Hard Disk

F1

Esc


Change Option+-

General Help


Tab Select Field

213


8.2.6 CPU Configuration Submenu

This submenu appears when [CPU Configuration] is selected from the Advanced menu.

It configures CPU settings.

table: Items on the CPU Configuration Submenu


C1E Support Disabled (Unchangeable) The CPU internal setting.

Hardware Prefetcher Enabled (Unchangeable)

Adjacent Cache Line

Prefetch

• Disabled


Sets the use of the CPU cache access function.

Vanderpool Technology • Disabled (Initial value)

• Enabled

Sets the use of virtualization technology.

Note:

� This item can be selected only immediately

after power is supplied. The item cannot be

selected during startup.

Execute Disable Bit • Disabled (Initial value)

• Enabled

Sets the use of the security function to avoid buffer

overflow.

Intel(R) SpeedStep(tm)

tech.

• Maximum

• Minimum

• Automatic

• Disabled (Initial value)

Sets the CPU power saving function.

This item is not supported when the Xeon processor

E5405 (2GHz/12MB) CPU is used.

Intel(R) C-State tech. Disabled (Unchangeable) Sets the function to optimize the performance and

power status by moving the CPU status according

to the load.

Exit



BIOS SETUP UTILITY

Advanced

This should be enabled in order to enable or disable the Hardware Prefetcher Disable Feature.

F1

Esc


Change Option+-

General Help


Tab Select Field

CPU Configuration

Hardware Prefetcher [Enabled]C1E Support [Disabled]

Adjacent Cache Line Prefetch [Enabled]

Execute Disable Bit [Disabled]Vanderpool Technology [Disabled]

Intel(R) SpeedStep(tm) tech. [Disabled]Intel(R) C-STATE tech. [Disabled]

214


8.2.7 Security Menu

This menu configures the security features.

table: Items on the Security Menu


Supervisor Password/User

Password

- Displays whether each password is set or not.

[Not installed] appears when the password is not

set, and [Installed] appears when it is set.

Change Supervisor

Password

- Press the [Enter] key to display the administrator

password setting window. The administrator

password prevents unauthorized startup of the

BIOS Setup Utility.

For details about procedures for setting, changing,

and deleting the password, refer to "9.4.2 Security

against Unauthorized Use" (�pg.248).

Change User Password - Press the [Enter] key to display the user password

setting window. The system password prevents

unauthorized access to the system.

An administrator password must be specified.

For details about procedures for setting, changing,

and deleting the password, refer to "9.4.2 Security

against Unauthorized Use" (�pg.248).

Clear User Password - Selecting this item and pressing the [Enter] key will

delete the user password. This item appears when

[User Password] is specified.

Password Check • Setup (Initial value)

• Always

Sets the scope protected by the password.

This item appears when [Supervisor Password] or


• Setup

When starting the BIOS Setup Utility, entering

the password is required.

• Always

When starting the system or BIOS Setup Utility,

entering the password is required.

Supervisor Password :Not InstalledUser Password :Not Installed

Change Supervisor PasswordChange User Password


BIOS SETUP UTILITY


Security Settings Install or Change the password.

F1

Esc


Change Option+-

General Help


Tab Select Field

215


Supervisor Password Lock • Standard (Initial value)

• Extended

Set the scope protected by the setup password. This item appears when [Supervisor Password] or


table: Items on the Security Menu


216


8.2.8 Server Menu

This menu configures memory and CPU.

table: Items on the Server Menu


Post Errors Enabled (Unchangeable) Sets whether to cancel system startup and stop the

system when a Power On Self Test (POST) error is

detected.

ASR&R - Configures ASR&R setting. Press the [Enter] key to display the submenu.

�"8.2.9 ASR&R Submenu" (pg.217)

CPU Status - Configures CPU setting. Press the [Enter] key to display the submenu.

�"8.2.10 CPU Status Submenu" (pg.220)

Memory Status - Configures a memory setting. Press the [Enter] key to display the submenu.


Console Redirection - Configures console settings. Press the [Enter] key to display the submenu.

�"8.2.12 Console Redirection Submenu" (pg.222)

System Information - Configures system settings. Press the [Enter] key to display the submenu.

�"8.2.13 System Information Submenu" (pg.223)

Exit

Server Configuration

Post Errors [Enabled]


BIOS SETUP UTILITY


ASR&R

CPU Status

Memory Status

Console Redirection

System Information

Wait for F1key to be pressed if error occurs.

F1

Esc


Change Option+-

General Help


Tab Select Field

217


8.2.9 ASR&R Submenu

This submenu appears when [ASR&R] is selected from the Server menu.

It configures ASR&R settings.

Main Advanced Security ExitBoot Exit

ASR&R

OS Boot Watchdog Timer [Disabled]


BIOS SETUP UTILITY

Server

Enable/Disable OS Boot Watchdog Timer

Boot Retry Counter [Retry 3 times]ASR&R Boot Delay(Minute) [ 2]After Power Failure [Last State]

F1

Esc


Change Option+-

General Help


Tab Select Field

218


table: Items on the ASR&R Submenu


OS Boot Watchdog Timer • Disabled (Initial value)

• Enabled

Sets whether to enable or disable the OS Boot

Monitoring function, when ServerView is installed

to the OS.

If for some reason booting the operating system is

interrupted when this function is enabled, the

system will automatically restart.

The OS Boot Monitoring function can also be

enabled or disabled from ServerView.

Note:

� If ServerView is not installed to the OS, be

sure to set the OS Boot Watchdog Timer to

[Disabled]. If the setting is set to [Enabled],

the server may automatically turn off or

restart unexpectedly.

Even when ServerView is installed on the

OS, if starting the system while the "Server

Management Tools" disk is inserted, be sure

to disable the "OS Boot Monitoring" function.

If the system is started with this function

enabled, the server may automatically turn

off or restart improperly.

If the OS Boot Monitoring function is

needed, it should be reset to enabled before

resuming normal server operation.

When setting this function, refer to

"ServerView User's Guide" to fully learn

about its specifications, in order to use it

properly with the correct settings.

Timer Count Down Value • 2 Minutes

• 5 Minutes

• 10 Minutes (Initial value)

• 15 Minutes

• 20 Minutes

• 30 Minutes

• 60 Minutes

• 100 Minutes

Sets the monitoring time of the "OS Boot

Monitoring" function.

This item appears when [OS Boot Watchdog Timer]

is set to [Enabled].

Timer Count Action • No Action

• Reset (Initial value)

• Power Off

• Power Cycle

Sets the operation when the OS did not boot

successfully within the time set with the [Timer

Count Down Value] setting.

This item appears when [OS Boot Watchdog Timer]

is set to [Enabled].

• No Action: Takes no action.

• Reset: Restarts the system.

• Power Off: urns the server off.

• Power Cycle: Turns the server off and back on

again.

219


Boot Retry Counter • No Retry

• Retry1 time

• Retry2 times

• Retry3 times (Initial value)

• Retry4 times

• Retry5 times

• Retry6 times

• Retry7 times

Sets the maximum number of retries to boot the

operating system within the range of 0 to 7.

ASR&R Boot Delay

(Minute)

2 (Unchangeable) Sets the standby time for startup after shutdown due

to trouble (such as overheating) in minutes. The

system restarts after the set standby time.

After Power Failure • Stay Off

• Last State (Initial value)

• Power On

Sets the server operation when power supply is

restored after power failure or turning on the main

power of the Chassis.

• Stay Off

The power stays turned off.

• Last State

The power state before the power failure is

restored.

• Power On

The power is turned on.

Note:

� When a UPS scheduled operation is

performed in an OS such as Windows

Server 2003 and Linux, in which the power

turns off after shutdown, set this item to

[Power On]. If this is not set to [Power On],

the server will not start up automatically at

the specified time.

table: Items on the ASR&R Submenu


220


8.2.10 CPU Status Submenu

This submenu appears when [CPU Status] is selected from the Server menu.

It configures CPU status setting.

table: Items on the CPU Status Submenu


CPU1 Status Enabled (Unchangeable) Displays the CPU status.

After replacing the CPU, set to [Enabled]. CPU2 Status


CPU Status

* CPU1 Status: [Enabled]


BIOS SETUP UTILITY

Server

If a CPU is failed butequipped, the ServiceProcessor has stoppedthe CPU on demand ordue to CPU errors.Status of empty CPUslot is unchangeable.

CPU2 Status: [Enabled]

F1

Esc


Change Option+-

General Help


Tab Select Field

221


8.2.11 Memory Status Submenu

This submenu appears when [Memory Status] is selected from the Server menu.

It configures the memory setting.

table: Items on the Memory Status Submenu


Memory Scrubbing Enabled (Unchangeable) Sets whether or not to use the Memory Scrubbing

function.

By using the Memory Scrubbing function, and

accessing each memory in order, memory errors can

be fixed.

Memory Mirror • Disabled (Initial value)

• Mirror

Sets whether or not to use the memory redundancy

function. If using the redundant memory function

installing ServerView is necessary.

DIMM 1, 2 Enabled (Unchangeable) Displays the memory status. After replacing memory, set to [Enabled].

DIMM 3, 4

DIMM 5, 6

DIMM 7, 8


Memory Status


BIOS SETUP UTILITY

Server

If enabled the wholememory will be scrubbed to preventuncorrectable memoryerrors.

Memory Scrubbing [Enabled]Memory Mirror [Disabled]

DIMM 1,2 [Enabled]DIMM 3,4 [Enabled]DIMM 5,6 [Enabled]DIMM 7,8 [Enabled]

F1

Esc


Change Option+-

General Help


Tab Select Field

222


8.2.12 Console Redirection Submenu

This submenu appears when [Console Redirection] is selected from the Server menu.

It configures detailed settings for console redirection.

table: Items on the Console Redirection Submenu


Com Port Address • Disabled

• On-board COM A (Initial value)

Sets whether or not to perform console redirection

using a serial port.

Protocol ANSI (Unchangeable) Sets a terminal type of a remote host when console

redirection is used.

This item appears when [Com Port Address] is set

to [On-board COM A].

Flow Control XON/XOFF

(Unchangeable)

Sets flow control when console redirection is set.

Only [XON/XOFF] is available in this Server

Blade.



Mode • Standard (Initial value)

• Enhanced

Sets whether or not to continue console redirection

after POST when console redirection is set.




Console Redirection


BIOS SETUP UTILITY

Server

Com Port Address [On-board COM A]Protocol [ANSI]Flow Control [XON/XOFF]Mode [Standard]

F1

Esc


Change Option+-

General Help


Tab Select Field

223


8.2.13 System Information Submenu

This submenu appears when [System Information] is selected from the Server menu.

It configures System Information setting.

table: Items on the System Information Submenu


Manufacturer - Displays the name of the installed CPU vendor.

Brand String - Displays the CPU name and frequency.

Frequency - Displays the CPU frequency.

FSB Speed - Displays the FSB speed.

Stepping - Displays the CPU stepping.

Cache L1 - Displays the L1 cache.

Cache L2 - Displays the L2 cache.

On Board LAN1 Mac

Address to On Board LAN6 Mac

Address

- Displays the MAC address of On Board LAN1 to

On Board LAN6.


System Information

Manufacturer:IntelBrand String:Genuine Intel(R) CPU 3.00GHzFrequency :3.00GHzFSB Speed :666MHzStepping :F62

Cache L1 :32 KBCache L2 :4096 KB

On Board LAN1 Mac Address: nn:nn:nn:nn:nn:nnOn Board LAN2 Mac Address: nn:nn:nn:nn:nn:nnOn Board LAN3 Mac Address: nn:nn:nn:nn:nn:nnOn Board LAN4 Mac Address: nn:nn:nn:nn:nn:nnOn Board LAN5 Mac Address: nn:nn:nn:nn:nn:nnOn Board LAN6 Mac Address: nn:nn:nn:nn:nn:nn


BIOS SETUP UTILITY

Server

F1

Esc


Change Option+-

General Help


Tab Select Field

224


8.2.14 Boot Menu

This menu sets OS startup options.

table: Items on the Boot Menu


Bootup Num-Lock • Off

• On (Initial value)

Sets NumLock state at start up.

Boot Device

Priority

- Sets from which drive and in which order the OS

should be read.

Press the [Enter] key to display the

submenu.�"8.2.15 Boot Device Priority Submenu"

(pg.225)

Hard Disk Drives - Sets the priority sequence for each device.

Press the [Enter] key to display the submenu.

"Removable Drives" and "CD/DVD Drives" are

displayed when the USB device is connected.

Removable Drives

CD/DVD Drives

Boot Device Priority Hard Disk Drives


BIOS SETUP UTILITY


Boot Settings

Bootup Num-Lock [On]

Select Power-on statefor Numlock.

F1

Esc


Change Option+-

General Help


Tab Select Field

225


8.2.15 Boot Device Priority Submenu

This submenu appears when [Boot Device Priority] is selected from the Boot menu.

It sets from which drive and in which order the OS should be read.

*1: Displayed when USB-connected floppy disk or DVD-ROM unit is connected.

*2: Displayed when the "Onboard LAN2 OPROM" setting in the Advanced menu "8.2.5 PCI Configuration Submenu" (�pg.212) is changed to [Enabled].

� Do not set a device selected in this menu to [Disabled].

table: Items on the Boot Device Priority Submenu


1st Boot Device to

5th Boot Device

(Set the boot order.)

• [USB:Y-E USB-FDU] *1

• [USB:GENERIC CDR****] *1

• [SCSI:#***ID**LUN]

• [Network:MBAv*.*.*]

• [Network:MBAv*.*.*] *2

Sets the boot priority sequence for each device.

Use the [+] [-] keys to change the order of priority for

the selected device while shifting it one by one.

You can also replace the priority order between two

devices specified in the steps below.

1. Select the first device to change the priority

sequence, and press the [Enter] key.

2. Select a device to replace the priority level with

the initially selected device, and press the

[Enter] key.

Main Advanced Security ExitServer

Boot Device Priority

1st Boot Device2nd Boot Device


BIOS SETUP UTILITY

Boot

F1

Esc


Change Option+-

General Help


Tab Select Field

4th Boot Device3rd Boot Device

5th Boot Device

226


8.2.16 Exit Menu

This menu exits the BIOS Setup Utility.

table: Items on the Exit Menu

Item Description

Save Changes and Exit Saves the current settings in CMOS and exits the BIOS Setup Utility. After it exits

the server reboots.

Discard Changes and Exit Exits the BIOS Setup Utility without saving current settings. Previously saved

settings remain valid.

Load Previous Value Sets all set values to the currently stored values.

Get Default Values Loads and displays the default settings for the server.

Save Changes and ExitDiscard Changes and ExitLoad Previous Value

Get Default Values


BIOS SETUP UTILITY


Exit Options Exit system setupafter saving thechanges.

F10 key can be usedfor this operation.

F1

Esc


Change Option+-

General Help


Tab Select Field

227

Chapter 9

Operation and Maintenance

This chapter explains the maintenance to be

performed after server operations start.

9.1 Daily Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

9.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

9.3 System Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

9.4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

9.5 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

9.6 Restoring the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

9.7 Reinstalling the OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

9.8 Maintenance Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

9.9 Maintenance & Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

228


9.1 Daily Maintenance

This section explains how to perform maintenance during operations.

� PRIMERGY information

For the latest information on PRIMERGY, update modules, drivers and the software, refer to the Fujitsu

PRIMERGY website.

http://www.fujitsu.com/global/services/computing/server/ia/driver/

Regarding BIOS and firmware, contact to Fujitsu Support Office. Refer to the following website.

http://www.fujitsu.com/global/contact/computing/PRMRGY_index.html

9.1.1 Checking the Server Condition

Use the status LED and server monitoring tool to check the server status.

� Checking each LED

This server is equipped with LEDs that display various hardware conditions.

Check the server status via each LED after starting the server. For details about the location and function

for each status display LED, refer to "1.3 Component Names and Functions" (�pg.27) and "Chapter 1

Component Names and Functions" in the "BX600 S3 Blade Server System Unit Hardware Guide".

� Server Monitoring Tool (ServerView)

ServerView is software that monitors whether the server hardware is in a normal state to protect

important server resources. When using ServerView, the server hardware is monitored all the time. Early

detection of errors is made possible because if an error that could cause trouble is detected, the

administrator is notified in real-time. This allows the server administrator to remove system errors early

and avoid trouble.

For an overview of and details about installation of ServerView and other high reliability tools, refer to

"1.2.2 High Reliability Tools" (�pg.23) and "Chapter 6 High Reliability Tools" (�pg.163).

� Check using Management Blade

The Management Blade is equipped with two management interfaces (Web UI and CLI) that enable you

to monitor whether the server hardware is running properly.

For details about the Management Blade, refer to "BX600 Management Blade Hardware Guide".



229


9.2 Troubleshooting

This section explains the corrective actions to be taken when the server is not

running properly or when error messages are displayed.

Depending on the situation, refer to the following.

• Hardware problems:

�"9.2.1 Hardware Troubleshooting" (pg.229)

• Error messages:

�"9.2.2 Error Messages" (pg.234)

• Software problems:

�"9.2.3 Software Troubleshooting" (pg.238)

If the problem is not resolved after performing the following troubleshooting, contact an office listed in

the "Contact Information" of the "Start Guide".

When contacting an office listed in the "Contact Information" of the "Start Guide", "9.8.2 Contacting

Maintenance Support" (�pg.259) and collect the required information.

� PRIMERGY information

For the latest information on PRIMERGY, update modules, drivers and the software, refer to the Fujitsu

PRIMERGY website.


Regarding BIOS and firmware, contact to Fujitsu Support Office. Refer to the following website.


9.2.1 Hardware Troubleshooting

This section explains hardware related troubleshooting. If it does not operate properly or if a failure is

suspected, check the following.

For optional devices, refer to the optional device manuals.

� Chassis

� The main power of the Chassis will not turn on, or the power LED on the front of the Chassis does not light up

• Check to see whether the power cable of the Chassis is properly connected to the outlet.

For instructions on connecting the power cable, refer to the "Start Guide".

• The main power of the Chassis may have been turned on within 2 minutes of the power cable being

connected. Turn the power on after 2 minutes has lapsed.



230


� Server Blade

� The Server Blade will not turn on, or the power LED on the front of the Server Blade does not light up

• Check whether the Server Blade is securely installed in the Server Blade slot of the Chassis.

• Check whether the main power of the Chassis is turned on.

• Check to see whether the power cable of the Chassis is properly connected to the outlet.

For details, refer to the "Start Guide".

� The Server Blade will not turn on, or the KVM select LED blinks

Check whether the number of installed Server Blades exceeds the limit

For details, refer to "4.2 Installing Server Blades/Storage Blades" in "BX600 S3 Blade Server System

Unit Hardware Guide".

� The hard disk access LED does not light up

The Server Blade may be damaged. Contact an office listed in the "Contact Information" of the "Start

Guide".

When contacting an office listed in the "Contact Information" of the "Start Guide", refer to "9.8.2

Contacting Maintenance Support" (�pg.259) and collect the required information.

� An error message is displayed

Refer to "9.2.2 Error Messages" (�pg.234).

� The LAN does not operate properly

The Switch Blade may not be running properly. Check the Switch Blade settings.

� Switch Blade

If there is a problem with network connection, first check the wiring and confirm that the device is

normally connected to network.

If the error still occurs, refer to the following.

� Switch indicator diagnosis

There is a device connected to a port of the Switch Blade, but the link LED is

off

• Check that the Switch Blade and connected device are turned on.

• Check that the cable is connected to both the Switch Blade and device.

• Check that the cable type is appropriate and the cable length does not exceed the allowable range.

• Check that there are no defects in the connection between the cable and adapter of the connected

device. Replace the defective cable or adapter as required.

• Check that all the system components are installed correctly. If the network cable does not function

normally, execute a test in an environment where all the components other than the cable function

normally.

231


� There are problems accessing the management interface

The management interface of the switch board can be accessed from anywhere in the connected network

using Telnet, Web browser, or SNMP-based network management software.

If there are problems accessing the management interface, check the following.

Cannot connect to the Switch Blade using Telnet, Web browser, or SNMP

software

• Check that the appropriate IP address, subnet mask, and default gateway are set to the agent.

• When connecting to the agent with the IP address in the tagged VLAN group, check that the

management station includes an appropriate tag in the sending frame.

• Check that the Switch Blade is appropriately connected to network, and also check that the port used

is enabled.

• Check the network cable between the management station and Switch Blade.

• If connection using Telnet cannot be enabled, four active sessions may already be opened. Try

connecting after waiting for a while.

• When using a spanning tree, check the connection state 30 seconds after the cable has been

connected.

Cannot access the setup screen of the Switch Blade in the serial port

connection of the Management Blade

Check that serial port and terminal emulator settings are correct by referring to "BX600 Management

Blade Hardware Guide".

Forgot or lost your password

Refer to the Switch Blade manual, and perform password initialization of the Switch Blade that will be

used.

Failed to open the management screen using the Web browser during

connection with the network

• Switch Blade may not reboot when the Management Blade console redirection function is used. Exit

Console Redirection temporarily.

• Main power could be off when using the Management Blade console redirection function. Exit

Console Redirection temporarily.

� Other

Communication failure between the Switch Blade and connected switch

occurred

Is the LAN cable connected using wiring that causes a network loop? Review the connection, or enable

spanning tree settings between the cable and switch.

232


� Display

� The display will not turn on

Check to see whether the power cable of the display is properly connected to the outlet.

For instructions on connecting the power cable, refer to the "Start Guide" as well as the manual of the

display.

� Nothing is displayed on the screen

• Check to see whether the KVM select LED of the Server Blade that you wish to display the screen

lights up green. When the LED does not light up, press the KVM select switch.

• Check to see whether the cable of the display is properly connected to the outlet. If it is not

connected, turn the server off, and correctly connect the cable.

• For instructions on connecting the cable, refer to the "Start Guide".

• Check that the brightness volume and contrast volume of the display are adjusted correctly. If they

need to be adjusted, perform the necessary adjustments.

For details, refer to the manual of the display.

• There may be an error in the system area of the memory. Contact an office listed in the "Contact

Information" of the "Start Guide".

� Typing the keyboard does not display any characters, or the mouse cursor does not move

• Check to see whether the keyboard and mouse are connected properly. If they are not connected, turn

the server off and then connect the cables to the server.

For the connection procedures, refer to the "Start Guide".

• Another server blade may be selected by the KVM select function. Press the KVM select switch.

� The screen shakes

If an object that produces a strong magnetic field such as a television or a speaker is near the display,

move it further away from the display.

The display may also shake if a nearby cell-phone receives a call. Do not use a cell-phone near the

display.

� The screen display is distorted

During 3D program execution in Windows Server 2003, Windows Server 2003 R2, Windows Server

2003 x64, or Windows Server 2003 R2 x64, the screen display may malfunction or the 3D program may

terminate abnormally. If this occurs, set Color quality in screen properties to anything other than True

Color (32 bits).

233


� Floppy disk drive

� Cannot read or write to the floppy disk

Prolonged use of the floppy disk drive accumulates dust on the device head (the part which reads/writes

data). A dirty head can impair the ability to read/write data to/from a floppy disk correctly.

Clean the head once every three months.

� Cannot write to the floppy disk

• Check to see whether the floppy disk drive is properly connected to the Server Blade.

For more information on the connection procedures, refer to the "Start Guide".

• The write protection of the floppy disk may be applied.

Flip the switch on the disk to allow writing.

� CD/DVD drive

� Cannot read data

• Check to see whether the CD/DVD drive is properly connected to the Server Blade.

For more information on the connection procedures, refer to the "Start Guide".

• The CD/DVD drive may not properly be recognized on the OS. Check the settings.

For details, refer to the CD/DVD drive manual.

• Check to see whether the CD/DVD is inserted properly. If it is not, correctly insert the CD/DVD so

that the label is facing up.

• Check to see that the CD/DVD is not dirty. If it is dirty, wipe it with a soft, dry cloth.

• Check to see that the CD/DVD is not scratched or bent. If scratched or damaged, replace the CD/

DVD.

� The unit does not operate properly

• Check to see whether the cable is connected properly. If it is not, correctly connect the cable.

For more information on the connection procedures, refer to the "Start Guide" and the CD/DVD drive

manual.

� SCSI device (internal/external)

� The unit does not operate properly

• Check to see whether the SCSI cable is connected properly. If it is not, correctly connect the cable.

• For more details on the internal hard disk unit, refer to "7.7 Installing an Internal Hard Disk Unit"

(�pg.197).

• Check that the jumper pins are set correctly. Set them if they are not set correctly.

• Check that the SCSI-ID and terminator are set correctly. Set them if they are not set correctly.

234


9.2.2 Error Messages

This section explains the error messages for this server.

� POST error messages

If an error occurs during Power On Self Test, a device check performed during the server startup,

(POST), deal with it according to the following table.

� When checking/changing the settings of the BIOS Setup Utility, refer to "8.2 BIOS Setup Utility"

(�pg.205).

� For instructions on checking peripheral connections, refer to the "Start Guide".

� For details on installing internal options, refer to "Chapter 7 Installing Internal Options" (�pg.171).

table: List of POST Error Messages

Message Contents and troubleshooting

Boot Failure OS booting has failed.

Check to see whether the drives (hard disk, CD/DVD drive,

floppy disk drive, etc.) and cables to be used for booting have no

error. If the message still appears, the Server Blade must be

replaced. Contact an office listed in the "Contact Information"

of the "Start Guide".

Invalid Boot Diskette Booting disk error has occurred.






Reboot and Select proper Boot device or Insert Boot

Media in selected Boot device and press a keyNo drive to boot OS is detected.






Interrupt Controller-1 error An interrupt controller error has occurred.

The Server Blade must be replaced. Contact an office listed in

the "Contact Information" of the "Start Guide".Interrupt Controller-2 error

CMOS Battery Low CMOS battery (button battery) is close to burned out. Contact

an office listed in the "Contact Information" of the "Start

Guide".

CMOS Checksum Bad A CMOS setting or checksum error has occurred.

Correct the current settings using the BIOS Setup Utility or

restore the default settings.

If the message still appears, the Server Blade must be replaced.

Contact an office listed in the "Contact Information" of the

"Start Guide".

CMOS Date/Time Not Set The time and date may not be set. Enter the correct time and

date on "8.2.2 Main Menu" (�pg.208) of the BIOS Setup

Utility.

235


NVRAM Checksum Bad, NVRAM Cleared A NVRAM checksum error has occurred.

Replace the Server Blade. Contact an office listed in the

"Contact Information" of the "Start Guide".

Keyboard/Interface Error The keyboard or keyboard connector is not connected properly.

Check to see whether the keyboard is connected properly. If the

message still appears, replace the key board, Server Blade, or

KVM module. Contact an office listed in the "Contact


Cache Memory Error A cache memory error in the CPU has occurred.

Replace the CPU. Contact an office listed in the "Contact


Gate20 Error A chip set error has occurred.



DMA-1 Error A DMA error has occurred.


the "Contact Information" of the "Start Guide".DMA-2 Error

DMA Controller Error

Resource Conflict A conflict occurred between resources.





"Start Guide".

Static Resource Conflict

PCI I/O conflict: A conflict occurred between PCI settings or an error has

occurred.

Replace the Server Blade. Contact an office listed in the

"Contact Information" of the "Start Guide".

PCI ROM conflict:

PCI IRQ conflict:

PCI IRQ routing table error

No enough Space to copy PCI Option ROM

Warning:Now CPU1 Max support Freq. doesn't

match with last time.

Press F1 use the present CPU1 or shutdown to change

CPU1.

A CPU error has occurred.



If the message still appears, replace the faulty CPU.



"Start Guide".

Warning:Now CPU2 Max support Freq. doesn't

match with last time.

Press F1 use the present CPU2 or shutdown to change

CPU2.

CPU Mismatch Error: CPU1 and CPU2 Frequency

mismatch!CPUs with varying frequencies are installed together.



If the message still appears, replace the faulty CPU.

If the message still appears, the baseboard must be replaced.


"Start Guide".

CPU Mismatch Error: CPU1 and CPU2 Stepping

mismatch!

CPU Mismatch Error: CPU1 and CPU2 System Bus

Frequency mismatch!

CPU Mismatch Error: CPU1 and CPU2 Cache Size

mismatch!

H/W malfunction! A hardware error has occurred.



Warning:DIMM Type Mismatch, has Log. The

DIMM has been Disabled!

Varying types of memory modules have been installed together.

Check the system event log and replace memory in the bank.



236


� Server Management Tools error messages

The following error messages may appear while executing Server Management Tools. In such cases,

perform the corresponding corrective actions. If messages other than the following are displayed,

contact an office listed in the "Contact Information" of the "Start Guide".

Warning:Memory Mirror Feature could not be

enabled.

Since the memory configuration is invalid, the memory

redundancy function is not available.

When using the memory redundancy function, check that two or

more even numbers of memory banks of the same size are

installed.

When not using the memory redundancy function, check that

[Memory Mirror] is set to [Disabled] in "8.2.11 Memory Status

Submenu" (�pg.221) on the [Server] menu of the BIOS Setup

Utility.



"Start Guide".

Warning:DIMM Type mixed has Log. The DIMM has

been Disabled!

Varying types of memory modules have been installed together.

Check the system event log and replace memory in the bank.

table: Server Management Tools: List of Error Messages

Message Description

Write protect error writing drive A.

Abort, Retry, Fail?

The inserted floppy disk is write-protected. Disable the

write-protect, and then press the [R] key.

Not ready writing drive A.

Abort, Retry, Fail?

The floppy disk is not inserted into the floppy disk drive.

Insert the proper floppy disk ("Server Management Tools"

disk), and then press the [R] key.

ERROR:Fail to create data file. The following are possible causes. Check the floppy disk

status.

• The floppy disk is write-protected. Disable the write-

protect and retry.

• The floppy disk is not inserted into the floppy disk drive.

Insert the proper floppy disk, and then retry.

• There is an error in the contents of the floppy disk. Create

the "Server Management Tools" disk again. If this

occurred while recovering BIOS information, configure

the information using the BIOS Setup Utility. Then store

the BIOS information.

ERROR:Fail to write 1st CMOS data into data

file. nn

ERROR:Fail to write 2nd CMOS data into data

file. nn

ERROR:Fail to write ESCD data into the data

file. nn

ERROR:Fail to write SEEPROM data into the

data file. nn

ERROR:Fail to open data file. The file for recovering the BIOS information does not exist

on this floppy disk. Insert the floppy disk on which the BIOS

information was stored, and then retry.

ERROR:Fail to write 1st CMOS data into system. The following are possible causes. Check the floppy disk

status again.

• The floppy disk is not inserted into the floppy disk drive.

Insert the proper floppy disk, and then retry.

• A different model or an unsupported version of BIOS

information. Insert the proper floppy disk, and then retry.

• There is an error in the contents of the floppy disk. Create

the "Server Management Tools" disk again. If this

occurred while recovering BIOS information, configure

the information using the BIOS Setup Utility. Then store

the BIOS information.

ERROR:Fail to write 2nd CMOS data into

system.

ERROR:Fail to write ESCD data into system.

ERROR:Fail to write SEEPROM data into

system.



237


Other messages Contact an office listed in the "Contact Information" of the

"Start Guide".

table: Server Management Tools: List of Error Messages

Message Description

238


9.2.3 Software Troubleshooting

This section explains software-related troubleshooting. For troubles during OS installation or system

operation, refer to the following contents.

� Trouble at a ServerStart startup

� After a boot from PRIMERGY Startup Disc, nothing is displayed on the screen.

This situation may occur if the hard disk drive still contains the previous information. In that case, this

situation may occur even when insert Windows Server 2003 installation disc.

In such a situation, physically format the hard disk drive to delete the previous information and start up

ServerStart.

For physical formatting for hard disk drive, refer to the manual in the Array Controller Document &

Tool CD.

For the manual of the SAS RAID Ctrl to be used, refer to "2.3.2 Notes on Configuring RAID" (�pg.42)

� Error messages during installation

The following error messages may appear during installation using ServerStart. Observe the corrective

action against the relevant error.

� "WzDiskAdmin: System Error! ......................, Last Error: The device is not ready." appears

Optional SCSI/SAS devices (e.g., hard disk cabinet, DAT unit) may be connected.

Disconnect the optional SCSI/SAS devices and perform installation again. Connect the optional devices

after the installation completes.

� "Operating System not found" appears when the system restarts from the CD/DVD after file copy

The following factor may be possibly root cause.

• The Active flag is selected.

� "Missing Operating System" appears during installation

The installation partition size may be too large. Specify the installation partition size correctly. For

details on the installation partition size, refer to "2.3.1 Installation Partition Size" (�pg.42).

� "Error 1920. Service (PXE Services) failed to start" appears during preconfigured installation

The system installed with the preconfigured settings (PXE server) may not be connected to the network.

Check the LAN cable connection and click [Rerun].

239


� Application software which uses tftp client function (tftp.exe) does not operate properly

For the system on which Windows Server 2003 is installed, since the tftp client function (tftp.exe) is not

installed by default, and application software which uses the tftp client function (tftp.exe) does not

operate properly. To use the tftp client function (tftp.exe), install "tftp.exe" from the OS installation disc

according to the following procedures.

1 Insert the OS installation disc into the CD/DVD drive.

The OS installation disc must be any of Windows Server 2003 CD that has applied SP1,

Windows Server 2003 x64 DVD or Windows Server 2003 R2 Disc 1 CD-ROM.

2 Start the Command Prompt and move to the i386 folder of the CD/DVD drive.

3 Execute the following command to extract "tftp.exe" in the

"%Systemroot%\system32" folder.

4 Confirm that "tftp.exe" exists in the "%Systemroot%\System32" folder.

� Error window appears after installing or uninstalling ServerView (For Windows Server 2003)

For Windows Server 2003 with Service Pack 1 applied, the following message may appear on restarting

after installing/uninstalling ServerView. The operation will run properly. Click [Close Message] to close

the message..

� Error window appears after LAN driver installation (For Windows Server 2003)

The following window may appear when the installation of the LAN driver to the [Ethernet controller]

under [Other devices] starts.

[CD/DVD drive]:\i386>expand -r:tftp.exe TFTP.EX_ %Systemroot%\system32

In order to protect the computer, this program is terminated by

Windows. Name: SNMP Service

240


This error results from that the LAN driver for the network adapter recognized immediately after the OS

installation is not updated.

Clicking [Finish] in this window displays the [Help and Support Center] window. Click [X] to close this

window. The "!" mark is displayed at the LAN device name in Device Manager. The device names are

displayed properly when all the LAN drivers are installed and the system is restarted.

� LAN operation fails or error message appears during LAN driver installation

A conflict may have occurred between system resources including the LAN and other expansion cards.

Delete all the LAN drivers and check that conflicts between system resources do not exist. Then, restart

the system and reinstall the LAN drivers again.

� Event log errors after installation

After installation, the following events may be displayed in Event Viewer. Check and perform the

corrective action against the relevant event.

� Cannot collect the memory dump

If the memory dump file cannot be created, perform the following procedures.

� Correcting the settings

If the memory dump cannot be collected, check the settings of the paging file and memory dump file.

For setting procedures, refer to "5.1 Memory Dump/Paging File Setting" (�pg.100).

table: List of event log errors that may occur after Installation

ID Description Cause and corrective action

62 This computer is a domain PDC at the

root of forest. Use the net command

"net time /setsntp:<server name>" to

configure it for synchronization from

an external time source.

Cause: An NTP was selected as a component.

Corrective action:

ServerStart cannot configure the NTP server due to the

absence of items for specifying it. After OS installation,

perform the following procedure to specify the time server.

1. Start SNTP server operation on another machine.

For example, the SNTP server address is

<172.22.78.246>.

2. Enter the following at a Command Prompt.

net time /setsntp:172.22.78.246

w32tm -s 172.22.78.246

1000 The user or computer name cannot be

identified. The return value is "1722".

Cause: The primary DNS server address may be invalid or the server

cannot be accessed.

Corrective action:

Perform the following procedures to correct the DNS address

in Internet protocol (TCP/IP) properties.

1. Right-click [My Network] and click [Properties].

2. Right-click [Local Area Connection] and click

[Properties].

3. Click [Internet Protocol (TCP/IP)] and click

[Properties].

4. Enter the correct DNS address in the [Primary DNS

server] box.

241


� Collecting memory dump to other than the system drive

If the memory dump is set to be collected to the system drive (C:\), change the settings so that the

memory dump can be saved to a drive other than the system drive. For setting procedures, refer to "5.1

Memory Dump/Paging File Setting" (�pg.100). If only the system drive exists, or if there is no free

space in any of the drives, perform one of the following:

• Adding a hard disk unit

• Replacing with a higher-capacity hard disk unit

� Reducing the installed memory to collect the memory dump

There must be enough free disk space that matches the size of the installed memory; therefore, reduce

the installed memory to a collectable size. Check the memory dump settings when changing the installed

memory size.

For setting procedures, refer to "5.1 Memory Dump/Paging File Setting" (�pg.100).

� Changing the write type of the debugging information

If the memory dump cannot be collected, select a write type of debugging information within the range

of free space of the volume size. If the above does not provide a solution, try increasing the size of the

hard disk or adding an additional hard disk unit. For setting procedures, refer to "5.1 Memory Dump/

Paging File Setting" (�pg.100).

� Restoring the system

In the event where the system file, system configuration, or environment changes during startup are

corrupted, use the repair information stored on the repair disk created at the installation to restore the

system. For restoration procedures, refer to the following:

• "9.6.1 For Windows Server 2008" (�pg.254)

� SNMP service startup fails

If the Simple Network Management Protocol (SNMP) is installed, but has not started, perform the

following procedures to start the service.

1 Click [Start] – [Computer Management].

2 Select [Services] on the [Services and Applications] menu.

3 On the details, select [SNMP Service].

4 Select [Start] on the [Action] menu.

� To have the service automatically start each time the OS starts, double-click [SNMP Service] on the

details, and select [Automatic] for the [Startup type] setting of the [SNMP Service Properties] window.

242


� Time display in Linux OS environment

� Difference in time between the OS and the hardware clock

Since the software clock on OS is employed but not the hardware clock functioned in the server for time

display in Linux environment, time -lag may occur between the OS and the hardware clock.

When time precision is required on OS, it is recommended to use the NTP service to periodically correct

the time displayed on the OS.

� Changing the time settings for the OS and hardware clock

In a Linux environment, the time displayed on the OS (the software clock value on the OS) is written to

the hardware clock in the server when the OS is shut down.

• Procedure for prohibiting the time on the OS from being written to the hardware clock

When you do not want the time on the OS to be written to the hardware clock at an OS shutdown,

comment the following line out in /etc/rc0.d/S01halt.

runcmd $"Syncing hardware clock to system time" /sbin/hwclock $CLOCKFLAGS

↓

#runcmd $"Syncing hardware clock to system time" /sbin/hwclock $CLOCKFLAGS

• Procedure for reflecting the hardware clock value to the time on the OS

To reflect the hardware clock value to the software clock value on the OS, run the following

command.

>hwclock --hctosys

243


9.3 System Event Log

To operate system event log, use Server Management Tools

This section explains how to use Server Management Tools.

� The server settings are set so that when the System event log area in the server becomes full a new

event log is automatically written over the old log areas.

9.3.1 Server Management Tools

Server Management Tools perform the following to the system event log stored in the Baseboard

Management Controller (BMC: a micro-controller used for managing the baseboard environment, such

as its temperature and voltage sensors).

• Viewing the system event log

• Saving the system event log

• Deleting the system event log

When an system event log occurs, save the log using Server Management Tools and contact an office

listed in the "Contact Information" in the "Start Guide".

� The system event log of this Server Blade can be viewed from the management terminal via the

Management Blade.

→ "BX600 Management Blade Hardware Guide".

� The "Server Management Tools" disk is for this Server Blade only. Do not use those tools on other

systems. If it is used, the system may be damaged.

� To execute the Server Management Tools, follow the startup procedure shown in "9.3.2 Starting and

Exiting Server Management Tools" (�pg.244) to start the Server Blade. Do not run this tool on the

server started from the hard disk drive or other floppy disks. Otherwise, the system may be corrupted.

� Do not eject the floppy disk when the floppy disk access LED is on. Doing so may destroy the data on

the floppy disk.

244


9.3.2 Starting and Exiting Server Management Tools

The steps for starting and exiting Server Management Tools are as follows:

� Preparation for using Server Management Tools

To use Server Management Tools, prepare the "Server Management Tools" disk of the server at hand.

Use the Display/USB Extension Cable to connect to the floppy disk drive to the Server Blade.

For details, refer to the "Start Guide".

� Starting Server Management Tools

� Before starting up the system from the "Server Management Tools" disk, first check that the

ServerView "OS Boot Monitoring" function is disabled (default setting is "Disabled").

If you start up the system while the "OS Boot Monitoring" function remains enabled, the operation of

the Server Blade may become unpredictable at such times as an abrupt power interruption or restart.

If the "OS Boot Monitoring" function is needed, it should be reset to enabled before resuming normal

server operation. For details of ServerView, refer to "ServerView User’s Guide".


floppy disk drive.





Please select:

1 = JP Keyboard

2 = US Keyboard

Your selection

245




Enter the following command and press the [Enter] key.

A:\>ipmiview

Server Management Tools menu appears.

4 Select an item using [↑] or [↓] and press the [Enter] key.

The screens that can be displayed are shown.

� Only the following function is supported by Server Management Tools:

• System Event Log (SEL)

Operations of other items are not ensured.

� Key operations

The following shows the key operations in the menu window of Server Management Tools.

� Exiting Server Management Tools

Press the [Esc] key once in the menu window of Server Management Tools.

The power can be turned off when the DOS prompt is displayed.

table: List of Server Management Tools key operations

Key Roles of key

[↑][↓] Selects an item.

[Enter] Executes the selected item.

[Esc] Exits Server Management Tools.

General InformationTemperature InformationFan InformationVoltage InformationSystem Event Log (SEL)FRU Information (ID Proms)FSC/System Specific Functions

FUJITSU SIEMENS COMPUTERS

IPMI-Tool - Vn.nn

< > Select <ENTER> Start <ESC> Exit

246


9.3.3 Viewing/Saving/Deleting the System Event Log

Viewing, saving, and deleting the system event log is performed in the System Event Log (SEL)

window.

� Starting the [SYSTEM EVENT LOG (SEL)] window

1 Start Server Management Tools.

2 Select [System Event Log (SEL)], and press the [Enter] key.

The [SYSTEM EVENT LOG (SEL)] window appears.

� Key operations

The following shows the key operations in the System Event Log (SEL) window.

� Saving logs

1 Press the [F2] key in the System Event Log (SEL) window.

2 Enter the name of the file to save the log, and press the [Enter] key.

The logs are saved on a floppy disk with the specified file name.

table: List of System Event Log (SEL) window key operations

Key Roles of keys

[↑], [↓], [←], [→], [PageUp], [PageDown], [Ctrl]+[Home], [Ctrl]+[End]

Scrolls the screen.

[Esc] Ends the System Event Log (SEL) window and returns to the

Server Management Tools menu window.

[F2] Saves log.

[F3] Erases log.

004 MMM-DD-YYYY HH:MM:SS [*****] ****************************************003 MMM-DD-YYYY HH:MM:SS [*****] ****************************************002 MMM-DD-YYYY HH:MM:SS [*****] ****************************************001 MMM-DD-YYYY HH:MM:SS [*****] ****************************************000 MMM-DD-YYYY HH:MM:SS [*****] ****************************************


SYSTEM EVENT LOG (SEL)

< ,PgUp/Dn,(Ctrl-)Home/End> Move <F2> SaveToFile <F3> Clear <ESC> Exit

247


� Deleting logs

When number of system event logs reaches the maximum (254 logs), the oldest log is overwritten with

the newest log.

Periodically start Server Management Tools to check the system event log and save/delete logs as

necessary.

The following shows the steps for deleting an event log.

1 Press the [F3] key in the System Event Log (SEL) window.


2 Press the [Enter] key.

This deletes the system event log.

� If you continue operations with event logs full, it is difficult to remedy a fault. Event logs should be

periodically saved and deleted.


<ENTER> Clear SEL <ESC> Exit

SYSTEM EVENT LOG (SEL)

248


9.4 Security

Security features are provided in order to protect the Server Blade hardware and

software resources from theft. Additional security functions against unauthorized use

provided by the BIOS Setup Utility, etc. are also available to help maintain a highly

reliable data security system.

9.4.1 Hardware Security

For details on the hardware security, refer to "2.1 Hardware Security" in the "BX600 Management Blade

Hardware Guide".

9.4.2 Security against Unauthorized Use

A password can be set to prevent unauthorized use of the Server Blade.

When a password is set, the server is accessible to only the users who know the password.

The password is set in the BIOS Setup Utility. For details on the BIOS Setup Utility, refer to "8.2 BIOS

Setup Utility" (�pg.205).

� Password types

The following two types of password can be set in this Server Blade.

The type of password defines the privileges of server operations.

� Supervisor password (Administrator password)

This is the password that allows specific persons to access the BIOS setup.

Unless the set password is entered, the BIOS setup cannot be accessed and the OS cannot be booted.

� User password (User password)

This is the password that allows specific persons to use the Server Blade.

Unless the set password is entered, part of the BIOS setup cannot be accessed and the OS cannot be

booted.

249


� Setting a password

1 Start the BIOS Setup Utility.


2 Use the [←] [→] keys to select [Security] from the [Main] menu and press the

[Enter] key.

The [Security] menu appears.

3 Use the [↑] [↓] keys to select the type of password to set.

• When setting an administrator password

Move the cursor to [Change Supervisor Password] and press the [Enter] key.

• When setting a user password

Move the cursor to [Change User Password] and press the [Enter] key.

The password entry window appears.

4 Enter a password in the [Enter New Password] up to six alphanumerical

characters.

Blocks are displayed instead of the letters entered.


To cancel the password setting, press the [Esc] key.

6 In the [Confirm New Password] field, enter the password you have entered in

Step 4 and press the [Enter] key.

Display in [Supervisor Password] or [User Password] changes from [Not Installed] to [Installed].

� Logging on as a user enables you to set the user authority only, such as user password.

� Changing and deleting a password

If a password is already set, you can change or delete it in [Change Supervisor (User) Password].

1 When changing a password, enter a new one in the [Enter New Password] field

on the password entry screen.

When deleting a password, execute step 3 without entering any characters.

2 When changing a password, enter the password entered in step 1 in the

[Confirm New Password] again.

When deleting a password, execute step 3 without entering any characters.


When the password is deleted, [Not installed] is displayed in [System Password] or [Setup

Password] of the [Security] menu.

250


� The system shuts down after three invalid password entries. If this happens, turn off the Server Blade,

turn it back on, and then enter the correct password.

� If you forgot your password and cannot start the Server Blade, clear the CMOS with the switch block

on the Server Blade to delete the password. After the CMOS has been cleared, restore the BIOS

settings (�"8.1 Switch Block Settings" (pg.204)).

After this, return switch block settings to the original settings and use this utility to set a password.

9.4.3 Security When Disposing of the Server

� Notes regarding the deletion of data from the hard disk when disposing of or transferring the server

When disposing of or transferring a server that has been used, the data in the hard disk may be read and

used for unforeseen purposes. To prevent confidential or important data from leaking out, the data on the

hard disk must be wiped before disposal or transfer.

However, wiping the hard disk is not an easy task. Simply initializing (formatting) the hard disk or

deleting the files may give the pretense that the data no longer exists, but in reality the data is simply no

longer accessible to the OS. However, it is still accessible to malicious individuals that can restore the

data.

Therefore, if confidential or important data is saved to the hard disk, in addition to the operations

mentioned above, it is recommended to use third-party tools or services to wipe the data completely

from the disk to prevent its restoration.

When disposing of or transferring the server, it is the customer's responsibility to wipe data contained in

the hard disk in order to prevent such important data from leaking.

Also, if software license agreements prohibit unauthorized distribution of software (OS or application

software), transferring the server without removing the software may violate the license agreements.

These issues must be taken into consideration.

251


9.5 Backup

This Server Blade utilizes high reliability components and hard disks, however, as a

precautionary measure, it is recommended that periodic backups be made of the

data.

9.5.1 Importance of Backups

If the data on the server is backed up, it can be restored from the backup data in the event of data

corruption in hard disk units due to hardware failures or operational errors. If backup are not created,

restoration is impossible and your important data will be lost permanently. For anxiety-free system

operation, be sure to perform periodic backups of the system.

9.5.2 Backup Devices, Software and Their Operations

Backup operations differ depending on network operating systems, applications, and system operations.

Contact an office listed in the "Contact Information" in the "Start Guide" and make backups using the

following items.

• Backup device (e.g., DAT72 unit)

• Backup software (Standard backup software supplied with the OS, software for tape backup, etc.)

� The Windows Server Backup function that is standardly provided with Windows Server 2008

can be used. However, backup to a tape library cannot be performed using the Windows

Server Backup function.

• Backup operations (schedules)

Use our genuine backup devices and software. Observe the backup medium (tape) storage conditions.

Mirroring/disk array systems

� To improve system reliability, a mirroring or disk array system is recommended in addition to periodic

backup creation.

252


� Notes on operating backups

Notes on using backups are as follows.

For details, refer to the device manuals.

� Head cleaning

Airborne dust and dust from the magnetic media can collect on the head of the magnetic tape device. To

remove this dust, head cleaning must be implemented. Implement head cleaning when the device

displays a cleaning request. Particularly DDS devices require periodic head cleaning, otherwise dust can

cling to the magnetic head, creating a situation that cannot be cleaned using standard head cleaning

methods, and eventually render the device useless.

Also note that there is a limit to how many times the cleaning media can be used.

Using cleaning media that has exceeded its life span will have no cleaning effect. Note these points

especially when performing automatic backups with library devices.

� Managing media life span

Media is a consumable product that must be replaced regularly.

Continued use of media exceeding its life span can have negative effects on the device (e.g. increase the

speed of dust accumulation).

The life span of media varies depending on the environment and operating conditions of the device, the

type of backup software used, and other operating conditions, however, it is recommended that they be

replaced sooner than later.

As a guide to when the life span of the media will expire, write the date it was first used on the media.

� Rotating media

Perform backup operations using multiple mediums on a rotating basis.

When using a single media cartridge repeatedly, backup data can be temporarily lost in the event the

backup fails. Also if the hard disk fails during backup, the backup data cannot be recovered.

� Avoid leaving media in devices

Because the magnetic recording surface of the device is exposed, media can be easily affected by

airborne dust when left inserted for a long period of time. Insert the media before using it, and remove

the media after use, and then restore it to its case.

Also note that some tape devices write management information to the tape when ejecting the media. If

the power were to go out when the media is still in the device, this writing process will not be performed

and the media may become corrupted.

To avoid this, remove the media from the device when turning off the server/device.

� Verifying data after backup

Some backup software products provide data verification functions after backup is completed. Such

functions will read and verify the data written to the media after backup is completed. This will increase

the usage of the media, thus reducing the number of times it can be used for backups.

Depending on the hardware being used, some devices perform "read after write" operations on data; note

the points of this section as necessary.

253


� Ejecting media after backup

Some backup software products provide functions for ejecting media after backup is completed. Such

functions will rewind the tape after backup is completed and then eject the media from the drive.

Be sure to execute this function for autoloader/library devices. Depending on the structure of some

servers, this function may cause the media to be ejected from an internal device of the server and hit the

Chassis cover. If this is the case, open the cover when ejecting, or do not eject the media.

� Media label types and positions

When writing information such as the name on media, use the label that came with the media.

The area in which a label can be posted on the media of each device varies.

Failing to post labels in the designated area can damage the device.

� Data storage

When storing data for long periods of time, store the media in a location not affected by humidity and

magnetic fields.

254


9.6 Restoring the system

If the system is damaged, use the backup data created after the installation to restore

the system.

� Backup data for system recovery must be created in advance. For the procedure for creating it, refer to

"5.2 Creating Backup Data for System Recovery" (�pg.107).

� When using the backup device, refer to the manual provided with the backup device or Readme.txt

included in the device driver.


The whole server can be restored using the Windows Server Backup function.

� Items required

• Windows Server 2008 DVD-ROM (Installation disc)

• Backup data created using the Windows Server Backup function (connectable shared folder, DVD,

etc.)

1 Insert the Windows Server 2008 DVD-ROM (Installation disc) immediately after

turning on the server.

Check that there is not already a floppy disk inserted in the floppy disk drive at this time.

2 When active area is specified on the hard disk, the following message is

displayed on the bottom of the window. Press any key while the message is

displayed.

The Windows Server 2008 setup window appears.

Press any key to boot ...

255


3 Click [Repair your computer] displayed in the bottom left of the window.

4 Click [Windows Complete PC Restore].

When using a shared folder to restore the system, the message [Valid location for backup cannot

be found.] is displayed. Click [Cancel].

5 Specify the backup type, and click [Next].

When backup data is in a folder on another machine, or when the backup data is not the latest

data, select [Restore specific backup].

In this case, the window to specify a restoration target appears after clicking [Next].

Select the backup to be restored and click [Next]. When the backup data is stored on the network,

specify the shared folder in which the backup data is stored from [Advanced Settings].

The window to set the restoration options appears.

6 Perform the settings as required, and click [Next].

The restoration settings completion window appears.

256


7 Click [Finish].

The restoration start window appears.

8 Check the checkbox, and click [OK].

System restoration starts.

After the restoration has completed, the system is automatically rebooted. After rebooting, the

system is restored using the backup data.

� For operation with a BitLocker drive encryption set, perform the encryption settings again after

the system restoration.


• Items required

• Windows Server 2003 CD/DVD

• Automated System Recovery (ASR) floppy disk (created beforehand)

• Backup media (created beforehand)

• Driver disk (for onboard SCSI or onboard array)

For details on the driver to be used, refer to "4.2.4 Installing Windows Server 2003" (�pg.86). For

how to create driver disks, refer to "4.1 Creating Driver Disks" (�pg.70).

1 Insert the Windows Server 2003 CD/DVD after turning on the server.

Check that there is not already a floppy disk inserted in the floppy disk drive at this time.

2 When a message prompting you to press the [F6] key appears immediately

after the start of setup, press the [F6] key.

3 When a message prompting you to press the [F2] key appears, press the [F2]

key.

A message prompting you to insert the ASR floppy disk appears.

4 Insert the ASR floppy disk and follow the window instructions.

5 The system restarts and a message appears. Press the [F6] key.

6 Follow the window instructions to restore the system.

Notes on Automated System Recovery

� Automated System Recovery does not restore data files.

257


9.7 Reinstalling the OS

This section explains the procedure for reinstalling the OS.

9.7.1 Checking before OS Reinstallation

� Deletion of data from the disk

Reinstallation deletes all disk contents. Save the necessary data and system configuration in a different

location.

� Other notes

Any remaining notes are the same as those for initial installation. Make sure to check the settings in

advance.

258


9.8 Maintenance Service

This section explains the details of the maintenance service.

If the cause of the failure is uncertain or if the original condition cannot be restored,

contact an office listed in the "Contact Information".

For details about contact information, refer to the "Start Guide".

9.8.1 Maintenance Service

� Maintenance support period

The maintenance support period is for five years after the purchase of the server.

� Non-durable components

Depending on the environment and period of usage there will be non-durable components that require

replacement within the warranty period.

Customer's who have signed up to hardware maintenance contract will be provided with replacement

parts free of charge and will have higher priority for replacement. Customer's not signed up to hardware

maintenance contract will be charged for operation cost (including the maintenance parts) separately.

Replacing non-durable components

� To ensure stable operation of the server system, it is recommended that a maintenance service

agreement be purchased.

� Lifetime of non-durable components

The lifetime of such components is calculated based on appropriate usage environments.

Although the guaranteed range for operation is set between 10 and 35 °C, the lifetime is assumed at a

constant average temperature of 25 °C.

� For details about Chassis non-durable components, refer to "6.5 Non-durable Components" in BX600

S3 Blade Server System Unit Hardware Guide".

259


9.8.2 Contacting Maintenance Support

Before contacting maintenance support, check the following.

� Fill in the "Configuration Sheet" and "Accident Sheet" of "Configuration Sheets".

� Item

• Model name and product ID of the Chassis

They are indicated on the label on the Chassis. For the label location, refer to the "Start Guide".

• Model name and product ID of the Server Blade

They are indicated on the label supplied with the Server Blade. For the label location, refer to the

"Start Guide".

• Hardware configuration (Types and locations of internal options)

• Configuration information of Server Blade (Set values with BIOS Setup Utility)

• OS used in Server Blade

• LAN/WAN system configuration

• Phenomena (what happened when doing what, what was displayed, etc.)

• Date/time of occurrence

• Environmental settings of the server

• LED statuses

• USB floppy disk drive

• The latest "Server Management Tools" disk with a setting information stored

� Maintenance work

Note the following points for maintenance work:

• The settings will revert to the default values when blades and other units are replaced for

maintenance. After replacement, specify the set values required for operations again.

• During maintenance work, the maintenance engineer may ask you to turn on the LEDs such as the

maintenance LEDs. Please follow the instructions.

260


9.9 Maintenance & Notes

This section explains the details of the maintenance & notes.

9.9.1 Operations after Replacement of a SAS Module or an Expansion Card Slot Module

If the SAS module or the expansion card slot module is replaced due to an error when the array

controller function is used for this Server Blade, the logical drive of the array controller is initialized

again after replacement. This is because the data integrity information showing whether data was written

correctly on internal hard disk unit in the past is stored in the SAS module or the expansion card slot

module. As the information is lost due to replacement, the initialization is automatically executed to

ensure the data integrity.

You can restore this information using maintenance tool just before the replacement and write back after

the replacement, however, if you cannot restore the information because of the malfunction of the SAS

module or the expansion card slot module, the initialization procedure starts. This does not mean hard

disk failure as well as the initialization.

For details of the initialization, refer to the manual in the Array controller Document & Tool CD.

261

Appendix

This appendix explains the specifications for the

server and internal options. It also covers how to

recycle the products.

A Server Blade Specifications . . . . . . . . . . . . . . . . . . . . . . . 262

B Specifications for Internal Options . . . . . . . . . . . . . . . . . . 264

C External Floppy Disk Drive (USB) Notes on Usage . . . . . . 267

D About Switch Blade (PG-SW107) Connection . . . . . . . . . 268

E Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

262

Appendix

A Server Blade Specifications

This section explains the specifications for the Server Blade.

table: Server Blade Specifications

Item Functions and Specifications

Product Name PRIMERGY BX620 S4 Server Blade

Type Diskless type

Product ID PGUX624CA2 PGUX624EA

Chipset Intel 5000P + ESB2

CPU

Standard

(frequency/

cache/FSB)

Dual Core Intel® Xeon® Processor E5205

(1.86GHz/6MB/1066MHz)

Quad Core Intel® Xeon® Processor L5410

(2.33GHz/12MB/FSB1333MHz)

Conversion

kit(frequency/

cache/FSB)

Dual Core Intel® Xeon® Processor

X5260 (3.33GHz/6MB/FSB1333MHz)

Quad Core Intel® Xeon® Processor

E5405 (2GHz/12MB/FSB1333MHz)

E5420 (2.5GHz/12MB/FSB1333MHz)

X5460 (3.16GHz/12MB/FSB1333MHz)

–

Number of

multiplication1 (Max. 2)

Memory

Module

Standard 1GB (DDR2-667 FBD 512MB DIMM × 2)

Redundancy Memory mirror

Adding size 1GB / 2GB / 4GB / 8GB

Maximum 32GB (4GB DIMM ×8 slots)

PCI slots

For expansion

boardStandard: N/A, Option: PCI-X 64-bit/133MHz×1, or PCI-Express (x8) × 1

For PCI card Standard: N/A, Option: PCI-X 64-bit/133MHz×1, or PCI-Express (x4) × 1

Internal 2.5-inch hard disk drive 2 bays (hot-pluggable)

Adding size 73.4GB/146.8GB (10,025rpm, SAS), 73.4GB (15,000rpm, SAS)

Maximum 293.6GB (146.8GB × 2)

CD/DVD drive Type: DVD-ROM drive unit (USB external option) *1

Floppy disk drive Option (USB floppy disk drive) *1

Onboard

controller

Video

VGA chip: ATI ES1000

Video RAM capacity: 16MB

Resolution: 640×480, 800×600, 1024×768, 1280×1024

Display colors: Differ depending on resolution and OS.

SAS LSI 1068 (2 port use, SAS module, IME array function)

LAN Broadcom BCM5715S (1Gbps, Dual port) × 3

Security chip –

Internal I/O

port

Video *2 1 (Analog RGB)

keyboard *2 1 (PS/2)

Mouse *2 1 (PS/2)

SAS 2

SerDes (LAN) 6 (1Gbps)

SerDes

(LAN/FC)2 (For expansion board, Max. 10Gbps)

Serial 1 (for system management)

I2C 1 (for system management)

USB 1 (USB 1.1)

External I/O port Display/USB expansion cable *3: Display × 1, USB 2.0 × 2

263


*1: In this blade server system, at least 1 unit is required. DVD-ROM drive units have a CD-R/RW function but this function cannot be used to write to CD media.

*2: Connects to each keyboard/ mouse/ display connector of the CRT/KB cable (1 provided with the Chassis) that was connected to the Chassis (each Server Blade can switch and use).

*3: Connect the display/ USB expansion cable (1 included with the Chassis) to the Server Blade's front connector.

The specifications for this Server Blade are liable to be updated without any notice. Please be forewarned.

� Support OS

The supported OSes of this server are as follows.


• Windows Server 2008 Enterprise (32-bit)


• Windows Server 2008 Enterprise (64-bit)

• Windows Server 2003, Standard Edition (SP1 or later)

• Windows Server 2003, Enterprise Edition (SP1 or later)

• Windows Server 2003, Standard x64 Edition

• Windows Server 2003, Enterprise x64 Edition

• Windows Server 2003 R2, Standard Edition

• Windows Server 2003 R2, Enterprise Edition

• Windows Server 2003 R2, Standard x64 Edition

• Windows Server 2003 R2, Enterprise x64 Edition

• Red Hat Enterprise Linux ES (v.4 for x86)

• Red Hat Enterprise Linux ES (v.4 for EM64T)

• Red Hat Enterprise Linux AS (v.4 for x86)

• Red Hat Enterprise Linux AS (v.4 for EM64T)

• Red Hat Enterprise Linux 5 (for x86)

• Red Hat Enterprise Linux 5 (for Intel64)

The latest information about the supported OS

� For the latest information such as notes on supported OS not described in this manual, refer to the

Fujitsu PRIMERGY website (http://primergy.fujitsu.com).

Keyboard/Mouse/

DisplayOptional (Connect to the Chassis)

Internal clock precision ± 2 to 3 minutes/month

Input voltage

(supplied from the Chassis)DC 12V (During operation) / DC 5V (During standby)

Power consumption/heating value Max. 347W (Max. 1,250kJ/h) Max. 240W (Max. 864kJ/h)

Dimensions (Unit: mm) 42 × 476 × 286 (W × D × H) (1 slot occupied in BX600 S3 Chassis)

Weight 7.0kg

table: Server Blade Specifications


264

Appendix

B Specifications for Internal Options

This section explains the specifications and packaged items of internal options for the

Server Blade.

When you have bought an internal option as a standard option, check the contents of

each optional package before use. Should it happen that items are missing, contact

an office listed in the "Contact Information" of "Start Guide".

B.1 CPU Specifications

� Package

• CPU (1)

• Heat sink (1)

� Specifications

� Dual core processor

� Quad core processor

table: CPU Specifications (Dual Core Processor)


Product name Processor Xeon E5205 (1.86GHz/6MB) Processor Xeon X5260 (3.33GHz/6MB)

Product ID PG-FG43G PG-FG43H

Number of core 2

Clock frequency 1.86GHz 3.33GHz

Internal secondary cache size 6MB

Front side bus 1066MHz 1333MHz

table: CPU Specifications (Quad Core Processor)


Product nameProcessor Xeon E5405

(2GHz/12MB)

Processor Xeon E5420

(2.5GHz/12MB)

Processor Xeon X5460

(3.16GHz/12MB)

Processor Xeon L5410

(2.33GHz/12MB)

Product ID PG-FG43J PG-FG43K PG-FG43L PG-FG43P

Number of core 4

Clock frequency 2GHz 2.5GHz 3.16GHz 2.33GHz

Internal secondary

cache size12MB

Front side bus 1333MHz

265


B.2 Memory Specifications

� Package

• RAM modules (2)

� Specifications

B.3 Internal Hard Disk Unit Specifications

� Package

• Internal hard disk unit (1)

� Specifications

*1: The value indicates memory capacity of the formatted hard disk (1GB = 10003 bytes).

*2: Hot plug carrier is not included.

table: Memory Specifications


Product name Memory Module-1GB Memory Module-2GB Memory Module-4GB Memory Module-8GB

Product ID PG-RM1CJ PG-RM2CJ PG-RM4CJ PG-RM8CJ

Component512MB DDR2 667 FBD

× 2

1GB DDR2 667 FBD

× 2

2GB DDR2 667 FBD

× 2

4GB DDR2 667 FBD

× 2

Capacity 1GB 2GB 4GB 8GB

Clock

frequency667MHz

Number of

pins240

table: Internal Hard Disk Unit Specifications


Product nameHDD SAS 10k 73GB hot plug

2.5inch

HDD SAS 10k 147GB

hot plug 2.5inch

HDD SAS 15k 73GB

hot plug 2.5inch

Product ID PG-HDD71B PG-HDD41B PG-HDD75B

Interface Serial Attached SCSI (SAS)

Storage media 2.5-inch hard disk unit

Memory capacity *1 73.4GB 146.8GB 73.4GB

Maximum data transfer speed 3Gbit/s

Average latency speed 3.0ms 2.0ms

Rpm 10,025rpm 15,000rpm

Dimension (unit: mm) *2 70.1 × 100.45 × 15.0 (W × D × H)

Weight 0.22kg

266

Appendix

B.4 Expansion Card Slot Module Specifications

� Package

• Expansion card slot module (1)

� Specifications

table: Expansion card slot module specifications

Item Contents

Product name Expansion Card Slot Module

Product ID PG-CS103 PG-CS104

PCI slot PCI-X (64-bit 133MHz) × 1 PCI-Express (x4) × 1

Dimension (unit: mm) 40 × 200 × 85 (W × D × H)

Weight Approx. 260 g

267


C External Floppy Disk Drive (USB) Notes on Usage

The section explains notes on the usage of USB connected floppy disk drive.

� Notes on floppy disk drive recognition at server startup

If the floppy disk drive (USB), with a floppy disk inserted, is not connected at server startup, BIOS

cannot recognize the floppy disk drive (USB). When installing Windows/Linux, or when using

Windows Server 2003 Automatic System Recovery (ASR), make sure to connect the floppy disk drive

(USB) with a floppy disk inserted before server startup.

� Notes on floppy disk media exchange recognition when installing windows manually and at system recovery

When performing system recovery using Windows Server 2003 Automatic System Recovery (ASR),

also when installing Windows manually, system recovery/installation might not be performed properly.

This is caused by the device driver being unreadable due to recognition failure of the floppy disk media

replacement.

After pressing the [Enter] key in accordance with the procedures on the screen, if the floppy disk access

LED on the floppy disk drive (USB) does not turn on and the floppy disk is not accessed, follow the

procedures below.

1 Eject the floppy disk and wait for 2 seconds or longer, then press the [Enter] key

several times.

2 Insert the floppy disk and wait for 2 seconds or longer, then press the [Enter]

key.

If the floppy disk cannot be accessed, perform the procedures above again.

268

Appendix

D About Switch Blade (PG-SW107) Connection

Explanation about connecting this Server Blade's onboard LAN to BX600 Switch

Blade (PG-SW107) and LAN number relation.

table: Relation of connection when installing a Switch Blade (PG-SW107)

Network bladeServer blade slot

LAN number MAC

AddressSlot Port Physical Web-UI CLI BIOS

NET1 1

1

1 No.1 NIC1 LAN1

Small

↑

↓

Big

NET2 1 2 No.2 NIC2 LAN2





NET1 4

2

1 No.1 NIC1 LAN1

Small

↑

↓

Big






NET1 7

3

1 No.1 NIC1 LAN1

Small

↑

↓

Big






NET1 10

4

1 No.1 NIC1 LAN1

Small

↑

↓

Big






NET1 13

5

1 No.1 NIC1 LAN1

Small

↑

↓

Big






269


NET1 16

6

1 No.1 NIC1 LAN1

Small

↑

↓

Big






NET1 19

7

1 No.1 NIC1 LAN1

Small

↑

↓

Big






NET1 22

8

1 No.1 NIC1 LAN1

Small

↑

↓

Big






NET1 25

9

1 No.1 NIC1 LAN1

Small

↑

↓

Big






NET1 28

10

1 No.1 NIC1 LAN1

Small

↑

↓

Big






table: Relation of connection when installing a Switch Blade (PG-SW107)

Network bladeServer blade slot

LAN number MAC

AddressSlot Port Physical Web-UI CLI BIOS

270

Appendix

� This Server Blade's onboard LAN has 6 ports, the sequence depends on the OS or manner the LAN

driver was installed. When planning a network, pay attention to the LAN numbers, device names in the

OS, and local area connection names above.

If the OS is Windows, the MAC address, device name, and local connection name can be checked

with the "ipconfig /all" command in command prompt.

Local area connection name Device name

MAC Address

271


E Recycling

This section explains how to recycle this server.

� Disposing of the server

When scrapping this server, contact an office listed in the "Contact Information" of "Start Guide". This

server must be disposed of as industrial waste.

Furthermore, if the server is disposed of as it is, someone else may gain access to the information

contained on the hard disks. It is therefore recommended that all drives be formatted before disposal.

However, just formatting or deleting files may not avoid the risk that the data is restored and used for

wrongful purposes. If confidential or private information is saved, in order to make it impossible to be

restored, it is recommended to use third-party data wiping tools.

� Disposing of used-up batteries

Used-up batteries must be disposed of as industrial waste and therefore require special processing. Let a

licensed industrial waste disposal company take care of disposal.

� Disposing of liquid crystal displays

Liquid crystal displays must be disposed of as industrial waste and therefore require special processing.

Let a licensed industrial waste disposal company take care of disposal.

272

Appendix

273


Index

A

Advanced Menu . . . . . . . . . . . . . . . . . . . . 209

Application wizard

Expert mode . . . . . . . . . . . . . . . . . . . . . 65

ASR&R Submenu. . . . . . . . . . . . . . . . . . . 217

Auto-run Function from CD/DVD Drives . . 117

B

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Backup cabinet . . . . . . . . . . . . . . . . . . . . . 202

BACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Installing . . . . . . . . . . . . . . . . . . . . . . . 123

LAN driver advanced setup . . . . . . . . . 123

VLAN . . . . . . . . . . . . . . . . . . . . . . . . . 143

Baseboard . . . . . . . . . . . . . . . . . . . . . . . . . 31

BIOS Setup Utility . . . . . . . . . . . . . . . . . . . 205

How to Exit . . . . . . . . . . . . . . . . . . . . . 206

How to Start . . . . . . . . . . . . . . . . . . . . 205

Key Operations . . . . . . . . . . . . . . . . . . 206

BMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Boot Device Priority Submenu . . . . . . . . . 225

Boot Menu . . . . . . . . . . . . . . . . . . . . . . . . 224

Boot monitoring setting . . . . . . . . . . . . . . . 167

C

Cautions for manual installation . . . . . . . . . 45

Chassis connector . . . . . . . . . . . . . . . . . . . 30

Checking before OS installation . . . . . . . . . 33

Connector

Display / USB extension connector . . . . 29

Connector for expansion card slot module . 31

Console Redirection Submenu . . . . . . . . . 222

Contacting Maintenance Support . . . . . . . 259

CPU

Available CPUs . . . . . . . . . . . . . . . . . . 177

How to Install. . . . . . . . . . . . . . . . . . . . 178

How to Remove . . . . . . . . . . . . . . . . . 181

Installation location . . . . . . . . . . . . . . . 176

Installation Order. . . . . . . . . . . . . . . . . 176

Specifications . . . . . . . . . . . . . . . . . . . 264

CPU Configuration Submenu . . . . . . . . . . 213

CPU socket. . . . . . . . . . . . . . . . . . . . . . 30, 31

CPU Status Submenu. . . . . . . . . . . . . . . . 220

Creating a DOS Floppy Disk . . . . . . . . . . . 116

Creating Driver Disks . . . . . . . . . . . . . . . . . 70

Creating Maintenance Tools . . . . . . . . . . . 113

D

Defective CPU Disconnection Function . . .181

Defective Memory Disconnection Function .187

DIMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183

Disk Manager . . . . . . . . . . . . . . . . . . . . . . . .59

Drive Letter Assignment . . . . . . . . . . . . . . .117

Driver types

Windows Server 2003. . . . . . . . . . . . . . .71

Windows Server 2003 x64 . . . . . . . . . . .71

Windows Server 2008 (32-bit/64-bit) . . . .70

DSNAP. . . . . . . . . . . . . . . . . . . . . . . . .24, 169

Installation. . . . . . . . . . . . . . . . . . . . . . .169

Usage . . . . . . . . . . . . . . . . . . . . . . . . . .169

Dual Core Intel Xeon Processor . . . . . . . . . .18

Dummy unit . . . . . . . . . . . . . . . . . . . . . . . .199

E

Error Messages . . . . . . . . . . . . . . . . .234, 238

POST Error Messages . . . . . . . . . . . . .234

Server Management Tools Error Messages

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .236

Event logs. . . . . . . . . . . . . . . . . . . . . . . . . .240

Exit Menu . . . . . . . . . . . . . . . . . . . . . . . . . .226

Expansion board

Available Expansion Boards . . . . . . . . .195

BIOS Setting with Expansion Card Installed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

How to Install . . . . . . . . . . . . . . . . . . . .195

How to Remove . . . . . . . . . . . . . . . . . .196

Installation location . . . . . . . . . . . . . . . .194

Expansion board active link display LED. . . .29

Expansion board slot . . . . . . . . . . . . . . .30, 31

Expansion Card Slot . . . . . . . . . . . . . . . .29, 30

Expansion card slot module

Available Expansion Card Slot Module .189

Expansion cards

Available Expansion Card . . . . . . . . . . .189

How to Install . . . . . . . . . . . . . . . . . . . .190

How to Remove . . . . . . . . . . . . . . . . . .193

Installation location . . . . . . . . . . . . . . . .188

Expert mode . . . . . . . . . . . . . . . . . . . . . . . . .55

F

Fan monitoring . . . . . . . . . . . . . . . . . . . . . .165

H

Hard disk access LED . . . . . . . . . . . . . . . . .27

Hard disk failure LED . . . . . . . . . . . . . . . . . .28

274

Hard disk status LED . . . . . . . . . . . . . . . . . . 27

High Reliability Tools . . . . . . . . . . . . . . . . . . 23

How to install . . . . . . . . . . . . . . . . . . . . . 25

How to store the BIOS Information. . . . . . . 111

HRM/server . . . . . . . . . . . . . . . . . . . . . . . . 168

I

Identification label . . . . . . . . . . . . . . . . . . . 184

Installation

DSNAP . . . . . . . . . . . . . . . . . . . . . . . . 169

ServerStart . . . . . . . . . . . . . . . . . . . . . . 113

ServerView. . . . . . . . . . . . . . . . . . . . . . 166

Installation Partition Size . . . . . . . . . . . . . . . 42

Installing the Fibre Channel Driver . . . . . . . . 94

Installing the LAN Driver

Error window after installation. . . . . . . . 239

Windows Server 2003 . . . . . . . . . . . . . . 92

Windows Server 2003 x64 . . . . . . . . . . . 91

Windows Server 2008 (32-bit) . . . . . . . . 89

Windows Server 2008 (64-bit) . . . . . . . . 90

Intel® PROSet . . . . . . . . . . . . . . . . . . . . . . 151

Creating a team . . . . . . . . . . . . . . . . . . 154

Local Address Setting . . . . . . . . . . . . . 161

Notes on Referring to Help Topics . . . . 152

Teaming . . . . . . . . . . . . . . . . . . . . . . . . 153

VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Internal Hard Disk Unit

Available Internal Hard Disk Units . . . . 198

How to Install . . . . . . . . . . . . . . . . . . . . 199

How to Remove . . . . . . . . . . . . . . . . . . 200

Installation location. . . . . . . . . . . . . . . . 198

Replacing the failed unit . . . . . . . . . . . . 200

Specifications . . . . . . . . . . . . . . . . . . . . 265

I/O expansion board port . . . . . . . . . . . . . . . 30

K

KVM select LED. . . . . . . . . . . . . . . . . . . . . . 28

KVM select switch . . . . . . . . . . . . . . . . . . . . 29

L

LAN active link display LED . . . . . . . . . . . . . 29

LAN Driver Advanced Setup . . . . . . . . . . . 151

Intel® PROSet . . . . . . . . . . . . . . . . . . . 151

M

Main Menu (BIOS) . . . . . . . . . . . . . . . . . . . 208

Manual installation

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Windows Server 2003 . . . . . . . . . . . . . . 86

Windows Server 2003 x64 . . . . . . . . . . . 83

Windows Server 2008 (Full) . . . . . . . . . . 76

Windows Server 2008 (Server Core) . . . 79

Memory Dump. . . . . . . . . . . . . . . . . . 100, 240

Memory Dump File Setting . . . . . . . . . . . . 101

Memory Dump Setting . . . . . . . . . . . . . . . . 100

Memory modules

Available Memory Modules . . . . . . . . . 183

How to Install . . . . . . . . . . . . . . . . . . . . 186

How to Remove . . . . . . . . . . . . . . . . . . 186

Identifying . . . . . . . . . . . . . . . . . . . . . . 184

Installation location. . . . . . . . . . . . . . . . 183

Specifications . . . . . . . . . . . . . . . . . . . . 265

Memory monitoring . . . . . . . . . . . . . . . . . . 165

Memory slots . . . . . . . . . . . . . . . . . . . . . 30, 31

Memory Status Submenu. . . . . . . . . . . . . . 221

Multiple LAN adapter configuration . . . . . . . 43

Adapter numbers . . . . . . . . . . . . . . . . . . 44

N

NMI function . . . . . . . . . . . . . . . . . . . . . . . . 29

Notes on a multiple LAN adapter configuration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Notes on UPS . . . . . . . . . . . . . . . . . . . . . . 118

O

OS installation wizard

Expert mode . . . . . . . . . . . . . . . . . . . . . 60

P

Paging File Setting. . . . . . . . . . . . . . . . . . . 103

Password

Administrator Password . . . . . . . . . . . . 248

Change . . . . . . . . . . . . . . . . . . . . . . . . 249

Delete . . . . . . . . . . . . . . . . . . . . . . . . . 249

Setting . . . . . . . . . . . . . . . . . . . . . . . . . 249

User Password. . . . . . . . . . . . . . . . . . . 248

PCI Configuration Submenu . . . . . . . . . . . 212

PCI-Express . . . . . . . . . . . . . . . . . . . . . . . . 18

PCI-X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Peripheral Configuration Submenu . . . . . . 210

POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Error Messages . . . . . . . . . . . . . . . . . . 234

Power supply monitoring . . . . . . . . . . . . . . 166

Precautions on installation . . . . . . . . . . . . . . 42

Q

Quad Core Intel Xeon Processor . . . . . . . . . 18

R

RAID Configuration

Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

RAID error monitoring . . . . . . . . . . . . . . . . 165

RAID Management Tool. . . . . . . . . . . . 24, 164

Recovering the BIOS Information . . . . . . . 112

275


Release latch . . . . . . . . . . . . . . . . . . . . . . . 27

Restoring the system

Windows Server 2003 . . . . . . . . . . . . . 256

Windows Server 2008 . . . . . . . . . . . . . 254

S

SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

SAS connector . . . . . . . . . . . . . . . . . . . . . . 31

Security

Against unauthorized use . . . . . . . . . . 248

Hardware . . . . . . . . . . . . . . . . . . . . . . 248

When disposing of the server . . . . . . . 250

Security Menu. . . . . . . . . . . . . . . . . . . . . . 214

Selecting the installation method. . . . . . . . . 39

Server blade power LED. . . . . . . . . . . . . . . 28

Server blade power switch . . . . . . . . . . . . . 28

Server Management Tools . . . . . . . . 110, 243

Error Messages. . . . . . . . . . . . . . . . . . 236

How to Exit . . . . . . . . . . . . . . . . . . . . . 245

How to Start . . . . . . . . . . . . . . . . . . . . 244

Server Menu . . . . . . . . . . . . . . . . . . . . . . . 216

Server Monitoring Tool . . . . . . . . . . . . 23, 165

Installation. . . . . . . . . . . . . . . . . . . . . . 166

Server Specifications . . . . . . . . . . . . . . . . 262

ServerStart . . . . . . . . . . . . . . . . . . . . . . . . . 20

Cautions . . . . . . . . . . . . . . . . . . . . . . . . 43

Features . . . . . . . . . . . . . . . . . . . . . . . . 20

Installation. . . . . . . . . . . . . . . . . . . . . . 113

Supported expansion cards. . . . . . . . . . 45

Uninstallation. . . . . . . . . . . . . . . . . . . . 115

ServerView . . . . . . . . . . . . . . . . . . 23, 24, 165

Installation. . . . . . . . . . . . . . . . . . . . . . 166

Settings Required Before Operating the Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

SNMP service. . . . . . . . . . . . . . . . . . . . . . 241

Solving problems . . . . . . . . . . . . . . . . . . . 169

Specifications for Internal Options. . . . . . . 264

Switch block . . . . . . . . . . . . . . . . . . . . . . . . 31

Setting. . . . . . . . . . . . . . . . . . . . . . . . . 204

System diagnosis support tools. . . . . . . . . . 24

System event log . . . . . . . . . . . . . . . . . . . 243

Deleting. . . . . . . . . . . . . . . . . . . . . . . . 247

Saving. . . . . . . . . . . . . . . . . . . . . . . . . 246

Viewing . . . . . . . . . . . . . . . . . . . . . . . . 246

System Information Submenu. . . . . . . . . . 223

System Recovery Disk . . . . . . . . . . . . . . . 107

T

Temperature monitoring . . . . . . . . . . . . . . 166

Top cover

How to Attach . . . . . . . . . . . . . . . . . . . 175

How to Remove . . . . . . . . . . . . . . . . . 174

Troubleshooting

Hardware . . . . . . . . . . . . . . . . . . . . . . 229

Types of internal options. . . . . . . . . . . . . . .172

U

Uninstallation

ServerStart . . . . . . . . . . . . . . . . . . . . . .115

USB Configuration submenu . . . . . . . . . . .211

V

Voltage monitoring . . . . . . . . . . . . . . . . . . .166

Numeric

2.5-inch storage bay . . . . . . . . . . . . . . . .27, 30

• The contents may be revised without prior notice.

• Fujitsu assumes no liability for damages to third party copyrights or other rights

arising from the use of any information in this manual.

• No part of this manual may be reproduced in any form without the prior written

permission of Fujitsu.

PRIMERGY BX620 S4 Server Blade

User's Guide

B7FH-5591-01ENZ0-00

Issued in

Issued by

August, 2008

FUJITSU LIMITED

b7fh-5591-01en

Documents

driverslanintelappsprosetdxvistax64dxsetup

driverslanintelappsprosetdxvista32dxsetup

driverslanintelappsprosetdxwinx64dxsetup

driverslanintelappsprosetdxwin32dxsetup

driverschipsetintel5000pinfinstautol

programsjapanese2hrmiasvhrminstall

driversvideoes1000setup

programsjapanesedsnapreadmejp