You are on page 1of 532

PRIMERGY ServerView Suite

iRMC S2 - integrated Remote Management Controller (Firmware Version 3.77A)

Edition December 2009

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@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 1.1 1.2 1.3 1.4 1.5 1.6 2 2.1 2.2 2.3 3 3.1 3.1.1 3.1.1.1 3.1.1.2 3.1.1.3 3.1.2 3.1.3 3.1.4 3.2 3.2.1 3.2.2 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Purpose and target groups of the manual . . . . . . . . . . 14 Functions of the iRMC S2 (overview) . . . . . . . . . . . . . 15 Communication interfaces of the iRMC S2 . . . . . . . . . . 21 IPMI - technical background . . . . . . . . . . . . . . . . . . 22 Changes since the previous manual . . . . . . . . . . . . . 31 Notational conventions . . . . . . . . . . . . . . . . . . . . 32

Logging on to the iRMC S2 for the first time . . . . . . . . . 33 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 33 iRMC S2 factory defaults . . . . . . . . . . . . . . . . . . . 34

Logging into the iRMC S2 web interface . . . . . . . . . . . 35 Configuring the iRMC S2 . . . . . . . . . . . . . . . . . . . 37 . . 38 . . 39 . . 39 . . 40 . . 40 . . 40 . . 41 . . 43

Configuring the LAN interface of the iRMC S2 . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . Connected to the correct LAN port? . . . . . . . . . . . Interaction between the IP addresses of the iRMC S2 and the system . . . . . . . . . . . . . . . . . . . . . . Access from a different subnet . . . . . . . . . . . . . . Configuring the LAN interface: Configuration tools . . . . . Configuring the LAN interface using the BIOS / TrustedCore Setup program . . . . . . . . . . . . . . . . . . . . . . . . Testing the LAN interface . . . . . . . . . . . . . . . . . .

Configuring text console redirection via LAN using the BIOS/TrustedCore Setup program . . . . . . . . . . . . . . 44 Configuring text console redirection . . . . . . . . . . . . . . . 45 Using console redirection while the operating system is running 49

iRMC S2

Contents 3.3 3.3.1 3.3.2 3.4 3.4.1 3.4.2 3.4.3 3.5 3.5.1 3.5.2 4 4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 4.3.3.1 4.3.3.2 4.3.3.3 4.3.3.4 4.4 4.4.1 4.4.2 4.4.2.1 4.4.2.2 4.4.2.3 4.4.2.4 4.4.2.5 Configuring and using the serial interface of the iRMC S2 . . 51 Configuring the serial interface . . . . . . . . . . . . . . . . . . 52 Using the Remote Manager (Serial) interface . . . . . . . . . . 54 Configuring the iRMC S2 over the iRMC S2 web interface Configuring the LAN parameters . . . . . . . . . . . . . . . Configuring alerting . . . . . . . . . . . . . . . . . . . . . . Configuring text console redirection . . . . . . . . . . . . . . . . . . . . . 55 55 56 56

Configuring iRMC S2 using the Server Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Configuring the LAN parameters . . . . . . . . . . . . . . . . . 57 Configuring alerting . . . . . . . . . . . . . . . . . . . . . . . . 58 User management for the iRMC S2 . . . . . . . . . . . . . . . 59 User management concept for the iRMC S2 . . . . . . . . . . 60 User permissions . . . . . . . . . . . . . . . . . . . . . . . . 62 Local user management for the iRMC S2 . . . . . . . . . . Local user management using the iRMC S2 web interface . . . . . . . . . . . . . . . . . . . . . Local user management via the Server Configuration Manager SSHv2 public key authentication for iRMC S2 users . . . . . . Creating public and private SSHv2 keys . . . . . . . . . . Loading the public SSHv2 key onto the iRMC S2 from a file Configuring PuTTY and the OpenSSH client for using the public SSHv2 key . . . . . . . . . . . . . . . . . . . . Example: Public SSHv2 key . . . . . . . . . . . . . . . . . Global user management for the iRMC S2 . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . iRMC S2 user management via an LDAP directory service (concept) . . . . . . . . . . . . . Global iRMC S2 user management using permission groups and roles . . . . . . . . . . . . . . . . . . . Organizational units (OU) SVS and iRMCgroups . . . Cross-server, global user permissions . . . . . . . . iRMCgroups: Permission profiles are defined via permission groups . . . . . . . . . . . . . . . . . . . SVS: Permission profiles are defined via roles . . . . . 64 . . . . . 64 66 68 70 74

. 76 . 82

. . . . 83 . . . . 84 . . . . 85 . . . . 85 . . . . 87 . . . . 89 . . . . 91 . . . . 94

iRMC S2

Contents 4.4.3 4.4.3.1 4.4.3.2 4.4.3.3 4.4.3.4 4.4.3.5 4.4.3.6 4.4.4 4.4.4.1 4.4.4.2 4.4.4.3 4.4.4.4 4.4.5 4.4.5.1 4.4.5.2 4.4.6 4.4.6.1 4.4.6.2 4.4.6.3 4.4.6.4 4.4.6.5 4.4.6.6 4.4.7 4.4.7.1 4.4.7.2 4.4.7.3 4.4.7.4 4.4.7.5 4.4.8 4.4.8.1 4.4.8.2 4.4.8.3 4.4.9 SVS_LdapDeployer - Generating, maintaining and deleting the “SVS” and “iRMCgroups” structures . . . . . . . . . . . . . Configuration file (XML file) . . . . . . . . . . . . . . . . . Starting SVS_LdapDeployer . . . . . . . . . . . . . . . . . -deploy: Create or modify an LDAP structure . . . . . . . . -delete: Deleting an LDAP structure . . . . . . . . . . . . . -import: Importing an LDAP v1 structure into an LDAP v2 structure . . . . . . . . . . . . . . . . . . . . . . . . . . . -synchronize: Synchronizing changes made in an LDAP v2 structure with an LDAP v1 structure . . . . . . . . . . . . . Typical application scenarios . . . . . . . . . . . . . . . . . . Performing an initial configuration in which LDAP v1 and LDAP v2 structures coexist . . . . . . . . . . . . . . . Importing an LDAP v1 structure into an LDAP v2 structure . Re-generating or expanding an LDAP v2 structure . . . . . Re-generating an LDAP v2 structure and prompting for and saving authentication data . . . . . . . . . . . . . . . . iRMC S2 user management via Microsoft Active Directory . . . Configuring iRMC S2 LDAP/SSL access at the Active Directory server . . . . . . . . . . . . . . . . . . . . Assigning an iRMC S2 user to a role (permission group) . . iRMC S2 user management via Novell eDirectory . . . . . . . Software components and system requirements . . . . . . Installing Novell eDirectory . . . . . . . . . . . . . . . . . Configuring Novell eDirectory . . . . . . . . . . . . . . . . Integrating iRMC S2 user management in Novell eDirectory Assigning an iRMC S2 user to a permission group . . . . . Tips on administering Novell eDirectory. . . . . . . . . . . . iRMC S2 user management via OpenLDAP . . . . . . . . . . Installing OpenLDAP . . . . . . . . . . . . . . . . . . . . . Creating SSL certificates . . . . . . . . . . . . . . . . . . . Configuring OpenLDAP . . . . . . . . . . . . . . . . . . . Integrating iRMC S2 user management in OpenLDAP. . . . Tips on OpenLDAP administration . . . . . . . . . . . . . . Configuring email alerting to global iRMC S2 users . . . . . . . Global email alerting . . . . . . . . . . . . . . . . . . . . . Displaying alert roles . . . . . . . . . . . . . . . . . . . . . Assigning iRMC S2 users to an alert role . . . . . . . . . . SSL copyright . . . . . . . . . . . . . . . . . . . . . . . . . .

96 96 97 99 101 102 103 105 105 105 106 106 107 108 113 120 120 121 128 134 140 144 147 147 147 148 150 154 156 157 161 163 164

iRMC S2

Contents 5 5.1 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.4.1 5.2.4.2 5.2.4.3 5.3 5.3.1 5.3.2 5.3.3 5.3.4 6 6.1 6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.2 6.2.1 6.2.1.1 6.2.1.2 6.2.1.3 6.2.2 7 7.1 7.2 Advanced Video Redirection (AVR) . . . . . . . . . . . . . 167

Requirements: Check the AVR settings . . . . . . . . . . . 168 Using AVR . . . . . . . . . . . . . . . . . . . . . . . Parallel AVR sessions . . . . . . . . . . . . . . . . . . “Local Monitor Off” function . . . . . . . . . . . . . . . Redirecting the keyboard . . . . . . . . . . . . . . . . Redirecting the mouse . . . . . . . . . . . . . . . . . Synchronizing the mouse pointer . . . . . . . . . . Managed Windows server: Adjusting the settings for synchronization of the mouse pointers . . . . . . . Managed Linux server: Adjusting the settings for synchronization of the mouse pointers . . . . . . . Menus of the AVR window Extras menu . . . . . . . . Remote Storage menu . . . Languages menu . . . . . . Preferences menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 171 172 173 175 175

. . . . 177 . . . . 180 . . . . . . . . . . . . . . . . . . . . 183 184 187 187 188

Remote Storage . . . . . . . . . . . . . . . . . . . . . . . . 191 Providing remote storage at the remote workstation Starting Remote Storage . . . . . . . . . . . . . . . . Provision of storage media for Remote Storage . . . . Connecting storage media as remote storage . . . . . Clearing Remote Storage connections . . . . . . . . . Removing the storage medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 193 196 200 204 205 206 207 207 213 214 219

Providing remote storage via a Remote Storage server . . Remote Storage server under Windows . . . . . . . . . . . . Installing the Remote Storage server . . . . . . . . . . . . Remote Storage server execution modes . . . . . . . . . Configuring, starting and exiting the Remote Storage server Remote Storage server (iRMCSrv) under Linux . . . . . . . .

iRMC S2 web interface . . . . . . . . . . . . . . . . . . . . 221 Logging into the iRMC S2 web interface . . . . . . . . . . . 222 Required user permissions . . . . . . . . . . . . . . . . . 224

iRMC S2

Contents 7.3 7.4 7.4.1 7.4.2 7.5 7.5.1 7.5.2 7.5.3 7.5.4 7.5.5 7.6 7.6.1 7.6.2 7.6.3 7.7 7.7.1 7.7.2 7.7.3 7.8 7.8.1 7.8.2 7.8.3 7.8.4 7.8.5 7.9 7.9.1 7.9.2 Structure of the user interface . . . . . . . . . . . . . . . . 228

System Information Information on the server . . . . . . . . . . . . . . . . . . . 231 System Overview General information on the server . . . . . . . . . . . . . . . 232 System Component Information Information on the server components . . . . . . . . . . . . . 237 iRMC S2 - Information, firmware and certificates . . . iRMC S2 Information - Information on the iRMC S2 . . . . Save iRMC S2 Firmware Settings -Save firmware settings Certificate Upload - Load the DSA/RSA certificate and private DSA/RSA key . . . . . . . . . . . . . . . . . . . Generate a self-signed Certificate - Generate self-signed RSA certificate . . . . . . . . . . . . . . . . . . . . . . . iRMC S2 Firmware Update . . . . . . . . . . . . . . . . . . . 240 . . . 241 . . . 245 . . . 247 . . . 254 . . . 256 261 262 267 270 271 272 278 279 283 284 286 288 289 290

Power Management . . . . . . . . . . . . . . . . . . . . . . Power On/Off - power the server up/down . . . . . . . . . . . . Power Options - Configuring power management for the server Power Supply Info - Power supply and IDPROM data for the FRU components . . . . . . . . . . . . . . . . . . . . Power Consumption - Control the power consumption of the server . . . . . . . . . . . . . . . . . . . . . . . . . . Power Consumption Configuration - Configure power consumption of the server . . . . . . . . . . . . . . . . . . . . Current Power Consumption - Show the current power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . Power Consumption History - Show server power consumption Sensors - Check status of the sensors . . . . . . . . . . Fans - Check fans . . . . . . . . . . . . . . . . . . . . . . Temperature - Check temperature sensors . . . . . . . . . Voltages - Check voltage sensors . . . . . . . . . . . . . . Power Supply - Check power supply . . . . . . . . . . . . Component Status - Check status of the server components . . . . . . . . . . . .

System Event Log (SEL) - Displaying and configuring the server’s event log . . . . . . . . . . . . . . . . . . . . . . . 291 System Event Log Content Show information on the SEL and SEL entries . . . . . . . . . 292 System Event Log Configuration - Configure the SEL . . . . . . 295

iRMC S2

Contents 7.10 7.11 7.11.1 7.11.2 7.11.3 7.11.4 7.12 7.12.1 7.12.2 7.12.3 Server Management Information - Configuring the server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Network Settings - Configure the LAN parameters . . . . Network Interface - Configure Ethernet settings on the iRMC S2 . . . . . . . . . . . . . . . . . . . . . . . . . . . Ports and Network Services - Configuring ports and network services . . . . . . . . . . . . . . . . . . . . . . . . . . . . DHCP Configuration - Configuring the host name for the iRMC S2 . . . . . . . . . . . . . . . . . . . . . . . . . . . DNS Settings - Enable DNS for the iRMC S2 . . . . . . . . . Alerting - Configure alerting . . . . . . . . . . . . . SNMP Trap Alerting - Configure SNMP trap alerting . . Serial / Modem Alerting - Configure alerting via modem Email Alerting - Configure email alerting . . . . . . . . . . . . . . . . . . . . . 301 . 302 . 305 . 309 . 311 . . . . 313 314 315 317 323 323 325 326 333 336 340

7.13 User Management - Manage users . . . . . . . . . . . . . . 7.13.1 iRMC S2 User - local user management on the iRMC S2 . . . 7.13.1.1 New User Configuration - Configuring a new user . . . . . 7.13.1.2 User “<name>” Configuration - User configuration (details) . 7.13.2 Directory Service Configuration (LDAP) Configuring the directory service at the iRMC S2 . . . . . . . 7.13.2.1 Configuring iRMC S2 for Microsoft Active Directory . . . . 7.13.2.2 Configuring iRMC S2 for Novell eDirectory / OpenLDAP . . 7.14 7.14.1 Console Redirection - Redirecting the console . . . . BIOS Text Console Configure and start text console redirection . . . . . . . 7.14.1.1 BIOS Console Redirection Options Configure text console redirection . . . . . . . . . . . 7.14.1.2 Text Console Redirection (via Serial over LAN) Start text console redirection . . . . . . . . . . . . . 7.14.1.3 Text console redirection while the operating system is running . . . . . . . . . . . . . . . . . . . . . . . . 7.14.2 Advanced Video Redirection Start Advanced Video Redirection (AVR) . . . . . . . . . 7.15 7.16

. . . 345 . . . 345 . . . 347 . . . 349 . . . 354 . . . 356

Remote Storage . . . . . . . . . . . . . . . . . . . . . . . . 366 Operating iRMC S2 via Telnet/SSH (Remote Manager) . . . 368

iRMC S2

Contents 8 8.1 8.2 8.2.1 8.2.2 8.2.3 8.2.4 8.2.5 8.2.6 8.2.7 8.2.8 8.2.9 8.2.10 8.2.11 8.2.12 8.2.13 8.2.14 9 iRMC S2 via Telnet/SSH (Remote Manager) . . . . . . . . . 373

Operating the iRMC S2 using the ServerView Remote Management Frontend . . . . . . . . . . . . . . . . . . . . . 374 Remote Manager . . . . . . . . . . . . . . . . . . . . . Operating Remote Manager . . . . . . . . . . . . . . . . Overview of menus . . . . . . . . . . . . . . . . . . . . Logging in . . . . . . . . . . . . . . . . . . . . . . . . . Main menu of the Remote Manager . . . . . . . . . . . . Required user permissions . . . . . . . . . . . . . . . . Change the password . . . . . . . . . . . . . . . . . . . System Information - Information on the managed server . Power Management . . . . . . . . . . . . . . . . . . . . Enclosure Information - System event log and status of the sensors . . . . . . . . . . . . . . . . . . . . . . . Service processor - IP parameters, identification LED and iRMC S2 reset . . . . . . . . . . . . . . . . . . . . . . . Console Redirection (EMS/SAC) - Start text console redirection . . . . . . . . . . . . . . . . . . . . . . . . . Start a Command Line shell... - Start a SMASH CLP shell Console Logging - Redirect message output to the text console (serial) . . . . . . . . . . . . . . . . . . . . Command Line Protocol (CLP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 375 376 378 380 382 383 384 385

. . . 387 . . . 391 . . . 392 . . . 393 . . . 394 . . . 397

Configuring iRMC S2 using the Server Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 Starting system configuration . . . . . . . . . . Calling the Server Configuration Manager from the ServerView Installation Manager . . . . . . . . . Calling the Server Configuration Manager from the Windows Start menu . . . . . . . . . . . . . . . . Calling the Server Configuration Manager from the Operations Manager . . . . . . . . . . . . . . . . . . . . . . . 402 . . . . . . . 402 . . . . . . . 403 . . . . . . . 405

9.1 9.1.1 9.1.2 9.1.3 9.2 9.3 9.4

iRMC Power Consumption Control - Control the power consumption of the server . . . . . . . . . . . . . . . . . . . 410 iRMC Advanced Features - Remote Storage Server, License Key and HP SIM Integration . . . . . . . . . . . . . 412 ASR&R Fan Settings . . . . . . . . . . . . . . . . . . . . . . 414

iRMC S2

Contents 9.5 9.6 9.7 9.8 9.9 9.10 9.11 9.12 9.13 9.14 9.14.1 9.14.2 10 10.1 10.2 10.3 10.3.1 10.3.2 10.3.3 10.3.4 10.3.5 10.4 10.5 ASR&R Temperature Settings . . . . . . . . . . . . . . . . 416 iRMC LAN Interface - Configure LAN parameters of the iRMC S2 . . . . . . . . . . . . . . . . . . . . . . . . . 418 iRMC Networking Ports - Configuring ports and network services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 iRMC DNS Registration - Configuring the host name for the iRMC S2 . . . . . . . . . . . . . . . . . . . . . . . . 423 iRMC DNS Server - Activating DNS for the iRMC S2 . . . . 425 iRMC EMail Alerting -Configure email alerting . . . . . . . 427 iRMC Mail Format Settings - Mail-format-dependent settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 iRMC SNMP Alerting - Configure SNMP Trap alerting . . . 432

iRMC User Management - Local user management on the iRMC S2 . . . . . . . . . . . . . . . . . . . . . . . . 433 iRMC Directory Service - Configuring the directory service 439 Configure iRMC S2 for Microsoft Active Directory . . . . . . . 441 Configuring iRMC S2 for Novell eDirectory / OpenLDAP . . . . 443 Firmware update . . . . . . . . . . . . . . . . . . . . . . . . 447 iRMC S2 firmware (overview) . . . . . . . . . . . . . . . . . 448 Setting up the USB memory stick . . . . . . . . . . . . . . 451 Updating firmware images . . . . . . . . . . . . . . . . over the iRMC S2 web interface . . . . . . . . . . . . . . Update using the ServerView Update Manager . . . . . . Online update using ServerView Update Manager Express or ASP . . . . . . . . . . . . . . . . . . . . . . . . . . . Update using the operating system flash tools. . . . . . . . Update via the FlashDisk menu . . . . . . . . . . . . . . . . . 454 . . 454 . . 454 . . 455 . . 455 . . 457

Emergency flash . . . . . . . . . . . . . . . . . . . . . . . . 459 Flash tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

iRMC S2

. . . . . . iRMC S2-specific commands .3 12. . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . 463 Installing the operating system via iRMC S2 general procedure . . . . . .2 12. . . . .2. . . . 519 iRMC S2 . . . . . . . . . . . . 477 Installing Linux on the managed server after configuration . . . . . . . . SCCI-compliant Power On/Off commands . . . . . . .1 11. . . . . . . . 489 489 490 495 497 498 502 504 11. . . 466 Booting the managed server from PRIMERGY ServerView Suite DVD 1 and configuring it with the Installation Manager .4 12. . . . . . .4 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Remote installation of the operating system via iRMC S2 . . . . . . . . . . . . . . . . . .1 12. . . . . BIOS-specific commands . 487 Overview . . . . . . . . . . . .2. . . 470 Installing the operating system on the managed server after configuration . . . . . . . . . . . . . . . . . 477 Installing Windows on the managed server after configuration . . . . . . .6 12. . . . . . . . . . . . . Firmware-specific commands . . . . . . . . .2. .1 12. . . . . . . . . . . . .2. . . . 464 Connecting a storage medium as remote storage .5 12. .7 Related Publications . .1 11. . . . . . . . . . . . . . . . . . . . . . SCCI-compliant communication commands SCCI-compliant signaling command . . . . . . . . .2 12. . . . .Contents 11 11. . . . . . . . . . . .4. . . . . 487 Description of the IPMI OEM commands Description format . . . . .2 12 12. . . . . . 481 IPMI OEM Commands . . .2 11. . . . . . . . . . . . . . 513 Index .4.2. . . . . . . . .

.

message-based interface between the central system controller (Baseboard Management Controller .technical background” on page 22. In response to this development.1 Preface Modern server systems are becoming increasingly complex. abstract. The iRMC S2 (integrated Remote Management Controller) is a BMC with integrated LAN connection and extended functionality which was previously only available using additional plug-in boards. in particular over PRIMERGY servers whose system status is “out-of-band”. The requirements with respect to the management of such systems are growing accordingly. the iRMC S2 offers comprehensive control over PRIMERGY servers. In this way. Figure 1: iRMC S2 on the system board of a PRIMERGY server iRMC S2 13 . For further details on IPMI.BMC) and intelligent hardware for platform management. irrespective of the system status. please refer to section “IPMI . such as the RemoteView Service Board (RSB). a number of vendors founded the “Intelligent Platform Management Interface” (IPMI) initiative with the objective of defining a standardized.

com 14 iRMC S2 . Other information http://www. its own web server. 1. The iRMC S2 remains powered up even when the server is in stand-by mode. contact the service and support partners responsible for you. This manual describes how to configure the iRMC S2 and the various user interfaces available.ts. separate user management and independent alert management. Service If you have any further questions on remote management for PRIMERGY servers. and service staff who have a sound knowledge of hardware and software. the iRMC S2 has its own operating system. Configuring the iRMC S2 with the Server Configuration Manager Updating the firmware Remote installation of the operating system via iRMC S2 IPMI OEM Commands Further documentation on ServerView remote management You will find additional manuals on the topic of ServerView remote management and on the PRIMERGY ServerView suite in the chapter “Related Publications” on page 513.1 Purpose and target groups of the manual This manual is aimed at system administrators.Purpose and target groups of the manual Preface As an autonomous system on the system board of a modern PRIMERGY server.fujitsu. It provides basic information on the technology behind IPMI and deals with the following aspects in detail: – – – – – – – – – – – Logging on to the iRMC S2 Configuring the iRMC S2 User management on the iRMC S2 Advanced Video Redirection via iRMC S2 Remote Storage via iRMC S2 iRMC S2 web interface Telnet/SSH-based interface (Remote Manager) of the iRMC S2. network administrators.

● Power management Irrespective of the status of the system. To use AVR and Remote Storage. you have the following options for powering the managed server up or down from the remote workstation – using the iRMC S2 web interface – using the Remote Manager and the command line interface (CLP) – with a script. The Remote Manager is an alphanumeric user interface for the iRMC S2. This means that it is possible to start the iRMC S2 web interface and text console redirection using the ServerView Remote Management Frontend directly from ServerView Operations Manager. you require a valid license key. ● Security (SSL. With Advanced Video Redirection (AVR) and Remote Storage.Preface Functions of the iRMC S2 1.2 Functions of the iRMC S2 (overview) The iRMC S2 supports a wide range of functions that are provided by default. which can be purchased separately. SSH) Secure access to the Web server and secure graphical console redirection including mouse and keyboard can be provided over HTTPS/SSL. iRMC S2 15 . the iRMC S2 also provides two additional advanced features for the remote management of PRIMERGY servers. Standard functions of the iRMC S2 ● Browser access The iRMC S2 features its own web server which can be accessed by the management station from a standard web browser. An encrypted connection protected using SSH mechanisms can be set up to access the iRMC S2 using the Remote Manager. ● ServerView Integration The ServerView agents detect the iRMC S2 and automatically assign it to the relevant server.

sensors and the power supply on the iRMC S2 web interface provide information in a separate column as to whether the server component affected is a CSS component or not. ● “Headless” system operation The managed server does not require a mouse. ● Customer Self Service (CSS) Summary tables for the server components. In addition. In addition. This calls the Remote Manager. ● Identification LED To facilitate identification of the system.Functions of the iRMC S2 ● Preface Power consumption control The iRMC S2 allows comprehensive power consumption control on the managed server. far simpler cabling in the rack and increased security. ● Power LED The power LED informs you whether the server is currently switched on or off. ● 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. 16 iRMC S2 . via which you can start a text console redirection session. for instance if it is installed in a fully populated rack. The benefits of this include lower costs. event logging and recovery control. You can switch between these modes as required. ● Text console redirection You can start a Telnet/SSH session to the iRMC S2 from the ServerView Remote Management Frontend. error list of the system event log (SEL) shows for every event whether it has been triggered by a CSS component. you can activate the identification LED from the iRMC S2 web interface. ● Basic functions of a BMC The iRMC S2 supports the basic functions of a BMC such as voltage monitoring. you can specify the mode (minimum power consumption or maximum performance) that the iRMC S2 uses to control power consumption on the managed server. monitor or keyboard to be connected.

the iRMC S2 also supports SMASH CLP (System Management Architecture for Server Hardware Command Line Protocol) as standardized by the DMTF (Distributed Management Task Force). 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. this module allows you to determine what module is faulty and whether you can replace the faulty module yourself. ● Command line interface (CLP) In addition to the Remote Manager. the LAN interface of the fitted system NIC (Network Interface Card) on the server is reserved for the management LAN. This means that it is possible to configure the iRMC S2 when the server is first configured with ServerStart.interactive or script-based The following tools are available for configuring the iRMC S2: – – – – 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. ● Simple configuration .Preface ● Functions of the iRMC S2 LAN On some systems. iRMC S2 17 . ● Support for the LocalView service panel If PRIMERGY servers are equipped with a ServerView local service panel. It is also possible to configure a large number of servers on the basis of scripts. The ports marked with a wrench symbol are assigned to the iRMC S2 (see figure 7 on page 39).

● Global user management using a directory service The global user IDs for the iRMC S2 are stored centrally in the directory service's directory. ● Alert management The alert management facility of the iRMC S2 provides the following options for forwarding alerts (alerting): – Platform Event Traps (PET) are sent via SNMP. – Direct alerting by email. to a mobile phone via SMS). ● Power supply The iRMC S2 is powered by the standby supply of the system. This can then be used to send alerts (e. the iRMC S2 provides the ServerView agents with all the relevant information. If DNS/DHCP is not available. In addition. – A modem can be connected to the serial interface. It has a default name and DHCP support is set by default so that the iRMC S2 gets its IP address from the DHCP server. This makes it possible to manage the user identifications on a central server. 18 iRMC S2 . The iRMC S2 name is registered by the Domain Name Service (DNS). Up to five DNS servers are supported. They can therefore be used by all the iRMCs that are connected to this server in the network.Functions of the iRMC S2 ● Preface Local user management The iRMC S2 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. The following directory services are currently supported for iRMC S2 user management: – Microsoft® Active Directory – Novell® eDirectory – OpenLDAP ● DNS / DHCP The iRMC S2 provides support for automatic network configuration.g. the iRMC S2 also supports static IP addresses.

Preface ● Functions of the iRMC S2 Read. No additional software needs to be installed in the management station other than the Java Runtime Environment. It also reduces the load on the network by using hardware and video compression. – Remote access for boot monitoring. – System-independent graphical and text console redirection (including mouse and keyboard). – AVR supports up to two simultaneous “virtual connections” for working on a server from a different location. BIOS administration and operation of the operating system. ● Advanced Video Redirection (AVR) The iRMC S2 supports Advanced Video Redirection which offers the following benefits: – Operation over a standard web browser. iRMC S2 19 . – using the iRMC S2 web interface or – using the Telnet/SSH-based interface (Remote Manager) of the iRMC S2. save and delete the contents of the SEL. Extended functionality of the iRMC S2 Alongside the standard functionality. filter and save the system event log (SEL). You can view. – 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. the iRMC S2 also supports the Advanced Video Redirection and Remote Storage functions.

Boot from Remote Storage. (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”. Update BIOS from remote workstation. 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.Functions of the iRMC S2 ● Preface 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. Install drivers and small applications. 20 iRMC S2 . 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.

Preface

Communication interfaces of the iRMC S2

1.3

Communication interfaces of the iRMC S2

The iRMC S2 provides the following communication interfaces: iRMC S2 web interface (web interface) The connection to the iRMC S2 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 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 over the web interface. Secure access to the iRMC S2 web server can be provided with HTTPS/SSL. Operation of the iRMC S2 over the web interface is described in chapter “iRMC S2 web interface” on page 221.

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 using the Remote Manager is described in chapter “iRMC S2 via Telnet/SSH (Remote Manager)” on page 373.

Remote Manager (Serial): Text-based serial interface over Serial 1 The Remote Manager (serial) interface is identical to the Remote Manager interface.

iRMC S2

21

IPMI - technical background

Preface

1.4

IPMI - technical background

The iRMC S2 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 23].

22

iRMC S2

Preface Advantage

IPMI - technical background

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 30)

iRMC S2

23

IPMI - technical background IPMI, IPMB and ICMB The IPMI initiative resulted in three central standards:

Preface

– 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 is an I2C 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 I2C 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.

24

iRMC S2

Preface

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' I2C modules that cannot process IPMI commands. An overview of the fundamental elements of an IPMI implementation is available in figure 3 on page 26.

iRMC S2

25

IPMI - technical background

Preface

Figure 3: IPMI block diagram (source: IPMI specification, see section “References” on page 30)

26

iRMC S2

Preface

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.

iRMC S2

27

IPMI - technical background

Preface

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.

28

iRMC S2

Preface

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 30) 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.

iRMC S2

29

IPMI - technical background User identifications

Preface

For ‘session based’ channels (see the section “Channel concept under IPMI” on page 29), 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

30

iRMC S2

5 Changes since the previous manual This edition replaces the following online manual: “iRMC S2 .integrated Remote Management Controller”. iRMC S2 31 .Preface Changes compared with the previous version 1. “Remote Storage”: Additional description: Remote Storage under Linux. October 2009 edition. The manual has been supplemented as follows: ● Chapter 6.

32 iRMC S2 . options. This symbol is used to highlight important information and tips. this is indicated for instance by [SHIFT] . If uppercase characters are to be entered explicitly. Keys are shown as they appear on the keyboard. This symbol indicates an action which you must carry out. Indicate a list of alternatives separated by “|”. files and paths are shown in italics. the title of the chapter or section is named and the page number given refers to the start of the section. monospaced font. If two keys are to be pressed simultaneously. Indicates variables which must be replaced by current values. In running text. <text> Monospaced font Monospaced font Commands to be entered at the keyboard are Bold monospaced font shown in bold. this is indicated by a hyphen between the two keyboard symbols. menu items. and the names of buttons. Table 1: Notational conventions If reference is made to passages elsewhere in this manual. commands.[A] for A.6 Notational conventions The meanings of the symbols used in this manual are as follows: V Warning I Ê Text in italics 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.Notational conventions Preface 1. [square brackets] {braces} [Keyboard] [symbols] Indicate optional entries. Output from the system is shown in monospaced font.

– If you want to log in with a symbolic name rather than an IP address at the iRMC S2 web interface. – For console redirection: Sun Java Virtual Machine Version 1.2 Logging on to the iRMC S2 for the first time The factory default settings of the iRMC S2 allow you to log in to the iRMC S2 for the first time without the need for any configuration activities. iRMC S2 33 . In your network: – You must have a DHCP server in your network. the DHCP server in your network must be configured for dynamic DNS. Otherwise you must ask for the IP address.0_06 or higher.1 Requirements On the remote workstation: – Windows: Internet Explorer as of Version 6. – DNS must be configured.5.x: Linux: Mozilla Firefox 1.5. 2.

For reasons of security.Manage users” on page 323). 34 iRMC S2 . Default DHCP name of the iRMC S2 The default DHCP name of the iRMC S2 uses the following pattern: IRMC<SerialNumber> I The serial number corresponds to the last 3 bytes of the MAC address of the iRMC S2. it is recommended that you create a new administrator account once you have logged in. You can take the MAC address of the iRMC S2 from the label on your PRIMERGY server.2 iRMC S2 factory defaults The firmware of the iRMC S2 provides a default administrator ID and a default DHCP name for the iRMC S2. the MAC address of the iRMC S2 can be found as a read-only entry above the fields on the page Network Interface (see page 302). and then delete the default administrator account or at least change the password for the account (see section “User Management . Default administrator ID: Administrator ID: Password: admin admin I Both the administrator ID and the password are case-sensitive.iRMC S2 factory defaults Logging on to the iRMC S2 for the first time 2. After you have logged in.

I You can take the DNS name of the iRMC from the label on your PRIMERGY server. Ê Type in the data for the default administrator account. The iRMC S2 web interface opens showing the System Information page (see page 231).. iRMC S2 35 .. The following login prompt appears: Figure 6: Login prompt for the iRMC S2 web interface I If the login prompt does not appear. check the LAN connection (see section “Testing the LAN interface” on page 43). User name: admin Password: admin Ê Click OK to confirm your entries.Logging on to the iRMC S2 for the first time .3 Logging into the iRMC S2 web interface Ê Open a web browser on the remote workstation and enter the DNS name or IP address of the iRMC S2. in the web interface 2.

.

3 Configuring the iRMC S2 The following tools are available for configuring the iRMC S2: – BIOS Setup Utility / TrustedCore Setup Utility (see page 41) – iRMC S2 web interface (see page 221) – Server Configuration Manager (see page 401) – Server Management Tool (IPMIVIEW) This chapter provides you with information about the following topics: – Configuring the LAN interface of the iRMC S2 using the BIOS Setup program (see page 41). see page 55). – Configuring text console redirection via LAN using the BIOS Setup program (see page 44). – Configuring the serial interface of the iRMC S2 using the BIOS Setup program (see page 51). – iRMC S2 using the Server Configuration Manager (for an overview. – Configuring the iRMC S2 over the web interface (for an overview. see page 57). iRMC S2 37 .

Fast Forwarding=enabled). Port Fast=enabled.LAN interface Configuring the iRMC S2 3.1 Configuring the LAN interface of the iRMC S2 This section describes: – Requirements for configuring the LAN interface – Configuring the LAN interface in the BIOS Setup program – Testing the LAN interface I "Spanning Tree" tree for the connection of the iRMC S2 must be deactivated (e. 38 iRMC S2 .g.

3. these are port 1 and the top left-hand port).1. the system board of a PRIMERGY server provides two or three LAN interfaces. Dedicated Service LAN (Port exclusively for the iRMC S2) Shared LAN (iRMC and system) LAN port exclusively for the system Figure 7: Ports for the iRMC S2 (indicated by wrench symbol) iRMC S2 39 . Depending on the server type. Depending on the type of PRIMERGY server.1 Prerequisites Note the following requirements with respect to configuring the IP address: – The LAN cable must be connected to the correct port.1. different ports may be marked with the wrench symbol.1.Configuring the iRMC S2 LAN interface 3. (see section “Connected to the correct LAN port?” on page 39).1 Connected to the correct LAN port? The interface for a LAN connection is provided on an onboard LAN controller assigned to the iRMC S2 (see also figure 4 on page 28). for example. The ports marked with a wrench symbol are assigned to the iRMC S2 (in figure 7. – Interaction between the IP addresses of the iRMC S2 and the system (see the section “Interaction between the IP addresses of the iRMC S2 and the system” on page 40). I Check that the LAN cable is connected to the correct port.

you must configure the gateway.1.2 Configuring the LAN interface: Configuration tools You can configure the iRMC S2’s LAN interface in a number of ways: Depending on the type of the PRIMERGY server – using the BIOS Setup Utility or the TrustedCore® Setup Utility (see page 41).1. – iRMC S2 web interface (see section “Network Settings . – using the Server Configuration Manager (see “iRMC LAN Interface Configure LAN parameters of the iRMC S2” on page 418).1.Configure the LAN parameters” on page 301).LAN interface 3. 3.1. 3.2 Configuring the iRMC S2 Interaction between the IP addresses of the iRMC S2 and the system The LAN controller of the PRIMERGY server requires a separate IP address for the iRMC S2 in order to ensure that data packets are reliably transferred to the iRMC S2 (and not to the operating system). 40 iRMC S2 . – using the Server Management Tool. The IP address of the iRMC S2 must be different from that of the system (operating system).1.3 Access from a different subnet If the remote workstation accesses the iRMC S2 of the managed server from a different subnet and DHCP is not used.

Do this by pressing [F2] while the server is booting.1. I The Service setting is mandatory for the Type TX150 S6 PRIMERGY server. Service LAN Port The Service setting is recommended. iRMC S2 41 .3 Configuring the LAN interface using the BIOS / TrustedCore Setup program Ê Call the BIOS / TrustedCore Setup Utility of the managed server. Ê Call the LAN parameter configuration menu: – BIOS: Advanced – IPMI – LAN Settings – TrustedCore: Server – IPMI – LAN Settings Figure 8: LAN Settings menu (shown here for the TrustedCore Setup Utility) Ê Configure the following settings: Service LAN Set the value to Enabled.Configuring the iRMC S2 LAN interface 3.

Gateway Address Specify the IP address of the gateway. the following name is passed to the DHCP server on initial installation of the iRMC S2: iRMC<last 3 bytes of the MAC address>.e. are set automatically. Local IP Address Enter the IP address you have determined for the iRMC S2 of the managed system. using the iRMC S2 web interface.Enable DNS for the iRMC S2” on page 311). Ê Save the settings. for instance (see sections “DHCP Configuration . If you activate the DHCP option and there is no DHCP server available.LAN interface DHCP Configuring the iRMC S2 If you enable DHCP. the iRMC S2 goes into a search loop (i. If you do not want to use text console redirection on the iRMC S2. Subnet Mask. Ê If you want to use console redirection on the iRMC S2. I Do not activate the DHCP option if no DHCP server is available. etc. continue with section “Configuring text console redirection via LAN using the BIOS/TrustedCore Setup program” on page 44. By default. In this case. the iRMC S2 gets its LAN settings autonomously from a DHCP server on the network. exit the BIOS/TrustedCore Setup and continue with the next section “Testing the LAN interface”. the values for Local IP Address.Configuring the host name for the iRMC S2” on page 309 and “DNS Settings . it constantly searches for a DHCP server). 42 iRMC S2 . You can specify that the DHCP and DNS services are to be used after initial installation. Subnet Mask Enter the subnet mask for the network.

Ê Test the connection to the iRMC S2 with a ping command. If no login prompt appears.Configuring the iRMC S2 LAN interface 3. iRMC S2 43 .1. it is probable that the LAN interface is not working.4 Testing the LAN interface You can test the LAN interface as follows: Ê Use a web browser to attempt to log into the iRMC S2 web interface.

Configure and start text console redirection” on page 345).Console redirection via LAN Configuring the iRMC S2 3.2 Configuring text console redirection via LAN using the BIOS/TrustedCore Setup program Text console redirection will be available depending on the configuration of text console redirection and on the operating system of the server – either for the duration of the BIOS POST phase only or – beyond the BIOS POST phase while the operating system is running. I You can also configure text console redirection via LAN using the iRMC S2 web interface (see section “BIOS Text Console . This section describes: – Configuration of text console redirection via LAN using the BIOS / TrustedCore Setup Utility – Special requirements of the operating system used that you need to take account of if you also want to use console redirection while the operating system is running. 44 iRMC S2 .

iRMC S2 45 . Settings in the Peripheral Configuration menu Ê Call the Peripheral Configuration menu: Advanced – Peripheral Configuration Figure 9: Peripheral Configuration menu (as it appears in the TrustedCore Setup Utility) Ê Configure the following settings: Serial 1 Set the value to Enabled.2. Serial 1 Address Accept the first value pair proposed.Configuring the iRMC S2 Console redirection via LAN 3.1 Configuring text console redirection Ê Call the BIOS / TrustedCore Setup Utility of the managed server. Serial Multiplexer Set the value to iRMC. Do this by pressing [F2] while the server is booting.

Console redirection via LAN Settings in the Console Redirection menu Ê Call the Console Redirection menu: Server – Console Redirection Configuring the iRMC S2 I The appearance of the Console Direction menu varies depending on the Setup Utility (BIOS or TrustedCore) you are using.) 46 iRMC S2 . Port Set the value to Serial 1. Protocol Leave this setting unchanged. (The setting depends on the terminal type used. Ê Make the following settings in the BIOS Setup Utility: Figure 10: Console Redirection menu (as it appears in the BIOS Setup Utility) Console Redirection Set the value to Enabled. Baud Rate Specify the baud rate.

Baud Rate Specify the baud rate. (The setting depends on the terminal type used.) Mode This setting affects the behavior of console redirection while the operating system is running (after the POST phase has completed) see section “Using console redirection while the operating system is running” on page 49: Standard Console redirection is terminated after the BIOS POST phase. Ê Make the following settings in the TrustedCore Setup Utility: Figure 11: Console Redirection menu (as it appears in the TrustedCore Setup Utility) Com Port Address Set the value to On-board COM A. iRMC S2 47 .Configuring the iRMC S2 Console redirection via LAN Flow Control Leave this setting unchanged. Enhanced Console redirection continues to be available after the BIOS POST phase.

R. Ê Continue with section “Testing the LAN interface” on page 43. On Console redirection continues to be available after the BIOS POST phase. Exiting the BIOS / TrustedCore setup Ê Save your settings and exit the BIOS/TrustedCore Setup utility.) Continue C.) Flow Control Leave this setting unchanged. 48 iRMC S2 . (The setting depends on the terminal type used. (The setting depends on the terminal type used. after POST: This setting affects the behavior of console redirection while the operating system is running (after the POST phase has completed) see section “Using console redirection while the operating system is running” on page 49: Off Console redirection is terminated after the BIOS POST phase.Console redirection via LAN Configuring the iRMC S2 Console Type Leave this setting unchanged.

R. after POST: On Windows Server 2003 Windows Server 2003 handles console redirection automatically after the POST phase.2 Using console redirection while the operating system is running Depending on the operating system used on the managed server.2. the Windows Server 2003 SAC console is transferred: Figure 12: Windows Server 2003 SAC console Linux You must configure a Linux operating system in such a way that it handles console redirection after the POST phase. While the operating system is booting. DOS The BIOS setting for console redirection mode must be set as follows (see section “Settings in the Console Redirection menu” on page 46): – BIOS Setup Utility: Mode: Enhanced – TrustedCore Setup Utility: Continue C. you can continue to use console redirection after the BIOS POST phase. No further settings are necessary.Configuring the iRMC S2 Console redirection via LAN 3. Once it has been configured. iRMC S2 49 . you have unrestricted access from the remote workstation.

lst : console=ttyS0.conf: console=ttyS0.<baud-rate> console=tty0 50 iRMC S2 .Console redirection via LAN Settings required The settings may differ between program versions. Configuring the iRMC S2 SuSe and RedHat Add the following line to the end of the file /etc/inittab: xx:12345:respawn:/sbin/agetty <baud-rate> ttyS0 RedHat Insert the following kernel boot parameter in the file /etc/grub.<baud-rate> console=tty0 SuSE Insert the following kernel boot parameter in the file /boot/grub/menu.

You can configure alerting via modem using the web interface of the iRMC S2 (see section “Serial / Modem Alerting .Configuring the iRMC S2 Serial interface 3. iRMC S2 51 .Configure alerting via modem” on page 315). – You can forward alerts via modem.3 Configuring and using the serial interface of the iRMC S2 The serial interface of the iRMC S2 offers you the following possibilities: – You can use the terminal application Remote Manager (Serial) over a null modem cable (see section “Using the Remote Manager (Serial) interface” on page 54).

52 iRMC S2 .1 Configuring the serial interface Settings in the BIOS Ê Call the BIOS / TrustedCore Setup Utility of the managed server. Serial Multiplexer Set the value to iRMC.Serial interface Configuring the iRMC S2 3. Serial 1 Address Accept the first value pair proposed.3. Ê Call the Peripheral Configuration menu to configure the serial port: Advanced – Peripheral Configuration Figure 13: Peripheral Configuration menu (as it appears in the TrustedCore Setup Utility) Ê Configure the following settings: Serial 1 Set the value to Enabled. Do this by pressing [F2] while the server is booting.

iRMC S2 53 . Stop bits 1 Flow Control None Exiting the BIOS / TrustedCore setup Ê Save your settings and exit the BIOS/TrustedCore Setup utility.Configuring the iRMC S2 Serial interface The following values are not shown in the menu and are preset (see page 54. “Terminal program (VT100+)”): Bits per second 9600 Data bits 8 Parity None. Ê Continue with section “Testing the LAN interface” on page 43.

54 iRMC S2 .2 Using the Remote Manager (Serial) interface If you connect a computer over a null modem cable and start a terminal program (VT100+) on this computer. you can access the Remote Manager (Serial) terminal program. Parity Set the value to None.Using the serial interface Configuring the iRMC S2 3. The Remote Manager (Serial) interface is identical to the Remote Manager interface (see chapter “iRMC S2 via Telnet/SSH (Remote Manager)” on page 373). Prerequisites On the managed server: The Serial Multiplexer BIOS setting must be configured on the iRMC (see section “Configuring the serial interface” on page 52). Terminal program (VT100+): Configure the following port settings for the terminal program: Bits per second Set the value to 9600. Flow Control Set the value to None. Data bits Set the value to 8.3. Stop bits Set the value to 1.

Configure Ethernet settings on the iRMC S2” on page 302 for the settings required. See the section “DHCP Configuration .Configuring the iRMC S2 . Configuring DHCP Ê Configure the DHCP settings in the DHCP Configuration page.4 Configuring the iRMC S2 over the iRMC S2 web interface Ê Start the iRMC S2 web interface (see section “Logging into the iRMC S2 web interface” on page 222). Configuring DNS Ê Configure the DNS settings in the DNS Settings page. See the section “DNS Settings .Configuring ports and network services” on page 305 for the settings required. iRMC S2 55 . Configuring ports and network services Ê Configure the ports and network services on the Ports and Network Services page. 3. Configuring the LAN settings Ê Configure the LAN settings on the Network Interface page.Enable DNS for the iRMC S2” on page 311 for the settings required.. See the section “Network Interface . click Network Settings (see section “Network Settings .4..Configuring the host name for the iRMC S2” on page 309 for the settings required. over the iRMC S2 web interface 3.Configure the LAN parameters” on page 301).1 Configuring the LAN parameters Ê In the navigation area. See the section “Ports and Network Services .

over the iRMC S2 web interface Configuring the iRMC S2 3.Configure email alerting” on page 317 for the settings required.4.4.2 Configuring alerting The pages for configuring alerting are grouped in the navigation area under Alerting (see section “Alerting .Configure alerting via modem” on page 315 for the settings required.3 Configuring text console redirection Ê Configure text console redirection in the BIOS Text Console window. Ê Configure SNMP trap forwarding. See the section “Serial / Modem Alerting . Configuring email notification (email alerting) Ê In the navigation area. See the section “Email Alerting .. The Email Alerting page appears. click SNMP Traps. Ê Configure email alerting. See the section “SNMP Trap Alerting Configure SNMP trap alerting” on page 314 for the settings required. The Serial / Modem Alerting page appears. click Email.. Configuring alert forwarding to a mobile phone via modem Ê In the navigation area.Configure alerting” on page 313).. The SNMP Traps page appears. Configuring alert forwarding over SNMP Ê In the navigation area.Configure and start text console redirection” on page 345 for the settings required. 3. See the section “BIOS Text Console . 56 iRMC S2 . Ê Configure alert forwarding via modem. click Serial / Modem.

Configuring the host name for the iRMC S2” on page 423 for the settings required. 3. See the section “iRMC DNS Registration . Configuring ports and network services Ê Configure the ports and network services in the iRMC Networking Ports dialog box.Activating DNS for the iRMC S2” on page 425 for the settings required.. Configuring DHCP/DNS (dynamic DNS) Ê Configure the DHCP settings in the iRMC DNS Registration dialog box.5 Configuring iRMC S2 using the Server Configuration Manager Ê Start the Server Configuration Manager (see chapter “Configuring iRMC S2 using the Server Configuration Manager” on page 401). See the section “iRMC Networking Ports .Configuring ports and network services” on page 421 for the settings required. See the section “iRMC DNS Server .Configure LAN parameters of the iRMC S2” on page 418 for the settings required. See the section “iRMC LAN Interface . Configuring DNS Ê Configure the DNS settings in the iRMC DNS Server dialog box.5. using the Server Configuration Manager 3.. iRMC S2 57 .1 Configuring the LAN parameters Configuring the LAN settings Ê Configure the LAN settings in the iRMC LAN Interface dialog box.Configuring the iRMC S2 .

See the section “iRMC SNMP Alerting . See the section “iRMC Mail Format Settings . 58 iRMC S2 .2 Configuring alerting Configuring alert forwarding over SNMP Ê Configure SNMP trap forwarding in the iRMC SNMP Alerting dialog box.Configure SNMP Trap alerting” on page 432 for the settings required.Configure email alerting” on page 427 for the settings required.5. Ê Configure the user-specific email settings in the iRMC EMail Format Settings dialog box. Configuring email notification (email alerting) Ê Configure the global email settings in the iRMC EMail Alerting dialog box.Mail-formatdependent settings” on page 430 for the settings required. See the section “iRMC EMail Alerting .... using the Server Configuration Manager Configuring the iRMC S2 3.

– 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 S2 user management: – Microsoft® Active Directory – Novell® eDirectory – OpenLDAP This chapter provides information on the following topics: – – – – User management concept for the iRMC S2 User permissions Local user management on the iRMC S2 Global user management using the individual directory services iRMC S2 59 .4 User management for the iRMC S2 User management for the iRMC S2 uses two different types of user identifications: – Local user identifications are stored locally in the iRMC S2’s non-volatile storage and are managed via the iRMC S2 user interfaces.

password) which users enter when logging in to one of the iRMC S2 interfaces. the iRMC S2 continues the verification with step 2. iRMC S2 proceeds as follows (see also figure 14 on page 61): 1. The iRMC S2 authenticates itself at the directory service via LDAP with a user name and password.Concept User management on the iRMC S2 4.1 User management concept for the iRMC S2 User management for the iRMC S2 permits the parallel administration of local and global user identifications. ● 2. determines the user rights by means of an LDAP query and checks whether the user is authorized to work with these at the iRMC S2. 60 iRMC S2 . Otherwise. The iRMC S2 compares the user name and password with the locally stored user identifications: ● If the user is authenticated successfully by iRMC S2 (user name and password are valid) then the user can log in. When validating the authentication data (user name.

An SSL-secured LDAP connection between iRMC S2 and the directory service guarantees secure data exchange. SSL login via the iRMC S2 web interface is only required if LDAP is active (LDAP enable option. the use of SSL for the LDAP connection between the iRMC S2 and directory service is recommended. password SSL SSH iRMC S2 local user identifications SSL User name. iRMC S2 61 . password SSL LDAP login Directory service Global user identifications Figure 14: Login authentication via the iRMC S2 I Although optional.User management on the iRMC S2 Concept iRMC S2 web interface Login SSL SSH Login SSH Telnet Login Serial interface Login User name. and in particular the secure transfer of the user name and password data. see page 334).

I The permission groups correspond to the IPMI privilege level. for Power Management) are associated with these groups or privilege levels. – for the Remote Manager. Channel-specific privileges (channel-specific permission groups) The iRMC S2 assigns each user identification to one of the following four channel-specific permission groups: – – – – users Operator Administrator OEM Since iRMC S2 assigns these permissions on a channel-specific basis. users can have different permissions. 62 iRMC S2 . Certain permissions (e.User permissions User management on the iRMC S2 4.web interface. The scope of permissions granted increases from User (lowest permission level) through Operator and Administrator up to OEM (highest permission level). depending on whether they access the iRMC S2 over the LAN interface or the serial interface.2 User permissions The iRMC S2 distinguishes between two mutually complementary types of user permissions: – Channel-specific privileges (via assignment to channel-specific permission groups) – Permissions to use special iRMC S2 functions I The privileges and permissions required for the use of the individual iRMC S2 functions are described – for the iRMC S2. on page 382.g. on page 224.

Manage users” on page 323). you can also individually assign users the following permissions: – Configure User Accounts Permission to configure local user identifications – Configure iRMC S2 Settings Permission to configure the iRMC S2 settings. – Video Redirection Enabled Permission to use Advanced Video Redirection (AVR) in “View Only” and “Full Control” mode – Remote Storage Enabled Permission to use the Remote Storage functionality Preconfigured user ID The firmware of the iRMC S2 provides a default administrator ID for the iRMC S2 which possesses all permissions: Administrator ID: Password: admin admin I Both the administrator ID and the password are case-sensitive in the case of local users. and then delete the default administrator account or at least change the password for the account (see section “User Management . iRMC S2 63 .User management on the iRMC S2 Permissions to use special iRMC S2 functions User permissions In addition to the channel-specific permissions. It is urgently recommended that you create a new administrator account as soon as possible once you have logged in.

3 Local user management for the iRMC S2 The iRMC S2 possesses its own local user management.Manage users” on page 323. Showing the list of configured users Ê In the navigation area. 64 iRMC S2 ..iRMC S2 User function. change the configuration of existing users and remove users from the list. User management can be performed manually or using scripts (with IPMIView). Up to 16 users to be configured with passwords and be assigned various rights depending on the user groups they belong to. The User Management page opens containing a list of configured users (see page 324). Ê Start the iRMC S2 web interface (see section “Logging into the iRMC S2 web interface” on page 222).3. The user identifications are stored in the iRMC S2’s local.1 Local user management using the iRMC S2 web interface permission. This page is described in section “User Management . non-volatile storage. You can also configure new users.. Here. locally via the web interface User management on the iRMC S2 4. The following options are available for user management on the iRMC S2: – User management via the web interface – User management via the Server Configuration Manager – User management using the Server Management Tool (IPMIVIEW) 4. click the User Management . you can delete users and call the page for configuring new users.. I User management on the iRMC S2 requires Configure User Accounts You can view a list of configured users under the web interface.

This page is described in section “New User Configuration . Here.User management on the iRMC S2 Configuring new users . This page is described in section “User “<name>” Configuration User configuration (details)” on page 326. click on the Delete button in the same line as the user to be deleted.. you can change the configuration parameters for the new user.Configuring a new user” on page 325.. iRMC S2 65 . The New User Configuration page opens. click the New User button. The User “<name>” Configuration page opens showing the settings for the selected user. Modifying the configuration of a user Ê On the User Management page. locally via the web interface Ê On the User Management page. click the name of the user whose configuration parameters you want to change. This page allows you to configure the basic settings for the new user. Deleting users Ê On the User Management page.

The dialog box contains a list of all the configured users (see page 433). Ê Click the Modify.. This window is described on page 434.. Configuring new users Ê In the iRMC User Management dialog box. You can also configure new users.. Ê Make the settings for the new user in the Edit existing user window. change the configuration of existing users and remove users from the list. button or double-click the selected line. Showing the list of configured users Ê Choose iRMC User Management..2 Local user management via the Server Configuration Manager I Prerequisite: The current ServerView agents must be installed on the managed server. ManagerUser management on the iRMC S2 4.. Ê Start the Server Configuration Manager (see chapter “Configuring iRMC S2 using the Server Configuration Manager” on page 401). locally via the Server Config. You can view a list of configured users under Server Configuration Manager. I User management on the iRMC S2 requires Configure User Accounts permission.3. Ê Confirm your settings by clicking OK. 66 iRMC S2 . select a line below the displayed user in which only the user ID is shown. Here you can delete users and call the Edit existing user window showing the settings for the selected user. The Edit existing user window opens.

button or double-click the selected user. Manage Modifying the configuration of a user Ê Select a user in the iRMC User Management dialog box.. Deleting users Ê Select a user in the iRMC User Management dialog box. The Edit existing user window opens showing the configured settings for this user. Ê Click the Delete button to delete the user.User management on the iRMC S2 . Ê Confirm your settings by clicking OK. iRMC S2 67 .. Ê Click the Modify... Ê Modify the settings for the user in the Edit existing user window. locally via the Server Config.

3 SSHv2 public key authentication for iRMC S2 users In addition to authentication by means of a user name and password. The user is only responsible for keeping their private key secret. the user can now log into the iRMC S2 extremely securely and without the need to enter a password. the SSHv2 key of an iRMC S2 user is uploaded to the iRMC S2 and the iRMC S2 user uses their private key with the program PuTTY or the OpenSSH client program ssh. To implement SSHv2 public key authentication.3. – The user (or administrator) uploads the public key to the iRMC S2. public key authentication of a user on the iRMC S2 happens as follows: The user who wishes to log into the iRMC S2 creates the key pair: – The private key is read-protected and remains on the user's computer. The iRMC S2 supports the following types of public keys: – SSH DSS (minimum requirement) – SSH RSA (recommended) The public SSHv2 keys that you upload to the iRMC S2 can be available either in RFC4716 format or in OpenSSH format (see page 82). If the configuration allows this. for example. Public key authentication In outline. the iRMC S2 also supports SSHv2-based public key authentication using pairs of public and private keys for local users. 68 iRMC S2 .SSHv2 public key support User management on the iRMC S2 4.

Configuring the program PuTTY or ssh for SSHv2 access to the iRMC S2 (see page 76). They are described in the subsequent sections: 1. iRMC S2 69 . Loading the public SSHv2 key onto the iRMC S2 from a file (see page 74). Creating the public and private SSHv2 keys with the program PuTTYgen or ssh-keygen and saving them in separate files (see page 70). 3. 2.User management on the iRMC S2 SSHv2 public key support The following steps are necessary to set up private key authentication.

3.1 User management on the iRMC S2 Creating public and private SSHv2 keys You can create public and private SSHv2 keys – with the program PuTTYgen or – with the OpenSSH client program ssh-keygen.SSHv2 public key support 4. select the key type SSH-2RSA and click Generate to start generation of the keys. The following window appears when PuTTYgen is started: Figure 15: PuTTYgen: Creating new private and public SSHv2 keys Ê Under Parameters.3. The progress of the generation operation is then displayed under Key (see figure 16 on page 71). 70 iRMC S2 . Creating the public and private SSHv2 keys with PuTTYgen Proceed as follows: Ê Start PuTTYgen on your Windows computer.

Ê Click Save private key to save the private SSHv2 key to a file for use with PuTTY (see page 76). Ê Move the mouse pointer over the blank area of the progress display to increase the randomness of the generated keys. When the keys have been generated. You can upload the public key to the iRMC S2 from this file (see page 74). iRMC S2 71 .User management on the iRMC S2 SSHv2 public key support Figure 16: PuTTYgen: Creating a new key pair (progress bar). Ê Click Save public key to save the public SSHv2 key to a file. PuTTYgen displays the key and the fingerprint of the public SSHv2 key: Figure 17: PuTTYgen: Creating a new private SSHv2 key (progress bar).

openssh.org. You will find a detailed description of the operands in the OpenSSH OpenSSH manual pages under http://www. Example: Generating an RSA key pair with ssh -keygen 1 2 3 4 5 72 iRMC S2 .openssh. you can obtain OpenSSH from http://www.html Proceed as follows: Ê 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 queries the user for the file name under which the private key is to be stored and for 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.SSHv2 public key support User management on the iRMC S2 Creating the public and private SSHv2 keys with ssh-keygen I If it is not already pre-installed in the Linux distribution you are using.org/manual.

ssh-keygen uses the default file name id_rsa. ssh-keygen requests the file name under which the SSHv2 key is to be saved. ssh-keygen does not use a passphrase. 5. ssh-keygen requests you to enter a passphrase (and to confirm it) that is used to encrypt the private key. 3. ssh-keygen informs the user that the newly generated private SSHv2 key has been saved in the file /.User management on the iRMC S2 Explanation: SSHv2 public key support 1.ssh/id_rsa. ssh-keygen displays the fingerprint of the public SSHv2 key and the local login to which the public key belongs. If you press [Enter] to confirm without entering a file name. iRMC S2 73 .pub. 2. If you press [Enter] to confirm without entering a passphrase.ssh/id_rsa. 4. ssh-keygen informs the user that the newly generated public SSHv2 key has been saved in the file /.

74 iRMC S2 . open the detailed view for the required browser (in this case user3) iRMC S2 User Management page: (1) (2) Figure 18: iRMC S2 web interface: Loading the public SSHv2 key onto the iRMC S2 Ê Click Browse in the group User SSHv2 public key upload from file (1) and navigate to the file containing the required public key (2).2 User management on the iRMC S2 Loading the public SSHv2 key onto the iRMC S2 from a file Proceed as follows: Ê Under the iRMC S2 web interface.3.3. Ê Click Upload to load the public key onto the iRMC S2.SSHv2 public key support 4.

make sure that the fingerprint shown here matches that shown in PuTTYgen (see figure 17 on page 71) under Key fingerprint. iRMC S2 75 . the iRMC S2 displays the key fingerprint in the group User SSHv2 public key upload from file: Key type Key length MD5 fingerprint of the saved key Figure 19: Display of the key fingerprint I For reasons of security.User management on the iRMC S2 SSHv2 public key support After the key has been successfully uploaded.

3. 76 iRMC S2 .3. Proceed as follows: Ê Start PuTTY on your Windows computer.SSHv2 public key support 4.3 User management on the iRMC S2 Configuring PuTTY and the OpenSSH client for using the public SSHv2 key Configuring PuTTY for using the public SSHv2 key The PuTTY program allows you to set up a public-key-authenticated connection to the iRMC S2 and log in either under your user name or using the auto-login mechanism. The following window appears when PuTTY is started: Figure 20: PuTTY: Selecting and loading an SSH session Ê Select a saved SSH session or create a new SSH session for the iRMC S2 for which you want to use the SSHv2 key. PuTTY handles the authentication protocol automatically on the basis of the public/private SSHv2 key pair previously generated.

iRMC S2 77 .Auth to configure the SSH authentication options. This opens the following window (see figure 22 on page 78). This opens the following window: SSHv2 public key support Figure 21: PuTTY: Loading an SSH session Ê Choose SSH .User management on the iRMC S2 Ê Click Load to load the selected SSH session.

78 iRMC S2 . I Please note: At this point.SSHv2 public key support User management on the iRMC S2 Figure 22: Configuring the SSH authentication options Ê Select the file containing the private key that you want to use with the iRMC S2. you require the private key (see page 71) and not the public key that you loaded onto the iRMC S2.

Data.User management on the iRMC S2 SSHv2 public key support I Under Connection . Figure 23: PuTTY: Specifying the user name for automatically logging into the iRMC S2 iRMC S2 79 . you can additionally specify a user name for automatic login onto the iRMC S2.

3.openssh.html 80 iRMC S2 . Access should be denied to all other users.SSHv2 public key support User management on the iRMC S2 Configuring the OpenSSH client program ssh for using the public SSHv2 key You establish an SSHv2-protected connection to the iRMC S2 using the OpenSSH client program ssh. ssh reads its configuration options in order from the following sources: 1.org/manual. Command line arguments that you specify when calling ssh: 2. You can log in either under your current local login or under a different login. I You will find detailed information on the configuration of ssh and on its operands on the manual pages for OpenSSH under http://www.ssh/config) I Although this file contains no security-critical information. System-wide configuration file (/etc/ssh/ssh_config) This file contains default values for configuration parameters – if there is no user-specific configuration file or – if the relevant parameters are not specified in the user-specific configuration file. I The login must have been configured as a local login on the iRMC S2 and the associated SSHv2 key must have been loaded on the iRMC S2. The value found first applies for each option. User-specific configuration file ($HOME/. read/write permission should only be granted to the owner.

to log in to the iRMC S2 inder SSHv2-authentication: ssh -l [<user>] <iRMC_S2> or ssh [<user>@]<iRMC_S2> <user> User name under which you want to log into the iRMC S2.call. <iRMC_S2> iRMC S2 name or IP address of the iRMC S2 you want to log into. You can then log in from your local computer under $HOME/User1 as follows on the iRMC S2 "RX100_S52-iRMC" using the login user4: ssh user4@RX100_S52-iRMC iRMC S2 81 .pub has been loaded onto the iRMC S2 for an iRMC S2 uesr user4 (see page 74). If you do not specify <user>.User management on the iRMC S2 Proceed as follows: SSHv2 public key support Ê Start ssh.ssh/id_rsa. ssh uses the user name under which you are logged into your local computer to log you in to iRMC S2. it is assumed that ssh-keygen has been used to generate a public/private RSA key pair as described under „Example: Generating an RSA key pair with ssh -keygen“ auf Seite 72 and that the public key User1/. Example: SSHv2-authentifcated login on the iRMC S2 For the following ssh.

3.3.SSHv2 public key support 4. Public SSHv2 key in RFC4716 format ---.END SSH2 PUBLIC KEY ---- Public SSHv2 key in OpenSSH format ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAIBScBsgP9B74qNa9+w8Ccv3kDVVu2boKCGLv4hx v6+AUFrF6sYdGey1QQ7MkwSeax3NmoZBkvkR9hNfZSqxkPCkd//LyUil9US5/9Ar JxjlhXUzlPPVzuBtPaRB7+bISTJVMUorNwrcN48b6AAoYBhKC4AOtOP1OGwsfc+F pGJ2iw== rsa-key-20090401 82 iRMC S2 .BEGIN SSH2 PUBLIC KEY ---Comment: "rsa-key-20090401" AAAAB3NzaC1yc2EAAAABJQAAAIBScBsgP9B74qNa9+w8Ccv3kDVVu2boKCGLv4hx v6+AUFrF6sYdGey1QQ7MkwSeax3NmoZBkvkR9hNfZSqxkPCkd//LyUil9US5/9Ar JxjlhXUzlPPVzuBtPaRB7+bISTJVMUorNwrcN48b6AAoYBhKC4AOtOP1OGsfc+F pGJ2iw== ---.4 Example: Public SSHv2 key User management on the iRMC S2 The following shows the same public SSHv2 key in both RFC4716 format and in OpenSSH format.

– Global iRMC S2 user management via Microsoft Active Directory – Global iRMC S2 user management via Novell eDirectory – Global iRMC S2 user management via OpenLDAP I Alongside the measures described in this section which you perform in the directory service. The following directory services are currently supported for iRMC S2 user management: – Microsoft® Active Directory – Novell® eDirectory – OpenLDAP This section provides you with information about the following topics: – Overview of global user management for the iRMC S2 – Concept of global user management for the iRMC S2 using an LDAP directory service – Configuring global iRMC S2 user management in the directory service (generating the permissions structures specific to iRMC / iRMC S2 in the directory service).. – using the Server Configuration Manager (see page page 439). global user management also requires you to configure the local LDAP settings at the iRMC S2.. globally via a directory service 4. You may configure the local LDAP settings either – at the iRMC S2 web interface (see page page 333).User management on the iRMC S2 .4 Global user management for the iRMC S2 The global user IDs for the iRMC S2 are managed centrally using an LDAP directory service. iRMC S2 83 .

. 84 iRMC S2 . They can therefore be used by all the iRMCs and iRMC S2s that are connected to this server in the network. iRMC n Login Authentication Figure 24: Shared use of the global user identifications by multiple iRMCs Communications between the individual iRMCs / iRMC S2s and the central directory service is performed via the TCP/IP protocol LDAP (Lightweight Directory Access Protocol). I Global user management is currently not supported for the following iRMC S2 functions: – Login via IPMI-over-LAN – Console redirection via SOL iRMC 1 Login Authentication Login Authentication iRMC 2 Directory service Global user identifications .1 Overview The global user IDs for the iRMC S2 (and for the iRMC) are stored centrally for all platforms in the directory service's directory. using a directory service for the iRMC / iRMC S2 makes it possible to use the same user identifications for logins at the iRMCs / iRMC S2s as are used for the operating system of the managed servers..4. Optionally.. communication via LDAP can be secured by SSL.. This makes it possible to manage the user identifications on a central server. globally via a directory service User management on the iRMC S2 4. Furthermore.. LDAP makes it possible to access the directory services which are most frequently used and most suitable for user management.

4. >. Here. ~. |. – iRMC users obtain their privileges by virtue of being members of a group in the organizational unit (OU) iRMCgroups.. is provided via additional LDAP groups and organizational units (OUs) which are combined in separate OUs in a domain of the LDAP directory server (see figure 26 on page 88). Novell eDirectory and OpenLDAP. the permissions are directly assigned to the individual user groups. an attempt is made to find a match in the entries in iRMCgroups. The figures are based on the example of the Active Directory Users and Computers console in the Microsoft Active Directory user interface. Instead. the first matching entry is relevant. globally via a directory service 4. – iRMC S2 users obtain their privileges by being assigned a role (user role) declared in the organizational unit (OU) SVS or by membership of a group of the OU iRMCgroups. In either case.2.User management on the iRMC S2 . <. : I The concept of directory service-based.4. (.. all the information that is relevant for the iRMC / iRMC S2. global iRMC S2 user I The following characters are reserved as metacharacters for search You must therefore not use these characters as components of Relative Distinguished Names (RDN). =. \. the login data of the user is first compared with the entries in SVS to authenticate a user. Assigning permissions directly with user groups Global user management on the iRMC and the iRMC S2 (firmware version < 3.2 iRMC S2 user management via an LDAP directory service (concept) management described below applies equally to the directory services Microsoft Active Directory. iRMC S2 85 . I If both the OU SVS and the structure iRMCgroups are defined in the directory service. strings in LDAP: *. including the user permissions (privileges).77) controls the assignment of permissions by means of user groups. &. ).1 Global iRMC S2 user management using permission groups and roles Global iRMC / iRMC S2 user management via an LDAP directory server requires no extension to the standard directory server schema. !. If no matching entry is found there.4.

globally via a directory service User management on the iRMC S2 Assigning permissions with user roles (abbreviated to: roles) Global user management on the iRMC S2 (firmware version 3. figure 25 illustrates the concept of role-based assignment of user permissions with the roles Administrator.. Instead. Storage iRMC Settings iRMC Info Figure 25: Role-based assignment of user permissions The concept of user roles offers important advantages. Smith Mr.. Baker Administrator Maintenance Observer UserKVM User Mgmnt. task-oriented permission profile for activities on the iRMC S2. Observer and UserKVM. Several roles can be assigned to each user with the result that the permissions for this user are defined by the sum of the permissions of all the assigned roles. – It is only necessary to adapt the permissions of the user role in the event that the permission structure changes. In this case. Miller Ms.77 or later) controls the assignment of permissions by means of user roles. AVR Rem. they are assigned to the user role. Mr. including: – The individual permissions do not need to be assigned to each user or user group individually.. 86 iRMC S2 . Maintenance. each role defines a specific.

The iRMCgroups and SVS OUs are structured as follows: – iRMCgroups contains the OUs Departments and Shell: – Departments contains the groups for the user privileges. – iRMC S2 < firmware version 3.77A and iRMC support LDAP v1 structures that are stored in the OU iRMCgroups.4. – SVS contains the OUs Declarations. – User Settings contains details specific to users or user groups such as the mail format (for email alerting) and the groups for the user shells. LDAP v2 structures have been introduced to take future functional extensions into account.. I You use the software tool SVS_LdapDeployer (see page 96) to generate LDAP v1 and LDAP v2 structures and to maintain co-existing LDAP v1 and LDAP v2 structures.2.77A supports LDAP v2 structures that are stored in the OU SVS.2 . – If you operate both PRIMERGY servers with iRMC S2 and servers with iRMC. This results in the following recommendation: – If your server park comprises only PRIMERGY servers with iRMC S2.User management on the iRMC S2 4.77A or later is installed on all iRMC S2s. globally via a directory service Organizational units (OU) SVS and iRMCgroups The firmware for iRMC and iRMC S2 currently supports two different types of LDAP structures: – iRMC S2 as of firmware version 3. In this event.. you should only use LDAP v2 structures for global user management on the directory server. the directory server requires both LDAP v1 structures and LDAP v2 structures for global user management. iRMC S2 87 . Departments and User Settings: – Declarations contains a list of the defined roles and the list of predefined iRMC S2 user permissions (see section “User permissions” on page 62). ensure that Version 3. – Departments contains the groups for the user privileges. – Shell contains the groups for the user shells.

Permission groups can also be located at any point within the base domain. Unlike the standard users.. iRMC S2 users are also members of one or more groups of the OU SVS or of the OU iRMCgroups.. however. globally via a directory service User management on the iRMC S2 In the case of Microsoft Active Directory. 88 iRMC S2 . Figure 26: The OUs SVS and iRMCgroups in the domain fwlab.. for example.6x of the firmware. the entries for the iRMC S2 users are located in the standard OU Users.firm. the user entries for the iRMC S2 can be located at any points below the base domain.net I As of Version 3.

There are no restrictions concerning the number of departments (OUs) listed under Departments. the administrator permissions for the managed servers are also often assigned on a department-specific basis.. the servers which are managed via iRMC S2 are usually assigned to different departments. figure 27 on page 90 presents an example of this type of organizational structure on the basis of Active Directory Users and Computers. Departments are combined in the OU “Departments” The OU Departments combines the servers which are managed by iRMC S2 to form a number of groups. These correspond to the departments in which the same user IDs and permissions apply.User management on the iRMC S2 4.3 . If there is no department of this name in the LDAP directory then the permissions present in the Others department are used. DeptY and Others. I When configuring the directory service at the iRMC S2 via the iRMC S2 web interface (see page 333).2. Others is a predefined department name subsuming all those servers which do not belong to another department. globally via a directory service Cross-server. iRMC S2 89 . The entry Others is optional.. you specify the name of the department to which the managed server with the relevant iRMC S2 belongs. via the Server Configuration Manager (see page 439) or via the Server Management Tool (IPMIVIEW). for example. Furthermore. In figure 27 on page 90. global user permissions In large enterprises. these are the departments DeptX. but recommended.4.

globally via a directory service User management on the iRMC S2 Figure 27: Organizational structure of the domain fwlab.firm.net 90 iRMC S2 ....

for example. There are no restrictions concerning the number of permission groups.4 . If..User management on the iRMC S2 4.. (If a user belongs to more than one permission group in the same department then the first result returned by an LDAP query always apples. globally via a directory service iRMCgroups: Permission profiles are defined via permission groups The associated permission groups (security groups) are listed directly below each department (figure 27 on page 90). V CAUTION! Make sure that no user simultaneously belongs to more than one permission group in one and the same department. Every permission group defines a specific permission profile which applies to all the users who belong to the relevant permission group.) I The permission groups in global iRMC S2 user management also include the channel-specific permission groups (see page 62). The associated permission is listed under Notes using the following syntax: V CAUTION! You must not change the user profile in the Notes field. you click a department (e.4. For detailed information on the individual user permissions.g. see section “User permissions” on page 62. as this would make it impossible to log in.2. Roles can only be changed using the SVS_LdapDeployer (see page 96). The names of the permission groups can be chosen as required subject to certain syntactic requirements imposed by the employed directory service. LAN: OEM | Administrator | Operator | User | None Serial: OEM | Administrator | Operator | User | None UserAccounts: On | Off iRMCsettings: On | Off Video Redirection: On | Off Remote Storage: On | Off iRMC S2 91 . DeptX) (1) in the hierarchy tree in Active Directory Users and Computers (see figure 28 on page 92) then the permission groups (security groups) defined for this department are listed in the display area (here: DeptX). You can click on one of the displayed security groups (2) to open the Properties dialog for this security group (here: Maintenance).

.. globally via a directory service User management on the iRMC S2 (2) (1) Figure 28: Properties dialog for the Maintenance security group 92 iRMC S2 ..

globally via a directory service In the LDAP server. Unlike when you assign permissions. iRMC S2 93 . you can specify not only the user permissions but also the preferred shell for a user.. I A user should only belong to a single shell group. Any user who does not belong to a shell group is assigned by default to the Remote Manager group..User management on the iRMC S2 Settings for the preferred shell . – SmashCLP (see page 393). the definition of the preferred shell is purely user-specific and not department-dependent. The sequence of priorities follows the above list (with priority descending from top to bottom). Any user who belongs to multiple shell groups is automatically assigned to the group with the highest priority among these groups. Figure 29: Defining the preferred shell The following groups can be selected: – IPMIbasicMode – IPMIterminalMode – None – RemoteManager (see page 373).

g.5 User management on the iRMC S2 SVS: Permission profiles are defined via roles The associated user roles (authorization roles) that are required are listed directly below each department (figure 27 on page 90).4. Displaying user roles If you select a department (e.. Otherwise... there are no restrictions concerning the number of roles. globally via a directory service 4. task-oriented permission profile for activities on the iRMC S2. the user roles defined for this department (here: DeptX) are displayed (2). Each alert role defines a specific alerting profile for email alerting (see section “Configuring email alerting to global iRMC S2 users” on page 156). DeptX) under SVS in the structure tree for Active Directory Users and Computers (see figure 30) (1) and expand the associated nodes DeptX – Authorization Roles. Each authorization role defines a specific. (1) (2) Figure 30: Display of the user roles in the “Users and Computers” snap-in 94 iRMC S2 . All the roles listed here must be defined in the OU Declarations.2. I The alert roles are listed as well as the authorization roles. The names of the roles can be chosen as required subject to certain syntactic requirements imposed by the employed directory service.

kvms4) under Users in the structure tree for Active Directory Users and Computers (see figure 31) (1) and open the Properties dialog box for this user by choosing Properties – Members from the context menu.. globally via a directory service Displaying permission groups to which a user is assigned If you select a user (e.g.User management on the iRMC S2 . (2) (1) Figure 31: Properties dialog box for the user kvms4 iRMC S2 95 . the permission groups to which the user belongs (here: kvms4) are displayed in the Members tab (2)..

jar on PRIMERGY ServerView Suite DVD 1. Alternatively. This section describes: – The configuration file of the SVS_LdapDeployer – SVS_LdapDeployer – The commands and options of the SVS_LdapDeployer – Typical application scenarios 4. If you do not specify the authentication data in the configuration file or in the command line when calling the SVS_LdapDeployer. The SVS_LdapDeployer is a Java archive (SVS_LdapDeployer.xml that are supplied together with the jar archive SVS_LdapDeployer. I Valid connection data for the connection to the directory server must You can also optionally enter the authentication data for accessing the server. maintaining and deleting the “SVS” and “iRMCgroups” structures To allow global iRMC S2 user management to be able to handled using a directory service... you can specify the authentication data in the command line of the SVS_LdapDeloyer.1 Configuration file (XML file) SVS_LdapDeployer generates LDAP structures on the basis of an XML configuration file.xml and Generic_InitialDeploy. the structure(s) (OU) SVS and iRMCgroups must be created in the LDAP directory service..3. You use the SVS_LdapDeployer to generate and modify the structures SVS and iRMCgroups.Generating. I The syntax of the configuration file is illustrated in the sample always be entered under <Settings> in the input file.4. This input file contains the structure information for the structure(s) SVS and/or iRMCgroups in XML syntax.4. 96 iRMC S2 . globally via a directory service User management on the iRMC S2 4.jar) provided on your PRIMERGY ServerView Suite DVD 1. the SVS_LdapDeployer prompts you to enter the authentication data at runtime.3 SVS_LdapDeployer . configuration files Generic_Settings.

User management on the iRMC S2 4.4.3.2 Starting SVS_LdapDeployer

... globally via a directory service

Proceed as follows to start the SVS_LdapDeployer: Ê Save the Java archive (jar archive) SVS_LdapDeployer.jar in a folder on the directory server. Ê Open the command interface of the directory server. Ê Switch to the folder in which the jar archive SVS_LdapDeployer.jar has been stored. Ê Call the SVS_LdapDeployer using the following syntax:
java -jar SVS_LdapDeployer.jar <command> <file> [<option>...]

I You are informed about the various steps that are being performed
<command> Specifies the action to be performed. The following commands are available: -deploy Creates an LDAP structure for global iRMC / iRMC S2 user management on the directory server (see page 99).

while the SVS_LdapDeployer is running. You will find detailed information in the file log.txt, which is created in the execution folder every time that SVS_LdapDeployer is run.

-delete Deletes an LDAP structure used for global iRMC / iRMC S2 user management from the directory server (see page 101). -import Creates an equivalent LDAP v2 structure from an existing LDAP v1 structure (see page 99). -synchronize Makes corresponding changes in an existing LDAP v1 structure to reflect any changes that you make in an LDAP v2 structure (see page 99). <file> The configuration file (.xml) used as an input file by SVS_LdapDeploy. This configuration file contains the structure information for the structure(s) SVS and/or iRMCgroups in XML syntax.

iRMC S2

97

... globally via a directory service

User management on the iRMC S2

I The syntax of the configuration file is illustrated in the sample
<option> [<option> ...] Option(s) that control execution of the specified command. The following sections describe in detail the individual commands available in SVS_LdapDeployer together with the associated options.

configuration files Generic_Settings.xml and Generic_InitialDeploy.xml that are supplied together with the jar archive SVS_LdapDeployer.jar on PRIMERGY ServerView Suite DVD 1.

I The SVS_LdapDeployer generates all the required subtrees including all
the groups but not the relations between users and groups. You create and assign user entries to groups by means of the corresponding tools in the employed directory service after generating the OUs SVS and/or iRMCgroups in the directory service.

98

iRMC S2

User management on the iRMC S2 4.4.3.3

... globally via a directory service

-deploy: Create or modify an LDAP structure

The -deploy command allows you to create a new LDAP structure on the directory server or to add new entries to an existing LDAP structure.

I Before you delete entries from an existing LDAP structure, you must first
delete the LDAP structure itself using -delete (see page 101) and then generate it again using a suitably adapted configuration file. Syntax:
-deploy [ [ [ <file> [-structure {v1 | v2 | both}] -username <user>] -password <password>][ -store_pwd <path>][ -kloc <path>] -kpwd [<key-password>]]

<file> XML file containing the configuration data.

I The <Data> section in the configuration file must contain all the

necessary roles and departments required for initially generating or expanding a structure.

-structure v1 | -structure v2 | -structure both Creates an LDAP v1 structure or an LDAP v2 structure or an LDAP v1 and an LDAP v2 structure. -username <user> User name for logging in to the directory server. -password <password> Password for the user <user>.

iRMC S2

99

... globally via a directory service

User management on the iRMC S2

-store_pwd Encrypts the password <password> using a randomly generated key and saves the encrypted password in the configuration file after -deploy has been executed successfully. By default, the randomly generated key is stored in the folder in which the SVS_LdapDeployer is executed.

V CAUTION!
You should save the randomly generated key in a safe place. If the predefined target folder is not adequate for your security needs, or if the folder in which the key is saved can also be accessed by other users, use the options -kloc and -kpwd to save the key securely. -kloc <path> Saves the randomly generated key under <path>. If you do not specify this option, the key is saved in the folder in which SVS_LdapDeployer is executed. -kpwd [<password>] Specifies a password to protect the randomly generated key. If you do not specify <password>, the password is automatically generated on the basis of a snapshot of the current runtime environment.

100

iRMC S2

User management on the iRMC S2 4.4.3.4

... globally via a directory service

-delete: Deleting an LDAP structure

The -delete command allows you to remove an LDAP structure from the directory server. Syntax:
-delete [ [ [ <file> [-structure {v1 | v2 | both}] -username <user>] -password <password>][ -store_pwd <path>][ -kloc <path>] -kpwd [<key-password>]]

<file> XML file that specifies the structure to be deleted. -structure v1 | -structure v2 | -structure both Deletes an LDAP v1 structure or an LDAP v2 structure or an LDAP v1 and an LDAP v2 structure. -username <user> User name for logging in to the directory server. -password <password> Password for the user <user>. -stor_pwd Encrypts the password <password> using a randomly generated key and saves the encrypted password in the configuration file after -delete has been executed successfully. By default, the randomly generated key is stored in the folder in which the SVS_LdapDeployer is executed.

V CAUTION!
You should save the randomly generated key in a safe place. If the predefined target folder is not adequate for your security needs, or if the folder in which the key is saved can also be accessed by other users, use the options kloc and -kpwd to save the key securely. -kloc <path> Saves the randomly generated key under <path>. If you do not specify this option, the key is saved in the folder in which SVS_LdapDeployer is executed. -kpwd [<password>] Specifies a password to protect the randomly generated key. If you do not specify <password>, the password is automatically generated on the basis of a snapshot of the current runtime environment.

iRMC S2

101

... globally via a directory service 4.4.3.5

User management on the iRMC S2

-import: Importing an LDAP v1 structure into an LDAP v2 structure

The -import command allows you to generate an equivalent LDAP v2 structure on the directory server from an existing LDAP V1 structure. Syntax:
-import <file>[ -username <user>] [ -password <password>][ -store_pwd <path>][ -kloc <path>] [ -kpwd [<key-password>]]

<file> XML file that specifies the structure to be imported. -username <user> User name for logging in to the directory server. -password <password> Password for the user <user>. -stor_pwd Encrypts the password <password> using a randomly generated key and saves the encrypted password in the configuration file after -import has been executed successfully. By default, the randomly generated key is stored in the folder in which the SVS_LdapDeployer is executed.

V CAUTION!
You should save the randomly generated key in a safe place. If the predefined target folder is not adequate for your security needs, or if the folder in which the key is saved can also be accessed by other users, use the options kloc and -kpwd to save the key securely. -kloc <path> Saves the randomly generated key under <path>. If you do not specify this option, the key is saved in the folder in which SVS_LdapDeployer is executed. -kpwd [<password>] Specifies a password to protect the randomly generated key. If you do not specify <password>, the password is automatically generated on the basis of a snapshot of the current runtime environment.

102

iRMC S2

User management on the iRMC S2 4.4.3.6

... globally via a directory service

-synchronize: Synchronizing changes made in an LDAP v2 structure with an LDAP v1 structure

In a mixed configuration using LDAP v1 and LDAP v2 structures, you can use the -synchronize command to synchronize changes you have made in an LDAP v2 structure with an existing LDAP v1 structure.

I Always make your changes in the LDAP v2 structure!
Syntax:
-import <file>[ -username <user>] [ -password <password>][ -store_pwd <path>][ -kloc <path>] [ -kpwd [<key-password>]]

<file> XML file that specifies the structure to be imported. -username <user> User name for logging in to the directory server. -password <password> Password for the user <user>. -stor_pwd Encrypts the password <password> using a randomly generated key and saves the encrypted password in the configuration file after -synchronize has been executed successfully. By default, the randomly generated key is stored in the folder in which the SVS_LdapDeployer is executed.

V CAUTION!
You should save the randomly generated key in a safe place. If the predefined target folder is not adequate for your security needs, or if the folder in which the key is saved can also be accessed by other users, use the options -kloc and -kpwd to save the key securely. -kloc <path> Saves the randomly generated key under <path>. If you do not specify this option, the key is saved in the folder in which SVS_LdapDeployer is executed.

iRMC S2

103

... globally via a directory service

User management on the iRMC S2

-kpwd [<password>] Specifies a password to protect the randomly generated key. If you do not specify <password>, the password is automatically generated on the basis of a snapshot of the current runtime environment.

104

iRMC S2

User management on the iRMC S2

... globally via a directory service

4.4.4

Typical application scenarios

Four typical scenarios for using SVS_LdapDeployer are described below. 4.4.4.1 Performing an initial configuration in which LDAP v1 and LDAP v2 structures coexist

You wish to set up global user management for iRMC and iRMC S2 for the first time. In order to do this, you require both LDAP v1 and LDAP v2 structures. Recommended method: 1. Generate the Department definitions for LDAP v1 and LDAP v2 structures (iRMCgroups and SVS):
java -jar SVS_LdapDeployer.jar -deploy myInitialDeploy.xml -structure both

2. Any changes you make in the future should then only be made in the LDAP v2 structure and then transferred to the LDAP v1 structure using the synchronize command (see page 103):
java -jar SVS_LdapDeployer.jar -synchronize mySettings.xml

4.4.4.2

Importing an LDAP v1 structure into an LDAP v2 structure

You are already operating global user management for iRMC and iRMC S2 on the basis of LDAP v1 and in future also wish to use LDAP v2. Recommended method: 1. Import (convert) an existing LDAP v1 structure (iRMCgroups) into an LDAP v2 structure (SVS). Both structures are to coexist.
java -jar SVS_LdapDeployer.jar -import mySettings.xml

This statement copies department definitions and the assignment of users to permission groups from the existing LDAP v1 structure into a new LDAP v2 structure. 2. Any changes you make in the future should then only be made in the LDAP v2 structure and then transferred to the LDAP v1 structure using the synchronize command (see page 103):
java -jar SVS_LdapDeployer.jar -synchronize mySettings.xml

iRMC S2

105

... globally via a directory service 4.4.4.3

User management on the iRMC S2

Re-generating or expanding an LDAP v2 structure

You wish to re-generate an LDAP v2 structure or expand an existing LDAP v2 structure. Recommended method:
java -jar SVS_LdapDeployer.jar -deploy myInitialDeploy.xml -structure -structure v2

or
java -jar SVS_LdapDeployer.jar -deploy myInitialDeploy.xml

4.4.4.4

Re-generating an LDAP v2 structure and prompting for and saving authentication data

You wish to re-generate an LDAP v2 structure. The authentication data is to be provided and saved using the command line. Recommended method:
java -jar SVS_LdapDeployer.jar -deploy myInitialDeploy.xml -store_pwd -username admin -password admin

I After the login data has been saved, you can connect to the directory

server using SVS_LdapDeployer without specifying a user name and password. The SVS_LdapDeployer then uses the values stored in the XML configuration file, provided that these are available. SVS_LdapDeployer can only use a saved password if it can decrypt it. This requires you to execute SVS_LdapDeployer in the same runtime environment that applied for the previous call with -store_pwd (see page 100). In this context, “the same runtime environment” means “the same the user on the same computer” or “a user with permission to access the folder under which they key is stored (-kloc option, see page 100)”. call SVS_LdapDeployer in the future. Furthermore, other authentication data can also be used temporarily by explicitly specifying the data in the command line or when requested to do so by SVS_LdapDeployer.

I You can also use user accounts that have already been saved when you

106

iRMC S2

. I Prerequisite: An LDAP v1 and/or an LDAP v2 structure has already been generated in the Active Directory service (see section “SVS_LdapDeployer Generating. You must perform the following steps to integrate iRMC S2 user management in Microsoft Active Directory: 1. 2.4.5 iRMC S2 user management via Microsoft Active Directory This section describes how you integrate iRMC S2 user management in Microsoft Active Directory. globally via Active Directory 4.. Assign iRMC S2 users to iRMC S2 user groups in Active Directory. iRMC S2 107 .User management on the iRMC S2 . maintaining and deleting the “SVS” and “iRMCgroups” structures” on page 96). Configure iRMC S2 LDAP/SSL access at the Active Directory server.

An RSA certificate is required before iRMC S2 can use LDAP via SSL. globally via Active Directory 4. Ê Select the option Use custom settings to generate the key pair and CA certificate. Ê Choose Enterprise root CA. Generate an RSA certificate for the domain controller. Ê Double-click on Certificate Services and make sure that the Certificate Services Web Enrollment Support and Certificate Services CA options are selected. Installation directly on the CA is simpler since fewer steps are required than when installing on another server.Control Panel . choose: Start . you require an Active Directory environment and an installed IIS (Internet Information Services).. choose Certificate Services under Components. The following steps are involved in configuring LDAP access: 1. Proceed as follows to install an Enterprise CA: Ê In the Windows start menu. A reproduction of the SSL copyright can be found on page 164.Add/Remove Windows Components Ê In the wizard for Windows components.. Install an Enterprise CA 2. 3.Software .4. Install the RSA certificate on the server Installing the Enterprise CA I A CA is a “certification authority for certificates”.1 User management on the iRMC S2 Configuring iRMC S2 LDAP/SSL access at the Active Directory server I The iRMC S2-LDAP integration uses the SSL implementation developed by Eric Young on the basis of the OpenSSL Project.. I To install and configure Enterprise CA successfully. An Enterprise CA (certification authority for enterprises) can be installed on the domain controller itself or on another server.5. 108 iRMC S2 . Below is a description of how to install the Enterprise CA on a server other than the domain controller.

To do this. Ê Add the snap-in for local computer certificates. Ê In Windows Explorer.. proceed as follows: Ê Transfer the file containing the certification authority certificate to the domain controller. Ê Load the public certification authority certificate to the certificate directory Trusted Root Certification Authorities on the domain controller. Ê Under Place all certificates in the following store click on Browse and choose Trusted Root Certification Authorities. iRMC S2 109 . Ê Click on Copy to File. Ê Copy the certification authority certificate (CA Certificate) from the current user’s Trusted Root Certification Authorities directory to the local computer's Trusted Root Certification Authorities.Trusted Root Certification Authorities . globally via Active Directory Ê Select Microsoft Base DSS Cryptographic Provider to create DSA certificates of length 1024 bytes. Ê Enter mmc in the Windows prompt window to start the Management Console.. Ê Click on Install Certificate. Ê Navigate to Certificates (Local Computer) .User management on the iRMC S2 . Ê Click on the Details tab in the certificate window. Ê Add the snap-in for local computer certificates. Ê Export the public certification authority certificate (CA Certificate). proceed as follows: Ê Enter mmc in the Windows prompt window to start the Management Console. Ê Add the snap-in for the current user’s certificates. open the certificate from the newly created certification authority.Certificates and double-click. Ê Double-click on the certificate from the newly created certification authority. To do this. Ê Choose a file name for the certification authority certificate and click on Finish.

. in the file request.req to the Saved Request window. Ê Click on Submit a certificate request. Ê Copy the content of the file request.g.3. Ê Download the certificate and save it (e.firm.. 110 iRMC S2 . adapt the specification under “Subject=” to the name of the employed domain controller.1 . e. Ê Select the Web Server certificate template.1.inf with the following content: [Version] Signature="$Windows NT$" [NewRequest] Subject = "CN=<full path of domain controller host>" KeySpec = 1 KeyLength = 1024 Exportable = TRUE MachineKeySet = TRUE SMIME = FALSE PrivateKeyArchive = FALSE UserProtected = FALSE UseExistingKeySet = FALSE ProviderName = "Microsoft RSA SChannel Cryptographic Provider" ProviderType = 12 RequestType = PKCS10 KeyUsage = 0xa0 [EnhancedKeyUsageExtension] OID=1.inf .5.inf request. globally via Active Directory Creating a domain controller certificate User management on the iRMC S2 Proceed as follows to create an RSA certificate for the domain controller: Ê Create a file named request. Ê Click on advanced certificate request. Ê Enter the following command in the Windows prompt window: certreq -new request.fwlab.6.cer).3.5.net”. this is for Server Authentication Ê In the file request. Subject = “CN=domino.7..req Ê Enter the following URL in the certification authority browser: http://localhost/certsrv Ê Click on Request a Certificate.g.

globally via Active Directory Ê Enter the following command in the Windows prompt window: certreq -accept request. Ê Click on Copy to File.. Ê Select Yes.Personal Certificates . Ê Choose a file name for the certificate and click on Finish. Ê Add the snap-in for local computer certificates. iRMC S2 111 . Ê Click on the Details tab in the certificate window.Certificates. Ê Navigate to Certificates (Local Computer) .User management on the iRMC S2 . Ê Double-click on the new server certification authentication certificate. export the private key.. proceed as follows: Ê Enter mmc in the Windows prompt window to start the Management Console. To do this. Ê Assign a password.cer Ê Export the certificate with the private key.

Ê Double-click on the domain controller certificate. Ê Add the snap-in for local computer certificates. Ê Click on Install Certificate. Ê Add the snap-in for the current user’s certificates. Ê Under Place all certificates in the following store click on Browse and choose Personal Certificates. Ê Enter mmc in the Windows prompt window to start the Management Console.. globally via Active Directory User management on the iRMC S2 Installing the domain controller certificate on the server Proceed as follows to install the domain controller certificate on the server: Ê Copy the domain controller certificate file that has just been created to the domain controller. Ê Copy the domain controller certificate from the current user’s Personal Certificates directory to the local computer's Personal Certificates directory.. Ê Use the password which you assigned when exporting the certificate.. 112 iRMC S2 .

5.User management on the iRMC S2 4.4. or – on the basis of the role entry / group entry I The example below uses the LDAP v2 structure to describe assignment based on the role entry in the OU SVS. Figure 32: Active Directory Users and Computers snap-in Ê Double-click the permission group (here: Administrator). the group entries are stored in the OU iRMCgroups.. globally via Active Directory Assigning an iRMC S2 user to a role (permission group) You can assign iRMC S2 users to iRMC S2 permission groups either – on the basis of the user entry.2 . The assignment procedure on the basis of the user entry is very similar. In the LDAP v1 structure.. Proceed as follows: Ê Open the snap-in Active Directory Users and Computers. The Administrator Properties dialog opens (see figure 33 on page 114): iRMC S2 113 . I The users must be entered in the groups “manually” in Active Directory.

globally via Active Directory User management on the iRMC S2 Figure 33: Administrator Properties dialog Ê Select the Members tab... button. The Select Users. Ê Click on the Add. or Computers dialog opens (see figure 34 on page 115). 114 iRMC S2 .. Contacts...

or Computers dialog opens (see figure 36 on page 116).User management on the iRMC S2 . I Users may also be entered at a different location in the directory. The Locations dialog opens. Contacts. or Computers dialog Ê Click on the Locations. this is the OU Users.... Click OK to confirm. The Select Users. Figure 35: Locations dialog Ê Select the container (OU) containing your users. Contacts.). 115 iRMC S2 . button.. globally via Active Directory Figure 34: Select Users. (By default.

. The Select Users... button.. Contacts. 116 iRMC S2 . globally via Active Directory User management on the iRMC S2 Figure 36: Select Users. or Computers dialog Ê Click on the Advanced. or Computers extended dialog opens (see figure 37 on page 117). Contacts..

Contacts. iRMC S2 117 .searching Ê Click the Find Now button to display all the users in your domain. or Computers dialog . Under Search results: in the display area you can now view the search result (see figure 38 on page 118). globally via Active Directory Figure 37: Select Users.User management on the iRMC S2 ...

The selected users are now displayed (see figure 39 on page 119). 118 iRMC S2 .displaying the search results Ê Select the users who are to be added to the group and click OK to confirm. globally via Active Directory User management on the iRMC S2 Figure 38: Select Users. or Computers dialog .... Contacts.

or Computers dialog .confirming the search results Ê Confirm by clicking OK.User management on the iRMC S2 .. iRMC S2 119 . Contacts.. globally via Active Directory Figure 39: Select Users.

tar.. globally via Novell eDirectory User management on the iRMC S2 4. No extensive eDirectory knowledge is required. – 512 MB free RAM 120 iRMC S2 .1 I Use the specified version or a more recent version of the components listed below.6. iMan_26_linux_32.tar.gz The following system requirements must be fulfilled in order to install and operate Novell eDirectory: – OpenSSL must be installed.gz – eDirectory 8.8: 20060526_0800_Linux_88-SP1_FINAL. you can skip the next three sections and continue with section “Integrating iRMC S2 user management in Novell eDirectory” on page 134.tgz for SuSE. Novell eDirectory (formerly NDS) consists of the following software components: – eDirectory 8. I The installation and configuration of Novell eDirectory are described in detail below..npm – iManager: iMan_26_linux_64.tgz otherwise – ConsoleOne: c1_136f-linux. Software components and system requirements 4. If you are already familiar with Novell eDirectory.6 iRMC S2 user management via Novell eDirectory This section provides you with information about the following topics: – The Novell eDirectory system components and system requirements – Installing Novell eDirectory – Configuring Novell eDirectory – Integrating iRMC S2 user management in Novell eDirectory – Tips on administering Novell eDirectory.8: eDir_88_iMan26_Plugins.4.4. before starting the Novell eDirectory installation. I If OpenSSL is not already installed: Ê Install OpenSSL..

4. Ê Add the following line to /etc/sysconfig/network/ifroute-eth0: 224.0. proceed as follows: Ê Create or (if it already exists) open the file /etc/sysconfig/network/ifroute-eth0.0 240. it is necessary to install the following components: – eDirectory Server and administrations utilities – iManager (administrations utility) – ConsoleOne (administrations utility) I Prerequisites for the installation of Novell eDirectory: – A Linux server operating system must be fully installed and running. 8443.0.. iRMC S2 121 . For SuSE Linux.0.0.User management on the iRMC S2 4.0 eth0 This adapts eth0 to the system configuration.2 Installing Novell eDirectory . globally via Novell eDirectory To install Novell eDirectory. For OpenSuSE. – The firewall must be configured for connections to the following ports: 8080.. 81.0 0. 389.0. you configure this in the file /etc/sysconfig/SuSEfirewall2: Ê Add the entry FW_SERVICES_EXT_TCP to the file /etc/sysconfig/SuSEfirewall2 as follows: FW_SERVICES_EXT_TCP="8080 8443 9009 81 389 636" – In accordance with the eDirectory Installation Guide.6. 9009. the system must be set up for multicast routing.0. 636.

/home/eDirectory) before you can use the procedure below to perform installation. The eDirectory packages are then installed. Ê If you are asked which program you want to install: Enter “1” to install the Novell eDirectory server and press the [Enter] key to confirm.tar..gz Installing the eDirectory Server and administration utilities Proceed as follows: Ê Log in with root permission (superuser). – All the files required for the installation must have been copied to a directory (e./nds-install : . Installing eDirectory Server Ê Go to the setup subdirectory of this eDirectory directory: cd eDirectory/setup Ê Call the installation script ..gz iMan_26_linux_64. /home/eDirectory has a new subdirectory named eDirectory.tar. Ê Switch to the directory containing the files required for installation (in our example: /home/eDirectory): cd /home/eDirectory Ê Extract the archive 20060526_0800_Linux_88-SP1_FINAL.gz After extraction.gz: tar -xzvf 20060526_0800_Linux_88-SP1_FINAL. the eDirectory utilities./nds-install Ê Accept the EULA with “y” and confirm with the [Enter] key.tar.g.. the iManager and ConsoleOne: – The root permission is required in order to perform installation.tar.tgz c1_136f-linux. globally via Novell eDirectory User management on the iRMC S2 I Prerequisites for the installation of the eDirectory Server. These files are as follows: 20060526_0800_Linux_88-SP1_FINAL. 122 iRMC S2 .

/nds-install Ê Accept the EULA with “y” and confirm with the [Enter] key. Ê If you are asked which program you want to install: Enter “2” to install the Novell eDirectory administration utilities and press the [Enter] key to confirm.. The eDirectory administration utilities are then installed. globally via Novell eDirectory After installation of the Novell eDirectory Server.bashrc) and enter the following lines in the specified sequence ahead of “# End of . iRMC S2 123 .. open your configuration file (in the example: /etc/bash.User management on the iRMC S2 . you must update the names for the paths to the eDirectory in a number of environment variables and export these variables.. Ê To do this.”: export PATH/opt/novell/eDirectory/bin:/opt/novell/eDirectory/ sbin:$PATH export LD_LIBRARY_PATH=/opt/novell/eDirectory/lib:/ opt/novell/eDirectory/lib/nds-modules:/opt/novell/ lib:$LD_LIBRARY_PATH export MANPATH=/opt/novell/man:/opt/novell/eDirectory/ man:$MANPATH export TEXTDOMAINDIR=/opt/novell/eDirectory/share/ locale:$TEXTDOMAINDIR Ê Close the terminal and open a new terminal in order to export the environment variables. Installing the eDirectory administration utilities Ê Go to the setup subdirectory of the eDirectory directory: cd eDirectory/setup Ê Call the installation script: ..

. Ê Press [Enter] to use the default path for the download. Ê Go to the installs subdirectory of iManager: cd iManager/installs/linux Ê Call the installation script: . Ê Press [Enter] to use the default path for installation. The installation program searches the internet for downloads. Tomcat. Ê Extract the archive iMan_26_linux_64. This can take a few minutes. 124 iRMC S2 .6. Ê Select All to download all the plug-ins. Proceed as follows: Ê Log in with root permission (superuser). Ê Select 1... globally via Novell eDirectory Installing and calling iManager User management on the iRMC S2 I iManager is the recommended tool for installing Novell eDirectory. Ê Select 1.tgz. JVM for iManager installation. /home/eDirectory has a new subdirectory named iManager./iManagerInstallLinux. Ê Select 2.Yes to install the locally available plug-ins.tgz After extraction.bin Ê Select the language for the output of installation messages. Ê Click through and accept the EULA.Yes for plug-in download. Ê Accept the default SSL port (8443) for Tomcat. Ê Go to the directory /home/eDirectory: cd /home/eDirectory Whether installing in SLES10 or in OpenSuSE.tgz: tar -xzvf iMan_26_linux_64. Ê Select 1. Ê Accept the default port (8080) for Tomcat. You are then asked to select the plug-ins that you want to install. you use the archive *_64.No for automatic Apache configuration (optional).Novell iManager 2.

in order to terminate installation. iRMC S2 125 .. “root.g. it is possible that not all the context menu's pop-up windows will be displayed.User management on the iRMC S2 . globally via Novell eDirectory Ê Accept the default JK connector port (9009) for Tomcat... In Mozilla Firefox. Ê Enter the administration user ID (e. you can use the following URL to log in at iManager via a web browser. https://<IP address of the eDirectory server>:8443/nps I Novell recommends that you use Microsoft Internet Explorer or Mozilla Firefox as your web browser. Logging in to Novell iManager After installation.g.fts”) for the user with the appropriate administration permissions. Ê Accept the summary of your entries which is displayed with 1-OK. “fwlab”) for the user with the appropriate administration permissions. Ê Enter the tree name (e..

Ê Enter “8” to install all the snap-ins. globally via Novell eDirectory Installing and starting ConsoleOne User management on the iRMC S2 ConsoleOne is another administration tool for Novell eDirectory. However.tar. it is.gz: tar -xzvf c1_136f-linux. Ê Go to the directory /home/eDirectory: cd /home/eDirectory Ê Extract the ConsoleOne archive c1_136f-linux.tar. I Since root permission is required in order to work with ConsoleOne. sufficient to export the ID superuser Root. the system-wide export of the path name is presented below. 126 iRMC S2 .gz After extraction. Proceed as follows to install ConsoleOne: Ê Log in with root permission (superuser) at eDirectory Server. However./c1-install Ê Select the language for the output of installation messages. Ê Go to the directory Linux: cd Linux Ê Call the installation script c1-install: .. /home/eDirectory has a new subdirectory named Linux. ConsoleOne needs the path to an installed Java runtime environment.. in principle. the system-wide export of the path name requires modifications in the bash profile.. This means that normal users can also work with ConsoleOne if they have root permission. You can export the corresponding path name to the environment variable C1_JRE_HOME.

. you can also specify the path name of any other Java runtime environment installed on the eDirectory Server..mydomain:81 Starting ConsoleOne You start ConsoleOne in the system prompt using the following command: /usr/ConsoleOne/bin/ConsoleOne iRMC S2 127 .bashrc) Ê Enter the following line in the configuration file in front of “# End of . However. globally via Novell eDirectory Ê Open the configuration file for editing (in the example: /etc/bash.4.User management on the iRMC S2 Proceed as follows: . Ê Open the file hosts.nds or via the SLP service and multicast. Ê Generate the file hosts.nds if it does not yet exist.mycomputer..nds and insert the following lines: #Syntax: TREENAME..”: export C1_JRE_HOME=/opt/novell/j2sdk1.FQDN:PORT MY_Tree.2_05/jre I The java runtime environment installed together with eDirectory is ConsoleOne obtains the available tree hierarchies either via the local configuration file hosts. Proceed as follows to insert your tree hierarchy in the configuration file: Ê Go to the configuration directory: cd /etc used here.

Admin User Fully distinguished name (fully distinguished name of the object path and attributes) of the user with permission to perform administration. for example. e... Creating an NDS tree Create an NDS (Network Directory Service) tree using the utility ndsmanage.dc=mycompany NCP Port Specify port 81.you specify the name of the PRIMERGY server on which the LDAP server is running. Configure eDirectory for LDAP.g.g.. Server Context Fully distinguished name (fully distinguished name of the object path and attributes) of the container which contains the server object. 128 iRMC S2 . Instance Location Specify the path: /home/root/instance0 Configuration File Specify the following file: /home/root /instance0/ndsconf Password for admin user Enter the administrator password here. globally via Novell eDirectory 4.dc=mycompany.dc=organization. Test eDirectory access via LDAP Browser.g. dc=organization. e. 3.6. For Server Name. ndsmanage requires the following information to do this: TREE NAME Unique name in the network for the new NDS tree.3 Configuring Novell eDirectory User management on the iRMC S2 Perform the following steps to configure Novell eDirectory: 1. e. lin36-root-0. Create an NDS tree 2. cn=admin.4. Server Name Name of an instance of server class in eDirectory. MY_TREE.

Ê After configuring the NDS tree. globally via Novell eDirectory Proceed as follows to configure the NDS tree: Ê Open a command box. restart the PRIMERGY server in order to activate the configuration.User management on the iRMC S2 .. Ê Enter “y” to create a new tree. iRMC S2 129 . to recreate the NDS tree. Ê Start the utility ndsmanage by entering the command ndsmanage: ndsmanage Ê Enter “c” to generate a new instance of the class server. ndsmanage configures the NDS tree. Ê Enter “y” to continue configuration. Configuring eDirectory for LDAP The following steps are involved in configuring eDirectory for LDAP: – Install Role Based Services (RBS) – Install plug-in modules – Configure Role Based Services (RBS) – Configure eDirectory with/without SSL/TLS support Proceed as follows to complete the individual points: Ê Log in under the administrator ID (Admin) at iManager via a web browser. Server Context etc..e. Server Name. Ê Go to the directory /home/eDirectory. i. ndsmanage then queries the values for TREE NAME. in sequence (see page 128). Once input is complete.

130 iRMC S2 . this is “mycompany”.RBS Configuration Ê Start the RBS Configuration Wizard. Ê Click Install. Ê Click Install. select all the modules. Configuring Role Based Services (RBS) Ê In the page Available Novell Plug-in Modules. select the Configure tap (by clicking on the desk icon). Ê In the Configure tab. However. since the iRMC S2 firmware is configured for the use of RSA/MD5 certificates. SSL/TLS-secured. select the eDirectory-specific package eDir_88_iMan26_Plugins.. globally via Novell eDirectory Installing Role Based Services (RBS). global iRMC S2 user management via eDirectory requires an RSA/MD5 certificate of 1024 bytes in length. select Role Based Services . select Plug-in installation .) Installing plug-in modules Proceed as follows: Ê In iManager.Available Novell Plug-in Modules Ê In the modules listed in the page Available Novell Plug-in Modules. (In the example above. If you are not certain. select all the modules that are required for LDAP integration.. Ê In the Configure tab. select the Configure tap (by clicking on the desk icon)..npm. Proceed as follows: Ê In iManager. Configuring eDirectory for SSL/TLS-secured access I During eDirectory installation. a temporary certificate is generated with the result that access to the eDirectory is secured by SSL/TLS by default. User management on the iRMC S2 Install RBS using the iManager Configuration Wizard. Ê Assign RBS2 to the container that is to be managed.

g.Connection. The Connection tab contains a drop-down list which displays all the certificates installed on the system. globally via Novell eDirectory You create an RSA/MD5 certificate of length 1024 bytes as follows using ConsoleOne: Ê Log into the LDAP server under your administrator ID (Admin) and start ConsoleOne. Ê Select LDAP . If you want to use LDAP without SSL then you must perform the following steps: 1.LDAP Server . Enable a non-SSL-secured LDAP. iRMC S2 131 . Reload the LDAP configuration. Ê Log in at iManager with valid authentication data.. perform the following steps in iManager: Ê Start iManager via the web browser. treename/mycompany/myorganisation). web browser login at the eDirectory server is only possible via an SSL connection. specify the following values: 1. 2. Consequently. 1024 bits 2. signature RSA/MD5 A new signature of the required type is created. Configuring eDirectory for non-SSL-secured access I Anonymous login and the transfer of plain text passwords via non- secured channels are deactivated by default in eDirectory.LDAP Options . Ê Navigate to your corporate structure's root directory (e. To activate the newly created certificate for the SSL-secured LDAP connection.User management on the iRMC S2 .custom to create a new object of class NDSPKI:Key Material. Ê Select the required certificate in the drop-down list.NDSPKI key material .connection. Relax the bind restrictions. Ê In the dialog which is then displayed. SSL or TLS 3.. 3. Ê Select New Object .

Ê In the Connection tab. Ê Click OK. Ê Start iManager via the web browser. click the Apply button. Ê Click with the mouse to highlight the LDAP Server object and select Modify Object in the associated context menu.connection. 132 iRMC S2 .. Ê Set the value to “0”. Mycompany). Ê In the General tab. Ê In the Other sheet. Ê Select LDAP . Ê In the General tab. 3.. Ê Under Valued Attributes. in the associated context menu.LDAP Group . Ê In the object tree. Ê Start ConsoleOne and log in to eDirectory. navigate to the LDAP Server object.. select ldapBindRestrictions Ê Click the Edit button.General. 2. The LDAP server object is then displayed on the right-hand side of the window.. Ê Log in at iManager with valid authentication data.LDAP Options . Reload the LDAP configuration.. Ê Log in at iManager with valid authentication data.Connection. deactivate the option Require TLS for all Operations. Ê Select the Roles and Tasks view. click Refresh NLDAP Server Now.LDAP Server . globally via Novell eDirectory Proceed as follows: User management on the iRMC S2 1. Enable a non-SSL-secured LDAP. Relax the bind restrictions.g.LDAP Options . Ê In the right-hand content frame. Ê Right-click to highlight the LDAP Server object and select Properties. Ê Select LDAP . deactivate the option Require TLS for Simple Binds with password. open the Other sheet. Ê Click on the Base DN object at the left of the window (e.

After successfully completing steps 1 .. iRMC S2 133 . globally via Novell eDirectory Testing eDirectory access via LDAP Browser. you should be able to establish a connection to eDirectory via the LDAP Browser utility.User management on the iRMC S2 . proceed as follows: Ê Check that SSL is active (see page 131). If this attempt fails.3 above. Figure 40: Testing LDAP access to eDirectory: SSL activated Ê Try to log in at eDirectory under the administrator ID (in the example: admin) via a non-SSL-secured connection.. You can use Jarek Gavor's LDAP Browser (see page 150) to test this connection as follows: Ê Try to log in at eDirectory under the administrator ID (in the example: admin) via an SSL connection.

– Declare the iRMC groups and user permissions in eDirectory.6. – Assign users to the permission groups. globally via Novell eDirectory User management on the iRMC S2 Figure 41: Testing LDAP access to eDirectory: SSL not activated Ê If the login fails again: Relax the bind restrictions (see page 131). 134 iRMC S2 . maintaining and deleting the “SVS” and “iRMCgroups” structures” on page 96).4 Integrating iRMC S2 user management in Novell eDirectory I Prerequisite: An LDAP v1 and/or an LDAP v2 structure has already been generated in the eDirectory directory service (see section “SVS_LdapDeployer Generating..4... 4. You must perform the following steps in order to integrate iRMC S2 user management in Novell eDirectory: – Generating the principal iRMC user.

figure 42 on page 135 illustrates this process for global iRMC S2 user management with Novell eDirectory. 4) The iRMC asks the eDirectory server to provide the user permissions of the user User1. SSL-based communication iRMC: Bind as Principal User 1 iRMC is authenticated iRMC determines the fully-qualified DN of User1 2 iRMC 3 eDirectory Bind with User1's DN User1 is authenticated iRMC determines the user permissions of User1 User permissions 4 1) The iRMC logs in at the eDirectory server with the predefined.. globally via Novell eDirectory LDAP authentication process for iRMC S2 users in eDirectory The authentication of a global iRMC S2 user on login at the iRMC S2 is performed in accordance with a predefined process (see page 60).. Figure 42: Authentication diagram for global iRMC S2 permissions iRMC S2 135 .User management on the iRMC S2 . known permission data (iRMC setting) as “Principal User” and waits for the successful bind. The establishment of a connection and login with the corresponding login information is referred to as a BIND operation. 3) The iRMC logs in at the eDirectory server with the fully-qualified DN of the user User1 and waits for the successful bind. 2) The iRMC asks the eDirectory server to provide the fully qualified Distinguished Name (DN) of the user with “cn=User1”. eDirectory determines the DN from the preconfigured subtree (iRMC setting).

. Creating the Principal User for the iRMC S2 Proceed as follows to create the Principal User for the iRMC S2: Ê Log in at iManager with valid authentication data. Ê Enter the necessary specifications in the displayed template.Configuring the directory service at the iRMC S2” on page 333).Create User. an object in eDirectory possesses only very limited query and search permissions in an LDAP tree. the permissions assigned to an OU and identified as “inherited” are automatically passed on to the objects in this group. By default. I The Principal User's Distinguished Name (DN) and password must The user's Context: may be located at any position in the tree.e. 136 iRMC S2 .. which contains the DNs in the page Directory Service Configuration page of the iRMC S2 web interface (see page 333). Assigning user permissions to the iRMC groups and users match the corresponding specifications for the iRMC S2 configuration (see section “Directory Service Configuration (LDAP) . In this case.g. You may assign permissions either to an individual object (i. globally via Novell eDirectory User management on the iRMC S2 I You configure the “Principal User's” permission data and the subtree I A user's CN must be unique within the searched subtree. Ê Select Users . you must assign this object the corresponding permissions. a specific user) or to a group of objects which are collated in the same organizational unit (OU) such as iRMCgroups / SVS or people.. Ê Select Roles and Tasks. people). If an object is to be able to query all the attributes in one or more subtrees. Ê Assign the Principal User search permissions for the following subtrees: – Subtree (OU) iRMCgroups or SVS – Subtree (OU) that contains the users (e.

. Ê In the menu tree structure. Ê Under Trustee Name.. Once the search operation has been completed. globally via Novell eDirectory I To integrate iRMC S2 user management in Novell eDirectory. A progress display indicates the status of the search.User management on the iRMC S2 .sbdr4) to which the permission is to be granted. Ê In iManager. specify the name of the object (in figure 43 on page 138 iRMCgroups. it is necessary to assign search permissions to the following objects (trustees): – Principal User – Subtree which contains the iRMC S2 users Detailed information on how to do this can be found below.Rights to Other Objects. iRMC S2 137 . click the Roles and Tasks button. Ê Click OK.sbrd4 and SVS. specify the eDirectory subtree (iRMCgroups / SVS) which iManager is to search through for all the objects for which the trustee Users currently has read permission. Ê Under Context to Search From. The page Rights to Other Objects is displayed. the page Rights to Other Objects is displayed with the results of the search (see figure 43 on page 138). Proceed as follows to assign an object search permissions for all attributes: Ê Start iManager via the web browser. select Rights . Ê Log in at iManager with valid authentication data.

globally via Novell eDirectory User management on the iRMC S2 Figure 43: iManager .Rights To Other Objects I If no object is displayed under Object Name. 138 iRMC S2 .. Ê Click Assigned Rights.. Ê Use the object selector button to select the object for which you want to assign the trustee a permission. Ê Assign the trustee additional permissions if necessary: Ê Click Add Object.Roles and Tasks . If the property [All Attributes Rights] is not displayed: Ê Click Add Property.. then the trustee currently has no permissions within the specified context. The Add Property window is displayed (see figure 44 on page 139).

User management on the iRMC S2 .. iRMC S2 139 . Ê Click Apply to activate your settings.Roles and Tasks . globally via Novell eDirectory Figure 44: iManager .. This authorizes the user/user group to query all the attributes in the selected object's subtree.Add Property Ê Highlight the property [All Attributes Rights] and click OK to add it. enable the options Compare.Rights To Other Objects . Ê For the property [All Attributes Rights]. Read and Inherit and click OK to confirm.

sbrd4. globally via Novell eDirectory 4. – In the example of the LDAP v2 structure (see figure 46 on page 141) this is: Administrator. The Modify Group page is displayed. OU people to a permission group. The Members tab of the Modify Group page is displayed: 140 iRMC S2 .AuthorizationRoles. Proceed as follows: Ê Start iManager via the web browser.Departments.SVS. – In the example of the LDAP v1 structure (see figure 45 on page 141). The assignment procedure on the basis of the user entry is very similar.4.. Ê Perform the following steps for all the permission groups to which you want to assign iRMC S2 users: Ê Use the object selector button to select the permission group to which you want to add iRMC S2 users. this is: Administrator..DeptX.6.. The assignment starting from the group entry / role entry is explained.Modify Group. Ê Select Groups .iRMCgroups. Ê Select the Members tab.5 User management on the iRMC S2 Assigning an iRMC S2 user to a permission group You can assign iRMC S2 users (for instance from the OU people) to the iRMC permission groups either – starting from the user entry (preferable if there only a few user entries) or – starting from the role entry / group entry (preferable if there are a lot of user entries). Ê Log in at iManager with valid authentication data.DeptX.sbrd4.Departments. Ê Select Roles and Tasks. I The following example shows the assignment of iRMC S2 users from an I The users must be entered in the groups “manually” in eDirectory.

Roles and Tasks .Modify Group .“Members” tab (LDAP v2) Ê Perform the following steps for all the users of the OU people which you want to assign to the iRMC group: Ê Click the object selector button . globally via Novell eDirectory Figure 45: iManager . iRMC S2 141 . The Object Selector (Browser) window is opened (see figure 47 on page 142).Modify Group ..“Members” tab (LDAP v1) Figure 46: iManager .Roles and Tasks ..User management on the iRMC S2 .

select the required user(s) in the OU people and click OK to confirm. globally via Novell eDirectory User management on the iRMC S2 Figure 47: Assigning users to the iRMC group ... The selected users are now listed in the display area in the Members tab of the Modify Group page (see figure 48 on page 143). 142 iRMC S2 ..selecting users Ê In the Object Selector (Browser) window.

sbdr4). globally via Novell eDirectory Figure 48: Display of the selected iRMC S2 users in the “Members LDAP v1” tab Figure 49: Display of the selected iRMC S2 users in the “Members LDAP v2” tab Ê Confirm with Apply or OK in order to add the selected users to the iRMC group (here: .SVS. .iRMCgroups.... ... iRMC S2 143 ..sbdr4 or .User management on the iRMC S2 .

Proceed as follows to configure a tree: Ê Under My World. Password: <password> 3. for any unidentifiable reason. Login-Name: root 2. no tree is configured.6. Context: mycompany 144 iRMC S2 .6 User management on the iRMC S2 Tips on administering Novell eDirectory.. Tree: MY_TREE 4. select the node NDS.Authenticate Ê Enter the following authentication data for login: 1. Ê Log in with root permission. Restarting the NDS daemon Proceed as follows to restart the NDS daemon: Ê Open the command box. globally via Novell eDirectory 4. Ê Execute the following command: rcndsd restart If. I If you are starting ConsoleOne for the first time. the nldap daemon fails to start: Ê Start the lndap daemon “manually”: /etc/init.d/nldap restart If iManager does not respond: Ê Restart iManager: /etc/init.. Ê In the menu bar.. select: File .4.d/novell-tomcat4 restart Reloading the configuration of the NLDAP server Proceed as follows: Ê Start ConsoleOne and log in to eDirectory.

For example. For this latter task... enter dstrace TIME.. I You are very strongly recommended to activate the modules LDAP and TIME by making the following entry: dstrace LDAP TIME Ê Terminate ndstrace by entering quit. Configuring ndstrace Ê Go to the eDirectory directory /home/eDirectory: cd /home/eDirectory Ê Start screen by means of the command screen. Ê Right-click on the LDAP Server object and select Properties. in the context menu. This terminates the configuration of ndstrace.g. The LDAP Server object is then displayed in the right-hand side of the window. bash). Ê Start ndstrace with the command ndstrace. The following procedure is recommended: Ê Open the command box (e. Ê Select the modules that you want to activate. you use the screen tool. if you want to display the times at which events occurred..User management on the iRMC S2 . click the Base DN object (Mycompany). Ê In the General tab. The purpose of the configuration described below is to redirect the output from ndstrace to a file and display the content of this file at another terminal. iRMC S2 145 . globally via Novell eDirectory Ê In the left-hand part of the window. click the Refresh NLDAP Server Now button. Configuring the NDS message trace The nds daemon generates debug and log messages which you can trace using the ndstrace tool.

use the key combination [Ctrl] + [a]. [Ctrl] + [c] Ê Activate log recording: tail -f ./ndstrace.... (The terminals are numbered from 0 to 9) 146 iRMC S2 . globally via Novell eDirectory Outputting messages at a second terminal User management on the iRMC S2 Ê Start ndstrace and redirect message output: ndstrace -l >ndstrace.log Ê To switch between the virtual terminals. [Ctrl] + [0].log Ê Use the following key combination to open a second terminal: [Ctrl] + [a].

com/services/ssh_test_certificate. 4.umn.7.org.openssl.html http://www. For more detailed information.flatmtn.2 Creating SSL certificates You should create a certificate with the following properties: – Key length: 1024 bits – md5RSAEnc You use OpenSSL to create key pairs and signed certificates (self-signed or signed by an external CA).com/tutorials/web-server/apache-ssl-certs.freebsdmadeeasy.4. For OpenSuSE.1 Installing OpenLDAP I Before installing OpenLDAP.html http://www.. proceed as follows: Ê In the file.html iRMC S2 147 .4. – Tips on OpenLDAP administration 4. – Integrating iRMC S2 user management in OpenLDAP.User management on the iRMC S2 .akadia.php http://www. /etc/sysconfig/SuSEfirewall2 extend the option FW_SERVICES_EXT_TCP as follows: FW_SERVICES_EXT_TCP=“389 636” To install the packages OpenSSL and OpenLDAP2 from the distribution medium.edu/~brams006/selfsign.4.tc. use the setup tool YaST. see the OpenSSL home page at http://www.7 iRMC S2 user management via OpenLDAP This section provides you with information about the following topics: – Installing OpenLDAP (Linux). you must configure the firewall for connections to the ports 389 and 636. – Configuring OpenLDAP.. – Creating an SSL certificate. globally via OpenLDAP 4.com/computer/Linux-SSLCertificates. The following links provide instructions on setting up a CA and creating test certificates: – – – – http://www.7.

key. Ê Select Databases to create a new database.pem -out server. Ê Under Global Settings/Allow Settings.key.cer.key. or – by assigning the LDAP daemon ldap read permission for the files containing the certificates and private keys.enc.7.cer. Ê Declare the paths of the files created during installation (see section “Installing OpenLDAP” on page 147). 148 iRMC S2 .pem. globally via OpenLDAP User management on the iRMC S2 Following certificate creation. activate the setting LDAPv2-Bind. 4.. you must have the following three PEM files: – Root certificate: root.pem should only assign the LDAP daemon (ldap) read permission for the file server.3 Configuring OpenLDAP Proceed as follows to configure OpenLDAP: Ê Start the Yast setup tool and select LDAP-Server-Configuration.pem I The private key must not be encrypted with a pass phrase since you You use the following command to remove the pass phrase: openssl rsa -in server.pem – Private key: server. you can do this by – setting the owner of the files with the certificates and private keys to “ldap”. Ê Make sure that certificates and private keys in the file system can be read by the LDAP service. Ê Select Global Settings/TLS Settings: Ê Activate the setting TLS..key..pem – Server certificate: server.4. Since openldap is executed under the uid/guid=ldap.

.pem I If the configuration created by YaST for SSL does not function.. check that the following obligatory entries are present in the file /etc/openldap/slapd.key.User management on the iRMC S2 .pem TLSCertificateFile /path/to/certificate. globally via OpenLDAP I If the configuration created by YaST does not function overall.conf: allow bind_v2 TLSCACertificateFile /path/to/ca-certificate.pem TLSCertificateKeyFile /path/to/privat. check that the following entry is present in the configuration file /etc/sysconfig/openldap: OPENLDAP_START_LDAPS=“yes” iRMC S2 149 .

for example the LDAP Browser\Editor published by Jarek Gawor (see page 150).: JAVA_HOME=C:\Program Files\Jave\jdk1.. Ê Set the environment variable JAVA_HOME to the installation directory for the JAVA runtime environment. I Prerequisite: An LDAP v1 and/or an LDAP v2 structure has already been generated in the OpenLDAP directory service (see section “SVS_LdapDeployer Generating. I To generate the Principal User (ObjectClass: Person) use an LDAP browser.7.4.5. LDAP Browser\Editor published by Jarek Gawor The LDAP Browser\Editor published by Jarek Gawor is easy to use via a graphical user interface.g.. Proceed as follows to install the LDAP Browser\Editor: Ê Unpack the Zip archive Browser281.zip to an installation directory of your choice.4 User management on the iRMC S2 Integrating iRMC S2 user management in OpenLDAP.0_06 150 iRMC S2 . The integration of iRMC S2 user management in OpenLDAP comprises the following steps: – Generating the principal iRMC user. – Creating the new iRMC S2 user and assigning this user to the permission group. e. globally via OpenLDAP 4. The tool is available for download in the internet.. maintaining and deleting the “SVS” and “iRMCgroups” structures” on page 96).

Ê Log in at the OpenLDAP directory service with valid authentication data. Ê Select the subtree (subgroup) in which the Principal User is to be created..Configuring the directory service at the iRMC S2” on page 333). Ê Open the Edit menu. Proceed as follows: Ê Start the LDAP Browser. Ê Edit the Distinguished Name DN. Ê Enter a Surname SN. Ê Click Set and enter a password. The text below describes how you use the Jarek Gawor LDAP Browser\Editor to generate the Principal User. Ê Select Person.. Ê Select Add Entry.User management on the iRMC S2 Generating the Principal User . for example the LDAP Browser\Editor published by Jarek Gawor (see page 150). The Principal User can be created anywhere in the tree. iRMC S2 151 . globally via OpenLDAP I To generate the Principal User (ObjectClass: Person) use an LDAP browser. match the corresponding specifications for the iRMC S2 configuration (see section “Directory Service Configuration (LDAP) . Ê Click Apply. I The Principal User's Distinguished Name (DN) and password must .

. Ê Edit the Distinguished Name DN. Ê Select Person. Proceed as follows: Ê Start the LDAP Browser. Ê Log in at the OpenLDAP directory service with valid authentication data. The following text describes how you use the Jarek Gawor LDAP Browser\Editor to create a new iRMC S2 user and add this user to the permission group. for example the Jarek Gawor LDAP Browser\Editor (see page 150). you use an LDAP browser. Ê Click Set and enter the password.. Ê Enter a Surname SN. Ê Select Add Entry. The new user can be created anywhere in the tree. 152 iRMC S2 .. Ê Create a new user. globally via OpenLDAP User management on the iRMC S2 Creating the new iRMC S2 user and assigning this user to the permission groups. To do this. proceed as follows: Ê Select the subtree (subgroup) in which the new user is to be created. Ê Open the Edit menu. I To create a new user (ObjectClass Person) and assign a user to the permission group. Ê Click Apply.

ou=SVS.ou=iRMCgroups. Ê Specify “Member” as the attribute name.dc=mycompany Ê Open the Edit menu. globally via OpenLDAP Ê Assign the user you have just created to the permission group.ou=Departments. To do this.dc=mycompany iRMC S2 153 . dc=myorganisation. specify the fullyqualified DN of the user you have just created. dc=myorganisation..ou=YourDepartment. proceed as follows: Ê Select the iRMCgroups or SVS subtree (subgroup) to which the user is to belong.ou=Departments. Ê Select Add Attribute.ou=Departments. i.ou=YourDepartment.dc=mycompany or cn=UserKVM. dc=myorganisation.e.e.ou=iRMCgroups.User management on the iRMC S2 ..ou=YourDepartment.ou=SVS.ou=YourDepartment. As the value. cn=UserKVM.ou=Departments. – For LDAP v1: cn=UserKVM. i. dc=myorganization.dc=mycompany – For LDAP v2: cn=UserKVM.

Ê Log in with root permission. 154 iRMC S2 . see: http://www... Ê Enter the following command: rcldap restart Message logging The LDAP daemon uses the Syslog protocol for message logging. For an explanation of the various levels. globally via OpenLDAP 4.7.zytrax.4.conf. I The logged messages are only displayed if a log level other than 0 is set in the file /etc/openldap/slapd..com/books/ldap/ch6/#loglevel table 2 on page 155 provides an overview of the log levels and their meanings.5 User management on the iRMC S2 Tips on OpenLDAP administration Restarting the LDAP service Proceed as follows to restart the LDAP service: Ê Open the command box.

log levels iRMC S2 155 .. globally via OpenLDAP Log level -1 0 1 2 4 8 16 32 64 128 256 512 1024 2048 Meaning Comprehensive debugging No debugging Log function calls Test packet handling Heavy trace debugging Connection management Show sent/received packets Search filter processing Configuration file processing Processing of access control lists Status logging for connections/operations/events Status logging for sent entries Output communication with shell backends.User management on the iRMC S2 . Output results of entry parsing. Table 2: OpenLDAP ..

156 iRMC S2 . – When configuring the LDAP settings on the Directory Service Configuration page (see page 333).Global email alerting User management on the iRMC S2 4. This means that it can be configured and handled centrally for all platforms using a directory server. as an LDAP v2 structure is required. Appropriately configured global user IDs can receive email alerts from all iRMC S2s that are connected to a directory server in the network. email alerting must have been enabled under Directory Service Email Alert Configuration. I Prerequisites The following requirements must be met for email alerting: – Global email alerting requires Version 3. – A principal user must have been configured in the iRMC S2 web interface who has been granted permission to search in the LDAP tree (see section “Directory Service Configuration (LDAP) Configuring the directory service at the iRMC S2” on page 333).4.8 Configuring email alerting to global iRMC S2 users Email alerting to global iRMC S2 users is integrated in the global iRMC S2 user management system.77A or later of the iRMC S2 firmware.

g.4. Displaying alert types The following alert types are supported: Alert type FanSens Temperat HWError Security SysHang POSTErr SysStat DDCtrl NetInterf RemMgmt SysPwr Memory Others Table 3: Alert types Cause Fan sensors Temperature sensors Critical hardware error Security System hung POST error System status Disk drives and controllers Network interface Remote Management Power management Memory Miscellaneous iRMC S2 157 . These are defined in addition to the authorization roles in the configuration file of the SVS_LdapDeployer (see page 96). each with an assigned severity (e.g. “critical”).jar on PRIMERGY ServerView Suite DVD 1.xml and Generic_InitialDeploy.xml that are supplied together with the jar archive SVS_LdapDeployer. The syntax of the alert roles is illustrated in the sample configuration files Generic_Settings. Assigning a user to a particular alert group specifies what alert types and severities the user will be alerted of by email.1 Global email alerting Global email alerting Alert roles are required for global email alerting via the directory server. Displaying alerting groups (alert roles) An alert role groups together a selection of alert types (e. temperature threshold exceeded).User management on the iRMC S2 4.8.

The LDAP email table is initially created by the iRMC S2 firmware the first time the iRMC S2 is started and then updated at regular intervals. For global email alerting. 158 iRMC S2 . for instance if the first mail server is not available. Preferred mail server. the iRMC S2 sends emails to the following users when an alert is issued: – all appropriately configured local iRMC S2 users.Global email alerting User management on the iRMC S2 Each alert type can be assigned one of the following severity levels: Warning. the email is sent to the second mail server. I It is recommended that you use email distribution lists for global email alerting. Critical. All. The size of the LDAP email table is limited to a maximum of 64 LDAP alert roles and a maximum of 64 global iRMC S2 users for whom email alerting is configured. – all global iRMC S2 users registered in the LDAP email table for this alert. the setting Automatic is used on the preferred mail server: If the email cannot be successfully sent immediately. Supported mail formats The following email formats are supported: – – – – Standard Fixed Subject ITS-Format Fujitsu REMCS Format corresponding mail format group. I If a mail format other than Standard is used. you must add the users to the LDAP email table If email alerting is configured (see page 160) and the option LDAP Email Alert Enable (see page 333) is selected. (none).

and the LDAP Alert Table Refresh option).User management on the iRMC S2 Global email alerting The LDAP directory server gets the following information from the email table for the purposes of email alerting: ● ● List of the global iRMC S2 users for whom email alerting is configured. – Required mail format. You specify the update interval as part of the LDAP configuration in the iRMC S2 web interface (under the option LDAP Alert Table Refresh (see section “Directory Service Configuration (LDAP) Configuring the directory service at the iRMC S2” on page 333. – when the LDAP configuration is changed. The LDAP email table is updated in the following circumstances: – when the iRMC S2 is started for the first time or restarted. – at regular intervals (optional). iRMC S2 159 . For each global iRMC S2 user: – List of the configured alerts for each alert type (type and severity).

eDirectory or OpenLDAP).Global email alerting User management on the iRMC S2 Configuring global email alerting on the directory server This section describes how to configure email alerting on the directory server. Ê Create a configuration file in which the alert roles are defined.Configuring the directory service at the iRMC S2” on page 333). Ê Start the SVS_LdapDeployer using this configuration file in order to generate a corresponding LDAP v2 structure (SVS) on the directory server (see page 97 and page 106). I The method used to configure the email addresses differs depending on the directory service used (Active Directory. You configure these in the iRMC S2 web interface (see section “Directory Service Configuration (LDAP) . I Settings must also be made for the iRMC S2. Proceed as follows: Ê In the directory service. 160 iRMC S2 . enter the email addresses of the users to whom emails are to be sent.

for instance. – Under DeptX.User management on the iRMC S2 4. (1) (2) Figure 50: OU SVS with alert roles I To ensure that emails are sent to the users in the individual alert roles.8. the newly created OU SVS is displayed in Active Directory. the relevant department must be configured in iRMC S2 (in figure 50: DeptX) (see page 337).4. iRMC S2 161 . together with the components Alert Roles and Alert Types under Declarations and together with the component Alert Roles under DeptX (see figure 50): – Under Declarations. Alert Roles displays all the defined alert roles and all the alert types are displayed under Alert Types (1).2 Displaying alert roles Global email alerting After the LDAP v2 structure has been generated. Alert Roles displays all the alert roles that are valid in the OU DeptX (2).

and open the Properties dialog box for this alert role by choosing Properties – Members from the context menu. all the users that belong to the alert role (here: StdSysAlerts) are displayed in the Members tab (2).g. (2) (1) Figure 51: Users assigned to the alert role “StdSysAlert” 162 iRMC S2 .Global email alerting User management on the iRMC S2 If you select an alert role (e. StdSysAlerts) under SVS – Departments – DeptX – Alert Roles in the structure tree for Active Directory Users and Computers (see figure 51) (1).

User management on the iRMC S2 4. in the Properties dialog box of the Active Directory Users and -Computers snap-in (see figure 51 on page 162).. you make an assignment by clicking Add. Novell eDirectory and OpenLDAP). iRMC S2 users are assigned to iRMC S2 alert roles in the same way in which iRMC S2 users are assigned to iRMC S2 authorization roles and using the same tools. for instance.3 Assigning iRMC S2 users to an alert role Global email alerting You can assign iRMC S2 users to alert roles either – on the basis of the user entry. In the various different directory services (Microsoft Active Directory.8.. In Active Directory. or – on the basis of the role entry. iRMC S2 163 .4.

4. 164 iRMC S2 .9 SSL copyright The iRMC S2-LDAP integration uses the SSL implementation developed by Eric Young on the basis of the OpenSSL Project.SSL copyright User management on the iRMC S2 4.

User management on the iRMC S2 SSL copyright iRMC S2 165 .

.

I A valid license key is required to use the Advanced Video Redirection Advanced Video Redirection (AVR) allows you to control the mouse and keyboard of the managed server from your remote workstation and to show the current graphical and text output from the managed server. I The AVR Java applet allows you to use the Remote Storage function (see chapter “Remote Storage” on page 191).5 Advanced Video Redirection (AVR) function. This chapter provides information on the following topics: – Checking the AVR settings – Using AVR – Menus of the AVR window iRMC S2 167 .

70. 85 60. 70. 85 32 1280 x 1024 (UXGA) 60. 75 Maximum color depth [bits] 32 32 32 16 24 16 640 x 480 (VGA) 800 x 600 (SVGA) 1024 x 768 (XGA) 1152 x 864 56. 75. 75. 65 Table 4: Supported display settings I If a high-resolution graphics mode is set on the server (shown on a gray background in the table).1 Requirements: Check the AVR settings Check the following important settings before using AVR: Graphics mode settings on the managed server AVR supports the following graphics modes: Resolution Refresh rates [in Hz] 60. 168 iRMC S2 . 75. 60. I Only VESA-compliant graphics modes are supported. 85 60. 72. 85 1280 x 1024 (UXGA) 60 1600 x 1200 (UXGA) 60. 75. 70. this is shown on the iRMC web interface.Prerequisites Advanced Video Redirection 5.

– on the managed server. iRMC S2 169 . – on the iRMC S2. Keyboard settings I The keyboard settings must be identical: – on the remote workstation.Advanced Video Redirection Supported text mode The iRMC S2 supports the following common text modes: – – – – 40 x 25 80 x 25 80 x 43 80 x 50 Prerequisites Refer to the Help system for your operating system for information on the display settings.

– The Local Monitor <status> indicator shows whether the local monitor of the managed server is switched on (see section ““Local Monitor Off” function” on page 172). Remote Storage is used to call the remote storage function (see page 187). – Integrated special keys (see page 173).2 Using AVR Ê To start AVR. The AVR window also contains the following elements: – Menu bar: The Preferences and Extras menus allow you to configure the AVR settings and to control the AVR (see page 183). click the Start Video Redirection or Start Video Redirection (Java Web Start) button on the Advanced Video Redirection (AVR) page of the iRMC S2 web interface (see page 356).Using AVR Advanced Video Redirection 5. The Advanced Video Redirection window (AVR window) opens. Menu bar Integrated special keys Local Monitor <status> Figure 52: Advanced Video Redirection (AVR) window 170 iRMC S2 . showing you the display on the managed server. Languages (see page 187) menu allows you to set the language (German/English) in which the menus and dialog boxes of the AVR window are to be shown.

Advanced Video Redirection Using AVR 5. You will always be asked if you want to switch to full-control mode. the existing session is switched to view-only mode. you are initially in view only mode. If you decide to switch to fullcontrol mode and another full-control mode session is already active.2. iRMC S2 171 . When AVR is first started.1 Parallel AVR sessions AVR can be used by two user sessions simultaneously. One user has full control over the server (full-control mode) and the other can only passively observe keyboard and mouse operation of the server (view only mode).

Local Monitor always off The local monitor is always switched off and cannot be switched on because a high-resolution graphics mode has been set on the managed server (see table 4 on page 168).2 “Local Monitor Off” function The Local Monitor Off function of the iRMC S2 allows you to power down the local monitor of the managed server for the duration of your AVR session. In this way. You configure the “Local Monitor Off” function on the Advanced Video Redirection page of the iRMC S2 web interface (see page 356). as the Enable Local Monitor Off option (see page 361) is deactivated. you can switch the local monitor of the server on and off from the remote workstation as follows: – In Full Control mode in an AVR session using the Extras menu – directly on the Advanced Video Redirection page with administrator or OEM permissions You can also configure that the local monitor is always switched off automatically whenever a new AVR session is started. Local Monitor On The local monitor is on. After you have configured the system appropriately. but can be switched on. you ensure that the inputs you make and the actions you perform on the local monitor on the server using AVR cannot be seen. but can be switched off.2. 172 iRMC S2 .Using AVR Advanced Video Redirection 5. Local Monitor Off The local monitor is off. The current status of the local monitor is shown in the AVR window in blue letters to the top right of the integrated special keys: Local Monitor always on The local monitor is always switched on and cannot be switched off. The identification LED flashes to indicate "Local Monitor Off" mode on the server.

Figure 53: AVR window . Ê If keyboard redirection appears not to be working. use Windows keys or special key combinations which are not sent by AVR if you press them on your own keyboard. for instance. because they are interrupted by the client’s operating system. you should use the integrated special keys or the virtual keyboard. [Ctrl] Left CTRL key (corresponds to the [Ctrl] key on your keyboard). iRMC S2 173 . [Alt] Alt(ernate) key (corresponds to the [Alt] key on your keyboard). Some special key combinations suchas [ALT] + [F4] cannot be sent. i.integrated special keys [Mouse Sync] Press this key to synchronize the mouse pointers (see also section “Synchronizing the mouse pointer” on page 175). Using the integrated special keys.e. These keys are implemented as “sticky keys”.3 Redirecting the keyboard Keyboard redirection only works when the focus is on the AVR window. Special key combinations AVR passes all normal key combinations to the server. check that the AVR window is not in viewonly mode. you will find a bar containing the special keys.Advanced Video Redirection Using AVR 5. they remain pressed when you click them and only return to their normal position when you click them again. Special keys such as Windows keys are not sent. Integrated special keys Below the menu bar of the AVR window. How to switch to full-control mode is described on page 185. you can. Ê If the keyboard does not respond.2. In such cases. simply click on the AVR window.

Virtual keyboard The virtual keyboard (see figure 54) provides you with a functional representation of the keyboard. [Context] Context menu for the selected object (corresponds to the key combination [Shift] + [F10] on your keyboard). This means that you can use the virtual keyboard as a fully functional replacement for a real keyboard. [Ctrl-Alt-Del] Corresponds to the key combination [Ctrl]+ [Alt] + [Del] on your keyboard.Using AVR [Win] Advanced Video Redirection Left and right Windows keys (correspond to the keys on your keyboard between the left and right [Ctrl] and [Alt ] keys). All key combinations are available when you use the virtual keyboard. You activate the virtual keyboard in the AVR window from the Extras menu (see page 184). [Lock] Caps lock (corresponds to the [Caps Lock] key on your keyboard). [Alt Gr] Alt(ernate) Gr(aphic) key (corresponds to the [Alt Gr] key on your keyboard). 174 iRMC S2 . Figure 54: Virtual Keyboard (keyboard layout: German (DE)) Secure Keyboard If you are connected to the iRMC S2 web interface over an HTTPS connection. entries at the keyboard are transferred over a secure SSL connection.

4 Redirecting the mouse The mouse pointer on the managed server is moved synchronously with the mouse on the remote workstation.2. Ê Move the local mouse pointer to the top left corner of the AVR window. 5.Advanced Video Redirection Using AVR 5. The mouse pointer on the managed server automatically follows this movement.2. The pointers are synchronized when the two mouse pointers completely overlap.4. You configure the mouse redirection settings in the AVR window in the Mouse tab of the Preferences menu (see page 188).1 Synchronizing the mouse pointer When the AVR window is first opened. To synchronize the two mouse pointers. iRMC S2 175 . use one of the following alternatives (see figure 55 on page 176): Ê Click [Mouse Sync] in the menu bar of the AVR window. it is possible that the mouse pointer on the remote workstation (local mouse pointer) is not yet synchronized with the mouse pointer on the managed server.

for instance because the preconfigured settings have been changed.Using AVR Advanced Video Redirection (3) (1) (2) Press the Mouse Sync key or (1) Drag the local mouse cursor to the top left corner. (2) The server’s mouse pointer follows automatically. Figure 55: Synchronizing the local mouse pointer and the mouse pointer of the managed server I Correct synchronization of the mouse pointers requires that certain settings are made on the managed server. 176 iRMC S2 . you can restore correct synchronization of the mouse pointers by making the settings described below. (3) The mouse pointers are synchronized when they completely overlap and e displayed as a single mouse pointer. If synchronization of the mouse pointers does not function correctly. If the managed server has been installed using the ServerView Installation Manager these settings has been preconfigured automatically by the Matrox VGA installation. The settings must be made on the managed server.

you will find the install_kronos2_vga. You can make all the settings for the managed server either directly at the managed server or from the remote workstation over AVR.bat for the relevant Matrox VGA driver installation (32-bit or 64-bit) is located. you can either make the settings for mouse pointer synchronization using a batch program or using the Windows Start menu and the context menu.00\DRV\VIDEO\MATROX\iRMC\W2K and on your PRIMERGY ServerView Suite DVD 1. I By default.2.Advanced Video Redirection 5. Ê Reboot the managed server when the batch program has executed.bat to start the batch program. Ê Switch to the folder in which the batch program install_kronos2_vga. the Matrox graphics driver is installed as well as the mouse pointer speed and hardware acceleration being adjusted.4.2 Using AVR Managed Windows server: Adjusting the settings for synchronization of the mouse pointers On a Windows server. You must adjust the following settings: – Speed of the mouse pointer – Hardware acceleration I When you adjust the settings using a batch program. Adjusting the settings on the managed server using a batch program Proceed as follows: Ê Open a DOS prompt window.bat programs under: C:\Program Files\Fujitsu\ServerView Suite\Installation Manager\ Content\V10.09. iRMC S2 177 .12. Ê Type setup.

Using AVR Advanced Video Redirection Adjusting the settings on the managed server using the Windows Start menu and the context menu Proceed as follows to adjust the mouse pointer: Ê Choose Start . Ê Click the [OK] button to save the settings. Ê Disable the Enhance Pointer Precision option.Settings .Printers and Other Hardware .Mouse and choose the Pointer Options tab.Pointer Options Ê Set the Pointer Speed to a medium value.Control Panel . 178 iRMC S2 . This opens the following window: Figure 56: Mouse Properties .

.. and the Troubleshooting tab. Advanced button. Ê Click the [OK] button to save the settings.Settings tab.Advanced Video Redirection Proceed as follows to adjust the hardware acceleration: Ê Right-click on the desktop background.. This opens the following window: Figure 57: Properties .Troubleshooting: Hardware acceleration Ê Set the Hardware Acceleration to a value as shown in figure 57. choose: Using AVR Properties . . Ê In the context menu that appears. iRMC S2 179 .

x Suse 10. Ê Run the command xset with the following arguments: xset m 1 1 180 iRMC S2 .4.x Suse 9.3 Advanced Video Redirection Managed Linux server: Adjusting the settings for synchronization of the mouse pointers Prerequisite: The managed server is running under one of the following Linux operating systems: – – – – – Red Hat 4.x Different graphical user interfaces (GUIs) are available for Suse Linux and Redhat Linux.x Red Hat 5.Using AVR 5.2. Command syntax: xset m(ouse)][acceleration][threshold] Proceed as follows: Ê Call a command line tool. Adjusting temporary settings on the managed server using commands Use the xset command to make the settings for Pointer acceleration and Pointer threshold (recommended values: 1 in each case) for the duration of the current session.x Suse 11. The most important GUIs are: – Gnome – KDE You can adjust the mouse pointer synchronization settings on the managed server either using commands or under menu guidance. You must adjust the following settings: – Mouse motion acceleration = 1 – Mouse motion threshold =1 You can make all the settings for the managed server either directly at the managed server or from the remote workstation over AVR.

You make permanent settings as follows for KDE: I The procedure for KDE described below only applies to Suse Linux.Peripheral . Adjusting the permanent settings on the managed server under menu guidance I It is not necessary to set the values again after rebooting the server.kde/share/config/kcminputrc as follows: [Mouse] Acceleration=1 Threshold=1 I It is not necessary to set the values again after rebooting the server.Advanced Video Redirection Adjusting permanent settings on the managed server using a configuration file (KDE) You make permanent settings as follows for KDE : Using AVR Ê Change the settings in the text file /root/.Control Center . Ê Choose N .Advanced tab The Mouse .Control Center window opens: Figure 58: Mouse Control Center window iRMC S2 181 .Mouse .

You make permanent settings as follows for Gnome: Ê Call the gconf-editor editor under the shell.0x (minimum value) – Pointer threshold: 20 pixels (maximum value) Ê Save the settings. I It is not necessary to set the values again after rebooting the server.gnome . Ê Choose: desktop .peripherals .Using AVR Advanced Video Redirection Ê Set the following values in the Mouse Control Center window: – Pointer acceleration: 1. Ê Reboot the managed server.mouse Ê Modify the following attribute values: motion_acceleration 1 motion_threshold 1 182 iRMC S2 .

– You can set up and clear remote storage connections with the Remote Storage menu.Advanced Video Redirection Menus of the AVR window 5. – The Languages menu allows you to set the language (German/English) used to display the AVR menus and dialogs. You can also make a virtual keyboard available. iRMC S2 183 . – The Preferences menu allows you to configure the mouse.3 Menus of the AVR window The menu bar of the AVR window contains the following menus: – The Extras menu allows you to control the AVR session. keyboard and logging settings.

even if the local monitor is switched off: – you are in view-only mode.Menus of the AVR window Advanced Video Redirection 5. The Virtual Keyboard window opens (see figure 54 on page 174).Extras menu Virtual Keyboard . – A high-resolution graphics mode is set on the managed server (see table 4 on page 168).3. Local monitor <status> display: Local Monitor always off 184 iRMC S2 .. Turn local monitor on Switches on the local monitor of the managed server.1 Extras menu You can select the following functions in the Extras menu: Figure 59: AVR window .. Update local monitor state Refreches the display of the local monitor state. I This function is disabled in the following cases.

I Note that any existing full-control session will be switched to view-only mode. Take Full Control. Ê Click Cancel if you do not want to switch to full-control mode. Ê Click OK to confirm that you want to switch to full-control mode.Take Full Control. Local monitor <status> display: Local Monitor always on Refresh Screen Refreshes the AVR window..) The following dialog box opens: Figure 60: Extras menu .. I This function is disabled in the following cases. iRMC S2 185 .. Switch to full-control mode. (This function is disabled if you are already in full-control mode.. – When AVR was started. the Local Monitor Off option was not enabled under Local Monitor (see page 360).Advanced Video Redirection Menus of the AVR window Turn local monitor off Switches off the local monitor of the managed server. even if the local monitor is switched on: – you are in view-only mode.

Menus of the AVR window Disconnect Session. (This function is disabled if you are already in view-only mode.. Ê Click Cancel if you do not want to terminate the selected AVR session. To terminate your own session.) Exit Terminate your own AVR session.. Ê Click OK to confirm that you want to terminate the selected AVR session. Switch to view-only mode. choose Exit.. 186 iRMC S2 . Figure 61: Extras menu . Relinquish Full Control. Terminate another AVR session.Disconnect Session Ê Select the AVR session that you wish to terminate. Advanced Video Redirection I It is only possible to terminate other AVR sessions with A list of current AVR sessions appears: Disconnect Session..

Double-click Remote Storage.Languages menu iRMC S2 187 .. to open the Storage Devices window (see page 194).3.Remote Storage menu Remote Storage.. choose the language in which the menus and dialog boxes of the AVR window are to be shown: Figure 63: AVR window . 5..2 Remote Storage menu You call the remote storage functionality under Remote Storage: Figure 62: AVR window . This window allows you to attach or detach media on the remote workstation as Remote Storage devices (see chapter “Remote Storage” on page 191).3.3 Languages menu From the Languages menu..Advanced Video Redirection Menus of the AVR window 5.

Preferences menu Mouse tab The Mouse tab allows you to specify the mouse mode: Figure 65: Preferences menu . Hide Mode (Relative) or Relative Mode – Linux: Hide Mode (Relative) or Relative Mode I Default setting: Relative Mode Ê Confirm your entries by clicking OK.Menus of the AVR window Advanced Video Redirection 5.Mouse tab Depending on the server operating system. you must make the following settings: – Windows: Absolute Mode.4 Preferences menu The Preferences menu contains tabs for configuring the mouse.3. 188 iRMC S2 . keyboard and logging together with a Misc tab for further functions: Figure 64: AVR window .

Logging tab I None must be set! Ê Confirm your entries by clicking OK. iRMC S2 189 .Keyboard tab Languages Select the keyboard layout for the virtual console. I The keyboard layout at the managed server must also be set accordingly. Logging tab The Logging tab is used to configure the logging settings. Ê Confirm your entries by clicking OK. Figure 67: Preferences menu .Advanced Video Redirection Keyboard tab Menus of the AVR window The Keyboard tab allows you to specify the keyboard layout for the virtual console: Figure 66: Preferences menu .

you configure whether the iRMC S2 is to perform hardware compression for the AVR session. Ê Confirm your entries by clicking OK. the iRMC S2 performs hardware compression for the AVR session.Misc tab Hardware Compression If you enable this option. Figure 68: Preferences menu .Menus of the AVR window Misc tab Advanced Video Redirection On the Misc tab. 190 iRMC S2 .

It is not possible to establish concurrent Remote Storage connections via an applet and via the Remote Storage server. You can provide the source for the virtual drive as follows: – As a physical drive or image file at the remote workstation using the AVR Java applet (see page 192). Remote Storage makes a “virtual” drive available which is located elsewhere in the network. Up to two media can be redirected. I Parallel remote storage connections: The following are possible concurrently: – either up to two Remote Storage connections to virtual drives at the remote workstation (if the connection is established over the AVR Java applet) or – one Remote Storage connection to a Remote Storage server. – As a CD/DVD ISO image file centrally in the network via a Remote Storage server (see page 206).6 Remote Storage I A valid license key is required to use the Remote Storage function. iRMC S2 191 . I The Remote Storage page of the iRMC S2 web interface allows you to obtain information on the status of the current remote storage connections and establish the connection to a Remote Storage server (see page 366).

. This section provides information on the following topics: – Starting Remote Storage – Provision of storage media for Remote Storage – Connecting storage media as remote storage – Clearing Remote Storage connections – Removing media made available for Remote Storage 192 iRMC S2 . providing on the remote workstation Remote Storage 6.1 Providing remote storage at the remote workstation If you provide the source for a virtual drive on the remote workstation then the remote storage functionality supports the following device types: – Floppy – CD ISO image – DVD ISO image You can use the virtual drive to install an operating system on your PRIMERGY server from the remote workstation (see chapter “Remote installation of the operating system via iRMC S2” on page 463)...

Remote Storage. iRMC S2 193 . This opens the AVR window.. containing the storage media currently available for Remote Storage.Remote Storage .Remote Storage .. Ê In the menu bar in the AVR window.1 Starting Remote Storage You start the Remote Storage function using the AVR Java applet (see section “Advanced Video Redirection . button to start Advanced Video Redirection (see section “Advanced Video Redirection .1. Figure 69: AVR window . The Storage Devices dialog box opens...Start Advanced Video Redirection (AVR)” on page 356). providing on the remote workstation 6. Ê Start the iRMC S2 web interface (see section “Logging into the iRMC S2 web interface” on page 222)..Start Advanced Video Redirection (AVR)” on page 356).Remote Storage. choose: Remote Storage . Ê Open the Advanced Video Redirection page and click on the Start Video Redirection..

providing on the remote workstation “Storage Devices” dialog box on a Windows system Remote Storage Figure 70: Storage Devices dialog box I When a storage medium is inserted in an optical drive (CD ROM. but its contents are not displayed. 194 iRMC S2 . the storage medium is reserved by the local explorer... If a storage medium is inserted. DVD ROM) the contents are displayed automatically..

. iRMC S2 195 .Remote Storage . Mounted storage media are automatically displayed in the Storage Devices dialog box.. providing on the remote workstation “Storage Devices” dialog box on a Linux system Figure 71: Storage Devices dialog box I Physical storage media must be mounted to allow them to be connected as Remote Storage devices.

... providing on the remote workstation

Remote Storage

6.1.2

Provision of storage media for Remote Storage

Ê In the Storage Devices dialog box, click Add... . The Add Storage Device dialog box opens. “Add Storage Device” dialog box on a Windows system

Figure 72: Add Storage Device dialog box (Windows)

“Add Storage Device” dialog box on a Linux system

Figure 73: Add Storage Device dialog box (Linux)

196

iRMC S2

Remote Storage

... providing on the remote workstation

Ê In the Add Storage Device dialog box, navigate to the directory of the remote storage medium that you want to make available for remote storage from your remote workstation. Ê Select the required device type under Storage Type. The following storage types can be selected: – Floppy – CD ISO image – DVD ISO image

I Physical storage devices must be mounted on Linux systems.
Ê Specify the storage medium you wish to connect as Remote Storage under File Name: – 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) “Add Storage Device” dialog: Selecting the storage medium (Windows)

Figure 74: Add Storage Device dialog: Selecting the storage medium

iRMC S2

197

... providing on the remote workstation

Remote Storage

“Add Storage Device” dialog: Selecting the storage medium (Linux)

Figure 75: Add Storage Device dialog: Selecting the storage medium

Ê Click Select to confirm your selection. The selected storage medium is made available for Remote Storage and displayed in the Storage Devices dialog. Display in the “Storage Devices” dialog (Windows)

Figure 76: Storage Devices dialog: The provided storage medium is displayed.

198

iRMC S2

Remote Storage

... providing on the remote workstation

Display in the “Storage Devices” dialog (Linux)

Figure 77: Storage Devices dialog: The provided storage medium is displayed.

iRMC S2

199

... providing on the remote workstation

Remote Storage

6.1.3

Connecting storage media as remote storage

Ê In the Storage Devices dialog (see figure 76 and figure 77 on page 199), click the storage medium that you want to connect as Remote Storage. Ê Click Connect to connect the selected storage medium as Remote Storage. The Storage Devices dialog opens with the message regarding safe removal. The storage medium is connected as Remote Storage.

I If you wish to connect two storage devices as Remote Storage at the
same time, a confirmation dialog box is displayed before the connection is established (see section “Connecting two storage devices as Remote Storage at the same time” on page 202). Storage Devices dialog: Showing Remote Storage connection (Windows)

Figure 78: Storage Devices dialog: The storage medium is connected as Remote Storage.

200

iRMC S2

Remote Storage

... providing on the remote workstation

Storage Devices dialog: Showing Remote Storage connection (Linux)

Figure 79: Storage Devices dialog: The storage medium is connected as Remote Storage.

iRMC S2

201

... providing on the remote workstation

Remote Storage

Connecting two storage devices as Remote Storage at the same time

I The example in the following section illustrates how to simultaneously
In figure 80, you can see that two storage devices have been provided as Remote Storage:

connect two storage media as Remote Storage on a Windows system. The same procedure applies for Linux systems.

Figure 80: Storage Devices dialog: Connecting 2 storage devices as Remote Storage

Ê Select the two storage devices and click Connect to connect the storage devices as Remote Storage. The system then makes a proposal regarding the assignment of your storage devices to USB 1.1 and USB 2.0 (see figure 80 on page 202).

202

iRMC S2

Remote Storage

... providing on the remote workstation

Figure 81: Connection Type dialog: Assignment to USB 1.1 and USB 2.0

Ê Click Swap if you want to swap the assignment of the storage devices to USB 1.1 and USB 2.0.

Figure 82: Connection Type dialog: Assignment to USB 1.1 and USB 2.0 swapped

Ê Click OK to connect the storage devices as Remote Storage.

iRMC S2

203

... providing on the remote workstation

Remote Storage

6.1.4

Clearing Remote Storage connections

Ê Open the Storage Devices dialog (see section “Starting Remote Storage” on page 193). The list of storage media connected as Remote Storage is displayed (using Windows in the example).

Figure 83: Storage Devices dialog: Clearing Remote Storage connections

Ê “Safely remove” the storage device, i.e. ensure that no more applications/programs are accessing the storage media. Ê Click Disconnect to clear all Remote Storage connections.

204

iRMC S2

Remote Storage

... providing on the remote workstation

6.1.5

Removing the storage medium

Remove a storage medium from the list of media available for Remote Storage as follows: Ê Open the Storage Devices dialog (see section “Starting Remote Storage” on page 193). The list of storage media available for Remote Storage is displayed (using Windows in the example):

Figure 84: Storage Devices dialog: Removing a Remote Storage medium

Ê Select the storage medium you want to remove. Ê Click Remove... to remove the storage medium.

iRMC S2

205

x-based ISO images A PRIMERGY server running iRMC S2 and a firmware version Ï 3. Booting from WinPE 2..60A is required to boot from a WinPE 2.g. providing via a Remote Storage server Remote Storage 6. – The Remote Storage server must be started (see page 217 and page 220). – The managed server’s iRMC S2 must be connected to the Remote Storage server (see page 366).. The Remote Storage server is available for Windows and Linux systems The Remote Storage server is available in a 32-bit and 64-bit variant for both Windows and Linux. 206 iRMC S2 . You can use this image file to boot one or more PRIMERGY servers from the remote workstation (see chapter “Remote installation of the operating system via iRMC S2” on page 463).x-based ISO image (e.2 Providing remote storage via a Remote Storage server You can use a Remote Storage server to provide an image file (ISO/NRG image) as remote storage for any number of PRIMERGY servers that can be administered via iRMC S2.. Windows Server 2008 and ServerView Installation Manager). I You will find the individual variants of the Remote Storage server on your PRIMERGY ServerView Suite DVD 1 under SVSoftware\Software\RemoteView\iRMC Making the ISO image available to the PRIMERGY Server via Remote Storage The following requirements must be satisfied if your PRIMERGY server is to use the image file made available by the Remote Storage server: – The Remote Storage server must be installed (see page 207 and page 219).

exe for installing the Remote Storage server are located on the PRIMERGY ServerView Suite DVD 1 under SVSoftware\Software\RemoteView\iRMC\Widows_32 and SVSoftware\Software\RemoteView\iRMC\Widows_x64 respectively. Proceed in the same way to install the 64-bit variant.1 Remote Storage server under Windows The Remote Storage server is available in 32-bit and 64-bit versions..Remote Storage .exe to install the Remote Storage server.1 Installing the Remote Storage server The installation programs RemoteStorageServer_Installer32.2. The following description refers to installation of the 32-bit variant.. 6. The 32-bit and 64-bit versions of the Remote Storage server must not be installed at the same time on 64-bit systems.2.exe and RemoteStorageServer_Installer64. Ê Start RemoteStorageServer_Installer32. providing via a Remote Storage server 6.1. The welcome screen of the installation program appears: iRMC S2 207 .

. providing via a Remote Storage server Remote Storage Figure 85: Installing the Remote Storage server: Welcome screen Ê Click the Next button. The window in which you specify the installation directory appears (see figure 86 on page 209).. 208 iRMC S2 ..

.. providing via a Remote Storage server Figure 86: Installing the Remote Storage server: Specifying the installation folder Ê If you do not want to install the Remote Storage server in the default folder.. Ê Click the Next button.Remote Storage . iRMC S2 209 . click Browse.. The window allowing you to select where the program shortcut appears in the Start menu appears (see figure 87 on page 210). to navigate to the directory you wish to use.

... specify the folder you wish to use by clicking Browse... providing via a Remote Storage server Remote Storage Figure 87: Installing the Remote Storage server: Specifying the installation folder Ê If you do not want to place the program shortcut in the default folder. Here you can check the settings you have made and launch installation of the Remote Storage server (see figure 88 on page 211).. The Ready to Install window opens. 210 iRMC S2 . Ê Click the Next button.

.. The window shown in figure 89 on page 212 is displayed once installation is complete: iRMC S2 211 .Remote Storage . providing via a Remote Storage server Figure 88: Installing the Remote Storage server: Starting installation Ê Click Install to start installation of the Remote Storage server.

the Remote Ê Click Finish to close the installation program. 212 iRMC S2 ....exe. providing via a Remote Storage server Remote Storage Figure 89: Installing the Remote Storage server: Closing the installation program I If you check the Launch Remote Storage Server option. your installation directory contains a number of files including RemoteStorageServer. Once installation has been completed successfully. Storage server's GUI (see page 214) is started when the installation program has been closed.

Executing the Remote Storage server as a service The following points should be noted – The image file can be located either on a computer in the network or on the same host on which the Remote Storage server is running. Executing the Remote Storage server as a stand-alone program The following points should be noted – The image file (ISO/NRG image) may be present locally on the Remote Storage server or on an assigned network drive. you must start the image file “manually”. – When the host on which the Remote Storage server is located is booted.Remote Storage 6. you must specify the path of the image file in UNC notation. providing via a Remote Storage server Remote Storage server execution modes You can execute the Remote Storage server in the following modes as required: – as a background service – as a stand-along program You configure the Remote Storage server execution mode via a graphical user interface (see page 214).1. I If the image file is not on the computer on which the Remote Storage server is running. The Remote Storage server is then executed until it is explicitly terminated or the host is shut down... iRMC S2 213 . – When the host on which the Remote Storage server is located is booted.2 . the image file becomes available automatically.2. the remote storage server starts automatically. – When the host on which the Remote Storage server is located is booted. You also need a user account with access permissions on the image file.

1. Calling the Remote Storage server’s graphical user interface You call the Remote Storage server’s graphical user interface as follows: Ê Choose Start .3 Remote Storage Configuring.Remote Storage Server.Fujitsu RemoteStorageServer . The Remote Storage server’s graphical user interface appears: Figure 90: The Remote Storage server’s graphical user interface (here in the “Idle” state) 214 iRMC S2 .2. start and exit the Remote Storage server via a graphical user interface (GUI).Programs .. starting and exiting the Remote Storage server You configure.. providing via a Remote Storage server 6..

e. you must specify the path of the image file in UNC notation... button and then navigate to and select the required image file in the Choose a file dialog which now opens and then confirm. Force Using Port If you have configured a port number other than the default port number (5901) for the iRMC S2’s remote storage port (see page 308 or page 421). then you must activate this option and enter the configured port number in the associated field. the Remote Storage server uses the first detected LAN connection. it is not being executed. you specify the image file made available as remote storage together with other parameters: ISO Image Path and Filename: Ê Enter the path and name of the image file directly in the field. Force Using IP Address If the host on which the Remote Storage server is executed possesses more than one LAN connection: You can specify the IP address of the LAN connection that is to be used for the Remote Storage server if this is executed as a service. You must also ensure that the account entered under Log On As User (see page 216) is valid and has access permissions on the share on which the image file is located. providing via a Remote Storage server Configuring the Remote Storage server I Configuration is only possible if the Remote Storage server is in the “idle” state. or: Ê Click the Browse. In the graphical user interface.. i. By default. I If the Remote Storage server is to run as a service (see the Run as Service option on page 216) and the image file is located on a computer in the network. iRMC S2 215 .Remote Storage ..

the image file (ISO/NRG image) must be located on a local drive. In this event. You must also specify the image file in UNC notation (see input field ISO Image Path or Filename on page 215). Specify the user name in the form: – For local users: . In this event.. providing via a Remote Storage server Remote Storage Run as Service Activate this option if the Remote Storage server is to be executed as a service in the background (see page 213). the specified account must have access permissions on the network drive on which the image file is located. 216 iRMC S2 .\Logon-Name – For domain users: DOMAIN\LogOnName or LogOnName@DOMAIN<mailto:LogOnName@DOMAIN> I The image file (ISO/NRG image) can be located on a network drive if the Log On As User option is enabled. Ê Click the Apply button to activate your settings.. Log On As User he Remote Storage server is executed under the user account that you specify in the following input fields.. Ê Select one of the two options below: Use Local System Account The Remote Storage server is executed as a service under the local system account.

I Execution of the Remote Storage server is not interrupted automatically iRMC S2 217 . providing via a Remote Storage server Starting the Remote Storage server Ê Click the Start button to start the Remote Storage server as a service or as a stand-alone program: Figure 91: The Remote Storage server is executed (“Running” status) Status Messages: The logged execution states of the Remote Storage server are displayed here.Remote Storage . the Remote Storage server is started automatically when the computer on which the Remote Storage server is installed is booted. then if the graphical user interface is exited... I If the Run as service execution mode is configured (see page 216).

. 218 iRMC S2 .. providing via a Remote Storage server Exiting the Remote Storage server Remote Storage Ê Click the Stop button to terminate execution of the Remote Storage server..

– An iRMC S2 running a version Ï 3.2 Remote Storage server (iRMCSrv) under Linux The iRMCSrv Remote Storage server allows you to make an ISO/NRG image available as remote storage to a PRIMERGY server running iRMC S2.Remote Storage . iRMC S2 219 . SLES 10. Properties The iRMCSrv Remote Storage server is available in 32-bit and 64-bit variants and supports the following Linux platforms: – Red Hat Linux 4.2. SLES 11 You can execute the iRMCSrv Remote Storage server in the following modes as required: – as a background daemon – as a stand-along program Prerequisites The following prerequisites must be met if the iRMCSrv Remote Storage server is used: – An iRMC S2 running a version Ï 3. 3. This can be – on the computer on which the Remote Storage server is running or – on a mounted network drive.g.60 of the firmware is required to boot from a WinPE 2. Log into the iRMC S2 of the managed server using the web interface and with Remote Storage permissions. providing via a Remote Storage server 6. e. Windows Server 2008... Making an ISO image available via remote storage Proceed as follows: 1. Make sure that the Remote Storage server is running. Red Hat Linux 5 – SUSE Linux SLES 9.60 of the firmware requires an iRMCSrv Remote Storage server Ï V2.1)/Installation Manager. 2. ServerStart (Version Ï 7. Use the Remote Storage page to establish a connection to the Remote Storage server.0.x-basied ISO image.

220 iRMC S2 . -daemon Starts iRMCSrv as a background daemon. providing via a Remote Storage server Starting the Remote Storage server (iRMCSrv) You start the Remote Storage server as follows: Remote Storage iRMCSrv [-version] [-daemon] [-port <portnumber>] [<iso-path>] -version Shows the iRMCSrv version. You also need a user account with access permissions on the image file. Default: 5901 <iso-path> Pathname of the ISO image on the Remote Storage server... -port <portnumber> Specifies the port number to be used for the Remote Storage connection.. you must specify the path of the image file in UNC notation. I If the image file is not on the computer on which the Remote Storage server is running.

When you enter values in the iRMC S2 web interface. iRMC S2 221 . you often receive assistance in the form of tool tips.7 iRMC S2 web interface The iRMC S2 not only has its own operating system. I The software described below is based in part on the work of the Independent JPEG Group. You can choose whether to show the menus and dialog boxes of the iRMC S2 web interface in German or English. but also acts as a web server. providing its own interface.

– LDAP access to the directory service is not configured for the iRMC S2 (LDAP enabled option is not activated) and Always use SSL Login option (see page 334) is not activated: Figure 92: Login screen for the iRMC S2 web interface (LDAP access not configured and the “Always use SSL login” option is not selected) Ê Type in the data for the default administrator account. check the LAN connection (see section “Testing the LAN interface” on page 43). and then delete the default administrator account or at least change the password for the account (see “User “<name>” Configuration . 222 iRMC S2 .Logging into the iRMC S2 web interface iRMC S2 web interface 7.1 Logging into the iRMC S2 web interface Ê Open a web browser on the remote workstation and enter the (configured) DNS name (see page 311) or IP address of the iRMC S2. it is recommended that you create a new administrator account once you have logged in. Different login screens appear depending on whether LDAP access to a directory service has been configured for the iRMC S2 (LDAP enabled option. Ê Click OK to confirm your entries. For reasons of security.User configuration (details)” on page 326). see page 334): I If no login screen appears. User name: admin Password: admin I Both the User name and the Password are case-sensitive.

Ê Click Login to confirm your entries. all communication between the web browser and the iRMC S2 is carried out over HTTPS. iRMC S2 223 . it is recommended that you create a new administrator account once you have logged in. The iRMC S2 web interface opens showing the System Information page (see page 231).iRMC S2 web interface Logging into the iRMC S2 web interface – LDAP access to the directory service is configured for the iRMC S2 (LDAP enabled option is activated) or Always use SSL Login option is activated): Figure 93: Login screen for the iRMC S2 web interface (LDAP access configured) I The user name and password are always SSL-protected when they are transmitted. User name: admin Password: admin I For reasons of security. and then delete the default administrator account or at least change the password for the account (see “User “<name>” Configuration . Ê Type in the data for the default administrator account.User configuration (details)” on page 326). If you activate the Secure (SSL) option.

All other Settings is selected. Include User Settings is selected. Open and edit Certificate Upload page. Firmware Aktualisierung aus einer Datei iRMC S2 TFTP Einstellungen X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Table 5: Permissions to use special the iRMC S2 web interface 224 iRMC S2 Remote Storage Enabled Administrator Operator OEM User .Required user permissions iRMC S2 web interface 7. Open the System Component Information page. Reset Error Counter. Load license key onto the iRMC S2. page Open iRMC S2 Firmware Update page. Set firmware selector. Functions in the iRMC S2 web interface Permitted with IPMI privilege level Required permission Configure iRMC S2 Settings Video Redirection Enabled Configure User Accounts Open the System Overview page. Open and edit Generate a self signed RSA Cert. Switch identification LED on/off. Set Asset Tag Configuration. View SPD Data. Edit Save iRMC S2 FW Settings page.2 Required user permissions table 5 provides an overview of the permissions which are required in order to use the individual functions available at the iRMC S2 web interface. Open iRMC S2 Information page. Reboot iRMC S2.

Clear the system event log (SEL). page Open Power On/Off page. Open System Event Log Content page. *) Open Fans page. Open Voltages page.iRMC S2 web interface Required user permissions Functions in the iRMC S2 web interface Permitted with IPMI privilege level Required permission Configure iRMC S2 Settings Video Redirection Enabled Configure User Accounts Open and edit iRMC S2 TFTP Firmware Update. Open Power Supply Info page. Open and edit Power Consumption Configuration page Open Current Power Consumption page Open Power Consumption History page. Start fan test (Fan Test group). Select individual Fans (System Fans group). Open Temperature page Define action on critical temperature. Use Power Control. Set Fan Check Time (Fan Test group). Set Fan Fail Action / Delay Time. Open Power Supply page. Open and edit the Power Options page. Open Component Status page. Modify Boot Options. Save event log X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Table 5: Permissions to use special the iRMC S2 web interface iRMC S2 225 Remote Storage Enabled Administrator Operator OEM User .

Logon in window for power mgmt & text console red. Open and edit the Adv. Start iRMC S2 SSH Access. Open and edit Serial / Modem Alerting page. Video Redirection page. Open the BIOS Text Console page. page.Required user permissions iRMC S2 web interface Functions in the iRMC S2 web interface Permitted with IPMI privilege level Required permission Configure iRMC S2 Settings Video Redirection Enabled X Configure User Accounts Define the severity for the display of SEL entries Open System Event Log Configuration page. Open and edit the DHCP Configuration page. Modify the BIOS Console Redirection Options. SSH login X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Table 5: Permissions to use special the iRMC S2 web interface 226 iRMC S2 Remote Storage Enabled X Administrator Operator OEM User . Open and edit the Remote Storage page. Open and edit DNS Settings page. Services page. Open and edit Server Management Info. Open and edit the Directory Service Config. Open and edit the Email Alerting page. Edit System Event Log Configuration page. Open and edit the iRMC S2 User page. Open and edit SNMP TRAP Alerting page. Start Console Redirection. page. Open and edit the Ports and Netw. Start text console redirection (Enter Console). Open and edit the Network Interface page.

Telnet login *) This Feature is not supported for all PRIMERGY Servers.iRMC S2 web interface Required user permissions Functions in the iRMC S2 web interface Permitted with IPMI privilege level Required permission Configure iRMC S2 Settings Video Redirection Enabled Configure User Accounts Start iRMC S2 Telnet Access. X X X X X X X X Table 5: Permissions to use special the iRMC S2 web interface iRMC S2 227 Remote Storage Enabled Administrator Operator OEM User .

3 Structure of the user interface The iRMC S2 web interface is structured as follows: Selected function Interface language selector Title bar Navigation area Working area Figure 94: Structure of the iRMC S2 web interface 228 iRMC S2 .Structure of the user interface iRMC S2 web interface 7.

options. Click this icon to choose the language (German or English) used to display the navigation area.iRMC S2 web interface Structure of the user interface Choosing the language for the iRMC S2 web interface On the right of the black bar above the work area. the following login screen appears: Figure 95: Login page (after logging out) iRMC S2 229 . links and buttons. you will find the links Logout and Refresh: ● Logout allows you to terminate the iRMC S2 session after you have confirmed this in a dialog box. you will find a flag icon. Different login screens appear after the session has been closed depending on whether LDAP access to a directory service has been configured for the iRMC S2 (LDAP enabled option. dialog boxes. menus and dialog boxes of the iRMC S2 web interface. When you click one of these links (in figure 94:System Overview). the link is enabled and the work area for that function is displayed showing any output. Below the links to the individual iRMC S2 functions. Navigation area The navigation area contains the menu tree structure whose nodes combine the links to the individual iRMC S2 functions arranged on a task basis. see page 334): – If LDAP access to the directory service is not configured for the iRMC S2 (LDAP enabled is not activated) and then Always use SSL login option (see page 334) is deactivated.

Structure of the user interface iRMC S2 web interface Click the Login button to open the login screen of the iRMC S2 web interface (see figure 92 on page 222). the appropriate login screen appears (see figure 93 on page 223). I Alternatively. you can configure the interface to automatically update the contents periodically (see “Enable Auto Refresh” on page 306). – If LDAP access to the directory service is configured for the iRMC S2 (LDAP enabled option is activated) or the Always use SSL login option (see page 334) is deactivated. ● Click Refresh to refresh the contents of the iRMC S2 web interface. 230 iRMC S2 . This allows you to log in again if you wish.

General information on the server” on page 232 – “System Component Information .iRMC S2 web interface System Information 7.4 System Information Information on the server The System Information entry contains the links to the following pages: – “System Overview .Information on the server components” on page 237 iRMC S2 231 .

system FRUs (Field Replaceable Units) / IDPROM.System Information iRMC S2 web interface 7. the System Overview page allows you to enter a customer-specific asset tag for the managed server.1 System Overview General information on the server The System Overview page provides information on – – – – – the system status. Figure 96: System Overview page 232 iRMC S2 .4. system (general information) the operating system of the managed server. current overall power consumption of the managed server In addition.

iRMC S2 web interface System Status System Information The status of the global error LED. You can also switch the PRIMERGY identification LED on and off. flashes red. Prefailure event for a CSS component. Prefailure event for a non CSS component. Figure 97: System Overview page . Status of the server The server is operational. the CSS LED and the identification LED are shown under System Status. CSS LED Informs about the server’s CSS (Customer Self Service) LED: Status Info (iRMC S2) off on blinking CSS LED on the Server does not light up. Critical event. The following statuses are possible: – On: “Power ON” (green) with text “Suspend to RAM (Standby)” – On: “Standby mode (green) with text “Suspend to RAM (Standby)”. iRMC S2 233 . lights orange. Defective CSS component. Status of the servers No critical event. flashes orange. – Off: “Power OFF” (orange) Error LED Informs about the server‘s Global Error LED: Status Info (iRMC S2) off on blinking Global Error LED on the Server does not light up. lights red.System Status Power LED Power status of the server.

It can then be evaluated by in-house tools or used for integration in enterprise management systems (such as CA Unicenter). you can enter a customer-specific asset tag for the managed server. Asset Tag Configuration Under Asset Tag Configuration.System Information Identify LED Server identifier. I The customer-specific asset tag allows you to assign the server an inventory number or other identifier of your choice. Ê Click Apply to accept the asset tag. With Windows-based systems. this customer-specific asset tag is provided automatically by the WMI (Windows Management Instrumentation).System Status page System Asset Tag You can enter the asset tag here. The following statuses are possible: – On (blue) – Off (grey) iRMC S2 web interface Turn On/Turn Off Click the Turn On / Turn Off button to toggle the PRIMERGY identification LED on and off. 234 iRMC S2 . Figure 98: The System Overview .

System Information Operating System Information Operating System Information lists information on the operating system of the managed server.Operating System Information iRMC S2 235 . Figure 99: System Overview page . Figure 100: System Overview page .iRMC S2 web interface System Information System Information System Information lists information on the managed server.

minimum.Current Overall Power Consumption Under Current Overall Power Consumption you can see all the measurements current. Figure 101: System Overview page . maximum and average power consumption for the server in the current interval. A graphical display also shows the current power consumption of the server compared with the maximum possible power consumption. 236 iRMC S2 . Figure 102: System Overview page .System Information System FRU / IDPROM Information iRMC S2 web interface Information on the FRUs (Field Replaceable Units) is listed under System FRU/IDPROM Information. FRUs are system components that can be released and removed from the system. The CSS Component column indicates for each of the components whether the CSS (Customer Self Service) functionality is supported.System FRU / IDPROM Information Current Overall Power Consumption I This option is not supported for all PRIMERGY servers.

2 System Component Information Information on the server components The System Component Information page provides information on the CPU and the main memory modules.4. Component slot is empty. The CSS Component column indicates for each of the components whether the CSS (Customer Self Service) functionality is supported.iRMC S2 web interface System Information 7. Warning: The status of the component has deteriorated. Fault: The component has a fault. The following status icons indicate the possible statuses of the system components: OK: Component status is okay. Table 6: Status of the system component iRMC S2 237 .

this page indicates whether TPM is enabled or disabled. 238 iRMC S2 .System Information iRMC S2 web interface Figure 103: System Component Information page I On PRIMERGY servers with support for TPM (Trusted Platform Module). System CPU Information This group provides information on the status. IDs. CSS capability and performance of the CPU(s) in the managed PRIMERGY server. IDs. CSS capability and performance of the main memory modules in the managed PRIMERGY server. System Memory Information This group provides information on the status.

The SPD data for a memory component is stored in an EEPROM integrated in the component and serves to allow the BIOS to automatically detect this memory component (RAM. Deselect all Cancels your selection.iRMC S2 web interface Select System Information Here you can select individual memory modules to which the action you select under Please select memory action from list is to be applied. iRMC S2 239 . Apply to the selected modules Applies the selected action to the selected memory modules. DIMM). Please select memory action from list This list allows you to select an action to be applied to the selected memory modules. View SPD Data / No SPD Data Clicking the toggle button View SPD Data / No SPD Data shows or hides vendor-specific details (Serial Presence Detect (SPD) data) for the individual memory components. Select all Selects all memory modules.

Load the DSA/RSA certificate and private DSA/RSA key” on page 247.Save firmware settings” on page 245 – “Certificate Upload . – “Generate a self-signed Certificate .Generate self-signed RSA certificate” on page 254 – “iRMC S2 Firmware Update” on page 256 240 iRMC S2 .Information.5 iRMC S2 . firmware and certificates The iRMC S2 entry contains the links to the following pages: – “iRMC S2 Information .iRMC S2 iRMC S2 web interface 7.Information on the iRMC S2” on page 241 – “Save iRMC S2 Firmware Settings .

– View information on the active iRMC S2 sessions.iRMC S2 web interface iRMC S2 . set the firmware selector and load a firmware image and restart the iRMC S2. – Load license key onto the iRMC S2.iRMC S2 Information 7.1 iRMC S2 Information Information on the iRMC S2 The iRMC S2 Information page provides you with the following options: – View information on the firmware and the SDRR version of the iRMC S2.5. Figure 104: iRMC S2 Information page iRMC S2 241 .

Figure 105: iRMC S2 Information page . Active Session Information The Active Session Information group shows all the currently active iRMC S2 sessions. you can view information on the firmware and the SDRR version of the iRMC S2 and restart the iRMC S2.iRMC S2 . I The Reboot iRMC S2 button is disabled during the BIOS POST phase of the managed server.Firmware Information and iRMC S2 reboot Reboot iRMC S2 Reboots the iRMC S2.iRMC S2 Information Running Firmware iRMC S2 web interface Under Running Firmware. Figure 106: iRMC S2 Information page .Active Session Information 242 iRMC S2 .

Upload When you click this button.iRMC S2 Information The License Key group allows you to load a license key onto the iRMC S2. the license key specified in the input field is loaded onto the iRMC S2.License Key I You require a valid license key to be able to use the iRMC S2 functions Advanced Video Redirection (see page 356) and Remote Storage (see page 366). iRMC S2 243 .iRMC S2 web interface License Key iRMC S2 . Figure 107: iRMC S2 Information page . You can purchase the license key.

244 iRMC S2 .iRMC S2 Information Miscellaneous iRMC S2 Options iRMC S2 web interface The Miscellaneous iRMC S2 Options group allows you to make settings for the layout of the iRMC S2 web interface. Temperature Units Specifies the unit used for displaying temperature values at the iRMC S2 web interface (degrees Celsius / degrees Fahrenheit).Miscellaneous Options Default Language Specifies the language (German / English) that is set as default the next time the iRMC S2 web interface is called. Figure 108: iRMC Information page . This setting applies for the current session and is preset the next time the iRMC S2 web interface is called. Colour Schema Specifies the color scheme for displaying the iRMC S2 web interface. This setting applies for the current session and is preset the next time the iRMC S2 web interface is called.iRMC S2 .

pre. V CAUTION! Always save the setting using Save iRMC S2 Firmware settings in ServerView® WinSCU XML format. you require Configure User Accounts permission.iRMC S2 web interface iRMC S2 .5.bin.Save Firmware settings 7. I If you want to save the user settings (Include User Settings). Save iRMC S2 Firmware settings in binary (BMCCLONE..2 Save iRMC S2 Firmware Settings Save firmware settings The Save iRMC S2 Firmware Settings page allows you to save the current firmware settings and a number of other settings for the iRMC S2 in a file. Configure iRMC S2 settings permission is sufficient.. button to load the firmware settings onto the iRMC again.exe) format are saved in a file with the name iRMC_S2_settings. – The firmware settings selected under Save iRMC S2 Firmware settings in binary (BMCCLONE. you can use the Import. – The firmware settings selected under Save iRMC S2 Firmware settings in ServerView® WinSCU XML format are saved in a file with the name iRMC_S2_settings. In all other cases.exe) format should only be used if the system module of the managed server is being replaced. In WinSCU (see page 403). iRMC S2 245 .

iRMC S2 . Save All Click Save All to save all the settings. 246 iRMC S2 .Save Firmware settings iRMC S2 web interface Figure 109: Save iRMC S2 Firmware Settings page Save Click Save to save the selected settings.

iRMC S2 247 . I The iRMC S2 is supplied with a predefined server certificate (default I Input format of the X.5. If you want to access the iRMC S2 over secure SSL/SSH connections.3 Certificate Upload .Certificate Upload 7.509 DSA/RSA certificate and the RSA/DSA must both be available in PEM-encoded format (ASCII/Base64). it is recommended that you replace the certificate with one signed by a Certificate Authority (CA) as soon as possible.509 DSA/RSA certificate and the private DSA/RSA key: The X.509 DSA/RSA certificate (SSL) from a Certificate Authority (CA) and/or your private DSA/RSA key (SSH) onto the iRMC S2. certificate).Load the DSA/RSA certificate and private DSA/RSA key The Certificate Upload page allows you to load a signed X.iRMC S2 web interface iRMC S2 .

iRMC S2 .Certificate Upload iRMC S2 web interface Figure 110: Certificate Upload page 248 iRMC S2 .

Certificate Upload Displaying the currently valid (CA) DSA/RSA certificate Ê In the group Certificate Information and Restore. click View CA Certificate to show the currently valid CA certificate.display of the currently valid SSL/SSH certificate iRMC S2 249 . Ê In the group Certificate Information and Restore.iRMC S2 web interface iRMC S2 . Figure 111: Certificate Upload page . click View Certificate to show the currently valid SSH/SSL-certificate.

Figure 112: Certificate Upload page . click Default Certificate to restore the default certificate delivered with the firmware after you have confirmed that you wish to do so. Ê In the group Certificate Information and Restore.Certificate Upload iRMC S2 web interface Restoring the default certificate default CA certificate Ê In the group Certificate Information and Restore.Restoring the default CA certificate 250 iRMC S2 . click Default CA Certificate to restore the default CA certificate delivered with the firmware after you have confirmed that you wish to do so.iRMC S2 .

Figure 113: Loading a CA certificate from a local file Proceed as follows: Ê Save the CA certificate in a local file on the managed server. This process can take up to 30 seconds... No explicit reset of the iRMC S2 is required. all the existing HTTPS connections are closed and the HTTPS server is automatically restarted. Ê Click the View CA Certificate button to make sure that the certificate has been loaded successfully.iRMC S2 web interface Loading a CA certificate from a local file iRMC S2 . iRMC S2 251 . I When you upload the certificate and/or private key. Ê Specify this file under CA Certificate File by clicking the associated Browse.Certificate Upload Use the CA Certificate upload from file group to load a CA certificate from a local file. button and navigating to the file containing the CA certificate. Ê Click the Upload button to load the certificate and/or the private key onto the iRMC S2.

Ê Click the View Certificate button to make sure that the certificate has been loaded successfully. Ê Click the Upload button to load the certificate and the private key onto the iRMC S2.Certificate Upload iRMC S2 web interface Loading the DSA/RSA certificate and private DSA/RSA key from local files You do this using the group SSL Certificate and DSA/RSA private key upload from file.iRMC S2 .509 DSA/RSA (SSL) certificate and the private DSA/RSA key in corresponding local files on the managed server. This process can take up to 30 seconds. I The private key and the certificate must be loaded on the iRMC S2 at the same time. No explicit reset of the iRMC S2 is required. Figure 114: Loading the DSA/RSA certificate / private DSA/RSA key from local files Proceed as follows: Ê Save the X. I When you upload the certificate and private key. all the existing HTTPS connections are closed and the HTTPS server is automatically restarted. 252 iRMC S2 . Ê Specify the files Private Key File and Certificate File by clicking on the associated Browse button and navigating to the file which contains the private key or the certificate.

I This is necessary in order to make a certificate or private key loaded onto the iRMC S2 valid. iRMC S2 253 . Ê Use the Remote Manager to reset the iRMC S2 (see section “Service processor . identification LED and iRMC S2 reset” on page 391). I You cannot simultaneously enter the certificate and key for the same upload.iRMC S2 web interface iRMC S2 . I Do not use this method to load a root certificate onto the iRMC S2.Certificate Upload Entering the DSA/RSA certificate / private DSARSA key directly You do this using the group SSL DSA/RSA certificate or DSA/RSA private upload via copy & paste. Always load a root certificate using a file (see page 252).509 DSA certificate or the private DSA key to the input area. Ê Click the View Certificate button to make sure that the certificate has been loaded successfully. Ê Click the Upload button to load the certificate or the private key onto the iRMC S2. Figure 115: Entering the DSA/RSA certificate / private DSARSA key directly Proceed as follows: Ê Copy the X.IP parameters.

Generate a self-signed Certificate iRMC S2 web interface 7.iRMC . Figure 116: Generate a self-signed RSA Certificate page 254 iRMC S2 .4 Generate a self-signed Certificate Generate self-signed RSA certificate You can create a self-signed certificate using the Generate a self-signed Certificate page.5.

I When generating the new certificate. This can take up to 5 minutes depending on the key length.iRMC S2 web interface iRMC . Certificate Creation Proceed as follows to create a self-signed certificate: Ê Enter the requisite details under Certificate Creation.Generate a self-signed Certificate Certificate Information and Restore The Certificate Information and Restore group allows you to view the currently valid DSA/RSA certificate and/or restore the default RSA/DSA certificate. No explicit reset of the iRMC S2 is required. View Certificate You can view the currently valid DSA/RSA certificate using this button. all the existing HTTPS connections are closed and the HTTPS server is automatically restarted. Ê Click Create to create the certificate. Default Certificate You can use this button to restore the default certificate delivered with the firmware after you have confirmed that you wish to do so. iRMC S2 255 .

5 iRMC S2 Firmware Update The iRMC S2 Firmware Update page allows you to update the iRMC S2 firmware online. Here you can also see information on the iRMC S2 firmware and set the firmware selector.iRMC S2 Firmware Update iRMC S2 web interface 7. you must provide the current firmware image either locally on a remote workstation or on a TFTP server. To do this. Figure 117: iRMC S2 Firmware Update page 256 iRMC S2 .5.

You have the following options: – Auto . – Select most recently programmed FW The most recently updated firmware image is selected.Firmware Information Firmware Selector You use the firmware selector to specify which firmware image is to be activated the next time the iRMC S2 is rebooted.iRMC S2 web interface Firmware Image Information iRMC S2 Firmware Update Under Firmware Image Information. Figure 118: iRMC S2 Firmware Update . – Low FW Image The low firmware image is selected. you can view information on the firmware version and the SDRR version of the iRMC S2 and set the firmware selector. – High FW Image The high firmware image is selected. – Select least recently programmed FW The least recently updated firmware image is selected. – Select FW Image with oldest FW version The firmware image with the oldest version is selected.FW Image with highest FW version The firmware image with the most recent version is selected automatically. iRMC S2 257 . Apply Click Apply to set the firmware selector to the option you have set under Firmware Selector.

inactive firmware The inactive firmware is automatically selected.iRMC S2 Firmware Update Firmware Update from File iRMC S2 web interface The Firmware Update from File page allows you to update the iRMC S2 firmware online. Figure 119: iRMC S2 Firmware Update page .com/com/support/downloads. – High Firmware Image The high firmware image (firmware image 2) is selected.html. You have the following options: – Auto .fujitsu. you must provide the current firmware image in a file on a remote workstation.ts. To do this. You will find the appropriate firmware image for your PRIMERGY server on PRIMERGY ServerView Suite DVD 1 or you can download it under http://support.Firmware Update from File Flash Selector Specify what iRMC firmware is to be updated. – Low Firmware Image The low firmware image (firmware image 1) is selected. 258 iRMC S2 .

Opens a file browser that allows you to navigate to the update file.iRMC S2 web interface Update file File in which the firmware image is stored.com/com/support/downloads.ts. Figure 120: iRMC S2 Firmware Update page .iRMC S2 TFTP Settings TFTP Server IP address or DNS name of the TFTP server on which the file with the firmware image is stored. iRMC S2 Firmware Update I The files listed below each allow you to update one component of the iRMC S2 firmware in every update run (runtime firmware and SDR record). iRMC S2 TFTP Settings The Firmware Update from File page allows you to update the iRMC S2 firmware online. you must provide the current firmware image in a file on a remote workstation.bin is also available for some PRIMERGY servers / blade servers.. Browse. You will find the appropriate firmware image for your PRIMERGY server on PRIMERGY ServerView Suite DVD 1 or you can download it under http://support. The file rt_sdt_<D-number>_4_08g_00.fujitsu. <SDR-Version>.html. dcod<FW-Version>. iRMC S2 259 . Ê Click the Apply button to activate your settings and to start updating the iRMC S2 firmware.SDR Updates the SDR record..bin Updates the runtime firmware. This allows you to update all the components of the iRMC S2 firmware in a single operation. To do this.

Ê Click the TFTP Start button to download the file containing the firmware image from the TFTP server and to start updating the iRMC S2 firmware.iRMC S2 Firmware Update Update file File in which the firmware image is stored. dcod<FW-Version>. This allows you to update all the components of the iRMC S2 firmware in a single operation using a TFTP server. – Low Firmware Image The low firmware image (firmware image 1) is selected.bin is also available for some PRIMERGY servers / blade servers. The file rt_sdt_<D-number>_4_08g_00. iRMC S2 web interface I The files listed below each allow you to update one component of the iRMC S2 firmware every time TFTP is started (runtime firmware and SDR record).inactive firmware The inactive firmware is automatically selected. <SDR-Version>. 260 iRMC S2 .bin Updates the runtime firmware. – High Firmware Image The high firmware image (firmware image 2) is selected. You have the following options: – Auto . Flash Selector Specify what iRMC firmware is to be updated. Ê Click the TFTP Test button to test the connection to the TFTP server.SDR Updates the SDR record. Ê Click the Apply button to activate your settings.

6 Power Management The Power Management entry contains the links to the power management pages for your PRIMERGY server: – “Power On/Off . – “Power Supply Info .power the server up/down” on page 262. – “Power Options .Power supply and IDPROM data for the FRU components” on page 270.Configuring power management for the server” on page 267.iRMC S2 web interface Power Management 7. iRMC S2 261 .

Power Management .6.power the server up/down The Power On/Off page allows you to power the managed server on and off. Figure 121: Power On/Off page 262 iRMC S2 .1 Power On/Off . You are informed of the server’s current power status and are also able to configure the behavior of the server during the next boot operation.Power On/Off iRMC S2 web interface 7.

In addition.Power Status Summary iRMC S2 263 .Power On/Off The Power Status Summary group provides information on the current power status of the server and on the causes for the most recent Power On/Power Off. a Power On counter records the total months. days and minutes during which the server has been powered. Figure 122: Power On/Off page .iRMC S2 web interface Power Status Summary Power Management .

the default mechanism applies again. Ê Click the Apply button to activate your settings. – Floppy: The system is booted from floppy disk. Halt on errors Interrupt the boot process if errors occur during the POST phase. Ê From the Boot Device Selector list. You can set whether the BIOS is to interrupt the boot process for the system if errors occur during the POST phase. – Harddrive: The system is booted from hard disk.Power Management . select the storage medium you wish to boot from. I The options set here only apply to the next boot operation. – PXE/iSCSI: The system is booted from PXE / iSCSI over the network. – CDROM/DVD: The system is booted from CD /DVD. 264 iRMC S2 . After this. The following options are available: – No change: The system is booted from the same storage medium as previously. Figure 123: Power Management .Power On/Off Boot Options iRMC S2 web interface The Boot Options group allows you to configure the behavior of the system the next time it is booted.Boot Options page Ê Select the desired BIOS behavior from the Error Halt Settings list: Continue Continue the boot process if errors occur during the POST phase.

Restart (server is powered up) Figure 125: Power On/Off page. Immediate Reset Completely restarts the server (cold start). Press Power Button Depending on the operating system installed and the action configured. Power Cycle Powers the server down completely and then powers it up again after a configured period. Immediate Power Off Powers the server down. Restart (server is powered down) Power On Switches the server on. you can trigger various actions by briefly pressing the power-off button. You can configure this time in the Power Cycle Delay field of the ASR&R Options group (see page 298). iRMC S2 265 .powering the server up and down / rebooting the server The Power Control group allows you to power the server up/down or to reboot the server. regardless of the status of the operating system.Power On/Off Power Control . Figure 124: Power On/Off page.iRMC S2 web interface Power Management . regardless of the status of the operating system. These actions could be shutting down the computer or switching it to standby mode or sleep mode.

Ê Click the Apply button to start the required action. 266 iRMC S2 .Power On/Off iRMC S2 web interface Graceful Power Off (Shutdown) Graceful shutdown and power off. Graceful Reset (Reboot) Graceful shutdown and reboot. This option is only available if ServerView agents are installed and signed onto the iRMC S2 as “Connected”.Power Management . This option is only available if ServerView agents are installed and signed onto the iRMC S2 as “Connected”.

2 Power Options Configuring power management for the server The Power Options page allows you to define the server’s behavior after a power outage and specify the server’s power on/off times.Power Options 7.6. Figure 126: Power Options page iRMC S2 267 .iRMC S2 web interface Power Management .

Specify behavior of the server after a power outage The Power Restore Policy group allows you to specify the server’s power management behavior after a power outage. The configured action will be performed after a power outage. 268 iRMC S2 .Power Options iRMC S2 web interface Power Restore Policy . Restore to powered state prior to power loss The power up/down status of the server is restored to the status prior to the power outage. Figure 127: Power Options page. Always power on The server is always powered up again after a power outage. Power Restore Policy Always power off The server always remains powered down after a power outage.Power Management . Ê Click the Apply button to activate your settings.

Power Options Power On/Off Time . No traps are sent if you specify the value “0”. iRMC S2 269 . Figure 128: Power Options page. if so. Power On/Off Time Ê Click the Apply button to activate your settings. how many minutes before the event this should be done.iRMC S2 web interface Power Management .Specify power on/off times for the server The input fields of the Power On/Off Time group allow you to specify the times at which the server is powered up/down for the individual days of the week or for specified times during the day. I Specifications in the Everyday field take priority! The Trap fields also allow you to configure whether the iRMC S2 sends an SNMP trap to the management console before a planned power-on / power-off of the managed server and.

Power Management .3 Power Supply Info . The CSS Component column indicates for each of the components whether the CSS (Customer Self Service) functionality is supported.6. Figure 129: Power Supply Info page 270 iRMC S2 .Power supply and IDPROM data for the FRU components The Power Supply Info page provides you with information on the power supply specifications and the IDPROM data of the FRUs of the server.Power Supply Info iRMC S2 web interface 7.

Configure power consumption of the server” on page 272.) – “Power Consumption History .Control the power consumption of the server The Power Consumption entry contains the links to the pages for monitoring and controlling the power consumption of the managed server: – “Power Consumption Configuration .iRMC S2 web interface Power Consumption 7.Show server power consumption” on page 279 (Not shown on all servers with iRMC S2.Configuring power management for the server” on page 267.7 Power Consumption . – “Power Options . (Not shown on all servers with iRMC S2.) iRMC S2 271 .

Configure power consumption of the server The Power Consumption Configuration page allows you to specify the mode the iRMC S2 uses to control the power consumption of your PRIMERGY server. the Power Limit Options group is also displayed (see page 274). 272 iRMC S2 . I If you set the “Power Limit” power control mode in the Power Consumption Options group or in the Scheduled Power Consumption Configuration.7.Power Consumption iRMC S2 web interface 7.1 Power Consumption Configuration . – The Enhanced Speed Step option must be enabled in the BIOS setup. Figure 130: Power Consumption Configuration page I Prerequisite: The following requirements must be met in order to configure power consumption control: – The managed PRIMERGY server must support this feature.

– Scheduled: The iRMC S2 controls power consumption in accordance with a schedule that you can define using the SCU (see “Scheduled Power Consumption Configuration” on page 274). Power Control Mode Mode for controlling the power consumption of the managed server: – Power Mgmt. Disabled: The iRMC S2 allows the operating system to control power consumption.iRMC S2 web interface Power Consumption Options Power Consumption The Power Consumption Options group allows you to select the power control mode and specify whether the power consumption should be monitored over time. power consumption can rise. Power Monitoring Units Unit of electrical power used to display power consumption: – Watt – BTU/h (British Thermal Unit/hour. 1 BTU/h corresponds to 0. performance is not always ideal. In this event.293 Watt). – Minimum Power: The iRMC S2 controls the server to achieve the lowest possible power consumption. iRMC S2 273 . – Power Limit: The Power Limit Options group is displayed (see “Power Limit Options” on page 276). In this event. – Best Performance: The iRMC S2 controls the server to achieve best performance.

If this is not the case.g. this may be because: – The CPU (e. Ê Click the Apply button to activate your settings.32 of the firmware. I Power monitoring is enabled by default as of Version 3. 274 iRMC S2 . low-power CPU) of the server does not support scheduled power control.Power Consumption iRMC S2 web interface Enable Power Monitoring If you enable this option. Scheduled Power Consumption Configuration The Scheduled Power Consumption Configuration group allows you to specify in detail the schedules and modes (operating-system-controlled. best performance. – The system is currently in the BIOS POST phase. a message to this effect is displayed. I The Scheduled Power Consumption Configuration group only appears if you I Configuration for scheduled power control mode assumes that the If this message appears even though “Enhanced Speed Step” is enabled. Enhanced Speed Step option has been enabled in the BIOS setup. lowest power consumption) that the iRMC S2 uses to control power consumption on the managed server. I This setting only takes effect on PRIMERGY servers that support power monitoring. power consumption is monitored over time. have enabled the power control mode scheduled in the Power Consumption Options group.

Time 2 Time [hh:ss] at which the iRMC S2 starts power control as defined in Mode 2 on the relevant day of the week. iRMC S2 Mode 2 will only be activated at Time 2 on the relevant day of the following week. 275 . otherwise the power control mode specified under I Specifications in the Everyday field take priority.iRMC S2 web interface Power Consumption Figure 131: Power Consumption Configuration page (scheduled) Time 1 Time [hh:ss] at which the iRMC S2 starts power control as defined in Mode 1 on the relevant day of the week. I Set Time 1 < Time 2. Mode 2 Power consumption mode used by the iRMC S2 for power control as of Time 2 on the relevant day of the week. Mode 1 Power consumption mode used by the iRMC S2 for power control as of Time 1 on the relevant day of the week.

Figure 132: Power Consumption Configuration page (scheduled) Power Limit Maximum power consumption (in Watts). The power limit then applies to all periods for which this power control mode is enabled in the Scheduled Power Consumption Configuration group. Power Limit Options The Power Limit Options group is displayed under the following circumstances: – The power control mode Power Limit is selected and enabled in the Power Consumption Options group.Power Consumption Ê Click the Apply button to activate your settings. 276 iRMC S2 . – The power control mode Scheduled is enabled in the Power Consumption Options group and the power control mode Power Limit is enabled at least once in the Scheduled Power Consumption Configuration group. iRMC S2 web interface I You can also configure scheduled power control using the Server Configuration Manager (see section “iRMC Power Consumption Control Control the power consumption of the server” on page 410).

Immediate Power Off The server is immediately powered down irrespective of the status of the operating system. When the threshold is reached. Enable Dynamic Power Control The power limit is controlled dynamically. I This option is only supported if ServerView agents are installed and signed onto the iRMC S2 as “Connected”. Action Reaching Power Limit Action to be performed after the threshold has been reached and the grace period has expired. iRMC S2 277 .iRMC S2 web interface Power Consumption Warning Threshold Threshold as a percentage of the maximum power consumption specified under Power Limit. Graceful Power Off (Shutdown) Shut down the system "gracefully" and power it down. Power Limit Grace Period Period (in minutes) for which the system waits after the threshold has been reached until the action is performed. the action defined under Action Reaching Power Limit is performed. Continue No action is performed.

7. Figure 133: Current Power Consumption page 278 iRMC S2 .2 Current Power Consumption Show the current power consumption I This view is not supported by all PRIMERGY servers with iRMC S2. The Current Power Consumption page shows the current power consumption of the system components and of the overall system.Current Power Consumption iRMC S2 web interface 7.

7. I This page is not shown on all PRIMERGY servers with iRMC S2.3 Power Consumption History Show server power consumption The Power Consumption History page charts the power consumption of your PRIMERGY server. Figure 134: Power Consumption History page iRMC S2 279 .iRMC S2 web interface Current Power Consumption 7.

Power History Options Power History Units Electrical power units: – Watt – BTU/h (British Thermal Unit/hour. 1 BTU/h corresponds to 0. minimum. A graphical display also shows the current power consumption of the server compared with the maximum possible power consumption.Current Power Consumption Current Power Consumption iRMC S2 web interface I This option is not supported for all PRIMERGY servers.Current Power Consumption Power History Options You specify the parameters for displaying the power consumption under Power History Options.293 Watt). maximum and average power consumption. Figure 135: Power Consumption History . 280 iRMC S2 . Under Current Power Consumption you can see all the measurements for the server power consumption in the current interval: current. Figure 136: Power Consumption History .

Measurements for the last hour (60 values). iRMC S2 281 . 12 hours Measurements for the last 12 hours. this shows all the measurements of the last hour. One measurement is shown for each 10-minute period (every 10th measurement. 168 values in all). One measurement per hour is shown (every 60th measurement. 180 values in all). 1 day Measurements for the last 24 hours.iRMC S2 web interface Current Power Consumption Power History Period Period for which the power consumption is charted. 180 values in all). The following intervals can be selected: 1 hour Default. One measurement is shown for each period of approx four hours (every 120th measurement. One measurement is shown for each two-day period (every 2880th measurement. 2 weeks The measurements for the last month. 144 values in all). 1 month The measurements for the last 6 months. 1 year Measurements for the last 12 months. 1 week The measurements for the last week. One measurement is shown for each five-minute period (every 5th measurement. 168 values in all). Since one measurement is generated every minute. 144 values in all). One measurement is shown for each period of approx one day (every 240th measurement.

Current Power Consumption iRMC S2 web interface Enable Power Monitoring Specifies whether power monitoring is to be carried out. Figure 137: Power Consumption History . Power History Chart Power History Chart shows the power consumption of the managed server over time in the form of a graph (using the settings made under Power History Options). Ê Click the Delete History button to delete the displayed data.Power History Chart 282 iRMC S2 . I This setting only applies to PRIMERGY servers that support consumption logging. Ê Click the Apply button to activate your settings.32 of the firmware. I Power Monitoring) is enabled by default as of Version 3.

Check status of the sensors The “Sensors” entry provides you with pages which allow you to test the sensors of the managed server: – “Fans . – “Temperature .Check fans” on page 284. – “Power Supply .Check temperature sensors” on page 286. To facilitate checking the status. the sensor status is not only shown in the form of the current value. but also using a color code and a status icon: Black / The measured value is within the normal operational value range. – “Component Status . System operation is not yet jeopardized.Check status of the server components” on page 290. Table 7: Status of the sensors iRMC S2 283 . System operation may be jeopardized and there is a risk of loss of data integrity. Orange / The measured value has exceeded the warning threshold. Red / The measured value has exceeded the critical threshold. – “Voltages .8 Sensors .Check voltage sensors” on page 288.Check power supply” on page 289.iRMC S2 web interface Sensors 7.

1 Fans .Fans iRMC S2 web interface 7. Figure 138: Fans page 284 iRMC S2 .8.Sensors .Check fans The Fans page provides information on fans and their status.

Ê Select the fans for which you wish to define the behavior in the event of a fault. you must also specify the time in seconds between failure of the fan and shutdown of the server (Shutdown Delay) in the field to the right of the list. Select all Selects all fans. Ê Click the Start Fan Test button to start the fan test explicitly. I In the case of redundant fans. Ê Click the Apply to the selected Fans button to activate your settings for the selected fans. Analog Fans . Fan Check Time Enter the time at which the fan test is to be started automatically.Test fans Sensors . If you choose this option. – Choose shutdown-and-power-off if the server is to be shut down and powered down if the selected fans fail. You can use the options or buttons to select individual fans or all the fans and specify whether the server should be shut down after a specified number of seconds if this fan fails. iRMC S2 285 . shutdown is only initiated if more than one fan is faulty and shutdown-and-power-off is also set for these fans.Fans The Fan Test group allows you to specify a time at which the fan test is started automatically or to start the fan test explicitly.Specify server behavior in the event that a fan fails The Analog Fans group provides you with information on the status of the fans. Disable Fan Test Select this option to disable fan testing. Deselect all All selections are cancelled. Ê Click the Apply button to activate your settings.iRMC S2 web interface Fan Test . Ê Define the behavior in the event of a fault using the list at the bottom of the work area: – Choose continue if the server is not to be shut down if the selected fans fail.

Temperature iRMC S2 web interface 7. Figure 139: Temperature page You can use the options or buttons to select individual temperature sensors or all the temperature sensors and specify whether the server is to be shut down if the critical temperature is reached at the selected sensors. such as the CPU and the FBD (FullyBuffered DIMM) and the ambient temperature.Check temperature sensors The Temperature page provides information on the status of the temperature sensors which measure the temperature at the server components.8. 286 iRMC S2 . Select all Selects all temperature sensors.2 Temperature .Sensors .

Temperature Ê Select the sensors for which you wish to define the behavior in the event that the critical temperature is reached. Ê Click the Apply to the selected Sensors button to activate your settings for the selected temperature sensors. Ê Define the behavior in the event that the critical temperature is reached using the list at the bottom of the work area: – Choose continue if the server is not to be shut down if the critical temperature is reached at the selected sensors. – Choose shutdown-and-power-off if the server is to be shut down and powered down if the critical temperature is reached at the selected sensors. iRMC S2 287 .iRMC S2 web interface Deselect all All selections are cancelled. Sensors .

Check voltage sensors The Voltages page provides information on the status of voltage sensors assigned to the server components.3 Voltages . Figure 140: Voltages page 288 iRMC S2 .Voltages iRMC S2 web interface 7.Sensors .8.

Figure 141: Power Supply page iRMC S2 289 .Power Supply 7.Check power supply The Power Supply page provides information on the power supplied from the power supply units.4 Power Supply .iRMC S2 web interface Sensors .8.

Figure 142: Component Status page 290 iRMC S2 .Sensors . The CSS Component column indicates for each of the components whether the CSS (Customer Self Service) functionality is supported.8.5 Component Status Check status of the server components The Component Status page provides information on the status of the server components.Component Status iRMC S2 web interface 7.

iRMC S2 web interface System Event Log 7. – “System Event Log Configuration .Show information on the SEL and SEL entries” on page 292.Displaying and configuring the server’s event log The System Event Log entry contains the links to the pages for viewing and configuring the server event log (system event log.Configure the SEL” on page 295.9 System Event Log (SEL) . SEL): – “System Event Log Content .error categories iRMC S2 291 . Colored icons are assigned to the various event/error categories to improve clarity: Critical Major Minor Informational Customer Self Service (CSS) event Table 8: System event log content .

Figure 143: System Event Log Content page 292 iRMC S2 . The CSS Event column indicates for each of the events whether the event was triggered by a CSS (Customer Self Service) component.9.System Event Log iRMC S2 web interface 7.1 System Event Log Content Show information on the SEL and SEL entries The System Event Log Content page provides information on the SEL and displays the SEL entries.

the iRMC S2 allows you to download the file iRMC S2_EventLog.iRMC S2 web interface System Event Log Information System Event Log The System Event Log Information group informs you of the number of entries in the SEL. It also indicates the time when the last entries were added or deleted. which contains the SEL entries. Figure 144: System Event Log Content page. iRMC S2 293 . System Event Log Information Clear Event Log Click the Clear Event Log button to clear all the entries in the SEL.sel. Save Event Log After you have clicked the Save Event Log button.

After that. 294 iRMC S2 . Display Major.System Event Log System Event Log Content iRMC S2 web interface The System Event Log Content group displays the SEL entries filtered by error class. However. I You can modify the filter criteria for the duration of the current session in the System Event Log Content group. Ê Click the Apply button to activate your settings for the duration of the current session. the settings you make here are only valid until the next logout. Display Minor. System Event Log Content Display Critical. you can choose one or more severity levels other than the default values here. Display Info. Figure 145: System Event Log Content page. CSS only If you wish. the default settings apply again.

– whether the SEL is organized as a ring buffer or a linear buffer.2 System Event Log Configuration Configure the SEL On the System Event Log Configuration page.iRMC S2 web interface System Event Log 7. you can configure – the SEL entries which are displayed by default on the System Event Log Content page (see page 292).9. Figure 146: System Event Log Configuration page iRMC S2 295 .

CSS only Here you select one or more severity levels for which SEL entries should be displayed by default on the System Event Log Content page. I If a ServerView Local Service Display module is fitted in the managed PRIMERGY server. Ê Click the Apply button to activate your settings. you can also select the error severities for displaying the SEL entries in the display panel of the ServerView Local Service Display module. I When the linear SEL has been completely filled. it is not possible to add any further entries. 296 iRMC S2 . (This selection is independent of the selection you have made for the SEL entries displayed on the System Event Log Content page. Helpdesk Information Figure 147: Helpdesk Information Help desk String used to display the Help Desk Ê Click the Apply button to activate your settings. IPMI SEL The SEL is organized as a linear buffer.) Ring SEL The SEL is organized as a ring buffer. Display Minor. Display Info.System Event Log iRMC S2 web interface Display Critical. Display Major.

10 Server Management Information Configuring the server settings The Server Management Information page allows you to configure the following settings on the server: – ASR&R (automatic server reconfiguration and restart) settings for the server (see page 298) – Watchdog settings (see page 299) – HP System Insight Manager (HP SIM) integration (see page 300) Figure 148: Server Management Information page iRMC S2 297 .iRMC S2 web interface Server Management Information 7.

7) Maximum number of restart attempts that should be permitted for the server after a critical error (up to 7). boots after the firmware has been updated.Server Management Information ASR&R Options . ASR&R Options Retry counter Max (0 . I The Enabled setting is of value if the operating system no longer After a BIOS recovery flash has been performed successfully. Figure 149: Server Management Information page.Max) Number of restart attempts that a server should attempt after a critical error (maximum value is the value set under Retry counter Max). – Disabled The next time the system is booted. A BIOS recovery flash is then performed automatically the next time the system is booted from the DOS floppy (or a DOS floppy image). Retry counter (0 . the BIOS is not automatically flashed. 298 iRMC S2 . the BIOS is automatically flashed.Configure ASR&R settings iRMC S2 web interface The ASR&R Options group allows you to configure the ASR&R (automatic server reconfiguration and restart) settings for the server. reset the BIOS Recovery Flash bit to disabled. I The settings made on the ASR&R Options group become active the next time the managed server is started. BIOS recovery flash bit Enables/disables the BIOS recovery flash bit: – Enabled The next time the system is booted.

Configure software watchdog and boot watchdog The Watchdog Settings group allows you configure the software watchdog and the boot watchdog. The software watchdog is activated when the ServerView agents and the operating system have been completely initialized. If no more messages are received from a ServerView agent. The boot watchdog monitors the phase between startup of the system and the time at which the ServerView agents become available. Watchdog Options The software watchdog monitors the activities of system using the ServerView agents. Ê Click the Apply button to save your settings. You can specify an action to be performed if this happens. it is assumed that the system is no longer functioning correctly. The ServerView agents contact the iRMC S2 at defined intervals. iRMC S2 299 . I The settings made on the ASR&R Options group become active the next time the managed server is started.iRMC S2 web interface Server Management Information Power Cycle Delay (0 . If the ServerView agents do not establish a connection to the iRMC S2 of the server within a specified time.15) Time (in seconds) between powering down and powering up during a power cycle. it is assumed that the boot process has not been successful. Figure 150: Server Management Information page. Proceed as follows: Ê Check or uncheck the option(s) under Enabled for the Software Watchdog and/or Boot Watchdog. Watchdog Settings . The configured settings are saved and the actions which have been configured are performed in the appropriate circumstances. You can specify an action to be performed if this happens.

I The boot watchdog must wait until the system has been started. The configured settings are saved and the actions which have been configured are performed in the appropriate circumstances. Figure 151: Page Server Management Information .e. i.HP SIM Integration Options Proceed as follows: Ê Activate/deactivate the HP SIM Integration Disabled option in order to deactivate or to activate HP SIM integration. 300 iRMC S2 . HP System Insight Manager (HP SIM) Integration Options Configure HP SIM integration therefore have to specify a sufficient period for after timeout delay (1 100). Reset The server management software triggers a system reset. Ê Click the Apply button to activate your settings. Ê As appropriate. you can configure the following settings after Software Watchdog and/or Boot Watchdog: Continue No action is performed when the watchdog has expired. You Ê Click the Apply button. Power Cycle The server is powered down and immediately powered up again. The HP System Insight Manager (HP SIM) Integration Options group allows you to configure whether the iRMC S2 device will return some identifying information in response to an unauthenticated XML query sent from the HP System Insight Manager. the server continues to run.Server Management Information iRMC S2 web interface Ê If you have activated either of these options. An entry is made in the event log. enter the time (in minutes) after which this action is to be performed following after timeout delay.

– “DNS Settings .11 Network Settings Configure the LAN parameters The Network Settings entry brings together the links to the pages you use to configure the LAN parameters of the iRMC S2: – “Network Interface . – “Ports and Network Services .Configure Ethernet settings on the iRMC S2” on page 302.Configuring ports and network services” on page 305.Configuring the host name for the iRMC S2” on page 309.Enable DNS for the iRMC S2” on page 311.iRMC S2 web interface Network Settings 7. – “DHCP Configuration . iRMC S2 301 .

1 Network Interface Configure Ethernet settings on the iRMC S2 The Network Interface page allows you to view and change the Ethernet settings for the iRMC S2.11.Network Settings . Figure 152: Network Interface page 302 iRMC S2 .Network Interface iRMC S2 web interface 7.

the onboard LAN controller assigned to the iRMC S2 autonomously determines the correct transfer speed and duplex method for the network port it is connected to. the serial interface or via the BIOS. you will only be able to access the iRMC S2 using special configuration software.Network Interface V CAUTION! Contact the network administrator responsible for the system before you change the Ethernet settings. If you make illegal Ethernet settings for the iRMC S2. On some PRIMERGY server models. If Auto Negotiation is selected. LAN Port I This option is not supported for all PRIMERGY servers. LAN Speed LAN speed. The following options are available: – – – – – Auto Negotiation 100 MBit/s Full Duplex 100 MBit/s Half Duplex 10 MBit/s Full Duplex 10 MBit/s Half Duplex edit Ethernet settings (see chapter “User management for the iRMC S2” on page 59). I Only users with the Configure iRMC S2 Settings permission are allowed to MAC Address The iRMC S2’s MAC address is displayed here.iRMC S2 web interface Network Settings . iRMC S2 303 . the LAN interface of the installed system NIC (network interface card) can be set up – as shared LAN for shared operation with the system or – as a service LAN for exclusive use as a management LAN.

Otherwise (if the DHCP enable option is activated). Permitted value range: 1 Î VLAN Id Î 4094. the iRMC S2 only uses the field to display the address. Ê Click the Apply button to activate the configured Ethernet settings. activated) then you can enter this here.Network Interface iRMC S2 web interface IP Address The IP address of the iRMC S2 in the LAN.e. This address is different from the IP address of the managed server. The (configured) iRMC S2 can be registered with a DNS server by an appropriately configured DHCP server (see sections “DHCP Configuration .Enable DNS for the iRMC S2” on page 311). 304 iRMC S2 . it continues searching for a DHCP server until it finds one). Permitted value range: 0 Î VLAN Priority Î 7 (default: 0). the iRMC S2 goes into a search loop (i. VLAN Priority VLAN priority (user priority) of the iRMC S2 in the VLAN specified by VLAN Id. the iRMC S2 gets its LAN settings from a DHCP server on the network. DHCP enable If you activate this option. gateway IP address of the default gateway in the LAN. I If you are working with a static address (DHCP enable option not Subnet Mask Subnet mask of the iRMC S2 in the LAN. I Do not activate the DHCP option if no DHCP server is available on the network. VLAN enable This option allows you to activate VLAN support for the iRMC S2 VLAN Id VLAN ID of the virtual network (VLAN) the iRMC S2 belongs to.Configuring the host name for the iRMC S2” on page 309 and “DNS Settings .Network Settings . If you activate the DHCP option and there is no DHCP server available on the network.

iRMC S2 305 .Ports and Network Services 7.11.iRMC S2 web interface Network Settings . Figure 153: Ports and Network Services page I Configuration is not supported for ports where the input fields are deactivated in the iRMC S2 web interface.2 Ports and Network Services Configuring ports and network services The Ports and Network Services page allows you to view and modify the configuration settings for ports and network services.

seconds field. and you can log in again as required (see page 222). the contents of the iRMC S2 web interface are automatically refreshed periodically. Force HTTPS If you enable the Force HTTPS option. users can only establish a secure connection to the iRMC S2 on the HTTPS port specified in the entry field. Enable Auto Refresh If you activate this option. I If the SSL certificate has expired..Ports and Network Services Ports for web-based access iRMC S2 web interface Session Timeout Period of inactivity (in seconds) after which the session is automatically closed. If you disable the Force HTTPS option. I Your session will not automatically be closed if it is inactive when HTTP Port HTTP port of the iRMC S2 Default port number: 80 Configurable: yes Enabled by default: yes Communication direction: inbound and outbound HTTPS Port HTTPS (HTTP Secure) port of the iRMC S2 Default port number: 443 Configurable: yes Enabled by default: yes Communication direction: inbound and outbound the time specified in Session Timeout has elapsed if you enter a value for the refresh interval which is less than the Session Timeout in the Refresh every . seconds field (see page 307)..Network Settings . The login page of the iRMC S2 web interface then appears. Specify the refresh interval in the Refresh every . a message to this effect is issued in the browser. users can establish a non-secure connection to the iRMC S2 on the HTTP port specified in the entry field... 306 iRMC S2 .

. seconds Length (in seconds) of the interval for automatically refreshing the iRMC S2 web interface.. I If you enter a value for the refresh interval which is less than the Ports for text-based access Telnet Port Telnet port of the iRMC S2 Default port number: 3172 Configurable: yes Enabled by default: no Communication direction: inbound and outbound Session Drop Time Period of inactivity (in seconds) after which a Telnet connection is automatically cleared. your session will not automatically be closed when the time specified in Session Timeout has elapsed in the event of inactivity. SSH Port SSH (Secure Shell) port of the iRMC S2 Default port number: 22 Configurable: yes Enabled by default: yes Communication direction: inbound and outbound Session Timeout (see page 306). Telnet enabled If you enable the Telnet Enabled option.iRMC S2 web interface Network Settings . users can establish a connection to the iRMC S2 on the Telnet port specified in the entry field.Ports and Network Services Refresh every . iRMC S2 307 .

Ports and Network Services VNC ports iRMC S2 web interface Standard Port VNC port of the iRMC S2 for secure and non-secure Advanced Video Redirection (AVR) Port number: 80 Hard-configured Enabled by default: yes Communication direction: inbound Secure Port (SSL) VNC port of the iRMC S2 for the SSL-secured transfer of mouse and keyboard input for AVR.Network Settings . Port number: 443 Hard-configured. 308 iRMC S2 . Enabled by default: yes Communication direction: inbound Remote Storage Ports Standard Port Default remote storage port of the iRMC S2 Default port number: 5901 Configurable: yes Enabled by default: yes Communication direction: outbound to the remote workstation Ê Click the Apply button to store the configured settings.

Use iRMC S2 Name instead of Hostname The iRMC S2 name specified in the iRMC S2 Name entry field is used for the iRMC S2 instead of the server name. iRMC S2 309 .11. Figure 154: DHCP Configuration page Register DHCP Address in DNS Enables/disables transfer of the DHCP name to the DHCP server for the iRMC S2.3 DHCP Configuration Configuring the host name for the iRMC S2 The DHCP Configuration page allows you to configure a host name for the iRMC S2 and thus use “dynamic DNS”. Add Serial Number The last 3 bytes of the MAC address of the iRMC S2 are appended to the DHCP name of the iRMC S2.iRMC S2 web interface Network Settings . Dynamic DNS allows DHCP servers to autonomously pass on the IP address and system name of a network component to DNS servers to facilitate identification.DHCP Configuration 7.

DHCP Configuration iRMC S2 web interface Add Extension The extension specified in the Extension entry field is appended to the DHCP name of the iRMC S2. Extension Enter a name extension for the iRMC S2. iRMC S2 Name iRMC S2 name passed to DHCP for the iRMC S2 in place of the server name. 310 iRMC S2 .Network Settings . DNS Name Shows the configured DNS name for the iRMC S2.

In this event.4 DNS Settings .DNS Settings 7. Figure 155: DNS Configuration page DNS enabled Enables/disables DNS for the iRMC S2.DNS-Server 5.Enable DNS for the iRMC S2 The DNS Settings page allows you to activate the Domain Name Service (DNS) for the iRMC S2. iRMC S2 311 . the IP addresses of the DNS servers are obtained automatically from the DHCP server. This allows you to use symbolic DNS names instead of IP addresses for configuring the iRMC S2. you can enter up to five DNS server addresses manually under DNS-Server 1 .iRMC S2 web interface Network Settings . up to five DNS servers are supported.11. Obtain DNS configuration from DHCP If you activate this option. If you do not enable this setting.

. you can enter the names of up to five DNS servers here. DNS Server 1 . 312 iRMC S2 . specify the name of the default domain for requests to the DNS server(s).DNS Settings iRMC S2 web interface DNS Domain If the option Obtain DNS configuration from DHCP is disabled. Ê Click the Apply button to store the configured settings. 5 If the Obtain DNS configuration from DHCP option is disabled.Network Settings .

Configure alerting via modem” on page 315. iRMC S2 313 .Configure SNMP trap alerting” on page 314.Configure email alerting” on page 317. – “Email Alerting .iRMC S2 web interface Alerting 7.12 Alerting .Configure alerting The Alerting entry contains the links to the pages you use to configure alerting for the iRMC: – “SNMP Trap Alerting . – “Serial / Modem Alerting .

Ê Click the Apply button to activate the SNMP server as a trap destination. SNMP Server1 . Figure 156: SNMP Trap Alerting page SNMP Community Name of the SNMP community.SNMP Trap Alerting iRMC S2 web interface 7..12.1 SNMP Trap Alerting Configure SNMP trap alerting The SNMP Trap Alerting page allows you to view and configure the settings for SNMP trap alerting. Ê Click the Apply button to accept the community name. 314 iRMC S2 . I Forwarding of SNMP traps to up to seven SNMP servers is supported. Ê Click the Test button to test the connection to the SNMP server. SNMP Server7 (trap destinations) DNS names or IP addresses of the servers that belong to this community and are to be configured as Trap Destinations. Ê Click Apply All to activate all the settings if appropriate.Alerting .

iRMC S2 web interface Alerting . Modem Dial Prefix This entry will depend on the type of connection you have. Modem Init String Please refer to your modem documentation for details on this entry.Serial/Modem Alerting 7. Figure 157: Serial / Modem Alerting page Modem Alerting Enable Enables or disables serial/modem alerting.2 Serial / Modem Alerting Configure alerting via modem The Serial / Modem Alerting page allows you to configure how alerts are forwarded via a modem. Provider Phone Number Enter the name of the SMS server. iRMC S2 315 .12. Modem Reset/Hangup String Please refer to your modem documentation for details on this entry.

SMS Protocol Type Enable the option corresponding to the mobile phone network used.Serial/Modem Alerting Handy/Pager Phone Number Enter the name of the mobile phone.Alerting . Ê Click the Apply button to activate your settings. Ê Click the Test button to send a test alert. Handy/Pager Type You can choose between: – – – – – Signal Pager Numeric Pager Alpha pager SMS DoCoMo iRMC S2 web interface SMS Message Length Limit You can choose between 80 or 140 as the maximum length. 316 iRMC S2 .

Figure 158: Email Alerting page iRMC S2 317 .3 Email Alerting . I Configuration of two mail servers is supported.Email Alerting 7. Email alerting can be specified individually for each user (see section “User “<name>” Configuration .iRMC S2 web interface Alerting . I Email alerting is currently not supported for global iRMC S2 user IDs (see chapter “User management for the iRMC S2” on page 59).User configuration (details)” on page 326).12.Configure email alerting The Email Alerting page allows you to configure the settings for email alerting.

Global Email Configuration Email Alerting Enable Activate this option. Figure 159: Email Alerting page.255) Time (in seconds) between SMTP retries. Ê Click the Apply button to activate your settings.7) Number of SMTP retries. 318 iRMC S2 .Email Alerting iRMC S2 web interface Global Email Paging Configuration . SMTP Retry Delay (0 .Configure global email settings The Global Email Paging Configuration group allows you to configure the global email settings. SMTP Retries (0 . SMTP Response Timeout Timeout (in seconds) for an SMTP response.Alerting .

iRMC S2 web interface Alerting . the following information is required: Auth User Name User name for authentication on the mail server Auth Password Password for authentication on the mail server Confirm Password Confirm the password entered. Primary SMTP Server Configuration SMTP Server IP address of the primary mail server I You can activate the Domain Name Service (DNS) for the SMTP Port SMTP port of the mail server iRMC S2 (see “DNS Settings .Enable DNS for the iRMC S2” on page 311).Email Alerting Primary SMTP Server Configuration . iRMC S2 319 . Figure 160: Email Alerting page. Ê Click the Apply button to activate your settings. You can then use a symbolic name instead of the IP address. Auth Type Authentication type for connecting the iRMC S2 to the mail server: – None No authentication for the connection. In this case.Configure primary mail server The Primary SMTP Server Configuration group allows you to configure the primary server (SMTP server). – SMTP AUTH (RFC 2554) Authentication according to RFC 2554: SMTP Service Extension for Authentication.

In this case. You can then use a symbolic name instead of the IP address. SMTP Port SMTP port of the mail server Auth Type Authentication type for connecting the iRMC S2 to the mail server: – None No authentication for the connection.Configure secondary mail server The Secondary SMTP Server Configuration group allows you to configure the secondary server (SMTP server).Email Alerting iRMC S2 web interface Secondary SMTP Server Configuration .Enable DNS for the iRMC S2” on page 311). 320 iRMC S2 .Secondary SMTP Server Configuration SMTP Server IP address of the secondary mail server I You can activate the Domain Name Service (DNS) for the iRMC S2 (see “DNS Settings .Alerting . Ê Click the Apply button to activate your settings. Figure 161: Email Alerting page . – SMTP AUTH (RFC 2554) Authentication according to RFC 2554: SMTP Service Extension for Authentication. the following information is required: Auth User Name User name for authentication on the mail server Auth Password Password for authentication on the mail server Confirm Password Confirm the password entered.

Email Alerting The Mail Format dependent Configuration group allows you to configure the mailformat-dependent settings. Subject Fixed subject for the alert mails. Otherwise. Only active for the Fixed Subject mail format (see page 330). Mail Format dependent Configuration Some entry fields are disabled depending on the mail format. Message Type of message (email).Email Format Configuration page (see page 330). iRMC S2 321 . The following email formats are supported: – – – – Standard Fixed Subject ITS-Format Fujitsu REMCS Format Figure 162: Email Alerting page. I If the string entered here contains an “@”.User <Name> Configuration . Active for all mail formats. the string is interpreted as a valid email address. “admin@<ip-address>” is used as the valid email address.iRMC S2 web interface Mail Format dependent Configuration Configure mail-format-dependent settings Alerting . Only active for the Fixed Subject mail format (see page 330). You specify the mail format for each user using the New User Configuration . From Sender identification iRMC S2.

Ê Click the Apply button to store your settings. REMCS Id This ID is an additional server ID. Only active for the ITS mail format (see page 330).Email Alerting iRMC S2 web interface Admin Name Name of the administrator responsible (optional). Only active for the ITS mail format (see page 330). Only active for the mail format Fujitsu REMCS-Format.Alerting . Admin Phone Phone number of the administrator responsible (optional). You have to enter the URL manually. similar to the serial number. 322 iRMC S2 . Only active for the Standard mail format. Server URL A URL under which the server is accessible under certain conditions.

Clicking on a user name opens the User “<name>” Configuration window (see page 326).1 iRMC S2 User .13.local user management on the iRMC S2” on page 323.13 User Management . 7. in which you can view or modify the settings for this user.iRMC S2 web interface User Management 7. iRMC S2 323 .Manage users The User Management entry contains the links to the pages for local user management as well as for the configuration of the directory service for global user management (LDAP configuration): – “iRMC S2 User . – “Directory Service Configuration (LDAP) .Configuring the directory service at the iRMC S2” on page 333.local user management on the iRMC S2 The iRMC S2 User page contains a table showing all the configured users: Each line contains the data for one configured user. The user names are implemented in the form of links. I User ID 1 (“null user”) is reserved for the IPMI standard and is therefore unavailable for user management on the iRMC S2.

User Management . Click this button to delete the associated user after confirming this choice. New User When you click this button.iRMC S2 User iRMC S2 web interface Figure 163: User Management page Delete The table of configured users includes a Delete button after each user entry. You can configure a new user here. the New User Configuration page opens (see page 325). 324 iRMC S2 .

iRMC S2 User 7. Figure 164: User Management .Configuring a new user The New User Configuration page allows you to configure the basic settings for a new user. In figure 164 you can see the configuration of a user with the name “User3”.1 New User Configuration .1.New User Configuration page iRMC S2 325 .iRMC S2 web interface User Management .13. You will find explanations of the fields and selection lists on the New User Configuration page as of page 327 under the description of the User “<name>” Configuration page.

13. Figure 165: User Management .1. In figure 165 you can see the configuration of the user created in figure 164.User “<name>” Configuration page 326 iRMC S2 .User configuration (details) The User “<name>” Configuration page allows you to view. I The user ID is shown in brackets after the user name.iRMC S2 User iRMC S2 web interface 7. modify and extend the settings for a user.2 User “<name>” Configuration .User Management .

User Description Enter a general description of the configured user here.Start a SMASH CLP shell” on page 393.Configuring user access data The User Information group allows you to configure the access data for the user.iRMC S2 web interface User Management . The following options are available: – SMASH CLP See section “Start a Command Line shell.. – Remote Manager See chapter “iRMC S2 via Telnet/SSH (Remote Manager)” on page 373. Figure 166: User Management . User Shell Select the desired user shell here.. . Password Enter the user password. Name Enter the name of the user. User Information User Enabled Disable this option to lock the user.User “<name>” Configuration page. Confirm Password Confirm the password by entering it again here.iRMC S2 User User Information . – IPMI Basic Mode iRMC S2 327 .

User Management .Assigning user privileges The Privileges / Permissions group allows you to configure the channel-specific user privileges. iRMC S2 web interface Privileges / Permissions .iRMC S2 User – IPMI Terminal Mode – None Ê Click the Apply button to activate your settings. you can also individually assign users the following channel-independent permissions: Configure User Accounts Permission to configure local user access data. In addition to the channel-specific permissions.User “<name>” Configuration page. Configure iRMC S2 Settings Permission to configure the iRMC S2 settings. Privilege / Permissions LAN Channel Privilege Assign a privilege group for a LAN channel to the user here: – – – – User Operator Administrator OEM Refer to section “User permissions” on page 62 for information on the permissions associated with the privilege groups. Figure 167: User Management . 328 iRMC S2 . Serial Channel Privilege Assign a privilege group for a serial channel to the user here: The same privilege groups are available as for LAN Channel Privilege.

User SSHv2 public key upload from file The User SSHv2 public Key uploag from file group allows you to load an user SSHv2 public key from a local file. Ê Click the Apply button to activate your settings.User “<name>” Configuration page. Figure 168: User Management . iRMC S2 329 . User SSHv2 public key upload from file For further details on SSHv2 public key authentication for iRMC S2 users see section “SSHv2 public key authentication for iRMC S2 users” on page 68. Remote Storage enabled Permission to use the Remote Storage functionality.iRMC S2 User Video Redirection enabled Permission to use Advanced Video Redirection (AVR) in “View Only” and “Full Control” mode.iRMC S2 web interface User Management .

User “<name>” Configuration page. you can make a number of settings in the Email Alerting . Email Configuration Email Enabled Specify whether the user is to be informed about system statuses by email.Configure user-specific email settings The Email Configuration group allows you to configure the user-specific settings governing the email format.iRMC S2 User iRMC S2 web interface Email Configuration .Mail Format dependent Configuration group (see page 321). Mail Format Depending on the selected email format. Figure 169: User Management . The following email formats are available: – – – – Standard Fixed Subject ITS-Format Fujitsu REMCS Format 330 iRMC S2 .User Management .

the email is sent to the second mail server.iRMC S2 User Preferred Mail Server Select the preferred mail server. – Primary Only the mail server which has been configured as the primary SMTP server (see page 319) is used as the preferred mail server. – Secondary Only the mail server which has been configured as the secondary SMTP server (see page 320) is used as the preferred mail server. iRMC S2 331 . Email Address Email address of recipient. for instance because the preferred mail server is not available. You can choose one of the following options: – Automatic If the email cannot be sent successfully immediately. I Errors sending email are recorded in the event log.iRMC S2 web interface User Management .

All The iRMC S2 notifies users of every event in this group which causes an entry to be made in the system event log. 332 iRMC S2 . Warning The iRMC S2 notifies users by email if an entry in the system event log is reported as Minor or Major or Critical. Ê Click the Apply button to activate your settings. The following settings are available for each event group: None The notification function is deactivated for this paging group. Critical The iRMC S2 notifies users by email if an entry in the system event log is reported as CRITICAL.User Management . I Every entry in the event log for the iRMC S2 is assigned to a particular paging group.iRMC S2 User iRMC S2 web interface Paging Severity Configuration Here you can configure system events about which an iRMC S2 user is to be informed by email.

Novell eDirectory and Open LDAP. &.iRMC S2 web interface User Management . >.13. <. =. |. I Currently.Directory Service Config. Figure 170: Directory Service Configuration page (LDAP configuration) iRMC S2 333 . \ . support for iRMC S2 LDAP access is provided for the following directory services: Microsoft Active Directory. 7. strings in LDAP: *. ~. !. you must configure the iRMC S2 appropriately in the Directory Service Configuration page. : I The following characters are reserved as metacharacters for search You must therefore not use these characters as components of Relative Distinguished Names (RDN).2 Directory Service Configuration (LDAP) Configuring the directory service at the iRMC S2 In order to perform global user management via a directory service (see page 83).

334 iRMC S2 .Directory Service Config. I If LDAP Enable is checked then the login information (see page 222) is always transferred with SSL encryption between the web browser and the iRMC S2. Always use SSL Login I This option is only relevant if LDAP is deactivated. V CAUTION! If the option Disable Local Login is activated and the connection to the directory service fails then it is no longer possible to log in at the iRMC S2. Only if you do not activate Always use SSL Login and LDAP is deactivated is a mask secured via Digest Authentication Login used. I You should only activate LDAP SSL Enable if a domain controller certificate is installed. iRMC S2 web interface LDAP Enable This option specifies whether the iRMC S2 can access a directory service via LDAP. LDAP SSL Enable If you check this option then data transfer between iRMC S2 and the directory server is SSL encrypted. Directory service access via LDAP is only possible if LDAP Enable has been activated. If you activate this option then the HTTP SSL-secured login page is always used even if LDAP is deactivated. Disable Local Login If you activate this option then all the local iRMC S2 user identifications are locked and only the user identifications managed by the directory service are valid. I LDAP SSL Enable has no influence on whether or not the iRMC S2 web interface pages are SSL-protected on opening.User Management .

refer to “Configuring iRMC S2 for Microsoft Active Directory” on page 336. depending on the directory service you select: – For Active Directory.iRMC S2 web interface User Management . iRMC S2 335 . refer to “Configuring iRMC S2 for Novell eDirectory / OpenLDAP” on page 340. – For eDirectory and Open LDAP.Directory Service Config. Directory Server Type Type of directory server used: The following directory services are supported: – Active Directory: Microsoft Active Directory – Novell: Novell eDirectory – OpenLDAP: OpenLDAP Ê Click the Apply button to activate your settings. Different input fields are provided.

1 Configuring iRMC S2 for Microsoft Active Directory After you have confirmed the Active Directory you have chosen by clicking Apply.2.Directory Service Config. 336 iRMC S2 .User Management . iRMC S2 web interface 7.13. the following variant of the Directory Service Configuration page is shown: Figure 171: Directory Service Configuration: Specifications for Microsoft Active Directory I The entries shown as examples in figure 171 refer to the examples and figures shown in section “iRMC S2 user management via Microsoft Active Directory” on page 107.

iRMC S2 web interface Proceed as follows: User Management . Ê Click Apply to activate your settings. LDAP Server 2 IP address or DNS name of the LDAP directory server which is maintained as the backup server and used as the directory server if LDAP Server 1 fails. Ê Complete your specifications in the Global Directory Service Configuration group: Figure 172: Global Directory Service Configuration: Specifications for Microsoft Active Directory LDAP Server 1 IP address or DNS name of the LDAP directory server that is to be used. Department Name The department name is used in the directory service in order to determine the user permissions and alert roles. Domain Name Complete DNS path name of the directory server.Directory Service Config. iRMC S2 337 . A user may have different permissions for the department X server than for the department Y server (see also figure 27 on page 90). Base DN Base DN is automatically derived from Domain Name.

Figure 173: Microsoft Active Directory: Directory Service Access Configuration LDAP Auth User Name User name the iRMC S2 uses to log onto the LDAP server. LDAP Auth Password Password the user specified under User Name uses to authenticate themselves on the LDAP server. iRMC S2 web interface Ê Configure the LDAP access data in the Directory Service Access Configuration group: I The settings that you make here are required for alerting in connection with global user identifications. the settings in the Directory Service Access Configuration group are not significant. Confirm Password Repeat the password you entered under LDAP Auth Password.Directory Service Config. 338 iRMC S2 . If alerting is not enabled.User Management .

Directory Service Config. Ê Click Apply to activate your settings. Figure 175: Directory Service Email Alert Configuration LDAP Email Alert Enable Enables global email alerting. but does not fully authenticate the user. I This test only checks the basic access data (“Is the LDAP server present?”. LDAP Alert Table Refresh [Hours] Defines the interval at which the email table is regularly updated (see page 158). A value of “0” means that the table is not updated regularly.iRMC S2 web interface User Management . Ê Click Apply to activate your settings. Test LDAP Access Checks the access data to the LDAP directory server and shows the LDAP status as the result (see figure 174). “Is the user configured?”). iRMC S2 339 . Ê Configure the settings for global email alerting in the Directory Service Email Alert Configuration group. Figure 174: Microsoft Active Directory: Status of the connection to the LDAP server Ê Click Reset LDAP Status to reset the status display.

I The Directory Service Configuration page has an identical structure for both Novell eDirectory and OpenLDAP. Figure 176: Global Directory Service Configuration: Specifications for Novell eDirectory / Open LDAP I The entries shown as examples in figure 176 refer to the examples and figures shown in section “iRMC S2 user management via Novell eDirectory” on page 120.2 Configuring iRMC S2 for Novell eDirectory / OpenLDAP After you have confirmed you choice of Novell or OpenLDAP by clicking Apply. 340 iRMC S2 .User Management .Directory Service Config. the following variant of the Directory Service Configuration page is shown.2.13. iRMC S2 web interface 7.

iRMC S2 web interface Proceed as follows: User Management .Directory Service Config. A user may have different permissions for the department X server than for the department Y server (see also figure 27 on page 90). The directory service needs the department name in order to determine the user permissions. Department Name Department name. Ê Complete your specifications in the Global Directory Service Configuration group: Figure 177: Global Directory Service Configuration: Specifications for Microsoft Active Directory LDAP Server 1 IP address or DNS name of the LDAP directory server that is to be used. This DN forms the starting point for LDAP searches. LDAP Server 2 IP address or DNS name of the LDAP directory server which is maintained as the backup server and used as the directory server if LDAP Server 1 fails. iRMC S2 341 . Base DN The Base DN is the fully distinguished name of the eDirectory or Open LDAP server and represents the tree or subtree that contains the OU (Organizational Unit) iRMCgroups.

you do not need to specify the Base DN under Principal User DN.e. iRMC S2 web interface Groups directory as sub-tree from base DN Pathname of the organizational unit iRMCgroups as a subtree of Base DN (Group DN Context). Append Base DN to Principal User DN If you activate this option. under which the iRMC S2 queries the permissions of the iRMC S2 users from the LDAP server.User Management . i. User Search Context Pathname of the organizational unit Users as a subtree of Base DN (User Search Context). Ê Click Apply to activate your settings.Directory Service Config. Principal User DN Fully distinguished name. Confirm Password Repeat the password you entered under LDAP Auth Password. 342 iRMC S2 . Ê Configure the LDAP access data in the Directory Service Access Configuration group: Figure 178: Microsoft Active Directory: Directory Service Access Configuration LDAP Auth Password Password the Principal User uses to authenticate themselves on the LDAP server. In this event. the Base DN is used that you specified under Base DN in the Global Directory Service Configuration group. Bind DN Bind DN shows the principal user DN used for LDAP authentication. the full description of the object path and attributes of the generic iRMC S2 user ID (principal user).

If you inadvertently specify and activate an invalid search filter.Directory Service Config. an additional field User Login Search Filter appears containing the standard login search filter. Enhanced User Login Enhanced flexibility when users log in. If you select Enhanced User Login and activate it with Apply. You can modify the standard filter by specifying another attribute in place of “cn=”. V CAUTION! Only activate this option if you are familiar with the LDAP syntax. iRMC S2 343 . users can only log in to the iRMC under a global login after the Enhanced User Login option has been deactivated. Figure 179: LDAP search filter for “Enhanced User Login” At login. V Only activate this option if you are familiar with the LDAP syntax. All global logins are then permitted to log into the iRMC S2 which meet the criteria of this search filter.iRMC S2 web interface User Management . users can only log in to the iRMC S2 under a global login after the Enhanced User Login option has been deactivated. the placeholder “%s” is replaced by the associated global login. If you inadvertently specify and activate an invalid search filter.

Ê Click Apply to activate your settings.Directory Service Config. Ê Click Apply to activate your settings.User Management . I This test only checks the basic access data (“Is the LDAP server present?”. but does not fully authenticate the user. 344 iRMC S2 . iRMC S2 web interface Test LDAP Access Checks the access data to the LDAP directory server and shows the LDAP status as the result (see figure 174). Figure 180: eDirectory / OpenLDAP: Status of the connection to the LDAP server Ê Click Reset LDAP Status to reset the status display. “Is the user configured?”). Ê Configure the settings for global email alerting in the Directory Service Email Alert Configuration group. LDAP Alert Table Refresh [Hours] Defines the interval at which the email table is regularly updated (see page 158). Figure 181: Directory Service Email Alert Configuration LDAP Email Alert Enable Enables global email alerting. A value of “0” means that the table is not updated regularly.

Redirecting the console The following pages are available for console redirection: – “BIOS Text Console .1 BIOS Text Console Configure and start text console redirection The BIOS Text Console page allows you to configure and start text console redirection. 7. – “Advanced Video Redirection . iRMC S2 345 .Start Advanced Video Redirection (AVR)” on page 356.Configure and start text console redirection” on page 345.iRMC S2 web interface Console Redirection 7.14 Console Redirection .14. I Text console redirection can also be configured in the BIOS (see section “Configuring text console redirection via LAN using the BIOS/TrustedCore Setup program” on page 44).

BIOS Text Console iRMC S2 web interface Figure 182: BIOS Text Console page 346 iRMC S2 .Console Redirection .

iRMC S2 347 .see section “Text console redirection while the operating system is running” on page 354: Standard Console redirection is terminated after the BIOS POST phase. Enhanced Console redirection continues to be available after the BIOS POST phase.BIOS Text Console 7.iRMC S2 web interface Console Redirection .1 BIOS Console Redirection Options Configure text console redirection BIOS Console Redirection Options allows you to configure text console redirection.1. I The operating system can also permit text console redirection irrespective of the settings in the BIOS. Figure 183: BIOS Text Console page .14. Console Redirection Mode This setting affects the behavior of console redirection while the operating system is running (after the BIOS POST phase has completed) .BIOS Console Redirection Options Console Redirection This option allows you to enable/disable console redirection.

CTS/RTS (Hardware) Flow control is handled by the hardware. 38400. 9600. Serial Port Baud Rate The following baud rates can be set: 1200. VT100 8Bit. VT100+. Serial 2. Terminal Emulation The following terminal emulations are available: VT100 7Bit. Serial 1 must be set.Console Redirection .BIOS Text Console Console Redirection Port Two serial ports are available: Serial 1. only the connection over the null modem cable works. VT-UTF8 Serial 1 Multiplexer Check the consistency of the multiplexer settings: – Serial: System – LAN: iRMC S2 Ê Click the Apply button to activate your settings. PC-ANSI 8 Bit. 115200. XON/XOFF (Software) Flow control is handled by the software. 2400. iRMC S2 web interface I If console redirection is to be performed via LAN. If Serial 2 is selected. 348 iRMC S2 . 57600. PC-ANSI 7Bit. 19200. 4800. Serial Port Flow Control The following settings are possible: None Flow control is disabled.

I Text 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.14. Ê Click the Start Console Redirection button to start text console redirection function.iRMC S2 web interface Console Redirection . The Java applet for text console redirection is started (see figure 185 on page 350): iRMC S2 349 . Figure 184: Start text console redirection via Serial over LAN (SOL).BIOS Text Console 7.2 Text Console Redirection (via Serial over LAN) Start text console redirection Text Console Redirection (via Serial Over LAN) allows you to start text console redirection.1.

You are then prompted to enter your iRMC S2 user name and password: Figure 186: Power management and text console redirection .Console Redirection .BIOS Text Console iRMC S2 web interface Figure 185: Window for power management and text console redirection (before login) Ê Click the Logon button to log in to the iRMC S2.Login window 350 iRMC S2 .

The window for power management and text console redirection is then displayed: Console redirection bar Status bar Power management bar Console area Login bar Figure 187: Window for power management and text console redirection iRMC S2 351 .iRMC S2 web interface Console Redirection .BIOS Text Console Ê Enter your user name and password and click Login to confirm.

The Login and Logout buttons allow you to log in to and log out of the iRMC S2. Console redirection bar The Enter Console and Leave Console buttons in the console redirection bar allow you to show or hide the display in the console area. Power management bar The power management bar provides information on the power status of the managed server. the status bar provides information on the status of the console redirection (online/offline).Console Redirection . You can update the display by clicking the Status button.BIOS Text Console iRMC S2 web interface The elements of the console redirection window are explained below: Login bar The login bar shows the IP address and current firmware version of the iRMC S2. 352 iRMC S2 . Status bar The status bar shows the IP address of the iRMC S2 and the port number used for console redirection. In addition. Console area The console area contains the display from the redirected text console. You do not need to be connected with the console to do this. The Command drop-down list allows you to select and launch an IPMI command for power management of the managed server (see page page 353).

Completely restarts the server (cold start).BIOS Text Console You are then connected to the console and can execute the required command. Powers the server down completely and then powers it up again after approximately 5 seconds. iRMC S2 353 . IPMI command Power On Power Off Reset Power Cycle Shutdown Explanation Switches the server on. Switches the server off. Console Redirection . click Leave Console. either by entering it directly in the console area or by clicking it in the Command drop-down list (IPMI commands only): Enter SAC command directly. (No confirmation prompt!) or Select IPMI command and click. A AAA Figure 188: Entering SAC or IPMI commands at the console.iRMC S2 web interface Ê Click Enter Console. Graceful shutdown and power off. Ê To close the connection to the console. regardless of the status of the operating system.

you can continue to use console redirection after the BIOS POST phase.0” manual. refer to the “RemoteView 5.3 Text console redirection while the operating system is running Depending on the operating system used on the managed server. For further information on PRIMERGY ServerView Suite diagnosis.BIOS Text Console iRMC S2 web interface 7. the Windows Server 2003 SAC console is transferred: Figure 189: Windows Server 2003 SAC console 354 iRMC S2 . If the managed server starts the PRIMERGY ServerView Suite diagnosis software.Console Redirection . While the operating system is booting. you can operate PRIMERGY ServerView Suite diagnosis using console redirection.1. DOS I Condition: The BIOS setting for console redirection mode must be set to Enhanced (see the section “BIOS Text Console .14.Configure and start text console redirection” on page 345). No further settings are necessary. Windows Server 2003 Windows Server 2003 handles console redirection automatically after the POST phase.

BIOS Text Console You must configure a Linux operating system in such a way that it handles console redirection after the POST phase. Settings required The settings may differ between program versions.<baud-rate> console=tty0 iRMC S2 355 . you have complete remote access.conf: console=ttyS0.lst : console=ttyS0.iRMC S2 web interface Linux Console Redirection .<baud-rate> console=tty0 SuSE Insert the following kernel boot parameter in the file /boot/grub/menu. Once it has been configured. SuSe and RedHat Add the following line to the end of the file /etc/inittab: xx:12345:respawn:/sbin/agetty <baud-rate> ttyS0 RedHat Insert the following kernel boot parameter in the file /etc/grub.

Console Redirection . I In order to use the iRMC S2 function Advanced Video Redirection. AVR can be used by two users simultaneously.2 Advanced Video Redirection Start Advanced Video Redirection (AVR) The Advanced Video Redirection page allows you to start graphical console redirection.AVR iRMC S2 web interface 7.” on page 241). The AVR functionality is made available with a Java applet. The “Advanced Video Redirection” feature redirects graphical output from the managed server to the remote workstation and assigns keyboard and mouse input from the remote workstation to the managed server so that you can access the managed server from the remote workstation as if you were working locally.14. 356 iRMC S2 . One user has full control over the server (full-control mode) and the other can only passively observe keyboard and mouse operation of the server (view-only mode). you require a license key (see “Load license key onto the iRMC S2.

AVR Figure 190: Advanced Video Redirection page iRMC S2 357 .iRMC S2 web interface Console Redirection .

namely the most recently created screenshot. A maximum of one video screenshot is stored in the firmware of the iRMC S2.in Windows. The following actions are available by clicking on one of the buttons displayed: View Screenshot (This only appears if a video screenshot has been stored. – delete the screenshot stored in the iRMC S2 firmware. Delete Screenshot (This only appears if a video screenshot has been stored.) The video screenshot stored in the iRMC S2 firmware is deleted after you have confirmed that you wish to do so. these are typically watchdog events or "bluescreens" on the managed server.Console Redirection .) A thumbnail of the screenshot is shown in the ASR Screenshot group. Preview Screenshot (This only appears if a video screenshot has been stored.AVR Creating an ASR screenshot The ASR Screenshot page allows you to iRMC S2 web interface – take a screenshot of the current VGA screen on the managed server (video screenshot) and store it in the firmware of the iRMC S2.) The screenshot is shown in a separate browser window. 358 iRMC S2 . Make Screenshot Takes a new video screenshot. Figure 191: Creating an video screenshot I A video screenshot is automatically created on ASR&R events . – view the screenshot stored in the iRMC S2 firmware.

(two active AVR sessions) Disconnect If you click Disconnect. If no AVR session is currently active then the AVR Active Session Table is not displayed. a Disconnect button is displayed for each Session. If two AVR Sessions are currently active. Figure 193: Video Redirection Options None No USB port will be disabled. Video Redirection Options .Disable USB Port allows you to specify which USB ports are to be disabled on the managed server for the duration of the AVR session.Deactivating USB ports on the managed server for the duration of the AVR session I This function is not supported for all PRIMERGY servers.iRMC S2 web interface Console Redirection .Show current AVR sessions The AVR Active Session Table lists the currently active AVR sessions. choose Exit from the Extras menu in the AVR window (see page 184). iRMC S2 359 .AVR AVR Active Session Table . To close your own session. I You can only close AVR sessions of other users with the Disconnect button. Video Redirection Options . Figure 192: AVR Active Session Table . a confirmation dialog box appears in which you can close the AVR session to the left of the button.

AVR iRMC S2 web interface Front USB Only the USB port on the front of the server will be disabled. you can configure: – that the local monitor can be switched on and off from the remote workstation. Ê Click the Apply button to activate your settings.Local Monitor 360 iRMC S2 . – that the local monitor shuts down automatically for the duration of the AVR session when an AVR session is started.Power up/down options for local server monitor The status of the local monitor on the managed server is shown under Local Monitor (see section ““Local Monitor Off” function” on page 172). Disable All All USB ports of the server will be disabled. Figure 194: Advanced Video Redirection page .Console Redirection . Local Monitor . In addition. Rear USB Only the USB port on the back of the server will be disabled.

If you activate this option.AVR Enable Local Monitor Off This option allows you to activate the following options: – In full-control mode of an AVR session. the local monitor is automatically switched off for the duration of the session when an AVR session is started. see page 184). – For users with administrator or OEM permissions. After the AVR session is closed. I This option only takes effect if Enable Local Monitor has been activated. the local Automatic Local Monitor Off when AVR is started monitor is automatically switched on again when the AVR session is closed. iRMC S2 361 . you can switch the local monitor on and off (AVR Extras menu. I If no concurrent session with Local Monitor Off is active. the local monitor is automatically switched off again if a new. Figure 195: Advanced Video Redirection page . The local monitor is switched on again automatically when all AVR sessions have been closed. the local monitor is automatically switched on again if no concurrent session with Local Monitor Off is active.Local Monitor On/Off – You can also configure that the local monitor is switched off automatically for the duration of an AVR session when an AVR session is started (see the Automatic Local Monitor Off when AVR is started option). Ê Click the Apply button to activate your settings. concurrent AVR session is started. This also allows the local monitor to be switched on and off (see figure 195).iRMC S2 web interface Console Redirection . the toggle button Turn Off / Turn On is also enabled. I Parallel AVR sessions: Even if you switch on the local monitor during your AVR session (in the AVR menu Extras or with the Turn On button).

The Java applet for Advanced Video Redirection is started. and you are asked whether you want to take full control of the managed server using AVR or whether you wish to remain in the view-only mode.AVR Video Redirection .Console Redirection . The Java applet shows the AVR window in view-only mode. Figure 197: AVR window (view-only mode) 362 iRMC S2 .Starting AVR You start AVR under Video Redirection.Local Monitor Ê Click the Start Video Redirection or Start Video Redirection (Java Web-Start) button to start a second AVR session. iRMC S2 web interface Figure 196: Advanced Video Redirection page .

Users should agree among themselves what modes they are to use in their sessions. If you have decided to actively use AVR.iRMC S2 web interface Console Redirection . the window for active use of AVR is opened (see figure 198). Figure 198: AVR window (full-control mode) The menus of the AVR window and the integrated special keys are described in chapter “Advanced Video Redirection (AVR)” on page 167. In this case. Ê Click Cancel to remain in view-only mode. iRMC S2 363 .AVR Ê Click OK to take over full control of the managed server. I This places the currently active AVR session in view-only mode. the following window appears. with which you can log into the managed server.

AVR iRMC S2 web interface The two active AVR sessions are shown as follows on the Advanced Video Redirection page: Figure 199: AVR window with two active AVR sessions Disconnect If you click Disconnect. 364 iRMC S2 .Console Redirection . choose Exit from the Extras menu in the AVR window (see page 184). I You can only close AVR sessions of other users with the Disconnect button. To close your own session. a confirmation dialog box appears in which you can close the AVR session to the left of the button.

iRMC S2 web interface Console Redirection .AVR The following window appears if the managed server is powered down: Figure 200: AVR window when the server is powered down iRMC S2 365 .

The source for the virtual drive can be a physical drive (floppy disk drive CD-ROM/DVD-ROM) or an ISO image (image file). Remote storage connections via applet and Remote Storage Server are not possible simultaneously. I In order to use the iRMC S2 function Remote Storage.g.15 Remote Storage The Remote Storage feature provides the managed server with a “virtual” drive which is physically located elsewhere in the network. The image file may also be a network drive (with drive letter. I Parallel remote storage connections: The following are possible concurrently: – either up to two Remote Storage connections to virtual drives at the remote workstation (if the connection is established over the AVR Java applet) or – one Remote Storage connection to a Remote Storage server. You can make the remote storage media available as follows: – As a physical drive or image file at the remote workstation (see page 192). The Remote Storage page allows you to display information on the status of the current remote storage connections and establish the connection to a remote storage server. – As an image file centrally in the network via a remote storage server (see page 206). e. “D:” for drive D).Remote Storage iRMC S2 web interface 7. you require a license key (see page 243). 366 iRMC S2 .

Disconnect Click the Disconnect button to terminate the connection to the remote storage server. Connect Click the Apply button to save the remote storage server’s IP address or DNS name and establish the connection to the remote storage server. I Before it is possible to establish the connection to the remote storage server the remote storage server must be installed and running. iRMC S2 367 .iRMC S2 web interface Remote Storage Figure 201: Remote Storage page IP Address or DNS Name Here you enter the IP address or DNS name of the computer on which a remote storage server is installed. Apply Click the Apply button to save the remote storage server’s IP address or DNS name.

This is known as the Remote Manager. You can call the Remote Manager from the iRMC S2 web interface as follows: – Use the iRMC S2 SSH Access link to initiate an SSH (Secure Shell) encrypted Telnet connection to the iRMC S2.Configuring ports and network services” on page 305). Requirements on the managed server Access via Telnet must be activated for the iRMC S2 (see the section “Ports and Network Services . – Use the iRMC S2 Telnet Access link to initiate an unencrypted Telnet connection to the iRMC S2.16 Operating iRMC S2 via Telnet/SSH (Remote Manager) A Telnet/SSH-based interface is available for the iRMC S2. The alphanumeric user interface of the Remote Manager provides you with access to system and sensor information. I Maximum number of parallel sessions: – Telnet: up to 4 – SSH: up to 2 – Telnet and SSH in total: up to 4 Operation of the iRMC S2 using the Remote Manager is described in chapter “iRMC S2 via Telnet/SSH (Remote Manager)” on page 373. I Access via the Telnet protocol is deactivated by default for security reasons. power management functions and the error event log. 368 iRMC S2 . You can also start text console redirection and a SMASH CLP shell.Telnet / SSH access (Remote Manager) iRMC S2 web interface 7. as passwords are transmitted in plain text.

click on the link iRMC S2 SSH Access (SSH) or iRMC S2 Telnet Access (Telnet). Ê In the navigation bar. The Java applet for the SSH or Telnet connection is started and the following window is displayed (in this case using the example of an SSH connection): Figure 202: Establishing an SSH connection to the iRMC S2 iRMC S2 369 . the display for an SSH connection is shown below.iRMC S2 web interface Telnet / SSH access (Remote Manager) Establishing an SSH/Telnet connection and logging into the Remote Manager I If the screen displays for SSH and Telnet connections differ only with respect to the connection-specific information displayed.

click Connect. – Logging into the Remote Manager over an SSH connection I If the host key of the managed server is not yet registered at the remote workstation. you are requested to enter the user name and password. The main menu of the Remote Manager is then displayed (see figure 205 on page 372). The following login window is displayed: Figure 203: SSH connection: Logging in to the Remote Manager Ê Enter your user name and password and confirm your entries by clicking Login. 370 iRMC S2 . iRMC S2 web interface As soon as the connection to the iRMC S2 has been established.Telnet / SSH access (Remote Manager) Ê In the connection bar. the SSH client issues a security alert with suggestions on how to proceed.

the login window is shown with or without system information (see page 378). The main menu of the Remote Manager is then displayed (see figure 205 on page 372). started at some point on the system.iRMC S2 web interface Telnet / SSH access (Remote Manager) – Logging into the Remote Manager over a Telnet connection The Remote Manager login window is displayed: Figure 204: Telnet connection: Logging in to the Remote Manager I Depending on whether ServerView agents have already been Ê Enter your user name and password and confirm your entries by pressing [Enter]. iRMC S2 371 .

372 iRMC S2 .Telnet / SSH access (Remote Manager) iRMC S2 web interface Figure 205: Main menu of the Remote Manager Closing a Telnet/SSH connection Ê Close the connection to the Remote Manager by clicking the Disconnect button in the connection bar of the Remote Manager window or by pressing the [0] key in the main menu of the Remote Manager (see figure 205).

I Maximum number of parallel sessions: – Telnet: up to 4 – SSH: up to 2 – Telnet and SSH in total: up to 4 Requirements on the managed server Access via Telnet must be activated for the iRMC S2 (see the section “Ports and Network Services . you can correct any nonstandard value for the management port after the Remote Management Frontend has been started. You can call the Remote Manager over the following interfaces: – iRMC S2 web interface (see page 368) – any Telnet/SSH client – ServerView Remote Management Frontend The iRMC S2 supports secure connections over SSH (Secure Shell). the Remote Management Frontend works with the default value. Since a connection is not automatically established when the Remote Management Frontend is started.Configuring ports and network services” on page 305). In principle. It is nevertheless recommended that the iRMC S2 web interface or the ServerView Remote Management Frontend (referred to below simply as the Remote Management Frontend) be used. any Telnet/SSH client that interprets VT100 sequences can be used to access the iRMC S2. The Remote Manager interface is identical for Telnet and SSH connections.8 iRMC S2 via Telnet/SSH (Remote Manager) A Telnet-based interface is available for the iRMC S2. as passwords are transmitted in plain text. This is known as the Remote Manager. iRMC S2 373 . I Access via the Telnet protocol is deactivated by default for security reasons. I Since the ServerView Operations Manager does not know the value of the management port.

374 iRMC S2 .Operating the iRMC S2 using the Remote Management Frontend 8.1 Operating the iRMC S2 using the ServerView Remote Management Frontend You will find detailed information on establishing a connection to the iRMC S2 using the Remote Management Frontend and on the work environment of the Remote Management Frontend in the “PRIMERGY ServerView Suite ServerView Remote Management Frontend” manual.

1 Operating Remote Manager Operation of Remote view is described on the basis of the example in figure 206. iRMC S2 375 ... which shows an excerpt from the main menu of the Remote Manager. The end of the section also provides a brief overview of SMASH CLP. operating 8. e. Figure 206: Operating the Remote Manager Ê Select the required menu item by entering the number or letter which precedes the menu item. Functions that the user is not permitted to use are indicated by a dash (-) and functions that are not available are indicated by an asterisk (*).Remote Managerr .g.2 Remote Manager This section describes operation of the iRMC S2 from the Remote Manager and the various functions in detail.2.Telnet/SSH . Ê Press [0] or the key combination [Ctrl] [D] to close the Remote Manager. 8. An appropriate event will be written to the event log. “c” for “Change password”.

2 Overview of menus The Remote Manager menu for the iRMC S2 has the following structure: ● System Information – Chassis Information – Mainboard Information – OS and SNMP Information ● Power Management – Immediate Power Off – Immediate Reset – Power Cycle – Power on – Graceful Power Off (Shutdown) – Graceful Reset (Reboot) ● Enclosure Information – System Event-Log – View System Event-Log (text. newest first) – View System Event-Log (text.2. newest first) – Dump System Event-Log (raw. oldest first) – Dump System Event-Log (raw.Remote Manager 8. oldest first) – View System Eventlog Information – Clear System Event-Log – Temperature – Voltages/Current – Fans – Power Supplies – Door Lock – CPU Sensors 376 iRMC S2 .Overview of menus Telnet/SSH .

Telnet/SSH .Remote Manager – Component Status (Lightpath) – List All Sensors ● Overview of menus Service Processor – Configure IP Parameters – List IP Parameters – Toggle Identify LED – Reset iRMC S2 (Warm reset) – Reset iRMC S2 (Cold reset) ● ● ● ● Change password Console Redirection (EMS/SAC) Start a Command Line shell Console Logging iRMC S2 377 .

2. the SSH client issues a security alert with suggestions on how to proceed. the login window of the Remote Manager (Telnet/SSH window) is displayed at the terminal client at the remote workstation.Logging in Telnet/SSH .Remote Manager 8. I When logging in over an SSH connection: If the host key of the managed server is not yet registered at the remote workstation. the login window is shown with or without system information.3 Logging in As soon as a connection to the iRMC S2 has been established. Depending on whether ServerView agents have already been started at some point on the system. Figure 207: Remote Manager: Login window (with system information) 378 iRMC S2 .

Ê In order to be able to use the Remote Manager.Telnet/SSH . You can terminate the login process at any time using [Ctrl][D]. the System Name) are only shown for servers and only if the server is configured appropriately. you must log in with a user name and a password. Then an appropriate event will be written to the Event log and the relevant main menu of the Remote Manager displayed (see section “Main menu of the Remote Manager” on page 380). Some details (e.Remote Manager Logging in Figure 208: Remote Manager: Login window (without system information) The Remote Manager window contains information on the affected PRIMERGY system.g. iRMC S2 379 . This information identifies the server and indicates its operating status (Power Status).

Remote Manager 8.Main menu Telnet/SSH ... (see section “Power Management” on page 385). Power the server up or down..2.4 Main menu of the Remote Manager Figure 209: Remote Manager: Main menu window The main menu of the Remote Manager provides the following functions: System Information. View information on the managed server (see section “System Information Information on the managed server” on page 384).. Table 9: Main menu of the Remote Manager 380 iRMC S2 . Power Management.

identification LED and iRMC S2 reset” on page 391).) (see section “Enclosure Information System event log and status of the sensors” on page 387). check error and event messages from the error log and event log (temperature. Change password Console Redirection (EMS/SAC) Start a Command Line shell. Configure the iRMC S2 (e. e... Service Processor....Start text console redirection” on page 392). Redirect output of messages to the text console (see section “Console Logging Redirect message output to the text console (serial)” on page 394). fan.Remote Manager Main menu Enclosure Information. Change the password (see section “Change the password” on page 383). .Start a SMASH CLP shell” on page 393). Text console redirection (see section “Console Redirection (EMS/SAC) . Request information on the current system status.. update firmware or change IP address) (see section “Service processor .g. Console Logging Table 9: Main menu of the Remote Manager iRMC S2 381 ...g. etc.Telnet/SSH . Start a command line shell (see section “Start a Command Line shell.IP parameters.

Clear System Eventlog Sensor overviews (Temperature.. ....View/Dump System Eventlog System Eventlog .. Power Management..... Console Logging X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Table 10: Permissions to use the Remote Manager menus 382 iRMC S2 Remote Storage Enabled Administrator Operator OEM User . Service Processor.Toggle Identify LED Service Processor.Reset iRMC S2 (warm/cold reset) Change Password Console Redirection (EMS/SAC) Start a command Line shell. Remote Manager menu items Permitted with IPMI privilege level Required permission Configure iRMC S2 Settings Video Redirection Enabled Configure User Accounts System Information.5 Required user permissions table 10 provides an overview of the user permissions which are required in order to use the individual Remote Manager functions...Remote Manager 8. .... Fans .. Enclosure Information System Eventlog .List IP Parameters Service Processor..Required permissions Telnet/SSH .. .. .) Service Processor.Configure IP Parameters Service Processor.2.

Remote Manager Change the password 8.6 Change the password The Change password menu item allows a user with the privilege Configure User Accounts (see page 62) to change their own password or the passwords of other users.2.Telnet/SSH . iRMC S2 383 .

..System Information Telnet/SSH .2. Information on the operating system and the ServerView version of the managed server and on the SNMP settings. Information on the mainboard of the managed server and its product data.7 System Information Information on the managed server The following menu appears if you choose System Information. from the main menu: Figure 210: Remote Manager: System Information window The submenu contains the following functions: Chassis Information Mainboard Information OS and SNMP Information Information on the chassis of the managed server and its product data. Table 11: System Information menu 384 iRMC S2 .Remote Manager 8.

.Remote Manager Power Management 8..2.8 Power Management The following menu appears if you choose Power Management.Telnet/SSH . from the main menu: Figure 211: Remote Manager: Power Management window iRMC S2 385 .

regardless of the status of the operating system. This menu item is only available if ServerView agents are installed and signed onto the iRMC S2 as “Connected”. Completely restarts the server (cold start).Power Management The submenu contains the following functions: Immediate Power Off Immediate Reset Power Cycle Power On Graceful Power Off (Shutdown) Telnet/SSH . This menu item is only available if ServerView agents are installed and signed onto the iRMC S2 as “Connected”. Powers the server down completely and then powers it up again after a configured period.Remote Manager Powers the server down. Graceful Reset (Reboot) Table 12: Power Management menu 386 iRMC S2 . Graceful shutdown and reboot. Graceful shutdown and power off. Switches the server on. regardless of the status of the operating system.

.9 Enclosure Information System event log and status of the sensors The following menu appears if you choose Enclosure Information.Telnet/SSH . from the main menu: Figure 212: Remote Manager: Enclosure Information window iRMC S2 387 ..Remote Manager Enclosure Information 8.2.

Display information on the fans and their status. Display information on the voltage and current sensors and their status. Display information on whether the front panel or housing are open. Localize the processors of the server. Table 13: Enclosure Information menu 388 iRMC S2 .Remote Manager Call the System Eventlog menu (see the section “System Eventlog” on page 389). Display information on the power supplies and their redundancy status. Display detailed information on all sensors. Display detailed information on all sensors that have a PRIMERGY diagnostic LED. Display information on the temperature sensors and their status.Enclosure Information The submenu contains the following functions: System Eventlog Temperature Voltages/Current Fans Power Supplies Door Lock CPU Sensors Component Status List All Sensors Telnet/SSH .

Remote Manager System Eventlog Enclosure Information The following menu appears if you select System Eventlog from the Enclosure Information. submenu: Figure 213: Remote Manager: System Eventlog window iRMC S2 389 .Telnet/SSH ...

Enclosure Information The submenu contains the following functions: View System Eventlog (text, newest first) View System Eventlog (text, oldest first)

Telnet/SSH - Remote Manager

The contents of the Event log are output to screen in a readable form and in chronological order (the most recent entry first). The contents of the Event log are output to screen in a readable form and in reverse chronological order (the oldest entry first).

Dump System Eventlog The contents of the Event log are dumped in (raw, newest first) chronological order (the most recent entry first). Dump System Eventlog The contents of the Event log are dumped in reverse (raw, oldest first) chronological order (the oldest entry first). View System Eventlog Information Clear System Eventlog Display information on the event log. Clear the contents of the event log.

Table 14: System Eventlog menu

390

iRMC S2

Telnet/SSH - Remote Manager

Service Processor

8.2.10 Service processor - IP parameters, identification LED and iRMC S2 reset
The following menu appears if you choose Service Processor... from the main menu:

Figure 214: Remote Manager: Service Processor window

iRMC S2

391

Console Redirection (EMS/SAC) The submenu contains the following functions: Configure IP Parameters

Telnet/SSH - Remote Manager

Configure the IP address, subnet mask and default gateway. You can also specify whether DHCP is to be activated Display the IP settings. Switch the PRIMERGY identification LED on/off. Reset the iRMC S2. The connection is closed. Only the interfaces are re-initialized. Reset the iRMC S2. The connection is closed. The entire iRMC S2 is re-initialized.

List IP Parameters Toggle Identify LED Reset iRMC S2 (warm reset) Reset iRMC S2 (cold reset)

Table 15: Service Processor menu

I It is recommended that you reboot the server after a Reset iRMC S2 (Cold
Reset) or Reset iRMC S2 (Warm Reset) (see page 265).

8.2.11 Console Redirection (EMS/SAC) Start text console redirection
You can start console redirection with the Console Redirection (EMS/SAC) item from the main menu.

I Text-based console redirection only works over the LAN with Serial 1.
If console redirection is also to be used while the operating system is running, the Serial 1 Multiplexer must be set to System.

I Use the keyboard shortcut "<ESC>(" or "~." (tilde dot) to exit the text
console. It is possible that only one of these options will work, depending on the type of PRIMERGY server used.

392

iRMC S2

Telnet/SSH - Remote Manager

Start a Command Line shell...

8.2.12 Start a Command Line shell... Start a SMASH CLP shell
Start a Command Line shell... in the main menu allows you to start a SMASH CLP shell. SMASH CLP stands for “Systems Management Architecture for Server Hardware Command Line Protocol”. This protocol permits a Telnet- or SSHbased connection between the management station and the managed server. For further details on SMASH CLP, please refer to section “Command Line Protocol (CLP)” on page 397. When you select (s) Start a Command Line shell... from the main menu, the following window appears:

Figure 215: Remote Manager: Start a SMASH CLP shell... window

Ê Choose (1) Start a SMASH CLP shell... to start the SMASH CLP shell.

iRMC S2

393

Console Logging

Telnet/SSH - Remote Manager

8.2.13 Console Logging - Redirect message output to the text console (serial)
The Console Logging item in the main menu allows you to redirect message output (logging) to the text console (serial interface). When you select (l) Console Logging from the main menu, the following window appears:

Figure 216: Remote Manager: Console Logging

The submenu contains the following functions: Change Logging Run State Show and change the logging run state. For a more detailed description, see “Console Logging Run State Menu” on page 395 Clear the console logging buffer. Show the console log (in fast mode)

Clear Console Logging Buffer Replay Console (Fast mode)

Replay Console (Continuous mode) Show the console log (in continuous mode)
Table 16: Console Logging menu

394

iRMC S2

Telnet/SSH - Remote Manager Console Logging Run State Menu

Console Logging

Figure 217: Remote Manager: Console Logging Run State Menu

iRMC S2

395

Console Logging

Telnet/SSH - Remote Manager

The Console Logging Run State Menu provides the following functions: Start Console Logging Stop Console Logging Toggle to Text Mode Start output of messages to the text console. Stop output of messages to the text console. Switch to text mode. All escape sequences are filtered out before messages are output to the console.

Toggle to Normal Mode Switch to normal mode. In normal mode, only the following escape sequences are filtered out before messages are output to the console: <ESC>( <ESC>stop <ESC>Q <ESC>R<ESC>r<ESC>R <ESC>^ This means that color, pseudo-graphics, etc. can also be represented to a limited extent.
Table 17: Console Logging Run State menu

396

iRMC S2

Telnet/SSH - Remote Manager

Command Line Protocol (CLP)

8.2.14 Command Line Protocol (CLP)
The iRMC S2 supports various text-based user interfaces, known as user shells, which can be configured differently for individual users. The System Management Architecture for Server Hardware (SMASH) initiative defines a number of specifications with the following objectives: – Provision of standardized interfaces for managing heterogeneous computer environments, – Provision of an architecture framework with uniform interfaces, hardware and software discovery, resource addressing and data models. You can find further information on SMASH under the following link: http://www.dmtf.org/standards/smash SMASH CLP syntax SMASH CLP specifies a common command line syntax and message protocol semantics for managing computers on the Internet and in enterprise and service provider environments. You can find detailed information on SMASH CLP in the DMTF document “Server Management Command Line Protocol Specification (SM CLP) DSP0214”. The general syntax of the CLP is as follows:
<verb> [<options>] [<target>] [<properties>]

<verb> Verbs specify the command or action to be executed. The list of verbs describes the following activities, for instance: – Establish (set) and retrieve (show) data, – Change the status of a target (reset, start, stop), – Manage the current session (cd, version, exit), – Return information on commands (help). In iRMC S2 systems, the verb oemfujitsu also allows the use of special OEM commands.

iRMC S2

397

Command Line Protocol (CLP)

Telnet/SSH - Remote Manager

<options> Command options modify the action or the behavior of a verb. Options can immediately follow the verb in a command line and must always be introduced by a dash ("-"). Options allow you to, for instance, – define the output format, – permit recursive execution of a command, – display the version of a command or – request help. <target> <target> specifies the address or the path of the object to be manipulated by the command, i.e. the target of the command. This can be a single managed element such as a hard disk, a network adapter (Network Interface Card, NIC), or the management program (Management Assistance Program, MAP) itself. Targets can, however, also be services such as a transport service. Several managed elements which can be managed by the management program can be subsumed under a single <target>, for instance the entire system. Only one <target> may be specified for each command. <properties> <properties> describe the properties of the target of the command which are required to execute the command. Thus, <properties> identify the properties of the target’s class that are to be retrieved or modified by the command.

398

iRMC S2

Telnet/SSH - Remote Manager User data in the CLP (overview)

Command Line Protocol (CLP)

Data within the CLP is structured hierarchically. The command cd allows you to navigate within this structure. An overview of the user data in the CLP is shown in figure 218. The names in rectangles indicate command targets. On every level of the hierarchy, the command/verb show displays the available targets, properties and verbs.

/./root

system 1

map 1

log 1

firmware

accounts

nic 1

oemsensors

oemsefru

record 1

record n

user 1

user 16

Figure 218: Structure of the user data in SMASH CLP

Hierarchy of the CLP commands An overview of the CLP command hierarchy is shown in table 18 on page 400.

iRMC S2

399

Command Line Protocol (CLP) Telnet/SSH .Remote Manager Table 18: Hierarchy of the CLP commands 400 iRMC S2 .

iRMC S2 401 . I This is only supported for servers on which the ServerView agents for Windows are installed. – On the remote workstation using the graphical interface of the Operations Manager.9 Configuring iRMC S2 using the Server Configuration Manager This chapter describes how to use the Server Configuration Manager to – configure the iRMC S2 (as of page 418). I This is only supported for servers on which the ServerView agents for Windows are installed. You can configure the iRMC S2 either locally on the managed server or from the remote workstation via the ServerView Operations Manager (referred to simply as the Operations Manager below). – configure a directory service on the iRMC S2 (see page 439). The Server Configuration Manager functions can be accessed in the following ways: – Locally on managed servers using ServerStart. I Requirements: The current ServerView agents must be installed on the managed server. – Locally on managed Windows-based servers using the Windows Start menu. – configure and manage user IDs at the iRMC S2 (as of page 433).

1 Calling the Server Configuration Manager from the ServerView Installation Manager You can also call the Server Configuration Manager from the ServerView Installation Manager (abbreviated to Installation Manager below). but are functionally identical.Starting system configuration Server Configuration Manager 9. The Installation Manager makes the Server Configuration Manager available both during preparation for installation and as a separate maintenance program.1. the Windows Start menu and the ServerView Operations Manager. the dialog boxes of the Server Configuration Manager variant called from Operations Manager are depicted. Configuration via the Installation Manager is of significance when installing the server. The Installation Manager is described in the manual “PRIMERGY ServerView Suite ServerView Installation Manager”.1 Starting system configuration This section describes how to call the Server Configuration Manager from the ServerView Installation Manager. 402 iRMC S2 . 9. I The user interfaces of the individual Server Configuration Manager variants differ slightly in terms of their layout. In the description of the Server Configuration Manager dialog boxes for configuring the iRMC S2 (see page 418ff).

1.Server Configuration Manager Starting system configuration 9. Ê Click OK.2 Calling the Server Configuration Manager from the Windows Start menu On Windows-based servers. The tab view of the System Configuration window opens. iRMC S2 403 . The System Configuration window opens: Figure 219: System Configuration window Ê Accept the preset values. You can scroll to the left and right through the tabs by clicking the arrows next to the tabs. To do this. select: Start – All Programs – Fujitsu – ServerView – Agents – Configuration Tools – System Configuration. proceed as follows: Ê On the managed server. you can also call the Server Configuration Manager via the Windows Start menu.

Ê Click the Save Page button. 404 iRMC S2 .Starting system configuration Applying settings Server Configuration Manager To apply the settings made in the individual tabs. proceed as follows for each tab: Ê Click the Apply button. The iRMC S2 automatically reboots to activate the changed settings.

3 Calling the Server Configuration Manager from the Operations Manager The Server Configuration Manager dialog boxes for configuring the iRMC S2 are also available from the graphical user interface of the Operations Manager. The start window of the Operations Manager opens: iRMC S2 405 . This allows you to configure the iRMC S2 of the managed server from the remote workstation via a Web interface. Proceed as follows: Ê Start the Operations Manager (refer to the manual “PRIMERGY ServerView Suite Operations Manager”).1.Server Configuration Manager Starting system configuration 9.

This opens the following window: 406 iRMC S2 .Starting system configuration Server Configuration Manager Figure 220: Operations Manager: Start window Ê Choose Server Configuration from the Administration menu of the Operations Manager start window.

Server Configuration Manager Starting system configuration Figure 221: Operations Manager: Server Configuration window .Server list (1) tab Ê In the hierarchy tree of the Server list tab. select the server to be configured. This opens the following window (see figure 222 on page 408): iRMC S2 407 .

. The following window appears.. specify the details on the selected server and confirm your entries by clicking GO.Starting system configuration Server Configuration Manager Figure 222: Operations Manager: Server Configuration window .Server list (2) tab Ê In the right-hand side of the window. showing the Boot Watchdog page (see figure 223 on page 409): 408 iRMC S2 ...

I After you have completed configuring a server.Server Configuration Manager Starting system configuration Figure 223: Operations Manager: Server Configuration window . Choose Reload Page or Reload all to reset the settings to the original values. click the required function. I This manual only describes those dialog pages which are relevant for I Activate the configured settings for each server either separately for each dialog page with Save Page or after you have completed the entire configuration with Save all.Configuration tab Ê In the navigation area. iRMC S2 409 . The associated dialog page then appears in the right-hand side of the window. Ê Configure the settings you require and save them with Save Page or with Save all. you can select further servers for configuration in the Server list tab. configuring the iRMC S2 and for user management on the iRMC S2.

410 iRMC S2 .2 iRMC Power Consumption Control Control the power consumption of the server The iRMC Power Consumption Control dialog page allows you to specify the mode the iRMC S2 uses to control the power consumption of your PRIMERGY server. I Enable Power Consumption Monitoring is enabled by default as of Version 3. Figure 224: iRMC Power Consumption Control dialog page Ê Configure the following settings: Enable Power Consumption Monitoring Specifies whether power monitoring is to be carried out. I This setting only takes effect on PRIMERGY servers that support power monitoring.iRMC Power Consumption Control Server Configuration Manager 9. Ê Select iRMC Power Consumption Control.32 of the firmware.

Power Consumption Scheduler I The Power Consumption Scheduler is only activated if you select the Power Consumption Scheduler option under Power Control Mode. lowest power consumption) that the iRMC S2 uses to control power consumption on the managed server. – Best Performance The iRMC S2 controls the server to achieve best performance.Server Configuration Manager iRMC Power Consumption Control Power Control Mode Mode for controlling the power consumption of the managed server: – Disabled The iRMC S2 allows the operating system to control power consumption. performance is not always ideal. iRMC S2 411 . In this event. The Power Consumption Scheduler allows you to specify in detail the schedules and modes (operating-system-controlled. – Minimal Power Consumption The iRMC S2 controls the server to achieve the lowest possible power consumption. best performance. – Power Consumption Scheduler The iRMC S2 controls power consumption on the basis of the Power Consumption Scheduler (see below). In this event. power consumption can rise.

License Key and HP SIM Integration You can perform the following tasks on the iRMC Advanced Features dialog page: – store the IP address or DNS name of a remote storage server on the iRMC S2.3 iRMC Advanced Features Remote Storage Server. Ê Choose iRMC Advanced Features. Figure 225: iRMC Advanced Features dialog page Ê Configure the following settings: Hostname or IP address Here you enter the DNS name or IP address of the computer on which a remote storage server is installed. 412 iRMC S2 .iRMC Advanced Features Server Configuration Manager 9. – deactivate or activate HP SIM integration. – enter a license key for the use of the Advanced Video Redirection and Remote Storage functionality.

Server Configuration Manager iRMC Advanced Features License Key Enter a valid license key for the use of the Advanced Video Redirection and Remote Storage functionality here. Enable or disable this option to activate or deactivate HP SIM integration. Disable HP System Insight Manager integration .. iRMC S2 413 ... If the Disable HP System Insight Manager Integration . option is deactivated. the iRMC S2 responds with identification information to a non-authenticated XML query from the HP Insight Managers..

Ê Choose ASR&R Fan Settings. Shutdown The server is shut down if the fan is still faulty after the time specified in Action Delay (sec) has elapsed.ASR&R Fan Settings Server Configuration Manager 9. Figure 226: ASR&R Fan Settings dialog page Ê Configure the following settings: Fail Action Specify whether the server is to be shut down if the corresponding fan fails. you can also specify whether the server is to be shut down if that fan fails.4 ASR&R Fan Settings The ASR&R Fan Settings dialog page shows information on the fans of the managed server. Action Delay (sec) If you select “Shutdown” under Fail Action. Continue The server is not shut down. For each fan. 414 iRMC S2 . you can specify a time delay here.

the server is shut down immediately after the fan fails. Continue The server is shut down. I If you do not enter a value. iRMC S2 415 .Server Configuration Manager ASR&R Fan Settings The server is shut down if the relevant fan fails and is still faulty after the specified time has elapsed. Set fail action for all fans Here you can specify for all fans whether the server is to be shut down if any fan fails. Shutdown The server is shut down if the failed fan is still faulty after the time specified in Action Delay (sec) has elapsed.

For each sensor. Continue The server is not shut down.ASR&R Temperature Settings Server Configuration Manager 9. Ê Choose ASR&R Temperature Settings. you can also specify whether the server is to be shut down if critical temperature thresholds are reached. Figure 227: ASR&R Temperature Settings dialog page Ê Configure the following settings: Fail Action Specify whether the server is to be shut down if a critical temperature threshold is reached on the selected sensor.5 ASR&R Temperature Settings The ASR&R Temperature Settings dialog page shows information on the temperature sensors of the managed server. 416 iRMC S2 . Shutdown The server is shut down.

Server Configuration Manager ASR&R Temperature Settings Set fail action for all fans Here you can specify for all temperature sensors whether the server is to be shut down if the critical temperature is reached on any temperature sensor. Continue The server is not shut down. Shutdown The server is shut down. iRMC S2 417 .

V CAUTION! Contact the network administrator responsible for the system before you change the LAN settings. the serial interface or via the BIOS.Configure LAN parameters of the iRMC S2 The iRMC LAN Interface dialog page is used to configure the LAN parameters (Ethernet settings) for the iRMC S2. If you set illegal LAN parameters for the iRMC S2 you will only be able to access the iRMC S2 again using special configuration software. Ê Choose iRMC LAN Interface.iRMC LAN Interface Server Configuration Manager 9. Figure 228: iRMC LAN Interface dialog page 418 iRMC S2 .6 iRMC LAN Interface .

the values for IP address. You can specify that the DHCP and DNS services are to be used after initial installation in the following dialog pages: iRMC DHCP DNS Configuration (see page 423) and iRMC DNS Server Configuration (see page 425) or by configuring this in the iRMC S2 web interface (see section “Network Settings . I This entry is only evaluated if DHCP is not activated (see Obtain an IP address automatically (Use DHCP)). the following name is passed to the DHCP server on initial installation of the iRMC S2: iRMC<last 3 bytes of the MAC address>.Configure the LAN parameters” on page 301). Subnet Mask Subnet mask of the iRMC S2 in the LAN.e. IP Address The address of the iRMC S2 in the LAN. iRMC S2 419 . Default Gateway IP address of the default gateway in the LAN. I This entry is only evaluated if DHCP is not activated (see Obtain an IP address automatically (Use DHCP)). and Default Gateway are set automatically. If you activate the DHCP option and there is no DHCP server available. By default. I This entry is only evaluated if DHCP is not activated (see Obtain an IP address automatically (Use DHCP)). I Do not activate the DHCP option if no DHCP server is available.Server Configuration Manager Ê Configure the following settings: iRMC LAN Interface Obtain an IP address automatically (Use DHCP) If you enable Obtain an IP address automatically (Use DHCP). In this case. This address is different from the IP address of the managed server. it constantly searches for a DHCP server). Subnet mask. the iRMC S2 goes into a search loop (i. the iRMC S2 gets its LAN settings autonomously from a DHCP server on the network.

iRMC LAN Interface Server Configuration Manager LAN Speed LAN speed. 420 iRMC S2 . the LAN interface of the installed system NIC (network interface card) can be set up – as shared LAN for shared operation with the system or – as a service LAN for exclusive use as a management LAN. VLAN enabled This option allows you to activate VLAN support for the iRMC S2 VLAN ID VLAN ID of the virtual network (VLAN) the iRMC S2 belongs to. I The Service LAN setting is mandatory for the Type TX150 S6 PRIMERGY server. VLAN Priority VLAN priority (user priority) of the iRMC S2 in the VLAN specified by VLAN Id. LAN Port I This option is not supported for all PRIMERGY servers. Permitted value range: 0 Î VLAN Priority Î 7 (default: 0). the onboard LAN controller assigned to the iRMC S2 autonomously determines the correct transfer speed and duplex method for the network port it is connected to. On some PRIMERGY server models. The following options are available: – – – – – Auto Negotiation 100 MBit/s Full Duplex 100 MBit/s Half Duplex 10 MBit/s Full Duplex 10 MBit/s Half Duplex If Auto Negotiation is selected. Permitted value range: 1 Î VLAN Id Î 4094.

V CAUTION! Configuration is not supported for ports where the input fields are deactivated in the iRMC S2 web interface (see page 305). Ê Select iRMC Networking Ports.7 iRMC Networking Ports Configuring ports and network services The iRMC Networking Ports dialog page allows you to view and modify the configuration settings for ports and network services. Figure 229: iRMC Networking Ports dialog page Ê Configure the following settings: HTTP Port HTTP port of the iRMC S2 (non-secure connection) HTTPS Port HTTPS port of the iRMC S2 (secure connection) iRMC S2 421 . It is only possible to verify whether the ports can be configured using the iRMC S2 Web interface.Server Configuration Manager iRMC Networking Ports 9. The preset values must not be changed using the Server Configuration Manager during initial configuration.

If the SSL certificate has expired. Telnet enabled If you enable the Telnet Enabled option. This input field is only displayed if Telnet enabled is activated. VNC Ports . VNC Ports .Standard Port VNC port of the iRMC S2. Remote Storage Ports . a message to this effect is issued in the web browser.Standard Port Remote storage port of the iRMC S2 422 iRMC S2 . hard-configured (port number: 80). hard-configured (port number: 443).iRMC Networking Ports Server Configuration Manager Force HTTPS If you disable the Force HTTPS option. users can establish a connection to the iRMC S2 on the Telnet port specified in the entry field. If you enable the Force HTTPS option. Telnet Port Telnet port of the iRMC S2. SSH Port SSH port of the iRMC S2 Drop Time (sec) Period of inactivity (in seconds) after which a Telnet connection is automatically cleared. I You can also configure web access in the iRMC S2 web interface. users can establish a secure connection to the iRMC S2 on the HTTPS port specified in the entry field. users can only establish a nonsecure connection to the iRMC S2 on the HTTP port specified in the entry field.Secure Port Secure VNC port of the iRMC S2.

Add serial number The last 3 bytes of the MAC address of the iRMC S2 are appended to the end of the DHCP name of the iRMC S2. Figure 230: iRMC DNS Registration dialog page Ê Configure the following settings: Register DHCP address in DNS Enables/disables transfer of the DHCP name to the DHCP server for the iRMC S2.8 iRMC DNS Registration Configuring the host name for the iRMC S2 The iRMC DNS Registration dialog page allows you to configure a host name for the iRMC S2 and thus use “dynamic DNS”. iRMC S2 423 . Ê Choose iRMC DNS Registration. Dynamic DNS allows DHCP servers to autonomously pass on the IP address and system name of a network component to DNS servers to facilitate identification.Server Configuration Manager iRMC DNS Registration 9. Use user defined iRMC Name instead of host name The iRMC name specified in the iRMC Name entry field is used for the iRMC S2 in place of the server name.

iRMC DNS Registration Server Configuration Manager iRMC Name iRMC name passed to DHCP for the iRMC S2 in place of the server name. 424 iRMC S2 . Extension Enter a name extension for the iRMC S2. Add user defined extension The extension specified in the Extension entry field is appended to the DHCP name of the iRMC S2.

Obtain DNS configuration from DHCP If you activate this option.Server Configuration Manager iRMC DNS Server 9.DNS-Server 5. up to five DNS servers are supported. If you do not enabled this setting. Figure 231: iRMC DNS Server dialog page Ê Configure the following settings: DNS enabled Enables/disables DNS for the iRMC S2. Ê Choose iRMC DNS Server. iRMC S2 425 .9 iRMC DNS Server Activating DNS for the iRMC S2 The iRMC DNS Server dialog page allows you to activate the Domain Name Service (DNS) for the iRMC S2. This allows you to use symbolic DNS names instead of IP addresses for configuring the iRMC S2. In this event. the IP addresses of the DNS servers are obtained automatically from the DHCP server. you can enter up to five DNS server addresses manually under DNS-Server 1 .

specify the name of the default domain for requests to the DNS server(s). 5 If the Obtain DNS configuration from DHCP option is disabled.iRMC DNS Server Server Configuration Manager DNS Domain If the option Obtain DNS configuration from DHCP is disabled. DNS Server 1 .. you can enter the names of up to five DNS servers here. 426 iRMC S2 .

Server Configuration Manager iRMC EMail Alerting 9. SMTP Settings This is where you configure the global email settings.10 iRMC EMail Alerting Configure email alerting The iRMC Email Alerting dialog page allows you to configure how the iRMC S2 forwards emails. SMTP Retries Number of SNMP retries. Figure 232: iRMC EMail Alerting dialog page Ê Configure the following settings: Enable email alerting Activate this option. iRMC S2 427 . Ê Choose iRMC EMail Alerting. SMTP Retry Delay (sec) Time between SNMP retries.

SMTP Server IP address of the primary mail server I You can activate the Domain Name Service (DNS) for the SMTP Port SMTP port of the primary mail server iRMC S2 (see “iRMC DNS Server . Authentication Type Authentication type for connecting the iRMC S2 to the primary mail server: – None No authentication for the connection. Primary SMTP Server This is where you configure the settings for the primary mail server (SMTP server).iRMC EMail Alerting Server Configuration Manager Response Timeout (sec) Timeout (in seconds) for an SMTP response. You can then use a symbolic name instead of the IP address. 428 iRMC S2 .Activating DNS for the iRMC S2” on page 425). – SMTP AUTH (RFC 2554) Authentication according to RFC 2554: SMTP Service Extension for Authentication Authentication User Name User name for authentication on the primary mail server Password Enter the password for authentication on the primary mail server. Confirm Password Enter the password again here.

iRMC S2 429 . Confirm Password Confirm the password by entering it again here.Server Configuration Manager Secondary SMTP Server iRMC EMail Alerting This is where you configure the settings for the secondary mail server (SMTP server). – SMTP AUTH (RFC 2554) Authentication according to RFC 2554: SMTP Service Extension for Authentication Authentication User Name User name for authentication on the secondary mail server Password Enter the password for authentication on the secondary mail server. You can then use a symbolic name instead of the IP address. Authentication Type Authentication type for connecting the iRMC S2 to the secondary mail server: – None No authentication for the connection. SMTP Server IP address of the secondary mail server I You can activate the Domain Name Service (DNS) for the SMTP Port SMTP port of the secondary mail server iRMC S2 (see “iRMC DNS Server .Activating DNS for the iRMC S2” on page 425).

Figure 233: iRMC Mail Format Settings dialog page 430 iRMC S2 .11 iRMC Mail Format Settings Mail-format-dependent settings The iRMC Mail Format Settings dialog page allows you to configure the mailformat-dependent settings.iRMC Mail Format Settings Server Configuration Manager 9. The following email formats are supported: – – – – Standard Fixed Subject ITS-Format Fujitsu REMCS Format Ê Choose iRMC Mail Format Settings. You specify the mail format for each user using the iRMC User Management dialog page in the iRMC User Account Properties window (see page 434).

iRMC S2 431 . I If the string entered here contains an “@”. Only active for the Fixed Subject mail format (see page 437). Only active for the Fixed Subject mail format (see page 437). “admin@<ipaddress>” is used as the valid email address. Server URL A URL under which the server is accessible under certain conditions. similar to the serial number. Only active for the ITS mail format (see page 437). Only active for the mail format “Fujitsu REMCS-Format” (see page 437). Only active for the ITS mail format (see page 437). (Some entry fields are disabled depending on the mail format): From Sender identification iRMC S2. Only active for the Standard mail format (see page 437). interpreted as a valid email address. Administrator Name Name of the administrator responsible (optional). Administrator Phone Phone number of the administrator responsible (optional). REMCS Id This ID is an additional server ID. the string is Subject Fixed subject for the alert mails. Active for all mail formats.Server Configuration Manager iRMC Mail Format Settings Ê Configure the following settings. You have to enter the URL manually. Otherwise. Message Type of message (email).

SNMP Trap Destinations (Host Name or IP Address) DNS names or IP addresses of the servers that belong to this community and are to be configured as Trap Destinations. I Forwarding of SNMP traps to up to seven SNMP servers is supported.iRMC SNMP Alerting Server Configuration Manager 9. 432 iRMC S2 .Configure SNMP Trap alerting The iRMC SNMP Alerting dialog page allows you to view and configure the settings for SNMP trap alerting. Figure 234: iRMC SNMP Alerting dialog page Ê Configure the following settings: SNMP Community Name Name of the SNMP community. Ê Choose iRMC SNMP Alerting.12 iRMC SNMP Alerting .

.Server Configuration Manager iRMC User Management 9. Ê Choose iRMC User Management.. then click the Delete. first select the user (by selecting the corresponding line). I User ID 1 (“null user”) is reserved for the IPMI standard and is therefore unavailable for user management on the iRMC S2. button and confirm that you want to delete the user. iRMC S2 433 . Figure 235: iRMC User Management dialog page Ê To delete a user.13 iRMC User Management Local user management on the iRMC S2 The iRMC User Management dialog page allows you to configure the local user management settings for the iRMC S2. The dialog page contains a table showing all the configured users: Each line contains the data for one configured user. I User management on the iRMC S2 requires Configure User Accounts permission.

. Ê Double-click on a line for a specific user or select a user and click the Modify .iRMC User Management Server Configuration Manager Ê Double-click on a line for which the user ID is not yet assigned to any user (empty line) or select such a line and click the Modify .. button to open an empty Edit existing user window (containing default settings). Figure 236: Edit existing user window 434 iRMC S2 .. button to open the Edit existing user window. in which you can view and/or modify the settings for this user (see figure 236). in which you can configure a new user (see figure 236)..

User Name Enter the name of the user. LAN Assign a privilege group for a LAN channel to the user here. iRMC S2 435 . User Privileges This is where you configure the channel-specific user privileges as well as other permissions. Can use video redirection Permission to use Advanced Video Redirection (AVR) in “View Only” and “Full Control” mode.Server Configuration Manager Account enabled Disable this option to lock the user. Serial Assign a privilege group for a serial channel to the user here: The same privilege groups are available as for LAN Privilege. Can configure users Permission to configure local user access data. Password Enter the user password. User Description Additional information on the user. Account Data iRMC User Management This is where you configure the access data for the user. Can configure iRMC Permission to configure the iRMC S2 settings. Confirm Password Confirm the password by entering it again here. The following options are available: – – – – User Operator Administrator OEM Refer to section “User permissions” on page 62 for information on the permissions associated with the privilege groups.

iRMC User Management Server Configuration Manager Can use remote storage Permission to use the Remote Storage functionality.Start a SMASH CLP shell” on page 393. . Shell Select the desired user shell here. Enabled Specify whether the user is to be informed about system statuses by email. – Remote Manager See chapter “iRMC S2 via Telnet/SSH (Remote Manager)” on page 373.. 436 iRMC S2 . User Shell Select the user shell here.. – IPMI Basic Mode – IPMI Terminal Mode – None EMail Paging Settings This is where you configure the settings governing the email format and the global email settings. The following options are available: – SMASH CLP See section “Start a Command Line shell.

The following email formats are available: – – – – Standard Fixed Subject ITS-Format Fujitsu REMCS Format a particular paging group. I Every entry in the event log for the iRMC S2 is assigned to Address Email address of recipient. – Secondary Only the SMTP server which has been configured as the secondary SMTP server (see page 429) is used as the preferred mail server. I Errors sending email are recorded in the event log. for instance because the preferred mail server is not available.Server Configuration Manager Format iRMC User Management Depending on the selected email format. you can make a number of settings in the iRMC Email Format Settings dialog page (see page 430). iRMC S2 437 . Preferred Server Select the preferred mail server. the email is sent to the second mail server. You can choose one of the following options: – Automatic If the email cannot be sent successfully immediately. – Primary Only the SMTP server which has been configured as the primary SMTP server (see page 428) is used as the preferred mail server.

WARNING The iRMC S2 notifies users by email if an entry in the system event log is reported as WARNING. you configure the system events of which an iRMC S2 user is to be notified by email (Paging Severity Configuration). 438 iRMC S2 . the user is also notified of system event log entries with the status CRITICAL. Ê Confirm your settings by clicking OK. ALL The iRMC S2 notifies users of every event in this group which causes an entry to be made in the system event log. NONE The notification function is deactivated for this paging group. CRITICAL The iRMC S2 notifies users by email if an entry in the system event log is reported as CRITICAL.iRMC User Management Server Configuration Manager In the bottom third of the Edit existing user window. I If WARNING is set.

Server Configuration Manager iRMC Directory Service 9. Figure 237: iRMC Directory Service dialog page iRMC S2 439 . Novell eDirectory and OpenLDAP. strings in LDAP: &. >. Ê Choose iRMC Directory Service. ~. support for iRMC S2 LDAP access is provided for the following directory services: Microsoft Active Directory. <. =. I Currently. : I The following characters are reserved as metacharacters for search You must therefore not use these characters as components of Relative Distinguished Names (RDN). |.14 iRMC Directory Service Configuring the directory service The iRMC Directory Service dialog page allows you to configure the iRMC S2 for global user management via a directory service (see page 83). !.

– For eDirectory and OpenLDAP. depending on the directory service you select: – For Active Directory. Ê Activate the option LDAP Enable. Only if you do not activate Always use SSL Login and LDAP is deactivated is a mask secured via Digest Authentication Login used. I If LDAP Enable is checked then the login information (see page 222) is always transferred with SSL encryption between the web browser and the iRMC S2.iRMC Directory Service Server Configuration Manager LDAP enable This option specifies whether the iRMC S2 can access a directory service via LDAP. refer to “Configure iRMC S2 for Microsoft Active Directory” on page 441. Disable Local Login If you activate this option then all the local iRMC S2 user identifications are locked and only the user identifications managed by the directory service are valid. Different input fields are provided. refer to “Configuring iRMC S2 for Novell eDirectory / OpenLDAP” on page 443. Always use SSL login I This option is only relevant if LDAP is deactivated. Ê Choose the required directory service from Directory Server Type. 440 iRMC S2 . Directory service access via LDAP is only possible if LDAP Enable has been activated. V CAUTION! If the option Disable Local Login is activated and the connection to the directory service fails then it is no longer possible to log in at the iRMC S2. If you activate this option then the HTTP SSL-secured login page is always used even if LDAP is deactivated.

Server Configuration Manager iRMC Directory Service 9. Figure 238: iRMC Directory Service (Microsoft Active Directory) dialog page iRMC S2 441 .14.1 Configure iRMC S2 for Microsoft Active Directory I The entries shown as examples in figure 238 refer to the examples and figures shown in section “iRMC S2 user management via Microsoft Active Directory” on page 107.

iRMC Directory Service Ê Configure the remaining settings: Server Configuration Manager LDAP Server 1 IP address or DNS name of the LDAP directory server that is to be used. User Name. I LDAP SSL Enable has no influence on whether or not the iRMC S2 web interface pages are SSL-protected on opening. LDAP Server 2 IP address or DNS name of the LDAP directory server which is maintained as the backup server and used as the directory server if LDAP Server 1 fails. The settings that you make here are required for alerting in connection with global user identifications. A user may have different permissions for the department X server than for the department Y server (see also figure 27 on page 90). Ê Click the Save Page button to complete the directory service configuration and activate the settings. alerting is currently only supported for local user identifications. LDAP SSL Enable If you check this option then data transfer between iRMC S2 and the directory server is SSL encrypted. Domain Name Complete DNS path name of the directory server. Base DN Base DN is automatically derived from Domain Name. However. I You should only activate LDAP SSL Enable if a domain controller certificate is installed. 442 iRMC S2 . Department Name Department name. LDAP Auth Password These settings are not relevant at present. The directory service needs the department name in order to determine the user permissions. LDAP Auth.

2 Configuring iRMC S2 for Novell eDirectory / OpenLDAP I The Directory Service Configuration dialog page has an identical structure for both Novell eDirectory and OpenLDAP.14. Figure 239: iRMC Directory Service dialog page iRMC S2 443 .Server Configuration Manager iRMC Directory Service 9. I The entries shown as examples in figure 239 refer to the examples and figures shown in section “iRMC S2 user management via Novell eDirectory” on page 120.

LDAP Server 2 IP address or DNS name of the LDAP directory server which is maintained as the backup server and used as the directory server if LDAP Server 1 fails.iRMC Directory Service Ê Configure the remaining settings: Server Configuration Manager LDAP Server 1 IP address or DNS name of the LDAP directory server that is to be used. Group DN Context Pathname of the OU iRMCgroups as a subtree of Base DN. I You should only activate LDAP SSL Enable if a domain controller certificate is installed. 444 iRMC S2 . A user may have different permissions for the department X server than for the department Y server (see also figure 27 on page 90). Base DN The Base DN is the full distinguished name of the eDirectory or OpenLDAP server and represents the tree or subtree that contains the OU (Organizational Unit) iRMCgroups. LDAP SSL Enable If you check this option then data transfer between iRMC S2 and the directory server is SSL encrypted. I LDAP SSL Enable has no influence on whether or not the iRMC S2 web interface pages are SSL-protected on opening. User Search Context Pathname of the OU Users as a subtree of Base DN. LDAP Auth. User Name Generic iRMC S2 user ID under which the iRMC S2 queries the permissions of the iRMC S2 users from the LDAP server. Password Password the principal user uses to authenticate themselves on the LDAP server and confirmation of the password. LDAP Auth. The directory service needs the department name in order to determine the user permissions. This DN forms the starting point for LDAP searches. Department Name Department name.

Ê Click the Save Page button to complete the directory service configuration and activate the settings. By default. If you select Enhanced User Login. Bind DN Bind DN shows the principal user DN used for LDAP authentication. under which the iRMC S2 queries the permissions of the iRMC S2 users from the LDAP server. If you inadvertently specify and activate an invalid search filter. the User Login Search Filter input field is also activated. you do not need to specify the Base DN under Principal User DN. At login. this contains the standard login search filter. All global logins are then permitted to log into the iRMC S2 which meet the criteria of this search filter. iRMC S2 445 . The base DN specified under Base DN is used.Server Configuration Manager iRMC Directory Service Principal User DN Fully distinguished name of the generic iRMC S2 user ID (principal user). Append Base DN To Principal User DN If you activate this option. You can modify the filter by specifying another attribute in place of “cn=”. V CAUTION! Only activate this option if you are familiar with the LDAP syntax. the placeholder “%s” is replaced by the associated global login. Enhanced User Login Enhanced flexibility on user login. users can only log in to the iRMC S2 under a global login after the Enhanced User Login option has been deactivated.

.

I The managed server must be rebooted to activate the updated firmware. I Before updating the firmware. see page 449) both belong to the same firmware release.10 Firmware update This chapter provides you with information about the following topics: – iRMC S2 firmware (overview) – Creating a memory stick for updating the firmware – Updating firmware images – Emergency flash – flash tools I The current firmware versions are present on the PRIMERGYServerView Suite DVD 1 or can be downloaded manually from the Download section of the Fujitsu Technology Solutions web server. V CAUTION! When updating the firmware. note that problem-free operation of the firmware can only be guaranteed if the runtime firmware and the SDR (Sensor Data Record. read the supplementary documentation supplied with the new firmware carefully (in particular the Readme files). You can obtain the up-to-date version of the PRIMERGY ServerView Suite DVD 1 at two-monthly intervals. iRMC S2 447 .

1 iRMC S2 firmware (overview) The iRMC S2 uses two different firmware images to ensure that the firmware remains executable even during a firmware update. 448 iRMC S2 . page iRMC S2 Information (see page 240) or – using the flash tool (see page 460). This means that it is possible to update both active and inactive firmware images online. but is instead loaded into SRAM memory on startup and executed there.e. while the other is inactive. with the server operating system (Windows or Linux) running. Active and passive firmware image One of the two firmware images is active (running) at any given time. The firmware image that is active depends on the so-called firmware selector (see page 450). I Information on the iRMC S2 firmware and EEPROM can be found – in the iRMC S2 web interface.iRMC S2 firmware (overview) Firmware update 10. i. The two firmware images are stored on a 16-MB EEPROM (Electrically Erasable Programmable Read-Only Memory): – Firmware image 1 (low FW image) – Firmware image 2 (high FW image) The firmware of the iRMC S2 is not executed in the EEPROM.

If a firmware error is detected. the bootloader sets the firmware selector to the other firmware image. The SDRR also acts as an interface via which you can access the SDRs. iRMC S2 449 .Firmware update Structure of the iRMC S2 EEPROM iRMC S2 firmware (overview) The EEPROM of the iRMC S2 contains one area for firmware image 1 and one area for firmware image 2: Runtime firmware 8 MB for firmware image 2 SDRR (and configuration table) not used Runtime firmware 8 MB for firmware image 1 SDRR (and configuration table) Bootloader Figure 240: Structure of the iRMC S2 EEPROM – Bootloader The bootloader checks the firmware image that is currently active. You can perform a firmware update for each of these areas. – Runtime firmware The runtime firmware is the executable part of the iRMC S2's firmware. – SDRR (Sensor Data Record Repository) The SDRR contains the Sensor Data Records (SDR) in which sensor information for the managed server is stored.

iRMC S2 firmware (overview) Firmware selector Firmware update The firmware selector specifies the iRMC S2 firmware to be executed. The firmware selector can have the following values: 0 1 2 3 4 5 Firmware image containing the most recent firmware version firmware image 1 firmware image 2 Firmware image containing the oldest firmware version Firmware image most recently updated Firmware image that has been updated least recently differently after the update. I Depending on the update variant used. the firmware selector is set You can query and explicitly set the firmware selector – on the iRMC S2 Information page of the iRMC S2 web interface (see “Running Firmware” on page 242) or – using the flash tool (see page 460). the firmware selector is evaluated and processing branches to the corresponding firmware. 450 iRMC S2 . Every time the iRMC S2 is reset and restarted. .

Ê Start the file FTS_<nnnnnnn>.zip The ZIP archive contains the following files: – USBImage. – FTS_<nnnnnnn>. or Insert the current PRIMERGY ServerView Suite DVD 1 in the DVD drive of your computer.IMA Ê Connect the USB memory stick to your computer.exe – FTS_<nnnnnnn>. One of the following windows is opened depending on the file you call (see figure 241 on page 452): iRMC S2 451 .exe – iRMC_<Firmware-Version>.Firmware update Setting up the USB memory stick 10.exe or the file USBImag. The following files or following ZIP archive can be found in your download directory or on DVD 1.exe.2 Setting up the USB memory stick iRMC S2 in one of the following ways: I You do not need the USB memory stick if you update the firmware of the – using the ServerView Update Manager – using ServerView Update Manager Express or ASP – using the iRMC S2 web interface and TFTP server Proceed as follows: Ê Download the firmware iRMC Firmware Update for USB Stick from the Download section of the Fujitsu Technology Solutions web server to a directory on your computer.

then under Image File:.IMA.exe.Setting up the USB memory stick Firmware update Figure 241: Copying the image file to the USB memory stick (with FTS_<nnnnnnn>. Ê Click Clear USB Device to delete the data from the USB memory stick.exe) I If you have called USBImag.exe) Figure 242: Copying the image file to the USB memory stick (with USBImage. you must explicitly specify the file iRMC_<Firmware-Version>. 452 iRMC S2 .

IMA to the USB memory stick and extract it. Figure 243: Image files and flash tool on the USB memory stick.Firmware update Setting up the USB memory stick Ê Click Copy Image File to USB Device to copy the file BMC_<Firmware-Version>. When the copy operation is complete. V CAUTION! This action overwrites the content of the USB memory stick. iRMC S2 453 . the flash tools and image files are present on the USB memory stick.

The following methods are available for updating the firmware images: – over the iRMC S2 web interface – using the ServerView Update Manager – using ServerView Update Manager Express or ASP – Update using the operating system flash tools. you can start the update of the iRMC S2 firmware via a graphical user interface (Windows) or via a command line interface (Windows and Linux).3. 10. 454 iRMC S2 .3. The ServerView Update Manager accesses the update data via its Update Repository on the PRIMERGY ServerView Suite DVD 1 or on the management server. You update the update repository on the management server by means of the Download Manager or by performing a manual download from the Download section of the Fujitsu Technology Solutions web server. i. see the “PRIMERGY ServerView Suite . 10.e.1 over the iRMC S2 web interface The iRMC S2 Firmware Update page allows you to update the firmware of the iRMC S2 by providing the firmware image either locally on the remote workstation or on a TFTP server (see section “iRMC S2 Firmware Update” on page 256).Updating firmware images Firmware update 10. it is possible to update both active and inactive firmware images online.3 Updating firmware images Since the iRMC S2 firmware executes in the SRAM memory of the iRMC S2.2 Update using the ServerView Update Manager Using the ServerView Update Manager. with the server operating system running.ServerView Update Manager” manual. For more detailed information on firmware updates with the ServerView Update Manager.

4 Update using the operating system flash tools.e. The syntax and operands for the flash tools are described in section “Flash tools” on page 460. the ServerView agents must be started on the managed server. I An online update using the operating system flash tools is only performed as a recovery flash. Prerequisites – The flash tools and the files for the firmware update must be present in the file system of the managed server. For more detailed information on firmware updates with Update Manager Express and ASP. WinFLIRMCS2. sFLIRMCS2). 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. see the “ServerView Update Manager Express” manual. WinFLIRMCS2) or at the Linux CLI (rFLIRMCS2. you can also start an ASP in the Windows Explorer by doubleclicking the corresponding ASP-*.3. i. – Under Windows and Linux. Under Windows. no version check is performed.3 Online update using ServerView Update Manager Express or ASP Under Windows and Linux operating systems. iRMC S2 455 . 10.Firmware update Updating firmware images 10.3.exe file. rFLIRMCS2 or sFLIRMCS2 depending on the operating system that you are running: DOS Windows: Red Hat Linux: Suse Linux: flirmcs2 WinFLIRMCS2 rFLIRMCS2 sFLIRMCS2 You call the flash tools in the Windows command line (flirmcs2. You use one of the flash tools flirmcs2.

If an error occurs. the console informs you about the progress of the update operation. Ê In the Windows command line or the Linux Command Line Interface (CLI) switch to the drive corresponding to the USB memory stick. in the Windows command line you enter: WinFLIRMCS2 dcod<firmware-version>..g. E. Ê Restart the managed server.. This automatically activates the firmware image with the updated firmware.sdr /i During the firmware update.g. Ê Set the firmware selector to the value 4 by calling the flash tool with the parameter /s 4. E.bin <nnnnnnn>.Updating firmware images Proceed as follows: Firmware update I An online update using a USB memory stick is described below (see section “Setting up the USB memory stick” on page 451). the update operation is aborted and a corresponding return code is reported (see page 462). Ê Connect the USB memory stick to the managed server. in the Windows command line you enter: WinFLIRMCS2 /s 4 Ê Start the update of the firmware and the SDR data by calling the flash tool with the corresponding update files. 456 iRMC S2 .

If one of these areas is not up to date then the corresponding area for the inactive firmware is updated if it is not already up to date. The FlashDisk menu opens: Figure 244: FlashDisk menu Normal A normal flash is performed. During a normal flash operation.bat file is then started automatically. After completion of the boot operation. The autoexec.3.Firmware update Updating firmware images 10. iRMC S2 457 .5 Update via the FlashDisk menu I For an update via the FlashDisk menu. those areas of the EEPROM that contain the active firmware are checked to see whether they are up to date. you require a bootable USB memory stick (see section “Setting up the USB memory stick” on page 451). Ê Boot from the USB memory stick. Proceed as follows: Ê Connect the USB memory stick to the managed server (directly or via remote storage). the data in the USB memory stick is automatically copied to a RAM disk.

English / German Specify keyboard layout. the flash is performed for all three areas of firmware image 2 without any version check. If an error occurs. In the case of a recovery flash. 458 iRMC S2 . A firmware downgrade is only possible via recovery flash. Readme The Readme file is opened. the update operation is aborted. A corresponding return code is reported (see page 462). Ê Start the required update variant by clicking on the corresponding button. click on Exit. Ê Once the update operation has been completed. Recovery _U A recovery flash for firmware image 2 (high firmware image) is carried out.Updating firmware images Firmware update Recovery _L A recovery flash for firmware image 1 (low firmware image) is carried out. the flash is performed for all three areas of firmware image 1 without any version check. Ê Remove the USB memory stick from the managed server. with [Ctrl]+[Alt]+[Del]). Reboot An iRMC S2 warm start is performed. During the firmware update.g. Ê Restart the managed server (e. In the case of a recovery flash. the console informs you about the progress of the update operation. A firmware downgrade is only possible via recovery flash. to close the FlashDisk menu. German is set by default.

e. proceed as follows: Ê Disconnect the power supply connector.g. You can ignore the error message “iRMC S2 Controller Error” which the BIOS outputs during this period.Firmware update Emergency flash 10. I If the firmware is not active then the boot operation may take up to 2 minutes to start. In emergency mode. The managed server is now in emergency mode. Ê Insert the connector in the socket again with the Identify key held down. I Emergency mode is indicated by the error LED (global error LED) (rot) and the identification LED (blue) flashing alternately. To switch the managed server to emergency mode and then update the iRMC S2's firmware.4 Emergency flash If the iRMC S2 firmware can no longer be executed. because the SDRs are not compatible with the system. then you can use the emergency mode to start the firmware running again. the system automatically branches to the bootloader and is the ready for the firmware update. iRMC S2 459 . Ê Boot the server to DOS and use the recovery flash procedure to update the iRMC S2’s firmware.

rFLIRMCS2 and sFLIRMCS2 differ from Syntax flirmcs2 {/v|/o [/4]|/s[<value>]} flirmcs2 {<file1> [<file2>] [<file3>] [/n /l[<logfile>] /d /e /4 /i]} flirmcs2 {/h|/?} Options /v /o /s Displays the current version of the command. Displays the value of the firmware selector. Displays the current versions of both firmware images. rFLIRMCS2 and sFLIRMCS2. I The tools WinFLIRMCS2.Flash tools Firmware update 10. you simply enter “WinFLRMCS2”. “rFLIRMCS2” or “sFLIRMCS2” as appropriate. Sets the selector to the firmware image with the firmware which has not been updated for longest. This means that the description below also applies to WinFLIRMCS2. 0 1 2 3 4 5 Sets the selector to the firmware image with the most recent firmware. /s <value> Sets the value of the firmware selector. You use this option to define the firmware image from which the firmware is started after a firmware reset. Instead of “flirmcs2”. Sets the selector to the firmware image with the oldest firmware. Sets the selector to firmware image 1.5 Flash tools flirmcs2 only in respect of the name and the environment in which they are called. Sets the selector to firmware image 2. 460 iRMC S2 . Sets the selector to the firmware image with the most recently updated firmware.

I To update firmware image 2.Firmware update Flash tools <file1> through <file3> Specify one or more files to determine which updates are to be made: The following files are to be selected: boot<FW-Version>.SDR Updates the SDR. /4 Updating firmware image 2.bin Updates the runtime firmware. <SDR-Version>. This option has priority over the /p and /d options.bin Updates the bootloader firmware.log file. A rotating bar is shown in place of the percentage completion during the flashing operation. you must also specify option /4 (see below). /n /np /d /e /i No output on the console. /h and /? Outputs help information. If no logfile is specified. Update the inactive firmware. iRMC S2 461 . Emulation mode (for debugging purposes only). /l [<logfile>] Outputs error messages to the specified log file. the output is directed to the flbmc. dcod<FW-Version>. Outputs additional debug information.

16 Error flashing EEPROM. Timeout during communication with the target EEPROM. Firmware update Error accessing Keyboard Control Style interface (KCS). 15 Error erasing EEPROM. 12 Network node busy. 10 No buffer allocated. Incorrect binary file.Flash tools Return values 0 1 3 4 5 8 9 Firmware update was executed successfully. PROM type not available Communication with iRMC S2 not possible. 13 Timeout erasing EEPROM. 462 iRMC S2 . Illegal or missing arguments. 14 Timeout flashing EEPROM.

The description focuses primarily on the handling of the remote storage media. – Installing Linux from the remote workstation after configuration on the administered server. iRMC S2 463 . – Installing Windows from the remote workstation after configuration on the administered server. – The license key for the use of the iRMC S2 functions “Advanced Video Redirection (AVR)” and “Remote Storage” must be installed (see page 243). – Booting the administered server from the remote workstation using PRIMERGY ServerView DVD 1 (Windows and Linux). I Prerequisites for the remote installation of the operating system via iRMC S2: – The iRMC S2’s LAN interface must be configured (see page 38).ServerView Installation Manager”). The chapter discusses the following specific topics: – General procedure for the remote installation of an operating system using remote storage media. It is assumed that readers are familiar with the Installation Manager functionality (see the manual “PRIMERGY ServerView Suite .11 Remote installation of the operating system via iRMC S2 This chapter describes how you use the ServerView Installation Manager (abbreviated to Installation Manager below) and the iRMC features "Advanced Video Redirection (AVR)" and "Remote Storage" to install the operating system on the administered server from the remote workstation.

1 Installing the operating system via iRMC S2 .General procedure Remote installation of the operating system 11. 4. for example. However. 464 iRMC S2 . Optimize mouse pointer synchronization in the AVR window (only necessary under Linux). if you install using the Installation Manager then all configuration and installation steps can be performed using the mouse. This means that you can. – All the Installation Manager functions are available to you during installation. you are advised to install Windows via the Installation Manager for the following reasons: – The Installation Manager itself identifies the required drivers and copies these to the system. The following steps are required in order to perform an installation via the Installation Manager: 1. In contrast. – Installations without the Installation Manager have to be controlled via the keyboard since the mouse cursor cannot be synchronized during the installation process. Installing Windows without the Installation Manager using the Windows installation CD/DVDs You can perform a remote installation of Windows via Remote Storage either using the Installation Manager or exclusively using the Windows installation CD/DVDs. Use the Installation Manager at the remote workstation to install the operating system on the administered server. the remote installation of the operating system via iRMC S2 represents a local configuration and installation of the operating system on the administered server which you perform from the remote workstation via the AVR window using remote storage media. Boot and configure the managed server via DVD 1 or the Installation Manager boot image.general procedure For the Installation Manager. 3. The two procedures correspond in terms of the handling of the remote storage media. Connect the storage medium (DVD 1 or Installation Manager boot image) from which you want to boot as remote storage. 2. configure the entire system including the server management settings.

iRMC S2 465 .Remote installation of the operating system General procedure – If you install without the Installation Manager then all the settings required for mouse cursor synchronization must subsequently be performed manually. – Installation using the Installation Manager does not take significantly longer than installation using the operating system CD/DVDs. If the installation requires you to integrate drivers from the floppy disk then. Installing Linux without the Installation Manager using the Linux installation CD/DVD If you know which drivers are required by the system then you can start the Linux installation by booting from the Linux installation CD/DVD. before starting the installation. you must set up a remote storage connection – to the storage medium (CD-ROM/DVD-ROM or ISO image) from which you want to boot and – if necessary to storage medium for driver installation.

– Image file provided centrally in the network by means of a remote storage server. For detailed information on remote storage. The image file may also be on a network drive (with drive letter. see chapter “Remote Storage” on page 191. 466 iRMC S2 .2 Connecting a storage medium as remote storage Remote Storage makes a “virtual” drive available which is located elsewhere in the network.Remote storage connection Remote installation of the operating system 11. e. It is not possible to establish concurrent Remote Storage connections via an applet and via the Remote Storage server.g. The source for the virtual drive can be: – Physical drive or image file at the remote workstation. I The Remote Storage page of the iRMC S2 web interface allows you to obtain information on the status of the current remote storage connections (see page 366). I Parallel remote storage connections: The following are possible concurrently: – either up to two Remote Storage connections to virtual drives at the remote workstation (if the connection is established over the AVR Java applet) or – one Remote Storage connection to a Remote Storage server. “D:” for drive D).

Ê Start “Remote Storage” in the AVR window (see page 193). iRMC S2 467 . Ê Open the Advanced Video Redirection (AVR) page and start the AVR (see page 356).Remote installation of the operating system Remote storage connection Connecting a storage medium as remote storage at the remote storage workstation The following device types are supported when you boot from a virtual drive located at the remote workstation: – – – – – Floppy disk (physical storage medium)) CD-ROM (physical storage medium) DVD-ROM (physical storage medium) ISO image (image file) USB memory stick (emulates a floppy) Proceed as follows at the remote workstation to establish the remote storage connection: Ê Log into the iRMC S2 web interface with Remote Storage Enabled permission (see page 222).

Figure 245: Storage Devices dialog box: ServerView Suite DVD 1 Ê Click Connect to connect the DVD ROM drive (DVD 1) or the Installation Manager boot image as remote storage. I It is recommended that the PRIMERGY 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 Remote Storage or provided via a Remote Storage server. – If installation is performed from the vendor’s installation CD/DVD: Windows or Linux installation CD/DVD and optional drivers. The prepared storage media are displayed in the Storage Devices dialog box. 468 iRMC S2 .Remote storage connection Remote installation of the operating system Ê Prepare the storage media for remote storage (see page 196): – If installation is performed via the Installation Manager: PRIMERGY ServerView Suite DVD 1 or an Installation Manager boot image and optionally a formatted USB memory stick as a status backup medium.

iRMC S2 469 . I Before it is possible to use a virtual drive provided via a remote storage server. the remote storage server must be installed and started (see section “Providing remote storage via a Remote Storage server” on page 206).Remote installation of the operating system Remote storage connection Connect the ISO image (image file) provided by the remote storage server as remote storage You can use an image file provided via the remote storage server for booting from an Installation Manager boot image. To establish the connection to the remote storage server. proceed as follows at the remote workstation: Ê Log into the iRMC S2 web interface with Remote Storage Enabled permission (see page 222). Ê Establish the connection to the remote storage server (see page 367). Ê Select the Remote Storage page.

You can follow the progress of the boot process in the AVR window. 470 iRMC S2 .3 Booting the managed server from PRIMERGY ServerView Suite DVD 1 and configuring it with the Installation Manager Proceed as follows at the remote workstation: Ê Use the iRMC S2 web interface to start up the managed server or reboot the server (see page 265).Booting from DVD 1 Remote installation of the operating system 11. Remote Storage storage media are represented by the following entries in the BOS boot sequence (see figure 246 on page 471): – A (physical) floppy disk is represented by a separate entry “FTS RemoteStorage FD-(USB 2. I If a local CD-ROM/DVD-ROM drive and a CD-ROM/DVD-ROM Ê Press [F2] while the server is booting. Ê In the BIOS set-up. drive connected as remote storage are both present at the managed server then the managed server boots from the Remote Storage CD-ROM/DVD-ROM drive.0)”. open the menu Boot in which you can define the boot sequence.0 devices. Ê Specify the boot sequence as indicated in figure 246 on page 471. – All other remote storage device types are represented by the shared entry “CD-ROM DRIVE”. During the managed server’s BIOS POST phase. remote storage media are displayed as USB 2.

iRMC S2 471 . Ê Make sure that the correct boot sequence is specified. I If the system does not boot from the remote storage medium (PRIMERGY 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 remote storage if necessary.Remote installation of the operating system Booting from DVD 1 Figure 246: Boot Sequence menu in the BIOS setup Ê Save your settings and exit the BIOS setup. The managed server then boots from PRIMERGY ServerView Suite DVD 1 which is connected as remote storage.

Booting from DVD 1 Remote installation of the operating system It takes about 5 minutes to boot from PRIMERGY ServerView Suite DVD 1 via a remote storage medium. 472 iRMC S2 . For more detailed information on synchronizing the mouse cursor in the AVR window. Once the boot process has completed. The following window is displayed during the boot process: Figure 247: The managed server is booted from PRIMERGY ServerView Suite DVD 1. I Before you start to install the operating system. a dialog box is displayed in which you are asked to select a medium for the status backup area (status backup medium) (see figure 248 on page 473). see section “Synchronizing the mouse pointer” on page 175. you should synchronize the local mouse cursor and the cursor of the managed server in the AVR window at the remote workstation (see figure 248 on page 473).

Ê Specify whether the configuration data is to be stored on a local replaceable data medium or on a network medium: I Please note that if you do not select any status backup option all the configuration data is lost when you reboot. The mouse pointers are synchronized when they completely overlap and are displayed as a single mouse pointer .Remote installation of the operating system Booting from DVD 1 (3) (1) (2) Press the Mouse Sync key (1) (2) (3) Status backup options or Drag the local mouse pointer to the top-left corner. iRMC S2 473 . The server’s mouse pointer follows automatically. Figure 248: Installation Manager: Selecting the status backup medium Ê Choose Standard mode as the Installation Manager mode.

Depending on your infrastructure. you have to choose this option. Ê Choose the option on local drive (floppy / USB stick). 474 iRMC S2 . you can either obtain a temporary IP address via DHCP or manually configure an IPv4 or IPv6 address for the current Installation Manager session. Connecting the status medium and/or the installation media via the network Ê Set up the required shares for this purpose. Ê Select the corresponding drive in the box to the right of this option. I If you are making a medium with a prepared configuration file and/or an installation medium available via the network. see the manual “PRIMERGY ServerView Suite ServerView Installation Manager”. Ê Start the Installation Manager by clicking Continue. If you fail to do this and wish to save the configuration file: Connect the USB stick now and reboot from PRIMERGY ServerView Suite DVD 1.Booting from DVD 1 Status backup medium Remote installation of the operating system I The backup medium must not be write-protected. For more detailed information on creating Installation Manager status disks. A USB stick must already be connected to the USB port when the system is booted.

Welcome screen iRMC S2 475 .Remote installation of the operating system Starting local deployment Booting from DVD 1 The Welcome screen appears when you start the Installation Manager: Figure 249: Installation Manager .

476 iRMC S2 . 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. Once you have completed configuration with the Installation Manager. This allows you to start the installation process. To prepare the installation. I 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 remote storage (see section “Installing Windows on the managed server after configuration” on page 477). the Installation Info dialog page for the Windows installation (see page 477) or for the Linux installation (see page 481) is displayed.Booting from DVD 1 Remote installation of the operating system Ê Click Deployment to start preparation of the local installation (deployment).

4.Remote installation of the operating system Windows 11. you should install the operating system on the managed server.Start installation iRMC S2 477 . 11.4 Installing the operating system on the managed server after configuration Once you have completed configuration.1 Installing Windows on the managed server after configuration After configuration has been completed. the Installation Manager displays the following dialog page: Figure 250: Installation Manager .

shut down the current remote storage connections. To do this. 478 iRMC S2 . Ê Connect the CD ROM/DVD ROM drive containing the Windows installation CD/DVD as remote storage (see page 200). see page 204. The Installation Manager opens a confirmation dialog page when the copy operation is complete and prompts you to remove all the storage media from the removable media drives before the managed server is rebooted. Ê Remove PRIMERGY ServerView Suite DVD 1 from the DVD ROM drive at the remote workstation. I Close the application if autostart is active. The Storage Devices dialog box is displayed with the currently connected storage devices and a “Safe Remove” indication (see figure 251 on page 479).Windows Remote installation of the operating system If you have configured the local CD ROM/DVD ROM drive of the managed server as the installation source. Ê Click Start installation. Ê Before rebooting the system. proceed as follows at the remote workstation: Ê Clear your currently active remote storage connections. proceed as follows: Ê Start “Remote Storage” (see page 193). I Before rebooting the system. All the installation files are copied to the managed server. Ê Insert the Windows installation CD/DVD in this DVD ROM drive. For more detailed information on clearing remote storage connections. you must in particular shut down all current remote storage connections.

to remove all the remote storage connections. Ê On the confirmation dialog page.e..Remote installation of the operating system Windows Figure 251: Storage Devices dialog box: Clearing Remote Storage connections Ê “Safely remove” the storage device. Ê Click on Disconnect. i.. Once the managed server has rebooted. ensure that no more applications/programs are accessing the storage media. you can monitor the entire installation by means of the AVR (see figure 252 on page 480). iRMC S2 479 . click Ok to reboot the managed server.

see section “Managed Windows server: Adjusting the settings for synchronization of the mouse pointers” on page 177. 480 iRMC S2 . If Windows is installed using the Installation Manager. you must adapt the following settings at the managed server once the operating system has been installed: – Speed of the mouse pointer – Hardware acceleration For information on how to do this. problem-free synchronization of the mouse pointers is automatically ensured.Windows Remote installation of the operating system Figure 252: Monitoring the Windows installation in the AVR window I For a Windows installation from the Windows installation CD/DVD: To ensure perfect mouse cursor synchronization.

Start installation If you have configured the local CD ROM/DVD ROM drive of the managed server as the installation source.2 Installing Linux on the managed server after configuration I The mouse can be used but not synchronized during Linux installation. the Installation Manager displays the following dialog page: remote storage connection for the currently connected medium and then connect the new medium as remote storage. you must remove the After configuration has been completed. I Whenever you change a remote storage medium.4.Remote installation of the operating system Linux 11. Figure 253: Installation Manager . proceed as follows at the remote workstation: iRMC S2 481 .

All the installation files are copied to the managed server. Ê Connect the CD ROM/DVD ROM drive containing the Linux installation CD/DVD as remote storage (see page 200). proceed as follows: Ê Start “Remote Storage” (see page 193). I Close the application if autostart is active. you must in particular shut down all current remote storage connections. To do this. I Before rebooting the system.Linux Remote installation of the operating system Ê Clear your currently active remote storage connections. see page 204. Ê Insert the Linux installation CD/DVD in this DVD ROM drive. Ê Remove PRIMERGY ServerView Suite DVD 1 from the DVD ROM drive at the remote workstation. Ê Click Start installation. The Storage Devices dialog box is displayed with the currently connected storage devices and a “Safe Remove” indication (see figure 251 on page 479). The Installation Manager opens a confirmation dialog page when the copy operation is complete and prompts you to remove all the storage media from the removable media drives before the managed server is rebooted. shut down the current remote storage connections. Ê Before rebooting the system. For more detailed information on clearing remote storage connections. 482 iRMC S2 .

you can monitor the entire installation by means of the AVR (see figure 255 on page 484). i. Ê “Safely remove” the storage device.Remote installation of the operating system Linux Figure 254: Storage Devices dialog box: Clearing Remote Storage connections Ê Click on Disconnect. ensure that no more applications/programs are accessing the storage media. to remove all the remote storage connections. iRMC S2 483 .e. click Ok to reboot the managed server. Once the managed server has rebooted.. Ê On the confirmation dialog page..

484 iRMC S2 .Linux Remote installation of the operating system Figure 255: The managed server is booted from the Linux installation CD.

you must adapt the required settings at the managed server once the operating system has been installed. iRMC S2 485 . For information on how to do this.License Agreement I To ensure perfect mouse cursor synchronization. see section “Managed Linux server: Adjusting the settings for synchronization of the mouse pointers” on page 180.Remote installation of the operating system The following dialog page is displayed once booting is complete: Linux Figure 256: Linux Installation .

.

12 IPMI OEM Commands This section describes a selection of OEM-specific IPMI commands supported by the iRMC S2.1 ● Overview The following OEM-specific IPMI commands are supported by the iRMC S2: SCCI-compliant Power On/Off commands (SCCI: ServerView Common Command Interface) – 0115 Get Power On Source – 0116 Get Power Off Source – 011C Set Power Off Inhibit – 011D Get Power Off Inhibit – 0120 Set Next Power On Time ● SCCI-compliant communication commands – 0205 System OS Shutdown Request – 0206 System OS Shutdown Request and Reset – 0208 Agent Connect Status – 0209 Shutdown Request Canceled ● SCCI-compliant signaling commands – 1002 Write to System Display ● Firmware-specific commands – 2004 Set Firmware Selector – 2005 Get Firmware Selector – C019 Get Remote Storage Connection – C01A Set Video Display on/off iRMC S2 487 . 12.

Overview ● IPMI OEM Commands BIOS-specific command – F109 Get BIOS POST State – F115 Get CPU Info ● iRMC S2-specific commands – F510 Get System Status – F512 Get EEPROM Version Info – F543 Get SEL entry long text – F545 Get SEL entry text – F5B0 Set Identify LED – F5B1 Get Identify LED – F5B3 Get Error LED – F5DF Set Nonvolatile Cfg Memory to Default Values – F5E0 Set Configuration Space to Default Values – F5F8 Delete User ID 488 iRMC S2 .

The IPMI standard describes the IPMI commands using command tables which list the input and output parameters for each command.2.htm iRMC S2 489 .1 Description format The OEM-specific IPMI commands contained in this chapter are described in the format used by the IPMI standard for describing IPMI commands.IPMI OEM commands Description format 12.com/design/servers/ipmi/index.intel. 12. You can find information on the IPMI standards on the Internet under: http://developer.2 Description of the IPMI OEM commands The following sections describe the individual OEM-specific IPMI commands.

.SCCI-compliant Power On/Off commands IPMI OEM Commands 12.. LS byte first 80 28 00 15 BC 01 Command Specifier Completion Code 80 28 00 01 IANA-Enterprise-Number FTS. Request Data 1:3 4 Response Data 1 2:4 3 4 B8 01 NetFnlLUN: OEM/Group Cmd : Command Group Communication IANA-Enterprise-Number FTS.2 SCCI-compliant Power On/Off commands 01 15 .) Reboot after a CPU error Reboot by hardware reset Reboot after warm start Powered on by a PCI Bus Power Management Event Powered on by remote control via remote manager Reboot/reset by remote control via remote manager 490 iRMC S2 . SCSI termination power.Get Power On Source This command returns the reason for the most recent Power On. LAN. LS byte first Data Length Power on Source: Cause of last power on Power on Source 0x00 0x01 0x02 0x03 0x04 0x05 0x08 0x09 0x0C 0x15 0x16 0x1A 0x1D 0x1E Description Software or command Power switch (on the front panel or keyboard) Automatic restart after power failure Clock or timer (hardware RTC or software timer) Automatic restart after fan failure shutdown Automatic restart after critical temperature shutdown Reboot after watchdog timeout Remote on (modem RI line. The possible reasons are listed below. chip card reader.2.

LS byte first Data Length Cause of last power off Power off Source: Power off Source 0x00 0x01 0x02 0x03 0x04 0x05 0x08 0x0C 0x1D Description Software (SWOFF. The possible reasons are listed below. LS byte first 80 28 00 16 BC 01 Command Specifier Completion Code 80 28 00 01 IANA-Enterprise-Number FTS. Request Data 1:3 4 Response Data 1 2:4 3 4 B8 01 NetFnlLUN: OEM/Group Cmd : Command Group Communication IANA-Enterprise-Number FTS.Get Power Off Source SCCI-compliant Power On/Off commands This command returns the reason for the most recent Power Off.IPMI OEM Commands 01 16 . power off by command) Power switch (on the front panel or keyboard) AC power fail Clock or timer (hardware RTC or software timer) Fan failure Critical temperature Final power-off after repeated watchdog timeouts Final power-off after repeated CPU errors Powered off by remote control via remote manager iRMC S2 491 .

Set Power Off Inhibit IPMI OEM Commands This command sets the Power Off Inhibit flag. The effect of the Power Off Inhibit flag is the same as that of the Dump flag used when creating a main memory dump. In this case. “Power Cycle” or restart of the server. The cause of the most recent attempt to perform a “Power Off”. If the Power Off Inhibit flag is set. LS Byte first 80 28 00 1C 00 Command Specifier Object ID 00 00 Value ID 01 Data Length Power Off Inhibit Flag: 0 no Inhibit. but does not perform the action. Request Data 1:3 4 5 6:7 8 9 Response Data 1 2:4 B8 01 NetFn|LUN: OEM/Group Cmd : Command Group Communication IANA-Enterprise-Number FTS. which temporarily suppresses any unfounded attempt to power down the server. The stored action is only performed when the Power Off Inhibit flag is reset.SCCI-compliant Power On/Off commands 01 1C . “Power Cycle” or restart of the server is always saved at any given time. the firmware saves the cause of any attempt to perform a “Power Off”. 1 Inhibit BC 01 Completion Code 80 28 00 IANA-Enterprise-Number FTS. the initiator must set the flag before making the dump and reset it when the dump is complete. The Power Off Inhibit flag is automatically reset after a power failure or when the reset button is pressed. LS Byte first 492 iRMC S2 .

Set Power Off Inhibit” on page 492 Request Data 1:3 4 Response Data 1 2:4 5 6 B8 01 NetFn|LUN: OEM/Group Cmd : Command Group Communication IANA-Enterprise-Number FTS. LS Byte first 80 28 00 1D BC 01 Command Specifier Completion Code 80 28 00 IANA-Enterprise-Number FTS. LS Byte first 01 Response Data Length Power Off Inhibit Flag: 0 no Inhibit. see the description of “01 1C .Get Power Off Inhibit SCCI-compliant Power On/Off commands This command gets the value of the Power Off Inhibit flag. For further details on the Power Off Inhibit flag. 1 Inhibit iRMC S2 493 .IPMI OEM Commands 01 1D .

Resolution is 1 minute.Set Next Power On Time IPMI OEM Commands This command switches on a system at the given time independent of the stored On/Off times in the Configuration Space. If Time == 0. 494 iRMC S2 . LS byte first Time (LSB first) Time (UNIX-specific format) when the system switches on again. Request Data 1:3 4 5 6:7 8 9:12 Response Data 1 2:4 B8 01 NetFnlLUN: OEM/Group Cmd : Command Group Communication IANA-Enterprise-Number FTS. After the system has switched on. Time is NOT stored in non-volatile memory. Time is set to 0 internally. LS byte first 80 28 00 20 00 Command Specifier Object ID 00 00 Value ID 04 Data Length Time (LSB first) (see below) BC 01 Completion Code 80 28 00 IANA-Enterprise-Number FTS.SCCI-compliant Power On/Off commands 01 20 . I The command takes effect only once. the system is not switched on. You cancel a “Power On” time previously set with a 01 20 command by specifying the “Power On” time “0” in a subsequent 01 20 command.

Request Data 1:3 4 Response Data 1 2:4 B8 02 NetFnlLUN: OEM/Group Cmd : Command Group Communication IANA-Enterprise-Number FTS. the iRMC S2 communicates with Agent which finally performs the action.IPMI OEM commands SCCI-compliant communication commands 12.2. LS byte first 80 28 00 06 BC 02 Command Specifier Completion Code 80 28 00 IANA-Enterprise-Number FTS.System OS Shutdown Request This command initiates shutdown of the server’s operating system. LS byte first iRMC S2 495 . LS byte first 02 06 .System OS Shutdown Request and Reset This command initiates the shutdown of the server’s operating system and subsequently restarts the system. Request Data 1:3 4 Response Data 1 2:4 B8 02 NetFnlLUN: OEM/Group Cmd : Command Group Communication IANA-Enterprise-Number FTS. 02 05 . To execute the commands.3 SCCI-compliant communication commands I Die SCCI-compliant communication commands require that the Agent Service is running under the OS. LS byte first 80 28 00 05 BC 02 Command Specifier Completion Code 80 28 00 IANA-Enterprise-Number FTS.

Request Data 1:3 4 Response Data 1 2:4 5 6 B8 02 NetFnlLUN: OEM/Group IPMI OEM commands Cmd : Command Group Communication IANA-Enterprise-Number FTS. Request Data 1:3 4 Response Data 1 2:4 B8 02 NetFnlLUN: OEM/Group Cmd : Command Group Communication IANA-Enterprise-Number FTS. agent connected. LS byte first Data Length Connect Status: 00 = Connection lost.SCCI-compliant communication commands 02 08 . 01 = Connection re-established. LS byte first 496 iRMC S2 . LS byte first 80 28 00 09 BC 02 Command Specifier Completion Code 80 28 00 IANA-Enterprise-Number FTS. LS byte first 80 28 00 08 BC 02 Command Specifier Completion Code 80 28 00 01 IANA-Enterprise-Number FTS.Agent Connect Status This command checks whether the agent is active. 02 09 Shutdown Request Cancelled This command cancels a shutdown request that has been issued. agent not connected.

Request Data 1:3 4 5 6:7 8 B8 10 NetFnlLUN: OEM/Group Cmd : Command Group Fan Test IANA-Enterprise-Number FTS. Value ID (not used) Length Number of characters to write. 1 = Write String centered. characters exceeding the length of a display line are truncated. string need not be nullterminated. (The string need not be null-terminated. BC 10 Completion Code 80 28 00 IANA-Enterprise-Number FTS.IPMI OEM commands SCCI-compliant signaling command 12.) Attribute: 0 = Write String left aligned.4 SCCI-compliant signaling command 10 02 . LS byte first 80 28 00 02 Command Specifier Object Index: : Line on Display to write on.Write to System Display This command is used to write characters to the LocalView display (if connected). incremented by one.2. Characters to write to the display. LS byte first 9 10:10+n Response Data 1 2:4 iRMC S2 497 .

) 24 04 Completion Code Response Data 1 498 iRMC S2 .Firmware-specific commands IPMI OEM Commands 12.5 Firmware-specific commands 20 04 .) 1 = low firmware image 2 = high firmware image 3 = Auto oldest version (Select firmware image with oldest firmware version.Set Firmware Selector This command configures the firmware image of the iRMC S2 which is to be active after a firmware reset. Request Data 1 20 04 NetFnlLUN: Firmware CMD : Command Group Firmware Selector: 0 = Auto (Select firmware image with highest firmware version.) 4 = MRP (Select most recently programmed firmware.2.) 5 = LRP (Select least recently programmed firmware.

) 1 = low EEPROM 2 = high EEPROM 3 = Auto oldest version (Select EEPROM oldest firmware version.) 4 = MRP (Select most recently programmed firmware.) 5 = LRP (Select least recently programmed firmware. Request Data Response Data 1 2 20 05 24 05 Completion Code Next Boot Selector: 0 = Auto (Select EEPROM with highest firmware version.) Running Selector.IPMI OEM Commands 20 05 . tells which firmware is currently running: 1 = low EEPROM 2 = high EEPROM NetFnlLUN: Firmware CMD : Command Group Firmware 3 iRMC S2 499 .Get Firmware Selector Firmware-specific commands This command returns the current firmware selector setting.

Request Data 1 2 3 Response Data 1 2 3 4 5 C0 19 01 00 00 C4 19 Completion Code 01 00: No 01: Yes.Firmware-specific commands C0 19 . connected 00 00 NetFnlLUN: OEM CMD : Command Group Firmware 500 iRMC S2 .Get Remote Storage Connection or Status IPMI OEM Commands Depending on the parameters passed. the command returns information as to whether storage media are connected as Remote Storage. – the status and type of any Remote Storage connection(s). If Request Data 1 is set to “1”. this command returns information on – whether any Remote Storage connections are available.

Set Video Display On/Off This command allows you to switch the local console on or off. the command returns information on the status and type of any Remote Storage connection(s).IPMI OEM Commands Firmware-specific commands If Request Data 1 is set to “2”. Request Data 1 Response Data 1 C0 1A NetFnlLUN: OEM Cmd : Command Group Fan Test 00 = Set Video Display On 01 = Set Video display Off C4 1A Completion Code iRMC S2 501 . Request Data 1 2 3 Response Data 1 2 3 4 5 C0 19 02 00 00 = Connection 0 01 = Connection 2 C4 19 Completion Code 02 00 00 00 = Invalid / unknown 01 = idle 02 = Connection Attempt pending 03 = Connected 04 = Connection Attempts retries exhausted / failed 05 = Connection lost 06 = Disconnect pending 00 = Invalid / unknown 01 = Storage Server / IPMI 02 = Applet 03 = None / Not connected NetFnlLUN: OEM CMD : Command Group Firmware 6 C0 1A .

Request Data 1:3 4 Response Data 1 2:4 5 B8 F1 NetFnlLUN: OEM/Group Cmd : Command Group BIOS IANA-Enterprise-Number FTS.BIOS-specific commands IPMI OEM commands 12.BIOS POST State : 0 = BIOS is not in POST 1 = BIOS is in POST 502 iRMC S2 .2.Get BIOS POST State This command provides information whether BIOS is in POST.reserved [0] . LS Byte first 80 28 00 09 BC F1 Command Specifier Completion Code 80 28 00 IANA-Enterprise-Number FTS.6 BIOS-specific commands F1 09 . LS Byte first [7:1] .

LS Byte first 80 28 00 15 Command Specifier Socket Number (0-based) of the CPU BC F1 Completion Code: 01 = Unpopulated CPU Socket 80 28 00 IANA-Enterprise-Number FTS. LS Byte first Record ID Fan Control SDR.Get CPU Info BIOS-specific commands This command returns CPU-internal information. LS Byte first Platform ID Brand ID Maximal Core Speed of the CPU [MHz]. LS Byte first (0 if none) iRMC S2 503 . LS Byte first T-Control Offset T-Diode Offset CPU data Spare Record ID CPU Info SDR. The iRMC S2 gets this information from the BIOS during the POST phase. LS Byte first CPU ID. LS Byte first CPU ID High Word. LS Byte first Intel Qickpath Interconnect in Mega Transactions per second. Request Data 1:3 4 5 Response Data 1 2:4 5:6 7 8 9:10 11:12 13 14 15 16:17 18:19 20:21 B8 F1 NetFnlLUN: OEM/Group Cmd : Command Group BIOS IANA-Enterprise-Number FTS.IPMI OEM commands F1 15 .

etc.7 iRMC S2-specific commands F5 10 .Watchdog active Bit 1 .) POST Code I The Timestamp is only relevant for evaluating the Notifications Byte. LS byte first System Status (For details see below. Request Data 1:3 4 5:8 Response Data 1 2:4 5 6 7 8 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group Memory IANA-Enterprise-Number FTS.iRMC-specific commands IPMI OEM commands 12.System ON Bit 6 Bit 5 Bit 4 .Agent connected Bit 0 .Post State 504 iRMC S2 .Get System Status This command returns a variety of internal information on the system such as the power state.) Notifications (For details see below.SEL entries available Bit 3 Bit 2 . error status. System Status Bit 7 .2. LS byte first 80 28 00 10 Command Specifier Timestamp BC F5 Completion Code 80 28 00 IANA-Enterprise-Number FTS.) Signaling (For details see below.

SEL Modified (SEL Cleared) Bit 5 SDR Modified Bit 4 .New Output on LocalView display iRMC S2 505 .CSS LED Bit 2 .CSS LED Bit 1 .IPMI OEM commands iRMC-specific commands Signaling Bit 7 .SEL Modified (New SEL Entry) Bit 6 .Global Error LED Bit 0 .Global Error LED Notifications Bit 7 .Nonvolatile IPMI Variable Modified Bit 3 .ConfigSpace Modified Bit 2 Bit 1 Bit 0 .Localize LED Bit 6 Bit 5 Bit 4 Bit 3 .

Request Data 1:3 4 5 Response Data 1 2:4 5 6 7 8:10 11 12 13 14 15 16 17 18 19:20 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group Memory IANA-Enterprise-Number FTS.) ASCII coded letter BCD coded BCD coded ASCII coded letter LSB binary coded MSB binary coded Binary coded BCD coded Binary coded (major/minor) Major FW Revision Minor FW Revision Aux. Booter Revision 506 iRMC S2 . 01=EEPROM 2 BC F5 Completion Code 80 28 00 Status IANA-Enterprise-Number FTS. firmware and SDR) stored in the EEPROM(s). LS byte first 00=Checksum Error Runtime FW.iRMC-specific commands F5 12 . LS byte first 80 28 00 12 Command Specifier EEPROM# 00=EEPROM 1. SDRR-ID SDRR-ID Major Booter Revision Major Booter Revision Aux. 01=OK Binary coded BCD coded Binary coded (major/minor/res. FW Revision Major FW Revision Major SDRR Revision Minor SDRR Revision SDRR Revision Char.Get EEPROM Version Info IPMI OEM commands This command returns information on the current versions (bootloader.

IPMI OEM commands F5 43 . LS Byte first Next Record ID Actual Record ID Record type Timestamp Severity: Bit 7: Bit 6-4: 0 = No CSS component 1 = CSS component 000 = INFORMATIONAL 001 = MINOR 010 = MAJOR 011 = CRITICAL 1xx = Unknown’ reserved. LS Byte first 0x0000: get first record 0xFFFF: get last record in response SEL text size of Converted SEL data (16:n) in response 80 28 00 43 Record ID 7 8 Response Data 1 2:4 5:6 7:8 9 10:13 14 Offset MaxResponseDataSize BC F5 Completion Code: 80 28 00 IANA-Enterprise-Number FTS. read as 0000 Bit 3-0: 15 16:n n+1 Data length of the whole text requested part (n = 16 + MaxResponseDataSize .1) trailing '\0' character Converted SEL data String Terminator iRMC S2 507 . LS Byte first Command Specifier of SEL record.Get SEL entry long text iRMC-specific commands This command translates a given SEL entry into long text. Request Data 1:3 4 5:6 B8 F5 NetFn|LUN: OEM/Group Cmd : Command Group iRMC IANA-Enterprise-Number FTS.

LS Byte first Next Record ID Actual Record ID Record type Timestamp Severity: Bit 7: Bit 6-4: 0 = No CSS component 1 = CSS component 000 = INFORMATIONAL 001 = MINOR 010 = MAJOR 011 = CRITICAL 1xx = Unknown’ reserved. LS Byte first BC F5 Completion Code 80 28 00 IANA-Enterprise-Number FTS.Get SEL Entry Text IPMI OEM commands This command translates a given System Event Log SEL entry into ASCII text. LS Byte first 80 28 00 45 Command Specifier Record ID of SDR. Request Data 1:3 4 5:6 Response Data 1 2:4 5:6 7:8 9 10:13 14 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group iRMC IANA-Enterprise-Number FTS. read as 0000 Bit 3-0: 15 16:35 Data length Converted SEL data 508 iRMC S2 .iRMC-specific commands F5 45 .

LS byte first 80 28 00 B0 Command Specifier Identify LED: 0: Identify LED off 1: Identify LED on BC F5 Completion Code 80 28 00 IANA-Enterprise-Number FTS. LS byte first 80 28 00 B1 BC F5 Command Specifier Completion Code 80 28 00 IANA-Enterprise-Number FTS.IPMI OEM commands F5 B0 . In addition. I You can also switch the Identify LED on and off using the Identify switch on the server. LS byte first Response Data 1 2:4 F5 B1 . LS byte first State of Identify LED (only bit 0 is relevant) iRMC S2 509 .Set Identify LED iRMC-specific commands This command allows you to switch the Identify LED (blue) of the server on and off. you can set and read the GPIOs that are directly connected to the Identify LED. Request Data 1:3 4 5 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group BMC IANA-Enterprise-Number FTS. Request Data 1:3 4 Response Data 1 2:4 5 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group BMC IANA-Enterprise-Number FTS.Get Identify LED This command returns information on the status of the Identify LED (blue) of the server.

The CSS LED indicates.iRMC-specific commands F5 B3 . Request Data 1:3 4 Response Data 1 2:4 5 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group BMC IANA-Enterprise-Number FTS.Get Error LED IPMI OEM commands This command returns information on the status of the server’s Global Error LED (red) and CSS LED (yellow). LS byte first 80 28 00 B3 BC F5 Command Specifier Completion Code 80 28 00 IANA-Enterprise-Number FTS. LS byte first State of Error LED: 0 : CSS off / GEL off 1 : CSS off / GEL on 2 : CSS off / GEL blink 3 : CSS on / GEL off 4 : CSS on / GEL on 5 : CSS on / GEL blink 6 : CSS blink / GEL off 7 : CSS blink / GEL on 8 : CSS blink / GEL blink 510 iRMC S2 . The Global Error LED indicates the most serious error status of the components. whether the customer himself can rpair the fault.

IPMI OEM commands iRMC-specific commands F5 DF . Request Data 1:3 4 5:8 Response Data 1 2:4 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group BMC IANA-Enterprise-Number FTS. Request Data 1:3 4 5:8 Response Data 1 2:4 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group BMC IANA-Enterprise-Number FTS.Reset Nonvolatile Cfg Variables to Default This command forces all non-volatile IPMI settings to be set to default values. LS byte first iRMC S2 511 .Reset ConfigSpace variables to default This command forces all Configuration Space variables to be set to default values. LS byte first 80 28 00 E0 Command Specifier 43 4C 52 AA = ’CLR’0xaa: Security Code BC F5 Completion Code 80 28 00 IANA-Enterprise-Number FTS. LS byte first 80 28 00 DF Command Specifier 43 4C 52 AA = ’CLR’0xaa: Security Code BC F5 Completion Code 80 28 00 IANA-Enterprise-Number FTS. LS byte first F5 E0 .

V IMPORTANT! The system can no longer be managed if all iRMC S2 users are deleted.iRMC-specific commands F5 F8 . Request Data 1:3 4 5:8 Response Data 1 2:4 B8 F5 NetFnlLUN: OEM/Group Cmd : Command Group BMC IANA-Enterprise-Number FTS. LS byte first 512 iRMC S2 . This command allows individual iRMC S2 users to be deleted. LS byte first 80 28 00 F8 Command Specifier User ID (1-16) BC F5 Completion Code 80 28 00 IANA-Enterprise-Number FTS.Delete User ID IPMI OEM commands The system supports up to 16 users.

The documentation can also be downloaded free of charge from the Internet.fujitsu. [1] ServerView Suite Basic Concepts PRIMERGY Glossary PRIMERGY Abbriviations Secure PRIMERGY Server Management Enterprise Security PRIMERGY server management for secure. highly available platforms White Paper PRIMERGY ServerView Suite Installation Manager User Guide PRIMERGY ServerView Suite Deployment Manager User Guide PRIMERGY ServerView Suite ServerView Operations Manager Installation under Windows Installation Guide PRIMERGY ServerView Suite ServerView Operations Manager Installation under Windows Quick Installation Guide [2] [3] [4] [5] [6] [7] [8] iRMC S2 513 .ts. You will find the online documentation on the Internet at http://manuals.com under the link Industry standard servers.Related Publications The documentation for the PRIMERGY manuals can be found on the PRIMERGY ServerView Suite DVD 2 supplied with each server system.

Related publications [9] PRIMERGY ServerView Suite ServerView Operations Manager Installation under Linux Installation Guide PRIMERGY ServerView Suite ServerView Operations Manager Installation under Linux Quick Installation Guide PRIMERGY ServerView Suite ServerView S2 ServerView Agents (Linux. VMware) Quick Installation Guide PRIMERGY ServerView Suite ServerView Operations Manager Server Management User Guide PRIMERGY ServerView Suite ServerView Inventory Manager User Guide PRIMERGY ServerView Suite ServerView Archive Manager User Guide PRIMERGY ServerView Suite Asset Management Command Line Interface User Guide PRIMERGY ServerView Suite ServerView RAID Manager User Guide PRIMERGY ServerView Suite ServerView Event Manager User Guide [10] [11] [12] [13] [14] [15] [16] [17] 514 iRMC S2 .

Related publications [18] PRIMERGY ServerView Suite ServerView Threshold Manager User Guide PRIMERGY ServerView Suite ServerView Performance Manager User Guide PRIMERGY ServerView Suite ServerView Download Manager ServerView User Guide PRIMERGY ServerView Suite ServerView Update Manager User Guide PRIMERGY ServerView Suite ServerView Update Manager Express User Guide PRIMERGY ServerView Suite PrimeUp User Guide PRIMERGY ServerView Suite Bootable Update CD User Guide PRIMERGY ServerView Suite ServerView Online Diagnostics User Guide PRIMERGY ServerView Suite Local Service Concept (LSC) User Guide PRIMERGY ServerView Suite PrimeCollect User Guide [19] [20] [21] [22] [23] [24] [25] [26] [27] iRMC S2 515 .

Related publications [28] PRIMERGY ServerView Suite ServerView Virtual-IO Manager User Guide PRIMERGY ServerView Suite ServerView Virtual-IO Manager CLI Command Line Interface PRIMERGY ServerView Suite ServerView Integration Overview PRIMERGY ServerView Suite ServerView Integration in MOM User Guide PRIMERGY ServerView Suite ServerView Integration Pack for MS SCOM User Guide PRIMERGY ServerView Suite ServerView Integration Pack for MS SMS User Guide PRIMERGY ServerView Suite DeskView and ServerView Integration Pack for Microsoft SCCM User Guide PRIMERGY ServerView Suite ServerView Integration in HP OpenView NNM User Guide PRIMERGY ServerView Suite ServerView Integration in HP Operations Manager User Guide PRIMERGY ServerView Suite ServerView Integration Pack in Tivoli NetView User Guide PRIMERGY ServerView Suite ServerView Integration Pack in Tivoli TEC User Guide [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] 516 iRMC S2 .

Related publications [39] PRIMERGY ServerView Suite ServerView Integration in DeskView User Guide PRIMERGY ServerView Suite ServerView Remote Management Frontend User guide PRIMERGY ServerView Suite iRMC .integrated Remote Management Controller User Guide PRIMERGY ServerView Suite iRMC S2 .integrated Remote Management Controller User Guide PRIMERGY ServerView Suite Provision of ServerView Software on the Internet Description PRIMERGY BX300 Blade Server Systems Operating Manual PRIMERGY BX600 Blade Server Systems Operating Manual PRIMERGY BX600 Blade Server Systems ServerView Management Blade S3 User Interface Description User Guide PRIMERGY BX900 Blade Server Systems Operating Manual PRIMERGY BX900 Blade Server Systems ServerView Management Blade S1 User Interface Description User Guide PRIMERGY Blade Server System LAN Switch Blade User Interface Description User Guide [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] iRMC S2 517 .

Related publications [50] BIOS-Setup Description PRIMEPOWER ServerView Suite System Administration within a Domain User Guide FibreCAT CX Monitoring FibreCAT SX systems with ServerView Operations Manager Welcome Guide FibreCAT SX Monitoring FibreCAT SX systems with ServerView Operations Manager Welcome Guide StorMan Provisioning and managing virtualized storage resources Administrator and User Guide APC network management card User’s Guide VMware VMware ESX Server Installation Guide VMware VMware ESX Server Administration Guide [51] [52] [53] [54] [55] [56] [57] 518 iRMC S2 .

184 Languages menu 187 Preferences menu 188 Remote Storage menu 187 B BIOS text console 345 BIOS text console redirection configuring 44. 441 configuration using the iRMC S2 web interface 336 configuration using the Server Configuration Manager 441 iRMC S2 groups and user permissions 113 advanced features 412 Advanced Video Redirection see also AVR Advanced Video Redirection (AVR) 356 alert role assigning users 163 alert roles displaying 161 alert types 157 alerting configuring 56. 184 AVR window Extras menu 183. 45. 83. 58. 416 ASR&R Temperature Settings 416 assign iRMC S2 users to a group 113. 59. 313. 140 remote storage server to iRMC S2 367 remote storage server to the iRMC S2 412 assign iRMC S2 users to the OU iRMCgroups in eDirectory 140 Autonomous Support Package see ASP AVR 167 checking requirements 168 integrated special keys 173 Local Monitor Off function 172 menus 183 parallel sessions 171 redirecting the keyboard 171 redirecting the mouse 175 Secure Keyboard 174 special key combinations 173 starting 356 using 170 virtual keyboard 174. 432 analog fans 285 ASP 455 ASR&R Fan Settings 414 ASR&R options configuring 298 ASR&R settings configuring 414. 345 boot iRMC S2 242 boot options configuring 264 boot watchdog 299 C CA (Certification Authority) 108 CA certificate loading from local file 251 CA DSA/RSA certificate showing 249 call Remote Storage server GUI 214 CD ISO image (image file) 197 certificate self-signed 254 Certification Authority (CA) 108 iRMC S2 519 .Index A Active Directory 18.

58. LAN interface 40 configuration using the Server Configuration Manager 401 Active Directory 441 ASR&R Fan Settings 414 ASR&R Temperature Settings 416 calling from the Operations Manager 405 calling from the Windows Start menu 402. 423 HP SIM integration 413 HP SIM-Integration 300 IP parameters (iRMC S2) 418 520 iRMC S2 . 403 eDirectory 441. 416 boot options 264 console redirection 45. 313. 427 configuration file (SVS_LdapDeployer) 96 configuration tools. see CA channel-specific permission group 62 privileges 62 check fan 414 power supply 289 see also Enclosure Information 388 sensors 283 server component 290 temperature sensor 286 temperature sensors 416 voltage sensor 288 check temperature 388 CLP 397 syntax 397 user data 399 CLP. 441 eDirectory for LDAP 129 email alerting 317 Ethernet settings (iRMC S2) 302. 425 eDirectory 128. see also SMASH CLP color code (sensor) 283 Command Line Protocol (CLP) 397 command line shell (Remote Manager) 393 communication interfaces (iRMC S2) 21 component status 290 components (server) monitoring 290 configuration 410.Index certification authority. 345 directory dervice 439 directory service 333. 441 directory service (eDirectory) 340 directory service (OpenLDAP) 340 directory service on the iRMC S2 439 DNS for iRMC S2 311. 443 iRMC advanced features 412 iRMC directory service 439 iRMC DNS registration 423 iRMC DNS server 425 iRMC LAN interface 418 iRMC mail alerting 427 iRMC mail format settings 430 iRMC networking ports 421 iRMC SNMP alerting 432 iRMC user management 433 OpenLDAP 443 power consumption 410 power consumption control 410 requirements 401 starting system configuration 402 user ID (iRMC user management) 433 user ID (iRMC user manangement) 433 configure 427 alerting 56. 432 ASR&R options 298 ASR&R settings 414. 418 global email alerting 160 host name for iRMC S2 309.

301 LAN parameters (iRMC S2) 418 LDAP access on the iRMC S2 108 mail alerting 427 mail-format-dependent settings 321. 333. terminating 204 connection to remote storage server clearing 367 establishing 367 console logging 394 console redirection configuring 345 starting (Remote Manager) 392 while the operating system is running 49. 41. 425 DNS registration 423 DNS server (Server Configuration Manager) 425 DNS settings 311 documentation 14 domain controller 110 domain controller certificate 110. 430 new user 325. 112 DSA certificate default certificate 247 displaying current 249 entering directly 253 restoring default certificate 250 iRMC S2 521 . 433 users. eDirectory. 434 OpenLDAP 148. OpenLDAP directory service see also Directory Service display alert roles 161 current DSA certificate 249 display permission groups 95 display user roles 94 DNS for iRMC S2 configuring 311. 443 ports and network services (iRMC S2) 305. 83. 45. 433 connection to Remote Storage. 421 power consumption 272. 57.Index iRMC S2 37 iRMC S2 over the web interface 55 LAN interface 38. locally 323. 354 ConsoleOne installing 126 starting 127 copyright (SSL) 164 create NDS tree (eDirectory) 128 creating an SSH key pair 70 CSS LED 233 current monitoring 288 current power consumption 278 D default DHCP name (iRMC S2) 34 device type (remote storage) 197 DHCP configuration 309 directory service 18. 433 watchdog settings 299 configure power consumption 272 configure users locally 323. 345 user 325 user (details) 326 users 323. 439 see also Active Directory. 410 power on/off times (server) 269 Remote Storage server 215 serial interface 51 serial/modem alerting 315 server management information 297 SNMP trap alerting 314 system event log (server) 295 text console redirection 44. 278. 55. 59.

iRMC S2 448 firmware selector. 427 email alerting. iRMC S2 34 fan checking 414 testing 285 fan test 285 fans monitoring 284 firmware updating 447 firmware image. see Enterprise CA 108 error icon 291 error list error icon 291 error log error icon 291 Ethernet 302 Ethernet settings (iRMC S2) configure 418 configuring 302. 83. iRMC S2 450 firmware update online update 256. 441. iRMC S2 448 flash tools flirmcs2 455 online update (firmware) 455 rFLIRMCS2 455 sFLIRMCS2 455 syntax and operands 460 WinFLIRMCS2 455 FlashDisk menu actor y defaults. 443 administration tips 144 assigning iRMC S2 users to the OU iRMCgroups 140 configuration using the Server Configuration Manager 441 configuring 128 configuring for LDAP 129 creating Principal User for iRMC 136 iRMC S2 groups and user permissions 136 LDAP authentication process 135 software components and system requirements 120 testing access via LDAP browser 133 eDirectory Server installing 122 email alerting configuring 317. global 156 email configuration 330 email see also mail emergency mode 459 enclosure information (Remote Manager) 387 enter DSA certificate 253 DSA/RSA key 253 Enterprise CA 108 Enterprise Certification authority. 454 operands 460 firmware. 418 execution mode Remote Storage server 213 exit Remote Storage server 218 F factory defaults. 59.Index DSA key (private) entering directly 253 loading on the iRMC S2 247 providing in file 252 DSA/RSA certificate entering directly 253 input format 247 loading on the iRMC S2 247 showing 249 DSA/RSA key entering directly 253 input format 247 DVD ISO image (image file) 197 E eDirectory 18. iRMC S2 121 522 iRMC S2 .

Set Firmware Selector 498 2005 .System OS Shutdown Request and Reset 495 0208 . see also ISO image iManager installing 124 login 125 install ConsoleOne 126 iManager 124 Linux 481 OpenLDAP 147 operating system 463 Remote Storage server 207 iRMC S2 523 .Get Firmware Selector 499 C019 .Index FlashDisk menu offline update (firmware) functions.Agent Connect Status 496 0209 Shutdown Request Cancelled 496 1002 . 413 I ICMB 24 identification LED 234.System OS Shutdown Request 495 0206 .Get Power Off Source 491 011C . see IPMI interfaces (iRMC S2) 21 IPMB 24 IPMI background 22 channel concept 29 definition 22 implementation 24 IPMI-over-LAN interface 27 references 30 Serial Over LAN (SOL) 28 standards 24 user IDs 30 IPMI OEM commands 487 0115 .Set Next Power On Time 494 0205 .Get Power On Source 490 0116 . iRMC S2 15 see also remote installation of the operating system Windows 477 installing eDirectory administration utilities 122 eDirectory Server 122 integrated special keys (AVR) 173 Intelligent Platform Management Interface.Get Remote Storage Connection or Status 500 457 G generate self-signed certificate 254 global email alerting 156 configuring 160 global email paging configuration 318 Global Error LED 233 global iRMC S2 user ID 59 global iRMC S2 user management 83 via Active Directory 107 via eDirectory 120 via OpenLDAP 147 H helpdesk information 296 host name (iRMC S2) 423 configure 423 configuring 309 see also iRMC S2 name HP SIM integration configuring 300.Set Power Off Inhibit 492 0120 . 391 image file (ISO image) 197 image file (ISO/NRG image) 206 image file.Write to System Display 497 2004 .

Index C01A .Get Power Off Inhibit 493 iRMC factory defaults 121 iRMC advanced features 412 iRMC directory service 439 configuring Active Directory 441 configuring eDirectory 443 configuring OpenLDAP 443 configuring the eDirectory 441 iRMC directory service configuration 439 iRMC DNS registration 423 iRMC DNS server (Server Configuration Manager) 425 iRMC LAN interface 418 iRMC mail alerting 427 iRMC mail format settings (Server Configuration Manager) 430 iRMC S2 21 Advanced Video Redirection (AVR) 356 AVR 167 communication interfaces 21 configuring 37 configuring over the web interface 55 configuring the LAN interface 38.Get Error LED 510 F5DF .Reset Nonvolatile Cfg Variables to Default 511 F5E0 .Get BIOS POST State 502 F115 . 360 logging in (requirements) 33 logging into the web interface 35.Get SEL Entry Text 508 F5B0 .Get CPU Info 503 F510 . 448 firmware image 448 firmware image information 257 firmware selector 450 functions 15 license key 167.Get Identify LED 509 F5B3 . 206. 41.Get EEPROM Version Info 506 F543 . 57. 366 Remote Storage server 206 restarting 242 show current power consumption 278 SSH key 74 testing the LAN interface 43 user interface 228 user management 59 user permissions 62 524 iRMC S2 . 222 online update (firmware) 454 permissions 63 power consumption configuration 272 power consumption control 410 power supply 270 remote installation of the operating system 463 remote storage 187.Delete User ID 512 overview 487 IPMI OEMcommands 011D .Get System Status 504 F512 . 55.Get SEL entry long text 507 F545 . 301 configuring the serial interface 51 configuring with the Server Configuration Manager 57 default DHCP name 34 factory defaults 34 firmware 256.Set Identify LED 509 F5B1 .Reset ConfigSpace variables to default 511 F5F8 .Set Video Display On/Off 501 description format 489 F109 . 191. 191 local monitor off 172.

140 iRMC S2 user management global via Active Directory 107 global via eDirectory 120 global via OpenLDAP 147 integrating in OpenLDAP 150 iRMC S2 users assigning 113.voltages 288 server management information 297 structure of the user interface 228 system component information 232. 323 user management (local) 323 user management .temperature 286 sensors . 326 iRMC SNMP alerting 432 iRMC user management 433 iRMCgroups 96 assigning iRMC S2 users (eDirectory) 140 iRMC S2 525 . see configuration using the Server Configuration Manager iRMC S2 firmware settings 245 iRMC S2 information 241 iRMC S2 SSH access 368 iRMC S2 Telnet access 368 iRMC S2 user creating in OpenLDAP 152 iRMC S2 user group assigning 113.serial/modem alerting 315 alerting . 237 system event log 291 system event log configuration 295 system event log content 292 system information 231 user management 64. 140 iRMC S2 web interface 221 Advanced Video Redirection (AVR) 356 alerting 313 alerting .fans 284 sensors .component status 290 sensors .power supply 289 sensors .email alerting 317 alerting .SNMP trap alerting 314 BIOS text console 345 certificate upload 247 configuring iRMC S2 55 configuring power control 278 current power consumption 278 DHCP configuration 309 directory service configuration 333 DNS settings 311 firmware update via TFTP 256 iRMC S2 240 iRMC S2 information 241 iRMC S2 SSH access 368 iRMC S2 Telnet access 368 iRMC S2 Telnet/SSH access 368 local monitor 360 network interface 302 network settings 301 permissions 224 ports and network services 305 power configuration 272 power consumption history 279 power management 261 power on/off 262 power options 267 power supply 270 power supply info 270 remote storage 366 saving firmware settings 245 saving iRMC S2 firmware settings 245 sensors 283 sensors .new user configuration 325 user management .Index iRMC S2 configuration using the Server Configuration Manager.user “name” configuration 325.

see also directory service LDAP-Konfiguration Active Directory 336 license key 167. 301 testing 43 LAN parameters (iRMC S2) configuring 301. special (AVR) 173 keyboard redirect (AVR) 171 virtual (AVR) 174. see server management information. 360 monitor.Index ISO image (image file) 197. see server management information Microsoft Active Directory see Active Directory Microsoft Active Directory see also Active Directory monitor current 288 fans 284 power supply 289 temperature 286 voltage 288 monitor. 222 M mail alerting 427 configuring 427 mail alerting (Server Configuration Manager) 427 mail format settings 430 mail see also email mail-format-dependent configuration 321 main menu (Remote Manager) 380 managed server. 242. see also image file K key combinations. 184 konfigurieren Directory Service (Active Directory) 336 L LAN interface 418 LAN interface (iRMC S2) 39 configuring 38. 360 local user ID (iRMC S2) 59 local user management (iRMC S2) 64. 57. 191. 41. local 172. 243 loading onto the iRMC S2 242. 206 CD 197 DVD 197 ISO image. 55. 412 deleting 242. see check mouse pointer synchronizing 175 mouse redirection (AVR) 175 N Network 302 network interface 302 network settings 301 networking ports 421 526 iRMC S2 . 243 Linux. 418 LDAP access (iRMC S2) configuring 108 LDAP authentication process (eDirectory) 135 LDAP configuration 333 eDirectory 340 OpenLDAP 340 LDAP configuration (using the Server Configuration Manager) 439 LDAP email table 158 LDAP. 243. 323. remote installation 481 local monitor powering on and off 360 switching on and off 172 local monitor display 360 local monitor off 172. 433 log in to iRMC S2 (requirements) 33 to Remote Manager 378 to the iRMC S2 web interface 35.

83. remote installation 463 see also remote installation of the operating system organizational unit iRMCgroups 87. 91 SVS 87. see also privilege permissions for special iRMC S2 functions 63 iRMC S2 web interface 224 Remote Manager 382 ports and network services 305 configuring for iRMC S2 305. 267. 385 behavior after power outage 268 power on/off time 269 power restore policy 268 restart options 265 power off server 265 power on server 265 power on/off 262 power on/off time 269 power options 267 power restore policy 268 power status summary 263 power supply monitoring 289 power supply info 270 preconfigured user ID 63 iRMC S2 527 . 262. 59. 421 power consumption configuring 278 of the server 271 showing for server (current) 278 power consumption configuration 272 power consumption control 410 power consumption history 279 power control 265 power management 261. 94 overview of menus Remote Manager 375 P parallel AVR sessions 171 password changing 383 permission group 91 channel-specific 62 permission groups displaying 95 permission.Index new user configuration 325 notational conventions 32 Novell ConsoleOne see also ConsoleOne Novell eDirectory see also eDirectory Novell eDirectory see eDirectory Novell eDirectory Server see also eDirectory Server Novell eDirectory. 375 iRMC S2 via Telnet/SSH 368 Remote Manager 375 operating system. 443 administration tips 154 configuration using the Server Configuration Manager 443 configuring 148 creating an iRMC S2 user 152 creating SSL certificates 147 generating the Principal User 151 installing 147 integrating iRMC S2 user management 150 iRMC S2 groups and user permissions 150 iRMC S2 user management 147 OpenSSH client 80 operate iRMC S2 using Telnet/SSH 373. see eDirectory Novell iManager see also iManager O online update (firmware) 454 Open LDAP Browser/Editor 150 OpenLDAP 18.

373. channel-specific 62 PuTTY 76 PuTTYgen 70 Q query information on server 232 information on server components 237 iRMC S2 information 241 server management information 297 system information 231 query information information on server 232 iRMC S2 firmware 242 on iRMC S2 241 power supply 289 server components 237 system event log 295 voltage sensors 288 query iRMC S2 information 241 query system information 384 querying iRMC S2 firmware image information 257 querying information iRMC S2 firmware 257 R redirect keyboard (AVR) 171 redirect mouse (AVR) 175 remote installation of the operating system 463 general procedure 464 Linux 481 remote storage connection 466 requirements 463 Windows 477 remote management documentation 14 Remote Manager 368. see DSA/RSA key privilege privileges / permissions 328 privileges. 191. 375 changing the password 383 enclosure information 387 logging in 378 main menu 380 operating 375 overview of menus 375 permissions 382 power management 385 service processor 391 starting console redirection 392 starting the command line shell 393 system information 384 remote manager system event log 389 Remote Manager (Serial) 54 Remote Storage terminating a connection 204 remote storage 187.Index primary SMTP server configuration 319 Principal User creating in eDirectory 136 generating in OpenLDAP 151 private DSA/RSA key. 206. 366 connecting storage media 200 device type 197 providing storage media 196 removing the storage medium 205 starting 193 Remote Storage server 206 calling the GUI 214 configuring 215 executing as a service 213 executing as stand-alone 213 execution mode 213 exiting 218 installing 207 starting 217 528 iRMC S2 .

413 power consumption 272. see DSA/RSA certificate S secondary SMTP server configuration 320 Secure Keyboard (AVR) 174 security group 91 security group. 278 power management 267 power management after power outage 268 power options 267 power supply info 270 powering on and off 265 remote installation (Linux) 481 remote installation (Windows) 477 remote installation of the operating system 463 showing (current) power consumption 278 showing power consumption 279 specifying power on/off time 269 view event log 294 watchdog settings 299 Server Configuration Manager configuring iRMC S2 57 iRMC user management 433 see also configuration using the Server Configuration Manager user management 66 server management information 297 querying and configuring 297 ServerView Update Manager Express see Update Manager Express ServerView Update Manager see Update Manager service 14 service processor (Remote Manager) 391 sFLIRMCS2 online update (firmware) 455 show CA DSA/RSA certificate 249 DSA/RSA certificate 249 show power consumption of the server 279 iRMC S2 529 . see also permission group self-signed certificate 254 sensor checking 283 color code 283 status icon 283 sensors 283 serial/modem alerting 315 configuring 315 serial/modem interface (iRMC S2) 51 configuring 52 Remote Manager (Serial) 54 server ASR&R options 298 booting and configuring with ServerView DVD 1 470 checking components 290 checking sensors 283 configuring settings 297 configuring the event log 295 controlling power consumption 271 HP SIM integration options 300.Index remote storage server assigning 412 requirements AVR 168 iRMC S2 configuration using the Server Configuration Manager 401 remote installation of the operating system 463 restart options 265 rFLIRMCS2 online update (firmware) 455 RSA certificate.

237 querying 231 system information (Remote Manager) 384 T target group 14 Telnet 368. 345 while the operating system is running 49. 96 SVS_LdapDeployer 96 -delete 101 -deploy 99 -import 102 -synchronize 103 application scenarios 105 configuration file 96 starting 97 synchronize mouse pointer 175 system component status status icon 237 system event log 291. 373. 375 SSH key (example) 82 SSH key (public) loading onto the iRMC S2 74 SSHv2 public key 329 SSHv2 public key support 68 SSL 247 SSL and SSH certificate 247 SSL certificate creating 147 SSL copyright 164 start Advanced Video Redirection 356 remote storage 193 Remote Storage server 217 Remote Storage server GUI 214 SVS_LdapDeployer 97 status components 290 status icon system component status 237 status icon (sensor) 283 storage media connecting as remote storage 200 providing for remote storage 196 SVS 94. 375 temperature monitoring 286 temperature sensor checking 286 Temperature Settings (ASR&R) 414. 45. 232. 373. 368. 416 test fan 285 LAN interface 43 text console (logging) 394 text console redirection configuring 44. 294 system information 231. see SNMP trap alerting SNMP trap alerting 314 configuring 314. 354 530 iRMC S2 . 389 configuring 295 information 293 view 294 system event log configuration 295 system event log content 292.Index SMASH CLP 397 command hierarchy 399 commands 397 starting 393 syntax 397 user data 399 SMTP see also email SNMP alerting 432 SNMP alerting. 432 software watchdog 299 special key combinations (AVR) 173 special keys integrated (AVR) 173 SSH 247.

remote installation 477 WinFLIRMCS2 online update (firmware) 455 X X. 59 preconfigured 63 user information 327 user interface (iRMC S2) 228 user management 323. see DSA/RSA certificate iRMC S2 531 .509 certificate. 85 via directory service 85 user management (local) 433 user permissions 62 cross-server 89 global 85. locally 433 V ventilator. 140 concept 60 configuring LDAP access 108 creating a domain controller certificate 110 generating iRMCgroups in the LDAP directory service 96 generating SVS in the LDAP directory service 96 global 83 global user permissions 85. see iRMC S2 web interface Windows. 433 local using the iRMC S2 web interface 323 user management (iRMC S2) 59. 433 configuring (new) 434 configuring locally 433 configuring. see also fan view system event log (server) 294 virtual keyboard (AVR) 174. 184 voltage sensor checking 288 W watchdog settings configuring 299 web interface. 433 assigning users to a group 113.Index U update firmware 447 Update Manager online update (firmware) 454 Update Manager Express online update (firmware) 455 user configuring 325 configuring (details) 326 configuring (new) 325 user “name” configuration 326 user ID 30. 89 installing a domain controller certificate 112 installing an Enterprise CA 108 integrating in eDirectory 134 local 64 local via the iRMC S2 web interface 64 locally using the Server Configuration Manager 433 locally via the Server Configuration Manager 66 preferred shell 93 user ID 59 using Active Directory 83. 89 in Active Directory 113 in eDirectory 136 in OpenLDAP 150 user roles displaying 94 User SSHv2 public key upload from file 329 users configuring 323.