Fujitsu V4.90, Primergy ServerView Suite ServerView Remote Management Frontend V4.90 User Manual

2.95 Mb
Loading...

PRIMERGY ServerView Suite

ServerView Remote Management Frontend

ServerView Operations Manager V4.90

Edition June 2009

CommentsSuggestionsCorrections

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.

Feel free to send us your comments by e-mail to manuals@ts.fujitsu.com.

Certified documentation according to DIN EN ISO 9001:2000

To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2000.

cognitas. Gesellschaft für Technik-Dokumentation mbH www.cognitas.de

Copyright and Trademarks

Copyright © 2009 Fujitsu Technology Solutions GmbH.

All rights reserved.

Delivery subject to availability; right of technical modifications reserved.

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

Contents

1

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5

1.1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6

1.2

Structure of the manual . . . . . . . . . . . . . . . . . . . . .

8

1.3

Changes since the last edition . . . . . . . . . . . . . . . . .

9

1.4

Notational conventions . . . . . . . . . . . . . . . . . . . .

10

2

Configuring the Remote Management Frontend . . . . . . .

11

2.1Configuring multisession support, SSH access and

console redirection . . . . . . . . . . . . . . . . . . . . . . . 11

2.2Deleting/not deleting the console area on text console redirection after the end of a session . . . . . . . . . . . . . 13

3 Starting the Remote Management Frontend . . . . . . . . . 15

3.1Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.1.1Requirements at the managed server . . . . . . . . . . . . . . 16

3.1.2

Requirements at the remote workstation . . . . . . . . . . . . 17

3.2Starting the Remote Management Frontend via the

Operations Manager . . . . . . . . . . . . . . . . . . . . . . 18

3.2.1Starting the Remote Management Frontend via an

iRMC/ iRMC S2 . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.2.2Starting Remote Management Frontend via an

RSB/ RSB S2/ RSB S2 LP(3HU) or a BMC . . . . . . . . . . . 25

3.2.3Starting Remote Management Frontend via a

RemoteView Management Blade . . . . . . . . . . . . . . . . 30

ServerView Remote Management Frontend

Contents

4Working with the ServerView Remote Management

Frontend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.1The Remote Management Frontend user interface . . . . . . 33

4.1.1Remote Management window for Remote Manager and

Console Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.1.2Remote Management window for text console redirection

 

and power management . . . . . . . . . . . . . . .

. .

. .

.

. 38

4.2

Establishing a connection to the managed server

. .

. .

.

. 42

4.2.1Establishing a connection to the iRMC/ iRMC S2,

RSB S2/ RSB S2 LP (3 HU) via Telnet/SSH (Remote Manager) . 42

4.2.2Establishing a connection to the iRMC/ iRMC S2/BMC for

power management and console redirection . . . . . . . . . . . 49

5

Security . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . 53

5.1

Password protection

. . . . . . . . . . . . . . . . . . . . . . 53

5.2

Console redirection

. . . . . . . . . . . . . . . . . . . . . . . 54

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

ServerView Remote Management Frontend

1 Preface

The ServerView Remote Management Frontend provides you with a web-based working environment for the remote management of PRIMERGY servers which is integrated in the ServerView Operations Manager. The ServerView Remote Management Frontend is started from the ServerView Operations Manager and the installation of this application is therefore a necessary precondition.

The ServerView Remote Management Frontend and the ServerView Operations Manager are referred to below as the Remote Management Frontend and the Operations Manager respectively.

You simply need a standard web browser for the display at the remote workstation. You can open a separate browser window for each PRIMERGY server displayed in the Operations Manager ServerList window. From here, you can then open various windows for the remote management of the corresponding PRIMERGY server.

As a web-based solution, the Remote Management Frontend can be installed on a remote workstation set up under a Windows or Linux system.

IIn the case of an individual PRIMERGY server with installed

iRMC/ iRMC S2, you can also use the Remote Management Frontend functionality via this iRMC/ iRMC S2's web interface (See the manuals “iRMC - integrated Remote Management Controller” and “iRMC S2 - integrated Remote Management Controller”).

ServerView Remote Management Frontend

5

Overview

Preface

1.1Overview

The type of window displayed in the Remote Management Frontend depends, on the one hand, on the hardware (iRMC, RSB etc.) which you use to establish the connection to the managed server and, on the other, on the interface which is provided in each case.

