Tutorial Server Manager

User Guide - English

FUJITSU Software ServerView Suite

ServerView Installation Manager

Edition October 2013

Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion ofthis manual. Your feedback helps us optimize our documentation to suityour individual needs.

Feel free to send us your comments by e-mail [email protected].

Certified documentation according to DIN ENISO 9001:2008To ensure a consistently high quality standard and user-friendliness, thisdocumentation was created tomeet the regulations of a quality man-agement system which complies with the requirements of the standardDIN EN ISO 9001:2008.

cognitas. Gesellschaft für Technik-DokumentationmbH

www.cognitas.de

Copyright and trademarksCopyright © 1998 - 2014 Fujitsu Technology Solutions.

All rights reserved.

Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respectivemanufacturers.

http://www.cognitas.de/

Contents1 Introduction 91.1 Overview of functional scope 101.2 Additional documentation 111.3 Target groups and objectives of this manual 111.4 Changes to the previous edition 111.5 ServerView Suite link collection 121.6 Documentation for the ServerView Suite 131.7 Typographic conventions 14

2 Overview and quick step guides 152.1 InstallationManager (overview) 152.1.1 Configuration and unattended installation 172.1.1.1 Configuring the installation process and/or starting theinstallation 172.1.1.2 Configuration and configuration file 172.1.1.3 Unattended installation 18

2.1.2 Local and remote installation 192.1.2.1 Local installation on the target system 192.1.2.2 Remote installation 19

2.1.3 Typical or Customized deployment 202.1.3.1 Typical deployment mode 202.1.3.2 Customized deployment mode 20

2.2 Quick step guides 222.2.1 Initial local Windows installation 222.2.2 Remote installation via deployment server 25

3 Local deployment 293.1 Booting InstallationManager from DVD 313.1.1 Standard PRIMERGY server 313.1.2 PRIMERGY blade servers 31

3.2 Booting InstallationManager from aUSB stick 333.2.1 Requirements 333.2.2 Configuring the USB stick 34

3.3 Starting InstallationManager on the target system 373.4Windows Boot Manager - Selecting standard / express instal-lation 383.5 InstallationManager - initial window 41

ServerView InstallationManager 3

Contents

3.6 Graphical user interface (GUI) of the InstallationManager 463.7 Starting local deployment 483.8 Starting local system configuration 53

4 Remote deployment 594.1 Remote installation (overview) 614.1.1 Preparing the installation 624.1.2 Progression of the installation process 64

4.2 Preparing the deployment server 664.2.1 Installing and configuring a DHCP server on the deploymentserver 684.2.2 Installing InstallationManager 694.2.2.1 Installing the PXE server 704.2.2.2 Installing data packages for the remote installation 724.2.2.3 Installing JBoss Application server 764.2.2.4 Installing InstallationManager 84

4.2.3 Extensions for the remote installation of Linux and VMwareESX/ESXi systems 884.2.4 Verifying the services (PXE, TFTP, DHCP) 924.2.5 Configuring TFTP 934.2.6 Configuring router for multi segment deployment 94

4.3 Preparing the remote resource server 964.4 Preparing the target system for the remote installation 974.5 Starting InstallationManager on the deployment server 984.5.1 Starting InstallationManager locally underWindows 994.5.2 Starting InstallationManager remotely via web browser 1004.5.3 InstallationManagerWelcome Screen 1014.5.4 Graphical user interface (GUI) of the InstallationManager

1024.6 Starting remote deployment / remote system configuration 1064.6.1 Select the target system (Remote Installation and RemoteSystem Configuration Only) 1074.6.2 Configure Your UnattendedOperating System Installation

1124.6.3 Enter Parameters for the Server's BIOS and Hardware Con-figuration 1184.6.4 Launching the PXE-based remote installation / system con-figuration 126

4 ServerView InstallationManager

4.7Multiple installation (multi-deployment) of PRIMERGY servers129

5 Configuring the target system 1315.1 Server ConfigurationManager 1315.2 Configuringmass storage devices 1325.2.1 Configuring RAID controllers 1375.2.2 Configuring hard disks 1425.2.3 Configuring partitions 1435.2.3.1 Configuring partitions (Windows) 1435.2.3.2 Configuring partitions (Linux / VMware ESX/ESXi) 145

6 Configuring Windows and starting the installation 1496.1 User interface 1496.2 InstallingWindows (typical) 1516.2.1 Configuring disks and RAID controllers (typical) 1526.2.2 ConfiguringWindows installation 1566.2.3 Backing up the configuration / starting the installation 162

6.3 InstallingWindows (customized) 1646.3.1 Server ConfigurationManager 1666.3.2 Configuring Disks and RAID controllers 1676.3.3 ConfiguringWindows Server 2008 / Windows Server 2012

1686.3.3.1 Select the Installation Image 1686.3.3.2 Basic Settings 1706.3.3.3 System Settings 1746.3.3.4 Network Settings 1766.3.3.5 Services 1836.3.3.6 Additional Parameters 187

6.3.4 Selecting / configuring applications 1896.3.5 Backing up the configuration / starting the installation 195

7 Configuring Linux and VMware ESX/ESXi and starting theinstallation 1997.1 User interface 1997.2 Installing Linux / VMware ESX/ESXi (typical) 2017.2.1 Configuring Disks and RAID Controllers (typical) 2027.2.2 Configuring Linux / VMware ESX/ESXi settings 2057.2.3 Backing up the configuration / starting the installation 208

7.3 Installing Linux (customized) 209


Contents

Contents

7.3.1 Server ConfigurationManager 2107.3.2 Configuring disks and RAID controllers 2107.3.3 Configuring Linux / VMware ESX/ESXi 2117.3.3.1 Basic Configuration 2127.3.3.2 Package selection 2187.3.3.3 Configuring the X Windows System (for Red Hat andSuSE only) 2207.3.3.4 VMware virtual disk configuration (VMware ESX only)

2237.3.3.5 VMware LicenseOptions (VMware ESX/ESXi only) 2247.3.3.6 Grub bootloader options / mount options 2267.3.3.7 Network configuration 2297.3.3.8 Security and Firewall (for Red Hat and SuSE only) 2317.3.3.9 Authentication 2357.3.3.10 Pre Installation Script (for Red Hat and SuSE only) 2407.3.3.11 Post Installation Script 241

7.3.4 Selecting / configuring applications 2437.3.5 Backing up the configuration / starting the installation 249

8 Installation Monitor - Monitoring remote installation 2518.1 Graphical user interface of the InstallationMonitor 2518.2Monitoring remote installation 254

9 Maintenance 2619.1Maintaining and configuring PRIMERGY servers 2619.1.1 ServerView RAID 2629.1.2 Server ConfigurationManager 263

9.2Maintenance on the deployment server 2659.2.1 Configuring andmanagingMulti-Deployment (MDP) sets

2669.2.1.1 Configuring new MDP sets 2709.2.1.2 Adding a new set / editing a custom set 2729.2.1.3 Preparing and starting the PXE boot 274

9.2.2 Booting any required boot images via PXE 2759.2.3 Creating / importing a backup of the InstallationManagerrepository 2819.2.3.1 Creating a backup of the InstallationManager repos-itory 2819.2.3.2 Restoring the InstallationManager repository 282


10 Installation Manager Information 28311 Reference 28511.1 The PXE process 28511.2 Setting up a DHCP server 28711.3 VLAN (Virtual Local Area Network) 288

12 License Agreement for End User 291Index 299


Contents


1 IntroductionServerView InstallationManager (referred to here as InstallationManager forshort) comes as part of ServerView Suite. Within the ServerView Suite,InstallationManager is the component for configuring and installing operatingsystems and other user management and server management software.InstallationManager also enables subsequent adjustments to system set-tings on systems that have already been installed.

The operating system installation on the target system can be initiated locallyusing a DVD drive on that system, or remotely with PXE boot using a deploy-ment server.

In preparation for the installation, InstallationManager wizards guide youthrough a series of configurationmenus, where you compile all parametersrequired for system configuration and for the subsequent automatic operatingsystem installation. You can save these parameters to a configuration fileand use them to install additional servers with the same hardware archi-tecture.

This is the ServerView InstallationManager commonmanual that containsthe explanation for a function supported in a specific region and languageonly.

The installation of Suse Linux and VMware is not supported for Japan.

You will find the latest information on supported server systems andsupported operating systems for Japan as part of the restrictions of theServerView Suite on the Internet.


http://primeserver.fujitsu.com/primergy/products/note/svsdvd/

1 Introduction

1.1 Overview of functional scopel For local operating system installations on the target system: Auto-

matic recognition of the hardware configuration and RAID arrays of yourPRIMERGY server.

l Installation support for the following server operating systems: Micro-soft Windows Server, Red Hat and SuSE Linux Enterprise versions,VMware ESX, VMware ESXi.

Configuration and installation are largely the same for both VMwareESX/ESXi and the Linux distributions, and so the procedures aredescribed in the same chapter here.

l Creation of configuration files for the automatic installation of severalPRIMERGY servers with identical hardware configurations and for useas templates for additional, similar installation processes.

l Installation of drivers, service packs and application software.

The choice of software that you can install is automatically determinedby your server's hardware configuration.

l Remote access to configuration files and installation packages that areavailable on file servers or on DVD drives that are shared on the net-work.

l PXE-based remote network installation of PRIMERGY servers.

l Multi Deployment Platform: Integrating custom programs or scripts intothe InstallationManager platform (MSWindows PE) and launching thepackage on target systems via PXE boot.

l Using the "Generic PXE Boot" function, you can boot any required bootimages on the target system via PXE boot based on the PXE infra-structure of InstallationManager.

l Creating a backup of the InstallationManager repository.

l Restoring the InstallationManager repository using a backup.


1.2 Additional documentation

ServerView Suite bookletThis booklet, which accompanies your PRIMERGY server, provides anoverview of the components of the ServerView Suite and contains aquick-start guide to the process of wizard-assisted operating systeminstallation.

Online helpThe context-sensitive online help function provides detailed informationon all the configuration steps you will complete with the assistance of thevarious configuration wizards.

1.3 Target groups and objectives of this manualThis manual is aimed at users who have a sound knowledge of hardware andsoftware, as well as system administrators and service professionals. It pro-vides an introduction to the functional scope and operating concept of Instal-lationManager and describes the various options available when installingoperating systems on your PRIMERGY server using InstallationManager.

1.4 Changes to the previous editionThe current edition is valid as of ServerView InstallationManager V11.13.10and replaces the following onlinemanual:

"ServerView InstallationManager", Edition July 2013


1.2 Additional documentation

1 Introduction

1.5 ServerView Suite link collectionVia the link collection, Fujitsu Technology Solutions provides you with numer-ous downloads and further information on the ServerView Suite and PRIM-ERGY servers.

For ServerView Suite, links are offered on the following topics:

l Forum

l Service Desk

l Manuals

l Product information

l Security information

l Software downloads

l Training

The downloads include the following:o Current software statuses for the ServerView Suite as well as

additional Readme files.o Information files and update sets for system software com-

ponents (BIOS, firmware, drivers, ServerView agents and Server-View update agents) for updating the PRIMERGY servers viaServerView UpdateManager or for locally updating individualservers via ServerView UpdateManager Express.

o The current versions of all documentation on the ServerViewSuite.

You can retrieve the downloads free of charge from the Fujitsu Tech-nology Solutions Web server.

For PRIMERGY servers, links are offered on the following topics:

l Service Desk

l Manuals


l Product information

l Spare parts catalogue

Access to the link collectionYou can reach the link collection of the ServerView Suite in various ways:

1. Via ServerView Operations Manager.

l Select Help – Links on the start page or on themenu bar.

This opens the start page of the ServerView link collection.

2. Via the start page of the online documentation for the ServerView Suiteon the Fujitsu Technology Solutions manual server.

You access the start page of the online documentation via the fol-lowing link:

http://manuals.ts.fujitsu.com

l In the selection list on the left, select Industry standard servers.

l Click themenu item PRIMERGY ServerView Links.


3. Via the ServerView Suite DVD.

l In the start window of the ServerView Suite DVD, select the optionSelect ServerView Software Products.

l Click Start. This takes you to the page with the software products ofthe ServerView Suite.

l On themenu bar select Links.


1.6 Documentation for the ServerView SuiteThe documentation can be downloaded free of charge from the Internet. Youwill find the online documentation at http://manuals.ts.fujitsu.com under thelink Industry standard servers.


1.6 Documentation for the ServerView Suite

http://manuals.ts.fujitsu.com/

http://manuals.ts.fujitsu.com/

1 Introduction

For an overview of the documentation to be found underServerView Suiteas well as the filing structure, see the ServerView Suite sitemap (Server-View Suite –Site Overview).

1.7 Typographic conventionsThe following typographic conventions are used:

Convention ExplanationIndicates various types of risk, namely health risks,risk of data loss and risk of damage to devices.

Indicates additional relevant information and tips.

bold Indicates references to names of interface elements.monospace Indicates system output and system elements for

example, file names and paths.monospace sem-

ibold

Indicates statements that are to be entered using thekeyboard.

blue continuous text Indicates a link to a related topic.

pink continuous text Indicates a link to a location you have already visited.

<abc> Indicates variables whichmust be replaced with realvalues.

[abc] Indicates options that can be specified (syntax).

[key] Indicates a key on your keyboard. If you need toenter text in uppercase, the Shift key is specified, forexample,[SHIFT] + [A] for A. If you need to presstwo keys at the same time, this is indicated by a plussign between the two key symbols.

ScreenshotsSome of the screenshots are system-dependent, so some of the detailsshownmay differ from your system. Theremay also be system-specific dif-ferences inmenu options and commands.


2 Overview and quick step guidesInstallationManager allows you to install Microsoft Windows Server, LinuxEnterprise and VMware ESX/ESXi operating systems, as well as additionalsoftware, on PRIMERGY servers.

This chapter provides an overview of the functional scope of InstallationMan-ager and a quick step guide for the following installation variants:

l an initial local Windows installation in Typicalmode

l a remote installation via deployment server

In this manual, the term "deployment server" refers to servers on whicha PXE server is installed.

2.1 Installation Manager (overview)A PRIMERGY server installation using InstallationManager is distinguishedby the following characteristics:

l Separation of installation and configuration processes

The installation of an operating system on a PRIMERGY server com-prises a configuration phase and an installation phase:

1. In the configuration phase, you configure general system settings forthe target system, the RAID system, and hard disks as well as set-tings for the operating system that is to be installed.

InCustomized configurationmode, you can save these settings toa configuration file, which you can then use to install other identicalservers.

2. InstallationManager uses a previously created configuration file toconfigure the server and to install the operating system on the targetsystem automatically in unattendedmode.


2.1 InstallationManager (overview)

2Overview and quick step guides

l Local installation on the target system or remote installation

You have the option of configuring and installing the operating systemlocally on the target system. To do this, boot the target system fromPRIMERGY ServerView Suite DVD and initiate the local installation onthe target system. Alternatively, you can configure the installation proc-ess under aWindows Server operating system on a deployment serverand, from there, start the automatic installation process on the targetsystem via the network (remote installation).

l Configuration in Typical orCustomizedmode

o Typical deployment mode provides support in the form of presetvalues for configuration parameters, and it eliminates operatingerrors through plausibility checks. In addition, all software com-ponents required in order to use ServerView are included in the instal-lation.

o Customized deployment mode enables a configuration of the targetsystem and the operating system you want to install that is tailoredto your specific requirements.

In bothmodes, the InstallationManager wizards guide you through theindividual configuration steps.

To install Windows Server Core, youmust useCustomizedmode.


2.1.1 Configuration and unattended installationDuring the configuration phase, InstallationManager enters all selectedparameters in a configuration file (xml file), which you can save locally or onan external storagemedium after the customized configuration session hasended. You cannot start the operating system installation on the target sys-tem until all settings have been configured.

2.1.1.1 Configuring the installation process and/or starting the installation

InstallationManager offers the following options:

l Configure the installation process and install the operating system onthe target system immediately afterwards.

l Configure the installation process and - if you useCustomized con-figurationmode - save the configuration file for installing the operatingsystem at a later stage.

l Import an existing configuration file, modify it if required, and install theoperating system on the target system.

l For remote installations: Perform a replicated installation of amaximumof five servers based on a previously created configuration file.

2.1.1.2 Configuration and configuration file

Values must be configured for the following operating parameters using theInstallationManager wizards in preparation for an unattended installation:

l Target system (for remote installations only)

l Operating system to be installed

l Optional: System settings that are relevant for server management(using Server ConfigurationManager)

l Hard disks/RAID array configuration

l Disks: Selection, partitioning and formatting




l Configuration data for the operating system

l Applications that you want to be installed together with the operatingsystem. (The applications available for selection depend on the oper-ating system you are installing.)

Based on the selected installationmethod (local or remote), InstallationMan-ager sets some configuration parameters independently and offers defaultvalues for many configuration parameters.

During the system configuration process, the InstallationManager cancreate amaximum of one RAID array.

2.1.1.3 Unattended installation

As soon as you start the installation process, InstallationManager configuresthe system hardware and then starts installing the operating system inaccordance with the parameters in the configuration file. The entire instal-lation, including any restarts that are required, runs in fully automatic (unat-tended) mode, whichmeans that you are only required to intervene in theinstallation process in order to change storagemedia (operating system, serv-ice packs, applications) or in the case of incorrect or incomplete hardwaredetection. During installation of the operating system, InstallationManagerautomatically integrates drivers for system components that are not con-tained in the operating system.

In the case of local installations, you can track the progress of the installationon the target systemmonitor.

With remote installation, InstallationManager provides information about theinstallation process using a progress bar, logging information and systemmessages.

The target systemmouse, keyboard andmonitor are not required for aremote installation ("headless installation").


2.1.2 Local and remote installationInstallationManager offers the following alternatives for the installation:

l Local installation on the target system

l PXE-based remote installation

2.1.2.1 Local installation on the target system

For a local installation, boot from ServerView Suite DVD on the target sys-tem. InstallationManager then automatically detects the hardware con-figuration of the target system and, in particular, RAID and hard disk sys-tems, and it adjusts the scope of the configuration dialog box accordingly.

In the case of a local installation, you can choose between Typical deploy-ment mode (for an installation based on default values), andCustomizeddeployment mode (for an installation based on parameters specifically tai-lored tomeet your requirements).

2.1.2.2 Remote installation

For a PXE-based remote installation of the operating system, install and startInstallationManager as an independent application on a deployment serverunder aWindows Server operating system. The Central Management Station(CMS) on which ServerView Operations Manager is also installed is ideallysuited for use as a deployment server. Installation of the PXE service and ofprogram packages for remote installation is required in this case, as is theavailability of a DHCP server in the LAN segment of the deployment server.

If InstallationManager is installed on a deployment server, you can start itremotely by calling it via a browser on your local workstation desktop (Win-dows or Linux). A remote installation is configured in Customizedmode.

The target systemmust be prepared for the PXE boot. For this purpose,either configure the settings for the RemoteManagement Controller whendefining the target system, or prepare the target systemmanually (enable thePXE boot in the BIOS and place it in the first position in the boot sequence).InstallationManager then starts a PXE client on the target system that con-tacts the deployment server for the installation.




2.1.3 Typical or Customized deploymentInstallationManager offers twomodes, Typical andCustomized, for deploy-ment, i.e., for the configuration and execution of operating system instal-lations on PRIMERGY servers.

To install Windows Server Core, youmust useCustomizedmode.

2.1.3.1 Typical deployment mode

The Typical deployment mode is only supported for local installations on thetarget system. It is the default setting.

In this mode, InstallationManager proposes values for the configurationparameters and eliminates operating errors through plausibility checks. Italso automatically installs all software components required tomonitor thetarget system with ServerView Operations Manager.

The Typical deployment mode comprises the following steps:

1. Select the operating system you want to install.

2. Configure an unattended operating system installation.

3. Start the installation.

2.1.3.2 Customized deployment mode

InCustomized deployment mode, you configure the target system hardwareon the target system directly or on a deployment server under aWindowsServer operating system.

If you execute the configuration on the target system (local installation),InstallationManager automatically detects the hardware configuration of thetarget system and adjusts the configuration dialog boxes accordingly.

In case of remote installation, you can use the option to explicitly specify thehardware configuration of the target system. Alternatively, you can configureInstallationManager to retrieve target system data either from its own repos-itory or directly from the (remote) target system.


You can either follow the sequence of configuration steps proposed by Instal-lationManager (by clicking on theNext button) or use the tree structure (treeview) to select the sequence yourself. InstallationManager offers default set-tings for most configuration parameters.




2.2 Quick step guidesQuick step guides are provided below for an initial local installation of Win-dows in Typical mode and for a remote installation.

2.2.1 Initial local Windows installation

Youwill find the corresponding Quick Installation Guide in the bookletentitled "Server Installation with ServerView InstallationManager“,which comes with your server. For more information, see "Local deploy-ment" on page 29 and "InstallingWindows (typical)" on page 151 andrefer to the online help.

The only difference between a local installation in Customizedmodeand the procedure described below is that, when you select Cus-tomized, you are presented with amore extensive range of con-figuration options (see "InstallingWindows (customized)" on page164).

Follow the steps below on the target system:

1. Ensure that the DVD drive is the first drive accessed when the systemstarts. For more information, see "Booting InstallationManager fromDVD" on page 31.

2. Power on the server.

3. Insert the ServerView Suite DVD into the drive.

InstallationManager boots on the target system. Once the boot processis completed, the InstallationManager initial window is displayed.

4. Select the required interface language and country variant for the con-nected keyboard in this initial window.

5. If you want to save the configuration on a local drive:

l UnderStatus backup media, select the on local drive


(floppy/USB stick) option and then select the relevant drive (USBremovable storagemedium or floppy) in the list displayed.

Make sure that the storagemedium you select is not read-only.

6. If you want to access the installationmedia via a shared network drive(network share) or save the configuration to a network share:

l Select Connect status media and/or installation media via net-work.

You can either obtain a temporary IP address via DHCP or configurean IPv4 or IPv6 address manually for the current InstallationMan-ager session, depending on your infrastructure.

l Configure a temporary IP address for the current InstallationMan-ager session.

Depending on your infrastructure, you can either obtain a temporaryIP address via DHCP or configure an IPv4 or IPv6 address man-ually.

7. Leave the other default settings unchanged and click onNext.

8. Click onDeployment.

The Installation Manager Deployment Process Selectionwindow isdisplayed.

9. Select the default option Typical and click onNext.

TheConfigure Your Unattended Operating System Installationwin-dow opens.


2.2 Quick step guides


10. Select the relevant Windows operating system and click onNext.

TheConfiguration for Disks and RAID Controller configurationstep, in which you configure hard disk drives and RAID controllers, isdisplayed.

11. Define the boot medium. You can either select a hard disk or an existingRAID array or define a new RAID array. You can also select individualhard disks.

Note the following:

If you define a new RAID array, an existing array is deleted onthe selected RAID controller.

12. Click onNext.

The dialog box for configuring an unattendedWindows installationappears.

13. Specify the details of theWindows installation, including user and com-puter name, administrator password, time zone, IP address and SNMPsettings for the ServerView management station.

14. Click onNext.

An overview of the installation parameters you configured is displayed.

15. Check your entries.

If necessary, use theBack button tomake corrections toindividual configuration steps.

Configuration is then completed.

16. Leave all insertedmedia unchanged and click onStart Installation.

The installation is then executed in unassistedmode in accordance withyour settings.


Note that all data on the boot hard disk or selected RAID arrayis lost during the installation.

You only need to intervene in the installation process to changedatamedia (for the operating system and, if necessary, for serv-ice packs and other applications).

Do not remove the DVDs or CDs until prompted!

Once the installation is complete, your server is ready for use.

2.2.2 Remote installation via deployment serverSome preparations are required on the deployment server and on the targetsystem before a remote installation.

Preparing the deployment server for the remote installationFollow the steps below:

1. Install InstallationManager as an independent application on the deploy-ment server. Install the PXE service and data packages for the remoteinstallation also (see "Installing InstallationManager" on page 69). StartInstallationManager on the deployment server (see "Starting Instal-lationManager on the deployment server" on page 98).

2. Start deployment (see "Starting remote deployment / remote systemconfiguration" on page 106).

3. Select the target system settings (see "Select the target system(Remote Installation and Remote System Configuration Only)" on page107).

4. Select the relevant operating system (see "Configure Your UnattendedOperating System Installation" on page 112).




