Fujitsu PRIMEQUEST 3800B2 User Guide

PDF

ஆவணம்

விளம்பரம்

User Guide - English

FUJITSU Server PRIMEQUEST 3000 Series Business Model

iRMC S5

Configuration and Maintenance

CA92344-1651-06

Edition October 2019

Comments… Suggestions… Corrections…

The User Documentation Department would like to know your opinion of this manual.

Your feedback helps us optimize our documentation to suit your individual needs. https://support.ts.fujitsu.com/IndexContact.asp?lng=COM&ln=true

Copyright and trademarks

Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

–

The contents of this manual are subject to change without prior notice.

–

Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information in this manual.

–

No part of this manual may be reproduced in any form without the prior written permission of

Fujitsu.

–

Microsoft, Windows, Windows Server, Hyper-V and BitLocker are trademarks or registered trademarks of

Microsoft Corporation in the United States and/or other countries.

–

Linux is a registered trademark of Linus Torvalds.

–

Red Hat, the Shadowman logo and JBoss are registered trademarks of Red Hat, Inc. in the U.S. and other countries.

–

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Atom, Intel Atom Inside, Intel Core, Core

Inside, Intel vPro, vPro Inside, Celeron, Celeron Inside, Itanium, Itanium Inside, Pentium,

Pentium Inside, Xeon, Xeon Phi, Xeon Inside and Ultrabook are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries.

–

Ethernet is a registered trademark of Fuji Xerox Co., Ltd. in Japan and is a registered trademark of Xerox Corp. in the United States and other countries.

–

VMware is a trademark or registered trademark of VMware, Inc. in the United States and other countries.

–

Novell is a registered trademark of Novell Inc., and SUSE and the SUSE logo is a trademark, of

SUSE LLC, a Novell company, in the United States and other countries.

–

Xen is a trademark or registered trademark of Citrix Systems, Inc. or its subsidiaries in the

United States and other countries.

–

Other company names and product names are the trademarks or registered trademarks of their respective owners.

–

Trademark indications are omitted for some system and product names in this manual.

Contents

1 Preface..................................................................................................................................................................... 5

1.1

Concept and target groups for this manual ...................................................................................................... 5

1.2

Documentation overview .................................................................................................................................. 6

1.3

Typographic conventions ................................................................................................................................... 7

2 Overview of the iRMC functions ............................................................................................................................... 8

2.1

Standard functions ........................................................................................................................................... 8

2.2

Extended functions ......................................................................................................................................... 15

2.3

Embedded Lifecycle Management .................................................................................................................. 16

2.4

User interfaces ................................................................................................................................................ 18

2.5

Application programming interfaces ............................................................................................................... 19

2.6

Communication protocols used ...................................................................................................................... 20

2.7

Front panel LEDs controlled by the iRMC ........................................................................................................ 21

3 First Steps .............................................................................................................................................................. 22

3.1

Configuration of the LAN interface ................................................................................................................. 22

3.1.1

Requirements .......................................................................................................................................... 22

3.1.2

Configuring the LAN interface using UEFI ............................................................................................... 23

3.1.3

Testing the LAN interface ....................................................................................................................... 25

3.2

Logging in to the iRMC S5 for the first time .................................................................................................... 25

3.2.1

Requirements .......................................................................................................................................... 25

3.2.2

iRMC factory defaults ............................................................................................................................... 26

3.2.3

Logging in ............................................................................................................................................... 26

3.2.4

Logging out ............................................................................................................................................. 27

4 User management ................................................................................................................................................. 28

4.1

User management concept ............................................................................................................................. 28

4.2

User permissions ............................................................................................................................................ 31

4.3

Local user management ................................................................................................................................. 32

4.3.1

Local user management using the iRMC web interface ......................................................................... 32

4.3.2

Local user management using the Server Configuration Manager .......................................................... 33

4.3.3

Secure Authentication via SSHv2 ............................................................................................................. 33

4.3.3.1

Creating public and private SSHv2 keys .............................................................................................. 34

4.3.3.2

Uploading the public SSHv2 key .......................................................................................................... 36

4.3.3.3

Using the public SSHv2 key .................................................................................................................. 37

4.3.3.4

Example: Public SSHv2 key ................................................................................................................. 41

5 Remote installation of the operating system ......................................................................................................... 43

5.1

General procedure for installing the operating system ................................................................................... 43

5.2

Connecting a storage medium as Virtual Media .............................................................................................. 45

5.3

Booting the managed server .......................................................................................................................... 47

Contents

5.4

Installing Windows on the managed server .................................................................................................... 50

5.5

Installing Linux on the managed server ......................................................................................................... 51

6 Firmware update ................................................................................................................................................... 53

6.1

Firmware selector............................................................................................................................................ 54

6.2

Methods of firmware image update ................................................................................................................ 54

6.2.1

Firmware Update using the web interface ............................................................................................... 55

6.2.2

Firmware update using ServerView Update Manager .............................................................................. 56

6.2.3

Firmware update using ServerView Update Manager Express ................................................................. 56

6.3

Firmware image downgrade ........................................................................................................................... 57

1 Preface

1 Preface

The scalable PRIMEQUEST 3800B2/3800B is an Intel-based rack server for critical company scenarios, e.g. as database management system for medium or large-sized databases or as a consolidation basis to run an immensely large number of different applications using virtualization technologies.

Thanks to its highly developed hardware and software components, the server offers a high level of data security and availability. These include hot-plug HDD/SSD modules, hot-plug system fans, and also hot-plug power supply units, the Server Management ServerView Suite, Prefailure Detection and

Analysis (PDA) and Automatic Server Reconfiguration and Restart (ASR&R).

Security functions in the BIOS Setup and on the System Board protect the data on the server against manipulation. Additional security is provided by the lockable rack door.

The server occupies 5 height units (HU) in the rack.

1.1 Concept and target groups for this manual

This user guide is aimed at system administrators, network administrators, and service staff who have a sound knowledge of hardware and software. It provides basic information on the configuration of the iRMC and deals with the following aspects in detail: l

The Overview provides the basic facts of the iRMC’s functions. l

The First Steps provide information about the LAN connection and how to log on to the iRMC. l

User management explains the iRMC-related user management. l

Remote installation describes how to install the operating system via iRMC. l

Firmware update describes the firmware update of the iRMC. iRMC S5 - Configuration and Maintenance 5

1.2 Documentation overview

1.2 Documentation overview

More information on your PRIMEQUEST 3800B2/3800B can be found in the following documents:

– FUJITSU Server PRIMEQUEST 3000 Series Business Model iRMC S5 Concepts and Interface

– FUJITSU Server PRIMEQUEST 3000 Series Business Model iRMC S5 Web Interface

– FUJITSU Server PRIMEQUEST 3000 Series Business Model iRMC S5 Configuration and Maintenance

– FUJITSU Server PRIMEQUEST 3000 Series iRMC S5 RESTful API

– FUJITSU Server PRIMEQUEST 3000 Series Business Model Operating Manual

– FUJITSU Server PRIMEQUEST 3000 Series Business Model BIOS Setup Utility Reference Manual

All documentation on PRIMEQUEST hardware and ServerView software is available online from the Fujitsu manuals server at:

–

For the global market http://manuals.ts.fujitsu.com

The complete PRIMEQUEST documentation set can also be downloaded as a DVD ISO image at:

–

For the global market: ftp://ftp.ts.fujitsu.com/images/serverview/manuals

Further sources of information:

– ServerView Suite Glossary

– Manual for the monitor

– Documentation for the boards and drives

– Operating system documentation

– Information files in your operating system iRMC S5 - Configuration and Maintenance 6

1.3 Typographic conventions

1.3 Typographic conventions

The following typographic conventions are used:

Convention Explanation

Various types of risk, namely health risks, risk of data loss and risk of damage to devices.

Additional relevant information and tips. bold References to names of interface elements. monospace

System output and system elements, e.g., file names and paths inside

Text blocks. monospace

Commands, system output, syntax and statements that are to be entered using the keyboard outside Text blocks. monospace semibold

Process example for statements that are to be entered using the keyboard. blue continuous A link to a related topic. text purple continuous text

A link to a location you have already visited.

<abc>

[abc]

Variables which must be replaced with real values.

Options that can be specified (syntax).

[Key] Key on your keyboard. If you need to enter text in uppercase, the Shift key is specified, e.g., [Shift] + [A] for an A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols.

