FUJITSU S2, S3 User Manual
User Guide - English
ServerView Suite
Remote Management
iRMC S2/S3 - integrated Remote Management Controller
Edition July 2012
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.
Feel free to send us your comments by e-mail to
manuals@fujitsu-siemens.com.
Certified documentation
according to DIN EN ISO 9001:2008
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:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks
Copyright © 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Purpose and target groups of the manual . . . . . . . . . . 12
1.2 Functions of the iRMC S2/S3 (overview) . . . . . . . . . . . 13
1.3 Communication interfaces of the iRMC S2/S3 . . . . . . . . 19
1.4 Communication protocols used by the iRMC S2/S3 . . . . . 20
1.5 IPMI - technical background . . . . . . . . . . . . . . . . . . 21
1.6 DCMI (Data Center Management Interface) . . . . . . . . . 29
1.7 Changes since the previous versions of the manual . . . . 30
1.8 ServerView Suite link collection . . . . . . . . . . . . . . . . 33
1.9 Documentation for ServerView Suite . . . . . . . . . . . . . 34
1.10 Notational conventions . . . . . . . . . . . . . . . . . . . . 35
2 Logging on to the iRMC S2/S3 for the first time . . . . . . . 37
2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.2 iRMC S2/S3 factory defaults . . . . . . . . . . . . . . . . . . 38
2.3 Logging into the iRMC S2/S3 web interface . . . . . . . . . 39
3 Configuring the iRMC S2/S3 . . . . . . . . . . . . . . . . . . 41
3.1 Configuring the LAN interface of the iRMC S2/S3 . . . . . . 41
3.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.1.1.1 Connected to the correct LAN port? . . . . . . . . . . . . . 42
3.1.1.2 Interaction between the IP addresses of the iRMC S2/S3
and the system . . . . . . . . . . . . . . . . . . . . . . . . 43
3.1.1.3 Access from a different subnet . . . . . . . . . . . . . . . . 43
3.1.2 Configuring the LAN interface: Configuration tools . . . . . . . 43
3.1.3 Configuring the LAN interface using the BIOS / TrustedCore /
UEFI setup utility . . . . . . . . . . . . . . . . . . . . . . . . 44
3.1.3.1 Configuring the LAN interface of the iRMC S2 by using
the BIOS / TrustedCore setup utility . . . . . . . . . . . . . 44
iRMC S2/S3
Contents
3.1.3.2 Configuring the LAN interface of the iRMC S3 by using
the UEFI setup Utility . . . . . . . . . . . . . . . . . . . . . 46
3.1.4 Testing the LAN interface . . . . . . . . . . . . . . . . . . . . . 47
3.2 Configuring text console redirection via LAN using the
BIOS / TrustedCore / UEFI setup utility . . . . . . . . . . . . 48
3.2.1 Configuring text console redirection for the iRMC S2 . . . . . . . 49
3.2.2 Configuring text console redirection for the iRMC S3 . . . . . . . 53
3.2.3 Using console redirection while the operating system is running . 55
3.3 Configuring and using the serial interface of the
iRMC S2/S3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.3.1 Configuring the serial interface of the iRMC S2 . . . . . . . . . 58
3.3.2 Configuring the serial interface using of the iRMC S3 . . . . . . 60
3.3.3 Using the Remote Manager (Serial) interface . . . . . . . . . . 62
3.4 Configuring the iRMC S2/S3 over the iRMC S2/S3
web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.4.1 Configuring the LAN parameters . . . . . . . . . . . . . . . . . 63
3.4.2 Configuring alerting . . . . . . . . . . . . . . . . . . . . . . . . 64
3.4.3 Configuring text console redirection . . . . . . . . . . . . . . . 64
4 User management for the iRMC S2/S3 . . . . . . . . . . . . . 65
4.1 User management concept for the iRMC S2/S3 . . . . . . . . 66
4.2 User permissions . . . . . . . . . . . . . . . . . . . . . . . . 68
4.3 Local user management for the iRMC S2/S3 . . . . . . . . . 70
4.3.1 Local user management using the iRMC S2/S3 web interface . . 70
4.3.2 Local user management via the Server Configuration Manager . 71
4.3.3 SSHv2 public key authentication for iRMC S2/S3 users . . . . . 72
4.3.3.1 reating public and private SSHv2 keys . . . . . . . . . . . . 73
4.3.3.2 Loading the public SSHv2 key onto the iRMC S2/S3
from a file . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.3.3.3 Configuring PuTTY and the OpenSSH client for using
the public SSHv2 key . . . . . . . . . . . . . . . . . . . . . 79
4.3.3.4 Example: Public SSHv2 key . . . . . . . . . . . . . . . . . . 84
iRMC S2/S3
Contents
5 Advanced Video Redirection (AVR) . . . . . . . . . . . . . . 85
5.1 Requirements: Check the AVR settings . . . . . . . . . . . 86
5.2 Using AVR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.2.1 Using a low bandwidth . . . . . . . . . . . . . . . . . . . . . . 89
5.2.2 Parallel AVR sessions . . . . . . . . . . . . . . . . . . . . . . 89
5.2.3 Local Monitor Off" function . . . . . . . . . . . . . . . . . . . . 90
5.2.4 Redirecting the keyboard . . . . . . . . . . . . . . . . . . . . 91
5.2.5 Redirecting the mouse . . . . . . . . . . . . . . . . . . . . . . 93
5.2.5.1 Synchronizing the mouse pointer . . . . . . . . . . . . . . 93
5.2.5.2 Managed Windows server: Adjusting the settings for
synchronization of the mouse pointers . . . . . . . . . . . 95
5.2.5.3 Managed Linux server: Adjusting the settings for
synchronization of the mouse pointers . . . . . . . . . . . 98
5.3 Menus of the AVR window . . . . . . . . . . . . . . . . . . . 101
5.3.1 Extras menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.3.2 Remote Storage menu . . . . . . . . . . . . . . . . . . . . . . 105
5.3.3 Power Control menu . . . . . . . . . . . . . . . . . . . . . . . 106
5.3.4 Languages menu . . . . . . . . . . . . . . . . . . . . . . . . 107
5.3.5 Preferences menu . . . . . . . . . . . . . . . . . . . . . . . . 108
6 Remote Storage . . . . . . . . . . . . . . . . . . . . . . . . 111
6.1 Providing remote storage at the remote workstation . . . . 113
6.1.1 Starting Remote Storage . . . . . . . . . . . . . . . . . . . . 114
6.1.2 Provision of storage media for emote Storage . . . . . . . . . . 117
6.1.3 Connecting storage media as remote storage . . . . . . . . . . 121
6.1.4 Clearing Remote Storage connections . . . . . . . . . . . . . 125
6.1.5 Removing the storage medium . . . . . . . . . . . . . . . . . 126
6.2 Providing remote storage via a Remote Storage server . . . 127
6.2.1 Installing the Remote Storage server . . . . . . . . . . . . . . 128
6.2.2 Remote Storage server execution modes . . . . . . . . . . . . 129
6.2.3 Configuring, starting and exiting the Remote Storage server . . 130
7 iRMC S2/S3 web interface . . . . . . . . . . . . . . . . . . . 135
7.1 Logging into the iRMC S2/S3 web interface . . . . . . . . . 136
7.2 Required user permissions . . . . . . . . . . . . . . . . . . 138
iRMC S2/S3
Contents
7.3 Structure of the user interface . . . . . . . . . . . . . . . . 143
7.4 System Information - Information on the server . . . . . . . 146
7.4.1 System Overview - General information on the server . . . . . 147
7.4.2 System Component Information - Information on the server
components . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
7.5 BIOS - Backing up/restore BIOS settings, flashing BIOS . . 155
7.5.1 Backup/Restoration - Saving/Restoring BIOS single parameter
settings to/from a file . . . . . . . . . . . . . . . . . . . . . . 155
7.5.1.1 Backing up single BIOS parameters in
ServerView® WinSCU XML format . . . . . . . . . . . . . 156
7.5.1.2 Restoring single BIOS parameters in
ServerView® WinSCU XML format . . . . . . . . . . . . . 157
7.5.2 BIOS - Updating BIOS via "upload from file" or via TFTP . . . 159
7.6 iRMC S2/S3 - Information, firmware and certificates . . . . 164
7.6.1 iRMC S2/S3 Information - Information on the iRMC S2/S3 . . . 165
7.6.2 Save iRMC S2/S3 Firmware Settings -
Save firmware settings . . . . . . . . . . . . . . . . . . . . . 169
7.6.3 Certificate Upload - Load the DSA/RSA certificate and
private DSA/RSA key . . . . . . . . . . . . . . . . . . . . . . 172
7.6.4 Generate a self-signed Certificate -Generate self-signed RSA
certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
7.6.5 iRMC S2/S3 Firmware Update . . . . . . . . . . . . . . . . . 181
7.7 Power Management . . . . . . . . . . . . . . . . . . . . . . 186
7.7.1 Power On/Off - power the server up/down . . . . . . . . . . . 187
7.7.2 Power Options - Configuring power management for the server 191
7.7.3 Power Supply Info - Power supply and IDPROM data for the FRU
components . . . . . . . . . . . . . . . . . . . . . . . . . . 198
7.8 Power Consumption . . . . . . . . . . . . . . . . . . . . . 199
7.8.1 Power Consumption Configuration - Configure power
consumption of the server . . . . . . . . . . . . . . . . . . . 200
7.8.2 Current Power Consumption - Show the current power
consumption . . . . . . . . . . . . . . . . . . . . . . . . . . 206
7.8.3 Power Consumption History - Show server power consumption 207
7.9 Sensors - Check status of the sensors . . . . . . . . . . . 211
7.9.1 Fans - Check fans . . . . . . . . . . . . . . . . . . . . . . . . 212
7.9.2 Temperature - Report the temperature of the server
components . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
7.9.3 Voltages - Report voltage sensor information . . . . . . . . . . 217
7.9.4 Power Supply - Check power supply . . . . . . . . . . . . . . 218
iRMC S2/S3
Contents
7.9.5 Component Status - Check status of the server components . . 220
7.10 System Event Log and Internal Event Log . . . . . . . . . . 223
7.10.1 System Event Log Content -
Show information on the SEL and the SEL entries . . . . . . . 224
7.10.2 Internal Event Log Content Show information on the internal eventlog and the
associated entries . . . . . . . . . . . . . . . . . . . . . . . . 227
7.10.3 Event Log Configuration - Configure IPMI SEL and
internal event log . . . . . . . . . . . . . . . . . . . . . . . . . 230
7.11 Server Management Information - Configuring the server
settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
7.12 Network Settings - Configure the LAN parameters . . . . . 238
7.12.1 Network Interface Settings -
Configure Ethernet settings on the iRMC S2/S3 . . . . . . . . 239
7.12.2 Ports and Network Services -
Configuring ports and network services . . . . . . . . . . . . . 245
7.12.3 DNS Configuration - Configuring DNS for the iRMC S2/S3 . . . 249
7.13 Alerting - Configure alerting . . . . . . . . . . . . . . . . . . 253
7.13.1 SNMP Trap Alerting - Configure SNMP trap alerting . . . . . . 254
7.13.2 Serial / Modem Alerting - Configure alerting via modem . . . . 255
7.13.3 Email Alerting - Configure email alerting . . . . . . . . . . . . 257
7.14 User Management . . . . . . . . . . . . . . . . . . . . . . . 263
7.14.1 iRMC S2/S3 User - local user management on
the iRMC S2/S3 . . . . . . . . . . . . . . . . . . . . . . . . . 263
7.14.1.1 New User Configuration - Configuring a new user . . . . . . 265
7.14.1.2 User “<name>” Configuration - User configuration (details) . 266
7.14.2 Directory Service Configuration (LDAP) -
Configuring the directory service at the iRMC S2/S3 . . . . . . 273
7.14.2.1 Configuring iRMC S2/S3 for Microsoft Active Directory . . . 276
7.14.2.2 Configuring iRMC S2/S3 for Novell eDirectory /
OpenLDAP / OpenDS . . . . . . . . . . . . . . . . . . . . 280
7.14.3 Centralized Authentication Service (CAS) Configuration -
Configuring the CAS Service . . . . . . . . . . . . . . . . . . 286
7.15 Console Redirection - Redirecting the console . . . . . . . 292
7.15.1 BIOS Text Console -
Configure and start text console redirection . . . . . . . . . . . 292
7.15.1.1 BIOS Console Redirection Options -
Configure text console redirection . . . . . . . . . . . . . . 293
iRMC S2/S3
Contents
7.15.1.2 Text Console Redirection (via Serial over LAN) -
Start text console redirection . . . . . . . . . . . . . . . . 295
7.15.1.3 Text console redirection while the operating system
is running . . . . . . . . . . . . . . . . . . . . . . . . . . 300
7.15.2 Advanced Video Redirection -
Start Advanced Video Redirection (AVR) . . . . . . . . . . . . 302
7.16 Remote Storage . . . . . . . . . . . . . . . . . . . . . . . . 312
7.17 Operating iRMC S2/S3 via Telnet / SSH (Remote Manager) 315
8 iRMC S2/S3 via Telnet/SSH (Remote Manager) . . . . . . . 321
8.1 Requirements on the managed server . . . . . . . . . . . . 322
8.2 Operating Remote Manager . . . . . . . . . . . . . . . . . . 323
8.3 Overview of menus . . . . . . . . . . . . . . . . . . . . . . 324
8.4 Logging in . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
8.5 Main menu of the Remote Manager . . . . . . . . . . . . . 328
8.6 Required user permissions . . . . . . . . . . . . . . . . . . 330
8.7 Change the password . . . . . . . . . . . . . . . . . . . . . 332
8.8 System Information - Information on the managed server . 332
8.9 Power Management . . . . . . . . . . . . . . . . . . . . . . 334
8.10 Enclosure Information - System event log and status
of the sensors . . . . . . . . . . . . . . . . . . . . . . . . . 335
8.11 Service processor - IP parameters, identification LED and
iRMC S2/S3 reset . . . . . . . . . . . . . . . . . . . . . . . 339
8.12 Console Redirection (EMS/SAC) - Start text console
redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
8.13 Start a Command Line shell... - Start a SMASH CLP shell . 340
8.14 Console Logging - Redirect message output to
the text console (serial) . . . . . . . . . . . . . . . . . . . . 341
8.15 Command Line Protocol (CLP) . . . . . . . . . . . . . . . . 343
iRMC S2/S3
Contents
9 Configuring iRMC S2/S3 using the Server Configuration
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
9.1 Calling the Server Configuration Manager from the
ServerView Installation Manager . . . . . . . . . . . . . . . 348
9.2 Calling the Server Configuration Manager from the
Windows Start menu . . . . . . . . . . . . . . . . . . . . . . 348
9.3 alling the Server Configuration Manager from the
Operations Manager . . . . . . . . . . . . . . . . . . . . . . 350
10 Firmware update . . . . . . . . . . . . . . . . . . . . . . . . 353
10.1 iRMC S2/S3 firmware (overview) . . . . . . . . . . . . . . . 354
10.2 Setting up the USB memory stick . . . . . . . . . . . . . . . 357
10.3 Updating firmware images . . . . . . . . . . . . . . . . . . . 360
10.3.1 Update via the iRMC S2/S3 web interface . . . . . . . . . . . . 360
10.3.2 Update using the ServerView Update Manager . . . . . . . . . 361
10.3.3 Online update using ServerView Update Manager Express
or ASP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
10.3.4 Update using the operating system flash tools. . . . . . . . . . 363
10.3.5 Update via the lashDisk menu . . . . . . . . . . . . . . . . . . 365
10.4 Emergency flash . . . . . . . . . . . . . . . . . . . . . . . . 367
10.5 Flash tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
11 Remote installation of the operating system via
iRMC S2/S3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
11.1 Installing the operating system via iRMC S2/S3 - general
procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
11.2 Connecting a storage medium as remote storage . . . . . . 374
11.3 Booting the managed server from ServerView Suite DVD 1
and configuring it with the Installation Manager . . . . . . . 377
11.4 Installing the operating system on the managed server
after configuration . . . . . . . . . . . . . . . . . . . . . . . 380
11.4.1 Installing Windows on the managed server after configuration . 380
11.4.2 Installing Linux on the managed server after configuration . . . 383
iRMC S2/S3
Contents
12 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
12.1 IPMI OEM Commands supported by the iRMC S2/S3 . . . . 385
12.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
12.1.2 Description of the IPMI OEM commands . . . . . . . . . . . . 387
12.1.2.1 Description format . . . . . . . . . . . . . . . . . . . . . . 387
12.1.2.2 SCCI-compliant Power On/Off commands . . . . . . . . . 388
12.1.2.3 SCCI-compliant communication commands . . . . . . . . 393
12.1.2.4 SCCI-compliant signaling command . . . . . . . . . . . . 395
12.1.2.5 Firmware-specific commands . . . . . . . . . . . . . . . . 396
12.1.2.6 BIOS-specific commands . . . . . . . . . . . . . . . . . . 400
12.1.2.7 iRMC S2/S3-specific commands . . . . . . . . . . . . . . 402
12.2 Configuring the iRMC S2/S3 via SCCI and scripted
configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 412
12.2.1 iRMC S2/S3 configuration data . . . . . . . . . . . . . . . . . 412
12.2.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 412
12.2.1.2 SCCI file format . . . . . . . . . . . . . . . . . . . . . . . 414
12.2.1.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . 418
12.2.1.4 Exporting / importing configuration data from / on the
iRMC S2/S3 . . . . . . . . . . . . . . . . . . . . . . . . . 419
12.2.2 Scripted configuration of the iRMC S2/S3 . . . . . . . . . . . 420
12.2.2.1 List of SCCI commands supported by the iRMC S2/S3 . . . 420
12.2.2.2 Scripting with cURL . . . . . . . . . . . . . . . . . . . . . 421
12.2.2.3 Scripting with Visual Basic (VB) Script . . . . . . . . . . . 422
12.2.2.4 Scripting with Python . . . . . . . . . . . . . . . . . . . . 423
12.2.2.5 Generating encrypted passwords with iRMC_PWD.exe . . 424
iRMC S2/S3
1 Preface
Modern server systems are becoming increasingly complex. The requirements
with respect to the management of such systems are growing accordingly.
In response to this development, a number of vendors founded the “Intelligent
Platform Management Interface” (IPMI) initiative with the objective of defining a
standardized, abstract, message-based interface between the central system
controller (Baseboard Management Controller - BMC) and intelligent hardware
for platform management. For further details on IPMI, please refer to section
"IPMI - technical background" on page 21.
The integrated Remote Management Controllers iRMC S2 and iRMC S3 (in the
following iRMC S2/S3 for short) each represent a BMC with integrated LAN
connection and extended functionality. In this way, the iRMC S2/S3 offers
comprehensive control over PRIMERGY servers, irrespective of the system
status. In particular, the iRMC S2/S3 allows for out-of-band management
(Lights Out Management, LOM) of PRIMERGY servers. Out-of-band
management uses of a dedicated management channel that enables a system
administrator to monitor and manage servers via remote control regardless of
whether the server is powered on.
Figure 1: iRMC S2 on the system board of a PRIMERGY server
iRMC S2/S3 11
Purpose and target groups of the manual
As an autonomous system on the system board of a modern PRIMERGY
server, the iRMC S2/S3 has its own operating system, its own web server,
separate user management and independent alert management. The
iRMC S2/S3 remains powered up even when the server is in stand-by mode.
This manual describes how to configure the iRMC S2/S3 and the various user
interfaces available.
1.1 Purpose and target groups of the manual
This manual 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 technology behind IPMI and deals with the following
aspects in detail:
– Logging on to the iRMC S2/S3
– Configuring the iRMC S2/S3
– User management on the iRMC S2/S3
– Advanced Video Redirection via iRMC S2/S3
– Remote Storage via iRMC S2/S3
– iRMC S2/S3 web interface
– Telnet/SSH-based interface (Remote Manager) of the iRMC S2/S3
– Configuring the iRMC S2/S3 with the Server Configuration Manager
– Updating the firmware
– Remote installation of the operating system via iRMC S2/S3
– IPMI OEM Commands
Service
If you have any further questions on remote management for PRIMERGY
servers, contact the service and support partners responsible for you.
Other information
http://www.ts.fujitsu.com
12 iRMC S2/S3
Functions of the iRMC S2/S3
1.2 Functions of the iRMC S2/S3 (overview)
The iRMC S2/S3 supports a wide range of functions that are provided by
default. With Advanced Video Redirection (AVR) and Remote Storage, the
iRMC S2/S3 also provides two additional advanced features for the remote
management of PRIMERGY servers. To use AVR and Remote Storage, you
require a valid license key, which can be purchased separately.
Standard functions of the iRMC S2/S3
● Browser access
The iRMC S2/S3 features its own web server which can be accessed by the
management station from a standard web browser.
● Security (SSL, SSH)
Secure access to the Web server and secure graphical console redirection
including mouse and keyboard can be provided over HTTPS/SSL. An
encrypted connection protected using SSH mechanisms can be set up to
access the iRMC S2/S3 using the Remote Manager. The Remote Manager
is an alphanumeric user interface for the iRMC S2/S3.
● ServerView Integration
The ServerView agents detect the iRMC S2/S3 and automatically assign it
to the relevant server. This means that it is possible to start the iRMC S2/S3
web interface and text console redirection using the ServerView Remote
Management Frontend directly from ServerView Operations Manager.
● Power management
Irrespective of the status of the system, you have the following options for
powering the managed server up or down from the remote workstation
– using the iRMC S2/S3 web interface
– using the Remote Manager and the command line interface (CLP)
– with a script.
iRMC S2/S3 13
Functions of the iRMC S2/S3
● Power consumption control
The iRMC S2/S3 allows comprehensive power consumption control on the
managed server. In addition, you can specify the mode (minimum power
consumption or maximum performance) that the iRMC S2/S3 uses to control
power consumption on the managed server. You can switch between these
modes as required.
● Customer Self Service (CSS)
Summary tables for the server components, sensors and the power supply
on the iRMC S2/S3 web interface provide information in a separate column
as to whether the server component affected is a CSS component or not. In
addition, error list of the system event log (SEL) shows for every event
whether it has been triggered by a CSS component.
● Text console redirection
You can start a Telnet/SSH session to the iRMC S2/S3 from the ServerView
Remote Management Frontend. This calls the Remote Manager, via which
you can start a text console redirection session.
● Basic functions of a BMC
The iRMC S2/S3 supports the basic functions of a BMC such as voltage
monitoring, event logging and recovery control.
● “Headless” system operation
The managed server does not require a mouse, monitor or keyboard to be
connected. The benefits of this include lower costs, far 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 from the iRMC S2/S3
web interface.
● Global error LED
A global error LED informs you of the status of the managed system at all
times and at the same time shows the CSS (Customer Self Service) status.
● Power LED
The power LED informs you whether the server is currently switched on or
off.
14 iRMC S2/S3
Functions of the iRMC S2/S3
● 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
– reserve it for the management LAN
– set it up for shared operation with the system or
– make it completely available to the system.
The ports marked with a wrench symbol are assigned to the iRMC S2/S3
(see figure 7 on page 42).
● Command line interface (CLP)
In addition to the Remote Manager, the iRMC S2/S3 also supports SMASH
CLP (System Management Architecture for Server Hardware Command
Line Protocol) as standardized by the DMTF (Distributed Management Task
Force).
● Simple configuration - interactive or script-based
The following tools are available for configuring the iRMC S2/S3:
– iRMC web interface
– Server Configuration Manager
– The server management tool IPMIVIEW
– BIOS Setup
It is also possible to carry out configuration with the Server Configuration
Manager or IPMIVIEW using scripts. This means that it is possible to
configure the iRMC S2/S3 when the server is first configured via ServerView
Installation Manager. It is also possible to configure a large number of
servers on the basis of scripts.
● Support for the LocalView service panel
If PRIMERGY servers are equipped with a ServerView local service panel,
this module allows you to determine what module is faulty and whether you
can replace the faulty module yourself.
● Local user management
The iRMC S2/S3 has its own user management function which allows up to
16 users to be created with passwords and to be assigned various rights
depending on the user groups they belong to.
iRMC S2/S3 15
Functions of the iRMC S2/S3
● Global user management using a directory service
The global user IDs for the iRMC S2/S3 are stored centrally in the directory
service's directory. This makes it possible to manage the user identifications
on a central server. They can therefore be used by all the iRMC S2/S3s that
are connected to this server in the network.
The following directory services are currently supported for iRMC S2/S3
user management:
–Microsoft
–Novell
®
Active Directory
®
eDirectory
– OpenLDAP
– OpenDS
● CAS-based single sign-on (SSO) authentication
The iRMC S2/S3 supports Centralized Authentication Service (CAS)
configuration, which allows you to configure the iRMC S2/S3 web interface
for CAS-based single sign-on (SSO) authentication.
The first time a user logs in to an application (e.g. the iRMC S2/S3 web
interface) within the SSO domain of the CAS service, they are prompted for
their credentials by the CAS-specific login screen. Once they have been
successfully authenticated by the CAS service, the user is granted access
to the iRMC S2/S3 web interface as well as to any other service within the
SSO domain without being prompted for login credentials again.
● DNS / DHCP
The iRMC S2/S3 provides support for automatic network configuration. It
has a default name and DHCP support is set by default so that the
iRMC S2/S3 gets its IP address from the DHCP server. The iRMC S2/S3
name is registered by the Domain Name Service (DNS). Up to five DNS
servers are supported. If DNS/DHCP is not available, the iRMC S2/S3 also
supports static IP addresses.
● Power supply
The iRMC S2/S3 is powered by the standby supply of the system.
● Alert management
The alert management facility of the iRMC S2/S3 provides the following
options for forwarding alerts (alerting):
– Platform Event Traps (PET) are sent via SNMP.
– Direct alerting by email.
16 iRMC S2/S3
Functions of the iRMC S2/S3
– A modem can be connected to the serial interface. This can then be used
to send alerts (e.g. to a mobile phone via SMS).
In addition, the iRMC S2/S3 provides the ServerView agents with all the
relevant information.
● Read, filter and save the system event log (SEL).
You can view, save and delete the contents of the SEL
– by using the iRMC S2/S3 web interface or
– by using the Telnet/SSH-based interface (Remote Manager) of the
iRMC S2/S3.
● Read, filter and save the internal event log (iEL).
You can view, save and delete the contents of the iEL
– by using the iRMC S2/S3 web interface or
– by using the Telnet/SSH-based interface (Remote Manager) of the
iRMC S2/S3.
Extended functionality of the iRMC S2/S3
Alongside the standard functionality, the iRMC S2/S3 also supports the
Advanced Video Redirection and Remote Storage functions.
● Advanced Video Redirection (AVR)
The iRMC S2/S3 supports Advanced Video Redirection which offers the
following benefits:
– Operation over a standard web browser. No additional software needs to
be installed in the management station other than the Java Runtime
Environment.
– System-independent graphical and text console redirection (including
mouse and keyboard).
– Remote access for boot monitoring, BIOS administration and operation
of the operating system.
– 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 and video compression.
iRMC S2/S3 17
Functions of the iRMC S2/S3
– Local monitor-off support: It is possible to power down the local screen
of the managed PRIMERGY 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.
– Low bandwidth
In the case of a reduced data transfer rate, you can configure a lower
bandwidth (bits per pixel, bpp) in terms of color depth for your current
AVR session.
● Remote Storage
Remote Storage makes a “virtual” drive available which is physically located
on a remote workstation or made available centrally on the network using a
Remote Storage server.
The “virtual” drives available with Remote Storage are simply managed in
much the same way as local drives and offer the following options:
– Read and write data.
– Boot from Remote Storage.
– Install drivers and small applications.
– Update BIOS from remote workstation.
(BIOS update via USB)
Remote Storage supports the following device types to provide a “virtual
drive” on the remote workstation:
– CD ROM
–DVD ROM
– Memory stick
– Floppy image
– CD ISO image
– DVD ISO image
A Remote Storage server provides an ISO image centrally on the network in
the form of a “virtual drive”.
Remote Storage permits either the simultaneous connection of up to two
“virtual” drives at the remote workstation or the provision of an ISO image
via a Remote Storage server.
18 iRMC S2/S3
Communication interfaces of the iRMC S2/S3
1.3 Communication interfaces of the
iRMC S2/S3
The iRMC S2/S3 provides the following communication interfaces:
● iRMC S2/S3 web interface (web interface)
The connection to the iRMC S2/S3 web server is established over a
standard web browser (e.g. Microsoft Internet Explorer, Mozilla Firefox).
Among other things, the web interface of the iRMC S2/S3 provides you with
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 S2/S3 over the web
interface. Secure access to the iRMC S2/S3 web server can be provided
with HTTPS/SSL.
Operation of the iRMC S2/S3 over the web interface is described in chapter
"iRMC S2/S3 web interface" on page 135.
● Remote Manager: Text-based Telnet/SSH interface via LAN
You can call the Remote Manager
– from the ServerView Remote Management Frontend,
– directly from a Telnet/SSH client.
The alphanumeric user interface of the Remote Manager provides you with
access to system and sensor information, power management functions and
the error event log. In addition, you can launch text console redirection or a
SMASH CLP shell. 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 S2/S3 using the Remote Manager is described in
chapter "iRMC S2/S3 via Telnet/SSH (Remote Manager)" on page 321.
● Remote Manager (Serial): Text-based serial interface over Serial 1
The Remote Manager (serial) interface is identical to the Remote Manager
interface.
iRMC S2/S3 19
Communication protocols used by the iRMC S2/S3
1.4 Communication protocols used by the
iRMC S2/S3
The communication protocols and ports used by the iRMC S2/S3 are shown in
table 1.
Remote side of the
connection
RMCP → 623/UDP
HTTP port → 80/TCP
HTTPs port → 443/TCP
Telnet → 3172/TCP
SSH → 22/TCP
Tr a p → 162/UDP
Email → 25/TCP
Remote Storage → 5901/TCP
VNC ports
Standard port → 80/TCP
Secure port → 443/TCP
Table 1: Communication protocols and ports used by the iRMC S2/S3
Communication
direction
← 623/UDP
← 80/TCP
← 443/TCP
← 3172/TCP
← 22/TCP
← 25/TCP
← 5901/TCP
← 80/TCP
← 443/TCP
iRMC S2/S3 side of the connection
(port number / protocol)
I As of iRMC S2/S3 firmware version 5.00, the Remote Storage port is
used only for the Remote Storage server and client-internal
communications. For integrated Remote Storage (via the Java applet),
the http port is used.
20 iRMC S2/S3
IPMI - technical background
1.5 IPMI - technical background
The iRMC S2/S3 makes the BMC functions available over the IPMI interface.
Intelligent Platform Management
The “Intelligent Platform Management” initiative is a response to the increasing
complexity of modern server systems. A number of manufacturers have joined
this initiative in order to come up with a new solution for monitoring these server
systems.
The term “Intelligent Platform Management” expresses the core aspect of this
approach to the solution: Functions for monitoring and recovery of systems are
implemented directly in the hardware and firmware for platform management.
Objective
The objective was to define a standardized, abstract and message-based
interface between the central system controller (Baseboard Management
Controller - BMC) and intelligent platform management hardware.
The standardization committees combined the central characteristics of various
platform management modules into standardized descriptions.
Definition
The IPMI specification defines:
“IPMI is a hardware level interface specification that is ‘management
software neutral’ providing monitoring and control functions that can be
exposed through standard management software interfaces such as
DMI, WMI, CIM, SNMP, etc. As a hardware level interface, it sits at the
bottom of a typical management software stack” [see section "IPMI and
other management standards" on page 22].
iRMC S2/S3 21
IPMI - technical background
Advantage
The IPMI specifications ensure the independence of functions for inventory,
logging, recovery and monitoring of a system by the system processor, BIOS or
operating system.
This means that a system can still be involved in platform management when it
is shut down and turned off.
IPMI and other management standards
IPMI is best used in conjunction with system management software running
under the relevant operating system. Integration of the IPMI functionality into the
management functionality offered by a management application and the
operating system results in a powerful platform management environment.
An overview of the relationship between IPMI and the management software
stack is shown by figure 2:
Figure 2: IPMI in the management software stack (source: IPMI specification, see section
"References" on page 29)
22 iRMC S2/S3
IPMI - technical background
IPMI, IPMB and ICMB
The IPMI initiative resulted in three central standards:
– IPMI. Intelligent Platform Management Interface Specification
describes the higher-level architecture, the current commands, event
formats, data packets and properties that are used in IPMI-based systems.
– IPMB. Intelligent Platform Management Bus
2
is an I
C based (write only) bus, which provides a standardized connection
between various modules in a common housing.
IPMB can also be used as a standardized interface for remote management
modules.
– ICMB. Intelligent Chassis Management Bus
(Not currently implemented in the ServerView remote management
environment.)
provides a standardized interface for exchange of platform management
information and for control across systems. ICMB is designed in such a way
that it can be implemented with a device that is connected to the IPMB.
IPMI implementation
The core element of an IPMI implementation is the Baseboard Management
Controller (BMC).
The BMC performs the following tasks:
– The BMC organizes the interface between the system management
software and the platform management hardware.
– It provides autonomous functions for monitoring, event logging and recovery
control.
– The BMC acts as a gateway between the system management software and
IPMB.
IPMI allows platform management to be extended: Additional management
controllers can be connected via the IPMB. The IPMB is an I
2
C based serial
bus, which runs between the main modules of the system. It is used for
communication with and between the management controllers.
With the support of multiple management controllers, IPMI provides a scalable
architecture: A complex server system can use multiple controllers for
monitoring different subsystems, e.g. power supplies, hot swap RAID drive
modules etc.
iRMC S2/S3 23
IPMI - technical background
In addition, IPMI provides ‘low level’ I2C commands, which can be accessed via
a management controller connected to the IPMB on 'unintelligent' I
2
C modules
that cannot process IPMI commands.
An overview of the fundamental elements of an IPMI implementation is available
in figure 3 on page 25.
24 iRMC S2/S3
IPMI - technical background
Figure 3: IPMI block diagram (source: IPMI specification, see section
"References" on page 29)
iRMC S2/S3 25
IPMI - technical background
IPMI and “in band” and “out of band” management
In the field of system management, a distinction is made between “in-band” and
“out-of-band” management:
– The term “in-band” management is used when the operating system is
running on the managed server.
– The term “out-of-band” management is used when the operating system is
not running on the managed server, for instance if the hardware is faulty.
As different interfaces are available in an environment with IPMI compatible
systems, you can manage IPMI compatible systems either “in band” or “out of
band”.
IPMI-over-LAN
“IPMI-over-LAN” is the current name for the specification of the LAN interface in
the IPMI standard. This specification stipulates how IPMI messages can be sent
to or from the BMC of a managed system - encapsulated in RMCP (Remote
Management Control Protocol) data packets. These RMCP data packets are
transferred via an Ethernet LAN connection using the UDP (User Datagram
Protocol) under IPv4 (Internet Protocol Version 4).
The RMCP protocol has been specified to support the management of system
statuses in which the operating system is not running. The RMCP is a simple
inquiry/response protocol.
The interface for such a connection is provided on an onboard LAN controller
assigned to the BMC.
I The interface can only be provided by an on-board LAN controller, not by
an inserted LAN card.
26 iRMC S2/S3
IPMI - technical background
Of the two ports that RCMP uses under UDP, the BMC communicates with the
LAN controller via port 623 (primary RMCP Port).
Figure 4: BMC and LAN controller
Serial Over LAN interface (SOL)
“Serial Over LAN” is an interface compliant with the IPMI V2.0 standard, which
controls transfer of serial data over a LAN connection. In particular, SOL
specifies the packet formats and protocols for transferring serial data streams
over a LAN between the serial controller on the managed computer and a
remote workstation. SOL is based on the IPMI-over-LAN specification.
In order to establish an SOL connection, a remote management application first
initiates an IPMI-over-LAN session with the BMC. After this has been done, the
SOL services can be activated from the remote workstation. The data traffic
between the serial controller and the remote workstation is handled over the
same IPMI session as the IPMI commands.
As soon as an SOL connection has been established, data transfer between the
serial controller and the remote workstation is carried out as follows:
– Transfer from the serial controller to the remote workstation:
The data stream issued by the serial controller is partitioned by the BMC,
packaged and then sent to the remote workstation over the LAN.
– Transfer from the remote workstation to the serial controller:
BMC unpacks the characters contained in the packages sent by the remote
workstation and forwards them to the serial controller as a character stream.
iRMC S2/S3 27
IPMI - technical background
Figure 5: BMC and SOL
The SOL character data is then exchanged between the BMC of the managed
system and the remote workstation as SOL messages. The SOL messages are
encapsulated in RMCP+ data packets and transferred in UDP datagrams over
an Ethernet LAN connection using IPv4 (Internet Protocol Version 4). The
RMCP+ protocol is based on the RMCP protocol, but includes extensions for
encryption, authentication, etc.
Serial over LAN permits “headless” management by console redirection by both
the BIOS and the operating system of the managed server. High-cost
concentrator solutions are not required.
Channel concept under IPMI
‘Channels’ provide the mechanisms with which IPMI messages are routed to
the BMC via various connection carriers. Up to nine channels can be supported.
The system interface and the primary IPMB are fixed. The other seven channels
are available for the implementation.
Channels can be either ‘session based’ or ‘sessionless’. The ‘session’ concept
has two meanings: It is either a concept for user authentication (see the section
"User identifications" on page 29) or a concept for routing multiple IPMI
message streams via a single channel.
Examples of ‘session based’ channels are LAN channels or serial / modem
channels. Examples of ‘sessionless’ channels are the system interface and the
IPMB.
28 iRMC S2/S3
Data Center Management Interface (DCMI)
User identifications
For ‘session based’ channels (see the section "Channel concept under IPMI" on
page 28), a user login is necessary. By contrast, the ‘sessionless’ channels
have no user authentication.
Under IPMI, the user configuration is channel specific. Thus, users can have
different privileges depending on whether they are accessing the BMC via the
LAN channel or the serial channel.
References
Information about the IPMI standards can be found on the Internet:
http://developer.intel.com/design/servers/ipmi/index.htm
1.6 DCMI (Data Center Management Interface)
The iRMC S2/S3 supports the DCMI (Data Center Management Interface)
protocol, which is compliant with the IPMI V2.0 standard. DCMI has been
designed to improve manageability and energy efficiency of server systems that
are deployed in large data centers.
To meet the hardware management requirements of servers within data
centers, DCMI supports, among others, the following key features:
– Inventory functions (server identification)
– Power Management and power monitoring
– Power consumption monitoring and control
– Event logging
– Temperature monitoring
Detailed information about DCMI can be found on the DCMI home page:
http://www.intel.com/technology/product/DCMI
iRMC S2/S3 29
Changes compared with the previous version
1.7 Changes since the previous versions of the manual
iRMC S2/S3 - integrated Remote Management Controller
(edition Ju
This manual refers to the iRMC S2/S3 firmware version 6.5x and replaces the
following online manual: “iRMC S2/S3 - integrated Remote Management
Controller”, May 2012 edition.
The manual includes the following updates:
● The "0 Watt Technology" feature is described in Chapter "7 iRMC S2/S3 web
interface".
● The former chapter "12 IPMI OEM Commands" has been expanded and is
now an Appendix ("12 Appendix") to the manual, containing the following
sections:
– "12.1 IPMI OEM Commands supported by the iRMC S2/S3" (former
– "12.2 Configuring the iRMC S2/S3 via SCCI and scripted configuration"
ly 2012)
chapter "12 IPMI OEM Commands")
(new section).
iRMC S2/S3 - integrated Remote Management Controller
(edition May 2012)
This manual refers to the iRMC S2/S3 firmware version 6.5x and replaces the
following online manual: “iRMC S2 - integrated Remote Management
Controller”, November 2011 edition.
New iRMC S2/S3 features (described in Chapter "7 iRMC S2/S3 web
interface"):
● Agentless HDD monitoring (iRMC S3 only)
If the managed server supports the "agentless HDD monitoring" feature, the
HDD<n> status of each individual HDD is directly read and reported to the
iRMC S2/S3 via a dedicated lightpath status sensor and thus can be
displayed even in the case no ServerView agents are running.
● Backing up/restoring BIOS settings, flashing BIOS
If the BIOS of the managed server meets the corresponding feature
requirements, the iRMC S2/S3 allows you to perform the following actions:
30 iRMC S2/S3
Loading...