5. Follow the configuration steps below in the order given for the selectedoperating system:l Configure Server Management settings (optional, see "Server Con-

figurationManager" on page 131).

l Configure hard disks and RAID controllers (see "Configuringmassstorage devices" on page 132).

l Configure the operating system parameters.

l Select an application for the installation.

For more information about the relevant configuration steps,refer to "ConfiguringWindows and starting the installation" onpage 149 and "Configuring Linux and VMware ESX/ESXi andstarting the installation" on page 199.

6. Save the configuration file, giving it a name of your choice. If you do notspecify a name, InstallationManager uses the default name ser-startbatch.xml.

Preparing the target system for the remote installationFollow the steps below.

In the BIOS setup of the target system:

1. EnablePXE bootmode (Boot Sequence - Boot from a networkdevice)

2. Place thePXE boot in the first position in the boot sequence.

Whenmaking your settings for the target system (see "Selectthe target system (Remote Installation and Remote SystemConfiguration Only)" on page 107), you can specify that PXEboot mode is to be activated (either with or without a restart ofthe target system) if the target system has a remoteman-agement component (BMC/iRMC/iRMC S2/S3/S4man-agement blade).


Starting the remote installationFollow the steps below:

1. Power on the target system.

Whenmaking your settings for the target system (see "Selectthe target system (Remote Installation and Remote SystemConfiguration Only)" on page 107), you can specify that PXEboot is to be initiated automatically after the installation starts ifthe target system has a remotemanagement component(BMC/iRMC/iRMC S2/S3/S4 / Management Blade).

2. Start the remote installation on the deployment server (see "Backing upthe configuration / starting the installation" on page 195 and "Backing upthe configuration / starting the installation" on page 249).

InstallationManager is booted on the target system. The unattended instal-lation is then started directly on the target hardware.

Operating system CDs/DVDs, service packs and application packages maybe automatically connected via the network drive that you configured whenconfiguring theWindows settings in theSystem Settings dialog box (see"System Settings" on page 174) and the Linux / VMware ESX/ESXi setttingsin theBasic Settings dialog box (see "Basic Configuration" on page 212).Essential installation data is copied to the installation directory on the targetsystem.




3 Local deploymentWith local deployment, you configure and start the installation of the oper-ating system locally on the target system. To do this, you need to boot Instal-lationManager on the target system from ServerView Suite DVD or from aproperly configured USB stick.

To enable booting from aUSB stick, you first have to configure thestick (see "Configuring the USB stick" on page 34).

Follow the steps below on the target system for local deployment:

1. Define the boot drive:

l If you want to boot from DVD: Define the DVD drive as a boot drive.

l If you want to boot from USB stick: Define the USB device as a bootdrive.

2. Boot the target system from the ServerView Suite DVD or from a prop-erly configured USB stick.

The boot operation automatically starts InstallationManager on the tar-get system.

3. Start the deployment function.

The following figure illustrates the steps involved in a local instal-lation.


3 Local deployment

Figure 1: Local installation (overview)


3.1 Booting Installation Manager from DVDYoumust define the DVD drive on the target system as a boot drive so thatthe target system can boot from PRIMERGY ServerView Suite DVD.

3.1.1 Standard PRIMERGY serverThe DVD drive is configured as a boot drive in the BIOS setup in the standardPRIMERGY server delivery. If this configuration is subsequently changed,the following adjustments are required before the installation:

For DVD drives on an IDE/SATA bus:

l Ensure that the relevant IDE channel is activated in the system boardBIOS and that the DVD drive is the first drive accessed when the sys-tem starts (refer to themanual on the BIOS setup or to the operatingmanual for your server for information about the boot sequence. Bothmanuals are included on the ServerView Suite DVD).

For DVD drives on a SCSI/SAS bus:

l Define the DVD drive in the system board BIOS as the first boot drive.You can also control the start properties of the DVD drive in the BIOS ofyour controller (refer to the operatingmanual for the controller).

3.1.2 PRIMERGY blade serversThe following steps are required to allow a server blade to boot from theDVD:

1. Connect the server blade to a DVD and floppy disk drive via a USBport.

2. Connect a keyboard, mouse andmonitor on the rear of the blade serverand route these to the relevant server blade using KVM switches.

3. Define the DVD drive as a boot drive.

The required DVD drives and floppy disk drives are available as option-al accessories.


3.1 Booting InstallationManager from DVD

3 Local deployment

Connecting the DVD drives and USB storage medium to the serverbladeFollow the steps below:

l Connect the breakout cable provided to the USB/VGA front connectorof the relevant server blade.

l Connect the DVD drive and, if necessary, a USB storagemedium (flop-py disk drive or USB stick) to the USB ports on the breakout cable.

l If the connected devices are not powered or are insufficiently poweredby the USB port, connect both devices to an external power supply.

l Switch on the blade server and the relevant server blade.

Connecting the monitor, keyboard and mouse to the PRIMERGYblade serverFollow the steps below:

l Insert the purple keyboard connector and greenmouse connector in thePS/2 ports on the rear of the blade server.

l Connect themonitor's data cable to the VGA connector (3, blue) on therear of the blade server and plug themonitor power cable into a ground-edmains outlet.

l Press the KVM switch (1) on the front panel of the server blade to routethe keyboard, mouse andmonitor to it.

For more information about the location of the KVM switch, refer to theoperatingmanual for your blade server.

Defining the DVD drive as a boot driveFollow the steps below:

l When prompted, press [F2] to access the BIOS setup of the serverblade.

l In the Phoenix BIOS Setup Utility, select theBootmenu and activatetheBoot from CD-ROM Drive option.


l Press [ESC] on your keyboard and select theExit Saving Changesoption in theExit submenu.

3.2 Booting Installation Manager from a USB stickAs an alternative to booting ServerView Suite from the DVD, you can alsoboot from aUSB stick. To enable booting from aUSB stick, you first have toconfigure a boot block on the stick. Then copy the entire contents of theServerView Suite DVD to the USB stick. You can then start the InstallationManager from aUSB stick on any USB-bootable server.

3.2.1 RequirementsTomake a USB stick bootable, you need:

l A PC onwhich the Vista orWindows 2008 operating system isinstalled.

l Administrator rights on the selected PC.

l The USB stick used shouldmeet the following requirements:

o Storage capacity of 8 GB or highero USB V2.0o The USB stick must be bootable.


3.2 Booting InstallationManager from aUSB stick

3 Local deployment

3.2.2 Configuring the USB stick

Note that youmust be logged on as administrator or have administratorrights to configure the USB stick.

1. Insert the ServerView Suite DVD into the DVD drive of a computer run-ningMSWindows Vista, MSWindows 7, MSWindows Server 2008,MSWindows Server 2008 R2, or MSWindows Server 2012.

2. Optional: Copy the complete contents of the current ServerView SuiteDVD onto the selected PC. This may significantly reduce the timerequired for "loading".

3. Connect the USB stick to the PC.

4. If the USB stick is not recognized, make sure that support for USBdevices is enabled in the BIOS setup. If the USB stick is not rec-ognized, restart the computer.

If the USB stick is still not recognized, the stick is either defective orthe BIOS system of the PC is not designed for USB devices. In thelatter case, you need a different PC that meets the above-mentionedrequirements.

5. Start theSetup.exe program in the root directory of the DVD (or theDVD copy). If “Auto Play” is activated, your system will start Setup.exeautomatically.

Note forWindows 7 orWindows Server 2008 R2:

To executeSetup.exe you need to be logged in as Administrator.


6. Select Create bootable SVS USB Stick and click Start.

7. Select the USB stick you want to load up.


3.2 Booting InstallationManager from aUSB stick

3 Local deployment

8. Select the feature set you want your stick to support when it is loaded.

l Feature set SVIM complete:

Creates a full copy of the SVS DVD onUSB stick.

Includes feature sets Deployment andMaintenance.

Requires an USB stick of 8 GB capacity.

l Feature set Deployment:

Prepares the USB stick to be a bootable substitute of the SVS DVDsupporting OS deployment on PRIMERGY systems (local, remote &BX400 Easy Installation)

Includes feature setMaintenance.


l Feature set "Maintenance":

Prepares the USB stick to be a bootable substitute of the SVS DVDsupporting SVIM's maintenance functionalities

o ServerView PrimeCollecto Multi Deployment Platform (MDP)


9. Click Create SVIM on removable device ….


3.3 Starting Installation Manager on the target systemBooting from ServerView Suite DVD

To boot the target system from the ServerView Suite DVD, proceed as fol-lows:

1. Ensure that the DVD drive is accessed, when you start the target sys-tem.

2. Insert the ServerView Suite DVD into the drive previously defined asthe boot drive.


The InstallationManager is started automatically on the target system onboot.

Booting from a prepared USB stick

You can also use the USB stick prepared for booting to save statusinformation. The status information is added to the USB stick.

To boot the target system from aUSB stick, proceed as follows:

1. Connect the USB stick to the USB port previously defined as the bootdrive.

2. Ensure that the BIOS of the target system is configured so that it bootsautomatically from aUSB stick.


If the USB stick is not recognized, make sure that support for USBdevices is enabled in the BIOS setup. If the USB stick is not rec-ognized, restart the computer. By now, the USB stick should be listedas a bootable device in the BIOS.


3.3 Starting InstallationManager on the target system

3 Local deployment

If the USB stick is still not recognized, it may be connected to a non-bootable USB port, or the BIOS system of the PC is not designed forUSB devices.

In the latter case, you will have to start the InstallationManager fromthe DVD.

The InstallationManager is started automatically on the target system onboot.

3.4 Windows Boot Manager - Selecting standard /express installation

TheWindows Boot Managerwindow is not displayed inUEFI boot mode.

Starting the boot process opens theWindows Boot Managerwindowwhere you can determine whether you want to start a standard server instal-lation or to use an accelerated procedure for installing aWindows Server2008 x86 / MSWindows Server 2008 (R2) x64 / MSWindows Server 2012operating system.

Windows 2008 x86 / Windows 2008 (R2) x64 / Windows 2012express installation can only be accomplished as a "mere" oper-ating system installation. The following restrictions apply:

l Only MSWindows Server 2008 x86 / MSWindowsServer 2008 (R2) x64 / MSWindows Server 2012 oper-ating systems can be installed.

l Configuring any hardware settings by using the ServerConfigurationManager is not possible. However, hard-ware settings can be configured after operating systeminstallation has been completed.

l Configuring RAID controllers is not possible. RAID con-troller configuration should therefore be completed beforean express installation is started.


Standard installation and express installation (Windows Server 2008 /2008 R2 / 2012 only)

To install a MSWindows Server 2008 x86 / MSWindows Server 2008 (R2)x64 / MSWindows Server 2012 operating system via standard installation,the automatic boot process initially starts theWinPE 5 platform and sub-sequently has to reboot the server to change to the appropriateWinPE32(Windows Server 2008 x86 / Windows Server 2008 (R2) x64) / WinPE 4 (Win-dows Server 2012)Windows Server platform. In contrast, Windows 2008x86 / Windows 2008 (R2) x64 / Windows 2012 express installation shortensthis procedure as follows:

l The deployment process in the whole is accelerated.

l The appropriateWinPE 3.1 (Windows 2008 / Server 2008 (R2) x64) /WinPE 4 (MSWindows Server 2012) platform is used right from thestart. A server reboot is not necessary.

Windows Boot Menu

Figure 2: Windows Boot Manager


3.4Windows Boot Manager - Selecting standard / express installation

3 Local deployment

ServerView Installation Manager (WinPE64) [HW conf. and OS inst]Standard installation of the operating system. All supported operating sys-tems can be installed. No restrictions aremade.

If you do not select any options in theWindows Boot Menu:After a delay of some seconds, InstallationManager will auto-matically continue booting with this option.

Win2008 x86 express installation (w/o HW / RAID preparation)InstallationManager performs an express installation of a 32-bit WindowsServer 2008 operating system.

Win2008 x64 express installation (w/o HW / RAID preparation)InstallationManager performs an express installation of a 64-bit WindowsServer 2008 / Windows Server 2008 R2 operating system.

Win2012 express installation (w/o HW / RAID preparation)InstallationManager performs an express installation of aWindowsServer 2012 operating system.

Maintenance Mode (WinPE32) [PrimeCollect and MDP]InstallationManager is booted in theMaintenanceMode allowing you touse PrimeCollect andMDP.


3.5 Installation Manager - initial windowAfter booting, the InstallationManager opens the following window whereyou can select the GUI language.

Figure 3: ServerView Installation Manager - select the GUI language

l Select your preferred GUI language by clicking on the corresponding but-ton.

The InstallationManager initial window is then displayed.


3.5 InstallationManager - initial window

3 Local deployment

Figure 4: ServerView Installation Manager - initial window

Create bootable SVS USB stick ...Creates a bootable USB stick, which allows you to boot the InstallationManager from aUSB stick on any USB-bootable server.

l For the requirements tomake a USB stick bootable, see "Require-ments" on page 33.

l For details on configuring a USB stick, see "Configuring the USB stick"on page 34.

Clicking onCreate bootable SVS USB stick ... has the sameeffect as starting theSetup.exe program in the root directory ofthe DVD.


After booting, theStandard mode option is enabled by default for InstallationManager under Installation Manager mode.

You can also start the following programs from the initial window:

PrimeCollectThis program collects diagnostic data for service personnel. Moreinformation about PrimeCollect is provided on the ServerView SuiteDVD.

MDP (Multi Deployment Platform)In this mode, the InstallationManager platform is used as amulti-deployment platform, on which customer-specific MDP agents canbe started. For more information, refer to theWhite Paper on theServerView Suite DVD.

More information about these products is provided on the ServerViewSuite DVD.

Installation Manager settingsYou can configure the following settings in the initial window:

Regional and language settingsThe keyboard layout is set by default to the country variant you selectedfor your computer.

If necessary, you can select another country variant for the keyboard lay-out.

Connect status media and/or installation media via networkYoumust select this option if you are using amedium with a prepared con-figuration file and/or an installationmedium accessed via the network.

You can either obtain a temporary IP address via DHCP or configure anIPv4 or IPv6 address manually for the current InstallationManager ses-sion, depending on your infrastructure.



3 Local deployment

IPv4 settingsThese settings are used to configure an IPv4 address for the current Instal-lationManager session.

Get IP address automatically (DHCP)This option retrieves the IPv4 address dynamically via a DHCP serverin the network.

Do not select theGet IP address automatically (DHCP)option if a DHCP server is not available in your network.

If you enable theDHCP option and a DHCP server is notavailable, the server will not boot because it will be unable toget an IP address.

Take the following IP addressDefine a static IPv4 address here if the IP address is not to beretrieved from aDHCP server.

IP addressIPv4 address for the current session

Subnet maskSubnet mask

Default gatewayDefault gateway

IPv6 settingsConfigures an IPv6 address for the current InstallationManager session.

Stateful address configuration (DHCPv6)This option retrieves a (stateful) IPv6 address dynamically via aDHCPv6 server in the network.

Stateless address auto configurationRetrieves a (stateless) IPv6 address using autoconfiguration.


Status backup mediaSelect the relevant data backupmedium:

on local drive (floppy / USB stick)Insert themedium (floppy disk or USB stick) and select the relevantdrive letter.

The backupmediummust not be write-protected.

A USB stick must already be inserted in the USB port beforethe system starts.

If you forgot to do this and want to save the configurationfile: Insert the USB stick now and start a reboot from theServerView Suite DVD.

via networkDefine the required share settings and enter the folder, account andpassword.

No status backupSelect this option if you will not need the configuration data after theend of the session.

Note that the configuration data is lost at the end of the ses-sion and cannot be restored if you select this option.

General buttonsThe following buttons are provided in the initial window:

RescanUpdates the list of local drives.

Use this function, if you have connected a USB device to your PC afterInstallationManager has been started.

ContinueTakes you to the next window.



3 Local deployment

ExitCloses the InstallationManager and terminates the session.

l Click onContinue.

The settings specified in this dialog box becomes effective and the userinterface of the InstallationManager is displayed.

3.6 Graphical user interface (GUI) of the InstallationManagerAfter you have started InstallationManager from the DVD or from the USBstick, the start page of the InstallationManager GUI is displayed.

Figure 5: ServerView Installation Manager - graphical user interface (GUI)


The InstallationManager GUI comprises the following areas:

l Menu bar

l Display area

Menu barYou can execute the following functions from themenu bar:

HomeDisplays the welcome screen of the InstallationManager GUI.

DeploymentStarts system configuration and installation of an operating system.

ConfigurationStarts configuration of BIOS and hardware of the target system withoutinstalling an operating system.

MaintenanceOffers a selection of maintenance programs, which you can use to per-form configuration andmaintenance tasks on the server, independently ofthe operating system installation.

InformationProvides information about PRIMERGY servers and installation.

ExitOffers Options to reboot or shut down the server.

Please remove all removablemedia from the correspondingdrives before you shut down or reboot the server.

RebootReboots the server.

ShutdownShuts down the server.


3.6 Graphical user interface (GUI) of the InstallationManager

3 Local deployment


HelpStarts the online help.

Display areaThe display area displays the dialog step associated with the currently select-ed function.

In the case of the initial page of the InstallationManager GUI, the displayarea comprises the following elements:

l The InstallationManager version is displayed at the top of the screen.

l The system data of the PRIMERGY server is displayed underServerInformation.

l TheDeployment, Configuration,Maintenance and Information linksallow you to start the same functions that can be started from the cor-responding function buttons in themenu bar (seeMenu bar above).

3.7 Starting local deploymentFollow the steps below to start the local deployment on the target system:

1. In theMAC field of the InstallationManager GUI (see "Graphical userinterface (GUI) of the InstallationManager" on page 46), theMACaddress of the network card is displayed.

2. Click on the Deployment button in themain screen area or on theDeployment option in themenu bar.

The Installation Manager Deployment Process Selectionwindow isdisplayed.


Figure 6: Installation Manager Deployment Process Selection window

3. Select Typical orCustomized, depending on whether you want toexecute the configuration and/or installation with default values (Typ-ical) or with values that meet your specific requirements (Cus-tomized).

The following table shows the various configuration options available inthe Typical andCustomized installationmodes:

Configuration of ... typical customized

BIOS/BMC settings withServer ConfigurationManager

- optional

RAID/hard disk settings basic advanced

Hard disk partitioning 1 partition individual settings


3.7 Starting local deployment

3 Local deployment

Configuration of ... typical customized

Operating system parameters basic individual settings

Installation of ServerView products(e.g. SNMP agents, update agent)

automatic optional

Installation of add-on software - optional

4. Click onNext.

The initial window for configuring the automatic installation process is dis-played:

Figure 7: Initial window: Configure your Unattended Operating System Instal-lation


Configuration fileHere you specify whether you want to create a new configuration file oruse the values from an existing one.

Create a new configuration fileCreates a new configuration file.

Start an installation based upon an existing configuration fileInCustomizedmode, you can select a configuration file. The inter-preted contents of this file are then displayed on the right of the win-dow underContents of Configuration File.

Click the folder icon to select an existing configuration file. A dialogbox opens that allows you to select an appropriate configuration filefrom a local backupmedium.

InstallationManager provides the configuration file’s content in thecurrent session as default values for the configuration. You can usethese values as required and save them in the same configurationfile or a new configuration file at the end of the session.

Contents of Configuration FileThe contents of the configuration file (if one exists) are displayed here.

Select the operating systemSelect the version, edition and service pack of the operating systemyou want to install.

In the case of aWindows Server 2008 (R2) expressinstallation: Only the operating system configured forexpress installation can be selected (see "Windows BootManager - Selecting standard / express installation " onpage 38).


3.7 Starting local deployment

3 Local deployment

Server Management Configuration

Edit Server Management SettingsIf you select this option, Server ConfigurationManager is called aspart of the customized configuration of the installation process.Server ConfigurationManager allows you to configure server-spe-cific system settings for the target system.

This option is not available in the following cases:

l in Typical installationmode

l in the context of Windows Server 2008 (R2) expressinstallation.

5. Click onNext.The wizard for configuring and starting the unattended installation proc-ess starts.

6. To install aWindows operating system, see "ConfiguringWindows andstarting the installation" on page 149.l Typical Windows installation.

l CustomizedWindows installation.

If you want to install Windows Server Core, youmustselect Customizedmode.

7. To install a Linux operating system or VMware ESX/ESXi, see "Con-figuring Linux and VMware ESX/ESXi and starting the installation" onpage 199.l Typical Linux / VMware ESX/ESXi installation.

l Customized Linux / VMware ESX/ESXi installation.


3.8 Starting local system configurationFollow the steps below to start the local system configuration on the targetsystem:

1. In theMAC field of the InstallationManager GUI (see "Graphical userinterface (GUI) of the InstallationManager" on page 46), theMACaddress of the network card is displayed.

2. Click on theConfiguration button in themain screen area or on theConfiguration option in themenu bar.

3. Click onNext.

The initial window for configuring the server system is displayed:

Figure 8: Initial window: Configure


3.8 Starting local system configuration

3 Local deployment

Configuration fileHere you specify whether you want to create a new configuration file oruse the values from an existing one.


Start an installation based upon an existing configuration fileHere you can select a configuration file. The interpreted contents ofthis file are then displayed on the right of the window underCon-tents of Configuration File.

Click the folder icon to select an existing configuration file. A dialogbox opens that allows you to select an appropriate configuration filefrom the configfiles directory of the InstallationManager repository(remote installation) or from a local backupmedium (local instal-lation, customizedmode).

InstallationManager provides the configuration file’s content in thecurrent session as default values for the configuration. You can usethese values as required and save them in the same configurationfile or a new configuration file at the end of the session.

You can only use configuration files designed for systemconfiguration. Configuration files created for operatingsystem installation cannot be used in this context.

Contents of Configuration FileThe contents of the configuration file (if one exists) are displayed here.


Action after ConfigurationHere you specify whether the server shall be rebooted or shut downafter configuration is completed.

RebootReboots the server after configuration is completed.

ShutdownShuts down the server after configuration is completed.

Server Management Configuration

Edit Server Management SettingsIf you select this option, Server ConfigurationManager is called aspart of the system configuration process. Server ConfigurationMan-ager allows you to configure server-specific system settings for thetarget system.

5. Click onNext.The system configuration starts.

Installation Manager wizardsThe following wizards guide you through the system configuration:

l Server ConfigurationManager

The Server ConfigurationManager is only available if youselect theSystem Management Configuration option.

This wizard helps you to configure the general system behavior of thetarget system and of the target system BMC/iRMC/iRMC S2/S3/S4where applicable. The Server Configuration wizard is described in sec-tion "Server ConfigurationManager" on page 131.

l Wizard for configuring RAID controllers

You use this wizard to configure RAID controllers in the target system.The wizard is described in section "Configuring RAID controllers" onpage 137.



3 Local deployment

Configuration Info (Summary)This configuration step provides a summary and overview of all systemsettings you have configured. You can now save your configuration to afile and/or enable your settings.

Figure 9: Backing up the configuration / starting system configuration

Save Configuration to FileDefines a name for the configuration file (default name: ser-startbatch.xml), in which the configured parameters are saved.

Click the folder icon to define a name for the configuration file. A dialogbox is displayed.

l You can specify the file name (default name: serstartbatch.xml).You can overwrite this default namewith any name of your choice.


l You can select or create a folder in which InstallationManager willstore the configuration file. The folder is stored on the local backupmedium:

You should not use the default name for long-term backup of theconfiguration data.

The configuration file is created as a temporary file for the currentInstallationManager process and is no longer available for futurestarts of the InstallationManager.

To save the configuration file permanently, you can save it to anexternal medium (e.g. memory stick).

SaveBacks up the configured parameters in the file that you have specified intheSave the Configuration to File dialog.

System configuration is not started.

Start ConfigurationStarts system configuration and backs up the configured parameters inthe file you have specified in theSave the Configuration to File ...dialog.

If you are using an external backupmedium (USB stick), note:

Do not remove themedium. Otherwise, the system configurationprocess may be stopped.




4 Remote deploymentFor a remote installation of the operating system, install and start InstallationManager on a deployment server .

In this manual, the term "deployment server" refers to servers on whicha PXE server is installed.

This chapter provides information about the following topics:

l Remote installation (overview)

l Preparing the deployment server for the remote installation:

o Installing a DHCP server (if one does not already exist in the LANsegment)

o Installing a PXE server (if one is not already available)o Installing data packages for the remote installationo Installing InstallationManager

l Preparing the target system for a PXE boot

l Starting remote deployment

l Multi-deployment of PRIMERGY servers

The following figure illustrates the steps involved in a remote instal-lation:


4 Remote deployment

Figure 10: Remote installation (overview)


Explanation

1) If the target system has a remotemanagement interface (BMC, iRMC,iRMCS2/S3, or management blade), you can specify in theSelect thetarget system step that the PXE mode is to be activated automaticallyon the target system as part of the deployment process (either with orwithout a restart of the target system). Depending on your settings, itmay therefore not be necessary to separately enable PXE boot mode /place the PXE boot in the first position / power on the target system.

2) For details, see section "Progression of the installation process" onpage 1.

4.1 Remote installation (overview)A remote installation allows you to install an operating system on a PRIM-ERGY server from a deployment server via the network. For this purpose,InstallationManager is booted on the target system using the PrebooteXecution Environment (PXE)mechanism and is executed there remotely.


4.1 Remote installation (overview)

4 Remote deployment

4.1.1 Preparing the installation

In the LAN segment of the target system aDHCP server is required forPXE boot.

For Blade Server systems (such as PRIMERGY BX600):

The server blade that is to be installedmust be connected to the localnetwork via the switch blade.

The following steps are required to prepare for a remote installation:

1. Prepare the deployment server for the remote installation.

l Install the InstallationManager package.

The package consists of the following components, which areinstalled automatically by the InstallationManager installationwizards. These wizards detects whether some of these com-ponents are already installed.

o Fujitsu PXE Serviceo InstallationManager softwareo InstallationManager Data Packages

2. Prepare the remote resource server (optional).

Youmay use a remote server for storing and sharing the resourcesrequired for the installation process. In this case, the target server hasto be granted the access rights to access the remote resource server.


3. Prepare the target system for the remote installation.

l Activate the PXE boot mode in the BIOS.

l Configure the boot sequence for the PXE boot (theBoot from a net-work device) option.

Alternatively, you can configure the boot sequence via the webinterface of the iRMC / iRMC S2/S3/S4 / Management Bladeof the target system.

4. On the deployment server:

l Start InstallationManager and use the wizards provided to configurethe installation.

Save the configuration, if required.

l Initiate the installation process.

5. (Re)start the target system. This initiates the PXE boot of the target sys-tem.

Whenmaking your settings for the target system, you can specify thatPXE boot mode is to be activated (either with or without a restart of thetarget system) if the target system has a remotemanagement com-ponent (BMC/iRMC/iRMC S2/S3/S4/Management Blade).



4 Remote deployment

4.1.2 Progression of the installation processAfter the installation process is started from the deployment server, instal-lation of the operating system continues automatically. In other words, theuser is not prompted to enter any other data for the remainder of the instal-lation process.

If a user account for accessing InstallationManager data packages onthe deployment server was created during configuration of the instal-lation process, you are prompted to enter this user account and the cor-responding password.

The installation process

l establishes a platform structure for the selected system hardware.

l creates a status folder.

l activates the PXE server access list, which contains the current MACaddress of the target system.

For security reasons, the PXE service only accepts PXE requests fromMACaddresses specified in the access list.

Following the PXE boot process, the InstallationManager service that wasstarted on the target system copies the configuration file from the deploy-ment server and connects to the relevant datamedia in the network (for theInstallationManager-specific content, operating system, service packs andapplications). The unattended installation is then executed in the samewayas if InstallationManager had been started from a local DVD drive on the tar-get system.

Once the installation is complete, an installation log, which was created forthe current remote installation process, is copied to the deployment serverand is saved there. You can display the logged data using the InstallationMonitor (see chapter "InstallationMonitor - Monitoring remote installation" onpage 251).

The following figure illustrates the steps involved in a remote installation.


1. Configure the installation process.

2. Save the configuration file.

3. Start the PXE service (so that thedeployment server can acceptrequests from the target system).

4. Initiate a PXE (re)boot of the targetsystem (manually or automaticallyvia iRMC/Management Blade).

5. The PXE service boots a clientinstance of InstallationManager.

6. The deployment server directorystructure is loaded.

7. The client instance creates theRAID array andOS partitions.

8. The client instance connects to thedatamedium for the operating sys-tem, application software and serv-ice packs.

9. The client instance starts the auto-matic installation.

10. The deployment server starts thereboot of the installed server inorder to start the operating systemand starts customer-specificscripts for installing additional appli-cations (forexample, ServerViewagents).

Figure 11: Progression of a remote installation

Formore information about the PXE boot, see section "The PXE process" onpage 285.



4 Remote deployment

4.2 Preparing the deployment serverThe LAN segment of the InstallationManager requires a DHCP server.

For multi segment deployment see section "Configuring router for multisegment deployment" on page 94.

For Blade Server systems (such as PRIMERGY BX600):

The server blade that is to be installedmust be connected to the localnetwork via the switch blade.

Before you can perform a remote installation, the following software pack-ages must be installed on the deployment server:

l Windows Server 2008 Server orWindows Server 2012 platform

l Internet Explorer V7 (or higher) or Mozilla Firefox V3.0 or higher (rec-ommended)

l InstallationManager package

The package consists of the following components which areinstalled automatically by the InstallationManager installationwizards. These wizards detects whether some of these com-ponents are already installed.

o Fujitsu PXE Serviceo InstallationManager softwareo InstallationManager Data Packages

l For Linux and VMware ESX installations:

NFS, HTTP or FTP server