Quotation marks For names of chapters and manuals.

Table 1: Typographic conventions

Screenshots

Some of the screenshots are system-dependent, so some of the details shown may differ from your system. There may also be system-specific differences in menu options and commands. iRMC S5 - Configuration and Maintenance 7

2.1 Standard functions

2 Overview of the iRMC functions

The iRMC supports a wide range of functions that are provided by default. With Embedded

Lifecycle Management, the iRMC also provides additional advanced features for the remote management of PRIMEQUEST servers.

2.1 Standard functions

No special license key is needed for the standard functions.

Alert management

The alert management facility of the iRMC provides the following options for forwarding alerts: l

Platform Event Traps (PET) are sent via SNMP. l

Direct alerting by E-mail.

The iRMC also provides the ServerView Agents with all the relevant information.

Basic functions of a BMC

The iRMC supports the basic functions of a BMC, such as voltage monitoring, event logging and recovery control.

Browser access

The iRMC features its own web server, which can be accessed by the management station from a standard web browser.

CAS-based single sign-on (SSO) authentication

The iRMC supports Centralized Authentication Service (CAS) configuration, which allows you to configure the iRMC web interface for CAS-based SSO authentication.

The first time a user logs on to an application (e.g. the iRMC web interface) within the SSO domain of the CAS service, they are prompted for their credentials by the CAS-specific login screen. iRMC S5 - Configuration and Maintenance 8

2.1 Standard functions

Once they have been successfully authenticated by the CAS service, the user is granted access to the iRMC web interface as well as to any other service within the SSO domain without being prompted for login credentials again.

Customer Self Service (CSS)

You can replace several of the system's hardware components on your own. These components are marked in the iRMC S5 web interface and this information is also provided in ServerView Operations Manager.

In addition, the error list of the system event log (SEL) shows whether each event has been triggered by a CSS component.

DNS / DHCP

The iRMC provides support for automatic network configuration. It has a default name and

DHCP support is set by default so that the iRMC gets its IP address from the DHCP server.

The iRMC name is registered by the Domain Name System (DNS). Up to three DNS servers are supported. If DNS/DHCP is not available, the iRMC also supports static IP addresses.

Global error LED

A global error LED indicates the status of the managed server at all times.

Global user management using a directory service

The global user IDs for the iRMC are stored centrally in the directory of the directory service. This allows the user identifications to be managed on a central server. They can therefore be used by all the iRMCs that are connected to this server in the network. iRMC S5 - Configuration and Maintenance 9

2.1 Standard functions

The following directory services are currently supported for iRMC user management: l

Microsoft® Active Directory l

Novell® eDirectory l

OpenLDAP l

OpenDS, Open DJ, Apache DS

“Headless” system operation

The managed server does not require a mouse, monitor or keyboard to be connected. The benefits of this include lower costs, much simpler cabling in the rack and increased security.

Identification LED

To facilitate identification of the system, for instance if it is installed in a fully populated rack, you can activate the identification LED via the iRMC web interface.

LAN

On some systems, the LAN interface of the fitted system NIC (Network Interface Card) on the server is reserved for the management LAN. On other systems, you have the option of configuring this LAN interface to: l

Reserve it for the management LAN l

Set it up for shared operation with the system l

Make it completely available to the system

The ports marked with a wrench symbol are assigned to the iRMC.

LAN over USB

An interface called LAN over USB enables in-band communication between the managed server and the iRMC. This communication provides an additional interface from the managed server to the iRMC, e.g. to use the Redfish interface or access via SSH. It also avoids a shortcut between the management LAN and the productive LAN for e.g. Redfish access from managed server to iRMC. For more information, see the "iRMC S5 - Concepts and Interfaces" manual. iRMC S5 - Configuration and Maintenance 10

2.1 Standard functions

Local user management

The iRMC has its own user management function which allows up to 16 users to be created with passwords and assigned various rights depending on the user groups they belong to.

Network bonding

Network bonding for the iRMC is designed for redundancy in the event of Ethernet network adapter failures. Thus, iRMC network management traffic is protected from loss of service due to failure of a single physical link.

The iRMC supports active-backup mode, i.e. one port is active until the link fails, then the other port takes over the MAC and becomes active.

Power consumption control

The iRMC allows comprehensive control of power consumption on the managed server. You can also specify the mode the iRMC uses to control power consumption on the managed server. You can switch between these modes as required.

Power LED

The power LED tells you whether the server is currently switched on or off and allows several power operations depending on the current power state if either ServerView Agents or Agentless

Service are installed and running.

Power management

Irrespective of the status of the system, you have the following options for powering the managed server on or off from the remote workstation: l

Using the iRMC web interface l

Using the Power menu of the AVR window l

Using the Remote Manager l

With a script

Read, filter and save the system event log (SEL)

You can view, save and delete the contents of the SEL using a choice of interfaces: l

The iRMC web interface l

The Telnet/SSH-based interface (Remote Manager) of the iRMC

Read, filter and save the internal event log (iEL)

You can view, save and delete the contents of the iEL using a choice of interfaces: l

The iRMC web interface l

The Telnet/SSH-based interface (Remote Manager) of the iRMC

Security (TLS, SSH)

Secure access to the web server and secure graphical console redirection, including mouse and keyboard, is provided via HTTPS. An encrypted connection protected by SSH mechanisms can be set up to access the iRMC using the Remote Manager. The Remote

Manager is a text-based user interface of the iRMC. iRMC S5 - Configuration and Maintenance 11

2.1 Standard functions

ServerView integration

The ServerView Agents detect the iRMC and automatically assign it to the relevant server.

Communication between the iRMC and the ServerView Agentless Service (as of ServerView

Operations Manager 7.0) allows for enhanced out-of-band management of PRIMEQUEST servers.

Simple configuration - interactive or script-based

The following tools are available for configuring the iRMC: l iRMC web interface l

Profile Management l

Remote Manager l

RESTful API l

Server Configuration Manager l

UEFI BIOS Setup

It is also possible to perform configuration with the Server Configuration Manager or

IPMIVIEW using scripts. This means you can configure the iRMC when the server is first configured via ServerView Installation Manager. You can also configure a large number of servers on the basis of scripts and profile management.

SNMPv1/v2c/v3 support

You can configure an SNMP service on the iRMC which supports SNMPv1/v2c/v3 GET requests on SNMP SC2 MIB (Sc2.mib), SNMP MIB-2, SNMP OS.MIB, SNMP RAID.MIB and

SNMP STATUS.MIB.

When the SNMP service is enabled, information on devices such as fans, temperature sensors etc. is available via the SNMP protocol and can be viewed on any system running an SNMP Manager.

Furthermore SNMP traps can be sent to the recipient specified in the destination configuration of the trap. For more information, see the "iRMC S5 - Concepts and

Interfaces" manual.

Text console redirection

You can establish a Telnet/SSH session to the iRMC using a Telnet/SSH client to access the text based Remote Manager. The Remote Manager offers a restricted menu-based access to the iRMC. Besides Telnet there is support for SOL (serial over LAN) and SSH (Secure Shell).

UEFI support

Unified Extensible Firmware Interface (UEFI) is a specification for a software program that connects a computer's firmware to its operating system. UEFI has a firmware validation process, called secure boot. Secure boot defines how platform firmware manages security certificates, validation of firmware, and a definition of the interface (protocol) between firmware and the operating system. iRMC S5 - Configuration and Maintenance 12

2.1 Standard functions

VMware HCL support

During update preparation of a managed server with VMware ESXi operating system, inventory data is compared with the HCL file, which is downloaded from the update repository. This list is based on the information about certified server configuration published by VMware. The comparison results in the following actions: l

There are no entries for the component: the newest version is added to the update list l

There are entries for a component: the most recent certified version is added to the update list

You can skip the VMware HCL verification in the Update settings. This setting only affects systems with ESXi and ServerView CIM providers installed.

Advanced Video Redirection (AVR)

The iRMC supports Advanced Video Redirection via HTML5 or Java. AVR offers the following benefits: l

Operation via a standard web browser. No additional software needs to be installed on the management station other than a Java Runtime Environment if the Java applet is used. Otherwise the web browser must be able to interpret HTML5. l

System-independent graphical and text console redirection (including mouse and keyboard). l

Remote access for boot monitoring, BIOS administration and operation of the operating system. l