Hardware-specific displays in the Remote Management Frontend

The Remote Management Frontend's displays and controls are adapted to the remote hardware via which you establish the connection to a managed PRIMERGY server:

In the case of a PRIMERGY server with an installed iRMC or iRMC S2, you can use either the Telnet/SSH “Remote Manager” application or the managed server's power management and console redirection window in the Remote Management Frontend's console area.

In the case of a PRIMERGY server with an installed RSB or RSB S2/ RSB S2 LP (as of firmware version 6.4.57.29), the Telnet “Remote Manager” application is available to you in the Remote Management Frontend's console area once a connection has been established.

Only in the case of RSB:

You can use the Remote Manager to redirect the display at the console of the managed server. In this way, you can access the BIOS setup and the RemoteView/Diagnose system tools on the managed server.

In the case of a PRIMERGY server with an installed BMC with firmware version 2.x or higher, the managed server's power management and console redirection window is available in the Remote Management Frontend's console area after the establishment of a connection.

In the case of a blade server with a RemoteView Management Blade, the RemoteView Management Blade Telnet “Console Menu” application is available to you in the Remote Management Frontend's console area after the establishment of a connection. You can use the Console Menu to redirect the display at the consoles of the managed server blades. In this way, you can access the BIOS setup at the managed server blade.

6

ServerView Remote Management Frontend

Preface

Overview

The interface provided by the Remote Management Frontend for the remote management of PRIMERGY servers:

Depending on the hardware available for remote management on the individual managed servers, the Remote Management Frontend provides the following interfaces for web-based access to the managed servers.

Telnet-based interface (Remote Manager)

Depending on the managed PRIMERGY server, the connection may be established via

an iRMC/ iRMC S2 or

an RSB/ RSB S2/ RSB S2 LP (3HU) with firmware version 6.4.57.29 or higher.

Telnet-based interface (Console Menu) via a RemoteView Management Blade

SSH-based interface (Remote Manager) via an iRMC/ iRMC S2.

Interface for power management and console redirection (IPMI (1.5)-over- LAN-based) via a Kalypso BMC (BMC - firmware version 2.x or higher)

Interface for power management (IPMI (2.0)-over-LAN-based) and console redirection (via SOL) via

an iRMC/ iRMC S2 or

a BMC of the RX/TX 600 S2/S3

ServerView Remote Management Frontend

7

Structure of the manual

Preface

1.2Structure of the manual

This manual provides you with information about the following topics:

Chapter 1: Preface

This chapter provides you with a brief overview of the Remote Management Frontend.

Chapter 2: Configuration

This chapter describes how you can configure the basic settings of the Remote Management Frontend depending on your requirements.

Chapter 3: Starting the Remote Management Frontend

This chapter describes how you start the Remote Management Frontend via the graphical user interface of the Operations Manager, the prerequisites that must be fulfilled and the special requirements that exist depending on the remote management hardware used in the managed server.

Chapter 4: Working with the Remote Management Frontend

This chapter starts by explaining the structure and components of the Remote Management Frontend user interface. It then describes how you establish a connection to a managed server via the Remote Management Frontend's user interface.

Chapter 5: Security

This chapter provides a brief overview of password protection in the Operations Manager and in the remote management hardware.

8

ServerView Remote Management Frontend

Preface

Changes since the last edition

1.3Changes since the last edition

This edition is valid for the Remote Management Frontend V4.90 and replaces the following online manual: “Remote Management Frontend V4.80“, edition April 2009.

ServerView Remote Management Frontend

9

Notational conventions

Preface

1.4Notational conventions

The meanings of the symbols used in this manual are as follows:

VWarning

This symbol is used to draw attention to risks which

may represent a health hazard or which may lead

 

to data loss or damage to the hardware.

I

This symbol is used to highlight important information and tips.

Ê

This symbol indicates an action which you must

 

carry out.

 

 

Text in italics

In running text, commands, menu items, and the

 

names of buttons, options, files and paths are

 

shown in italics.

 

 

<text>

Indicates variables which must be replaced by

 

current values.

 

 

Monospaced font

Output from the system is shown in monospaced

 

font.

Monospaced font Commands to be entered at the keyboard are Bold monospaced font shown in bold, monospaced font.