l If dynamic IP adress management by DHCP is used, only oneDHCP server per LAN segment is allowed. If multiple DHCPservers are in use, only "reserved IP" address assignemnet isallowed.

l If multiple PXE servers are in use in one LAN segment, all PXEservers must be configured in passive/defensivemode". TheServer reacts onMAC addresses only listed in its current acti-vatedMAC adress/Image assignment list.

For standard InstallationManager / Deployment Manager usage theoriginal Fujitsu PXE service is required.

It may not be possible to start the InstallationManager on the deploy-ment server in the following cases:

l A PXE service is already installed on the deployment server sys-tem (e.g. SystemcastWizard, SystemcastWizard Professional,Microsoft RIS, Symantec Altiris).

l Installing or uninstalling ServerView Suite components (e.g.ServerView Operations Manager) prior to version 4.80 on a deploy-ment server system.

In this case, start the repair tool RepairAfterOMUpdate.exe.Once InstallationManager has been installed, you will find therepair tool on the deployment server system under:

<drive>:\ Program Files\Fujitsu\ServerView Suite\InstallationManager.

Do not use ServerView InstallationManager V10.nn.nn together withServerView Integration Pack for Altiris Deployment Server V3.0 (orolder). For compatibility reasons, use ServerView Integration Pack forAltiris Deployment Server V3.1 (or later).


4.2 Preparing the deployment server

4 Remote deployment

4.2.1 Installing and configuring a DHCP server on the deploy-ment server

The installation of a DHCP server on the deployment server is onlyrequired if a DHCP server is not already available in the LAN segmentof the deployment server.

Beside Scope option (060: PXE client) no further settings related tobootstrap images or bootstrap server definition should be assigned.These are required for BootP protocol, but not for a PXE protocol.

Figure 12: Wizard for Windows components

1. Start the wizard forWindows components from theWindows controlpanel:

Add/RemoveWindows Components (1)


2. In the wizard for adding or removingWindows components, select thecheck box next to theNetwork Services component (2).

3. Click on theDetails button (3).

4. In the list of available networking services, select the check box next totheDynamic Host Configuration Protocol (DHCP) component.

5. Use the DHCP Manager to define a range of IP addresses. No specialreservations, lease durations or server options are required.

6. Activate the new IP range.

4.2.2 Installing Installation ManagerThe InstallationManager must be installed on a system with theWindowsServer 2008 orWindows Server 2012 operating system. A user account withadministrator rights is required.

1. Insert ServerView Suite DVD into the DVD drive. The initial windowopens.

If the application does not start automatically, run theSetup.exe file.

2. Select the Install Installation Manager option in the initial window.

3. Click Start. A settings dialog box opens.

4. In the Installation Manager Functionality group, select the followingoptions:l Classic + Remote Installation: allows you to create and edit con-

figuration files for the installation of operating systems on PRIM-ERGY servers. It also installs Remote Installation functionality,which allows you to configure and install a PRIMERGY systemfrom the deployment server via PXE boot. The PXE Server com-ponent is also required for a remote installation. You should alsoselect the Data packages for Remote Installation option to enablean unassisted deployment process.



4 Remote deployment

l PXE Server: must be installed on the deployment server if youwant to perform a remote installation. Installation of the PXEserver is then automatically initiated before the installation ofInstallationManager. This option is set by default if a PXE serveris not yet installed on the deployment server.

5. In the Installation Manager add-on componentsgroup, select theData packages for Remote Installation option if it is not selected bydefault. These data packages, which are required to optimize a remoteinstallation, are installed automatically before installation of InstallationManager.

6. Click OK to start the installation.

Youmay be prompted to restart your server to complete the instal-lation.

A restart may be necessary due to a number of important changes thathave beenmade to theWindows registry that affect, for example, thestartup of the PXE service.

l Before you restart the server, remove the ServerView Suite DVDfrom the DVD drive.

4.2.2.1 Installing the PXE server

If you selected thePXE Server option in the component selection window,the PXE server is installed before InstallationManager.

1. Click on OK to confirm.

The first window of the installation wizard is displayed.

2. Click onNext.

3. Select the directory in which the PXE server is to be installed.

4. Click onNext.

5. Select the IP mode for the PXE service.

IPv6 requires a DHCPv6 server in the network. Local DHCPv6 can-nont be used onWindows Server 2008 R2 or earlier versions.


6. Click onNext.

7. Select the LAN card that the PXE server is to use to access the net-work.

8. Click onNext.

9. Follow the steps below:

l Select Yes only if a DHCP server is installed local to the PXE serveron the same deployment server. In this case, InstallationManagerautomatically adds a server option (060: PXE client) to the DHCPserver, whichmeans that the local DHCP server can be used as aproxy DHCP (PXE redirection service).

This step is also required if a DHCP service was installed after-wards local to the PXE service later.

l Select No if an external DHCP server is used.

Note the following:o If incorrect details of the proxy DHCP configuration are

entered, the PXE server will not be accessible to the PXEclient (on the target system).

o Ensure that the LAN cable is connected before you install thePXE service.

o A LAN segment may contain only one DHCP server and onePXE server. Otherwise, problems may arise in the com-munication between the deployment server and the target sys-tem.

o Note that a DHCP server must be installed in the LAN seg-ment for the remote installation. If a DHCP server is not avail-able, terminate the installation of the PXE server. For multisegment deployment see also section "Configuring router formulti segment deployment" on page 94.



4 Remote deployment

o If dynamic IP adress management by DHCP is used, only oneDHCP server per LAN segment is allowed. If multiple DHCPservers are in use, only "reserved IP" address assignemnet isallowed.

o If multiple PXE servers are in use in one LAN segment, allPXE servers must be configured in "passive/defensivemode".The Server reacts onMAC addresses only listed in its currentactivatedMAC address/Image assignment list.

10. Click on Install to start installing the PXE server.

11. Click onNext.

A window opens to inform you that the PXE server has been installedsuccessfully.

12. Click on Finish to complete the installation.

4.2.2.2 Installing data packages for the remote installation

If you enabled theData packages for Remote Installation option in the ini-tial window when selecting components, the data required for the remoteinstallation is copied to the hard disk.

The first dialog box of the installation wizard is displayed.

1. Click onNext.


Figure 13: License agreement

2. Accept the license agreement.

3. Click onNext.TheUser Information dialog box is displayed.

4. Enter your name and the name of your company.

5. Click onNext.TheDestination Folder dialog box is displayed.

6. Select the destination folder to which you want to copy the data pack-ages for the remote installation and assign a share name under whichthe installation data can be accessed in the network.

7. Click onNext.



4 Remote deployment

Figure 14: Defining a user account for access by the PXE client

8. Select Browse to select a user account in your network, or create anew account that can be used by the PXE client to access the datapackages for the remote installation.Domains should be entered in the form: <domain name>\<user name>

You have the option of entering the user account defined herewhen you define the target system at the start of the con-figuration session for the remote installation. In this case,InstallationManager automatically releases the installationdata for access by the PXE client. Otherwise, you are prompt-ed to enter a user name and password when installing the tar-get system.

9. Click onNext.


Figure 15: Starting installation of the data packages

10. Click onNext to start installing the data packages.

This process may take several minutes because approx-imately 5 GB of data is copied during the installation.

A progress bar indicates how the installation is progressing.

Figure 16: Installation of data packages in progress - the progress bar



4 Remote deployment

A window opens to inform you that installation has been successfullycompleted.

11. Click on Finish.

This starts the next installation step automatically.

4.2.2.3 Installing JBoss Application server

If you enabled theClassic + Remote Installation option in the initial win-dow while selecting components, installation of the JBoss Application Serverstarts now.

The first dialog box of the installation wizard opens.

Figure 17: Install JBoss Applicaion Server dialog box

1. Click onNext. The License Agreement dialog box opens.


Figure 18: License agreement dialog box


3. Click onNext. TheReadme Information dialog box opens.

4. Click onNext. TheDestination Folder dialog box opens.

5. Select the directory in which the JBoss Application Server is to beinstalled.

6. Click Next. The JBoss Service Logon Information dialog box opens.



4 Remote deployment

Figure 19: Specifying JBoss Service Logon Information

7. Specify a user account for running the JBoss service or whether youwant to use the built-in account LocalService.

8. Click onNext. TheSelect Directory Server dialog box opens.

Figure 20: Select Directory Server dialog box


9. Select the type of directory server you want to use for InstallationMan-ager:l a new installation of OpenDS provided with InstallationManager

l a directory server already used in your network, e.g., MS ActiveDirectory

10. Click Next. TheDirectory Service Settings dialog box opens.

Figure 21: Directory Service Settings dialog box

11. Enter the name of the directory server as fully qualified domain name. Ifno directory server is installed, the default options for the OpenDS direc-tory service are displayed.

12. If the directory service is already installed, the following options have tobe filled in, to ensure that InstallationManager can use the directoryservice for single sign on and role based access control.:l Port: communication port, default 1474

l SSL: secure communication, default Yes

l Base DN: distinguished name in LDAP notation



4 Remote deployment

l User Search Base: LDAP user search base (location where allLDAP users exist.) in LDAP notation

l User: user account in LDAP notation

l Password: password for the user account

13. Click Next. TheAdministrative User Password dialog box opens.

Figure 22: Administrative User Password dialog box

14. Enter the password for the administrative user svuser and confirm thepassword by entering it again.

15. Click onNext. TheComputer Details dialog box opens.


Figure 23: Computer Details dialog box

16. Check the network parameters that were automatically detected foryour system.

17. Click onNext. TheReady to Install the Application dialog boxopens.



4 Remote deployment

Figure 24: Starting installation of the JBoss Application Service


18. Click onNext to start the installation.

The installation wizard indicates how the installation is progressing ...

Figure 25: Completing the installation

... and informs you when the installation has been successfully com-pleted.



4 Remote deployment



This starts the next installation step automatically.

4.2.2.4 Installing Installation Manager

If you enabled theClassic + Remote Installation option in the initial win-dow while selecting components, installation of the InstallationManagerstarts now.

The first dialog box of the installation wizard opens.


Figure 27: Install Installation Manager dialog box

1. Click onNext. The License Agreement dialog box opens.

Figure 28: License agreement dialog box


3. Click onNext. TheUser Information dialog box opens.

4. Enter your name and the name of your company.



4 Remote deployment

5. Click onNext. TheDestination Folder dialog box opens.

6. Select the directory in which InstallationManager is to be installed.

7. Click onNext. TheReady to Install the Application dialog boxopens.

Figure 29: Starting Installation Manager


8. Click onNext to start the installation.

The installation wizard indicates how the installation is progressing ...


... and informs you when the installation has been successfully com-pleted.





4 Remote deployment

A message box opens advising you to unblock some settings of theWindows firewall (if enabled). This is required for the Deployment Serv-ice, the PXE Services, and the TFTP Services.

10. Click onOK to unblock the respective firewall settings.

InstallationManager is now installed on the deployment server. Theoptions for starting InstallationManager are described in section "Start-ing InstallationManager on the deployment server" on page 98.

At the end of the installation the JBoss application server is started. Theinstallation waits for the completion of the start about three to fiveminutesdepending on the system performance.

4.2.3 Extensions for the remote installation of Linux andVMware ESX/ESXi systemsBefore you can perform a remote installation of Linux or VMware ESX on thetarget system, the installation sources must be copied as follows:

l In the case of Linux / VMware ESX, from the corresponding Linux /VMware ESX installationmedia to an FTP/NFS or HTTP server. Youcan use any FTP, NFS or HTTP server that is accessible to the targetsystem and has sufficient bandwidth. The InstallationManager's boot-strap loader downloads the required installation packages from the FTP,NFS or HTTP server.

l In the case of VMware ESXi, from the VMware ESXi installationmedi-um to a network drive of your network that is accessible to the targetsystem. The InstallationManager's bootstrap loader downloads therequired installation packages from this network drive.


Setting up an NFS, HTTP or FTP server

In the case of NFS, the server usedmust be a Linux system.

To set up an FTP server on aWindows computer, youmust install the Inter-net Information Server (IIS) fromMicrosoft or similar software from anothervendor. For more information, refer to the documentation for the software inquestion. The deployment server on which InstallationManager is running isalso suitable for use as an FTP server.

To set up an NFS, FTP or HTTP server on a Linux system, refer to thesystem documentation.

Setting up a RedHat Linux installation sourceThe following RedHat Linux versions are supported:

l RedHat Enterprise Linux 5 “i386”the last two updates

l RedHat Enterprise Linux 5 “x86_64”the last two updates

l RedHat Enterprise Linux 6 “i386”the two last updates

l RedHat Enterprise Linux 6 “x86_64”the two last updates

In order to make the installation data available on the NFS, FTP or HTTPserver, youmust copy the required files from the installationmedia into therelevant NFS, FTP or HTTP file tree.

Follow the steps below:

1. First, create a subdirectory with a short, unique name (e.g RedHat) as abasis for the installation sources of the relevant RedHat system.

2. Then copy theRedHat directories (including all of their subdirectories)from all installationmedia of the relevant RedHat distribution into thisnew subdirectory.



4 Remote deployment

When the copy process is complete, you should have a RedHat direc-tory containing the contents of all RedHat directories on themedia.

3. Enter the basic subdirectory you have just created in the installation wiz-ard for the relevant RedHat Linux system together with the address ofthe NFS or FTP server.

Setting up a SuSE Linux Enterprise 10 / SuSE Linux Enterprise 11installation sourceIn order to make the installation data available on the NFS, FTP or HTTPserver, youmust copy the required files from the installation DVD to the rel-evant NFS, FTP or HTTP file tree.

The following versions are supported:

l SuSE Linux Enterprise Server 10 Edition i386 and x86_64 (including thelatest two Service Packs)

l SuSE Linux Enterprise Server 11 Edition i386 and x86_64 (includingService Pack 1)

To setup the installation source:

1. Create a subdirectory calledSLES10 orSLES11.

2. Copy the contents of the DVD, including all subdirectories, unchangedinto this new directory (a 1:1 copy).


Setting up a VMware ESX installation sourceIn order to make the installation data available on the NFS, FTP or HTTPserver, youmust copy the required files from the installation DVD to the rel-evant NFS, FTP or HTTP file tree.


l VMware ESX 4.1.x


1. Create a subdirectory calledVMWARE.


Setting up a VMware ESXi installation sourceIn order to make the installation data available on a network drive within yournetwork, youmust copy the required files from the installation DVD to the rel-evant directory of this drive.


l VMware ESXi 5.x


1. Create a subdirectory calledVMWARE.




4 Remote deployment

4.2.4 Verifying the services (PXE, TFTP, DHCP)Remote installation via deployment server requires the following:

l PXE (Preboot eXecution Environment) server and TFTP server areinstalled and have been started on the deployment server.

l If no DHCP (Dynamic Host Configuration Protocol) service is availablein the LAN segment of the deployment server: A DHCP server needs tobe running on the deployment server.

l For PXE boot a DHCP (Dynamic Host Configuration Protocol) serviceis required in the LAN segment of the target server: If the target serverand deployment server are in the same segment, it could also beinstalled on the deployment server itself or elsewhere in the current IPbroadcast domain.

For multi segment deployment see also section "Configuring router formulti segment deployment" on page 94.

Verifying the PXE server and the TFTP serverTo verify that the PXE server and the TFTP server are installed and havebeen started on the deployment server, proceed as follows:

1. Click Start - Administrative Tools - Services on the DeploymentServer.

2. Ensure that the PXE service and the TFTP service are installed andstarted.

Verifying the "DHCP Service" serviceTo find out if a centralized DHCP service is available in the LAN segment ofthe target server, contact your LAN administrator.

If no centralized DHCP service is available, verify that a DHCP service isrunning on the deployment server.

Proceed as follows:


1. Select Start - Administrative Tools - DHCP on the deploymentserver.

The DHCP administration utility starts.

2. In the tree view of the DHCP administration utility, click onServerOptions.

TheServer Options dialog box opens.

3. Make sure that the 060 ClassID option is selected in theServer Prop-erties dialog box.

4.2.5 Configuring TFTPTFTP (Trivial File Transfer Protocol) offers a very basic subset of the FileTransfer Protocol (FTP) functionality. In particular, TFTP provides no authen-tication.

PXE-based remote installation uses the TFTP service to transfer the bootimage to the target system. For this purpose, theGuest account must begranted the appropriate access permissions for the tftp folder:

l Traverse Folder / Execute File permission

l List Folder / Read Data permission

l Comprehensive "read" permissions.

To achieve this, proceed as follows:

1. Start Windows Explorer and navigate to the tftp folder

(default: C:\Program files\Fujitsu\ServerView Suite\D-eploymentService\tftp).

2. Right-click the tftp folder icon and select Properties.

3. In theProperties dialog box, select theSecurity tab.

4. In theSecurity tab, select theGuest account.

5. In thePermissions for Guest list, select theRead & Execute option.

6. Click onOK.



4 Remote deployment

4.2.6 Configuring router for multi segment deploymentIf deployment server and target server have to be in different segments, thefollowing settings and hints are advisable (i.e. deployment-server and targetserver resides in different LAN-segments or VLANs).

Bypass deployment communication inside router configuration on the fol-lowing protocols/ports:

l In direction from "deployment server" to "target server" (destination)

Destination Ports:

4973 UDP (Deployment Service's proprietary protocol)

4974 - 4989 UDP (Restore)

l In direction from "target server" to "deployment server" (destination)

Destination Ports:

67 UDP (PXE broadcast)

4011 UDP (PXE broadcast)

69 UDP (PXE/TFTP)

4972 UDP (Deployment Service's proprietary protocol)

4974 - 4989 UDP (Backup)

4974 - 4989 TCP (Backup)

l In both directions:

9213 UDP/TCP (InstallationManager installation protocol)

4971 (If "ServerView Deployment Manager" and "ServerView Deploy-ment Service" are located in different segments)

l "DHCP proxy" router functionmust be enabled


Caution:

Especially if you are using the "ARP proxy" router function, theassigned IP address provided at PXE boot for a target server instal-lation has to be constant over the whole deployment session. Thiscould be achieved by a long lease time (>2 hours) or reserved IP con-figuration in the DHCP server., provided the router settings aboveremote installation are supported in general for multi segment deploy-ment by ServerView InstallationManager / ServerView DeploymentManager:

l for all Linux (SuSE- or Red-Hat, x32 + x64) & Windows x32 plat-forms

l for multi segment remote installation of Win2K8 x64 (& R2) serversince SVIM V10.10.09

(Hotfix available for ServerView InstallationManager V10.10.05 -V10.10.08).



4 Remote deployment

4.3 Preparing the remote resource serverOptionally, youmay use a remote server for storing and sharing theresources that are required for the installation process.

In order to enable the target system to access the installation resources onthe remote resource server, proceed as follows:

1. Prepare the required installation resources: operating system instal-lation disks, optional disks (e.g. Service Pack CD-ROMs) etc.

2. Log in to the remote resource server using a user account with admin-istrator rights.

3. Create a folder (e.g. C:\SHARE_Install_Data) where you will providethe required installation resources.

You can either provide all resources in the same folder or dis-tribute the individual resources to separate folders.

4. Share the folder(s) on the network.

5. Grant theRead permission on the shared folder(s) to a user account onthe target server.

6. Copy the prepared installation resources to the shared folder(s).

7. Verify that the user account on the target server can read the installationresources from the folders via network access.


4.4 Preparing the target system for the remote instal-lationFor a remote installation of the target system, the InstallationManager clientinstance that was booted on the target system via PXE contacts the deploy-ment server. The target systemmust boot from a LAN card to enable thePXE boot.

Setting the boot sequence for booting from the network card

Only onboard LAN devices or specially prepared (flashed) Intel LANmezzanine cards support the network boot (PXE boot).

Use one of the following two procedures to define the boot sequence on thetarget system:

l Access the target system BIOS and set the boot sequence to theBoot from a network device setting.

For more information, refer to the BIOS Setupmanual on yourServerView Suite DVD.

l When you are configuring the installation process in theSelect the Tar-get System configuration step (see section "Select the target system(Remote Installation and Remote System Configuration Only)" on page107), you can specify that PXE boot mode is to be activated auto-matically as part of the installation process if the target system has aremotemanagement component (BMC/iRMC/iRMC S2/S3/-S4/management blade).


4.4 Preparing the target system for the remote installation

4 Remote deployment

Starting the PXE boot of the target systemUse one of the following two procedures to start the PXE boot of the targetsystem:

l Start the target system "manually" after you have defined the bootsequence accordingly.

l If the target system has a remotemanagement component(BMC/iRMC/iRMC S2/S3/S4/management blade):

Use the automatic option provided by InstallationManager after it hasbeen configured accordingly (see above).

4.5 Starting Installation Manager on the deploymentserverYou can start InstallationManager locally or remotely on the deploymentserver. In both cases, you require a web browser, which, in the case of alocal start, is called automatically with the correct web address.


4.5.1 Starting Installation Manager locally under WindowsFollow the steps below:

1. Select Start – Programs – Fujitsu ServerView Suite – InstallationMan-ager - start InstallationManager.

You are then prompted to enter a user name and password. The defaultuser account to access the user interface is:

User: Administrator

Password: admin

For details on how tomodify the user account settings refer to the"ServerView Suite: User Management in ServerView" manual.

Figure 32: Installation Manager logon

2. Enter your user name and password and click onOK to confirm.

The InstallationManager welcome screen is displayed.


4.5 Starting InstallationManager on the deployment server

4 Remote deployment

4.5.2 Starting Installation Manager remotely via web browserFollow the steps below:

1. Start a supported web browser (Internet Explorer or Firefox).

2. Enter the following address:

http://<IP address of the deployment server>:3169-/ServerStart/ImStartBase.html

You are then prompted to enter a user name and password. The defaultuser account to access the user interface is:

User: Administrator

Password: admin

For details on how tomodify the user account settings refer to the"ServerView Suite: User Management in ServerView" manual.

Figure 33: Installation Manager logon

3. Enter your user name and password and click onOK to confirm.

The InstallationManager welcome screen is displayed.


4.5.3 Installation Manager Welcome ScreenThe InstallationManager welcome screen is structured as follows:

Figure 34: Installation Manager welcome screen

You can select which InstallationManagement function you want to use inthis welcome screen:

InstallationThe Installation Manager link starts the Installation Manager.

This function allows you to install a computer.

MonitoringThe Installation Monitor link starts theRemote Installation Monitor.

This function allows you tomonitor current installations.



4 Remote deployment

LoggingThe Logging link opens the Logging Level dialog.

This function allows you to set the logging level used for themain log file

Logging LevelHere you can select the logging level for themain log file.

OKActivates the selected logging level and closes the dialog.

SSL for secure communicationEnables the SSL protocol for communication between InstallationMan-ager and the deployment server. (Address: https://<IP>...).

SSLmust be configured on the deployment server for this purpose.

You can select this option when starting InstallationManager eitherlocally or remotely.

4.5.4 Graphical user interface (GUI) of the Installation ManagerThe following initial screen of the InstallationManager GUI is displayed afteryou click on the InstallationManager link in the InstallationManager wel-


come screen:

Figure 35: Installation Manager GUI - initial screen



4 Remote deployment

The InstallationManager GUI comprises the following areas:

l Menu bar

l Display area

Menu barYou can execute the following functions from themenu bar:

HomeTakes you back to the initial window of the InstallationManager GUI.

DeploymentStarts the remote deployment

ConfigurationConfigures BIOS, hardware, and RAID configuration of the target systemwithout installing an operating system.

MaintenanceOption of booting any required boot images using the PXE infrastructureof InstallationManager.


HelpStarts the online help.


Display areaThe display area displays the dialog step associated with the currently select-ed function.

In the case of the initial page of the InstallationManager GUI, the displayarea comprises the following elements:

l The InstallationManager version is displayed at the top of the screen.

l The system data of the PRIMERGY server is displayed underServerInformation.

l TheDeployment, Configuration, Maintenance and Informationlinks allow you to start the same functions that can be started from thecorresponding function buttons in themenu bar (see "Menu bar" above).



4 Remote deployment

4.6 Starting remote deployment / remote system con-figurationProceed as follows:

l To start the remote deployment, click on theDeployment button orclick onDeployment in themenu bar on the start page of the Instal-lationManager GUI. The window for defining the target system is dis-played.

l To start the remote system configuration, click on theConfigurationbutton or click onConfiguration in themenu bar on the start page ofthe InstallationManager GUI. The window for defining the target sys-tem is displayed.

The only mode available for remote deployment is Customized. Thescreen for selecting a deployment mode is therefore skipped in thiscase.

The dialog boxes shown in this chapter are identical to those thatappear when you select Customized as your deployment mode. Formore information about Customizedmode, see section "Typical orCustomized deployment" on page 20.


4.6.1 Select the target system (Remote Installation and RemoteSystem Configuration Only)In this dialog box, you configure the settings required for a remote installationof the target system.

Figure 36: Target system definition

Saved ConfigurationsHere you can select the data for a target system that is already defined.


4.6 Starting remote deployment / remote system configuration

4 Remote deployment

Target system

The data of the target system selected underSaved Configurations is dis-played here. If you have not selected a target system underSaved Con-figurations or if you want to install a system that is not yet listed, this iswhere you define the system for which the following configuration session isto apply.

MAC addressMAC address of the LAN port (network card) on the target system that isto be used for the installation.

The requiredMAC address format is "nn-nn-nn-nn-nn-nn". How-ever, InstallationManager also accepts the formats"nnnnnnnnnnnn" and "nn:nn:nn:nn:nn:nn", which will be con-verted automatically.

PRIMERGY System TypePRIMERGY type of the target system

DescriptionThis input field is automatically filled with the values from theMACaddress andPRIMERGY System Type fields. You can change thisdefault value if required.

Access to the Installation Manager data packages available on thedeployment server

Authorizes access to the deployment server for the InstallationManagerclient instance on the target system.

User AccountUser account with access rights to the deployment server. This useraccount was set up during installation of InstallationManager on thedeployment server.

Password/Re-enter the passwordPassword for this user account.


Remote Management Interface of the target system

If the target system has a remotemanagement interface (BMC, iRMC, iRMCS2/S3/S4 or management blade), you can specify here that PXE mode is tobe activated automatically on the target system as part of the deploymentprocess (either with or without a subsequent restart of the target system).

Select Remote Management Controller

The remotemanagement interfacemust be specified if the tar-get system’s hardware configuration data shall be retrievedautomatically for usage in the configuration wizards.

Type

Indicates the type of remotemanagement interface:

Management Bladefor PRIMERGY blade servers.

Remote Management Controllerfor PRIMERGY servers with BMC, iRMC or iRMC S2/S3/S4.

MMB Remote Managerfor blade servers BX600 (withMMBS3) and BX900. Themanagementblade of the blade server is accessed via telnet. Read-write access viaSNMP is not necessary.

combinedfor Management Blades and RemoteManagement Controllers

Wake on LANfor target systems with aWoL-enabled network card (NIC), which ispowered by the standby power supply of the target system even if thetarget system is switched off.

No Remote Control interfacefor target systems that do not have amanagement interface. In thiscase, the input fields described below are not displayed.



4 Remote deployment

Broadcast to Bootstrap ServerIf you select this option, themagic packet is sent to UDP port 67 (Boot-strap Protocol (BOOTP) Server); otherwise, it is sent to UDP port 9. Thisoption is required if you specify the Unicast address of a BOOTP/DHCPserver under Broadcast Address. Furthermore, you should select thisoption if it is not guaranteed that all gateways included in a subnet broadcast are configured for "subnet broadcasting".

Broadcast AddressIP address of the target system, i.e, the broadcast address or unicastaddress of the target system to which the deployment server is to sendthemagic packet.

IP addressIP address of the BMC, iRMC, iRMC S2/S3/S4 or management blade.

IPMI User (for RemoteManagement Controller only)Local user account on the BMC, iRMC or iRMC S2/S3/S4.

IPMI Password (for RemoteManagement Controller only)Password for the local user account on the BMC, iRMC or iRMCS2/S3/S4.

SMASH User (for MMB RemoteManager only)Local user account on theMMB RemoteManager.

SMASH Password (for MMB RemoteManager only)Password for the local user account on theMMB RemoteManager.


SNMP Community (for Management Blade only)SNMP user group with the corresponding rights on themanagementblade.

CommandSelect the required action:

DisabledNo change to the PXE settings on the target system and no systemrestart.

Set boot mode to PXE (no restart)Automatically enables PXE boot mode without a restart of the targetsystem.

Restart system and boot via PXEAutomatically enables PXE boot mode with a restart of the target sys-tem.

The restart of the target system will be executed as soon as you startthe deployment process at the end of the InstallationManager session.

l Click onNext.

Depending on whetherDeployment orConfiguration has been startedvia the InstallationManager initial screen, the following window is dis-played:

l Deployment: Iinitial window for configuring an automatic installationprocessor (see "Configure Your UnattendedOperating SystemInstallation" on page 112)

l Configure: Initial window for configuring the server's BIOS and hard-ware is displayed (see "Enter Parameters for the Server's BIOS andHardware Configuration" on page 118.



4 Remote deployment

4.6.2 Configure Your Unattended Operating System InstallationIn this dialog box, you specify which operating system is to be installed onyour target system.

Figure 37: Initial window: Configure your Unattended Operating System Instal-lation

Configuration file

Here you specify whether you want to create a new configuration file or usethe values from an existing one.



Start an installation based upon an existing configuration fileHere you can select a configuration file. The interpreted contents of thisfile are then displayed on the right of the window underContents of Con-figuration File.

Click the folder icon to select an existing configuration file. A dialog boxopens that allows you to select an appropriate configuration file from theconfigfiles directory of the InstallationManager repository (remote instal-lation) or from a local backupmedium (local installation, customizedmode).

InstallationManager provides the configuration file’s content in the currentsession as default values for the configuration. You can use these valuesas required and save them in the same configuration file or a new con-figuration file at the end of the session.

Contents of Configuration FileIf you selected an existing configuration file, an extract of its content is dis-played here.

Select the operating systemHere you specify which operating system you want to install in which var-iant and which version on the target system.

Only operating systems that are released for the selectedPRIMERGY type of the target system are displayed for selec-tion.

InstallationManager supports the installation of the following operating sys-tems:

You will find the latest information on supported server systems andsupported operating systems for Japan as part of the restrictions of theServerView Suite on the Internet.



http://primeserver.fujitsu.com/primergy/products/note/svsdvd/

4 Remote deployment

Microsoft Windows

l Windows Server 2012: Standard Edition, Datacenter Edition, WindowsServer Foundation, Windows Storage Server Standard

l Windows Server 2008 (32-bit versions): Standard Edition, EnterpriseEdition, Web Server Edition, Small Business Premium Add-on Server

l Windows Server 2008 (64-bit versions): Standard Edition, EnterpriseEdition, Datacenter Edition, Web Server Edition, Windows Server Foun-dation, Small Business Server Standard, Small Busines x64 PremiumEdition Add-on Server, EBS Management Server, EBS MessagingServer, EBS Security Server, EBS Database Server).

l Windows Server 2008 R2: Standard Edition, Enterprise Edition, Data-center Edition, Web Server Edition, Windows Server Foundation)

Linux (SuSE and Red Hat Enterprise Linux)

l SuSE Linux Enterprise Server 10 Edition i386 and x86_64 (includingService Pack 4)

l SuSE Linux Enterprise Server 11 Edition i386 and x86_64 (includingService Pack 1 and Service Pack 2)

l RedHat Enterprise Linux 5.

l RedHat Enterprise Linux 6.

Hypervisor

l VMware ESX 4.x

l VMware ESXi 5.x

l Microsoft Hyper-V Server and Hyper-V Server 2008 R2

If you select Hypervisor - Microsoft Hyper-V - MicrosoftHyper-V Server or Microsoft Hyper-V Server 2008 R2,InstallationManager will install Hyper-V as the core variant.


Server Management ConfigurationHere you specify whether the server management system settings needto be changed or whether this step can be skipped.

Selected OS shall boot fromHere you specify the partition on the target system the selected operatingsystem shall boot from:

l Booting in "native" UEFI Boot mode from theGUID Partition Table(GPT) partition

l Booting in "legacy" UEFI Boot mode from theMaster Boot Record(MBR) partition

Which options are enabled for selection depends on both thePRIMERGY type of the target system and the operating sys-tem to be installed on it.

Identify the Hardware Configuration of the Remote SystemHere you can specify how InstallationManager shall receive the hardwareconfiguration data of the target system.

Do not use system dataYou have to configure target system data offline on the deployment serverby using the InstallationManager wizards

Use system data saved in the repository (<date/time>)The target system's hardware data is taken from the system data storedin the repository (<date/time>) on the deployment server.



4 Remote deployment

Please note:

l This option is only enabled for selection if system data isavailable on the deployment server.

l Check whether the current hardware configuration of thetarget system is identical as it was at <date/time>.

l If the current hardware configuration of the target systemis different from as it was at <date/time>, use the Instal-lationManager wizards to perform the required adap-tations or retrieve the current hardware configuration byselecting Retrieve system data from the target sys-tem.

Retrieve system data from the target system (The remote system willbe restarted)

The PXE infrastructure is used to get the hardware configuration dataonline from the InstallationManager Agent running on the target system .

This option is only enabled for selection if a remoteman-agement interface on the target system has been configured intheSelect the Target System dialog box.

Start now…Restarts the target system for detection of the target system's hard-ware configuration details. The complete hardware detection proc-ess may take someminutes.

After you have clickedStart now...the procedure continues as fol-lows:

1. InstallationManager opens a confirmation dialog box allow-ing you to confirm (OK) or cancel (Cancel) starting the hard-ware detection on the target system.


2. After you have confirmed withOK, InstallationManagerblocks the InstallationManager GUI and opens theRetrievesystem data from the target system dialog box.

3. This dialog box permanently informs you on the step cur-rently being performed by the InstallationManager Agent.During the entire hardware detection process you have theoption to cancel its execution.

4. Once hardware detection on the target system has suc-cessfully completed, the InstallationManager Agent trans-fers the system data file to the deployment server and theRetrieve system data from the target system dialog boxinforms you on successful completion.

5. By clickingOk you can close theRetrieve system datafrom the target system dialog box and unlock the Instal-lationManager GUI.

6. The InstallationManager wizards now use the target systemdata. E.g., the options offered for selection in the Server Con-figurationManager and in the wizard for configuringmassstorage devices depend on the detected data.

Installation Manager wizardsThe following wizards guide you through the configuration:

l Wizards for target system configuration

o Server ConfigurationManager


This wizard helps you to configure the general system behavior ofthe target system and of the target system BMC/iRMC/iRMCS2/S3/S4 where applicable. The Server Configuration wizard isdescribed in section "Server ConfigurationManager" on page 131.



4 Remote deployment

o Wizard for configuringmass storage devices (RAID system/harddisks)

You use this wizard to configure hard disks and RAID controllers inthe target system. The Raid / Disk wizard is described in section"Configuringmass storage devices" on page 132.

l Wizards for configuring installation-specific settings

o <operating system> (e.g. Windows Server 2008)

for configuring the specific settings of the operating system you areinstalling.

o Application wizard

for configuring applications that you want to subsequently install onthe operating system.

These wizards are described in the following chapters:o Windows systems:

see chapter "ConfiguringWindows and starting the installation" onpage 149,

o Linux and VMware ESX/ESXi systems:see chapter "Configuring Linux and VMware ESX/ESXi and startingthe installation" on page 199.

Installation Info (Summary)This configuration step provides a summary and overview of all instal-lation settings you have configured. You can now save your configurationto a file and/or start an unattended installation.

4.6.3 Enter Parameters for the Server's BIOS and HardwareConfigurationIn this dialog box, you enter the parameters for configuring the BIOS andRAID controllers of the target system.


Figure 38: Enter Parameters for the Server's BIOS and Hardware Configuration

Configuration file

Here you specify whether you want to create a new configuration file or usethe values from an existing one.


Start an installation based upon an existing configuration fileHere you can select a configuration file. The interpreted contents ofthis file are then displayed on the right of the window underContentsof Configuration File.

Click the folder icon to select an existing configuration file. A dialogbox opens that allows you to select an appropriate configuration filefrom the configfiles directory of the InstallationManager repository



4 Remote deployment

(remote installation) or from a local backupmedium (local installation,customizedmode).

InstallationManager provides the configuration file’s content in the cur-rent session as default values for the configuration. You can use thesevalues as required and save them in the same configuration file or anew configuration file at the end of the session.

You can only use configuration files designed for sytem con-figuration. Configuration files created for operating systeminstallation cannot be used in this context.

Contents of Configuration FileIf you selected an existing configuration file, an extract of its content is dis-played here.

Action after ConfigurationHere you specify whether the server shall be rebooted or shut down afterconfiguration is completed.

RebootReboots the server after configuration is completed.

ShutdownShuts down the server after configuration is completed.

Server Management ConfigurationHere you specify whether the server management system settings needto be changed or whether this step can be skipped.


Server Boot SettingsHere you specify the partition the target system shall boot from:

GPT Partition (-> UEFI Native Boot Mode)Target system boots in "native" UEFI Boot mode from theGUID Par-tition Table (GPT) partition .

MBR Partition (-> Legacy" UEFI Boot)Target system boots in "legacy" UEFI Boot mode from theMasterBoot Record (MBR) partition .

Depends on the system settingsThe partition the target system boots from depends on both the PRIM-ERGY type of the target system and the operating system installed onit.

Which options are enabled for selection depends on both thePRIMERGY type of the target system and the operating sys-tem installed on it.

Identify the Hardware Configuration of the Remote SystemHere you can specify how InstallationManager shall receive the hardwareconfiguration data of the target system.

Do not use system dataYou have to configure target system data offline on the deployment serverby using the InstallationManager wizards

Use system data saved in the repository (<date/time>)The target system's hardware data is taken from the system data storedin the repository (<date/time>) on the deployment server.



4 Remote deployment

Please note:

l This option is only enabled for selection if system data isavailable on the deployment server.

l Check whether the current hardware configuration of thetarget system is identical as it was at <date/time>.

l If the current hardware configuration of the target systemis different from as it was at <date/time>, use the Instal-lationManager wizards to perform the required adap-tations or retrieve the current hardware configuration byselectingRetrieve system data from the targetsystem.

Retrieve system data from the target system (The remote system willbe restarted)

The PXE infrastructure is used to get the hardware configuration dataonline from the InstallationManager Agent running on the target system .

This option is only enabled for selection if a remoteman-agement interface on the target system has been configured intheSelect the Target System dialog box.

Start now…Restarts the target system for detection of the target system's hard-ware configuration details. The complete hardware detection proc-ess may take someminutes.

After you have clickedStart now...the procedure continues as fol-lows:

1. InstallationManager opens a confirmation dialog box allow-ing you to confirm (OK) or cancel (Cancel) starting the hard-ware detection on the target system.

2. After you have confirmed withOK, InstallationManagerblocks the InstallationManager GUI and opens theRetrievesystem data from the target system dialog box.


3. This dialog box permanently informs you on the step cur-rently being performed by the InstallationManager Agent.During the entire hardware detection process you have theoption to cancel its execution.

4. Once hardware detection on the target system has suc-cessfully completed, the InstallationManager Agent trans-fers the system data file to the deployment server and theRetrieve system data from the target system dialog boxinforms you on successful completion.

5. By clickingOk you can close theRetrieve system datafrom the target system dialog box and unlock the Instal-lationManager GUI.

6. The InstallationManager wizards now use the target systemdata. E.g., the options offered for selection in the Server Con-figurationManager and in the wizard for configuringmassstorage devices depend on the detected data.

Installation Manager wizardsThe following wizards guide you through the hardware configuration:

l Server ConfigurationManager


This wizard helps you to configure the general system behavior of thetarget system and of the target system BMC/iRMC/iRMC S2/S3/S4where applicable. The Server Configuration wizard is described in sec-tion "Server ConfigurationManager" on page 131.

l Wizard for configuring RAID controllers

You use this wizard to configure RAID controllers in the target system.The Raid / Disk wizard is described in section "Configuring RAID con-trollers" on page 137.



4 Remote deployment

Configuration Info (Summary)This configuration step, provides a summary and overview of all systemsettings you have configured. You can now save your configuration to afile and/or enable your settings.

Figure 39: Backing up the configuration / starting the sytem configuration

Save configuration to fileDefines a name for the configuration file (default name: ser-startbatch.xml), in which the configured parameters are saved.




l You can select or create a folder in which InstallationManager willstore the configuration file. The folder is stored within the configfilesdirectory of the InstallationManager repository.



The remote system configuration is not started.

Start ConfigurationStarts remote system configuration and backs up the configured param-eters in the file you have specified in theSave the Configuration to File... dialog.

For details of how to launch a PXE-based remote installation, referto section "Launching the PXE-based remote installation / systemconfiguration" on page 126).

After the PXE-based installation is launched, the target system is rebooted.Then the hardware of the target system is configured.

During the remote system configuration the target systemmayreboot several times.



4 Remote deployment

4.6.4 Launching the PXE-based remote installation / systemconfigurationAfter you have verified your installation / system configuration settings in theInstallation Info/ Configuration Info dialog box (see "Backing up the con-figuration / starting the installation" on page 195 (Windows), "Backing up theconfiguration / starting the installation" on page 249 (Linux), or "Enter Param-eters for the Server's BIOS and Hardware Configuration" on page 118in thecase of a remote system configuration), you can save your configuration andlaunch the PXE-based remote installation.

From the user’s point of view, PXE-based remote installation comprises thefollowing steps:

1. In the Installation Info / configuration Infodialog box, click onStartinstallation / Start configuration.

2. Only

l if the target system does not have a remotemanagement interface(BMC, iRMC, iRMC S2/S3/S4 or management blade) :

or

l if you have not specified the settings for the remotemanagementinterface of your target system (see "Select the target system(Remote Installation and Remote System Configuration Only)" onpage 107):

Start the target system by local operation.


CAUTION!

If your target system is a blade server:

To avoid system boot failure due to not fully initializedMMBand switch blades:

After powering on the blade chassis, wait a few minutes beforeyou initiate a remote PXE boot via MMB. A valuable check isthe visibility of listedMAC adresses inMMBWebUI view ofyour assigned target blade.

For detailed information, refer to the user guide for your serverblade.



4 Remote deployment

3. The PXE-based system boot and therefore the installation / system con-figuration starts automatically.

Only in case of an installation: At the same time, the ServerView Instal-lationMonitor is started automatically on the deployment server. ItsRemote Installation Monitorwindow informs you about the progressand state of remote installation processes which have been started.

CAUTION!

Do not start any action on the target server before installation /system configuration is completed!

The target system is then configured. In case of an operating systeminstallation, after one or more possibly necessary restarts, the targetsystem continues with installing the operating system.

The systemmay reboot several times until installation / sys-tem configuration is completed. ???


4.7 Multiple installation (multi-deployment) of PRIM-ERGY serversThe InstallationManager allows you to remotely install up to five server sys-tems simultaneously.

To do this, follow the steps below:

1. Start deployment for a target system.

As soon as contact is established with the target system that is to beinstalled after the installation process has started, the InstallationMon-itor starts automatically. This provides information about how the instal-lation is progressing (see chapter "InstallationMonitor - Monitoringremote installation" on page 251).

2. Start deployment and installation for another target system.

You can use the same configuration file you used for the target systemyou have already started to install for the deployment of this second tar-get system, or you can use a different configuration file.

The hardware configuration of the two systems must be iden-tical if you want to use the same configuration file. InstallationManager uses themass memory subsystem to check whetherthis is the case.

Other hardware parameters, such as RAM, processor type,graphics and LAN controller (if using dynamic IP address allo-cation via DHCP server) do not affect the success of the instal-lation. These components are dynamically detected during theinstallation process and therefore do not need to be identical. ARemoteManagement Controller (BMC/iRMC/iRMC S2/S3/S4)specified in the configuration file does not necessarily have tobe present in the target system, provided that this RemoteMan-agement Controller is not used to trigger the automatic PXEboot of the target system.


4.7Multiple installation (multi-deployment) of PRIMERGY servers

4 Remote deployment

The new remote installation is displayed in the InstallationMonitor. Youcan click on the entries for the active installations to switch betweeninstallations and check on how each is progressing. The relevant infor-mation continues to be available after installation is completed (seechapter "InstallationMonitor - Monitoring remote installation" on page251).

3. Continue to repeat the previous step until a maximum of five installationprocesses are listed underActive Clients.

To install more than five servers simultaneously, you requireServerView Deployment Manager, which you will find underDeployment Software on ServerView Suite DVD. You requirea license for this module of ServerView Suite. It comes with ademo license.

You can obtain full licenses for using Deployment Managerfrom the Fujitsu Technology Solutions customer service teamby quoting order number U15000-C300.


5 Configuring the target systemBesides the configuration options for specific operating systems, the Instal-lationManager in customized installationmode offers many options for con-figuring

l Server-specific system settings on the target system:

the Server ConfigurationManager.

l Hard disks and RAID controllers.

Configuring Server-specific system settings on the target system viathe Server ConfigurationManager and configuring RAID controllers isnot possible in the context of aWindows Server 2008 (R2) expressinstallation.

5.1 Server Configuration ManagerThe Server ConfigurationManager enables you to configure the following set-tings for the target system:

l General system behavior

l BMC, iRMC or iRMC S2/S3/S4 if they are present on the target system

In order to configure general system behavior, the Server ConfigurationMan-ager runs through a sequence of steps with the following functionality:

l Select server type of the target system.

l Configure boot watchdog.

l Configure software watchdog.

l Configure scheduled times for powering the server on and off.

l Configure behavior after power failure and when restarting.

l Configure automatic fan test.

l Configure uninterruptible power supply (UPS) devices.


5.1 Server ConfigurationManager

5 Configuring the target system

Depending on the PRIMERGY server type of the target system, not allsteps may be performed. The sequence of the individual steps and theconfiguration options for the individual steps may also vary from sys-tem to system.

For details on the individual server configuration dialog steps, pleaserefer to the online help of the Server ConfigurationManager.

To access the online help related to a dialog step, proceed as follows:

1. Click in the window area currently displaying this dialog step.

2. Press the F1 key.

5.2 Configuring mass storage devicesThemass storage device configuration is used to configure the hard disksand RAID controllers. To permit direct installation of operating systems oniSCSI targets, you can also select, partition and format target LUNs.

CAUTION!

The InstallationManager will delete all existing partitions on all disksfor which new partitions have been defined.

The hardware configurations of two servers are differentiated solelywith reference to the hard disk subsystem. If you intend to use a con-figuration file for installing a number of target systems, the hard disksubsystems of the target systems in questionmust satisfy the con-figured requirements.

Installing Windows Server and Linux operating systems on iSCSI tar-gets

The InstallationManager also enables you to install Windows Server andLinux operating systems directly on iSCSI targets which are connected toyour PRIMERGY server via an iSCSI adapter using TCP/IP.


A prerequisite here is that the iSCSI adapter and iSCSI target are con-figured appropriately before the InstallationManager session starts.

The InstallationManager supports the iSCSI Host Bus Adapter (iSCSI HBA)adapter type for direct installation of Windows Server operating systems oniSCSI targets.

Configuring mass storage devices for installing Windows Server oper-ating systems

Figure 40: RAID / Disk wizard (Windows Server 2008) in Customized mode


5.2 Configuringmass storage devices


The configuration for a remote installation is shown. In the case of localinstallation on the target system or remote installation using PXE-based online detection of the target system's hardware configuration,the buttons for adding a controller / logical disk are omitted. Instead,only the controllers / logical disks that are actually present in the sys-tem are shown.

In the case of local installation on an iSCSI target or remote installationusing PXE-based online detection of the iSCSI target system's hard-ware configuration, buttons for iSCSI LUNs (logical drives on iSCSI tar-gets) are only displayed if the iSCSI LUNs actually exist and are vis-ible through suitable configuration of the iSCSI adapter and iSCSItarget.

Use these buttons tomake the following configurations:

RAID ControllerEnables a RAID controller to be configured for the RAID array.

SAS DiskEnables SAS hard disks which exist in the target system to be partitionedand formatted.

SATA DiskEnables SATA hard disks which exist in the target system to be par-titioned and formatted.

iSCSI HBA DiskEnables partitioning specifications to be entered for an iSCSI HBA harddisk which exists in the target system.

An iSCSI HBA Disk is an external iSCSI hard disk which is connected toyour PRIMERGY server via an iSCSI HBA (Host Bus Adapter) usingTCP/IP. The iSCSI HBA is a hardware interface which implements the ini-tiator (iSCSI client) on the PRIMERGY server.

Fibre Channel DiskEnables external FC (Fibre Channel) hard disks to be partitioned and for-matted.


Configuring mass storage devices for installing Linux and VMwareoperating systems

Figure 41: RAID / Disk wizard in Customized mode

The configuration for an offline remote installation is shown. In thecase of local installation on the target system or remote installationusing PXE-based online detection of the target system's hardware con-figuration, the buttons for adding a controller / logical disk are omitted.Instead, only the controllers / logical disks that are actually present inthe system are shown.

Use these buttons tomake the following configurations:

RAID ControllerEnables a new RAID controller to be configured for the RAID array.

SAS Disk




Enables SAS hard disks which exist in the target system to be partitionedand formatted.

SATA DiskEnables SATA hard disks which exist in the target system to be par-titioned and formatted.

Fibre Channel DiskEnables external FC (Fibre Channel) hard disks to be partitioned and for-matted.


5.2.1 Configuring RAID controllers

RAID ControllerDisplays the options available for the RAID configuration.

Figure 42: Configure RAID system

Controller VendorList showing the vendors of the supported RAID controllers.

Controller FamilyList showing the RAID controllers of the selected vendor.

Controller TypeList showing the controller variants of the selected family.




Controller NumberSets the controller number. The number refers to the entries specified inthe three preceding fields.

If, for example, a vendor is specifiedmore precisely (value not equal toAutomatic), but the value Automatic is selected forController FamilyandController Type, theController Number refers to this vendor’s con-trollers. If Controller Family is also specifiedmore precisely, ControllerNumber refers to the controllers of this vendor’s specified controllerfamily, etc.

Use existing Logical DisksDisables the subsequent options and uses the existing RAID array on thetarget system. If you do not select this option, the existing RAID array willbe deleted and you can configure a new RAID array with the followingoptions.

Configure RAIDSpecifies how the RAID array is to be configured.

AutomaticallyConfigures the RAID array across all existing disks. In this case, theRAID level is determined by the number of hard disks and the func-tionality of the controller:

l One disk: RAID7(JBOD)

l Two disks: RAID1

l Three disks: RAID5 (if the controller is capable of managing level 5.)

l More than three disks: RAID5 with hot spare (if the controller isequipped for this)

Type of RAID controllerl Type A: The controller is capable of managing RAID 5.

l Type B: The controller is capable of managing RAID 1E.

l Type C: The controller is capable of managing only RAID 1.


Detailed information on the number of supported hard disks andRAID levels depending on the RAID controller type.

Type A

# of HDD RAID Level

1 RAID 0

2 RAID 1

3 RAID 5

4 or more RAID 5 + Hot spare

Type B

# of HDD RAID Level

1 RAID 0

2 RAID 1

3 RAID 1 (one disk is not used)

4 or more (even) RAID 1E

5 ormore (odd) RAID 1E(If the RAID controller does not support oddnumbers of disks, the number of disks perarray is decreased by one automatically.)

Type C

# of HDD RAID Level

1 Cannot constitute.

2 RAID 1

3 or more Cannot constitute.




ManuallyUsing theManually option, you can configure the settings yourself:

RAID Level

In the case of local installation on the target system or remoteinstallation using PXE-based online detection of target systemdata:

The RAID level depends on the underlying controller’s capabil-ities and the number of connected hard disk drives. You only seethe RAID levels that can be configured.

Determines the level of data security:

RAID 0Striping (no redundancy). Data reconstruction is not possible. If ahard disk fails, the data on that hard disk is lost.

RAID 1Mirroring. If a hard disk fails and is replaced, its data is recon-structed automatically (rebuild).

If an additional hard disk is available as a standby disk (see theHotSpare option), it is automatically activated as a replacement for thedefective disk, and the data from the defective disk is recon-structed on this standby disk (rebuild).

RAID 5Distributed parity information. If a hard disk fails and is replaced, itsdata is reconstructed automatically (rebuild).

If an additional hard disk is available as a standby disk (see theHotSpare option), it is automatically activated as a replacement for thedefective disk, and the data from the defective disk is recon-structed on this standby disk (rebuild).

RAID 10


Comprises a combination of striping andmirroring. Faster thanRAID1, but redundant, unlike RAID 0.

RAID 50A combination of RAID 0 with a striped version of RAID 5. In thiscase, a RAID 0 array is created from at least two striped RAID 5arrays. To implement this, you therefore require at least six disks.

Number of DisksSpecifies the number of disks included in the RAID array. If all avail-able hard disks are to be used, enter "0".

Hot spareHere you specify whether you want to use an additional standby diskfor recovery in the event of disk failure if you are using RAID levels 1 or5. Then if a hard disk fails, the standby disk takes over the function ofthe defective hard disk. The data is still redundant.

Hot spare disks cannot be used with blade servers.

Blade servers contain amaximum of two disks, while at leastthree disks are required for the hot spare option. The Hotspareoption is therefore disabled when you are configuring bladeservers.

If you want to configure the system with a hot spare hard disk, selectYes.

Hard Disk WritecacheSpecifies whether the hard disk write cache - if available - shall beused.

ApplySaves the values that are currently set.

ResetRestores the values that were savedmost recently.




5.2.2 Configuring hard disksThe following step for configuring hard disks is structured identically forRAID controllers, SAS disks, SATA disks, iSCSI HBA Disks, and FibreChannel disks.

All existing partitions on a target hard disk are deleted.

Add diskCreates a new hard disk entry. An additional group is displayed for con-figuring a new hard disk.

Disk <n>Displays the options available for configuring the new hard disk.

Add partitionCreates a new partition in the configuration. An additional group isdisplayed for creating a new partition.

Remove diskDeletes the associated hard disk entry in the configuration.

Remove partitionDeletes the entry in the configuration for the partition shown besideit.

Partition <n>Partition already configured. You can edit the configuration parameters ofthe partition.

Delete controllerDeletes the controller from the configuration.


5.2.3 Configuring partitions

CAUTION!

When you configure new partitions for a hard disk, InstallationManagerdeletes all existing partitions on the disk.

The steps for configuring partitions for Linux / VMware ESX/ESXi sys-tems are different from the steps forWindows systems.

5.2.3.1 Configuring partitions (Windows)

The steps for configuring partitions forRAID disks, SCSI disks, IDEdisks and Fibre Channel disks are structured identically.

Figure 43: Configuring hard disk partitions (Windows)

Partition <n>Displays the options available for configuring the partition.

LabelName of the partition.

File systemDefines the system type for the selected partition. The following types arepermitted: NTFS and FAT.




Partition SizeSpecifies the size of the partition in MB.

MaximumThe partition is created with the largest possible size.

TheMaximum option allows you to select only one partitionper hard disk.

Due to technical reasons, after installation, the last 5 GB oflogical disk space remain unallocated and unconfigured.However, his memory can be allocated without problems.

Size in MBInteger (e.g. 2048) indicating the size of the partition (in MB).

QuickFormatSpecifies whether the hard disk is to be formatted in quick format mode.

In quick format mode, the hard disk is not checked for corruptsectors during formatting. You should therefore only use quickformat mode if the hard disk has already been formatted prop-erly and it has been found to be undamaged.

If you do not select the quick mode formatting takes severalhours.

Partition UsageDefines the purpose for which the partition is to be used.

BitlockerNeeded to use the “BitLocker Drive Encryption” feature.

BootBoot partition with OS loader.

OSPartition for theWindows system files.


DataPartition for data that is not system-specific.

ApplySaves the new or changed configuration.

ResetRestores the last saved values of the options for the partition currentlybeing edited.

5.2.3.2 Configuring partitions (Linux / VMware ESX/ESXi)

The steps for configuring partitions for RAID disks, SCSI disks, IDEdisks and Fibre Channel disks are structured identically.

Figure 44: Configuring hard disk partitions (Linux)

Partition <n>Displays the options available for configuring the partition.

Mount Point




Determines the directory in the target system's directory structure towhich the partition is to be added (mounted). The partition's directory struc-ture is added to this directory.

StandardSelects themount point: /boot, /var, /tmp, /usr, /opt

CustomDefines a directory of your choice as themount point.

Specify the directory using the following notation:

/<directoryname> (e. g. /mydirectory)

Filesystem TypeDefines the system type for the selected partition. The following types arepermitted: ext2, ext3, swap (only available for swap partitions) and vfat(only available for VMware ESX 4.1).

Size (MB)Integer (e.g. 2048) indicating themaximum size of the partition (in MB).

Use the recommended value for this partitionIf you select a default mount point for the partition and then select thisoption, the optimal size specifications for the selectedmount point areautomatically applied to the partition.

In this case, Additional size options are disabled.

Additional Size OptionsEnables the size specification to bemademore precise.

Fixed SizeCreates a partition with the size specified inSize.

Fill all space up to (MB)The partition will be expanded to the value specified here.

Fill to maximum available sizeThe partition is created with the largest possible size.


This option can only be selected for one partition per hard disk.

Force to be a primary partition (as primary)Creates the partition as a primary partition of the hard disk.

Up to four primary partitions are possible on each hard disk.

Create a lv group with the nameNot SuSE SLES 10 and VMware.

Creates an LV group (LV = Logical Volume) with the specified name. LVgroups are based on the LVM (LVM = Logical VolumeManager) whichimplements an abstraction level between hard disks and file systems.

You can not createmore than one LV group on the target sys-tem.

LV groups are based on the LVM which implements an abstraction levelbetween hard disks and file systems.

You can assign an LV group to several virtual partitions (logical volumes).File systems that are created on a logical volume of this type can lateroccupy several physical partitions in the installed system.




TheRAID / Diskwizard displays an LV group as follows:

Figure 45: RAID / Disk wizard - LV groups and logical volumes

When configuring a logical volume (virtual partition), you can assign aname of your choice to the logical volume.

Name of the Logical VolumeName of the logical volume.

ApplySaves the new or changed configuration.

ResetRestores the last saved values of the options for the partition currentlybeing edited.


6 Configuring Windows and startingthe installationWhen you configure the unattended installation of aWindows operating sys-tem, the InstallationManager's wizard guides you through each configurationstep. Or, you can activate the individual configuration steps directly and thusdetermine the sequence of the steps yourself.

The configuration steps are described here in the order they are pre-sented in the wizard.

6.1 User interfaceThe structure of the wizard's user interface is uniform:

l In the left area, click on the appropriate link in the tree structure to selecta configuration step directly.

l The parameters of the current configuration step will be displayed in theright area.


6.1 User interface

6 ConfiguringWindows and starting the installation

Figure 46: User interface for configuring the unattended installation

NextClick onNext to go to the next configuration step.

BackClick onBack to return to the previous configuration step.

CancelClick onCancel to stop configuring in the current wizard.

All changes will be discarded.


6.2 Installing Windows (typical)In detail, configuring a typical Windows installation includes the followingsteps:

l Configure hard disks/RAID controllers using the RAID / Disk wizard.

l Configure installation of theWindows operating system.

l Save installation parameters and/or start installation.

You cannot install Windows Server 2008 Server Core in typical mode.

If you use a USB stick as status backupmedia forWindows Server2008 / 2012 installation remove it in the Boot menu of the BIOS setting.

If you use a floppy disk or a USB stick as status backupmedia forWin-dows Server 2008 (64-bit) / Windows Server 2012 installation, changethe boot order in BIOS: set the hard disk above the floppy disk andUSB stick.

Prerequisitesl Youmust have started InstallationManager on the target system, see

"Starting InstallationManager on the target system" on page 37.

l Youmust have started the local deployment, see "Starting local deploy-ment" on page 48.

l Youmust have selected Typical installationmode in the InstallationManager Deployment Processwindow.

l Youmust have selected the operating system, operating system var-iant, and the service pack in the initial window of the unattendedinstallation configuration, see "Starting local deployment" on page48.

l Youmust havemade additional settings before clicking onNext.


6.2 InstallingWindows (typical)


6.2.1 Configuring disks and RAID controllers (typical)In this dialog box, you configure the disks and corresponding controllers onthe target system during a local installation via DVD. In this case InstallationManager checks the configuration of the computer and only offers optionsthat are compatible with the existing controller and disk.

Figure 47: Installing Windows (typical): Configuring disks and RAID controllers

RAID ControllerDisplays the RAID controller(s) that have been detected in the system.Logical Disk 0

Uses the existing RAID array and does not change the configuration ofthe RAID controller selected. In this case you only determine the size ofthe boot partition.


Boot Partition SizeSpecifies the size of the boot partition.

MinimumSpecifies 25000MB as minimum size of the boot partition.

All DiskSpecifies the whole disk for the boot partition.

Due to technical reasons, after installation, the last 5 GBof logical disk space remain unallocated and uncon-figured. However, his memory can be allocated withoutproblems.

ManuallyUses the specified size for the boot partition.

Create new RAID Array with one boot partition

Configures a new RAID array on the RAID controller selected. Everyexisting RAID configuration of this controller will be cleared.

RAID LevelDetermines the level of data security.

The RAID level depends on the underlying controller'scapabilities and the number of connected hard diskdrives. You only see the RAID levels that can be con-figured.

automaticConfigures the RAID array across all existing disks. The number ofdisks determines the RAID level if the controller supports this level:

l One disk: JBOD

l Two disks: RAID 1

l Three disks: RAID 5




l More than three disks: RAID 5 with recovery in the event ofdisk failure


RAID 0Striping (no redundancy): Data reconstruction is not possible. If ahard disk fails, the data on that hard disk is lost.

RAID 1Mirroring: If a hard disk fails and is replaced, its data is recon-structed automatically (rebuild). If an additional hard disk is avail-able as a standby disk (see the "Hotspare" option), it is auto-matically activated as a replacement for the defective disk, and thedata from the defective disk is reconstructed on this standby disk(rebuild).

RAID 5Distributed parity information: If a hard disk fails and is replaced, itsdata is reconstructed automatically (rebuild). If an additional harddisk is available as a standby disk, it is automatically activated as areplacement for the defective disk. The data from the defective diskis reconstructed on this standby disk (rebuild).

RAID 6Similar to RAID 5, but considerably faster.

RAID 10Comprises a combination of striping andmirroring. Faster thanRAID 1, but includes redundancy, unlike RAID 0.

Boot Partition SizeSpecifies the size of the boot partition.

MinimumSpecifies 25 000MB as minimum size of the boot partition.

All DiskSpecifies the whole disk for the boot partition.




Due to technical reasons, after installation, the last 5 GBof logical disk space remain unallocated and uncon-figured. However, his memory can be allocated withoutproblems.

ManuallyUses the specified size for the boot partition.

6.2.2 Configuring Windows installationIn this step you configure the settings of theWindows operating system thatis to be installed.

Figure 48: Installing Windows (typical): Configuring Windows settings

User Name


Name of the default target system user. This name should be identical tothe name of the owner of theWindows license.

This entry does not specify an user account.

OrganizationName of the default user's company or organization

Computer NameName of the computer in the workgroup or domain.

In the course of the installation process, lower case letters inComputer Namewill automatically be changed to upper caseletters.

Product-ID (optional)License number of theWindows version

In the case of a typical local installation:

Do not enter a product key if you use Fujitsu OEM operatingsystem installationmedia.

In the case of a user-definedWindows installation:

If you selected "Fujitsu OEMmedia" in the precedingSelectthe Installation Image dialog box, this input field is disabled.

If you use a DSP version of Windows, the license number isstored on the CD and is added to the configuration file duringinstallation. In otherWindows variants, the license numbermust be entered the first time the operating system is started fol-lowing the installation.

Admin Password / please repeatPassword for the administrator account on the server, whichmust beentered twice for security reasons.

The following requirements must bemet:

l A valid passwordmust consist of at least 6 characters.




l A valid passwordmust meet 3 of the following criteria:

o at least 1 uppercase letter (A-Z, English)o at least 1 lowercase letter (a-z, English)o at least 1 base 10 digit (0-9)o at least 1 non-alphabetic character (e.g. '!', '$', '#', '%', ...)


Time ZoneThe time zone in which you work. The time zone is entered as a key in theconfiguration file. If you install a JapaneseOS using the Operating Sys-tem - Recovery DVD forWindows Server 2008 R2 select Japanese.

Regional and Language Options for the Operating System (Formats,language and keyboard)

Sets the language for the windows installation.

Internet Protocol Version 6 ParametersHere you configure the Internet Protocol version 6 parameters (IPv6).

ModeSets themode.

DHCPThe IPv6 settings will be received from aDHCP server on the net-work.

Do not activate the DHCP mode if there is no DHCP available onyour network.




AutoconfigurationThe target system opens an internet connection via the IPv6 auto-configuration process. The target system communicates with therelevant routers in order to investigate the communication param-eters.

ManualInstallationManager explicitly requests the IPv6 parameters.

The IPv6 parameters described in the following will onlybe displayed, if theManualmode has been chosen.

IP AddressIPv6 address.

Subnet Prefix LengthLength of the Subnet Prefix. The Subnet Prefix is composed ofthe Global Routing Prefix and the Subnet ID.

Internet Protocol Version 4 ParametersHere you configure the Internet Protocol version 4 parameters (IPv4).

DHCPIf you enable DHCP, the IPv4 settings will be received from aDHCPserver on the network.

yesDHCP will be enabled.

noDHCP will not be enabled.

Do not activate DHCP if there is no DHCP available onyour network. Otherwise, the server will not boot because itcannot obtain an IP address.


The IPv4 parameters described below will only be shown ifno has been selected for DHCP.

IP AddressIPv4 address.

Subnet maskSubnet mask. The subnet mask uses the IP address to assign aspecific subnet to the IP address.

GatewayIP address of the default gateway computer or default router.

SNMP Settings for the ServerView Management StationHere you configure the SNMP service of the target system in order tosetup the SNMP communication between the ServerView Central Man-agement Station(s) and the target server.

IP Address for Trap DestinationThis list shows the IP addresses of the computers to which SNMPmessages are to be sent.

SNMP CommunityName of the community group that is permitted to send SNMP queriesto the target system. This name is a component of every SNMP mes-sage that the agent sends to theManagement Platform. This setting iscase-sensitive.

SNMP uses community groups to control authorizations for read andwrite access by SNMP Manager to themonitored objects (MIBobjects). A community name is included in every SNMP message, andidentifies the sender of themessage as amember of a given com-munity. SNMP Manager and agents can only communicate if theybelong to the same community.




PrivilegesDefines the privileges assigned to the community name: None, notify,read only, read and write, read and create. ReadOnly is the default set-ting. To use settings like SVR in ServerView Operations Manager, setthis option to read write.

6.2.3 Backing up the configuration / starting the installationThis step shows the parameters that have been configured. You can back upthese parameters to a file and/or start the unattended installation on the basisof the configuration shown.

Figure 49: Backing up configuration / Starting installation

SaveSaves the configured parameters in the temporary fileSerStartBatch.xml.The unattended installation is not started.


If you have provided an external backupmedium (e.g. USB memorystick), the configuration file is saved on that medium.

Start InstallationStarts the unattended installation of the operating system.

If you have selected a local drive as the source device, InstallationMan-ager will ask you to insert the requiredmedium (CD/DVD). In this case,insert themedium and click onOK.


l Do not remove themedium. Otherwise, the automaticinstallation process may be stopped (e.g. while installingWindows Server 2008, x64 Edition)

l If you use InstallationManager version < 10.09.10 forinstallation of Windows Server 2008, x64 Edition, a dialogbox Select save location for the configuration filewillbe displayed after the reboot of the target system.

In this case proceed as follows:

1. Select the local drive option and choose the externalbackupmedium.

2. Click onNext to continue with the installation.

After the installation is started, the system reboots. Then, before the oper-ating system installation starts, the hardware of the system is configured.

After the installation is started, the hardware of the system is configuredand the system reboots.

During the unattended installation the target systemmay rebootseveral times.




6.3 Installing Windows (customized)In detail, configuring a customizedWindows installation includes the fol-lowing steps:

l Configure general system behavior and remotemanagement controllerusing the Server ConfigurationManager (optional).


l Configure installation of theWindows operating system.

l Configure the installation of applications.

If you use a floppy disk or a USB stick as status backupmedia insert it into aserver before switch on. Then select Rescan inStartUpwindow.

If you use a USB stick as status backupmedia forWindows Server2008 / 2012 installation remove it in the Boot menu of the BIOS setting.

If you use a floppy disk or a USB stick as status backupmedia forWin-dows Server 2008 (64-bit) / Windows Server 2012 installation, changethe boot order in BIOS: set the hard disk above the floppy disk andUSB stick.

Prerequisitesl Youmust have started InstallationManager locally on the target system

or on a deployment server andmade the following specifications:o In the case of local installation youmust have selectedCus-

tomized installationmode in the Installation Manager Deploy-ment Processwindow, see "Starting InstallationManager on thetarget system" on page 37.

o In the case of remote installation in theSelect the Target Systemconfiguration step, youmust have specified the required infor-mation for the target system (MAC address of the LAN adapterthat is to be used for communicating with the deployment server,PRIMERGY system type, etc.), see "Select the target system


(Remote Installation and Remote System Configuration Only)" onpage 107.

l Youmust have selected the operating system, operating system var-iant, and the service pack in the initial window of the unattendedinstallation configuration.

l Youmust havemade additional settings before clickingNext.


6.3 InstallingWindows (customized)


6.3.1 Server Configuration Manager

The configuration steps for the Server ConfigurationManager are onlyoffered if you have selected theEdit Server Management Settingsoption in the initial window for configuring the installation process.

The Server ConfigurationManager offers a number of configuration steps,with which you configure additional settings for the target system besidesconfiguring the installation process.

Figure 50: Installing Windows (customized): Server Configuration Manager

For a description of the ConfigurationManager, refer to section "Server Con-figurationManager" on page 131.


6.3.2 Configuring Disks and RAID controllersYou can use the RAID / Disk wizard to assist you in configuring hard disksand RAID controllers.

Figure 51: Installing Windows (customized): Configuring disks and RAID con-trollers

For instructions on configuring hard disks and RAID controllers, refer to sec-tion "Configuringmass storage devices" on page 132.




6.3.3 Configuring Windows Server 2008 / Windows Server 2012

6.3.3.1 Select the Installation Image

In this dialog box, you select the installation variant and additional detailsbased on this variant.

Figure 52: Installing Windows (customized): Specifying the installation medium

Type of the Installation Source Medium

Defines the provider of the installationmedium.

Fujitsu OEMCD/DVD with Fujitsu OEM version of Windows Server 2008 / 2012

MicrosoftOriginal Microsoft Windows Server 2008 / 2012 installation CD/DVD


Customized ImageA customized installation DVD or ISO image with Microsoft WindowsServer 2008 / 2012. If you select this option, youmay only install the fullversion of Windows Server 2008 / 2012.

Type of InstallationInstallation variant of Windows Server 2008 / 2012

Note: If you change one of the following parameters, you will need to gothrough all the subsequent dialog boxes in the wizard again.

CoreInstalls Server Core. Server Core allows you to execute the specificserver roles of Windows Server 2008 / 2012 on a system where the graph-ical user interface has been reduced to aminimum.

FullInstalls the full Windows Server 2008 / 2012 operating system.

Setup LanguageLanguage for theWindows installation. You cannot select a language fortheMicrosoft or customized installation media.

If the selected language is Default or not available on the installationmedia, then the default language of the installationmedia will be used. Ifyou install a JapaneseOS using the Operating System - Recovery DVDforWindows Server 2008 R2 select Japanese.

ArchitectureArchitecture of the target system CPU (Intel x86 or AMD64) that youselected underSelect the operating system in theConfigure YourUnattended Operating System Installation dialog box. The architecturetype displayed here cannot be changed. It is an essential prerequisite forthe installation on the target system. The installationmediummust sup-port this architecture type.




Index of the ImageIndex of the image on the installationmedium. The default setting of "0"can only be changed for the customized installation medium.

6.3.3.2 Basic SettingsConfigure default user of the target system

In this dialog box, you specify the default user on the target system.

Figure 53: Installing Windows (customized): Configuring basic parameters

User nameName of the default target system user. This name should be identical tothe name of the owner of theWindows license.

The user name does not specify an user account.

OrganizationName of the default user's company or organization


Computer NameName of the computer in the workgroup or domain.

In the course of the installation process, lower case letters inComputer Namewill automatically be changed to upper caseletters.

Product-ID (optional)License number of theWindows version

In the case of a typical local installation: do not enter a productkey if you use Fujitsu OEM operating system installationmedia.

In the case of a user-defined installation:

If you selected "Fujitsu OEMmedia" in the preceding Selectthe Installation Image dialog box, this input field is disabled.

If you are using a DSP version of Windows, the license numberis stored on the CD and is added to the configuration file duringinstallation. In otherWindows variants, the license numbermust be entered the first time the operating system is started fol-lowing the installation.

Admin PasswordPassword for the administrator account on the server, whichmust beentered twice for security reasons.

The following requirements must bemet:

l A valid passwordmust consist of at least 6 characters.

l A valid passwordmust meet at least 3 of the following criteria:o at least 1 uppercase letter (A-Z, English)o at least 1 lowercase letter (a-z, English)o at least 1 base 10 digit (0-9)o at least 1 non-alphabetic character (e.g. '!', '$', '#', '%', ...)




Autologin CountDefines the number of times InstallationManager is to log on auto-matically after the installation.

Time ZoneThe time zone in which you work. The time zone is entered as a key in theconfiguration file. If you install JapaneseOS, select (GMT+09:00) Osaka,Sapporo, Tokyo.

Parameters for a typical, local installation

DHCPThe target system retrieves its IP address and additional configurationparameters from aDHCP server. If you select no, the parameters for thestatic IP configuration are displayed.

IP addressIP address of the selected adapter

subnet maskIPv4 only: Subnet mask for the selected adapter. The subnet maskassigns a specific subnet to the IP address.

GatewayIP address of a gateway computer or router.

SNMP Settings for the ServerView Management StationHere you specify themanagement stations to which you want the SNMPagent to send traps:

IP Address for Trap DestinationThis list shows the IP addresses of the computers to which SNMPmessages are to be sent.


CommunityName of the community group that is permitted to send SNMP queriesto the target system. This name is a component of every SNMP mes-sage that the agent sends to theManagement Platform. This setting iscase-sensitive.

SNMP uses community groups to control authorizations for read andwrite access by SNMP Manager to themonitored objects (MIBobjects). A community name is included in every SNMP message, andit identifies the sender of themessage as amember of a given com-munity. SNMP Manager and agents can only communicate if theybelong to the same community.

PrivilegesDefines the privileges assigned to the community name: None, notify,read only, read and write, read and create.

Parameters for user-defined local and remote installation

Regional and Language Options for the Operating SystemDefines the language of the operating system, the keyboard layout andcountry-specific settings for the target system.




6.3.3.3 System SettingsConfigure target system parameters and installation source

In this step, you provide network identification information about the targetsystem.

Figure 54: Installing Windows (customized): Configuring system parameters

Will participate inDefines the group to which the target system belongs.

WorkgroupYour system is included in a workgroup, which youmust also specify.


DomainYour system is included in a domain, which youmust also specify.

NameName of the workgroup or domain.

Domain UserUser account with authorization to add a computer to the domain. Thisentry is required if you want to add the system to a domain. Youmustalso specify the user account if an entry for a computer with this namealready exists in the domain.

Domain PasswordPassword for the user account.

DisplayHere you specify the settings used to display theWindows user interfacethe first time it is started.

ResolutionThe number of pixels per horizontal line, multiplied by the number of(pixel) lines on the screen. If the connected plug-and-play screen can-not display the configured resolution, theWindows display can bereset to standard VGA when it is started for the first time.

VRefreshVertical screen refresh rate.

BitsPerPixelNumber of bits per pixel.




Operating system installation sourceDefines the location of the installation packages for the operating system:

Local DVD drive (local installations only)Installs the operating system from the local DVD drive.

Network driveInstalls the operating system from the specified network drive.

Remote PathPath of the network drive in UNC notation in the form:\\<server>\<path>, e.g. \\myserver\share.

Remote UserUser account with the rights required to access the network drive.The account must exist on the computer that is referenced by theURL and which provides the resources. The newly created usermust have read privileges on the computer for the directory in thepath specified above.

Remote PasswordPassword for the user account.

6.3.3.4 Network Settings

In this dialog box, you specify the protocols that are used to allow the ports ofthe network cards to communicate.

l In the case of local installation on the target system, the InstallationManager displays the target system LAN adapters in this list. From thislist, youmust then select the LAN adapter that is to be activated on thetarget system.

l In a remote installation, the InstallationManager does not recognize thetarget system. In this case, youmust make the LAN adapters of the tar-get system known to the InstallationManager using the Add button.From this list, youmust then select the LAN adapter that is to be acti-vated on the target system.


Figure 55: Installing Windows (customized): Configuring Ethernet settings

AdapterInAdapter, the LAN adapters (network cards) present on the target systemare displayed, or LAN adapters must be configured for the target systemdepending on whether the InstallationManager recognizes the target system:

l In the case of local installation on the target system, the InstallationManager displays the target system LAN adapters in this list. From thislist, youmust then select the LAN adapter that is to be activated on thetarget system.

l In a remote installation, the InstallationManager does not recognize thetarget system. In this case, youmust make the LAN adapters of the tar-get system known to the InstallationManager using the Add button.From this list, youmust then select the LAN adapter that is to be acti-vated on the target system.




If you configuremore than one adapter, it is not possible to assign a log-ical adapter number directly to a physical slot number. This is onlydefined in the BIOS.

RemoveDeletes the selected adapter from the configuration.

AddIncludes a LAN adapter in the list.

Adapter DetailsHere, you configure the TCP/IP settings for a new LAN adapter. The con-figured TCP/IP settings are shown here for a selected adapter that has alrea-dy been configured inAdapters.

Internet Protocol Version 4 Parameters Here you configure the Internet Protocol version 4 parameters (IPv4) ofthe selected LAN adapter.

DHCPIf you enable DHCP, the LAN adapter receives its IPv4 settings from aDHCP server on the network.

YesDHCP will be enabled.

NoDHCP will not be enabled.

Do not activate DHCP if there is no DHCP available on your net-work. Otherwise, the server will not boot because it cannotobtain an IP address.

The IPv4 parameters described below for configuring the select-ed LAN adapter will only be shown if No has been selected forDHCP.


IP AddressIPv4 address for the LAN adapter.

Subnet maskSubnet mask for the LAN adapter. The subnet mask uses the IP addressto assign a subnet to the LAN adapter.

GatewayIP address of the default gateway/default router for the LAN.

Configure Additional IP AddressesHere you can configure additional IP addresses (including subnet masksand default gateways/default routers).

IP addressesTo configure an IPv4 address, click onAdd, enter the IPv4 addressand the subnet mask in the dialog that appears, and then click onOKto confirm.

To remove an IPv4 address that has already been configured from thelist, highlight the IPv4 address and then click onRemove.

GatewaysTo configure aGateway, click onAdd, enter the IPv4 address of theGateway in the dialog that appears, and then click onOK to confirm.

To remove aGateway that has already been configured from the list,highlight the Gateway and then click onRemove.

Configure DNS ServerConfigure the DNS server.

DNS Domain NameName of the default domain for queries to the DNS server or servers.

DNS ServerTo configure a DNS server, click onAdd, enter the IP address of thecorresponding DNS server in the dialog that appears, and then click onOK to confirm.




To remove a DNS server that has already been configured from thelist, highlight the server and then click onRemove.

Disable Dynamic UpdateNo dynamic updates. Dynamic updates are used to register anddynamically update the resource entries on DNS client computersafter any change on a DNS server.

Enable "Adapter Domain Name Registration"Domain registration for the adapter.

Configure WINS ServerConfigure aWINS server. It is generally quite sufficient to configure oneor at most twoWINS servers.

WINS-ServerTo configure aWINS server, click onAdd, enter the IP address of theWINS server in the dialog that appears, and then click onOK to con-firm.

To remove aWINS server that has already been configured from thelist, highlight the server and then click onRemove.

NetBIOS OptionActivates / disables NetBIOS over TCP/IP. NetBIOS over TCP/IP isonly required for the target system if the target system communicateswith older operating systems or if it uses NetBIOS functions.

You can choose from the following options:

l UseNetBIOS settings from the DHCP serverDefault if DHCP has been enabled. If the LAN card on the targetsystem uses DHCP, the DHCP options from the DHCPOffermessage received are adopted to disableNetBIOS over TCP/IPor to activate and configureNetBIOS over TCP/IP depending onthe configuration of the DHCP server.


l Enable NetBIOS over TCP/IPDefault if DHCP has not been enabled. NetBIOS over TCP/IP isactivated regardless of the DHCP options received.

l Disable NetBIOS over TCP/IPNetBIOS over TCP/IP is activated regardless of the DHCPoptions received.

Internet Protocol Version 6 Parameters Here you configure the Internet Protocol version 6 parameters (IPv6) ofthe selected LAN adapter.

ModeSets themode to configure the LAN adapter.

DHCPThe LAN adapter receives its IPv6 settings from aDHCP server onthe network.

Do not activate the DHCP mode if there is no DHCP available onyour network.

AutoconfigurationThe target system opens an internet connection via the IPv6 auto-configuration process. The target system communicates with therelevant routers in order to investigate the communication param-eters.

ManualInstallationManager explicitly requests the IPv6 parametersrequired for configuring the LAN adapter.

The IPv6 parameters described in the following for configuring theselected LAN adapter will only be displayed, if theManualmodehas been chosen.

IP AddressIPv6 address for the LAN adapter.




Length of Subnet PrefixLength of the Subnet Prefix. The Subnet Prefix is composed of theGlobal Routing Prefix and the Subnet ID.

Configure Additional IP AddressesHere you can configure additional IP addresses (including subnetmasks and default gateways/default routers).

IP addressesTo configure an IPv6 address, click onAdd, enter the IPv6 addressand the subnet mask in the dialog that appears, and then click onOK to confirm.

To remove an IPv6 address that has already been configured fromthe list, highlight the IPv6 address and then click onRemove.

Configure DNS ServerConfigure the DNS server.

DNS Domain NameName of the default domain for queries to the DNS server orservers.

DNS ServerTo configure a DNS server, click onAdd, enter the IP address ofthe corresponding DNS server in the dialog that appears, and thenclick onOK to confirm.

To remove a DNS server that has already been configured from thelist, highlight the server and then click onRemove.

TCP/IP Parameters GeneralThe security parameters for the TCP/IP configuration are shown here.

In these groups you can set the security options for the TCP/IP configurationof the target system (adapter enabled).


Domain nameName of the default domain for queries to the DNS server or servers.

DNS SuffixesThis list shows the defined suffixes in the sequence in which the DNSservers are searched.

RemoveDeletes the selected suffix from the list.

AddOpens theDNS Suffix dialog box, where you can add a new suffix tothe list. Suffixes indicate a domain and are added to computer names,for example, cswatcp.reskit.com.

Enable "Domain name devolution"TheMicrosoft DNS Caching Resolver uses Domain NameDevolution toresolve unqualified queries.

Enable "ICMP Redirect"Overwriting of OSPF (Open Shortest Path First)-generated routes withICMP (Internet Control Message Protocol) redirects is allowed.

Only enable this option if server routing or remote access services areto be installed on the target system.

6.3.3.5 Services

In this dialog box, you specify the services that you want InstallationMan-ager to pre-install with the operating system.

Services indicated by the button can be configured.




Figure 56: Installing Windows (customized): Selecting / Configuring services

SNMP ServiceInstalls the configurable SNMP service.

Trap Configuration ItemsHere you specify themanagement stations to which you want the SNMPagent to send traps:

Community NameName of the community that is permitted to send SNMP queries to thetarget system. This name is a component of every SNMP messagethat the agent sends to theManagement Platform. This setting iscase-sensitive.

SNMP uses communities to control authorizations for read and writeaccess by SNMP Manager to themonitored objects (MIB objects). Acommunity name is included in every SNMP message, and identifies


the sender of themessage as amember of a given community. SNMPManager and agents can only communicate if they belong to the samecommunity.

Trap DestinationsThis list shows the IP addresses of the computers to which SNMPmessages are to be sent. You can chooseAdd to specify newaddresses orRemove to delete addresses.

SecurityConfigures SNMP security for a community.

Accept Community NameThis list contains the community names from which the target systemwill accept messages. Youmust indicate the authorization for eachcommunity name: none, read, read_write.

Send Authentication TrapIf the agent on the target system rejects an SNMP request, it informsthe requestingManagement Platform via a trap.

SNMP requests from an unauthenticated community or computer arealways rejected by SNMP agents.

Accept SNMP packets from the default sourceSNMP packets are either accepted from localhost only (default) orfrom the host specified in theAccept Host Name field.

only read is the default setting. Change the right of the community toread and write because you cannnot change it using the ServerViewOperations Manager e.g., with ASR.

Accept Host NameThe IP address or host name of the computer whose SNMP packetsare to be accepted by the target system.




AgentInformation about the SNMP agent.

Contact Name(Optional) The person who is in a position to help in the event of a prob-lem (e.g. administrator).

Location(Optional) Physical location of the target system

ServicesSNMP services offered by the target system:

PhysicalThe target systemmanages physical devices (e.g. hard disks ordisk drives).

ApplicationsThe target system uses programs to send data via TCP/IP.

DataLink/SubnetThe target systemmanages a TCP/IP subnet or a data link (e.g. abridge).

InternetThe target system is used as an IP gateway (router).

End-to-EndThe target system is used as an IP host.


Routing and Remote Access ServiceDefines which routing strategies are supported by the target system (RRASserver):

Router TypeRouting strategies that the target system (RRAS Server) supports:

RAS is supportedThe target system supports RAS Routing.

LAN is supportedThe target system supports LAN routing exclusively.

RAS and LAN are supportedThe target system supports both RAS and LAN Routing.

WAN is supportedThe target system supports WAN Routing.

RAS and WAN are supportedThe target system supports both RAS andWAN Routing.

LAN and WAN are supportedThe target system supports both LAN andWAN Routing.

RAS, LAN and WAN are supportedThe target system supports RAS, LAN andWAN Routing.

6.3.3.6 Additional Parameters

In this dialog box, you configure the target system for remote support (remoteassistance). Remote support is based onWindows Remote Desktop Tech-nology and for example enables an expert to assist the administrator of theinstalled target system via a Remote Terminal Services Session.




Figure 57: Installing Windows (customized): Configuring remote support

Remote Desktop

enable Remote DesktopAllows access to the target system via the remote desktop program.

Remote Assistance

The following options allow you to define the qualitative scope and the dura-tion of the remote assistance.

This function is not available in the core variants of the operating sys-tem.

Enable remote assistanceEnables remote assistance for the target system.


Enable full remote controlRemote support is given complete control of the local monitor on the tar-get system. Otherwise, the local screen displays can only be passivelyobserved via remote assistance.

Ticket expires after ... daysValidity period of the settings for remote assistance.

6.3.4 Selecting / configuring applicationsIn this dialog box you can select programs which InstallationManager is toinstall in addition to the operating system.

InstallationManager copies drivers and software packages directly to theinstalled system. This way, even users using another installation tool will beable to perform a reference installation.

If you have not selected Japanese in the region and the languagedialog box, Japanese Software Packages are not provided.




Figure 58: Installing Windows (customized): Selecting / configuring applications

Select Applications

Displays the groups of programs that can be selected.

Some packages may be preselected, depending on the following crite-ria:

l operating system

l operating system language

l hardware type of the PRIMERGY server

l recommendation of FUJITSU LTD and Fujitsu Technology Solu-tions


The (n/n) pair of numbers following each group name indicates howmany programs (left number) are selected from the total number of pro-grams available in the group (right number).

Clicking on a "+" symbol displays the list of programs that are availablein the corresponding group.

Add-on Packages (n/n)Additional software (e.g. Java Runtime Environment, customspecificscripts and packages)

ServerView Suite (n/n)Components of the ServerView Suite

Software Packages for JAPAN (n/n)Software offered for the Japanesemarket.

This package is only available for Japanese-language operatingsystems.

Software Packages for PRIMEQUEST (n/n)Software available for PRIMEQUEST servers.

Some components of the package are only available for Japanese-language operating systems .

The dialog box is divided into two partsWhen you select an option or click on a program name, the dialog box is divid-ed into two parts:

l The programs available for selection continue to be displayed on theleft.

l On the right, you will see the information about the selected applicationas well as the parameters required for the installation.

Depending on theWindows Server operating system and depend-ing on the settings you configure using the configuration wizards,not all of the applications displayedmay be selectable.




If an application requires the installation of another applicationSome applications can only be installed if certain other applications areinstalled as well.

E.g. the installation of ServerView Suite - ServerView RAIDManagerrequires Add-on packages - Java Runtime Environment to be installed.

The Information area informs you about possible software depend-encies.

If you select an application requiring the installation of another applicationwhich is not already selected, the following dialog box opens:

Figure 59: The Application wizard tries to set the required parameters auto-matically

OKThe Application wizard attempts to select the required application.

If the Application wizard succeeds, your selection remains. Otherwise,your selection will be reset.

CancelResets your selection.


Details about the selected application are displayed on the right side

DescriptionA brief description of the selected option is displayed.

Settings for the selected application(not available for every application)Configures settings for the selected application.

Installation sourceDefines where InstallationManager can find the installation files.

Local installation:

ServerView Suite DVDData packages of the InstallationManager on the ServerView SuiteDVD.

Local removable mediaRemovablemedia on the target system.

Network shareApproved network drive.

Remote pathPath of the network drive in UNC notation in the form:

\\<Server>\<Path>, e.g. \\myserver\directory.

Remote user nameUser account with the necessary privileges for the network drive.The account must be present on the computer that the URL ref-erences and which provides the resources. The user must haveread privileges on the computer for the directory in the path spec-ified above.

Remote PasswordPassword for the user account




Remote installation:

ServerView Installation Manager data packagesData packages of the InstallationManager (on the deployment server)for remote installation.




Remote userUser account with the necessary privileges for the network drive.The account must be present on the computer that the URL ref-erences and which provides the resources. The user must haveread privileges on the computer for the directory in the path spec-ified above.


InformationProvides information about possible dependencies that are required for theinstallation of the selected program, e.g. certain services or applicationsmust be installed at the same time.


6.3.5 Backing up the configuration / starting the installationA summary of the parameters set is displayed. You can back up these param-eters to a file and/or start the unattended installation on the basis of the con-figuration shown.

Figure 60: Installing Windows (customized): Backing up the configuration / start-ing the installation







l You can select or create a folder in which InstallationManager willstore the configuration file. The folder is stored as follows:

o Local installation (customizedmode only):The folder is stored on the local backupmedium.

o Remote installation:The folder is stored within the configfiles directory of the Instal-lationManager repository.


For local installation on the target system:

The configuration can only be stored in customizedmode.




The unattended installation is not started.

Start InstallationStarts unattended installation of the operating system and backs up theconfigured parameters in the file you have specified in theSave the Con-figuration to File ... dialog.

For details of how to launch a PXE-based remote installation, referto section "Launching the PXE-based remote installation / systemconfiguration" on page 126).