AVR supports up to two simultaneous “virtual connections” for working on a server from a different location. It also reduces the load on the network by using hardware video compression. l

Local monitor-off support: It is possible to power down the local screen of the managed

PRIMEQUEST server during an AVR session in order to prevent unauthorized persons from observing user input and actions carried out on the local server screen during the

AVR session. l

Low bandwidth

If the data transfer rate is slow, you can configure a lower bandwidth (bits per pixel, bpp) in terms of color depth for your current AVR session.

Virtual Media

The Virtual Media function makes a “virtual” drive available which is located on a remote workstation or made available centrally on the network using the Remote Image Mount functionality.

The virtual drives available with Virtual Media are simply managed in much the same way as local drives and offer the following options: l

Read and write data l

Boot from Virtual Media l

Install drivers and small applications l

Update BIOS from remote workstation l

(BIOS update via USB) iRMC S5 - Configuration and Maintenance 13

2.1 Standard functions

Virtual Media supports the following device types to provide a virtual drive on the remote workstation: l

CD/DVD drive l

CD/DVD image l

HDD/USB physical and logical drive (Internet Explorer / Firefox needs to be run as

Administrator on Windows) l

HDD/USB image l

Shared folder used via the Virtual Media wizard

The Remote Image Mount function provides images centrally on a network share in the form of a virtual drive. iRMC S5 - Configuration and Maintenance 14

2.2 Extended functions

2.2 Extended functions

Alongside the standard functions, the iRMC also supports embedded Lifecycle Management

(eLCM). These extended functions require a valid license key, which can be purchased separately.

Embedded Lifecycle Management (eLCM)

The embedded Lifecycle Management (eLCM) solution allows you to control lifecycle management of PRIMEQUEST servers with a few mouse clicks centrally from the iRMC web interface without the need to handle physical devices. eLCM comprises the following functions: l eLCM update management l eLCM image management (Custom Image) l eLCM offline update l eLCM online update l eLCM custom image l eLCM health management (PrimeCollect)

For more information, see the "ServerView embedded Lifecycle Management (eLCM)" user guide. iRMC S5 - Configuration and Maintenance 15

2.3 Embedded Lifecycle Management

2.3 Embedded Lifecycle Management

ServerView embedded Lifecycle Management (eLCM) for Fujitsu PRIMEQUEST server supports general routine management tasks. System administrators benefit from simplified, highly integrated and automated server management processes.

The eLCM enhances ServerView functions directly available (embedded) within the server without the need for external media like USB, CD or DVD. Users have access to the following embedded ServerView functions: l

The embedded Installation Management (eIM) is the eLCM equivalent of the

ServerView Installation Manager. The eIM and the repository are stored on the iRMC internal SD card, so no external ServerView media needs to be set up to install Fujitsu

PRIMEQUEST servers. l

The embedded RAID Management (eRM) serves as the eLCM equivalent of the

ServerView RAID Manager and supplements the eIM with respect to RAID management. l

The embedded offline and online update is the eLCM edition of the ServerView Update

Manager modules. The online update allows you to update BIOS and controller firmware while the server operating system is running. The offline update allows you to update system components like network or storage controller firmware on the managed server. l

The embedded custom image allows you to specify a URL from which you can download ISO images onto the iRMC internal SD card. l eLCM PrimeCollect collects and stores detailed information about the hardware and software of Fujitsu PRIMEQUEST servers, including error information in the case of server malfunction. The collected information is stored in a ZIP file on the iRMC internal SD card.

The iRMC handles all eLCM-related network traffic exclusively via its dedicated management LAN port. None of the system LAN ports used by the server operating system are involved. Limiting any management-related traffic to the management LAN relieves the productive LAN and also helps to avoid security threats. eLCM bypasses the traditional server management, which requires agents and management software running on the server operating system. Shifting the management software to the iRMC improves the performance of the managed server.

The only software that eLCM in some cases needs to be running on the server's OS is the

ServerView Agentless Service component. Exclusively communicating with the iRMC S5 over

HTI (High-Speed Transfer Interface), the Agentless Service has only a very small footprint on the server operating system, with negligible impact on the system's overall performance.

The ServerView Service Platform (SV SP) is used within embedded Lifecycle Management.

It is an ISO image that is stored inside PRIMEQUEST servers on an optional iRMC internal

SD card and is managed by eLCM. iRMC S5 - Configuration and Maintenance 16

2.3 Embedded Lifecycle Management

Different operation scenarios are supported for these functions:

Interactive operation via console (physical or redirected)

Power-on the target system.

During POST (Power-On-Self-Test) press [F5].

In the opened eLCM menu select the function to be used: l

System configuration and installation l

RAID configuration

Once the platform has started follow the instructions displayed on the console.

Unattended operation via the iRMC web interface

Create a profile file specifying the intended system configuration and/or operating system installation. Profile handling is described in the "iRMC S5 - Concepts and

Interfaces" user guide.

Start the iRMC web interface and open the Deployment page.

Set the intended boot mode either to Extensible Firmware Interface Boot (EFI) or PC compatible (legacy).

Upload the profile file.

Start the deployment process with Activate .

Unattended process “SysRollOut Service” via REST API

For more information, see the REST API white paper. iRMC S5 - Configuration and Maintenance 17

2.4 User interfaces

2.4 User interfaces

The iRMC provides the following user interfaces: l iRMC web interface (web interface)

The connection to the iRMC web server is established via a standard web browser (e.g.

Microsoft Edge, Microsoft Internet Explorer 11, Mozilla Firefox, Google Chrome).

Among other things, the web interface of the iRMC provides access to all system information and data from the sensors such as fan speeds, voltages, etc. You can also configure text-based console redirection and start graphical console redirection

(Advanced Video Redirection, AVR). In addition, administrators can fully configure the iRMC using the web interface.

Secure access to the iRMC web server is provided with HTTPS. The web interface supports only HTTPS connections. HTTP links are redirected to HTTPS ensuring secure access.

Operation of the iRMC using the web interface is described in the "iRMC S5 - Web

Interface" user guide. l

Remote Manager : Text-based Telnet/SSH interface via LAN

You can call the Remote Manager directly from a Telnet/SSH client.

The text-based user interface of the Remote Manager provides you with access to system and sensor information, power management functions and the error event log.

You can also launch text console redirection. If you call the Remote Manager over SSH

(Secure Shell), the connection between the Remote Manager and the managed server is encrypted.

Operation of the iRMC using the Remote Manager is described in the "iRMC S5 -

Concepts and Interfaces" user guide. iRMC S5 - Configuration and Maintenance 18

2.5 Application programming interfaces

2.5 Application programming interfaces

The iRMC S5 supports APIs (Application Programming Interface) for scripted configuration.

With scripting only one iRMC has to be configured according to the requirements of the environment. This configuration is then uploaded to all other PRIMEQUEST servers without the need to access them all one by one. l

Redfish

Redfish is a DMTF standard specification and schema that specifies a RESTful interface.

It utilizes a range of IT technologies that have been selected because of their widespread use. These technologies create a new foundation from which servers can be managed using common programming and scripting languages, such as Python, Java and C. l

RESTful

Representational state transfer is a way to provide interoperability between computer systems on the internet. REST-compliant web services allow requesting systems to access and manipulate textual representations of web resources using a uniform and predefined set of stateless operations. l

SCCI

The Server Control Command Interface is a generic API defined by Fujitsu for different server management controller hardware as well as software. It can be easily extended to new commands or new configuration items.

For more information, see the "iRMC S5 Concepts and Interfaces" user guide. iRMC S5 - Configuration and Maintenance 19

2.6 Communication protocols used

2.6 Communication protocols used

The iRMC uses the following protocols and ports for communication:

Remote side of the connection

Communication direction iRMC side of the connection

(port no. / protocol)

Configurable Enabled by default

CAS / Single Sign-On

E-mail/SMTP

HTTPS

LDAP

Redfish

REST

RMCP

SNMP

SNMP trap

SSDP

SSH

Telnet

TFTP /repository

↔

3170/TCP

25/TCP

443/TCP

389/TCP/UDP

443/TCP

80/TCP

623/UDP

161/UDP

162/UDP

1900/UDP

22/TCP

3172/TCP

69/UDP yes no yes yes yes no yes yes yes yes yes yes no no yes yes yes no no yes no yes no yes yes yes iRMC S5 - Configuration and Maintenance 20