[square brackets]

Indicate optional entries.

{braces}

Indicate a list of alternatives separated by “|”.

 

 

[Keyboard] [symbols]

Keys are shown as they appear on the keyboard. If

 

uppercase characters are to be entered explicitly,

 

this is indicated for instance by [SHIFT] - [A] for A.

 

If two keys are to be pressed simultaneously, this

 

is indicated by a hyphen between the two keyboard

 

symbols.

 

 

Table 1: Notational conventions

If reference is made to passages elsewhere in this manual, the title of the chapter or section is named and the page number given refers to the start of the section.

10

ServerView Remote Management Frontend

2Configuring the Remote Management Frontend

You can use configuration files to make the following settings for the Remote Management Frontend:

Multisession support for power management and console redirection via BMC/ iRMC/ iRMC S2 and display of the buttons for SSH access (iRMC/ iRMC S2) and power management/console redirection

(iRMC/ iRMC S2) in the Operations Manager.

Deletion/non-deletion of the console area on text console redirection after termination of a console redirection session.

2.1Configuring multisession support, SSH access and console redirection

IThe following versions of the Operations Manager and the Remote Management Frontend must be present before you can configure the Remote Management Frontend settings described in this section:

Operations Manager V4.90 or higher

Remote Management Frontend V4.90 or higher

When you install the Remote Management Frontend, a folder named Features is automatically created in the directory

<SV-installation-directory>\ ServerView\ServerView Services\ wwwroot\ RemoteView. In this folder, you can configure whether the following Remote Management Frontend features are made available:

Multisession support for BMC/ iRMC/ iRMC S2

For each managed PRIMERGY server with iRMC/ iRMC S2 or BMC, it is also possible to open a browser window for power management and console redirection via iRMC/ iRMC S2 or BMC.

Default value: Multisession support for BMC/ iRMC/ iRMC S2 is activated.

IMultisession support is always activated for the other interfaces made available by the Remote Management Frontend.

ServerView Remote Management Frontend

11

Configuration

Installation and configuration

SSH access to the iRMC/ iRMC S2:

In the ServerView [server-name] window for PRIMERGY servers with iRMC/ iRMC S2, the iRMC SSH button for SSH access to the iRMC/ iRMC S2 is displayed (see figure 5 on page 22).

Default value: The iRMC SSH button is displayed.

Console redirection (SOL) and power management for PRIMERGY servers with iRMC/ iRMC S2:

The corresponding button (iRMC Power Management) is displayed in the ServerView [server-name] window (see figure 5 on page 22).

Default value: The iRMC Power Management button for console redirection (SOL) and power management is not displayed.

Configuring settings in the “Features” folder

You can activate or deactivate the individual features (multisession support, display of certain buttons) by creating or deleting the corresponding text files in the Features folder. The content of the text files is irrelevant, i.e. the files can be empty.

The following fixed names must be used for the text files:

MultiSessionBMC

Multisession support for BMC/ iRMC/ iRMC S2 power management and console redirection is activated.

SSHiRMC

The button for SSH access to iRMC/ iRMC S2 is displayed for PRIMERGY servers with iRMC/ iRMC S2.

SOLiRMC

The button for console redirection (SOL) and power management is displayed for PRIMERGY servers with iRMC/ iRMC S2.

IPlease note:

The file names are not case-sensitive.

The file names must not have any name suffix (.txt).

12

ServerView Remote Management Frontend

Installation and configuration

Configuration

2.2Deleting/not deleting the console area on text console redirection after the end of a session

When console redirection is performed, the content of the console area is deleted by default following termination of the console redirection session. If the content of the console area is to be retained after the end of the session then you must configure this as follows:

ÊDepending on the server, open the following files:

For servers using Kalypso BMC:

<SV-installation-directory>\ ServerView\ServerView Services\

wwwroot\ RemoteView\ appbmc.conf

For servers of the type RX/TX600 S1/S2 and servers with iRMC S1/ iRMC S2:

<SV-installation-directory>\ ServerView\ServerView Services\

wwwroot\ RemoteView\ appbmcl.conf

Ê Set the option Terminal.clearOnOffline to “false”.

ServerView Remote Management Frontend

13

3Starting the Remote Management Frontend

This chapter describes:

the requirements that must be fulfilled in order to start the Remote Management Frontend via the Operations Manager.

how you start the Remote Management Frontend via the Operations Manager and what you need to take account of depending on the status and remote management hardware of the managed server.

You start the Remote Management Frontend via the graphical user interface of the Operations Manager.

IThe Remote Management Frontend is not listed in the Start menu.

IIn the case of a PRIMERGY server with installed iRMC/ iRMC S2, you can also call the Remote Management Frontend functionality for this server via the corresponding links in the iRMC/ iRMC S2's web interface (see the manuals “iRMC - integrated Remote Management Controller” and “iRMC S2 - integrated Remote Management Controller”).

ServerView Remote Management Frontend

15

Requirements

Starting the Remote Management Frontend

3.1Requirements

Before you can start the Remote Management Frontend and establish a connection to the managed server, a number of requirements must fulfilled both at the managed server and at the remote workstation.

3.1.1Requirements at the managed server

Depending on whether the Remote Management Frontend accesses the managed server via an iRMC/ iRMC S2, an RSB/ RSB S2/ RSB S2 LP, a BMC or a RemoteView Management Blade, the following requirements must be fulfilled at the managed server:

iRMC/ iRMC S2

Both the iRMC/ iRMC S2's LAN interface and text console redirection (via Serial Over LAN) must be configured.

IText console redirection via Serial over LAN (SOL) assumes that the operating system and/or the BIOS use serial port 1 (COM1) for text console redirection.

For detailed information, see the manuals “iRMC - integrated Remote Management Controller” and “iRMC S2 - integrated Remote Management Controller”.

RSB S2/ RSB S2 LP (3HU)

Access via the Remote Management Frontend to an

RSB S2/ RSB S2 LP/ RSB S2 LP (3HU) is only possible if the

RSB S2/ RSB S2 LP/ RSB S2 LP (3HU) is operated with firmware version *29 or higher.

16

ServerView Remote Management Frontend

Starting the Remote Management Frontend

Requirements

The management port of the RSB S2/ RSB S2 LP (3HU) on the managed server should be configured to the default value 3172.

ISince the Operations Manager does not know the management port value, the Remote Management Frontend works with the default value.

Since a connection is not automatically established when the Remote Management Frontend is started, you can correct any nonstandard value for the management port after the Remote Management Frontend has been started.

BMC

The BMC must be configured for an IPMI-over-LAN connection and console redirection.

RemoteView Management Blade

The management port of the RemoteView Management Blade on the managed server should be configured to the default value 3172.

ISince the Operations Manager does not know the management port value, the Remote Management Frontend works with the default value.

Since a connection is not automatically established when the Remote Management Frontend is started, you can correct any nonstandard value for the management port after the Remote Management Frontend has been started.

3.1.2Requirements at the remote workstation

The following must be enabled in the web browser:

Java

JavaScript

ServerView Remote Management Frontend

17

... starting via the Operations Manager

Remote Management Frontend

3.2Starting the Remote Management Frontend via the Operations Manager

You start the Remote Management Frontend via the graphical user interface of the Operations Manager.

Proceed as follows:

ÊStart the Operations Manager

(see the manual “ServerView Operations Manager”). The main page of the Operations Manager opens:

Figure 1: ServerView Operations Manager: Start page

18

ServerView Remote Management Frontend

Remote Management Frontend ... starting via the Operations Manager

ÊOn the main page of the Operations Manager, click the link ServerList under the entry “ServerList”.

The ServerList window is displayed (see figure 2).

Figure 2: Operations Manager: “Server List” window

Access to the Remote Management Frontend varies depending on the Remote Management hardware that is present at the server:

For managed servers with iRMC/ iRMC S2:

Access via the Operations Manager window (see section “Starting the Remote Management Frontend via an iRMC/ iRMC S2” on page 20).

For managed servers with RSB/ RSB S2/ RSB S2 LP (3HU) and/or BMC:

Access via the Operations Manager window (see section “Starting Remote Management Frontend via an RSB/ RSB S2/ RSB S2 LP(3HU) or a BMC” on page 25).

For managed blade servers ( ) with RemoteView Management Blade: Access via the Blade Server View window (see section “Starting Remote Management Frontend via a RemoteView Management Blade” on page 30).

ServerView Remote Management Frontend

19

+ 43 hidden pages