If you have selected a local drive as the source device, InstallationMan-ager will ask you to insert the requiredmedium (CD/DVD). In this case,insert themedium and click onOK.


l Do not remove themedium. Otherwise, the automatic instal-lation process may be stopped (e.g. while installingWindowsServer 2008, x64 Edition).

l If you use InstallationManager version < 10.09.10 for instal-lation of Windows Server 2008, x64 Edition, a dialog boxSelect save location for the configuration filewill be dis-played after the reboot of the target system.

In this case proceed as follows:

1. Select the local drive option and choose the externalbackupmedium.

2. Click onNext to continue with the installation.

After the PXE-based installation is launched, the target system is rebooted.Then before the operating system installation starts, the hardware of the tar-get system is configured.

During the unattended installation the target systemmay rebootseveral times.

You can keep informed about the progress and status of a remote installationusing the InstallationMonitor (see chapter "InstallationMonitor - Monitoringremote installation" on page 251).




7 Configuring Linux and VMwareESX/ESXi and starting the installationWhen you configure the unattended installation of a Linux or VMWareESX/ESXi operating system, the InstallationManager's wizard guides youthrough each configuration step. Or, you can activate the individual con-figuation steps directly and thus determine the sequence of the steps your-self.

The configuration steps are described here in the order they are pre-sented in the wizard.