2.7 Front panel LEDs controlled by the iRMC

2.7 Front panel LEDs controlled by the iRMC

The iRMC controls the status LEDs which are located on the front panel of the server.

Status LEDs on the front panel:

Status of the Server

AC-OFF

S5 (shutdown)

S0 (power on) iRMC not readyON

Power-on Delay

S5 LED (green) off on off on on

LED on the Server

Power LED (green) off off on flashing with 0.5 Hz (iRMC-controlled) on iRMC S5 - Configuration and Maintenance 21

3 First Steps

The first steps for working with the iRMC are as follows: l

Establish a LAN connection. l

3.1 Configuration of the LAN interface

You configure the LAN interface for out-of-band communication with the UEFI setup utility.

Before you configure the LAN interface, there are some requirements to be met.

After configuration you must test the LAN interface.

3 First Steps

"Spanning Tree" tree for the connection of the iRMC must be deactivated (e.g. Port

Fast=enabled; Fast Forwarding=enabled).

You can also configure in-band communication via LAN over USB. For more information, see the "iRMC S5 Concepts and Interfaces" user guide.

3.1.1 Requirements

Before you configure the LAN interface of the iRMC the following requirements must be met:

The LAN cable must be connected to the correct port.

The interface for a LAN connection is provided on an on-board LAN controller assigned to the iRMC.

Depending on the server type, the system board of a PRIMEQUEST server provides two LAN interfaces. The ports marked with a wrench symbol are assigned to the iRMC.

Figure 1: Ports for the iRMC (indicated by wrench symbol) iRMC S5 - Configuration and Maintenance 22

3.1 Configuration of the LAN

Icon Meaning

DedicatedService/Management LAN (port exclusively for the iRMC; with the iRMC a

LAN speed up to 1000 MBit/s is available)

Shared LAN (iRMC and system)

LAN speed setting is only available on system.

Two IP addresses are required

The LAN controller of the PRIMEQUEST server requires a separate IP address for the iRMC in order to ensure that data packets are reliably transferred to the iRMC (and not to the operating system).

The IP address of the iRMC must be different from that of the system (operating system).

A gateway is configured for access from a different subnet

If the remote workstation accesses the iRMC of the managed server from a different subnet and DHCP is not used, you must configure the gateway.

3.1.2 Configuring the LAN interface using UEFI

You can configure the iRMC’s LAN interface using the UEFI setup utility:

Call the UEFI setup utility of the managed server. Do this by pressing [F2] while the server is booting.

Open the iRMC LAN parameter configuration menu:

Management – iRMC LAN Parameters Configuration iRMC S5 - Configuration and Maintenance 23

3.1 Configuration of the LAN

Figure 2: iRMC LAN Parameters Configuration Menu

In the Management LAN field, enter Enabled .

In the Management LAN Port field, enter Management .

For more information on configuring the remaining settings, see the "iRMC S5 -

Web Interface" user guide and/or see the "Reference Manual (BIOS Setup

Utility)".

Save the settings.

If you want to use console redirection on the iRMC, continue with configuring text console redirection, see the section "Configuring text console redirection for the iRMC

S5" in the "iRMC S5 - Concepts and Interfaces" user guide.

If you do not want to use text console redirection on the iRMC, exit the UEFI setup and

continue with testing the LAN interface ( "Testing the LAN interface" on page 25 ).

iRMC S5 - Configuration and Maintenance 24

3.2 Logging in to the iRMC S5 for the first time

3.1.3 Testing the LAN interface

You can test the LAN interface as follows:

Use a web browser to attempt to log in to the iRMC web interface. If no login prompt appears, it is probable that the LAN interface is not working.

Test the connection to the iRMC with the ping command.

3.2 Logging in to the iRMC S5 for the first time

The factory default settings of the iRMC allow you to log in to the iRMC for the first time without the need for any configuration activities.

3.2.1 Requirements

The following requirements must be met for a working connection:

On the remote workstation: l

Windows: Microsoft Edge, Microsoft Internet Explorer 11 or Google Chrome as of version 50 l

Linux: Mozilla Firefox as of version 50 l

For Video Redirection: either Java Virtual Machine or a web browser

For more information on Video Redirection, see the "Start-up procedure and validation information of Video Redirection" on the Fujitsu manual server .

In your network: l

If you do not use static IP addresses there must be a DHCP server in your network. l

If you want to log in with a symbolic name rather than an IP address on the iRMC web interface, the DHCP server in your network must be configured for dynamic DNS. l

DNS must be configured. Otherwise you must ask for the IP address.

If you use Microsoft Edge or Microsoft Internet Explorer 11 within an IPv6 network with HTTPS, it is recommended to provide the iRMC web interface with an IPv6 address in literal format instead of the standard format. E.g. use

2001-0db8-

85a3-0000-0000- 8a2e-0370-7334.ipv6-literal.net instead of http:// [2001:0db8:85a3:0000:0000:8a2e:0370:7334]

. iRMC S5 - Configuration and Maintenance 25

3.2 Logging in to the iRMC S5 for the first time

3.2.2 iRMC factory defaults

The firmware of the iRMC provides a default administrator ID and a default DHCP name for the iRMC.

Default administrator ID

Both the administrator ID and the password are case-sensitive.

Administrator ID admin

Password admin

For security reasons, it is recommended that you create a new administrator account once you have logged in, and then delete the default one. At least change the password for

the administrator account ( "User management" on page 28 ).

Default DHCP name of the iRMC

The default DHCP name of the iRMC uses the following pattern:

IRMC<SerialNumber>

The serial number corresponds to the last three bytes of the MAC address of the iRMC. You can read off the MAC address of the iRMC from the label on your PRIMEQUEST server.

After you have logged in, the MAC address of the iRMC can be found as a read-only field in the Network Interface group of the Network Management page in the Settings menu.

3.2.3 Logging in

Open a web browser on the remote workstation.

Enter the (configured) DNS name or IP address of the iRMC. e.g.

<IP address> or

IRMC<SerialNumber>

You can read off the DNS name of the iRMC from the label on your PRIMEQUEST server.

A login dialog box opens. iRMC S5 - Configuration and Maintenance 26

3.2 Logging in to the iRMC S5 for the first time

Figure 3: Login dialog box of the iRMC web interface

If no login dialog box opens, check the LAN connection.

If you use Microsoft Internet Explorer, On the Tools menu of Internet Explorer, click Compatibility View Settings. Click to uncheck the Display intranet sites in

Compatibility View check box in Compatibility View Settings dialog.

Enter the data for the default administrator account.

Username: admin

Password: admin

Both the Username and the Password are case-sensitive.

Click Login to confirm your entries.

The iRMC web interface opens with the System Overview page.

For security reasons, it is recommended that you create a new administrator account once you have logged in, and then delete the default one. At least change the password for

the administrator account ( "User management" on page 28 ).

3.2.4 Logging out

Logout allows you to terminate the iRMC session.

In the title bar open the <User> menu.

Click logout .

The user is logged out and the login dialog box opens again. This allows you to log in again if required. iRMC S5 - Configuration and Maintenance 27

4 User management

4 User management

User management for the iRMC uses two different types of user identifications: l

Local user identifications are stored locally in the iRMC’s non-volatile storage and are managed via the iRMC user interfaces. l

Global user identifications are stored in the central data store of a directory service and are managed via this directory service’s interfaces.

The following directory services are currently supported for global iRMC S5 user management: l

Microsoft® Active Directory l

Novell® eDirectory l

OpenLDAP l

OpenDJ

For more information on global user management using the individual directory services, see the "User Management in ServerView" user guide.

4.1 User management concept

User management for the iRMC allows the parallel administration of local and global user identifications.

When validating the authentication data (user name, password) which users enter when logging in to one of the iRMC interfaces, the iRMC proceeds as follows:

The iRMC compares the user name and password with the locally stored user identifications.

If the user is authenticated successfully (user name and password are valid) they can log in. l

Otherwise, the iRMC continues the verification with the next step.

The iRMC authenticates itself to the directory service via LDAP with a user name and password.

Depending on its LDAP configuration settings, the iRMC continues as follows: l

If ServerView-specific LDAP groups with authorization settings in the SVS structure on the LDAP server are used, the iRMC determines the user’s permissions by using an LDAP query and checks whether the user is authorized to work on the iRMC. iRMC S5 - Configuration and Maintenance 28

4.1 User management concept

Characteristics: o

Extension of the directory server structure required. o

Privileges/permissions are configured centrally on the directory server. l

If LDAP-standard groups are used with authorization settings deposited locally on the iRMC, the iRMC proceeds as follows:

The iRMC uses an LDAP query to determine which standard LDAP group on the directory server the user belongs to.

The iRMC checks whether a user group with this name is also configured locally on the iRMC. If so, the iRMC determines the user’s permissions by means of this local group.

Characteristics: o o

No extension of the directory server structure required.

Privileges/permissions are configured separately on each iRMC. iRMC S5 - Configuration and Maintenance 29

4.1 User management concept

Figure 4: Login authentication via the iRMC S5

The use of HTTPS for the LDAP connection between the iRMC and the directory service is recommended. An HTTPS-secured LDAP connection between iRMC and directory service guarantees secure data exchange, and in particular secure transfer of the user name and password data. iRMC S5 - Configuration and Maintenance 30

4.2 User permissions

4.2 User permissions

The iRMC distinguishes between two mutually complementary types of user permissions:

Channel-specific privileges (via assignment to channel-specific permission groups)

The iRMC assigns each user identification to one of the following four channel-specific permission groups: l

User l

Operator l

Administrator l

OEM

Since the iRMC assigns these permissions on a channel-specific basis, users can have different permissions, depending on whether they access the iRMC over the LAN interface or the serial interface.

The scope of permissions granted increases from User (lowest permission level) through

Operator and Administrator up to OEM (highest permission level).

The permission groups correspond to the IPMI privilege level. Certain permissions (e.g. for

Power Management) are associated with these groups or privilege levels.