7.1 User interfaceThe structure of the wizard's user interface is uniform:

l In the left area, click on the appropriate link in the tree structure to selecta configuration step directly.

l The parameters of the current configuration step will be displayed in theright area.


7.1 User interface

7 Configuring Linux and VMware ESX/ESXi and starting the installation

Figure 61: User interface for configuring the unattended installation

NextClick onNext to go to the next configuration step.

BackClick onBack to return to the previous configuration step.

CancelClick onCancel to stop configuring in the current wizard.


7.2 Installing Linux / VMware ESX/ESXi (typical)In detail, configuring a typical Linux installation includes the following steps:


l Configure installation of the Linux operating system.


Prerequisites:

1. Youmust have started InstallationManager on the target systemand started the local deployment.

2. Youmust have selected "Typical" installationmode in the Instal-lation Manager Deployment Processwindow.

3. Youmust have selected the operating system, operating systemvariant, and the service pack in the initial window of the unat-tended installation configuration.

4. Youmust havemade additional settings before clicking onNext.


7.2 Installing Linux / VMware ESX/ESXi (typical)


7.2.1 Configuring Disks and RAID Controllers (typical)In this dialog box, you configure disks and RAID controllers.

Figure 62: Installing Linux / VMware (typical): Configuring disks and RAID con-trollers

RAID Controller

Displays the RAID controller(s) that have been detected in the system.Logical Disk 0

Uses the existing RAID array and does not change the configuration ofthe RAID controller selected. In this case you only determine the size ofthe boot partition.


Create new RAID Array with one boot partition

Configures a new RAID array on the selected RAID controller. Everyexisting RAID configuration of this controller will be cleared.

RAID Level

Determines the level of data security.

The RAID level depends on the underlying controller'scapabilities and the number of connected hard disk drives.You only see the RAID levels that can be configured.

automatic

Configures the RAID array across all existing disks. Theabilities of the RAID controller and the number of disksattached determine the RAID level if the controller supportsthis level:

l One disk: JBOD

l Two disks: RAID 1

l Three disks: RAID 5 (if the controller supports level 5)

l More than three disks: RAID 5 with recovery in theevent of disk failure

RAID 0

Striping (no redundancy): Data reconstruction is not pos-sible. If a hard disk fails, the data on that hard disk is lost.

RAID 1

Mirroring: If a hard disk fails and is replaced, its data is recon-structed automatically (rebuild). If an additional hard disk isavailable as a standby disk (see the "Hotspare" option), it isautomatically activated as a replacement for the defectivedisk, and the data from the defective disk is reconstructedon this standby disk (rebuild).




RAID 5

Distributed parity information: If a hard disk fails and isreplaced, its data is reconstructed automatically (rebuild). Ifan additional hard disk is available as a standby disk, it isautomatically activated as a replacement for the defectivedisk. The data from the defective disk is reconstructed onthis standby disk (rebuild).

RAID 6

Similar to RAID 5, but considerably faster.

RAID 10

Comprises a combination of striping andmirroring. Fasterthan RAID 1, but includes redundancy, unlike RAID 0.

Size Boot Partition

Specifies the size of the boot partition.

Minimum

Specifies 25 000MB as minimum size of the boot partition.

Whole Disk

Specifies the whole disk for the boot partition.

Manually

Uses the specified size for the boot partition.


7.2.2 Configuring Linux / VMware ESX/ESXi settings

Figure 63: Installing Linux/VMware (typical): Configuring operating system set-tings

Installation number (only for Red Hat Linux 5)Enter the installation number. The scope of function for the distribution willbe defined precisely on the basis of the installation number.

LanguageLanguage for the target system.

KeyboardKeyboard type of the target system.

Time ZoneTime zone of the operating system on the target system.




The system clock uses UTCSpecifies that the system clock on the target system is to use UniversalTime Coordinated (UTC). This option is set by default.

Additional languages (only for Red Hat Linux 4)Installs additional languages from the language group.

Root Password / Verify PasswordEnter and reenter the root password.

Encrypt root passwordWhen it is entered, the root password is encrypted and sent to the targetsystem in encrypted form.

Get computer name via DNSThe target system retrieves the computer name from aDNS server.

Do not choose this option unless a DNS server is available onthe target system's network.

Computer nameName of the target system.

Configure the network interface via DHCPThe target system retrieves its IP address and additional configurationparameters from aDHCP server.

Do not choose this option unless a DHCP server is available onthe target system's network.

If you deselect this option, you have to configure the parameters for thestatic IP configuration.

IP AddressIP address of the selected LAN adapter.


Net maskSubnet mask for the selected adapter. The subnet mask uses the IPaddress to assign a subnet to the LAN adapter.

GatewayIP address of the default gateway/default router for the target system'sLAN.

Name serverIP or name of the DNS server in the target system's LAN.

Installation OptionsSelects packages for the installation.

MinimalDefault for VMware ESX/ESXi.

Only the packages that are absolutely essential for the system to runare installed. Additional packages can be installed "manually" after-wards, when the system is running.

EverythingDefault for Red Hat Enterprise Linux 5.

All packages will be installed.

DefaultInstallation with focus on server.

WorkstationInstallation with focus on workstation.




7.2.3 Backing up the configuration / starting the installationThis step shows the parameters that have been configured. You can back upthese parameters to a file and/or start the unattended installation on the basisof the configuration shown.

Figure 64: Backing up configuration / Starting installation

SaveSaves the configured parameters in the temporary fileSerStartBatch.xml.The unattended installation is not started.

If you have provided an external backupmedium (e.g. USB memorystick), the configuration file is saved on that medium.

Start InstallationStarts the unattended installation of the operating system.


7.3 Installing Linux (customized)In detail, configuring a customized Linux installation includes the followingsteps:

l Specify the target system

l Configure general system behavior and remotemanagement controllerusing the Server ConfigurationManager (optional).


l Configure installation of the Linux operating system.


Prerequisites:

1. Youmust have started InstallationManager andmade the fol-lowing specifications:

l In the case of local installation:

Youmust have selectedCustomized installationmode in theInstallation Manager Deployment Process.

l In the case of remote installation:

In the configuration stepSelect the Target System, youmusthave configured the required information for the target system(MAC address of the LAN adapter that is to be used for com-municating with the deployment server, PRIMERGY systemtype, etc.)

2. Youmust have selected the operating system, operating systemvariant, and the service pack in the initial window of the unat-tended installation configuration.

3. Youmust havemade additional settings before clicking onNext.


7.3 Installing Linux (customized)


7.3.1 Server Configuration Manager

The configuration steps for the Server ConfigurationManager are onlyoffered if you have enabled theEdit Server Management Settingsoption in the initial window for configuring the installation process.

The Server ConfigurationManager offers a number of configuration steps,with which you configure additional settings for the target system besidesconfiguring the installation process ( see also section "Server ConfigurationManager" on page 131).

7.3.2 Configuring disks and RAID controllersIn this step, you can configure hard disks and RAID controllers.


Figure 65: Configuring disks and RAID controllers

For instructions on configuring hard disks and RAID controllers, refer to sec-tion "Configuringmass storage devices" on page 132.

7.3.3 Configuring Linux / VMware ESX/ESXiVarious configuration steps are offered for configuring the operating system.The sequence of the configuration steps offered varies according to the oper-ating system selected.

The following description follows the sequence of configuration steps for RedHat Enterprise Linux 5.

l Basic Configuration

l Package Selection

l XWindows

l VMware ESX only: Virtual disk configuration

l VMware ESX/ESXi only: License options

l Grub Bootloader Options

l Network Configuration

l Security and Firewall

l Authentication

l Pre Installation Script

l Post Installation Script




7.3.3.1 Basic Configuration

In this dialog box, you define the basic parameters for installation on the tar-get system.

Figure 66: Installing Linux / VMware (customized): Basic configuration

Localization

Adapts the target system to suit regional requirements.

LanguageOperating system language on the target system

KeyboardKeyboard language


Time ZoneTime zone of the operating system on the target system.

System clock uses UTCSpecifies that the system clock is to use Coordinated Universal Time(UTC).

Mouse (SuSE only)Configures themouse type.

Emulate 3-key Mouse (SuSE only)Emulates amouse with three buttons. Select this option if a two-buttonmouse is to be used on the target system. If you click with both the leftand right mouse button (on a two-buttonmouse) at the same time, the sys-tem will then interpret this as a click on the third button of a three-buttonmouse.

Password

Defines the password for the root ID.

Root Password / Verify PasswordPassword for root ID, which youmust enter twice for security reasons.

Encrypt Root PasswordEncrypts the root password as soon as it is entered. In other words, it isnot buffered in a readable format.




Installation settings

Sets additional parameters for the installation.

Medium


Determines the location where InstallationManager can find the instal-lation files:

CD-ROM

Local CD-ROM drive.

NFS

Network drive, which you define using the following parameters:

l Server: DNS name or IP address of the server that is toserve as an installation source (for example, a deploymentserver).

l Directory: Full path name of the directory containing theinstallation files.

FTP/HTTP

URL of the FTP or HTTP server.

Hard drive

Local disk, which you define using the following parameters:

l Partition: The partition containing the directory with theinstallation files.

l Directory: Full path name of the directory containing theinstallation files.

UNC (VMware ESXi only)

Network path in UNC (Uniform Naming Convention) notationallowing you to address resources that are located on another com-puter in the network:

l Path: Path of the network drive in UNC notation in the form:\\<Server>\<Path>, e.g. \\myserver\directory.

l Remote User name: User account with the necessary priv-ileges for the network drive. The account must be present onthe computer that the UNC path references and which pro-vides the resources. The user must have read privileges onthe computer for the directory in the path specified above.

l Remote Password: Password for the user account.ServerView InstallationManager 215




Reboot system after installation

Reboots the system after the installation. Kickstart normallydisplays amessage and waits for a key to be pressed beforerestarting the target system.

Text mode (graphical is default)

Installs the target system in text mode rather than the defaultgraphics mode.

Interactive mode

Installs the operating system in interactivemode, whichmeans that you can change settings in the Kickstart file dur-ing the installation.




7.3.3.2 Package selection

In this dialog box, you specify which packages you want to install on the tar-get system.

Figure 67: Installing Linux (customized): Selecting a package

Installation Number (Red Hat EL 5 only)

Defines the functional scope of the distribution via the installation number.


Kernel (not Red Hat EL 5 )

Installs the standard (native) kernel.

Native KernelInstalls the package for the native kernel.

Native Kernel with PAE (in case of x86)Installs the package for the native kernel with PAE.

Kernel with XEN (package virtualization)Installs the package for the kernel with XEN for virtualization. This pack-age is required to reboot the XEN kernel (see Boot Loader).

Initialize package selection

You can use the relevant buttons to pre select packages for installation. Thecorresponding number of active packages is displayed during package selec-tion.

Minimal systemSelects all installation packages required for theminimal operating sys-tem.

Install everythingSelects all installation packages.

Default package groupsPackage groups recommended by Fujitsu Technology Solutions.

Select packages

Provides a logically grouped display of all installation packages. The pack-ages you pre selected using the buttons provided are displayed as active.You canmodify this pre selection to suit your requirements, i.e. add orremove packages as required.

For Red Hat EL5:Only changeable, if you entered a valid Installation Number.




Single packages selection

List of additional installation packages.

New packageEnter the name of the installation package that you want to add to the listby clicking onAdd.

RemoveDeletes the selected installation package from the list.

Remove allDeletes all installation packages from the list.

7.3.3.3 Configuring the X Windows System (for Red Hat and SuSE only)

In this dialog box, you configure the X Windows System.

Figure 68: Installing Linux (customized): Configuring the X Windows System


Configure the X Windows System

Enables the configuration of the X Windows System. If you do not select thisoption, all subsequent options are disabled.

The X Windows System installation packagemust be selected (for Red HatEL 4).General

Display options.

Color DepthColor depth for the X Windows System. The color depthmust be com-patible with the graphics card and themonitor.

ResolutionResolution for the X Windows System on the target system. The res-olutionmust be compatible with the graphics card and themonitor.

Default DesktopDefines the default desktop. The required parameters must be selected:

l GNOME

l KDE

l None

Start the X Windows System on bootSpecifies that the target system is to use a graphical logon screen.




Video Card

Determines the video card type.

Probe for video driverDetermines the video card type automatically. The installation programsearches the PCI bus for the card in this case. The search sequence isdefined by the PCI scan sequence of themotherboard.

If you select this option, the following two options are disabled.

Select a Video DriverUses the specified card. The card namemust be contained in the card listin /usr/share/hwdata/Cards in the hwdata package.

Video Card RAMDefines thememory on the video card.

Monitor

Determines themonitor type.

Probe for MonitorDetermines themonitor type automatically. If you select this option, allsubsequent options are disabled.

Select a MonitorUses the specifiedmonitor. Themonitor namemust be contained in themonitor list in /usr/share/hwdata/MonitorsDB in the hwdata pack-age. This option is ignored if you select theSpecify hsync and vsyncinstead of a monitor option.

Specify hsync and vsync instead of monitorEnables the options for horizontal and vertical refresh rates.

Horizontal Sync (kHz)Specifies the horizontal refresh rate for themonitor.

Vertical Sync (Hz)Specifies the vertical refresh rate for themonitor.


7.3.3.4 VMware virtual disk configuration (VMware ESX only)

In this step you configure a virtual disk for VMware ESX 4.x.

Figure 69: VMware ESX 4.x installation (customized): Configuring a virtual disk

The VMware Service Consolemust be installed on a VMFS data store,which is located on the host’s local hard disk or on an appropriate maskedSAN hard disk residing in the zone, which is assigned to this host.

The data store cannot be used simultaneously by more than one host.

Name of virtual discName of virtual disk.




Name of containing VMFS partitionName of the VMFS date store, on which the VMDK file will be created.

SizeSize of the virtual disk (megabytes).

Overwrite existing VMFSOverwrites VMFS partitions on the specified drives. If the hard disk onlycontains a single VMFS partition, youmust select this option.

7.3.3.5 VMware License Options (VMware ESX/ESXi only)

In this dialog box, you specify the type of licensing that applies in this case.

Figure 70: VMware ESX/ESXi installation (customized): Configuring VMwarelicense options


End User License Agreement

The license agreement is displayed here.

Accept End User LicenseConfirms the license agreement.

License ModeDefines the license type.

Use license serverThe licenses for multiple users aremanaged using a license server.

Manual input of licenseThe individual license for the target system, which you enter in theinput field.

Manual after installationThe individual license for the target system, which you enter after theinstallation.




7.3.3.6 Grub bootloader options / mount options

In this dialog box, you can configure the installation of GRUB for themul-tiboot capability of your target system.

In the case of SUSE Linux Enterprise Server (SLES 10, SLES 11), you canadditionally specify Mount Options.

Figure 71: Installing Linux / VMware (customized): Configuring bootloaderoptions


Bootloader OptionsConfigures the installation of GRUB for themultiboot capability of your targetsystem.

Install bootloaderSpecifies that Boot Manager is to be installed. If you deselect this option,all associated options are disabled.

Install bootloader onSpecifies where Boot Manager is to be installed:

MBRInstalls Boot Manager in theMBR. This is the default setting.

First sector of boot partitionInstalls Boot Manager in the first sector of the partition, which con-tains the kernel.

Kernel parametersAdditional parameters for the kernel command line.

Boot XEN kernel as default (Not Red Hat EL 4 and VMware)Restarts the XEN kernel. In this case the XEN hypervisor is installed sothat the target system provides a XEN-based virtualization environment.

To use this option you have to select the XEN kernel from the installationpackages.

Set GRUB passwordSpecifies that a password is required for GRUB Boot Manager. If you donot select this option, all subsequent options are disabled.

Password / Verify PasswordPassword for Boot Manager, which youmust enter twice for securityreasons.




Encrypt passwordEncrypts the password as soon as it is entered. In other words, it is notbuffered in a readable format.

Mount OptionsSpecifies whether the hard disk is to bemounted "by id" or "by device".(For SLES 10 and SLES 11 only)

CAUTION!If a USB device is connected to the target system:As thedevice order may be changed during installation, themount by id(udev-id) option is required in order to ensure successful instal-lation of the operating system.

If you want to use ServerView Deployment Manager for deployingthe operation system youmust select themount by deviceoption. In this case, a USB devicemust not be connected to the tar-get system.

mount by id (udev-id)The hard disk is mounted "by device id".Mounting devices by device ID has the advantage that device names arepersistent.

The udev program is used by the Linux kernel for administrating thedevice files whichmanage the file input/output. As of Linux kernel version2.6, udev replaces the formerly used devfs system.

mount by device (e.g. /dev/sda)The hard disk is mounted "by device name".


7.3.3.7 Network configuration

In this dialog box, you configure the target system's network connection.

Figure 72: Installing Linux / VMware (customized): Network configuration

Configure standard network for VMs (VMware only)Configures a standard network for VMware using a VM port group. Defaultsetting

Use VLAN ID (VMware only)Integer between 0 and 4095 as net ID of the VLAN.

Get computer name via DNSRetrieves the computer name from the DNS server during the installation.If you do not select this option, enter the name of the target systemdirectly.




Computer nameName of the target system if you have not selected theRequest hostname from DNS option.

Configure all network interfaces via DHCPRetrieves the IP configuration for all network connections from the DHCPserver. This is the default setting for Red Hat and SuSE SLES 10. If youselect this option, all subsequent parameters must also be set.

Specify Interfaces by MAC AddressSpecifies the PXE boot device by using theMAC Address

Network interfacePort on the LAN card of the target system for which theNetwork typeis valid.

Network typeDefines the IP configuration for the network connection.

DHCPRetrieves the configuration parameters from the DHCP server.

Fixed IPConfigures a static IP address with the following parameters:

IP AddressIP address of the target system

Net maskSubnet mask

GatewayDefault gateway

Name serverDNS server for name resolution


OffNo network is configured for the port selected at Networkinterface.

7.3.3.8 Security and Firewall (for Red Hat and SuSE only)

In this dialog box, you configure firewall protection as an additional securitymeasure for your system. The firewall exists between the target system andthe network and determines which target system resources are accessible tonetwork users.

Figure 73: Installing Linux (customized): Configuring the firewall




Security Enhanced Linux

SELinux (Red Hat only)Defines Security-Enhanced Linux mode. SEL serves as a supplement tothe kernel that allows you to define stricter access controls for accessingcertain resources.

ActiveEnables SELinux and therefore enforces compliance with all securityguidelines, such as the denial of access to certain files and programsby unauthorized users.

WarnProvides notification when access is denied. The warning statusassigns names to data and programs and logs these in the/var/log/auditd file, but does not enforce compliance with secu-rity guidelines.

DeactivatedSELinux is disabled.

Firewall Configuration

FirewallSwitches the firewall on or off. If you enable the firewall, your target sys-tem only accepts connections that you have explicitly defined (with theexception of the default settings).

CustomizeDefines the rules governing the operation of the firewall.

Standard firewall rulesThis setting only permits connections that respond to outgoingrequests, such as DNS responses and DHCP requests.


CustomizeConfigures the adapters of the LAN card so that they can receiveaccesses via defined communication ports. Additional options are dis-played for this purpose.

Trusted devicesList of the adapters that are to bemonitored by the firewall.

New trusted deviceAn adapter, which you can create by choosingAdd Device. SelectRemove Device to delete an adapter from the list.

Allow incomingDetermines the protocol, and therefore the communication port,that will be admitted by the firewall.

FTPFTP protocol if the target system is to be a public FTP server.The vsftpd packagemust be installed.

Mail (SMTP)SMTP protocol if the target system is to be a public mail server.

TelnetTelnet protocol for unencrypted remote logon to the target sys-tem. The telnet-server packagemust be installed.




SSHSSH for encrypted logon to the target system. The openssh-server packagemust be installed with SSH tools.

WWW (HTTP)HTTP and HTTPS protocols if the target system is to be a publicweb server. The httpd packagemust be installed.

Other portsList of additional communication ports.

New portA communication port, which you can create by choosingAddPort. Select Remove Port to delete a communication port fromthe list. Enter the port in the following format:<port>:(tcp|udp)

<port>: Name of the communication port or a port number.


7.3.3.9 Authentication

In this dialog box, you define the parameters for authentication.

Figure 74: Installing Linux / VMware (customized): Configuring authentication

Use Shadow PasswordsSaves the passwords for the user accounts in a separate file. Default set-ting (not SuSE SLES 10).

Use MD5Encrypts the passwords with theMD5 algorithm. Default setting (notSuSE SLES 10).




NIS:Enable NIS

Activates NIS support. Linux uses every domain in the network as stand-ard. You should therefore specify the relevant domain here.

NIS domainDomain name used for the NIS service.

Use Broadcast to find NISDetermines the NIS server using a general broadcast. Default setting.

SMB:Enable SMB Authentication (Red Hat only)

Enables the authentication of users to an SMB server (typically a SAMBAorWindows server). SMB authentication support has no knowledge ofhome directories, user accounts or shells. The pam_smb packagemustbe installed before you can use this option.

SMB serverName of the server or servers for SMB authentication. Multiple serversmust be separated by commas.

SMB WorkgroupName of the workgroup for the SMB server.


LDAP:Enable LDAP (Red Hat only)

Activates LDAP support in /etc/nsswitch.conf. The target systemcan determine information about users (user account, home directory,shell etc.) from an LDAP directory. The nss_ldap packagemust beinstalled before you can use this option.

LDAP serverName of the LDAP server to be used. This option is set in the/etc/ldap.conf file.

LDAP Base NameDistinguished name in the LDAP directory tree, under which the infor-mation is stored. This option is set in the /etc/ldap.conf file.

Use LDAP authentication method (Red Hat only)Activates LDAP authentication in /etc/nsswitch.conf. The targetsystem can determine information about users (user account, home direc-tory, shell etc.) from an LDAP directory. The nss_ldap packagemust beinstalled before you can use this option.

LDAP serverName of the LDAP server to be used. This option is set in the/etc/ldap.conf file.

LDAP Base NameDistinguished name in the LDAP directory tree, under which the infor-mation is stored. This option is set in the /etc/ldap.conf file.

Kerberos 5:Enable Kerberos5 Authentication (Red Hat only)

Activates Kerberos support. Kerberos itself is unable to call any homedirectories, user accounts or shells. If you enable Kerberos, youmustalso enable LDAP, NIS or Hesiod. The pam_krb5 packagemust beinstalled before you can use this option.

Kerberos Realm




The realm to which the target system belongs.

Kerberos domain controllerKDC that processes the requests within this realm. Multiple KDCsmust be separated by commas.

Kerberos Master ServerMaster KDC onwhich kadmind is running. This master server proc-esses password changes and other administrative tasks.


Hesiod:Enable Hesiod Support (Red Hat only)

Activates Hesiod support for searching for home directories, useraccounts and shells. For more information about installing and usingHesiod, refer to the /usr/share/doc/glibc-2.x.-x/README.hesiod file in the glibc package. Hesiod is an extension ofthe DNS that provides information on users, groups and other data.

Hesiod LHSLeft-hand side option, which is set in the /etc/hesiod.conf file.The Hesiod library uses this option to determine the name that is to besearched in the DHS when information is queried. (The base DN isused the sameway in the case of LDAP.)

Hesiod RHSRight-hand side option, which is set in the /etc/hesiod.conf file.The Hesiod library uses this option to determine the name that is to besearched in the DHS when information is queried. (The base DN isused the sameway in the case of LDAP.)

Name switch cache:Enable nscd (Red Hat only)

Activates the nscd service. The nscd service caches information aboutusers, groups and other data. This is useful if you want to distribute thisinformation via NIS, LDAP or Hesiod. Default setting.




7.3.3.10 Pre Installation Script (for Red Hat and SuSE only)

Figure 75: Installing Linux (customized): Entering a pre-installation script

In this dialog box, you can do the following:

l Enter direct scripting commands

l Specify a script that is available on the network

The %pre constant is not permitted. The script is executed before the Linuxinstallation after the configuration file is read. Since the name server is stillunknown at this point, you can only specify IP addresses to access a com-puter in the network.


7.3.3.11 Post Installation Script

Figure 76: Installing Linux (customized): Entering a post-installation script

In this dialog box, you can do the following:

l Enter direct scripting commands

l Specify a script that is available on the network

The %post constant is not permitted. The script is executed after the Linuxinstallation.

If the network operates with a static IP configuration, you can enter IPaddresses for a network resource directly. In the case of a dynamic IP con-figuration (DHCP), the /etc/resolv.conf file is not yet complete whenthe script is executed. IP addresses cannot yet be resolved and youmusttherefore define these IP addresses here.




Run outside of the chroot environmentDisables the chroot environment, in which the scripts would otherwise beexecuted after the installation. It is then possible to copy scripts or RPMsfrom the installationmedium.

Use a specific interpreterDefines an interpreter for another script language (for example, Perl). Thisoption is set by default.

Type your %post-script belowEnter the script here.


7.3.4 Selecting / configuring applicationsIn this step you can select programs which InstallationManager is to installin addition to the operating system.

Figure 77: Installing Linux (customized): Selecting / configuring applications




Select Applications

Displays the groups of programs that can be selected.

Some packages may be preselected, depending on the following crite-ria:

l operating system

l operating system language

l hardware type of the PRIMERGY Server

l recommendation of FUJITSU LTD and Fujitsu Technology Solu-tions

The (n/n) pair of numbers following each group name indicates howmany programs (left number) are selected from the total number of pro-grams available in the group (right number).

Clicking on a "+" symbol displays the list of programs that are availablein the corresponding group.

Add-on packagesAdditional software (e.g. Java Runtime Environment, custom scripts andpackages).

ServerView Suite (n/n)Components of the ServerView Suite.

Software Packages for JAPAN (n/n)(not for SLES 10, SLES 11)

Software offered for the Japanesemarket.

This package is only available for Japanese-language operatingsystems .


Software Packages for PRIMEQUEST (n/n)(not for SLES 10, SLES 11)

Software available for PRIMEQUEST servers.

Some components of the package are only available for Japanese-language operating systems.

The dialog box is divided into two partsWhen you select an option or click on a program name, the dialog box is divid-ed into two parts:

l The programs available for selection continue to be displayed on theleft.

l On the right, you will see the information about the selected applicationas well as the parameters required for the installation.

Depending on the Linux Distribution, not all the applications dis-playedmay be selectable.

If an application requires the installation of another applicationSome applications can only be installed if certain other applications areinstalled as well.

E.g. the installation of ServerView Suite - ServerView RAIDManagerrequires Add-on packages - Java Runtime Environment to be installed.

The Information field informs you about possible software depend-encies.

If you select an application which requires the installation of another appli-cation which is not already selected, the following dialog box opens:




Figure 78: Application wizard tries to set the required parameters automatically

OKThe Application wizard attempts to select the required application.

If the Application wizard succeeds, your selection remains. Otherwise,your selection will be reset.

CancelResets your selection.

Details about the selected application are displayed on the right side

DescriptionA brief description of the selected option is displayed.

Settings for the selected application

(not available for every application)Configures settings for the selected application.


Installation source

Defines where InstallationManager can find the installation files.

Local installation:

Local removable mediaRemovablemedia on the target system.

ServerView Suite DVDData packages of the InstallationManager on the ServerView SuiteDVD.




Remote user nameUser account with the necessary privileges for the network drive.The account must be present on the computer that the URL ref-erences and which provides the resources. The user must haveread privileges on the computer for the directory in the path spec-ified above.





Remote installation:

ServerView Installation Manager data packagesData packages of the InstallationManager (on the deployment server)for remote installation.




Remote userUser account with the necessary privileges for the network drive.The account must be present on the computer that the URL ref-erences and which provides the resources. The user must haveread privileges on the computer for the directory in the path spec-ified above.


Information

Provides information about possible dependencies that are required for theinstallation of the selected program, e.g. certain services or applicationsmust be installed at the same time.


7.3.5 Backing up the configuration / starting the installationA summary of the parameters set is displayed.

Figure 79: Installing Linux (customized): Backing up the configuration / startingthe installation







l You can select or create a folder in which InstallationManager willstore the configuration file. The folder is stored as follows:

o Local installation (customizedmode only):The folder is stored on the local backupmedium.

o Remote installation:The folder is stored within the configfiles directory of the Instal-lationManager repository.


For local installation on the target system:

The configuration can only be stored in customizedmode.




The unattended installation is not started.

Start InstallationStarts unattended installation of the operating system and backs up theconfigured parameters in the file you have specified in theSave the Con-figuration to File ... dialog.

You can keep informed about the progress and status of the remote instal-lation using the InstallationMonitor.


8 Installation Monitor - Monitoringremote installationThe InstallationMonitor informs you about the progress and state of remoteinstallation processes which have been started. To start the InstallationMon-itor, click the Installation Monitor link underMonitoring in the InstallationManager welcome screen.

The InstallationMonitor is started automatically after a remote instal-lation has been started.

8.1 Graphical user interface of the Installation MonitorThe following figure shows the InstallationMonitor window with two remoteinstallations started.


8.1 Graphical user interface of the InstallationMonitor

8 InstallationMonitor - Monitoring remote installation

Figure 80: Installation Monitor window: Two remote installation processes havecurrently been started

Remote installations which have already been completed are also dis-played, provided they are not explicitly removed from the list usingStop Installation.

Remote Installation MonitorTabular view of the remote installations which have currently been start-ed.


The table is only displayed if at least one remote installation proc-ess has been started.

In each row the table displays the key figures for a started installation proc-ess which you defined when the process was configured, and also the cur-rent state of the installation:

MAC AddressMAC address of the LAN port (network card) on the target system viawhich the deployment server communicates with the target systemduring installation.

Hardware IdPRIMERGY type of the target system.

Operating SystemOperating system which is installed on the target system.

StateCurrent state of the installation process.

CommentInformation about the installation process.

Refresh nowIf you deselect Refresh list automatically, you can refresh the dis-play using theRefresh now button.

Refesh list automaticallyWhen you select this option, the display of the started installation proc-esses is refreshed automatically.

l Click the table row which represents the installation process aboutwhose progress you want to be informed.

Selected MAC AddressDisplays theMAC address of the installation process which you selectedin the remote installation table.


8.1 Graphical user interface of the InstallationMonitor


Stop installationStops the selected installation process and removes the associated entryfrom the list.

ProgressDisplays the progress of the selected installation process.

Log fileDisplays logging information for the selected installation process.

System dataDisplays the system data of the target system for the selected installationprocess.

Refesh list automaticallyWhen you select this option, the information in the display area isrefreshed automatically.

Refresh nowIf you deselect Refresh list automatically, you can refresh the infor-mation in the display area using theRefresh now button.

8.2 Monitoring remote installationThe InstallationMonitor lists all remote installation processes which have cur-rently been started on the deployment server in a table. In addition to the con-figured characteristics (target system, operating system, etc.), the Instal-lationMonitor also displays the current state of each process.


Installation started, PXE boot of the target system not yet performedIn the following figure the installation process for the target system with theMAC address CA-08-A9-03-C5-CE is selected for monitoring via the Instal-lationMonitor.

Figure 81: Installation Monitor: Installation started, but PXE boot of the target sys-tem not yet performed

As no PXE boot has yet been performed for the target system with theMACaddress CA-08-A9-03-C5-CE, the associated installation process is in thestate “SeStAgent: Waiting for PXE boot”.


8.2Monitoring remote installation


Installation started, PXE boot of the target system performedThe PXE boot for the target system with theMAC addressCA-08-A9-03-C5-CE has in themeantime been performed, whichmeans that the installationprocess could begin installing the operating system (here: Windows Server2008 R2) on the target system.

Figure 82: Installation Monitor: Operating system is installed on the target system

At themoment the installation process is in the state “SeSt: Create Par-tition”, i.e. the installation process creates a partition on the target system inaccordance with the configured default values.


As theProgress option has been selected, the progress of the process isshown in the display area. In addition to the process step currently beingexecuted, the process steps which have already been performed are doc-umented.




Installation of the operating system on the target system has been suc-cessfully completedInstallation of the operating system (here: Windows Server 2008 R2) on thetarget system has been successfully completed.

As theProgress option is selected in the following figure, the progress of theprocess is shown in the display area. All the process steps which have beenperformed are documented.

Figure 83: Installation Monitor: Installation successfully completed. Display: Prog-ress of process


In the following figure the Log file option is selected.

Figure 84: Installation Monitor: Installation successfully completed. Display: Log-ging information




TheSystem data option is selected in the following figure:

Figure 85: Installation Monitor: Installation successfully completed. Display: Sys-tem data


9 MaintenanceDepending on whether you start InstallationManager from ServerView SuiteDVD or as an application on a deployment server, the following functions areavailable after you click onMaintenance on the start page of the user inter-face.

l If InstallationManager was started from the ServerView Suite DVD:

Wide range of options for maintenance and configuration of servers alrea-dy installed (see section "Maintaining and configuring PRIMERGYservers" on page 261).

l If InstallationManager was started on a deployment server:

o Configuring andmanagingMulti Deployment (MDP) sets.o Booting any required boot images using the PXE infrastructure of

InstallationManager.o Creating a backup of the InstallationManager repository.o Restoring the InstallationManager repository using a backup.

For further information, refer to section "Maintenance on the deploymentserver" on page 265.

9.1 Maintaining and configuring PRIMERGY serversIn addition to deploying PRIMERGY servers, InstallationManager offerscomprehensive options for maintaining and configuring servers which havealready been installed.

To take advantage of these, start InstallationManager on your server fromServerView Suite DVD and in the InstallationManager’s welcomewindowclick theMaintenance entry in themenu bar or in the display area.

TheServerView Installation Manager Maintenancewindow is then dis-played.


9.1Maintaining and configuring PRIMERGY servers

9Maintenance

Figure 86: ServerView Installation Manager Maintenance window

ServerView RAIDStarts the ServerView RAID Manager for configuring andmaintaining yourserver’s RAID controllers.

Server Configuration ManagerStarts the Server ConfigurationManager for configuring your server’s gen-eral system behavior and - if they exist - for configuring the BMC, iRMC oriRMC S2/S3/S4.

9.1.1 ServerView RAIDThe ServerView RAID Manager enables you tomonitor and configure RAIDcontrollers which are incorporated in your server.


Figure 87: ServerView RAID Manager

How you operate the ServerView RAID Manager is described in themanual“ServerView Suite ServerView RAID Manager”.

9.1.2 Server Configuration ManagerThe Server ConfigurationManager offers a sequence of steps in which youcan configure the settings for your server’s general system behavior and - ifthey exist - the BMC, iRMC or iRMC S2/S3/S4.

In terms of their sequence and functionality, the dialogs offered hereare identical to the configuration steps described in the section "ServerConfigurationManager" on page 131. The only differences are in thelayout.


9.1Maintaining and configuring PRIMERGY servers

9Maintenance

Figure 88: Server Configuration Manager

<<FirstTakes you to the first configuration step.

<BackTakes you to the previous configuration step.

Next>Takes you to the next configuration step.

Last>>Takes you to the last configuration step.

SaveWrites the current session’s configuration parameters to the non-volatilememory area of the PRIMERGY system, which is reserved for the ServerManagement functions.


9.2 Maintenance on the deployment serverWhen you start InstallationManager on the deployment server and click onMaintenance in the user interface, the following functions are available in theServerView Installation Manager Maintenancewindow.

Figure 89: ServerView Installation Manager Maintenance window


9.2Maintenance on the deployment server

9Maintenance

MDPIntegrating custom programs or scripts into the InstallationManager plat-form (MSWindows PE) and launching the package on target systems viaPXE boot.

Generic PXE BootBooting any required boot images using the PXE infrastructure of Instal-lationManager.

Backup RepositoryCreating a backup of the InstallationManager repository.

Restore RepositoryRestoring the InstallationManager repository using a backup.

9.2.1 Configuring and managing Multi-Deployment (MDP) setsTheMulti-Deployment Platform (MDP) is the bootable platform that Instal-lationManager provides for user-specific purposes. You can start MDP eitherlocally using the ServerView Suite DVD or remotely via PXE.

TheMDP infrastructure is described in theWhite Paper "MDP -Multi-Deployment Platform", which you will find on the ServerView SuiteDVD.

MDP enables you to start a PXE boot that is based on an “MDP set”. AnMDP set is a user-specific collection of scripts and/or programs that areexecuted in order to perform a PXE boot on theMDP platform.

All theMDP structural information (configuration files, etc.) required for aPXE boot is collected in theMDP set.

Two different types of MDP set are distinguished:

l PreconfiguredMDB set

A preconfiguredMDP set is an existingMDP set that has been createdby the user and which youmake available to InstallationManager. Theset must contain all theMDP infrastructure information (configurationdata, metadata, etc.) required by theMDP process.


l MDP configuration

In the context of anMDP configuration, you only provide executables.InstallationManager then uses these files to automatically generate therequiredMDP infrastructure information. You can only manageMDPconfigurations within InstallationManager.

TheMDP Configurations dialog box allows you to

l configure new MDP sets (MDP set configurations)

l manageMDP sets (preconfiguredMDP sets andMDP configurations)in a table

l prepare and start the PXE boot based on the selectedMDP set.

Proceed as follows:

In theServerView Installation Manager Maintenancewindow, click on theMDP link to open theMDP Configurations dialog.

Figure 90: MDP Configurations dialog

TheMDP Configurations dialog box displays in table form all MDP setsthat are currently available in InstallationManager. PreconfiguredMDP setsare displayed as typeCustom Set. MDP configurations are displayed astypeConfiguration.



9Maintenance

New ConfigurationOpens theGeneric MDP Configuration dialog box, which allows you toprovide theMDP infrastructure information (parameters, agents, files etc.)that is required for configuring a new MDP set. In addition, you can assigna name to this MDP set.

New Custom Set

Opens thePreconfigured MDP Set dialog box for adding a CustomMDPset to theConfigurations and Sets table.

EditOpens the dialog box for editing the selectedMDP set.

This button is only active if you select anMDP set in theCon-figurations and Sets table.

Which dialog box is opened depends on whether you have selected a cus-tomMDP set or anMDP configuration.

If a custom MDP set has been selected:

ThePreconfigured MDP Set dialog box allows you to rename the select-ed customMDP set.

Figure 91: Multi Deployment Platform - Renaming a preconfigured MDP set


NameNew name for the selectedMDP set.

OkApplies the new name to the selectedMDP set.

CloseCloses the dialog.

If an MDP configuration has been selected:

TheGeneric MDP Configuration dialog box allows you to view andmod-ify the current settings of the selectedMDP configuration.

DeleteDeletes the selectedMDP set following a confirmation dialog.

This button is only active if you select anMDP set in theConfigurationsand sets table.

BootOpens theGeneric PXE Boot dialog, where you can prepare and startthe PXE boot based on the selectedMDP set.

CloseCloses theMDP Configurations dialog.



9Maintenance

9.2.1.1 Configuring new MDP sets

Figure 92: Multi Deployment Platform - Generic MDP configuration

In theGeneric MDP Configuration dialog box, you provide theMDP infra-structure information (parameters, agents, files etc.) that is required for con-figuring a new MDP set. In addition, you can assign a name to this MDP set.

In the context of anMDP configuration, you only provide executables. Instal-lationManager then uses these files to automatically generate the requiredMDP infrastructure information. You can only manageMDP configurationswithin InstallationManager.

TheMDP configuration is displayed in theConfigurations and Sets table.Configuration

Defines the name of theMDP set and the final power status of the target sys-tem subsequent to a preceding PXE-based execution of theMDP set.


NameName of theMDP set.

Final Power StatusFinal power status of the target system subsequent to a preceding PXE-based execution of theMDP set.

Power OffDefault value. The target system will be powered off.

RebootThe target system will be rebooted.

Files

Provides the requiredMDP structure information (parameters, agents,executables, scripts, and other files).

NewOpens a dialog box which allows you to add a file to the current con-figuration.

All added files are displayed in the Files field.

DeleteDeletes the selected entry in the Files field as well as the correspondingfile from the configuration.

Command Line and Payload

Allows you to enter the command line for your executable or script, and theactual parameters.



9Maintenance

Command LineCommand line for your executable or script.

Agent PayloadData theMDP process is provided with via the<drive>:\MDP\Config.ini file.

OkCopies the new MDP configuration set to theConfigurations and Setstable.

In the case of an already existingMDP configuration: Applies themodifiedsettings.


9.2.1.2 Adding a new set / editing a custom set

Figure 93: Multi Deployment Platform - Adding a preconfigured MDP set


In thePreconfigured MDP Set dialog box, you can add a customMDP setto theConfigurations and Sets table or rename a customMDP set whichhas a corresponding entry in the table.

A preconfiguredMDP set is an existingMDP set that has been created bythe user and which youmake available to InstallationManager. The set mustcontain all theMDP infrastructure infomation (configuration data, metadata,etc.) required by theMDP process.Configuration Name

Defines / changes the name of theMDP set for use later on.

NameName of theMDP set for use later on.

Custom Set

TheCustom Set group is not displayed if you opened the dialogbox by clickingEdit in theMDP Configurations dialog box.

Selects the path of an existingMDP set.

Root FolderMDP set that you want to add to your configuration.

When you click on the folder icon, you can select theMDP set path viathe file browser.

OKCopies the selectedMDP set to theConfigurations and Sets table.

If you opened the dialog box by clickingNew Custom Set in theMDPConfigurations dialog box:Copies the selectedMDP set to theConfigurations and Sets table.

If you opened the dialog box by clickingEdit in theMDP Configurationsdialog box:Gives a new name to theMDP set.




9Maintenance

9.2.1.3 Preparing and starting the PXE boot

In theGeneric PXE Boot dialog box, you can prepare and start the PXEboot based on the selectedMDP set.

Figure 94: Generic PXE boot based on an MDP set

For an explanation of theGeneric PXE Boot dialog box, see section "Boot-ing any required boot images via PXE" on page 275.

OKStarts theMDP set-based generic PXE boot. The InstallationMonitorstarts automatically once the remote installation is started. The Instal-lationMonitor window provides information on the progress and status ofthe remote installation.