Adding the iRMC to the ServerView Operations Manager server list requires LAN channel privilege Administrator or OEM (for more information, see the "ServerView Operations

Manager" user guide).

Permissions to use special iRMC functions

As well as the channel-specific permissions, you can also individually assign users the following permissions:

Permission

Configure User

Accounts

Configure iRMC

Settings

Video Redirection

Enabled

Remote Storage

Enabled

Meaning

Permission to configure local user identifications

Permission to configure the iRMC settings

Permission to use Advanced Video Redirection (AVR) in “View Only” and “Full Control” mode

Permission to use the Virtual Media function

The privileges and permissions required for the use of the individual iRMC functions are described: l

For the iRMC web interface in the "iRMC S5 - Web Interface" user guide l

For the Remote Manager in the "iRMC S5 - Concepts and Interfaces" user guide iRMC S5 - Configuration and Maintenance 31

4.3 Local user management

4.3 Local user management

The iRMC has its own local user management. Up to 16 users can be configured with passwords and assigned various rights depending on the user groups they belong to. The user identifications are stored in the local, non-volatile storage of the iRMC S5.

The following options are available for user management on the iRMC: l

User management via the web interface ( "Local user management using the iRMC web interface" on page 32 )

User management via the Server Configuration Manager ( "Local user management using the Server Configuration Manager" on page 33 )

The iRMC also supports SSHv2-based public key authentication using pairs of public and

private keys for local users ( "Secure Authentication via SSHv2" on page 33 ).

4.3.1 Local user management using the iRMC web interface

The web interface provides a list of configured iRMC users. You can also configure new users, change the configuration of existing ones and remove users from the list.

User management on the iRMC requires Configure User Accounts permission.

Showing the list of configured users

A list of already configured users is displayed in the iRMC Local User Accounts group on the

User Management page in the Settings menu.

In this list you can delete users and open a dialog box for configuring new ones.

Configuring new users

You can configure a new user with the Add button below the list of configured users.

In the Add Local User Account dialog box you configure the basic settings for the new user.

Modifying the configuration of a user

You can modify the settings of a user account with the Edit button next to the relevant user in the list of configured users.

In the Edit Local User Account dialog box you can change the settings for an existing user.

Deleting users

You delete a user account with the Delete button next to the relevant user in the list of configured users.

For more information on the User Management page of the iRMC web interface, see the

"iRMC S5 - Web Interface" user guide. iRMC S5 - Configuration and Maintenance 32

4.3 Local user management

4.3.2 Local user management using the Server Configuration Manager

User management via the Server Configuration Manager largely conforms to user management using the iRMC web interface.

User management on the iRMC requires Configure User Accounts permission.

Requirement : The current ServerView agents must be installed on the managed server.

For how to start the Server Configuration Manager, see the "iRMC S5 - Web Interface" user guide.

For more information on the individual Configuration Manager dialogs, see the Server

Configuration Manager online help.

4.3.3 Secure Authentication via SSHv2

As well as authentication by means of a user name and password, the iRMC also supports

SSHv2-based public key authentication using pairs of public and private keys for local users. To implement SSHv2 public key authentication, the SSHv2 key of an iRMC user is uploaded to the iRMC. The iRMC user uses their private key with the program PuTTY or the

OpenSSH client program ssh, for example.

The iRMC supports the SSH RSA public key. The public SSHv2 keys that you upload to the

iRMC can be available either in RFC4716 format or in OpenSSH format ( "Example: Public

SSHv2 key" on page 41 ).

Public key authentication

Basically, public key authentication of a user on the iRMC happens as follows: The user who wishes to log in to the iRMC creates the key pair: l

The private key is read-protected and remains on the user's computer. l

The user (or administrator) uploads the public key to the iRMC.

If the configuration allows this, the user can now securely log in to the iRMC without needing to enter a password. The user is only responsible for keeping their private key secret.

The following steps are necessary to set up private key authentication. They are described in the subsequent sections:

Create the public and private SSHv2 keys with the program PuTTYgen or ssh-keygen

and save them in separate files ( "Creating public and private SSHv2 keys" on page

34 ).

Upload the public SSHv2 key onto the iRMC from a file ( "Uploading the public SSHv2 key" on page 36 ).

Configure the program PuTTY or ssh for SSHv2 access to the iRMC ( "Using the public

SSHv2 key" on page 37 ).

iRMC S5 - Configuration and Maintenance 33

4.3.3.1 Creating public and private SSHv2 keys

You can create public and private SSHv2 keys.

Using the PuTTYgen program

Start PuTTYgen on your Windows computer.

The PuTTYgen main window opens.

4.3 Local user management

Figure 5: PuTTYgen: Creating new private and public SSHv2 keys

In the Parameters group, select the RSA key type.

Click Generate to start generation of the keys.

A progress bar indicates the progress of the generation.

Move the mouse pointer over the progress bar to increase the randomness of the generated keys.

When the keys have been generated, PuTTYgen displays the key and the fingerprint of the public SSHv2 key. iRMC S5 - Configuration and Maintenance 34

4.3 Local user management

Figure 6: PuTTYgen: Generated private SSHv2 key

Click Save public key to save the public SSHv2 key to a file. You can upload the public

key to the iRMC from this file ( "Uploading the public SSHv2 key" on page 36 ).

Click Save private key to save the private SSHv2 key to a file for use with PuTTY.

Using the OpenSSH client program ssh-keygen

If it is not already pre-installed in the Linux distribution you are using, you can obtain

OpenSSH from https://www.openssh.com

You will find a detailed description of the parameters on the OpenSSH manual pages at https://www.openssh.com/manual.html

Proceed as follows:

Open a command window.

Call ssh-keygen to generate an RSA key pair: ssh-keygen -t rsa ssh-keygen logs the progress of the key generation operation. ssh-keygen prompts the user for the file name under which the private key is to be stored and the passphrase for the private key. ssh-keygen stores the resulting private and public SSHv2 keys in separate files and displays the fingerprint of the public key. iRMC S5 - Configuration and Maintenance 35

Example: Generating an RSA key pair with ssh-keygen

4.3 Local user management

Explanation:

ssh-keygen requests the file name in which the SSHv2 key is to be saved. If you press

[Enter] to confirm without entering a file name, ssh-keygen uses the default file name id_rsa.

ssh-keygen prompts you to enter a passphrase (and confirm it) that is used to encrypt the private key. If you press [Enter] to confirm without entering a passphrase, sshkeygen does not use one.

ssh-keygen informs the user that the newly generated private SSHv2 key has been saved in the file

/.ssh/id_rsa

ssh-keygen informs the user that the newly generated public SSHv2 key has been saved in the file

/.ssh/id_rsa.pub

ssh-keygen displays the fingerprint of the public SSHv2 key and the local login to which the public key belongs.

4.3.3.2 Uploading the public SSHv2 key

To upload the public SSHv2 key onto the iRMC from a file, proceed as follows:

Open the User Management page in the Settings menu.

In the list of configured users click Edit next to the relevant user.

In the Edit Local User Account dialog box, open the Certificates tab.

Open the SSHv2public Key subtab.

Click Select in the Upload group and navigate to the file containing the required public key.

Click Upload to load the public key onto the iRMC.

After the key has been successfully uploaded, the iRMC displays the key fingerprint in the Fingerprint field. iRMC S5 - Configuration and Maintenance 36

4.3 Local user management

Figure 7: Display of the key fingerprint

For security reasons, make ensure that the fingerprint shown here matches that shown in

PuTTYgen ( "Creating public and private SSHv2 keys" on page 34 ) in the

Key fingerprint field.

4.3.3.3 Using the public SSHv2 key

To use the public SSHv2 key you need to configure an appropriate tool:

Configuring PuTTY for using the public SSHv2 key

The PuTTY program allows you to set up a public-key-authenticated connection to the iRMC and log in either with your user name or using the auto-login mechanism. PuTTY handles the authentication protocol automatically on the basis of the public/private SSHv2 key pair previously generated.

Proceed as follows:

Start PuTTY on your Windows computer.

The PuTTY main window opens. iRMC S5 - Configuration and Maintenance 37

4.3 Local user management

Figure 8: Selecting and loading an SSH session

In the Saved Sessions list, select an SSH session with the iRMC S5 for which you want to use the SSHv2 key. You can also create a new session.

Click Load to load the parameters of the selected SSH session.

In the Category tree select SSH/Auth to configure the SSH authentication options.

The Authentication parameters are displayed. iRMC S5 - Configuration and Maintenance 38

4.3 Local user management

Figure 9: Configuring the SSH authentication options

Select the file containing the private key that you want to use with the iRMC S5.

At this point, you require the private key ( "Creating public and private SSHv2 keys" on page 34 ) and not the public key that you uploaded onto the iRMC.

In the Category tree, select Connection/Data to additionally specify a user name for automatic login on the iRMC. iRMC S5 - Configuration and Maintenance 39

4.3 Local user management

Figure 10: PuTTY: Specifying the user name for automatically logging in to the iRMC

Configuring the OpenSSH client program ssh for using the public SSHv2 key

You establish an SSHv2-protected connection to the iRMC using the OpenSSH client program ssh. You can log in under either your current local login or a different login.

The login must have been configured as a local login on the iRMC and the associated

SSHv2 key must have been loaded onto the iRMC S5. ssh reads its configuration options from the sources in the following order: l

Command line arguments that you specify when calling ssh. l

User-specific configuration file (

$HOME/.ssh/config

)

Although this file contains no security-critical information, read/write permission should only be granted to the owner. Access should be denied to all other users. l

System-wide configuration file (

/etc/ssh/ssh_config

)

This file contains default values for configuration parameters: l

If there is no user-specific configuration file l

If the relevant parameters are not specified in the user-specific configuration file iRMC S5 - Configuration and Maintenance 40

4.3 Local user management

The value found first applies for each option.

You will find detailed information on the configuration of ssh and its parameters on the manual pages for OpenSSH at: http://www.openssh.com/manual.html

Proceed as follows:

Open a command window.

Start ssh, to log in to the iRMC under SSHv2-authentication: ssh -l [<user>] <iRMC_S5> or ssh [<user>@]<iRMC_S5>

<user>

User name under which you want to log in to the iRMC. If you do not specify <user>, ssh uses the user name under which you are logged in on your local computer.

<iRMC_S5> iRMC name or IP address of the iRMC you want to log into.

Example: SSHv2-authenticated login on the iRMC

For the following ssh- call, it is assumed that ssh-keygen has been used to generate a

public/private RSA key pair ( "Creating public and private SSHv2 keys" on page 34 ) and that

the public key

User1/.ssh/id_rsa.pub has been loaded onto the iRMC for an iRMC

user user4 ( "Uploading the public SSHv2 key" on page 36 ).

You can then log in from your local computer under $HOME/User1 as follows on the iRMC

"PQ3000B-iRMC" using the user name user4: ssh user4@PQ3000B-iRMC

4.3.3.4 Example: Public SSHv2 key

The following shows the same public SSHv2 key in different formats:

RFC4716 format

---- BEGIN SSH2 PUBLIC KEY ----

Comment: "rsa-key-20090401"

AAAAB3NzaC1yc2EAAAABJQAAAIBScBsgP9B74qNa9+w8Ccv3kDVVu2boKCGLv4 hx v6+AUFrF6sYdGey1QQ7MkwSeax3NmoZBkvkR9hNfZSqxkPCkd//LyUil9US5/9

JxjlhXUzlPPVzuBtPaRB7+bISTJVMUorNwrcN48b6AAoYBhKC4AOtOP1OGsfc+F pGJ2iw==

---- END SSH2 PUBLIC KEY ---- iRMC S5 - Configuration and Maintenance 41

4.3 Local user management

OpenSSH format ssh-rsa

AAAAB3NzaC1yc2EAAAABJQAAAIBScBsgP9B74qNa9+w8Ccv3kDVVu2boKCGLv4 hxv6+\

AUFrF6sYdGey1QQ7MkwSeax3NmoZBkvkR9hNfZSqxkPCkd//LyUil9US5/9ArJ xjlhXUzlPPVzuBtPaRB7+\ bISTJVMUorNwrcN48b6AAoYBhKC4AOtOP1OGwsfc+FpGJ2iw== rsa-key-

20090401 iRMC S5 - Configuration and Maintenance 42

5 Remote installation of the operating system

5 Remote installation of the operating system

You can use the ServerView Installation Manager (abbreviated to Installation Manager below) and the iRMC features "Advanced Video Redirection (AVR)" and "Virtual Media" to install the operating system on the managed server from the remote workstation.

This chapter discusses the following specific topics: l

General procedure for the remote installation of an operating system using storage media which are provided via the "Virtual Media" feature. In the following, such storage media are referred to as virtual storage media for short. l

Booting the managed server from the remote workstation using the ServerView Suite

DVD 1 (Windows and Linux). l

Installing Windows from the remote workstation after configuration on the managed server. l

Installing Linux from the remote workstation after configuration on the managed server. l

The description focuses primarily on the handling of the virtual storage media. It is assumed that readers are familiar with the Installation Manager function (for more information, see the "ServerView Installation Manager" user guide).

Requirements for the remote installation of the operating system via iRMC S5: l

The iRMC’s LAN interface must be configured ( "Configuring the LAN interface using

UEFI" on page 23 ).

5.1 General procedure for installing the operating system

The Installation Manager regards the remote installation of the operating system via iRMC as a local installation and configuration on the managed server. You perform installation from the remote workstation via the AVR window using virtual media.

The following steps are required in order to install and configure via the Installation

Manager:

Connect the virtual storage medium (DVD or Installation Manager boot image) from which you want to boot as a virtual storage medium.

Boot and configure the managed server via DVD or the Installation Manager boot image. iRMC S5 - Configuration and Maintenance 43

5.1 General procedure for installing the operating system

Use the Installation Manager on the remote workstation to install the operating system on the managed server.

You can still install and configure the operating system without the Installation Manager using the CD/DVDs for:

Windows

You can perform a remote installation of Windows via Virtual Media either using the

Installation Manager or exclusively using the Windows installation CD/DVDs. The two procedures correspond in terms of the handling the virtual storage media.

However, you are advised to install Windows via the Installation Manager for the following reasons: l

The Installation Manager itself identifies the required drivers and copies these to the system. l

All the Installation Manager functions are available to you during installation. This means that you can, for example, configure the entire system including the server management settings. l

Installation using the Installation Manager does not take significantly longer than installation using the operating system CD/DVDs.

Installations without the Installation Manager must be controlled via the keyboard, as the mouse cursor cannot be synchronized during the installation process. In contrast, if you install using the Installation Manager then all configuration and installation steps can be performed using the mouse.

Linux

If you know which drivers are required by the system, you can start the Linux installation by booting from the Linux installation CD/DVD.

If the installation requires you to integrate drivers from the external device then, before starting the installation, you must set up a virtual media connection: l

To the storage medium (CD-ROM/DVD-ROM or ISO image) from which you want to boot l

If necessary to the storage medium for driver installation iRMC S5 - Configuration and Maintenance 44

5.2 Connecting a storage medium as Virtual Media

5.2 Connecting a storage medium as Virtual Media

The Virtual Media function makes a “virtual” drive available which is located elsewhere in the network.

The source for the virtual drive can be: l

Physical drive or image file on the remote workstation. The image file may also be on a network drive (with drive letter, e.g. “D:” for drive D). l

Image file provided centrally in the network via Remote Image Mount.

For more information on the "virtual Media" feature, see the "iRMC S5 - Web Interface" user guide.

To establish the virtual media connection, proceed as follows on the remote workstation:

Java applet

In the Settings menu, open the Services page.

In the Advanced Video Redirection (AVR) group, deselect the Favor HTML5 over Java Applet option.

Click Apply to submit your changes.

In the title bar, click to open the context menu.

Select Start Video Redirection to start AVR session.

The Java applet for Advanced Video Redirection starts. If there is another redirection session running, both sessions are shown in the AVR Active Session Table .

Click Media/Virtual Media Wizard ... or

Click one of the three Virtual Media icons on the toolbar.

The Virtual Media dialog box opens.

In the appropriate panel of the Virtual Media dialog box, click Select .

The Open file browser dialog box opens.

In the Open dialog box, navigate to the directory of the storage medium that you want to make available as virtual medium from your remote workstation. l

Installation with Installation Manager:

ServerView Suite DVD 1 or an Installation Manager boot image and optionally a formatted USB memory stick as a status backup medium. l

Installation from the vendor’s installation CD/DVD: Windows or Linux installation

CD/DVD and optional drivers.

It is recommended that the ServerView Suite DVD 1 and the operating system installation CD/DVD are stored in a folder as an image file (ISO image) and that they are connected from there as virtual storage media or provided via Remote

Image Mount. iRMC S5 - Configuration and Maintenance 45

5.2 Connecting a storage medium as Virtual Media

10.

Select the required device type in the Files of Type field.

11.

Specify the storage medium you want to connect as a virtual medium in the File

Name field:

In the case of an ISO image (ISO/NRG image), enter the file name. Alternatively, click on the file name in the Explorer.

In the case of a drive, enter the name of the drive, e.g.

D for drive D (Windows)

/dev/..

. (Linux)

12.

Click Open to confirm your selection.

The selected storage medium is made available as a virtual medium and displayed in the corresponding panel of the Virtual Media dialog box.

13.

Click Connect to connect the DVD ROM drive (DVD) or the Installation Manager boot image as virtual storage media.

HTML5

In the Settings menu, open the Services page.

In the Advanced Video Redirection (AVR) group, select the Favor HTML5 over Java

Applet option.

Click Apply to submit your changes.

In the title bar click to start Advanced Video Redirection.

This opens the AVR window.

In the status bar click Select . An Upload file dialog box opens in which you can select an ISO image that is then displayed in the CD image field.

Click Start Media .

The CD image is mounted. iRMC S5 - Configuration and Maintenance 46

5.3 Booting the managed server

5.3 Booting the managed server

To boot the managed server from the ServerView Suite DVD 1 and configure it with the

Installation Manager, proceed as follows:

In the title bar of the iRMC web interface click to power off and to start up or reboot the managed server. You can follow the progress of the boot process in the AVR window.

During the managed server’s BIOS POST phase, virtual storage media are displayed as

USB 2.0 devices. Virtual storage media are represented by the shared entry “CD-ROM

DRIVE” in the BIOS boot sequence:

If a local CD-ROM/DVD-ROM drive and a CD-ROM/DVD-ROM drive connected as a virtual medium are both present on the managed server the managed server boots from the

CD-ROM/DVD-ROM drive provided via Virtual Image.

Press [F2] on the keyboard while the server is booting.

In the UEFI set-up, open the Boot menu in which you can define the boot sequence.

Specify Boot Priority=1 (highest priority) for the ServerView Suite DVD 1 which is connected as a virtual storage medium.

Save your settings and exit the UEFI setup.

The managed server then boots from the ServerView Suite DVD 1 which is connected as virtual storage.

If the system does not boot from the virtual storage medium (ServerView Suite DVD 1 or

Installation Manager boot image):

Check whether the storage medium is displayed during the BIOS POST phase and connect the storage medium as a virtual medium if necessary.

Make sure that the correct boot sequence is specified.

It takes about five minutes to boot from the ServerView Suite DVD 1 via a virtual storage medium. The boot progress is indicated during the process. Once the boot process has completed, the Installation Manager startup displays a dialog box in which you are asked to select a medium for the status backup area (status backup medium).

Select Standard mode as the Installation Manager mode.

Specify where the configuration data is to be stored:

Status backup medium

Stores the configuration data on a local replaceable data medium. iRMC S5 - Configuration and Maintenance 47

5.3 Booting the managed server

Requirements l

The backup medium must not be write-protected. l

A USB stick must already be connected to the USB port when the system is booted.

If you fail to do this and wish to save the configuration file, connect the USB stick now and reboot from the ServerView Suite DVD 1.

Select the option on local drive (floppy / USB stick) .

Select the corresponding drive from the list to the right of this option.

For more information on creating Installation Manager status disks, see the “ServerView

Installation Manager” user guide.

Connecting the status medium and/or installation media via the network

Store the configuration data on a network medium.

1. Set up the required shares for this purpose.

If you provide a medium with a prepared configuration file and/or an installation medium via the network, you must select this option.

Depending on your infrastructure, you can either obtain a temporary IP address via DHCP or manually configure an IPv4 or IPv6 address for the current Installation Manager session.

If you do not select any status backup option all the configuration data will be lost when you reboot.

Start the Installation Manager by clicking Continue .

The Installation Manager Welcome page opens. iRMC S5 - Configuration and Maintenance 48

5.3 Booting the managed server

Figure 11: Installation Manager - Welcome page

Click Deployment to start preparation of the local installation (deployment).

To prepare the installation, the Installation Manager wizards take you through a sequence of configuration steps that gather specifications for configuring the system and for subsequent unattended installation of the operating system.

Configure the local CD-ROM/DVD-ROM drive of the managed server as the installation source. You can then also make the Windows installation CD/DVD available from the

CD-ROM/DVD-ROM drive of the remote workstation if you connect it to the managed

server as a virtual storage medium ( "Installing Windows on the managed server" on page 50 ).

Once you have completed the configuration with the Installation Manager, the Installation

Info

page for the Windows installation ( "Installing Windows on the managed server" on page 50

) or for the Linux installation ( "Installing Linux on the managed server" on page 51 )

is displayed. This allows you to start the installation process. iRMC S5 - Configuration and Maintenance 49

5.4 Installing Windows on the managed server

5.4 Installing Windows on the managed server

Once configuration is complete, the Installation Manager displays the Installation Info page.

Figure 12: Installation Manager - Installation Info page (Windows)

If you have configured the local CD-ROM/DVD-ROM drive of the managed server as the installation source, proceed as follows at the remote workstation:

In the menu bar of the AVR window, select Media/Virtual Media Wizard to open the

Virtual Media dialog box.

Safely remove the storage device, i.e. ensure that no more applications/programs are accessing the storage media.

To clear a virtual media connection, click the corresponding Disconnect button.

Clear all virtual media connections.

Remove the ServerView Suite DVD 1 from the DVD ROM drive at the remote workstation.

Insert the Windows installation CD/DVD into this drive.

Close the application if autostart is active.

Connect the CD-ROM/DVD-ROM drive containing the Windows installation CD/DVD as a virtual storage medium. iRMC S5 - Configuration and Maintenance 50

5.5 Installing Linux on the managed server

In the Installation Info page of the Installation Manager, click Start installation .

All the installation files are copied to the managed server.

When the copy operation is complete, the Installation Manager opens a confirmation dialog box and prompts you to remove all the storage media from the removable media drives before the managed server is rebooted.

Clear all current virtual media connections again.

10.

In the confirmation dialog box, click OK to reboot the managed server.

Once the managed server has rebooted, you can monitor the entire installation by means of the AVR.

5.5 Installing Linux on the managed server

During the installation you can use the mouse but cannot synchronize it.

Whenever you change a virtual storage medium, you must remove the virtual media connection for the currently connected medium and then connect the new medium as a virtual storage medium.

Once configuration is complete, the Installation Manager displays the Installation Info page.

Figure 13: Installation Manager - Installation Info page (Linux) iRMC S5 - Configuration and Maintenance 51

5.5 Installing Linux on the managed server

If you have configured the local CD-ROM/DVD-ROM drive of the managed server as the installation source, proceed as follows at the remote workstation:

In the menu bar of the AVR window, select Media/Virtual Media Wizard to open the

Virtual Media dialog box.

“Safely remove” the storage device, i.e. ensure that no more applications/programs are accessing the storage media.

To clear a Virtual Media connection, click the corresponding Disconnect button.

Clear all virtual media connections.

Remove the ServerView Suite DVD 1 from the DVD ROM drive at the remote workstation.

Insert the Linux installation CD/DVD into this drive.

Close the application if autostart is active.

Connect the CD-ROM/DVD-ROM drive containing the Windows installation CD/DVD as a virtual storage medium.

In the Installation Info page of the Installation Manager, click Start installation .

All the installation files are copied to the managed server.

Clear all current virtual media connections again.

10.

In the confirmation dialog box, click OK to reboot the managed server.

Once the managed server has rebooted, you can monitor the entire installation by means of the AVR. iRMC S5 - Configuration and Maintenance 52

6 Firmware update

6 Firmware update

The iRMC S5 uses two separate banks in flash memory. Each bank has a capacity of 46 MB and can contain a firmware image. The firmware images can be different: l

Firmware image 1 (low firmware image) l

Firmware image 2 (high firmware image)

One of the two firmware images is active (running) at any given time, while the other is inactive. The firmware image that is active depends on the so-called firmware selector

( "Firmware selector" on page 54 ).

The firmware of the iRMC is not executed in the EEPROM, but is loaded into SRAM memory on startup instead and executed there. This means that it is possible to update both active and inactive firmware images online, i.e. with the server operating system (Windows or

Linux) running.

If an error occurs while loading the firmware from one of the images, the firmware is automatically loaded from the other image.

Besides the possibility of performing a firmware update, you can also downgrade the firmware to the previous version.

The current firmware versions are present on the ServerView Suite DVD 2 or can be downloaded manually from the Download section of the Fujitsu web server.

You can obtain the up-to-date version of the ServerView Suite DVD 2 at two-monthly intervals.

Before updating or downgrading the firmware, read the supplementary documentation supplied with the new firmware carefully (in particular the Readme files). iRMC S5 - Configuration and Maintenance 53

6.1 Firmware selector

6.1 Firmware selector

The firmware selector specifies the iRMC S5 firmware to be executed. Every time the iRMC is reset and restarted, the firmware selector is evaluated and processing branches to the corresponding firmware.

The firmware selector can have the following values:

0 Firmware image containing the most recent firmware version

1 firmware image 1

2 firmware image 2

3 Firmware image containing the oldest firmware version

4 Firmware image most recently updated

5 Firmware image that has been updated least recently

Depending on the update variant used, the firmware selector is set differently after the update.

You can query and set the firmware selector explicitly: l

Query via the Overview page of the iRMC web interface in the Running iRMC

Firmware group (for more information, see the "iRMC S5 - Web Interface" user guide) l

Set via the iRMC Update group on the Update page of the Tools menu.

6.2 Methods of firmware image update

Several methods are available for updating the iRMC firmware images.

Some methods can be performed while the server's (host) operating system is running.

These are the so-called online firmware updates. The firmware update will not harm the operation system: l

Update using iRMC web interface l

Update using ServerView Update Manager l

Update using ServerView Update Manager Express or ASP

Some methods can also be run without a running server's operating system. These are the so-called offline Firmware updates: l

Update using iRMC web interface l

Update using ServerView Update Manager Express or ASP iRMC S5 - Configuration and Maintenance 54

6.2 Methods of firmware image update

If a new version of the bootloader is available, both firmware images will be automatically flashed within the same update process.

6.2.1 Firmware Update using the web interface

This update can be executed in online or offline mode of the server operating system (OS).

The Update page of the Tools menu allows you to update the firmware of the iRMC by providing the firmware image either: l

Locally on the remote workstation l

On a network share l

On a TFTP server (for more information, see the "iRMC S5 - Web Interface" user guide)

Figure 14: Update page iRMC S5 - Configuration and Maintenance 55

6.2 Methods of firmware image update

6.2.2 Firmware update using ServerView Update Manager

This update can be executed in online mode of the server OS.

Using the ServerView Update Manager, you can start the update of the iRMC firmware via a graphical user interface or via a command line interface (Windows and Linux). The

ServerView Update Manager accesses the update data via its Update Repository on the

ServerView Suite DVD 2 or on the management server.

You update the Update Repository on the management server using the Download

Manager or by manually performing a download from the Download section of the Fujitsu web server.

For more information on firmware updates with the ServerView Update Manager, see the

“ServerView Update Manager” user guide.

6.2.3 Firmware update using ServerView Update Manager Express

This update can be executed in online or offline mode of the server OS.

On Windows and Linux operating systems, you can update the iRMC firmware either using the graphical user interface of ServerView Update Manager Express or by using the ASP

(Autonomous Support Package) command interface.

Under Windows, you can also start an ASP in the Windows Explorer by double-clicking the corresponding

ASP-*.exe file. iRMC S5 - Configuration and Maintenance 56

6.3 Firmware image downgrade

6.3 Firmware image downgrade

Besides the possibility of performing a firmware update, you can also downgrade the firmware to the previous version.

The easiest way to downgrade the firmware is to store the previous-version firmware image as the inactive firmware image in the EEPROM of the iRMC. In this case, you only have to

set the firmware selector to this previous-version image ( "Firmware selector" on page 54 )

and restart the iRMC to activate the firmware.

You can also downgrade the firmware by applying the methods described in the following sections. In these cases, you perform a firmware update based on the firmware of the previous version. Special requirements to perform the downgrade are pointed out separately in the following sections.

When downgrading the firmware, note: l

Downgrade via Update Manager Express:

The firmware downgrade is only feasible in Expert mode. In addition, the Downgrade option must be activated. l

Downgrade via ASP:

Windows You can perform the downgrade if you start the ASP by double-clicking the corresponding *.exe file. When starting the ASP via the CLI, you must explicitly specify the Force=yes option.

Linux You must explicitly specify either option

-f or option

--force

. iRMC S5 - Configuration and Maintenance 57

வணக்கம்! Fujitsu PRIMEQUEST 3800B2 User Guide உடன் உங்களுக்கு உதவ சிறப்பாகப் பயிற்றுவிக்கப்பட்ட AI சாட்போட் நான். நான் ஆவணத்தை முழுமையாக மதிப்பாய்வு செய்துள்ளேன், மேலும் உங்களுக்குத் தேவையான சரியான தகவலைக் கண்டறிய அல்லது உள்ளடக்கத்தை தெளிவான மற்றும் எளிமையான சொற்களில் விளக்க உதவ முடியும். குறிப்பிட்ட அம்சங்கள், சரிசெய்தல் படிகள் அல்லது பொதுவான பயன்பாடு குறித்த வழிகாட்டுதலை நீங்கள் தேடுகிறீர்களானால், உங்கள் கேள்விகளைக் கேட்க தயங்கவும். உங்கள் கவலைகள் அல்லது தேவைகள் பற்றி நீங்கள் எவ்வளவு அதிகமாக விவரங்களை வழங்குகிறீர்களோ, அவ்வளவு துல்லியமாகவும் эффективноவும் நான் உங்களுக்கு உதவ முடியும்!

உதவியாளர் தட்டச்சு செய்கிறார்

உதவியாளர் விசைப்பலகையில் இல்லை. தயவுசெய்து, பின்னர் மீண்டும் முயற்சிக்கவும்.

உள்ளடக்க அட்டவணை

உங்கள் தாய்மொழி அல்லாத ஒன்று உட்பட, பல மொழிகளில் எழுதப்பட்ட ஆவணத்தை நீங்கள் அடைந்துவிட்டீர்கள் போல் தெரிகிறது. நீங்கள் விரும்பும் மொழி இல்லாத பக்கங்களை தற்காலிகமாக மறைக்க பின்வரும் இணைப்புகளைப் பயன்படுத்தலாம்.

விளம்பரம்