CancelCloses theGeneric PXE Boot dialog.


9.2.2 Booting any required boot images via PXEBesides using the PXE boot infrastructure of InstallationManager for theentire configuration and installation of PRIMERGY servers, you can also useit to boot any required boot images on a target system via PXE.

l Click Generic PXE Boot in theServerView Installation ManagerMaintenancewindow to open theGeneric PXE Boot dialog.

Figure 95: Generic PXE boot

Saved MAC AddressesHere you can select a previously savedMAC address from a list. ThisMAC address is automatically displayed in theMAC Address field of theTarget System group (see below).



9Maintenance

Target system

Determines the target system onwhich the boot image is to be booted.

MAC AddressMAC address of the LAN port (network card) on the target system that isused to enable communication between the deployment server and the tar-get system during the installation.

Remote Management Interface of the target system

Here you can configure that the PXE mode is activated automatically on thetarget system as part of the generic boot operation (either with or without arestart of the target system) in the following cases:

l The target system has a remotemanagement interface (BMC, iRMC,iRMC S2/S3/S4 or management blade).

l The target system has aWake on LAN (WoL)-capable LAN adapter (net-work card).

If the target system does not have any of these remotemanagementinterfaces, youmust start the target system for the PXE boot explicitlyvia local operation.

TypeType of remotemanagement interface on the target system.

You can choose from the following options:

l Remote Management Controller (IPMI) for PRIMERGY serverswith BMC, iRMC or iRMC S2/S3/S4.

l Management Blade (SNMP) for PRIMERGY blade servers.


l Wake On LAN for target systems with aWake on LAN (WoL)-capa-ble network card (NIC), which is powered by the standby branch ofthe target system even when the target system is switched off.

l No remote control if the target system does not have a remoteman-agement interface. In this case, youmust start the target system forthe PXE boot explicitly via local operation.

"Remote Management Controller (IPMI)" parameters

IP AddressIP address of the BMC, iRMC or iRMC S2/S3/S4.

IPMI UserLocal user account on the BMC, iRMC, or iRMC S2/S3/S4 of the tar-get system.

IPMI PasswordPassword for the local user account on the BMC, iRMC, or iRMCS2/S3/S4.

CommandDetermines when and how the installation is started on the target sys-tem:

Restart system and boot via PXE boot:Automatically enables PXE boot mode with a subsequent restart ofthe target system.

Set boot mode to PXE (no restart):Automatically enables PXE boot mode without a subsequentrestart of the target system. In this case, youmust initiate a restartyourself.



9Maintenance

"Management Blade" parameters

IP AddressIP address of themanagement blade

SNMP CommunitySNMP user group with the corresponding rights on themanagementblade.

CommandDetermines when and how the installation is started on the target sys-tem:

Restart system and boot via PXE boot:Automatically enables PXE boot mode with a subsequent restart ofthe target system.

Set boot mode to PXE (no restart):Automatically enables PXE boot mode without a subsequentrestart of the target system. In this case, youmust initiate a restartyourself.

"Wake On LAN" parametersIn the case of Wake on LAN, InstallationManager uses IP broadcast orEthernet broadcast to send amagic packet as a UDP datagram to the sub-net in which the target system is located.

The following applies:

l If the target system is in the same LAN segment as the deploymentserver, you do not need to specify an address underBroadcastAddress. In this case, InstallationManager automatically uses thelimited broadcast address 255.255.255.255 and sends themagicpacket to UDP port 9 as an Ethernet broadcast using theMACAddress of the target system.


l If the target system is in a different LAN segment that is bridged byone or more gateways, enter either of the following underBroadcastAddress:

o Subnet broadcast address of the LAN segment in which the tar-get system is located. The address must contain the value "255"in the device area (host area) (e.g. 123.123.2.255).

In this case, themagic packet is sent to the gateway via one or sev-eral hops, and the gateway ultimately transmits the Ethernet broad-cast to the subnet of the target system.o IP address of a BOOTP/DHCP server.

In this case, youmust select theBroadcast to Bootstrap Serveroption and specify a valid IP address under IP Address in the LANsegment of the target system.

Broadcast AddressSubnet broadcast address of the LAN segment in which the target systemis located, or Unicast address of a BOOTP/DHCP server.

If you specify the Unicast address of a BOOTP/DHCP server, youmustselect theBroadcast to Bootstrap Server option.

Broadcast to Bootstrap ServerIf you select this option, themagic packet is sent to UDP port 67 (Boot-strap Protocol (BOOTP) Server); otherwise, it is sent to UDP port 9.

This option is required if you specify the Unicast address of aBOOTP/DHCP server underBroadcast Address. Furthermore, youshould select this option if it is not guaranteed that all gateways includedin a subnet broadcast are configured for "subnet broadcasting".



9Maintenance

IP AddressAny Unicast address in the subnet of the target system. Using this IPaddress, the BOOTP/DHCP server determines the LAN interface (LANport) via which it is to send themagic packet (in this case, aDHCP/BOOTP reply packet).

Path and bootstrap image for PXE boot

ThePath and Bootstrap image for PXE boot group is onlydisplayed if the Generic PXE boot was started directly via theServerView Installation Manager Maintenancewindow.When using anMDP set (preconfiguredMDP set or MDP con-figuration), the corresponding information is provided by theMDP set.

Specifies the path for the boot image as well as the path and name of thebootstrap loader.

Boot image and bootstrap loader must be on the deploymentserver.

Boot Image PathDirectory on the deployment server in which the boot image is located.

Bootstrap LoaderDirectory and name of the bootstrap loader on the deployment server.

Is a Floppy ImageDefines that the boot image is a disk image.

OKBoots the boot image via PXE on the target system.

The InstallationMonitor starts automatically once the remote installationis started. The InstallationMonitor window provides information on theprogress and status of the remote installation.


CancelCloses theGeneric PXE Boot dialog.

9.2.3 Creating / importing a backup of the Installation ManagerrepositoryThe InstallationManager repository contains operating data for InstallationManager, configuration files with user configurations for an unattended instal-lation, as well as remote installation details (MAC address of the target sys-tem, remotemanagement interface of the target system via which the PXEboot is to be initiated, etc.).

InstallationManager offers the following functions to ensure the availability ofan intact repository at all times:

l Using theBackup Repository function, you can create a backup of theInstallationManager repository and save it to a ZIP file.

l Using theRestore Repository function, you can restore the Instal-lationManager repository from a backup.

9.2.3.1 Creating a backup of the Installation Manager repository

Using theBackup Repository function, you can create a backup of theInstallationManager repository and save it to a ZIP file.

l In theServerView Installation Manager Maintenancewindow, clickon theBackup Repository link to open theBackup Repositorydialog.

DirectoryDirectory in which you want to save the repository backup.

If you click on the folder icon, you can select the directory via the filebrowser.

NameName of the backup copy of the repository.

OKCreates a backup copy of the repository.



9Maintenance


9.2.3.2 Restoring the Installation Manager repository

Using theRestore Repository function, you can restore the InstallationMan-ager repository from a backup copy (ZIP file).

l In theServerView Installation Manager Maintenancewindow, clickon theRestore Repository link to open theRestore Repositorydialog.

Backup FilePath name of the repository backup.

If you click on the folder icon, you can select the backup copy via the filebrowser.

OKStarts restoring the repository.



10 Installation Manager InformationClicking the Information entry in themenu bar or display area in the startpage of the InstallationManager GUI takes you to the Informationwindow:

Figure 96: Information window

Operating instructions and technical manuals are provided on Server-View Suite DVD.

What’s NewProvides information on changes in the current release of the InstallationManager and the change history of the previous releases.


10 InstallationManager Information

RestrictionsProvides information on restrictions and product dependencies and offersproposed solutions.

Driver IndexProvides an overview of the driver and software packages which theInstallationManager installs for PRIMERGY servers and their hardwarecomponents.

Technical InformationProvides technical information for installing Linux on PRIMERGYservers.

DocumentsHere you will find How-tos and white papers.

EULAHere you will find the End-User License Agreement.

If you have started the InstallationManager as an autonomous application,the information page also contains the following entries: links to the webpages of Fujitsu Technology Solutions:

ManualsLink to theOnline Manuals page on the website of Fujitsu TechnologySolutions. An Internet connection is required here.

ProductsLink to thePRIMERGY Servers page on the website of Fujitsu Tech-nology Solutions. An Internet connection is required here.

ServerView LinksThe ServerView Suite link collection contains links to further informationon ServerView Suite and PRIMERGY servers.


11 ReferenceIn this section you will find information on the following topics:

l PXE (Preboot eXecutionEnvironment) process

l Setting up a DHCP server

l Virtual Local Area Network (VLAN)

11.1 The PXE processThe PXE process is based on the PXE protocol, which is supported by a spe-cial boot mode of the LAN adapter. It does not become active until the sys-tem BIOS activates the LAN adapter as a boot device during system bootand jumps to it. For this to happen, the LAN devicemust be set to the highestpriority in the system BIOS boot order.


11.1 The PXE process

11 Reference

Figure 97: The PXE process

2-3 The boot process on the client side starts with a PXE broadcast tothe DHCP server to receive a temporary IP address (mandatory).

4-5 A similar broadcast discovers the PXE boot server on port 67 or 4011(depending on the information issued by the DHCP server) request-ing a boot image name.

6-8 If the required information has been provided, a TFTP session is start-ed to receive the boot image from the PXE server. The image sizemust not exceed 1.44MB (floppy disk emulationmode). This bootimage is copied tomemory address 07C0h and started by the BIOS.

9 As long as the operating system kernel is not started and neither arethe kernel drivers, any LAN access is performed using the PXEBIOS.


The PXE protocol is used by the PXE service of the InstallationManager toboot the InstallationManager platform remotely on the reference system. Forthis purpose the deployment server (where the InstallationManager isinstalled) contains a bootstrap file and the actual OS image in the form of aRamDisk image.

This image (approx. 160MB in size) exists in duplicate: in a 32-bit and a 64-bit version. Which version of the image is selected depends on the type ofWindows installation operating system. After the RamDisk image has beentransferred, the InstallationManager platform (client instance of the Instal-lationManager) executes autonomously on the target system. A network con-nection is only still required to load further installation resources (drivers, soft-ware packages, OS images) dynamically and for status tracking via theInstallationMonitor.

The InstallationManager platform directory is approximately 2 x 160MB in size. However, thememory space required on the target sys-tem onwhich the PXE client runs is considerably greater. Remotebooting and unattended installation require aminimum of 1024MB ofmainmemory on the target server. In addition, operating systeminstallation can itself require additional memory.

11.2 Setting up a DHCP serverDHCP (Dynamic Host Configuration Protocol) is a protocol for assigningdynamic IP addresses to devices in a network. With dynamic addressing, adevice can have a different IP address every time it connects to the network.In some systems, the device's IP address can even change while it is stillconnected. DHCP also supports amix of static (reserved) and dynamic IPaddresses.


11.2 Setting up a DHCP server

11 Reference

WhenDHCP and PXE simultaneously run on a deployment server,both services occupy the same network port and PXE acts as a DHCPproxy. If, in this configuration, DHCP is uninstalled, PXE has to be rein-stalled autonomously. For more information, refer to the DeploymentManager manual.

The default directory C:\Program Files\Fujitsu\ServerView Suite\D-eploymentService\Bin contains a file called localipaddress.txt. Fromthis source the PXE service obtains its IP address. If the file is emptyor not present, the PXE service automatically occupies LAN port 0 (ifDHCP is located on the same level, it occupies LAN port 0 as well).Depending on the list underControl Panel - Network and Dial-up Con-nections - Settings - Advanced, you can also use a different LAN port.

11.3 VLAN (Virtual Local Area Network)A Virtual LAN is a local network which behaves as if all participants were vis-ible in the same network, although they are actually connected to differentphysical networks. VLANs are configured through software rather than hard-ware, whichmakes them extremely flexible. One of the biggest advan-tagesof VLANs is that, when a computer is physically moved to another location, itcan stay on the same VLAN without any hardware reconfiguration.

The PXE agent code (part of the target server BIOS boot phase) pro-tocol scans the LAN segment for PXE and DHCP servers by trans-mitting a broadcast on port 67. If these servers are placed behind arouter, hub or switch with activated Virtual LAN software, thesedevices have to be programmed port by port to bypass these broad-casts.

For multi segment deployment and required router configuration seealso section "Configuring router for multi segment deployment" onpage 94.

VLAN configurationThe PXE client running on the blade server does not support VLANs anddoes send untagged frames. However, the LAN is supported by PRIMERGY


server systems.

VLAN requirements

l The external switch in the LAN must support VLANs.

l The driver for the server blade network connectors (NIC) must allow tobe integrated in several VLANs.

l The image from the PXE server must already contain a driver pre-con-figured for VLANs.

Example of a VLAN configuration

l VLAN-IDs must be assigned for all segments on the segment switch,except for the deploy segment.

o I.e. data traffic towards the deploy segment is transmitted untagged.o If the PXE client sends an untagged frame, it is allocated to all three

source-ports by the switch blade. The untagged frame is only trans-ferred to the untagged port (connected to the deploy segment) by thesegment switch.

o After the operating system has been booted on the server blade, theoperating system identifies several separate segments due to theVLAN configuration.

l All ports in the switch blademust recognize all VLAN-IDs and have tobe configured for untagged frames at the same time. Even though theswitch blade does not perform a segmentation, without VLAN con-figuration it would abandon all frames that carry a VLAN tag.

Summaryl PXE service data is only forwarded to the deploy segment.

l The VLAN configuration provides the splitting of segments after theboot process.

l Data exchange among the segments is only possible via a router.

l Full redundancy can be configured for both network controllers.


11.3 VLAN (Virtual Local Area Network)

11 Reference


12 License Agreement for End User(Fujitsu Technology Solutions Software License Agreement for End User)

1. Subject of this Agreement1.1 For the purposes of this agreement “Software” shall mean the softwarewith the object code, the version and the specification indicated in the soft-ware product data sheet of Fujitsu Technology Solutions.

The Software consists of machine-readable instructions and/or printed doc-umentation and related licensedmaterials.

1.2 Please read this agreement carefully before you use the Software. If youdo not agree with the license terms in this agreement, you are not permittedto use the Software andmust immediately return all copies of the Softwareand all accompanying items to the Licensor/Sublicensor (either Fujitsu Tech-nology Solutions or the reseller who supplied you with the Software) withproof of purchase for a full refund.

1.3 Any use of the Software requires the proper payment of the applicablelicense fees. By using the Software you agree to be bound by the terms ofthis agreement.

1.4 Fujitsu Technology Solutions reserves the right to implement at any timein the future an additional software license key and/or license certificates ascountermeasures against software piracy.

1.5 Software components from third-party software suppliers which are partof the scope of the delivery are subject to separate license agreements thatare included with the Software or that are transmitted by Fujitsu TechnologySolutions upon request.

2. End User License2.1 Fujitsu Technology Solutions grants you a non-exclusive and non-trans-ferable license to use the Software on the number of workstations for whichyou have purchased licenses. Unless you purchase additional licenses, youare not permitted to operate the Software onmore than themaximum numberof licensed workstations or on hardware that exceeds the specified type.


12 License Agreement for End User

You are permitted tomake a backup copy of the Software for archiving pur-poses, provided you properly mark the copy or partial copy of the Softwarewith the copyright notice and any other ownership information.

2.2 You are not permitted to copy, modify or distribute the Software. Fur-thermore, you are not permitted to re-compile, re-engineer, convert, revise,compile or modify the Software. Youmay not sub-license, without selling therelated hardware, assign, rent, lease or transfer the Software except asexpressly permitted by this agreement or due tomandatory legal regulations.

2.3 If you acquired the Software as a program upgrade, your license for theuse of the old software version ends automatically with the installation of theupgrade version of the Software. If parts of the old software version are notreplaced by the upgrade version, the license for the old version continues tobe effective until the remnants of the old software version are also replacedor deactivated or shut down in any other way.

2.4 Unless specified otherwise in the respective software data sheet of Fujit-su Technology Solutions, the license for a software version or release doesnot give you any rights to new releases (updates), new versions (upgrades)or technical support services for the Software. Supplemental software sup-port contracts andmaintenance services, including or excluding newreleases and new versions and additional technical support services, can bepurchased separately either from Fujitsu Technology Solutions directly orfrom authorized software resellers.

3. DownloadingFor Software supplied by Fujitsu Technology Solutions over a network or asimilar distribution path, the following additional conditions shall apply:

All products supplied for downloading by Fujitsu Technology Solutions areselected, made available and— if supplied by third parties — provided with-out modification. However, you are fully responsible for ensuring themostcurrent version and usability of downloadablematerial for your own purposesand on your own system. You download Software at your own risk. FujitsuTechnology Solutions will not accept any liability, particularly not for trans-mission errors or problems that arise during the downloading process (line fail-ures, connection interruptions, server failures, data corruption, etc.).


The website of Fujitsu Technology Solutions is operated and administeredonly for those countries in which Fujitsu Technology Solutions has one ormore offices. Fujitsu Technology Solutions accepts no responsibility thatSoftware and/or documentation can or may be downloaded from a FujitsuTechnology Solutions website also in locations other than the countries men-tioned above. If you access a website of Fujitsu Technology Solutions fromabroad, you are fully responsible for complying with any local regulations.Fujitsu Technology Solutions expressly prohibits the downloading of Soft-ware and/or documentation from a Fujitsu Technology Solutions website incountries where such downloading is considered illegal.

4. CopyrightAll rights and licenses, unless they are expressly granted to you in thislicense terms, as well as all property and usage rights related to the Software(including parts of the Software) remain fully with Fujitsu Technology Solu-tions and/or its third-party licensors.

The license terms do not authorize you to use the brands, logos or trade-marks of Fujitsu Technology Solutions or its third-party licensors, nor are youpermitted to use any other brands which are deceptively similar to thebrands, logos or trademarks of Fujitsu Technology Solutions. Each and anyuse of brands, logos or trademarks with respect to the Software or FujitsuTechnology Solutions requires the express consent of Fujitsu TechnologySolutions.

5. Licensor’s warranty and liability disclaimer, if Software is sold anddelivered by ResellerIf you acquire the Software directly from an authorized reseller (called“Reseller”), the right to install and use the Softwaremay be subject to addi-tional software license conditions agreed upon between you as the licenseeand the respective reseller.

In all cases of an authorized software resale, the software is sublicensed andmade available to the licensee directly by the Reseller. In such cases, Fujit-su Technology Solutions is not a contractual party of the software licenseagreement between you, as licensee and the Reseller, as far as the pro-curement of the software licenses are concerned. Legal claims in connectionwith the software licensing can therefore be asserted only on the basis of the



agreements with the Reseller. Under no circumstances, however, will therespective scope of the license for the licensee exceed the scope of thelicense agreements as specified in sections 1, 2, 3 and 4 of this agreement.

Subject to mandatory legal regulations, particularly those governing liabilityand/or warranties, which cannot be excluded in connection with end userlicense agreement regulations and with reference to the licensee’s claimsagainst the Reseller, Fujitsu Technology Solutions disclaims all warrantiesfor the Software in this agreement.

For the same reason, Fujitsu Technology Solutions disclaims any and all lia-bility/claims for any violations of third parties’ rights as well as any impliedwarranties for the software’s marketability and its suitability for a particularpurpose. This disclaimer of liability does not apply in cases of willful or mali-cious behavior by Fujitsu Technology Solutions.

In this End User License Agreement, Fujitsu Technology Solutions grants nowarranties of any kind, either express or implied.

6. Disclaimer of liability with respect to shareware, freeware and/oropen source software components6.1 The Softwaremay contain freeware or shareware which Fujitsu Tech-nology Solutions received from a third party. Fujitsu Technology Solutionspaid no license fees for the use of this freeware or shareware. Accordingly,the licensee is not charged any license fees for the use of the freeware orshareware. You recognize and accept that Fujitsu Technology Solutionstherefore grants no warranties with respect to such freeware or sharewarecomponents and does not assume any liability in connection with the own-ership, the distribution and/or the use of the respective freeware or share-ware.

6.2 The Softwaremay also contain open source software components thatwere developed according to the “open sourcemodel” and which are dis-tributed exclusively on the basis of the GPL (General Public License:http://www.gnu.org/copyleft/gpl.html) terms and conditions or other standardopen source standard license terms and conditions applicable to the respec-tive open source components at the time of their dissemination. You rec-ognize and accept that the licensing of such open source software com-ponents is governed exclusively by the above-mentionedGPL terms or by


the conditions which are otherwise included with the open source softwarecomponents. Fujitsu Technology Solutions receives neither license fees norany other compensation for the delivered open source software components.As far as Fujitsu Technology Solutions or a third party receives any com-pensation in connection with open source software components, it isreceived exclusively for additional delivery items and/or services.

Because of the special nature of the development and distribution of opensource software components, Fujitsu Technology Solutions assumes noexpress or implied liability for such components and excludes any kind of war-ranty for such open source software components, particularly in connectionwith missing specifications, lack of functionality, programming errors or anyother malfunctions.

7. General limitations of liability7.1 Neither Fujitsu Technology Solutions nor its suppliers are liable for anyconsequential or indirect damages, including damages arising as a result ofor in connection with an operational interruption, lost profits or sales, lostdata, or costs of capital. Fujitsu Technology Solutions and its suppliers willnot be liable for additional ancillary or consequential costs or for any otherlosses, costs or expenses of any kind which arise as a result of the holding,sale, use or impossibility of use of the Software, independent of whethersuch claims are asserted due to warranty rights, contracts, tort or any otherlegal theory.

7.2 The liability of Fujitsu Technology Solutions for direct damage caused asa result of a contract violation and/or other action or lapse on the part of Fujit-su Technology Solutions which have not been excluded or cannot be com-pletely excluded due tomandatory law are limited to nomore than€250,000.00. Any and all other liabilities for direct damage are excluded.Damage caused by Fujitsu Technology Solutions as a result of slight neg-ligence are excluded to the extent permitted by applicable legal regulations.

7.3 Limitations and exclusions of liability resulting from this agreement do notapply to damage where Fujitsu Technology Solutions carries compulsory lia-bility according to applicable laws and where such liability cannot be limitedto amaximum amount (for example, liability for bodily damage; product lia-bility or fraudulently incorrect information).



8. Export controlsDue to its components as well as the nature or purpose of these com-ponents, the export of the Software and/or its accompanying documents maybe subject to official or regulatory approval. In cases where the Software isintended for export, you are obliged to get all approvals and authorizationsrequired to comply with all relevant export regulations.

The Softwaremay not be exported if there is reason to assume that the Soft-ware will be used in connection with nuclear, chemical or biological weaponsor for missile technology. Furthermore, youmay not deliver the Software—or have it delivered indirectly — to such companies or persons who are listedin the applicable U.S. export regulations (particularly the Table of DenialOrders/U.S. Denied Persons Lists (DPL) or in the E.U. export regulations(particularly the EU Terrorist List) or in the applicable warnings issued by theGerman export authorities or any other competent authorities in any country.

Under no circumstances is Fujitsu Technology Solutions obligated to deliversoftware, patches, updates or upgrades, to provide software for download orto fulfill any other contractual commitments if this would be a violation of theapplicable export regulations of the Federal Republic of Germany, the Euro-pean Union, the United States of America or of any other countries.

If you export or re-export the Software or a copy of it, this may be a violationof applicable export laws and a severe violation of the terms of this agree-ment.

9. Miscellaneous9.1 If any term or condition in this agreement or any other contract that is sub-ject to the terms and conditions of this agreement turns out to be invalid orunenforceable (partly or in full), the validity of all other terms and conditionsremains unaffected, unless complying with the remaining terms and con-ditions would represent an unreasonable hardship for either contract party,even with the application of applicable legal regulations to close the legalgap.

9.2 If you/ the licensee do not pay the license fees due and/or if the licenseedoes not comply with essential terms and conditions of this license agree-ment, Fujitsu Technology Solutions reserves the right to cancel the license.


In case of such cancellation, youmust immediately return any and all copiesof the software in your possession and confirm the complete return [of thesoftware copies] or the destruction of these copies in writing.

9.3 Neither you nor Fujitsu Technology Solutions is responsible or liable forthe respective party’s non-compliance with its obligations if the reason forsuch non-compliance is outside the party’s control due to forcemajeure.

9.4 Any and all modifications and/or amendments to these license terms andconditions are only valid if they aremade in writing.

10. Applicable law10.1 These license terms and conditions are governed by the laws of the Fed-eral Republic of Germany.

10.2 In the event that provisions of clause 10.1 are unenforceable, theselicense terms and conditions shall be governed by the laws of the country inwhich you acquire the Software, with the following exceptions: 1) In Aus-tralia, the terms and conditions of this license are governed by the laws of thestate or sovereign territory in which the business contract is being concluded;2) in Albania, Armenia, Belarus, Bosnia-Herzegovina, Bulgaria, Croatia, theCzech Republic, Georgia, Hungary, Kazakhstan, Kirgizia, the former Yugo-slavian Republic of Macedonia (FYROM), Moldavia, Poland, Romania, Rus-sia, Slovakia, Slovenia, the Ukraine and the Federal Republic of Yugoslavia,the terms and conditions of this license are governed by the laws of the Fed-eral Republic of Germany; 3) in the United Kingdom [Great Britain], all dis-putes with respect to these license terms and conditions are governed byEnglish law, and English courts have exclusive jurisdiction; 4) in Canada, theterms and conditions of this license are governed by the laws of the Provinceof Ontario; 5) in the United States of America and in Puerto Rico as well as inthe People’s Republic of China the terms and conditions of this license aregoverned by the laws of the U.S. State of New York.




IndexA

AdapterWindows 176

AppleTalk 176Authentication 235

B

Backing up the configuration 162Basic Configuration (Linux) 212Basic settingsWindows 170

C

Client for Microsoft network 183Client for Netware network 183Configure SNMP notification 183Configuring RRAS 183Createadditional domain controller 183child domain 183new domain tree 183new forest 183

Creating a new domain tree 183Creating a new forest 183Creating child domains 183

D

Defining a target system forremote installation

107

DNS server, Windows 176Domain controller 183downloadcurrent software versions 12information files 12

I

Installation image forWindows2008

168

IP configurationWindows 176

IPX 176

L

LinuxBasic Configuration 212

M

MAC address 107

N

NetBIOS 176NetMon 176Network settingsWindows 176

Novell Network Client 183

P

Passwordadministrator 170

Post Installation Script 241PPTP 176

R

Regional settingsWindows 170

Remote control forWindows 2008187Remote installationdefining a server type 112defining a target system 107

RIP 176

S

Server type for remote installation 112

Index

Services forWindows 183SNMP agent 183SNMP service 183SNMP Trap (see "SNMP noti-fication")

183

Starting the installation 162

T

Typographic conventions 14

U

User license forWindowsServer

174

W

Windowsbasic settings 170configuring RRAS 183DNS server 176IP configuration 176network settings 176services 183system settings 174

Windows 2008configuring remote control 187installation image 168installation variant 168

WINS-Server 176
