PRIMERGY BX900 Blade Server Systems

ServerView Management Blade S1 User Interface Description

Edition March 2010

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.fujtsu.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 © 2010 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 2 2.1 2.2 2.2.1 2.2.2 2.2.3 3 3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.4.1 3.3.4.2 3.3.4.3 3.3.4.4 3.3.4.5 3.3.4.6 3.3.4.7 3.3.4.8 3.3.5 3.3.6 3.3.7 3.3.8 3.3.9 3.3.9.1 3.3.9.2 3.3.9.3 3.3.9.4 3.3.9.5 3.3.10 3.3.11 3.3.12 3.3.13 3.3.14 3.3.15 3.3.16 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 PRIMERGY BX Blade Server Systems – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 The Blade Server Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Blade Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Features of the ServerView Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Redundancy of the ServerView Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Console Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Telnet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Entering the console mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Console main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Management Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Agent Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade Control Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade Voltage Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade NIC Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade Watch Dog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blue Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Blade Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade Event Log Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade Power On/Off Event Log Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Blade Wrap Around Event Log Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup All Event Log to USB Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set System Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Blade CMOS Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active Directory Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VLAN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I2C Bus Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Blade Configuration Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 17 19 20 21 21 22 22 23 23 23 24 24 25 25 27 29 30 30 31 31 31 31 32 33 34 35 36 37 37

ServerView BX900 S1 Management Blade

3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 4. . . . . . . . . . . . . . . . . . . .6 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . .4. . . . . . . . . . . . . . . . .3. .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5.5. . . . . . . . . . . . . .5. . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . System Unit . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . .2 4. . . . 40 TFTP Update . . . . . . . . . . . . . . . . . . . . . . . .2 4. . . . . . . . . . . . . .2 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 4. . . . . . . . . . . . . . . . . . . . . . . Logging . . . . . . . . . . . . . . . . .4 4. SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . . . . . . . . . . . . . .3. . . . . . .12 4 4. . . System Information Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . . .1 4. .9 3. . . . . . . . . . . . . . . . . . . 45 Login . . . . . . . . . . . . . . . . Firmware Update . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup/Restoration Management – iRMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . .7 4. . . . 41 Logout . . . . . . . . . . Backup/Restoration Management – BIOS . . . . .5. . . . . . . . Global Users . . . .3. . . . . . . . . Connection Blades . . .8 3. . . .4 4. . . . . . . . . . 52 52 52 53 55 57 58 62 62 64 64 64 64 65 65 66 66 66 68 68 68 69 69 69 69 70 71 72 72 72 73 73 73 74 75 76 4 ServerView BX900 S1 Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . Network Interface .3. . . . . . . . . . . . . . . . . . . . . . . . .4 4. . . . . . . . . . . . . . . . . . . . . . . Storage Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . Local Service Display . . . . . . . . . . . . . . . .4 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 3. .3 4. . . .3. . . . . . . . . . . . . . . . . . . . . . . .3 4. .3 4. . .17 3. . . .3. . . . . . . .4. . . . . . . . Event Log . . . . . . . . . . . . . . . . User Certificate . . . . . . . Server Blades . . 44 Web User Interface . . . .5. . . . . . . . . . . . . .3. . . . . . . . . . . . Asset Overview . . . . . . . . . . . . . . . . . . . . System (Status Overview) . . . . . . .6 4. .4. . . . .5. . . . . . .5. . . . . . . . . . . . . . . . . . Rear Fan Units . . . . . . . . . . . . . . . . . Backup/Restoration Management . . . . . . . . . System Certificate . . . . .1. . . . . . Power Supplies . . . . . . .4 Management Blade Base Configuration Backup/Restore . . . . . . . . . .11 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 4. . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 4. . 42 System Information Dump . . . . . . . . . Alerting . 42 Reboot Management Blade . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . 42 Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 4. . . . . . . . . . . . . . . . . . . . .5 4. . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . .2 4. . . . . . . . . . . . . . . . . . . . . . . 46 Components . . . . . . . . . . Dump Post Mortem . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 3. . . . . . . . . . . . . . . . . . . . . . . . . . . 45 The Start Page . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . . .3. . . . 41 Change Management Role To Slave . .6. . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . .5. . . . . New Local User Account . . . . . . Power Management . Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Management . . . . . . . . . . .3 4. . . . . . . . . . . . . . . . . . . . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . . .6 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . .5 4. . . . . . . . . . . 39 Console Redirection . . . . . . . . . . . . . . 38 Emergency Management Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 3. . . .3. . Certificate Handling . . . . . . . . . 43 Account Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Session Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 4. . . . . . . . . .6 3.1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 4. . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . . . . . . . . . . . . . . . . .1. Local Users . . . . . . . . . . . . . . .1 4. . . . . .4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Date Time . . . . .

. . . . . . 82 82 83 84 89 90 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Base Configuration Wizard . . . . . . . . . . . . 76 Language . . . .1 5. . . . . . . . . . . . . . . . . . . 137 ServerView BX900 S1 Management Blade 5 . . . . . . . . . . . . . Software Components . . . . . . . . . . 79 Power Consumption display . . . . . iRMC Integration in eDirectory . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 6 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 5. . . . . . . . . . . . . . . . . . . . . . . . . .1 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation and Setup of eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of eDirectory Server . . . . . . . . . . . . . . . . . . . . . . . .2 6. . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . .3 6. . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 5. . . . . . . . . . . . . .1 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . .1 5. . . .6. . . . . . . . . . . . . . .2 4. . . . . . . . . . . . . . . . . 135 Index . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . .2. . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . 95 Configuring an openLDAP Server . . . . . . . . . . Dynamic Mode . . .3 4. . . . . . . . . . . . . . . . . .3. . Logging in on the Management Blade as an LDAP user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . .4 6. . . . . . . . Settings on the Management Blade . . . . 81 Control via tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration tab . . . . . . . . . . . . . . . Monitoring tab . . . . . . . . . . Configuration of eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . .2 5. . . . . . . . . . . . . . . . . . . . . . 77 Power Management . . . . .6. . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 5.5 6. . . . . . . . . . . . . . . . . . . . .2. . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . .1 6. . . . . . . . . . . . . . .3. . . .3. . . . . . . . . . . . . . . . . . . . . 103 Configuring an eDirectory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . .4 6. . . . . . . . . . . . .3. . . . . . . . . . . .2. . . .6. . . . .5 Refresh . . .3. . . . . .2 6. . . .2 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Related Publications . . . . . . . . . . . . . . . . . . . . . . .4 5 5. . . . . . . . . . . . . 114 114 114 114 114 117 120 122 122 127 128 Abbreviations . . . . Control tab . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . Installation . . .1. . . Configuring the LDAP structure . . . No Dynamic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Configuring an Active Directory Server .

.

see section “Features of the ServerView Management Blade” on page 9. redundant ServerView management blades: an integrated management solution for complete remote administration of the blade server system. For a complete feature list.1 Introduction The PRIMERGY BX Blade Server Systems accommodate two hot-swapable. Figure 1: ServerView management blade – BX900 S1 Further information is provided on the PRIMERGY ServerBooks DVD: – PRIMERGY BX900 Blade Server System – Operating Manual – PRIMERGY Server Systems – RemoteDeploy – PRIMERGY BX Blade Server Systems – LAN Switch Blade – ServerView User Guide I For further information on updating BX components please refer to the Operating Manual of your BX system. ServerView BX900 S1 Management Blade 7 .

Commands to be entered through the keyboard are written in a semi-bold fixed font. 8 ServerView BX900 S1 Management Blade . e. then the Shift key is shown.g. then the chapter or section heading is placed in the reference.2 Target Group This manual is intended for system administrators. Marked variables that must be replaced by current values.[A] for A. [SHIFT] . If there are references to text or sections of text in this manual. System output is written using a fixed font. file names.Notational Conventions Introduction 1. network administrators. This symbol highlights important information and tips. and the page stated refers to the page on which the chapter or section begins. and path names are written in italic letters in text. options. Commands. If capital letters are to be entered explicitly. The following notational conventions are used in this manual: V Caution I Ê italic <variable> fixed font semi-bold fixed font [Key symbols] This symbol refers to a step that you must carry out in order to continue with the procedure. names of buttons. and service technicians that have a basic knowledge of hardware and software. If two keys need to be pressed at the same time. loss of data. 1. Keys are presented according to their representation on the keyboard. The manual informs the reader of the fundamentals of blade server monitoring and documents the requirements for the use of the ServerView management blade. menu items. or damage to equipment.1 Notational Conventions This symbol points out hazards that can lead to personal injury. then this is indicated by placing a hyphen between the two key symbols.

too. the system component is described that enables the user to communicate with the system. 2. and finally a redundantly configured pair of ServerView management blades. The user gets access to the functions provided by the ServerView management blade. All data traffic moving to and from the system is handled via TCP/IP over a LAN cable. Further development has made it necessary to treat the issues of CPU power and storage capacity separately. 2. or via a console menu using the Telnet protocol.2. which are described in this section. Rack optimized servers enable the system administrator to make adjustments in both fields according to the level that is needed. Servers like this are distinguished by the number of CPUs they use. 2. either via a web user interface. together with some switch blades. There are two ServerView management blades in a blade server system. in order to ensure redundancy. ServerView BX900 S1 Management Blade 9 . the blade server concept is reached.1 The Blade Server Concept A traditional server is a device that includes a multitude of components to do many different jobs at the same time. A blade server system typically consists of a number CPU boards. a high density is achieved for the system with very little power consumption compared to traditional servers. At the next step. and the number of PCI cards that can be used to connect them to other devices such as external storage systems or networks. the number of hard disks that can be plugged in. which are the I/O modules. enabling the user to monitor and control the system on the whole. and its major features are described. the user relies on functions provided by a system component called the ServerView management blade. Thus. The concept underlying this system is explained. The outsourcing of the power supply unit and the use of low-voltage CPUs help to reduce the size of a server blade. are separated from the CPU. Controller The ServerView management blade is equipped with an AMCC PPC405EP controller. Furthermore.2 Blade Server Management When performing administrative tasks for the blade server system. where I/O functions.1 Features of the ServerView Management Blade Within the blade server system the ServerView management blade is equipped with a number of features. known as server blades.2 PRIMERGY BX Blade Server Systems – Overview In this chapter an overview is given of the blade server system. Both ways of communication are described in more detail in the next two chapters of this manual (see chapter “Telnet Interface” and chapter “Web User Interface”).

and other impacts on air flow conditions – Setting the the system fans to an optimum speed – Monitoring the status ot the power supply modules – Monitoring the temperature of the switch blades via the I2C bus Event repository To store messages on events that occur in the system environment. 10 ServerView BX900 S1 Management Blade .0.Blade Server Management BX Blade Server System Overview Supported programs The ServerView management blade is compliant with IPMI (Internet Protocol Multicast Iniative) 1. when performing hardware monitoring tasks for the server blades. Hardware monitoring The hardware monitoring functions provided by the ServerView management blade include: – Monitoring voltage and temperature of each server blade via the IPMB interface – Monitoring the status of the system fans – Monitoring intrusion into the system fans. if they have been opened. the ServerView management blade is equipped with an event repository. e. An IPMB interface is provided to support the user. It supports schemes like FRU (Field Replaceable Units). Communication with the switch blades To enable communication with the switch blades. SSL (Secure Socket Layer) The Manager Blade provides SSL for network data privacy for Telnet as well as for HTTP connections. Auto configuration The management function auto configuration is used to back up system parameters to a ROM. It also allows the configuration of a watchdog timer. and SDR (Sensor Data Records). Communication with the server blades The ServerView management blade communicates with the server blades via an I2C bus. a CLI interface is provided. It also provides the possibility to restore these paramters if required. such as the IP address. i. It allows to configure settings of the switch blades. providing a 2 x 32 MB SDRAM. the IP mask. SEL (System Event Log). or the IP gateway address. This reduces the risk if system configuration data have been corrupted or lost. which is located on the management blade.

the standby component will take over control of the server management. but their MAC adresses differ from each other.2. 2.2 Redundancy of the ServerView Management Blade Of the two ServerView management blades within the blade server system. This is then the one that will be the master. As soon as the master fails to work properly. it will behave according to the following scenario: – Issue an ICMP broadcast ping to update the ARP table and switch the IP filtering table. using the MAC addresses. these components can continue to communicate by sending IP broadcast packages. one will take over the role of the master. The master blade and the redundant blade communicate symmetrically with each other via a TX/RX serial interface. for instance.3 Console Redirection When using the console redirection feature. who is in charge of the server management.BX Blade Server System Overview Blade Server Management 2. The KVM (Keyboard/Video/Mouse) input is captured and sent to the ServerView management blade. To support this mode.2. in order to adjust them with regard to the new MAC address – Define a proprietary protocol in L2. which is used for remote communication If communication between master and redundant component via the serial interface has broken down. When the system is powered up. the ServerView management blade acts as the console redirection agent. the management of the blade server system may be executed in remote control mode. The ServerView management blade will in turn send this input to a server blade. Fail-over scenario When the redundant ServerView management blade takes over control from the master. when unplugged by the system administrator. where the appropriate actions will be executed. it depends on which of the two ServerView management blade first outputs a heartbeat. ServerView BX900 S1 Management Blade 11 . while the other one will remain in a standby status as a redundant component. The two components have the same IP address.

.

For this purpose a RS232 cable (null modem cable) is used. The menu is described in this chapter. The parameters for this option are to be set as follows: Baud rate Parity bits Data bits Stop bits Flow control Terminal type 115200 None 8 1 None VT100 The console mode can also be entered via LAN. using the Telnet protocol. After approximately five seconds a welcome screen is displayed. and the login procedure is performed using the management blade IP address. A number of configuration activities can be performed via this menu. In this case.g.3 Telnet Interface Within the blade server system a console menu is provided for server management. 3. The settings are then as follows: Host IP address Telnet port Connected protocol Terminal type 192. ServerView BX900 S1 Management Blade 13 . the blade server system is started. the Telnet client is called up. IP address configuration or hardware status monitoring.10 (example for a management blade address) Same as the Telnet port configured for the management blade (default port: 3172) TCP/IP (Winsock) VT100 After these parameters have been set.168.1 Entering the console mode To enter the console mode a connection from a PC to the serial port of the blade server system has to be established first. An RX/TX signal will then be exchanged via this cable. After the connection has been established. the HyperTerminal option is called up on the PC. firstly a number of messages concerning the system appears on the screen.224. e. When using the serial port.

Entering the console mode Telnet Interface The user is requested to enter a user name and eventually a password. to be admitted to the console main menu: Figure 2: Welcome screen for access to the console menu 14 ServerView BX900 S1 Management Blade .

7. including management blades and switch blades. 9. Command Line Interface (see 3. Console Redirection (see 3.4 on page 39) This item provides an interface to send IPMI messages to a management blade in case of an emergency. 3. Management Agent (see 3. It can also be used for debugging purposes.3 on page 16) This item provides several options for the management of the whole blade server system. 4. 2. if it is not. 6. Account Management (see 3. 8. the second header which offers the option of rebooting appearst. * Change Management Role To Slave | Reboot Management Blade (see 3. Logout (see 3.11 on page 43) This item is used to get whole chassis information. the first header for changing the role of the management blade appears.2 Console main menu The console main menu looks like this: Figure 3: Console main menu There are nine items in the console main menu: 1.5 on page 40) This item is used to configure the console redirection mode. System Information Dump (see 3. i. according to the configuration: if the system is redundant in design.e. Emergency Management Port (see 3. ServerView BX900 S1 Management Blade 15 .12 on page 44) This item is used to change the user password. The items of the console main menu are described in more detail in the following sections. 5. The selected console redirection target will be active after the next boot.8 on page 42) This menu item is created dynamically.10 on page 42) This item is used to display consecutive lists of information.7 on page 41) This item is used to logout from the system. The reboot is executed immediately. TFTP Update (see 3.Telnet Interface Console main menu 3.6 on page 41) This item is used to update the management blade firmware.

3.I2C Bus Management (see 3.6 on page 25) 7.LDAP Authentication (see 3. Blue Screen (see 3.3.3 on page 20) 4.16 on page 37) 17. Storage Blade (see 3.Management Agent Telnet Interface 3.2 on page 19) 3.Set System Default (see 3.13 on page 35) 14.3.3.VLAN Information (see 3.Management Blade Base Configuration Backup/Restore (see 3.3.3. Connection Blade (see 3.3.3.10 on page 32) 11.3 Management Agent The following items are provided in the Management Agent sub-menu for server management: 1.3.Management Blade Configuration Backup/Restore (see 3.Server Blade CMOS Backup/Restore (see 3. User Management (see 3.3. Event Log (see 3. System Information (see 3.3.9 on page 30) 10.3.15 on page 37) 16.11 on page 33) 12.3.7 on page 27) 8.17 on page 38) 16 ServerView BX900 S1 Management Blade . Server Blade (see 3.5 on page 25) 6.1 on page 17) 2.8 on page 29) 9.12 on page 34) 13. Management Agent Information (see 3.3.3.14 on page 36) 15.3.Power Consumption (see 3. Management Blade (see 3.3.4 on page 21) 5.

Altogether. or date and time. too. while others are used to set more than one.3. There are options that are used to set a single parameter. For the former group of parameters their current values are displayed. the menu for these options looks like this: Figure 4: Agent Information menu ServerView BX900 S1 Management Blade 17 .Telnet Interface Management Agent 3.1 Management Agent Information This item provides several options to configure and display parameters of the management agent. such as the network IP address. Telnet and SMTP parameters.

Configuration of the Telnet server settings. including SMTP enabling/ disabling. including SNMP enabling/disabling. no matter whether the NTP server time is behind or ahead of management blade. Agent Telnet Agent DNS Agent SMTP Agent SSH Agent NTP Agent NIC Duplex Mode Setting of the management blade’s NIC duplex mode (full duplex or half duplex). SMTP sender. You can enable or disable the NTP service. 18 ServerView BX900 S1 Management Blade . Setting Mode allows you to specify which duplex mode should be active after the next reset. Configuration of the SMTP settings for mail sending. Configuration of the SSH settings. including Telnet port assignment and Telnet enabling/disabling.Management Agent These options are used to perform the following activities: Telnet Interface Option Set Service Lan Configuration Set Management Lan Configuration Set Time Zone Set Management Agent Date Time Set Management Agent Timeout Agent System Info Description Configuration of the servic LAN interface of the MMB. Configuration of the time-out value for login to the console menu. Configuration of the HTTP settings. Configuration of the SNMP settings. – Sync Always The management blade always syncs the time from NTP server. Execution Mode displays the current duplex mode. Configuration of the NTP (network time protocol) service. set the NTP server’s IP address and choose the Sync Mode: – Sync Afterwards Only if the management blade time is ahead of NTP server time. Configuration of the DNS server address and enabling/disabling DNS support. Configuration of date and time for the management blade. the management blade syncs the time from NTP server. HTTP protocol enabling/disabling and HTTP SSL security control. selecting an SMNP community string and a destination from the SNMP trap table. Configuration of the management LAN interface of the MMB. which is selected from a time zone table. Configuration of the time zone for the management blade. including port number assignment. SMTP relay server and mail user account. Settings used in SNMP for the management blade: – system name – system location – system contact Management Agent Administrative URL Agent HTTP Agent SNMP Display of the home page URL for the management blade.

Maximum voltage of the MMB.2 Management Blade Within the blade server management system there are two management blades. Serial number of the management blade. Minimum voltage of the MMB. Current voltage of the MMB. Status of the voltage supply of the MMB.3. One of them is active as the master of the server management system. Health status of the management blade. Date of manufacture for the management blade. showing their current values (see next figure): Figure 5: Management Blade menu The following parameters are displayed: Parameter Management Blade Run Mode Management Blade Status Management Blade Manufacture Management Blade Manufacture Date Management Blade Serial Number Management Blade Product Name Management Blade Model Name Management Blade Hardware Version Management Blade Firmware Version Service LAN MAC Address Management LAN MAC Address Management Voltage Status Management Voltage Maximum Value Management Voltage Minimum Value Management Voltage Normal Value Management Voltage Current Value Description Displays whether the management blade is run in master mode or slave (standby) mode. Product name of the management blade. The other one is in standby mode to ensure the availability of the system. Physical address (MAC address) of the service LAN interface of the MMB. Hardware version of the management blade. A number of parameters relating to the management blades is displayed to the user. A message will be displayed if this status is disturbed. Firmware version of the management blade. Name of the management blade model. Physical address (MAC address) of the management LAN interface of the MMB. Standard voltage of the MMB. Name of the manufacturer of the management blade.Telnet Interface Management Agent 3. ServerView BX900 S1 Management Blade 19 .

supporting the fan life time monitor. power supply groups and temperature sensors. excepting CPU blades and switch blades. including the chassis serial number and if there has been any intrusion into the inside of the chassis. including UPS number. The function is only working for VIOM. Displays information on the system temperature. temperature. including parameters like nominal speed. System Power Supply System Fan System Temperature System Chassis Table System UPS ID LED Control NIC Status Detection Turn on/off all server blades Automatic Inventory Retrieval 20 ServerView BX900 S1 Management Blade . sensor status and critical temperature reaction. In dual MMB mode the roles are switched when the LAN connection to the master fails. such as power supply. type. current speed. speed threshold and failure reaction. the inventory retrieval is automatically performed for inserted server blades or when the basic unit is powered on. IP address. Displays information on the system chassis. vendor. critical level. Displays information on the number and status of the system fans. connect port. KVM (= keyboard/video/mouse). off. If set to automatic. or blinking. fans. Displays the status of the system control: on. A fan test is also provided.3 System Information The System Information option provides information on all components of the blade server management system. Displays information on the power supply units. and SNMP community. Displays chassis UPS (uninterruptable power supply) information.3. and the slave takes over the role of the master. as well as the status of all system components.Management Agent Telnet Interface 3. Turns on or turns off all server blades. the automatic inventory retrieval is not done. including current value. If set to manual. The menu for this option looks like this: Figure 6: System Information menu The menu offers the following subordinate options to the user: Parameter System Control Information Description Displays the number of system fans. warning level.

Shows the current mode of Consumption Control (if Consumption Mode is enabled). Indicates the status of the Server Memory Dump Flag (normal or off). CMOS configuration and watchdog timers. The menu for this option looks like this: Figure 7: Server Blade menu 3. memory modules.4 Server Blade The Server Blade option provides general information on the server blades. Configuration of the LED control at the front of the blade server: blinking or off. Controls the "forced" shutdown (termination of processes is not waited for.1 Server Blade Control Information This option enables the user to set the following parameters: Parameter Server Power Description Set server power: (1) on (2) off (3) power-cycle (4) reset (5) NMI (6) force off The boot modes init and inventory are supported by VIOM function. Host name of the server blade. Is overwritten with the host name assigned in the operating system when ServerView agents are used. please refer to the VIOM specification. information on CPUs. voltage. these are closed immediately).3. temperature. If the "proper" shutdown of the server blade fails. The user can set up a power on/off schedule for server blade.Telnet Interface Management Agent 3. the "forced shutdown" is initiated after n minutes.3. Set Server Boot Mode Set Server Blade Host Name Server LED Control Server Power Control Mode Server Memory Dump Flag Server Power On/Off Time Control Server Power Force Power Off Enabled Server Power Force Power Off Control ServerView BX900 S1 Management Blade 21 .4.e. For details. i.

Displays the server blade model name. Displays the CPU ID. iRMC Address Configuration 3. USB stick. The following parameters are included: Parameter Server Blade Status Server Blade Manufacture Server Blade Manufacture Date Server Blade Serial Number Server Blade Identify Serial Number Server Blade Product Name Server Blade Product Version Server Blade Model Name Server Blade Hardware Version Server Blade BIOS Version Number of CPU Socket Number of Memory Socket Server Blade OS Type Server Blade OS Version Server Blade iRMC Firmware Version Server Blade Mezzanine Card Server Blade Active GUID Description Displays the server blade health status. Displays the server blade BIOS version. Displays the server blade serial number (motherboard). Server Blade Manufacture GUID 3.3 Server Blade CPU This option displays some information on the server blade CPU parameters. 22 ServerView BX900 S1 Management Blade . Displays the OS platform currently running on the server blade. However. Displays the server blade product name. the blade can be started up "without" the BIOS.4.4. Displays the server blade production date. Sets up the LAN connection of the iRMC.2 Server Blade Information This option displays some information on the server blade parameters.3. After the option has been set. Displays the CPU frequency. Displays how many CPU sockets are available on the server blade. the Active GUID differs from the Manufacture GUID. if the VIOM was enabled. Globally Unique Identifier which is stored in the BIOS.3. Normally the same value as in the Server Blade Manufacture GUID (see next entry).Management Agent Telnet Interface Parameter BIOS Recovery Flash Bit Description This option can be selected if the server blade’s BIOS has problems or a flash has failed. Displays the server blade iRMC firmware version. Displays whether a Mezzanine card is installed. Displays the server blade manufacturer. Displays the server blade serial number (systems). Displays the version of the OS currently running on the server blade. CD/DVD) and flashes it. Displays the server blade hardware version. Displays server blade memory information. Displays the server blade product version. The following parameters are included: Parameter CPU Type CPU Frequency CPU ID Description Displays the CPU type. It then searches autonomously for a suitable BIOS on the connected media (floppy.

3. 3. Displays the voltage status for the server blade. together with memory type and error information. Some of the parameters displayed can also be set by the user: Parameter Description Server Temperature Sensor Designation Displays the designation of the temperature sensor for the server blade. Displays the maximum voltage value for the server blade. Displays the nominal voltage value for the server blade. the error reset record and the error count start time. Displays the status of each memory module.4. The values displayed will be: – – – – NOT_AVAILABLE OK TOO_LOW TOO_HIGH Server Voltage Minimum Value Server Voltage Maximum Value Server Voltage Current Value Server Voltage Nominal Value Displays the minimum voltage value for the server blade. Displays the current voltage value for the server blade.3. Displays the CPU socket designation. Displays information on the CPU manufacturer.3.6 Server Blade Temperature This option provides information on the server temperature. The information is displayed in two tables: Parameter Server Blade Memory Information Table Server Blade Memory Modules Table Description Displays information on the total size of the memory. as well as on the error count. The values displayed will be: – – – – – OK NOT_PRESENT ERROR CRITICAL MISSING_TERMINATION CPU Name CPU Socket Designation CPU Manufacturer CPU Clock Displays the CPU name. Displays the CPU clock. The following parameters are displayed: Parameter Server Voltage Designation Server Voltage Status Description Displays the voltage designation for the server blade.Telnet Interface Management Agent Parameter CPU Status Description Displays the CPU status.4 Server Blade Memory This option provides information on the server blade memory. 3. ServerView BX900 S1 Management Blade 23 .5 Server Blade Voltage Table This option provides information on the server voltage.3.4.4.

Server Temperature Upper Critical Level This parameter can be set to configure the upper critical level of the temperature sensor for the server blade. Displays the current temperature value for the server blade. Server Temperature Lower Warning Level This parameter can be set to configure the lower warning level of the temperature sensor for the server blade. a time-out routine will be started. When the time-out is reached.8 Server Blade Watch Dog This option is used to configure the watchdog timers for the server blade.4. Server Blade Boot Watchdog 24 ServerView BX900 S1 Management Blade .7 Server Blade NIC Information This option displays the IP and MAC address of the server blade. Server Temperature Lower Critical Level Server Temperature Current Value This parameter can be set to configure the lower critical level of the temperature sensor for the server blade. Server Blade MAC Address Table Table with all MAC addresses of the server blade. 3. When the time-out is reached. It will be reset by the BIOS in periods configured within the POST code. This timer is used to monitor the server blade POST.Management Agent Telnet Interface Parameter Server Temperature Sensor Status Description Displays the status of the temperature sensor.3.4. A watchdog timer agent that resets the timer must be implemented in the operation system. Parameter Server Blade NIC IP Table Description Address table of the server blade's Network Interface Card. a time-out routine will be started.3. The values displayed will be: – – – – – SENSOR_DISABLED SENSOR_FAIL WARNING_TEMP_WARM CRITICAL_TEMP_WARM NOT-AVAILABLE Server Temperature Upper Warning Level This parameter can be set to configure the upper warning level of the temperature sensor for the server blade. 3. There are two timers that can bet set here: Parameter Server Blade Software Watchdog Description This timer is used to monitor the operation system and the software applications.

PRIMERGY SX940 S1). FC Switch Blade 3. Displays the storage blade model name. Displays the storage blade manufacture date.3.Telnet Interface Management Agent 3.5 Storage Blade The menu for this option looks like this: Figure 8: Storage Server Blade menu The following parameters are displayed: Parameter Storage Blade Status Storage Blade Manufacture Storage Blade Manufacture Date Storage Blade Serial Number Storage Blade Identify Serial Number Storage Blade Product Model Storage Blade Product Name Storage Blade Product Version Storage Blade Model Name Storage Blade Hardware Version Description Displays the storage blade health status. Displays the type name of the storage blade (e. Displays the storage blade product version. Displays the storage blade hardware version. Currently supported are the following types of connection blades: 1. GbE IBP Blade The menu for all these types is the same and looks like this: ServerView BX900 S1 Management Blade 25 .6 Connection Blade The Connection Blade option is used to display information on the connection blades that are part of the blade server system. Displays the storage blade manufacture vendor. Displays the storage blade serial number (systems). Displays the storage blade product name.3. Displays the storage blade serial number (motherboard). 3. GbE Switch Blade 2.g.

Enables/disables the switch period polling function. Applies for SB11 connection blades. GbE connection blades can run in two different modes – Switch and IBP. Sets the LED off or blinking. Displays the manufacturing date. A common management interface then exists for the connected connection blades.Management Agent Telnet Interface Figure 9: Connection Blade menu The following parameters are displayed: Parameter Status Administrative URL Manufacture Manufacture Date Serial Number Product Name Model Name Hardware Version Firmware Version User Assigned Name UID LED Control Power Control Period Polling Connection Blade Mode Stacking State Inter-Switch Link Setting Description Displays the status. Displays the model name. Displays the serial number. Starts rebooting the connection blade. The URL at which the MMB can be reached using a Web browser. Displays information on the manufacturer. This status can be retrieved by the management blade via a CLI command. 26 ServerView BX900 S1 Management Blade . Applies for SB11 connection blades. Displays the firmware version. Possible state: Master or Member. Displays the product name. The mode enabled is displayed here. The name of the connection blade (can be assigned by the user). Two SB11s which are operated in a fabric (horizontally adjacent to each other) can be interconnected to form "one" switch. MMB will be polling switch settings every 5 minutes if this function is enabled. These can be interconnected to form a stack. Displays the hardware version.

Telnet Interface Management Agent 3. 2. 3. Step 1 Select the user to be deleted. Administrator OEM Operator User The access rights of the various user roles are as follows: Administrator This role allows the user – to create.) OEM This role allows the user – to have the same functions as the Administrator and – to use OEM commands and functions on the iRMC controller Operator This role allows the user – to use commands on the iRMC controller as a result of IPMI permission level assignments of LAN/Serial for operators – to use the functions at the usual user interfaces (Web UI. because no explicit entry is provided for this. connection blades. CLI etc. We will therefore use an example to describe how you must proceed in this case. and server blades – to use commands on the iRMC controller as a result of IPMI permission level assignments of LAN/Serial for administrators – to use the functions at the usual user interfaces (Web UI. CLI etc. CLI etc.3. update.7 User Management The User Management option is used to change. The situation is somewhat different when an existing user is to be deleted. The following four user types (roles) with different permission rights are possible: 1. in this example the user Tom – type 2: ServerView BX900 S1 Management Blade 27 .) User This role allows the user – to use the functions at the usual user interfaces (Web UI. add and delete users.) Example: Deleting a user The methods for creating a new user or changing a user name or rights are intuitive and present no problems. 4. and delete a user account – to configure system settings related to the MMB.

Management Agent Telnet Interface Figure 10: User Management – deleting a user Step 2 Now select the name of the user to be deleted – type 1: Figure 11: User Management – deleting a user 28 ServerView BX900 S1 Management Blade .

as you can see in the menu: Figure 13: User Management – deleting a user 3. then enter RETURN: Management Agent Figure 12: User Management – deleting a user Step 4 User Tom has been deleted.Telnet Interface Step 3 To delete the user.3. as provided by UART. simply press the space bar. if the operating system used supports the blue screen feature.8 Blue Screen The Blue Screen option is available. ServerView BX900 S1 Management Blade 29 . The option will then display which server blades are currently in blue screen status.

The major events that have been logged on the management blade. 30 ServerView BX900 S1 Management Blade .3. The following parameters are displayed: Parameter All Event Informational Event Minor Event Major Event Critical Event Clear All Entries Description All events that have been logged on the management blade.Management Agent Telnet Interface 3. This parameter is used to clear all events from the management blade event log. The minor events that have been logged on the management blade.3. The informational events that have been logged on the management blade.9. The critical events that have been logged on the management blade. The menu for this option looks like this: Figure 14: Event Log menu Information is displayed for: – Events that were logged on the management blade event log – Events that were logged on a server blade event log 3.1 Management Blade Event Log This sub-option is used to display the events that have been logged on the management blade event log.9 Event Log The Event Log option is used to display the events that have been logged on the management blade and the server blades.

4 Management Blade Wrap Around Event Log Enable This option is used to specify whether the wrap-around functionality for the event log should be used or not. whether power on/off events for the server blades should be listed in the event log.2 Server Blade Event Log Table This sub-option is used to display the events that have been logged on a server blade event log. ServerView BX900 S1 Management Blade 31 .Telnet Interface Management Agent 3. Parameter enable disable Description When the event log repository is full.3. When the event log repository is full.5 Backup All Event Log to USB Device This option is used to save the MMB’s event log to a USB medium. 3. new event log entries replace the old ones beginning with the first event log entry.3 Server Blade Power On/Off Event Log Enable This option is used to specify.3.3. Parameter USB device selection Description Selects the USB medium (all the devices connected to the MMB are displayed here).3. Enable Starts the backup to the USB medium. The minor events that have been logged on the server blade.9. After a server blade has been selected. no event log entries are written any longer. The critical events that have been logged on the server blade.9. the following parameters are displayed: Parameter All Event Informational Event Minor Event Major Event Critical Event Clear All Entries Description All events that have been logged on the server blade.9. The informational events that have been logged on the server blade. The major events that have been logged on the server blade.9. Filename (empty default name) Name of the file which will be written to USB – if nothing is entered. This parameter is used to clear all events from a server blade event log. 3. a default name is used. 3.

The password for the user root is set to the default (“root“). The menu for this option looks like this: Figure 15: Set System Default menu The following parameters can be set: Parameter Set Config Default Description The configuration of the management blade is set to the default values. V Please note that all configured values are lost and the management blade has to be configured newly after using this option. 32 ServerView BX900 S1 Management Blade .Management Agent Telnet Interface 3. Set Username/Password Default All configured user names with the exception of root are deleted.10 Set System Default The Set System Default option is used to restore the default values. Set CMOS Backup Default All switch blade configuration backups and all server blade BIOS backups are deleted.3.

the Server CMOS Configure option is displayed: Figure 16: Server CMOS Configure menu The following parameters are displayed: Parameter CMOS Control Description Specifies the backup/restore policy: backup The BIOS parameters of the selected server blade are backed up. CMOS Configure Restore Target Server CMOS ID With BIOS Version Server CMOS ID With Mac Address Backup Date Time Specifies the server blade whose BIOS parameters are to be restored. the backup file will be displayed in the CMOS backup file table. smart-restore After the slot id. force-restore The backup file is restored without verification.Telnet Interface Management Agent 3.11 Server Blade CMOS Backup/Restore This option is used to backup and restore server blade BIOS parameters.3. Displays the CMOS ID with MAC address Displays date and time of the backup file generation. BIOS version and MAC address have been verified. ServerView BX900 S1 Management Blade 33 . the backup file of the selected server blade is restored. Displays the CMOS ID with BIOS version. After selecting the server blade whose BIOS is to be backed up or whose backup file is to be restored. The server blade must be powered on before backup/restore processing. If the backup is successful.

Displays the max. Shows the current power consumption of the connection blade. DC power consumption of each server blade. limit values. Settings for power control (redundancy. Displays the max.12 Power Consumption This option is used to control the power consumption. Shows the current power consumption of the storage blade. Power consumption of the base system. etc. 34 ServerView BX900 S1 Management Blade . Displays the max. dynamic. Difference between Power Budget Control Threshold and current Total Consumption. Includes one management blade and 6 fan modules. Current power consumption of the whole blade server system (including server blades).Management Agent Telnet Interface 3.) – observe submenus. DC power and the voltage range of the power supply units. DC power consumption of each connection blade. Storage Blade Power Consumption Table Displays the max. The menu for this option looks like this: Figure 17: Power Consumption menu The following parameters are displayed: Parameter Power Budget Control Threshold Base Consumption Total Consumption Remaining System Power Unit Status Table Storage Blade Current Power Consumption Table Server Blade Power Consumption Table Connection Blade Power Consumption Table Connection Blade Current Power Consumption Table Set Power Budget Control Description Displays the max. DC power of the active power supply.3. DC power consumption of each storage blade.

secondary LDAP server. IP addresses of the primary and. Domain name which was assigned by the LDAP server.Telnet Interface Management Agent 3.The login syntax is: username@domain (where username is an ASCII string of 1-256 bytes). OpenLDAP. Distinguished Name.3. "Department" of the user in the LDAP directory. eDirectory). Needed to set up a connection to the LDAP server. Password for setting up a connection to the LDAP server. ServerView BX900 S1 Management Blade 35 . Selects whether LDAP is to use a secure SSL connection. Name of the domain in which the user logs in. a unique object name in LDAP directories. if present.13 Active Directory Authentication Use Active Directory to login to the MMB through the Web-based or a CLI interface. Selects the LDAP type (Windows Active Directory. Figure 18: Active Directory Authentication menu The following parameters are displayed: Parameter LDAP Authentication Enable LDAP over SSL LDAP Type LDAP Server IP 1/2 Root Domain Name LDAP Base DN User LDAP Base DN User LDAP Department Special User Account Special User Password Description Enables/disables the LDAP functionality.

14 VLAN Information MMB supports up to 10 VLAN IDs. Figure 19: VLAN Information menu The following parameters are displayed for each group: Parameter VLAN Group ID VLAN IP VLAN Network Mask VLAN Enable Description Identifies different VLAN group IDs. 36 ServerView BX900 S1 Management Blade . The integer 2 to 4095 are supported. Sets the VLAN IP. Enables/Disables the VLAN function.Management Agent Telnet Interface 3. Sets the VLAN network mask.3.

15 I2C Bus Management This function is used to enable/disable I2C bus communication between MMB and server blades. Once I2C bus is set to disable.3. including certificates. The menu for this option looks like this: Figure 21: Management Blade Configuration Backup/Restoration menu ServerView BX900 S1 Management Blade 37 . MMB cannot update any server blade status..Telnet Interface Management Agent 3. to be backed up/restored.3. etc. users. Figure 20: I2C Bus Management menu 3.16 Management Blade Configuration Backup/Restore This option enables all the MMB settings.

Management Agent

Telnet Interface

3.3.17 Management Blade Base Configuration Backup/Restore
This option enables the most important MMB settings (Language, Identification, Network, Power Settings, PIN Settings) to be backed up/restored. The menu for this option looks like this:

Figure 22: Management Blade Base Configuration Backup/Restoration menu

38

ServerView BX900 S1 Management Blade

Telnet Interface

Emergency Management Port

3.4

Emergency Management Port

The Emergency Management Port (EMP) is for internal use only! The starting page for these option looks like this:

Figure 23: Starting page for Emergency Management Port option

I Type A plus <enter> to quit the EMP.

ServerView BX900 S1 Management Blade

39

Console Redirection

Telnet Interface

3.5

Console Redirection

There is one console port (serial port interface) within the blade server system. Console redirection can be configured for server blades or connection blades. The menu for this option looks like this:

Figure 24: Console Redirection menu

There is a sub-option of console redirection for server blades and one for switch blades. Furthermore, a return hotkey can be configured:

Sub-option
Console Redirect Connection Blade Set Return Hotkey, Ctrl+(a character)

Description
This option is used to configure a connection blade for console redirection. This option is used to configure a return hotkey. To do this, a character from A-Z is chosen, excluding M. The hotkey to exit console redirection and return to the previous mode is then Ctrl + the character that has been set here, e.g. Ctrl + R. The default character used for the return hotkey is Q.

Set Console Redirection Timeout

An active connection is automatically disconnected after n seconds.

40

ServerView BX900 S1 Management Blade

Upgrading of the Server Blade iRMC firmware.7 Logout This option is provided to perform a logout from the Telnet console menu. The update will then be performed as the system powers up. The default value for this parameter is disable. Update Server Blade BIOS Table Update Server Blade iRMC Table Upgrading of the Server Blade BIOS. This option is used to enable/disable the update and to display the TFTP status. 3. and the management blade must be rebooted. Management Blade Image File Name Setting of a file and path name for the management blade image. I For further information on updating BX components please refer to the Operating Manual of your BX system.6 TFTP Update The TFTP Update option is used to perform an update of the management blade firmware. The menu for this option looks like this: Figure 25: TFTP Update menu The following parameters can be set: Parameter TFTP Server IP Address Management Blade Update Enable Description Setting of an IP address for the TFTP server. After setting the parameter to enable. Upgrading of the management blade firmware.Telnet Interface TFTP Update 3. the TFTP server must be started. ServerView BX900 S1 Management Blade 41 . This option is used to enable/disable the update and to display the TFTP status.

The reboot is executed immediately. 42 ServerView BX900 S1 Management Blade . 3. OS type and OS version.g. I This menu item appears only if the system is not redundant in design.Change Management Role To Slave Telnet Interface 3. status. BIOS version. Displays the management blade event log. voltages. Provides information about temperatures. Displays the server blade event log. all modules’ FRU data and event logs.10 System Information Dump This option is used to display the event logs of management blades or server blades and to display consecutive lists of configuration/status information. The menu for this option looks like this: Figure 26: System Information Dump menu The following parameters are displayed: Parameter System Configuration/Status SEL for Management Blade Server Blade Configuration/Status SEL for Server Blade Dump System Information Dump Post Mortem Description Displays a consecutive list of system information. status. iRMC firmware version. IP address. Displays a consecutive list of information about the server blades.8 Change Management Role To Slave This item is used to change the role of the management blade. e. 3. I This menu item appears only if the system is redundant in design. fan speeds. e. MAC address and firmware version of the switch blades. Use in case of problem.9 Reboot Management Blade This item is used to perform a reboot of the system. to get all necessary information on customer site to analyze the problem in the development.g.

11 Command Line Interface This option is used to get chassis information or to manage series of servers. 3.Telnet Interface Command Line Interface Parameter Description Dump System Information/POST Permits the System Information Dump and POST Mortem Dump to be backed Mortem Backup Configuration up on a USB medium. operating system state. I Type exit to quit the SMASH CLI submenu. server system topology or access method. ServerView BX900 S1 Management Blade 43 . The menu for this option looks like this: Figure 27: Command Line Interface menu The following parameters are displayed: Parameter SMASH CLI Shell Description The SMASH (Systems Management Architecture for Server Hardware) Shell enables a simple and intuitive management of servers in data centers independent of machine state.

Account Management Telnet Interface 3. The menu for this option looks like this: Figure 28: Account Management menu 44 ServerView BX900 S1 Management Blade .12 Account Management This option is used to change the user password.

36. the message No Access Right! will appear. http://10. I If you enter an incorrect password more than three times. It does not depend on any special operating system for a platform.4 Web User Interface On the web server an interactive and user-friendly web user interface. 4.185 A pop-up window will then open in which you enter your user name and password: Figure 29: Input mask for login (Internet Explorer) The default user name and the default password are both admin.1 Login You log into the web server by entering an IP address in the browser’s URL line. is provided for server management. You log into this interface via the web browser. ServerView BX900 S1 Management Blade 45 .40. e.g. known as web console.

the installed components and their current status. main frame (4) and bottom frame (5). navigation frame (3). Status frame (2) The status frame consists of a number of graphical or text controls or displays. Banner frame (1) The banner frame comprises the following fields: ● The name of the blade server (in this example BX900S1em_172) is displayed in the field on the left below the logo. The name of the current user (in this example the user admin) is displayed in the upper field on the right. ● ● ● The banner frame is collapsible ( ). status frame (2). These fields become visible as soon as the cursor points to HELP. Taking our example in figure 30. Viewed from top left to bottom right. The fields are: – About Supplies information about the current firmware status. The start page looks like this: Figure 30: Frames of the start page The start page consists of five frames: banner frame (1). A HELP field at the far right below the link to sign out. 2. i.2 The Start Page After you have logged in successfully.e. the following elements are involved here: 46 ServerView BX900 S1 Management Blade . The HELP field is in turn subdivided into three fields. – On BX900 Remote Management Supplies an overview of all help texts.The Start Page Web User Interface 4. a home page (start page) is displayed which provides an overview of the system configuration. showing the graphical elements in a list and separating them with ⏐. A link for signing out (Sign out) below the name of the user who is currently logged in. 1. – On Page Shows the help text for the selected menu item (see Navigation frame below). we will describe the various elements below.

The Start Page The icon on the left (red) indicates that an error of the type "Critical Error" has occurred in the system. it is not a warning but indicates an error of the type "Critical Error". The icon in the middle (yellow) indicates that an error of the type "Warning" or "PDA Error" has occurred in the system. then you select the mode you require in the Consumption Control block using the Operation Mode pull-down menu. CMOS batteries. it is not a warning but indicates an error of the type "Critical Error". Such as error must be corrected immediately. When the yellow icon is in the blinking state. The component which is affected is displayed in the navigation frame (see below). is always displayed here. You configure the Operation Mode in the Configuration tab by selecting the Consumption Control item in the Power Consumption Options block using the Consumption Mode pull-down menu. The components which are affected are displayed in the navigation frame (see below). please refer to chapter “Power Management” on page 79. Detailed information on these error types is provided at the start of this list. After you actuate Apply. A PDA (Prefailure Detection Analysis) reports problems in hardware components (fans. I If errors of the type "Critical Error" and of the type "Warning" or "PDA Error" have occurred simultaneously in the system. The gray icon indicates that all system components are operating without error. CSS: Error: Controller Time This field specifies the blade server’s current data and time.e. Minimum Power. It is possible for more than one error of this type to occur in the system. Power Consumption Mode: disabled⏐Minimum Power⏐ Best Performance This field is a link to the Power Management → Configuration page in the navigation tree. The possible modes are: disabled. The component which is affected is displayed in the navigation frame (see below). The component which is affected is displayed in the navigation frame (see below). Best Performance. The red icon indicates that an error of the type "Warning" or "PDA Error" has occurred in the system. ⏐ yellow blinking ⏐ This field indicates errors of the type "CSS" (Customer Self Service). the red icon. For details. It indicates the Operation Mode configured. the higher-ranking error. Uptime Specifies the time since the blade server was started. the mode selected is displayed in the status frame after the colon. The gray icon indicates that all system components are operating without error. but can only be rectified by Customer Service. The yellow icon indicates that an error of the type "Warning" or "PDA Error" has occurred in the system. The icon on the right (green) indicates that the system is operating without error.Web User Interface ⏐ ⏐ This field displays the overall status of the blade server. This button enables you to refresh all the blade server data. It is possible for more than one error of this type to occur in the system. memory modules and hard disk drives) before these result in a system failure. ServerView BX900 S1 Management Blade 47 . in other words errors which users can rectify themselves. When the red icon is in the blinking state. Detailed information on these error types is provided at the start of this list. i. ⏐ red blinking ⏐ This field indicates errors of the type "Error". in other words errors which cannot be corrected by the user.

I If you have configured a "Consumption Limitation" (Power Consumption Options → Consumption Mode → Consumption Limitation) using the Power Management → Configuration menu item. You use the Video Redirection button to open a virtual console for the blade. the values set are displayed in color in the bar chart – in the example below a Limit Threshold of 80% (red) and a Warning Threshold of 40% (yellow): Figure 31: Power Consumption diagram with display of the Limitation Threshold (yellow and red) For details. if you have selected a server blade. Web User Interface This icon is optional and is displayed only if a USB stick is connected to the Master Management Blade. I The gray bar at the bottom of the status frame normally only contains the name of the component selected on the right. 48 ServerView BX900 S1 Management Blade . System Unit Details This button enables you to collapse the status frame. However. ⏐ You use the Locate button to switch the blade server’s and MMB’s ID LED on (blue) or off (gray). This value is changed by the system if you set the Dynamic Mode option (in the Power Consumption Options block of the Power Management → Configuration page).The Start Page Scheduled Power Consumption Mode: off⏐on This field indicates whether Power Consumption Mode is switched on or off. this bar (plus the line below it) contains additional information elements just for this blade (see figure): Figure 32: Additional status frame for a selected server blade The Remote Management button takes you to a website where you can administer the blade remotely. please refer to chapter “Power Management” on page 79. In the 2nd line (bar chart) the current primary input power of the PSUs and the maximum possible power consumption of the active PSUs are displayed in the form of a bar chart and in figures in watts. The maximum possible power consumption can vary dynamically if the Dynamic Mode option was enabled on the Power Management → Configuration page. The other fields have the same meaning as described above for the status frame. The 3rd line provides information about the secondary output power which is still available for the blades up to the specified upper limit. which is dynamic.

When you point the cursor to a component. I Hardware components which are not integrated into the BX900 base unit are not displayed in the navigation frame. i. i. I When the power supply is switched off (via Information / Operation – Power Management – Control – – Rear View Current System Power). either. The individual items are clickable. i. Each of the three views of the navigation tree is collapsible ( 4.Web User Interface 3. the associated information is displayed in the main frame.e. fan. This power-off status is also indicated by the LED at the bottom right glowing orange instead of green. or ). i. Navigation frame (3) The navigation frame consists of three different views: – Front View The Start Page Displays the BX900 base unit with the existing blades (server blades and storage blades). MMB. When you point the cursor to a blade. a tooltip with the relevant name is displayed (see the picture below). the associated information is displayed in the main frame. after they have been clicked on. The individual components are clickable. It contains information about the option/component which was selected via one of the two views or the navigation menu. after they have been clicked on. the associated information is displayed in the main frame. after they have been clicked on.e. etc. no blades are displayed. a tooltip with the relevant name is displayed.).e. Displays the BX900 components at the rear (power supplies. The individual blades are clickable. 5. Figure 33: Front and rear views of a fully-equipped MMB S1 with tooltip information – Tree View The tree view contains various menu items which can be used to influence the system properties and the configuration. the unit is totally black. Bottom frame (5) The bottom frame only contains a copyright notice at the bottom left. Main frame (4) The main frame supplies information about the BX900 base unit.e. ServerView BX900 S1 Management Blade 49 .

also appears both in the navigation frame (more precisely in the Front View and in the navigation tree) and in the main frame. The redundant error display on the start page has the advantage that an error is displayed even when all collapsible frames have been collapsed (see next figure): Figure 35: Start page with error display in the case of collapsed frames 50 ServerView BX900 S1 Management Blade . The faulty Server Blade 8 in our example is displayed a total of 6 times: 3 times in the status frame (top left and as CSS error). in each case the same error is indicated. The example below shows a start page with the complete error display in all three frames: Figure 34: Start page with error display The meaning of the error icons in the status frame has already been explained above. and in the main menu. which is a general indicator in the status frame for an error in the system.The Start Page Web User Interface Error handling Errors and warnings are displayed simultaneously in the status frame. the navigation frame and the main frame. This enables you to see precisely in which component the error has occurred (in our example in "Server Blade 8"). The icon. twice in the navigation frame (in the Front View and in the navigation tree). In other words.

Web User Interface Two notes: The Start Page The error icon is seemingly displayed 4 times in our example (System. Figure 36: Error display in the navigation tree When you point the cursor to the small displayed: icon in the Front View. The reason for this is that an error is always displayed at the highest level (System) and is "passed down" from there. System Unit. Server Blade-8 menu items) – see the next figure and detail. Server Blades. a tooltip with a corresponding message is Figure 37: Error display with tooltip ServerView BX900 S1 Management Blade 51 .

Clicking on a component causes further information to be displayed. <Rack Name> may not be longer than 13 characters and must start with a letter that can be followed by letters. System Contact The contact information for this system unit.3. digits and underscores ("_"). Update All Connection Blade Names On Changing Rack Name When this function is enabled. System Unit. 52 ServerView BX900 S1 Management Blade . If set to MANUAL. Storage Blades. Management Blades. Other types of connection blade are not affected by this function. automatic inventory retrieval is not performed. <System Name> may not be longer than 14 characters and must start with a letter that can be followed by letters. Connection Blades.1 System (Status Overview) The Status Overview displays a list of all available components in the main frame. All Fans Have Failed Enables the user to configure the reaction after all fans fail or are unavailable. This option has the following sub-functions: Status Overview.Components Web User Interface 4. the names of all connection blades are updated in accordance with the following syntax: <Rack Name>–<System Name>–CB<Slot Number> This only affects connection blades of the types Fujitsu GbE and Fujitsu 10GbE.3. Fan Test Daily test time Sets the fan test time for the system fan. Fan Control Enables the user to configure the reaction when individual fans fail or are unavailable. Note that the rack name can also be empty. digits and underscores ("_"). Rack Name The rack name of the system unit. 4. The system name is also used for DNS name resolution and as DHCP client identifier and therefore has to be unique. System Location The location of the system unit. Power Supplies. plus their status.3 Components The Components function provides information on hardware components of the system. Unique Rack ID The unique rack ID of the system unit. Server Blades.2 System Unit System Information System Name The name of the system unit. the inventory retrieval is performed automatically for the server blades which are inserted or when the system unit is powered on. The format should be HH:MM. Possible reactions: "continue" or "shutdown-and-poweroff". Automatic Inventory Retrieval If set to AUTOMATIC. 4.

Hardware Version Displays the management blade hardware version. MAC Address Displays the MAC address of the management blade network controller. Service LAN MAC Address Physical address (MAC address) of the service LAN interface of the MMB. and the other one is there to ensure redundancy. ServerView BX900 S1 Management Blade 53 . If there are two management blades (recommended). It is essential that there is at least one management blade installed to handle server management. Status Displays the current status of the management blade. Serial Number Displays the management blade serial number. 4.3 Management Blades The Management Blades function is used to display the number of management blades that have been embedded into the blade system for server management. Production Date Displays the production date of the management blade.Web User Interface Components Test at every startup Sets the fan behavior when the system powers on. Manufacturer Displays the management blade manufacturing information. Management Blade-1/2 Information Play Role The management blade plays the role of the master to handle server management or of a slave for standby purposes. Service LAN IP Address IP address of the service LAN interface of the MMB. Model Name Displays the management blade model name. one of them will be selected for the master role in the boot phase. Voltage Status Displays the voltage status of the management blade. Possible reactions: "continue" or "shutdown-and-poweroff". Both management blades will then start to boot up at the same time. Management LAN IP Address IP address of the management LAN interface of the MMB. Temperature Sensor Control Enables the user to configure what action will be taken when the system unit’s temperature sensor is in a critical state. Maximum Voltage Value Displays the maximum voltage value of the management blade. There are up to two management blades in the system. all the fans present will rotate at full speed for a while. Product Name Displays the management blade product name. If this function is checked.3. Management LAN MAC Address Physical address (MAC address) of the management LAN interface of the MMB. Firmware Version Displays the management blade management firmware version. The management blade that is the first to have its heartbeat detected will be the master. One of these plays the master role for server management.

54 ServerView BX900 S1 Management Blade . Normal Voltage Value Displays the normal voltage value of the management blade. Switch Role on NIC Status Detection Enables/disables NIC status detection. Critical.Components Minimum Voltage Value Displays the minimum voltage value of the management blade. Minor. Web User Interface Event Log This feature displays all system events and can be filtered by component and severity by selecting filtering factors and clicking the Apply button. Memory/USB Backup Status Shows the memory/USB backup status. Severity Informational. Major. Restoration Status Shows whether or not restoration is in progress. Current Voltage Value Displays the current voltage value of the management blade. Local Backup Files Choose a source file from the local file system. the MMB will reboot automatically. or All Events. Events are displayed with the following information. Link Down Timeout (0-300) Defines a timeout (0-300 sec) for NIC status detection when the timeout is reached. Description Message description. Clicking the Clear All Entries button causes all event entries in the event repository to be cleared for the selected component. Time Stamp Year-Month-Day HH:MM:SS. Switch Management Role When a slave MMB is present. Memory/USB Backup File The backup path and filename will be displayed here. Configuration Reboot Management Blade The submit button will show "Reboot" when there is only one MMB present. Memory/USB Backup File Select available source files from memory/USB. the master and slave MMB then switch roles (if the slave is ok). Restore Configuration: Backup Media Click the radio button to choose the source media. Backup/Restoration Backup Configuration: Backup Media Click the radio button to choose the backup media. the "Switch Role" button is enabled. If restoration is successful.

ServerView BX900 S1 Management Blade 55 . Model Name Displays the product part number. Operating System Information OS Type Displays the OS platform currently running on the server blade. Identification Serial Number Displays the identification serial number. OS Version Displays the OS version currently running on the server blade.4 Server Blades Server Blade-1 . including type. BIOS Version Displays the server blade’s BIOS version. CPU stepping.. Mezzanine Card Displays whether a Mezzanine card is installed or not. Serial Number Displays the server blade serial number. ekeying enabled and associated Connection Blade for network card. Network Card Information Displays the MAC address. speed. Event Log This feature displays all system events and can be filtered by component and severity by selecting filtering factors and clicking the Apply button. n Information Blade Asset Information Manufacturer Displays the manufacturer of the server blade. Product Name Displays the server blade product name. Manufacturer GUID Displays the manufacturer GUID.3. Active GUID Displays the active GUID. Product Version Displays the server blade product version. and socket type. NIC type. Memory Information Displays the memory module information and configuration. Firmware Version Displays the server blade iRMC firmware version. Production Date Displays the date the server blade was produced. BIOS enabled. Hardware Version Displays the server blade hardware version. Product Model Displays the server blade product model name. IP address. Time Stamp Year-Month-Day HH:MM:SS.Web User Interface Components 4. CPU Information Displays CPU processor information. Events are displayed with the following information..

Critical. iRMC Address Configuration Permits the address configuration of the associated iRMC. Host Name The user can enter a host name here which is also contained in the SNMP. Backup/Restoration CMOS Backup Backup of server blade BIOS parameters. CMOS Restoration Selects the CMOS file and restore policy to restore server blade parameters.Components Severity Informational. Mezzanine-2 MUX Configuration This box enables the Mezzanine Card (Quad-Port Ethernet) in slot 2 of the server blade to be switched from the default value bays 7/8 to bays 5/6 or 5/6/7/8. Major. These ports can be switched over in pairs to bays 5/6 or singly to bay 5/6/7/8. it is shut down by means of a hard power-off after a specifiable time (1 to 7 minutes). two ports (dual) lead to bay 7 and two to bay 8. then turns off the server blade. If the smart-restore option is selected. slot ID and BIOS version. graceful shutdown and power off Shuts down the running operating system and turns off the selected server blade. Power Management The user can execute turn-on and shutdown actions of the server blade. or All Events. 56 ServerView BX900 S1 Management Blade . Description Message description. the MMB takes over the OS host name. With the default. Configuration ASR (Automatic Server Restart) Enables/disables the Boot Watchdog timer and configures the action when it times out. Power-On/Off Time The user can set up a power on/off schedule for the server blade. hard power off Turns off the system power immediately. The multiplexer (MUX for short) of this Mezzanine Card has four ports. NMI Generates a non-maskable interrupt. If this action is successful. Power Setting If the "Force Power-Off" control box is enabled and graceful shutdown of the server blade fails. Minor. hard reset Resets the server blade immediately. The server blade must be powered on before backup/restoration operation. the backup file will be displayed in the CMOS file selecting table. and after a delay turns it on again. it will be restored with verified MAC address. If the ServerView agents are installed on the server blade. There are 6 options available. Boot Options Selects the server blade LAN port for a PXE boot. power on Turns on the server blade power. Web User Interface Clicking the Clear All Entries button causes all event entries in the event repository to be cleared for the selected component. graceful shutdown and power cycle First shuts down the running operating system.

. n Blade Asset Information Manufacturer Displays the manufacturer of the storage blade.3. Production Date Displays the date the storage blade was produced. Associated Server Blades Left Side The adjacent server blade on the left-hand side. Serial Number Displays the storage blade serial number.. Product Name Displays the storage blade product name. ServerView BX900 S1 Management Blade 57 . Hardware Version Displays the storage blade hardware version. Right Side The adjacent server blade on the right-hand side. Part Number Displays the storage blade part number.5 Storage Blades Storage Blade-1 . Product Version Displays the storage blade product version.Web User Interface Components 4. Product Model Displays the storage blade product model name.

3. The user assigned name may not be longer than 31 characters and may not begin with an underscore ("_") or a digit. Model Name Displays the connection blade’s model name. The mode can also be set in the Web interface of the selected GbE connection blade.3. Product Name Displays the connection blade’s product name.Components Web User Interface 4. Power Management Power Setting The user can reset the blade after selecting the power action and clicking the Apply button. Production Date Displays the connection blade's production date. Administrative URL URL address to link to the connection blade's web homepage. Serial Number Displays the connection blade’s serial number.6 Connection Blades GbE Connection Blade Information Manufacturer Displays the connection blade's production information. Firmware Version Displays the connection blade's management firmware version. The connection blade takes the assigned name and uses it (if it was not overwritten) for the following system settings: 1. Changing the rack name (via the menu item System Unit in the Web UI) may overwrite the here defined name. 2. Management Port MAC Address Displays the MAC address of the connection blade's service port. 4. For connection blades with product name "PY CB Eth Switch/IBP 10Gb 18/8" the command reset has to be used. Configuration User Assigned Name Enter the connection blade's user assigned name. Afterwards the blade has to be rebooted using the command reload (in case of product name "PY CB Eth Switch/IBP 1Gb 36/8+2" and "PY CB Eth Switch/IBP 1Gb 36/12"). The mode can be set via the Remote Manager (CLI): (3) Console Redirection → (1) Console Redirect Connection Blade → <CB-Selection> → executing the command boot-system mode (this resets the current mode and sets the new mode). Connection Blade CLI Prompt Name Port Naming Host name DHCP Client Identifier 58 ServerView BX900 S1 Management Blade . Hardware Version Displays the connection blade’s board version. Firmware Mode Displays the firmware mode (IBP or Switch).

Management Port Settings Displays the connection blade's network setting information. Enable DHCP Sets the IP mode (DHCP or NO-DHCP) for the management IP settings of the connection blade. Current Value The IP address / subnet mask / gateway address [Current Value] is the current connection blade management IP address / subnet mask / gateway address. Restore Configuration Backup Media Here you select the medium from which the interface data between the MMB and the connection blade is to be restored (Memory. Reset Configuration Settings to default Resets the configuration settings listed below to their default values. Login Password Enter the login password for the polling function. you can click the Refresh Status button to return to the default status Not Started. Memory/USB Backup Status After you have clicked the Backup button. the MMB will issue the event log. After the backup has been completed. Stack Port Setting Enables/disables the internal stacking port (only in the case of connection blades with the product name "BX900 Connection Blade GbE 36/8+2"). USB or Local File). If the setting "Login User Name/Password" or "Enable Polling Password" is invalid for the connection blade. Login User Name Enter the login user name for the polling function. USB or Local File). this means that the parameter has not been changed by the connection blade up to this point in time. Enable Polling Password Enter the enable password for the polling function. If no change is displayed after the button has been pressed. IP Address / Subnet Mask / Gateway Address Displays the connection blade's management IP address / subnet mask / gateway address. Polling Settings Enable Period Polling Enables/disables the connection blade's period polling function. This is necessary as the parameters can also be changed via the connection blade's own management functions.Web User Interface Components The current status of the parameters is queried using the Refresh button. A new file name consisting of an identification tag and the current date is then generated. The MMB will also disable the period polling function if it is enabled. The MMB will poll the connection blade's settings every 5 minutes if this function is enabled. Memory/USB Backup Files Here you can select the version which you wish to restore from all the versions which have been backed up so far. the status is displayed here. Memory/USB Backup File You can change the name of the file containing the backed-up data here by clicking the New Name button. Backup/Restoration Backup Configuration Backup Media Here you select the medium on which the interface data between the MMB and the connection blade is to be backed up (Memory. ServerView BX900 S1 Management Blade 59 .

Afterwards the blade will reboot automatically. Native or Interop). Product Number Displays the connection blade’s product number. Hardware Version Displays the connection blade’s board version. The mode can also be set in the Web interface of the selected FC connection blade. The user assigned name may not be longer than 31 characters and may not begin with an underscore ("_") or a digit. Changing the rack name (via the menu item System Unit in the Web UI) may overwrite the here defined name. View Configuration Displays the current interface data between the MMB and the connection blade. Administrative URL URL address to link to the connection blade's web homepage. Port Naming 3.Components Web User Interface Local Backup Files Offers you the option of searching for particular versions which have been backed up in local files. FC Connection Blade Information Manufacturer Displays connection blade's production information. the status is displayed here. WWN Address Displays the WWN address for FC connection blade. Product Name Displays the connection blade’s product name. The connection blade takes the assigned name and uses it (if it was not overwritten) for the following system settings: 1. The mode can be set via the Remote Manager (CLI): (3) Console Redirection → (1) Console Redirect Connection Blade → <CB-Selection> → executing the command ag -modedisable (this resets the current mode and sets the selected mode). Configuration User Assigned Name Enter the connection blade's user assigned name. Connection Blade CLI Prompt Name 2. Date Manufactured Displays the connection blade's production date. After restoration has been completed. Management Port MAC Address Displays the MAC address of the connection blade's service port. Firmware Version Displays the connection blade's management firmware version. Serial Number Displays the connection blade’s serial number. Host name 60 ServerView BX900 S1 Management Blade . Restoration Status After you have clicked the Restore button. Firmware Mode Displays the firmware mode (Access Gateway. you can click the Refresh Status button to return to the default status Not Started. Power Management Power Setting The user can reset the blade after selecting the power action and clicking the Apply button.

After the backup has been completed.Web User Interface Components FC Domain Settings The user can find and configure the setting Domain ID for the FC connection blade. USB or Local File). When setting the FC connection blade. Restore Configuration Backup Media Here you select the medium from which the interface data between the MMB and the connection blade is to be restored (Memory. the status is displayed here. Polling Settings Enable Period Polling Enables/disables the connection blade's period polling function. The MMB will poll the connection blade's settings every 5 minutes if this function is enabled. Memory/USB Backup File You can change the name of the file containing the backed-up data here by clicking the New Name button. the MMB will issue the event log. USB or Local File). and the complete configuration will be cleared when the connection blade is disabled. A new file name consisting of an identification tag and the current date is then generated. IP Address / Subnet Mask / Gateway Address Displays the connection blade's management IP address / subnet mask / gateway address. Backup/Restoration Backup Configuration Backup Media Here you select the medium on which the interface data between the MMB and the connection blade is to be backed up (Memory. Management Port Settings Displays the connection blade's network setting information. you can click the Refresh Status button to return to the default status Not Started. xx is a hexadecimal value and the validate values range from 1 to 239. Login User Name Enter the login user name for the polling function. The MMB will also disable the period polling function if it is enabled. ServerView BX900 S1 Management Blade 61 . If the setting "Login User Name" or "Login User Password" is invalid for the connection blade. Enable Polling Password Enter the enable password for the polling function. it needs to disable itself temporarily. Enable DHCP Sets the IP mode (DHCP or NO-DHCP) for the management IP settings of the connection blade. Reset Configuration Settings to default Resets the configuration settings listed below to their default values. The setting value should be fffcxx. Memory/USB Backup Status After you have clicked the Backup button. Current Value The IP address / subnet mask / gateway address [Current Value] is the current connection blade management IP address / subnet mask / gateway address. Management Port Control This setting permits the management port (network interface for managing the connection blade) to be switched between the positions "external/Front" and "internal/MMB1 or MMB2". Login Password Enter the login password for the polling function.

. Firmware Version Displays the rear fan unit’s firmware version. 4. 62 ServerView BX900 S1 Management Blade . Fan Details Link to the rear fan unit’s details. Model Name Displays the rear fan unit’s model name. Product Name Displays the rear fan unit’s product name.7 Rear Fan Units Unit Information Manufacturer Displays the rear fan unit’s manufacturer. Serial Number Displays the rear fan unit’s serial number. 6 Monitoring Group Status Information Status Displays the overall status for the system power supply. 4. Unit Information Status Fan1-Fan8 Displays the status of fan1to fan8 in the selected power supply. View Configuration Displays the current interface data between the MMB and the connection blade. Hardware Version Displays the rear fan unit’s hardware version. OVP 12V Status Displays the OVP 12V status.Components Web User Interface Memory/USB Backup Files Here you can select the version which you wish to restore from all the versions which have been backed up so far.. CSS Component Displays whether the rear fan unit is a CSS component or not.3. After restoration has been completed.8 Power Supplies PSU-1 . Product Version Displays the rear fan unit’s product version. Local Backup Files Offers you the option of searching for particular versions which have been backed up in local files. the status is displayed here. you can click the Refresh Status button to return to the default status Not Started.3. Redundancy Displays the power redundancy status of this system. Restoration Status After you have clicked the Restore button. Production Date Displays the rear fan unit’s production date.

Temperature Displays the current temperature of the power supply. ServerView BX900 S1 Management Blade 63 . Firmware Version Displays the power supply firmware version. Current Share Status Displays the current share status. Product Name Displays the product name of the power supply unit. Serial Number Displays the serial number of the power supply unit.Web User Interface UVP 12V Status Displays the UVP 12V status. EPOW Status Displays the EPOW status of the power supply. Model Name Displays the model name of the power supply unit. OCP 12V Status Displays the OCP 12V status. Hardware Version Displays the power supply hardware version. Product Version Displays the product version of the power supply unit. PWOK Status Displays the PWOK status of the power supply. Components Information System Power Supply Unit Manufacturer Displays the production information for the power supply unit. Production Date Displays the power supply production date. AC Range Status Displays the AC range of the power supply.

This option has the following sub-functions.4. Minor.2.4 Information 4. 4.e. or All Events. Export Event Log Exports all available logs to the selected media as text files. Severity Informational. i. Description Message description. Each component which is clicked on has a different number of tabs which provide further information. Major. Event Log Filter Displays all system events and can be filtered by component and severity by selecting filtering factors and clicking the "Apply" button.4. Major. Minor.1 Asset Overview The Asset Overview supplies general FRU information (FRU = Field Replaceable Unit). Critical. Event Log Content Time Stamp Year-Month-Day HH:MM:SS.Information Web User Interface 4. Clicking on a component in the table causes its properties and operating status to be displayed. Clicking the Clear All Entries button causes all event entries in the event repository to be cleared for the selected component. Severity Informational.1 Event Log This page displays all system events and can be filtered by component and severity by selecting filtering factors and clicking the Apply button. Critical. system components which can be replaced relatively simply on the customer premises when a fault occurs.4. 4. Component Management blade or server blades. 64 ServerView BX900 S1 Management Blade .2 Logging The System Event Log function provides information on events that happened on the system.

4.4. 4. Dump Contents The contents of the post mortem dump will be shown in this section.3 System Information Dump Dump Settings Enables the user to define where a System Information Dump is to be exported to. Clicking the "View Dump" button will create a dump for viewing. ServerView BX900 S1 Management Blade 65 . Dump Contents The contents of the dump will be shown in this section.Web User Interface Information 4.4 Dump Post Mortem Dump Post Mortem Enables the user to define where System Dump Post Mortem information is to be exported to. Clicking the "View Dump" button will create a dump for viewing.

Setting a "0000" (4 zeros) value also disables the PIN. Power Switch Sometimes a server blade power-off will fail when the user initiates a graceful shutdown and hard power-off for the system. If the forced power-off function is enabled.2 Power Management Monitoring Current Power Consumption Displays the real power consumption values: Current Power. Average Power. a message to this effect is issued.5. Power History Options Enables/disables the power monitoring function and the power history period setting. Actual / Maximum. Select the radio button and click the "Apply" button.Operation Web User Interface 4. the system will power off when the forced poweroff delay has expired. PIN Settings Enable/disables the PIN for the Local Service Display and defines a 4-digit value as the PIN. Delay After Power-Off Failed Determines the forced power-off delay (1 ~ 7 minutes).5 Operation 4. Click "Send Message" to send input message to the Local Service Display. Server Blade Power Control Turn On All Server Blades Powers on all server blades sequentially. Power History Chart Displays the power consumption history chart for the history period selected. If a line is longer than 26 characters. Limitation Threshold. The message text consists of up to 7 lines with up to 26 characters per line (including blanks and new line characters). Click "Clear Message" button to clear the input text. The user can configure this function in this tab. 66 ServerView BX900 S1 Management Blade . Turn Off All Server Blades Powers off all server blades sequentially. Changes will apply after the user has clicked the "Apply" button. 4. Minimum Power. Peak Power.5.1 Local Service Display Message Sends messages from the Web UI to the Local Service Display. Remaining Output. Control Current System Power The user can control the power action of this system. Enable Force Power-Off Enables/Disables the force power-off function.

the defined limitation action will already have been performed when the warning threshold is reached. Server Blade Stop Sequence Definition Server Blade Stop Sequence Defines a sequence rule for shutting down/powering off active server blades. Threshold Definition Sets thresholds as a percentage (Relative) or as a direct value (Absolute). If monitoring is disabled. Redundancy Redundancy depends on the number of PSUs. Warning Threshold Defines the warning threshold. Display Unit Sets the measurement units (Watt or BTU) for power consumption. Limit Duration Defines the duration time limit. Server Blade Stop Action Mode in which the server blade is shut down. Number of PSUs Displays the number of PSUs which are equipped in the system unit. Scheduled Consumption Configuration Defines up to 2 different consumption modes per day. the system will automatically correct it to the next higher permissible value. PSU Dynamic Mode together with NO Redundancy can cause an immediate system power off if the last active PSU can no longer provide sufficient power. A server blade shutdown requires installed and running ServerView agents. Value must be higher than the percentage value currently reached. Action after Limit exceeded Defines which action should to be taken with the active server blades after reaching the defined limit. Enable PSU Dynamic Mode Enables/disables the PSU Dynamic Mode. Default is "off". If you enter a value which is too low. Enable Dynamic Power Control Enables/disables the dynamic power control. Consumption Control Operation Mode Sets the operation mode for all server blades and fans. This also applies when a server blade is powered on and insufficient electricity is available. If PSU Control is not activated. if the value is "on". Consumption Mode Sets consumption mode. Consumption Mode cannot be selected. Available PSUs Displays the number of PSUs which are actually activated.Web User Interface Operation Configuration Power Consumption Options Enable Power Monitoring History Enables/disables monitoring. ServerView BX900 S1 Management Blade 67 . Enable PSU Control Enables/disables PSU control. the following settings are disabled. Applies in all cases that make it necessary to stop server blades. at least 3 PSUs are necessary for a typical system configuration. Consumption Limitation Limit Threshold Defines the limit threshold.

User Shell Permits the user to access the remote manager (CLI) or Server Management CLP.1 Local Users Local User Account Enabled Displays the status of account(s) (enabled or disabled) Name Displays the user name. New User Switches to the configuration page for a new user account (see section “New Local User Account”). Special Server Blade Privileges Configure User Accounts To grant/restrict user accounts. Permissions Administrator The user has full privileges to access the system. 4. The administrators can configure the user account by clicking the user name hyperlink.5. OEM The user has full privileges for access system but is not allowed to configure a user account. Delete Deletes a user account.5.3. Name Configures the user name.3. 4. configure permission of server blades. Password Configures the password for the user account.3 User Management The User Management enables administrators having the appropriate privileges to configure local user accounts. Possible user roles are: Administrator – OEM – Operator – User.5. Permission Displays the user permission rights. Special MMB Privileges Configure System Accounts Only administrators have permission to configure system accounts Configure System Settings This special privilege enables system settings to be modified via the web interface. Confirm Password Field for double-checking the password.2 New Local User Account Configure User Account Enabled Checkbox for setting the account status (enabled/disabled). 68 ServerView BX900 S1 Management Blade . Operator The user can configure I/O modules. User The user has read permission.Operation Web User Interface 4.

4 User Session Information Provides an overview of the users currently signed in.4.g. If LDAP is disabled. Warning: If your directory server is unreachable and LDAP is enabled.5. to install OS patches.Web User Interface Operation Configure System Settings This special privilege enables the iRMC configuration variables (Config Space Variables) to be modified. This allows a user role with few privileges to be granted an additional special privilege.5.5. This privilege enables the user to configure the connection blade via a Command Line Interface which is provided or by means of web access from the MMB. e. Backup Parameter Set Selects backup parameters by groups or detail items.3. Enable Remote Storage This special privilege enables a storage medium to be accessed which is made available via the server blade’s iRMC.5. Access Bays Access to bays can be granted/restricted. 4.3. Enable Video Redirection This special privilege enables the information which is displayed on the server blade (graphic or text-based) to be redirected to the user’s web browser which is connected to the MMB. ServerView BX900 S1 Management Blade 69 . 4.4 Backup/Restoration Management 4. Backup Media Here you select the medium on which the access and configuration data is to be backed up (Memory. BIOS Parameters of Server Blade Selects available server blades to load the BIOS settings.3 Global Users Defines if the users authenticated by the directory service have to be accessible over additional directory service types. Always use SSL Login Enables/disables SSL login. This allows a user to provide the OS of a server blade with additional IO functionality. this setting disables the standard Web browser authentication/login and forces the user to sign in via HTTPS. Current BIOS Parameters Displays the current BIOS parameter values of the selected server blade. 4.1 Backup/Restoration Management – BIOS Backup Permits the complete parameter set or a subset of a selected server blade to be saved. Two aspects must be observed here: Disable Local Login Disables/enables local login. Backup Action Permits the backup destination to be specified and the backup to be started. USB or Local File). you will not be able to sign in.

it is necessary that the voltage status of the BX900 system unit should be at least "auxiliary". After the backup has been completed.2 Backup/Restoration Management – iRMC Backup Selects available server blades to load the iRMC settings. 70 ServerView BX900 S1 Management Blade . A new file name consisting of an identification tag and the current date is then generated. MMB memory).5. After the backup has been completed. Restoration BIOS Parameters The parameters can be taken from backup files or directly from a selected server blade and can be modified "on the fly" before restoration is started. i. Restore Permits the specified BIOS parameters to be restored to one or more server blades. A new file name consisting of an identification tag and the current date is then generated. This function enables a configuration of a server blade's service processor (iRMC) to be used to simplify configuration of further server blades (up to 17 in a BX900). USB or Local File). For this purpose (up to 46) defined configuration values (iRMC Config variables) from the sectors a) user management and b) IP network are backed up on a medium (USB. 4. the status is displayed here. you can click the Refresh Status button to return to the default status Not Started. Restore Loads the iRMC settings from source media and modifies the settings to restore selected parameters to selected blades.Operation Web User Interface Memory/USB Backup File You can change the name of the file containing the backed-up data here by clicking the New Name button. To permit successful backup. the status is displayed here. you can click the Refresh Status button to return to the default status Not Started. Backup Action Backup Media Here you select the medium on which the access and LAN configuration data is to be backed up (Memory. Memory/USB Backup Status After you have clicked the Backup button.e. Memory/USB Backup Status After you have clicked the Backup button. Memory/USB Backup File You can change the name of the file containing the backed-up data here by clicking the New Name button.4. Restore Action Permits the restoration destination to be specified and starts restoration. and backs up the iRMC settings using the selected parameters. Restoration Source Permits selection of available backup files or a server blade which is to be restored (as they are or modified) to one or more server blades with matching capabilities. the status display of the MMB glows green. Restoration Parameter Set Selects restoration parameters by groups or detail items.

The configuration data contained in the backup file can be edited and then be copied to a server blade or to multiple server blades of the same type. the status display of the MMB glows green. "<<" removes all available blades from the upgrading window. TFTP Update Enable Enables/disables the TFTP update. it is necessary that the voltage status of the BX900 system unit should be at least "auxiliary". i. ">>" moves all available blades to the upgrade window. "<" removes selected blades from the upgrading window.5 Firmware Update Management Blade Firmware TFTP Server IP Address To set the TFTP server IP address which contains the management blade firmware image file.Web User Interface Operation The restoration procedure requires a backup to have been made beforehand and a corresponding backup file which is either made available via USB or is already contained in the MMB's memory. 4. To permit successful restoration.e. Server Blade iRMC and Server Blade BIOS TFTP Server IP Address To set the TFTP server IP address which contains the server blade firmware image file. TFTP Boot Image File Name To set the management blade image file name. This also ensures that all service processors of the server blades have identical settings. ">" moves selected blades to the upgrade window. Clicking the "Apply" button submits the TFTP update. Clicking the "Apply" button causes the TFTP firmware update configuration to be stored and starts the firmware update if the TFTP update is enabled (enables single MMB firmware update / dual MMB firmware update). ServerView BX900 S1 Management Blade 71 . TFTP Boot Image File Name To set the server blade image file name.5.

validity and distinguished name of the subject and issuer. Certificate Signing Request CSR Generation Key size Selects the key size for the key.Operation Web User Interface 4. Organization The official name of the organization. Start User Certificate Generation Starts to generate the user certificate. 72 ServerView BX900 S1 Management Blade . and it can also be the name of the server. the common name can consist of one word.6 Certificate Handling 4.1 System Certificate Certificate Displays the details of the SSL/SSH certificate. signature algorithm.2 User Certificate User Certificate User name The user name for which the MMB will issue the certificate. including the version.6. Organization Unit Needed if different divisions of the organization have different certificates. Certificate Upload The user can paste the private key and certificate in the blank field. Country Selects the country. Email Address The contact email address.5.5. serial number. Common Name The common name is typically composed of the host + domain names. Password for User Certificate Enter the password for the user certificate. error messages will be displayed asking the user to generate the user certificate first. State/Province The state of your locality.6.5. Location The locality where your organization is located or registered. The following information may be needed for CSR generation: Download CSR and Private Key 4. Confirm Password Enter the password for the user certificate again for confirmation. If the certificate is to be used on an intranet (or internal network). Download User Certificate Downloads the generated user certificate. If the user certificate is not generated yet.

6. Force HTTPS Enables/disables Force HTTPS for Telnet.Web User Interface Settings 4. Domain Name Server: It is possible to configure two domain name servers for resolving names. Duplex Execution Mode Displays the execution duplex mode of the NIC on the management blade. Duplex Setting Mode Sets the duplex mode of the NIC on the management blade.1 Network Interface Ethernet Service LAN Configuration: IP Address Sets the management blade's IP address. Default Route Displays the value of the default route.1. Duplex Execution Mode Displays the execution duplex mode of the NIC on the management blade. Enable Client Authentication Enables/disables client authentication for HTTP. Telnet: Enable Telnet Enables/disables Telnet. ServerView BX900 S1 Management Blade 73 .6 Settings 4. Management LAN Configuration: DHCP enable Enables/disables the DHCP function. Enable HTTPS Enables/disables SSL for HTTP.6. HTTP: Port Sets the HTTP port number. HTTPS Port Sets the HTTPS port number. Subnet Mask Sets the subnet mask's IP address. Gateway Sets the gateway's IP address. Default Route Displays the value of the default route.1 System Unit 4. IP Address Sets the management blade's IP address. Gateway Sets the gateway's IP address. Subnet Mask Sets the subnet mask's IP address.

1. Drop Time Sets the Telnet connection timeout value. SSH: Enable SSH Enables/disables the SSH function.6. The SNMP trap destinations are the receivers to which the MMB sends the traps. (The group of network devices with a common VLAN ID is a VLAN group. 74 ServerView BX900 S1 Management Blade .2 SNMP This function is used for normal SNMP (community and trap) and V3 security settings. Allowed IP Address/Subnet Here you can specify an IP address or a range of IP addresses in the form of a subnetwork mask which may access the MMB. the user can configure the VLAN. SNMP Trap Destination Displays the SNMP trap destination table. SNMP and Telnet.255. SSH. A maximum of 5 communities can be added to this table. New Community Enter the community name.255. The default value is 255. VLAN Network Mask Sets the VLAN network mask. The receiver must be a member of the same community. the default is 900 seconds. The integers 1 to 4094 are supported. VLAN The MMB supports up to 10 VLAN IDs. Group Enable The VLAN group can be enabled/disabled here. VLAN IP Address Sets the VLAN IP address.Settings Port Web User Interface Sets the Telnet port number. Permitted protocol Selects the permissible protocol type. 4. A maximum of 5 trap destinations can be added to this table. SSH Port Sets the SSH port number. the Telnet connection will be cleared and the user has to log in again. select the access permission and click the "New" button to submit a new addition. IP Filter The MMB enables user to configure up to 10 valid IP addresses for HTTP/HTTPS. New Trap Destination Either the IP address of the trap receiver or the receiver's DNS name must be entered here. If there is no activity in this time period. After clicking the "Modify" button. Basic SNMP Communities Displays the SNMP communities table.) Group ID Identifies different VLAN group IDs.255 (permits any IP address).

Primary/Secondary SMTP Server Configuration SMTP Server Sets the domain name or IP address of the SMTP server. The SNMP V3 trap destinations are the receivers to which the MMB sends the traps. Authentication Hash Method Selects the hash method (MD5 or SHA).3 Alerting Event Configuration This page provides the event filtering configuration. Event Log filter Selection of Event Source and corresponding Error Forwarding Level (SEL level needs to be sent). Server Blade Power On/Off Enables/disables the server blade’s Power On/Off Event Log function. SMTP Retry Delay (0-255) Sets retry interval if the SMTP server response failed. Global Email Paging Configuration SMTP Retry Sets the retry count (0-7) if the SMTP server response failed.Web User Interface Settings SNMP V3 V3 User Setting Up to 10 user accounts can be configured. 4. No Authentication. If an event occurs. A maximum of 5 trap destinations can be added. Permission Selects the read/write permission.1. User <n> User name of user <n>. Authentication Password Enter the authentication password. V3 Trap Destination Displays the V3 trap destination table. Privacy Password Enter the privacy password. New Trap Destination An entry (trap destination) can be added by entering the trap destination address and selecting User and Event Type. ServerView BX900 S1 Management Blade 75 . Management Blade Event Log Enables/disables the management blade’s Wrap Around Event Log function. Mail Configuration Email Alerting Enables/disables the mail alert function. Security Level Determines the security level (Authentication. an alerting email can be sent if these settings are configured. Select User Selects a user <n>. Privacy). SMTP Port Sets the port number of the SMTP server.6.

4 Date Time Controller Time Sets the date and time for the MMB. Sync Mode There are two sync modes available: – Sync Afterward: Only when the management blade time is ahead of the NTP server time will the management blade synchronize the time from the NTP server – Sync Always: The management blade always synchronizes the time from the NTP server. 4. Last Sync Date/Time Displays the latest date/time that the management blade synchronizes with the NTP Server. NTP Server 1 Enter the NTP server IP address. AUTH Password Enter the authentication password.2 Refresh Automatic Refresh Enable Automatic Refresh Enables/disables the Automatic Refresh Function. Auth-Login.Settings Web User Interface Auth Type Selects the authentication type. Date/Time Sets the time zone of this system and enables the Daylight Saving Time. Refresh Cycle Sets the refresh interval for automatic refresh. Network Time Protocol Enable NTP Enables/disables the NTP function.6.3 Language The user can set the language of the Web UI and/or of the Local Service Display.6. The valid value is 1 to 15 minutes. the MMB takes this second address if the first one cannot be reached).6. administrator name and phone number here. 4. AUTH User Name Enter the authentication user name. NTP Server 2 Enter an alternative NTP server IP address (if "Redundancy" is set. 4.1. 76 ServerView BX900 S1 Management Blade . Mail Format-dependent Configuration The user can configure the sender email address. Up to 5 user email addresses that can be modified are supported. Auth-Plain and Auth-Cram-md5 are supported. The format is (MM/DD/YYYY) and (HH:MM:SS).

The PIN number protects the Local Service Display against unauthorized access. gateway.Web User Interface Settings 4. Date/Time Settings Setting date and time for the MMB. the PSU dynamic mode and the maximum power consumption for the system unit. subnet mask.6. Ekeying Check Reports the number of ekeying mismatch conflicts. Power Settings Enables the user to adjust the PSU redundancy level. Export Settings The Export Settings menu is used to copy the current system unit settings to a file on a USB memory stick. system contact. rack name. The wizard appears when the user first signs into the Web UI and is displayed until the first time it has been completed successfully.4 Base Configuration Wizard The Base Configuration Wizard facilitates system startup. Caution: <Rack Name> and <System Name> may each only consist of a maximum of 13 characters and may not begin with an underscore ("_") or a digit (7-bit ASCII characters only). ServerView BX900 S1 Management Blade 77 . system location. Identification Settings The Identification menu provides input boxes to define the system name. Shows the details of each ekeying mismatch conflict. Import Settings Enables the system unit settings to be imported from a USB memory stick to the system unit. The format is (MM/DD/YYYY) and (HH:MM:SS). DNS addresses. Network Settings IPv4 The Network IPv4 menu provides spin boxes to define the IP address. Language Selection The user can set the language of the Web UI and of the Local Service Display. PIN Settings The PIN menu enables the user to define a PIN number.

Settings Web User Interface 78 ServerView BX900 S1 Management Blade .

Figure 38: System unit with 4 PSUs and 2 fans ServerView BX900 S1 Management Blade 79 . as can be seen on the Power Management → Configuration page. 2 fans are also used (see figure). It is important to distinguish here between the PSUs which can be seen in the Navigation Frame and the number of PSUs which are actually activated (item Available PSUs on the Power Management → Configuration → Power Consumption Options page).5 Power Management The power consumption of a BX900 S1 depends on the number of PSUs which are equipped in the system unit. In addition to these 4 PSUs. The example below is based on a system unit with 4 activated PSUs.

Information on the type and power consumption can be found on the sticker on the underside of the PSU (see figure). The reason is that a fan can also be mounted in a PSU slot. In the status overview on the welcome page both devices are specified correctly as fans (see figure): Figure 39: Power Supply Status display I If a PSU fails. the number of Available PSUs is decremented (in the example from 4 to 3): Figure 40: Number of Available PSUs The power consumption of a PSU depends on its type.Power Management I Not only the PSUs but also the fans are displayed as "PSU" in both the Navigation Tree (green dot) and in the Rear View (tooltip display). Figure 41: Underside of a PSU with sticker I The maximum output power provided by the power supply depends on the voltage of the supply network and ranges from 1165W (with 100V – 120V) to up to 2685W (with 200V – 240V). 80 ServerView BX900 S1 Management Blade .

the PSUs draw 19200W from the supply network. On the output side 6 activated PSUs make a maximum of 17280W (= 6 x 2680W) available to the system (with a voltage of 200V – 240V). all of which are activated (available status). In the 2nd line (bar chart) the current primary input power of the PSUs and the maximum possible power consumption of the active PSUs are displayed in the form of a bar chart and in figures in watts.1 Power Consumption display The total power consumption is displayed at the top right in the Status Frame: Figure 42: Display of the power consumption in the Status Frame Our sample display is based on a fully equipped system unit with 6 PSUs. which is dynamic. This value is changed by the system if Dynamic Mode is set. The maximum possible power consumption can vary dynamically if the Dynamic Mode option was enabled on the Power Management → Configuration page (see section “Dynamic Mode” on page 89). ServerView BX900 S1 Management Blade 81 . In the case of this maximum performance.Power Management Power Consumption display 5. The 3rd line provides information about the secondary output power which is still available for the blades up to the specified upper limit.

See also figure 61 on page 92 and figure 62 on page 93 below.2. 82 ServerView BX900 S1 Management Blade . Various settings can also be made in the "Power History Options" box.1 Monitoring tab The power consumption values from the field at the top right in the Status Frame are displayed in a table and a Power History Chart in the Monitoring tab.Control via tabs Power Management 5. Monitoring tab 2. Control tab 3.2 Control via tabs On the Power Management page three tabs are available which are described in detail below: 1. Figure 43: Power Management – Monitoring tab I The metric power unit can be switched from watts to BTU (and vice versa) both in this tab and in the Configuration tab. Configuration tab 5.

Figure 45: Power Management – iRMC page Re number 2 in figure 44 (Power Switch) In the case of Enable: if "graceful shutdown and off" (in 1 and 3) was selected and the server does not shut down in the time specified under "Delay After Power-Off Failed". the server blades assume the status which is set in the iRMC (see figure) after the system unit has been powered on. ServerView BX900 S1 Management Blade 83 . Re number 3 in figure 44 (Server Blade Power Control) Here all server blades can be shut down (executed in "graceful shutdown and off" mode) and started up when the system unit is running. a hard power-off is enforced for the server blade.2 Control tab The Control tab is used to control how the system unit and server blades are powered on and off.2. If a hard power-off is selected for the unit or the Force Power-Off has occurred.Power Management Control via tabs 5. Figure 44: Power Management – Control tab Re number 1 in figure 44 (Current System Power) The system unit can be switched on/off with "hard power off" or "graceful shutdown and off".

2.Control via tabs Power Management 5.3 Configuration tab Various settings for and dependencies on the power consumption are controlled in the Configuration tab. Figure 46: Power Management – Configuration tab 84 ServerView BX900 S1 Management Blade .

Power Management Control via tabs Re number 1 in figure 46 (Consumption Mode) The following modes can be selected: Figure 47: Consumption modes Depending on the mode selected. The mode selected is also displayed at the top in the Status Frame: Figure 48: Consumption modes ServerView BX900 S1 Management Blade 85 . the Apply buttons of the following boxes are shaded dark gray/enabled (can be used) or shaded light gray/disabled (cannot be used).

"Minimum Power" or "Best Performance" can be enabled as Operation Mode: Figure 49: Operation modes When "Minimum Power" or "Best Performance" is selected. the iRMC of the server blades is overridden by its settings (red text): Figure 50: Power Management – iRMC page The mode selected is also displayed at the top in the Status Frame: Figure 51: Selected operation mode 86 ServerView BX900 S1 Management Blade .Control via tabs Power Management Re a) in figure 48 (Consumption Control) If "Consumption Control" has been selected as the Consumption Mode. the Apply button of the box is shaded dark gray (enabled) so that "disabled".

Power Management Control via tabs Re b) in figure 48 (Consumption Limitation) If "Consumption Limitation" is selected. ServerView BX900 S1 Management Blade 87 . 17. If server blades are entered in the right-hand box. 2. the system shuts down the server blades in descending order from 18. Only server blades (slots) which are already powered on and therefore known to the Consumption Limitation function can be powered on/off. Figure 53: Consumption Limitation: shutdown I If Consumption Limitation is activated. Consumption Limitation should be activated when the system is up and running and constraints occur that require power consumption reduction activities. The Consumption Limitation function must disabled prior to the power-on procedure of additional blades. the system shuts down (starting with row 1) as many as required to ensure that the limit is fallen below. etc. 3. 16. server blades which are still powered off will not be allowed to power on. the mode is displayed at the top in the Status Frame and initially has no direct influence on the configuration in the iRMC: Figure 52: Consumption Limitation You can define how the box reacts if the limit is exceeded: if no server blades are contained in the right-hand box but the system needs to power off server blades.. all server blades which are expected to be used during operation must be powered on. Best practice: 1. but only as many as required to ensure that the limit is fallen below. Before Consumption Limitation is activated.

the mode is displayed as "on" at the top in the Status Frame (green arrow) and initially has no direct influence on the configuration in the iRMC.Control via tabs Power Management Re c) in figure 48 (Scheduled Power Consumption Mode) If "Scheduled Power Consumption Mode" is selected. What type of "Power Consumption Mode" is valid in a particular timeframe is also displayed at the top in the Status Frame (red arrow): Figure 54: Scheduled Power Consumption Mode Re number 2 in figure 46 (PSU Control) Only when "Enable PSU Control" is enabled (arrow) is it possible to work with Dynamic Mode and Redundancy Mode: Figure 55: Enable PSU Control 88 ServerView BX900 S1 Management Blade .

2. Figure 56: Dynamic Mode and Redundancy 2+1 Example 2: Dynamic Mode and No Redundancy Function like "Dynamic Mode and Redundancy 3+3 (= Full Redundancy)". and PSU-4 and PSU-5 remain on standby. Example 3: Dynamic Mode and Redundancy 5+1 In the case of minimal power consumption. Dynamic Mode switches PSU-3 to active. Dynamic Mode switches PSU-2 to active and PSU-5 to active standby. PSU-3 and PSU-4 remain on standby (see figure). PSU-1 is active and PSU-6 is on active standby. If more power is required. Example 1: Dynamic Mode and Redundancy 3+3 (= Full Redundancy) In the case of minimal power consumption. Dynamic Mode switches PSU-2 to active.1 Dynamic Mode Dynamic Mode means that the power currently needed is calculated and then only as many PSUs as are required are switched on. PSU-1 is active and PSU-6 is on active standby. All other PSUs are on standby. ServerView BX900 S1 Management Blade 89 .Power Management Control via tabs 5. PSU-3. and so on. All other PSUs are on standby. If more power is required. If more power is required.3. PSU-4 and PSU-5 remain on standby.

Example 3: Redundancy 3+1 (and 6 PSUs) PSU-1. If one PSU-1 through PSU3 now switches to defective. Figure 58: No Dynamic Mode and Redundancy 3+1 90 ServerView BX900 S1 Management Blade .2.Control via tabs Power Management 5. All the PSUs which have been configured are powered on.3. PSU-4 and 5 are on standby. 6 on active standby (see figure). 2. PSU-4 becomes active (see figure). Example 1: Redundancy 3+3 (= Full Redundancy) PSU-1. 3 are active and PSU-6 is on active standby.2 No Dynamic Mode No Dynamic Mode means that the power currently needed is not calculated. 3 active and PSU-4. Figure 57: No Dynamic Mode and Redundancy 3+3 Example 2: No Redundancy All PSUs are active. 5. 2.

Display for "Threshold Definition = Absolute": in watt: Figure 59: Threshold Definition = Absolute ServerView BX900 S1 Management Blade 91 .Power Management Control via tabs Re number 3 in figure 46 (Threshold Definition) This setting defines whether the specification of Limit Threshold for Consumption Limitation should be made in percent (= Relative) or as a direct value (= Absolute) (see figures).

Switchovers come into effect at various places in both tabs (see the figures below). Monitoring tab: Figure 61: Metric power unit – Monitoring tab 92 ServerView BX900 S1 Management Blade .Control via tabs Display for "Threshold Definition = Relative": in percent: Power Management Figure 60: Threshold Definition = Relative Metric Power Unit The metric power unit can be switched from watts to BTU (and vice versa) both in this tab and in the Monitoring tab.

Power Management Configuration tab: Control via tabs Figure 62: Metric power unit – Configuration tab ServerView BX900 S1 Management Blade 93 .

.

Installing a Windows Server First a Windows Server Operation System (Microsoft Windows Server 2003 or 2008. eDirectory (for Windows and Linux systems) 6. OpenLDAP (for Linux systems) 3. in the example Windows Server 2003) is installed on any server.1 Configuring an Active Directory Server 1. After installation has taken place. Active Directory (for Windows systems) 2.6 User Management There are three interfaces to User Management: 1. a configuration interface appears on which the required roles are configured: – Domain Controller Active Directory – DNS Server – DHCP Server (optional) Figure 63: AD – server roles ServerView BX900 S1 Management Blade 95 .

the OU SVS must be located on the first level below the domain (cf.). Here only the OU AuthorizationRoles which must be created within a department need be borne in mind. Specifically. Figure 64: Typical LDAP structure Example of an LDAP structure (OU) SVS (OU) Declarations (OU) AuthorizationRoles (Group) Administrator (Members from: domain/SVS/Declarations/Privileges/iRMC_MMB) (Member) CfgConnectionBlade (Member) IpmiLanAdmin (Member) IpmiSerialAdmin (Member) iRMCsettings (Member) RemoteStorage (Member) UserAccounts (Member) VideoRedirection (Group) CustomRole (Member) IpmiLanUser (Member) IpmiSerialUser (Member) VideoRedirection (Group) Maintenance (Member) IpmiLanOem (Member) IpmiSerialOem (Member) iRMCsettings (Member) VideoRedirection (Group) Observer (Member) IpmiLanUser (Member) IpmiSerialUser (Group) Operator (Member) IpmiLanOperator (Member) IpmiSerialOperator (Member) VideoRedirection 96 ServerView BX900 S1 Management Blade . A sample configuration is described here. Declarations. The groups contained in this must be derived from the path Domain/SVS/Declarations/AuthorizationRoles. etc.Configuring an Active Directory Server User Management 2. figure 64 on page 96). you must set up a particular structure consisting of so-called Organizational Units (OUs) and Groups and assign the Groups to OUs. Manual creation of an LDAP structure (based on Microsoft Active Directory) To permit the management blade to be accessed by means of an LDAP user. In addition. otherwise correct operation cannot be guaranteed. You must ensure the names of the OUs and groups are spelt correctly. this means that they must have the names described in the section “Example of an LDAP structure” on page 96 (SVS. How many departments there are and what they are called is determined by the administrator ("QA2" in the example).

The OUs must be configured in accordance with the schema shown above. groups must be created within the OUs (cf. ServerView BX900 S1 Management Blade 97 .User Management (Group) SerialUser (Member) IpmiSerialUser (OU) Privileges (OU) iRMC_MMB (Group) CfgConnectionBlade (Group) IpmiLanAdmin (Group) IpmiLanOem (Group) IpmiLanOperator (Group) IpmiLanUser (Group) IpmiSerialAdmin (Group) IpmiSerialOem (Group) IpmiSerialOperator (Group) IpmiSerialUser (Group) iRMCsettings (Group) RemoteStorage (Group) UserAccounts (Group) VideoRedirection (OU) Departments (OU) QA2 (OU) AuthorizationRoles (Group) Administrator (Group) Maintenance (Group) Observer (Group) Operator (OU) UserSettings (OU) iRMC_MMB (OU) PreferredShell (Group) IpmiBasicMode (Group) IpmiTerminalMode (Group) None (Group) RemoteManager (Group) SmashCLP Configuring an Active Directory Server figure 65 shows the context menu for creating an organizational unit. If it already exists. figure 67 on page 98). Figure 65: Creating an organizational unit As described above. figure 66 on page 98). it must be modified (cf. The group scope "Global" and the group type "Distribution" must be selected here. The group name (pre-Windows 2000) is a unique name.

members must be assigned to the groups from Domain/SVS/Declarations/AuthorizationRoles. These come from the path Domain/SVS/Declarations/Privileges/iRMC_MMB and can be selected freely by the administrator as required. 98 ServerView BX900 S1 Management Blade .Configuring an Active Directory Server User Management Figure 66: Creating a group Figure 67: New group Finally.

User Management Configuring an Active Directory Server Figure 68: Members of the Administrator group ServerView BX900 S1 Management Blade 99 .

AuthorizationRoles must be set in the next step (cf.Configuring an Active Directory Server User Management Assigning Domain users to the MMB To enable a user to log in on the management blade as a domain user. LDAP Type: Windows Active Directory 2. LDAP Server IP: IP of the Domain Controller 3. Special User Account/Password: Not required The IP settings and the DNS server must also be adjusted to the network concerned. Root Domain Name: Name of the domain 4. LDAP Base DN: Assigned automatically 5. In the AD Management select the AuthorizationRoles item (SVS – Departments – XY – AuthorizationRoles) 3. 1. 100 ServerView BX900 S1 Management Blade . and the time on the management blade must be synchronized with that on the AD server. 1. User LDAP Base DN: Not required 6. Create a user if none exists 2. Settings on the Management Blade figure 70 shows an example of the settings required for communication with an Active Directory. User LDAP Department: Department configured by LDAPDeployer 7. figure 69 on page 100). Add users to roles to grant the particular authorization (multiple selection is permitted for a user) Figure 69: AD AuthorizationRoles 3.

: ad@qa2. figure 72).User Management Configuring an Active Directory Server Figure 70: LDAP settings 4. ServerView BX900 S1 Management Blade 101 . Figure 71: Logging in as an AD user Whether a login was correct can be checked on the web interface (cf.local.g. cf. The syntax is: "user-name@domain" (e. figure 71). the domain is appended in the login mask. Logging in on the Management Blade as an AD User When a user logs in on the management blade as an AD user.

Configuring an Active Directory Server User Management Figure 72: AD user logged in 102 ServerView BX900 S1 Management Blade .

The services required were selected when installation took place: – openLDAP Server – DNS Server – DHCP Server (optional) figure 73 shows the configuration of the openLDAP Server using Yast. the domain "qa2. Figure 73: Configuration of openLDAP with Yast ServerView BX900 S1 Management Blade 103 . Installing the openLDAP Server A Suse Linux Enterprise Server 10 is taken as a basis. Both of these values are required for further configuration activities.dc=qa2. Among other things.User Management Configuring an openLDAP Server 6.dc=local" and the root DN "cn=Administrator" which were assigned during installation can be recognized.local .2 Configuring an openLDAP Server 1.

Figure 74: DHCP Server 104 ServerView BX900 S1 Management Blade .Configuring an openLDAP Server User Management 2. This installation can be performed later or while the overall system is being installed. Configuring the DHCP Server (optional) This section uses screenshots to illustrate the optional configuration of a DHCP Server.

User Management Configuring an openLDAP Server Figure 75: DHCP Server card selection Figure 76: DHCP Server LDAP support ServerView BX900 S1 Management Blade 105 .

Configuring an openLDAP Server User Management Figure 77: DHCP Server address range 106 ServerView BX900 S1 Management Blade .

Manual creation of an LDAP structure (based on Microsoft Active Directory)” on page 96 above. figure 78 shows the result of a successful configuration: Figure 78: LDAP structure ServerView BX900 S1 Management Blade 107 .User Management Configuring an openLDAP Server 3. Configuring the LDAP structure See the example in section “2.

Figure 79: User management 108 ServerView BX900 S1 Management Blade . figure 79).Configuring an openLDAP Server User Management Assigning Domain users to the MMB The next step is to create/edit users who are to be granted access to the management blade. The easiest way to do this is to use Yast's user management (cf.

User Management Configuring an openLDAP Server After the required users have been created. Figure 80: LDAP browser ServerView BX900 S1 Management Blade 109 . The password assigned when the LDAP server was installed is required to do this. the LDAP browser is started from Yast.

Configuring an openLDAP Server User Management The path "ou=AuthorizationRoles" of the department concerned is selected in the tree structure (cf. Figure 81: LDAP authorization roles 110 ServerView BX900 S1 Management Blade . figure 81).

Figure 82: Assigning users ServerView BX900 S1 Management Blade 111 .ou=people.: uid=username.g.dc= qa2.dc=local) [cf. A user is added by entering them under the "member" item (e. figure 82]. Clicking on the "Entry Data" tab makes role-specific properties visible.User Management Configuring an openLDAP Server The role which is to be assigned to a user is then selected.

"cn=Administrator. Figure 83: LDAP settings on the management blade 112 ServerView BX900 S1 Management Blade . Root Domain Name: Name of the domain 4.dc=local") 8. User LDAP Department: Department configured by LDAPDeployer 7. LDAP Server IP: IP of the Domain Controller 3. Special User Account: Special user who takes over communication between the MMB and LDAP Server (e.dc=qa2. and the time on the management blade must be synchronized with that on the AD Server.g. LDAP Type: OpenLDAP 2.Configuring an openLDAP Server User Management 4. Settings on the Management Blade figure 83 shows an example of the settings required for communication with an openLDAP Server. LDAP Base DN: Assigned automatically 5. Special User Password: LDAP password which was assigned when the server was installed The IP settings and the DNS Server must also be adjusted to the network concerned. User LDAP Base DN: ou in which the users are stored 6. 1.

Figure 84: Logging in on the management blade as an LDAP user ServerView BX900 S1 Management Blade 113 . Logging in on the Management Blade as an LDAP user The login on the management blade takes place without specifying the domain name using a user who is created on the LDAP Server and assigned to an AuthorizationRole.User Management Configuring an openLDAP Server 5.

2 System Requirements Ê OpenSSL must be installed.3 Configuring an eDirectory Server 6.tgz for SuSE. e.1 Software Components – eDirectory 8. in other words FW_SERVICES_EXT_TCP="8080 8443 9009 81 389 636". there is a new directory called eDirectory.0.3. 6. If it is not yet installed.3 Installation A Linux server system must be fully installed and running.1 Installation and Setup of eDirectory This chapter gives a detailed description of the steps needed to install and configure eDirectory (formerly known as NDS (Novell Directory Services)). Ê Extract eDirectory: tar -xzvf 20060526_0800_Linux_88-SP1_FINAL.1. This file must contain the following line (in addition): 224. install it before proceeding with eDirectory installation.g. 114 ServerView BX900 S1 Management Blade . In order to do that for SuSE.0. Ê Add the ports to FW_SERVICES_EXT_TCP. The following was tested on SLES 10.e. for OpenSuSE: Ê Edit the file /etc/sysconfig/SuSEfirewall2. we create a new file (or extend an existing one): /etc/sysconfig/network/ifroute-eth0 where eth0 should be changed to fit the system configuration.0 0. The firewall must be configured to allow connections to ports 8080.8 (20060526_0800_Linux_88-SP1_FINAL.1. 20060526_0800_Linux_88-SP1_FINAL.3. 8443.Configuring an eDirectory Server User Management 6.tar.tar. – The SSL certificate shall have a key size of1024 bits and algorithm md5RSAEnc. The following requirements apply: – eDirectory shall have a defined structure.0.gz) – eDirectory 8. i. After the archive has been extracted. 9009.gz have been copied into this directory. otherwise iMan_26_linux_32. 512 MB main memory is required.0.gz) 6.gz. Below we assume that /home/eDirectory is the directory where all the files needed for installation are stored. iMan_26_linux_64.tar.8 (eDir_88_iMan26_Plugins. 389.npm) – iManager (iMan_26_linux_64. According to the installation guide. 81. Ê Get root privileges (su) and change into /home/eDirectory: cd /home/eDirectory.1. 636.tar.3.tgz) – ConsoleOne (c1_136f-linux. – eDirectory shall be installed on Linux.3. 6. providing LDAP connectivity over SSL. the system shall be enabled for multicast routing.0.gz.0 240.0 eth0 eDirectory eDirectory must be installed with root privileges.tar.0.tgz and c1_136f-linux.

After installation you need to update some environment variables with the paths to eDirectory: Ê Edit your configuration file (in the example./iManagerInstallLinux. export LD_LIBRARY_PATH=/opt/novell/eDirectory/lib:/opt/novell/eDirectory/lib/ndsmodules: /opt/novell/lib:$LD_LIBRARY_PATH.bin.tgz archive to install it on SLES10 and OpenSuSE.User Management Ê Change to the setup of eDirectory: cd eDirectory/setup. Ê Extract iManager: tar -xzvf iMan_26_linux_64. Accept the EULA with "y". Ê Insert the following lines before "# End of …" 1. 2. Press [ENTER]. Ê Choose "1-Novell iManager 2. export MANPATH=/opt/novell/man:/opt/novell/eDirectory/man:$MANPATH. Ê Accept the EULA with "y". Ê Change to installs of iManager: cd iManager/installs/linux. Installation of Novell eDirectory Administration Utilities Ê Change to the setup of eDirectory: cd eDirectory/setup. Use the *_64. /etc/bash. 3. – Choose "1-Yes" to download the plug-in. JVM" for installation. Ê Enter "2" when prompted for what to install. Close the terminal and open a new terminal again in order to enable the exported environment variables. ServerView BX900 S1 Management Blade 115 . export PATH=/opt/novell/eDirectory/bin:/opt/novell/eDirectory/sbin:$PATH./nds-install. Ê Ê Ê Invoke the installation script: .6. Ê Go through the EULA step by step and accept it. After the archive has been extracted. Ê Invoke the installation script: . Ê Press [ENTER]. Ê Get root privileges (su) and change to /home/eDirectory: cd /home/eDirectory. Ê Press [ENTER]. Tomcat. Ê Administration utilities will then be installed. Configuring an eDirectory Server Installation of Novell eDirectory Server Ê Enter "1" when prompted for what to install. Ê Invoke the installation script: .tgz. there is a new directory called iManager. Ê Choose the language for installation messages.bashrc). Ê Press [ENTER]. Ê eDirectory packages will then be installed. export TEXTDOMAINDIR=/opt/novell/eDirectory/share/locale. iManager iManager is the recommended utility to administrate eDirectory./nds-install . 4.

Ê Choose the language to install. – Enter "fwlab" as the tree name. because ConsoleOne needs root privileges.gz. ConsoleOne ConsoleOne is another utility to administer eDirectory. Ê Change to configuration directory: cd /etc. The program looks on the internet for downloads. – Accept the default jk connector port (9009) for tomcat. You can log in to iManager afterwards using a web browser and the URL: https://IP-ADDRESS-OF-SERVER:8443/nps Novell recommends MS Internet Explorer or Mozilla Firefox for this task. – Press [ENTER] to use the default path.Configuring an eDirectory Server User Management – Press [ENTER] to use the default download path. – Choose to download "All" plug-ins. – Enter "root. Ê Edit your configuration file (in the example. Ê Change to Linux: cd Linux.nds if it does not exist: touch hosts.tar. Ê Insert the following line before "# End of …" 1. Firefox could accidentally block pop-up windows (context menu). – Choose "1-Yes" to install plug-ins which are available locally. but it is also OK to use the path of any other installed java runtime. Add our tree to the configuration file.nds) or SLP service and multicast. Ê Invoke the installation script: . Ê Get root privileges (su) and change to /home/eDirectory: cd /home/eDirectory. ConsoleOne needs the path to an installed java runtime. To do this throughout the system. ConsoleOne retrieves the available trees either by means of a local configuration file (hosts. We are making this throughout the system for the case that a regular user has been granted root privileges). Ê Create hosts.4. – Accept the default SSL port (8443) for tomcat.nds Ê Append the following line: 116 ServerView BX900 S1 Management Blade . export C1_JRE_HOME=/opt/novell/j2sdk1. there is a new directory called Linux. after which you will be prompted to select which plug-ins you want to install. Ê Extract ConsoleOne: tar -xzvf c1_136f-linux. – Accept the summary with "1-OK…" and continue installation. After the archive has been extracted.bashrc). I We are using the java runtime installed with eDirectory. /etc/bash. – Choose "2-No" to automatically configure apache (not mandatory). (In principle it is sufficient to do this for the superuser root.2_05/jre. Ê Enter "8" to install all snap-ins./c1-install. which can be exported to the environment variable C1_JRE_HOME. – Accept the default port (8080) for tomcat. This will take several minutes. you must edit the bash profile.fsc" for the authorized administration user.

cn=admin. please reboot the server so that the configuration takes effect.g. Server Context: The fully distinguished name of the container under which the server object resides. ServerView BX900 S1 Management Blade 117 . NCP Port: 81. i.g.dc=mycompany. MY_TREE. dc=organization.4 Configuration of eDirectory Create an NDS Tree Before creating the NDS tree. "mycompany".3.User Management 1. Configuration file: /home/root/instance0/nds. please define essential information about the tree which is to be to created: TREE NAME: Name that you want to give your tree. Ê Enter "c" to create a new instance. mycomputer. MY_TREE. e. Install Role-Based Services Ê Go to "Configure/Role Based Services/ RBS configuration". Ê Enter … I After finishing configuration of your NDS tree. e.conf Password for the admin user: Ê Open a terminal box. Ê Enter "y" to create a new tree. Ê Enter TREE NAME. Ê Change to /home/eDirectory.1.g.dc=mycompany. Ê Enter Server Name. #Syntax: TREENAME. Ê Assign RBS2 to the container to be managed. the name of the machine the LDAP server runs on. Instance location: /home/root/instance0.g. Ê Run the RBS configuration wizard. FQDN:PORT 2. Ê Enter "y" to continue. Configure eDirectory for LDAP Log in to iManager using a Web browser and an admin account. Configuring an eDirectory Server 6. Admin User: E. in the example above. e. lin36-root-0.e. Must be unique in your network.dc=organization. Ê Start "ndsmanage".mydomain:81 To start ConsoleOne later: /usr/ConsoleOne/bin/ConsoleOne. Server Name: The representation of the instance of a server object in eDirectory.

This tab has a drop-down list showing all installed certificates in this system. In order to use LDAP without SSL: 1. You can use ConsoleOne to create an RSA/MD5 certificate 1042 bytes in length. Ê Go to the root of your company structure. Ê Select "View Objects" . Ê Browse for the eDirectory-specific plug-in package "eDir_88_iMan26_Plugins. Ê Open ConsoleOne.npm". 2. If you are not sure. key 1024 2. Use your administration account to provided authentication for the LDAP server. Configure eDirectory for Non-SSL Use Anonymous logins and plaintext passwords over unsecured channels are disabled by default. Ê Select the desired certificate in the certificate drop-down list. e. Configure Role-Based Services Ê Click on available modules: Ê Install all modules needed for LDAP. Configure eDirectory for SSL Use The use of SSL/TLS is enabled by default in eDirectory. signature RSA/MD5 A new certificate of the desired type is created. A temporary certificate is created during installation. Ê Go to LDAP\Ldap Options\LDAP Server → Connection tab.g.Configuring an eDirectory Server User Management Install Plug-Ins Ê Go to "Configure/Plug-in installation/Available Novell Plug-in Modules". install all. Ê Log in to iManager using valid credentials. Ê Uncheck "Require TLS for Simple binds with password". Ê Step down the object-tree to the "LDAP Server" object. 118 ServerView BX900 S1 Management Blade . Lower Bind Restrictions Ê Log in to iManager using valid credentials. Ê Select Install. This means it is not possible to log in and browse an eDirectory server without an SSL connection. BMC FW is configured to use RSA/MD5 certificates for the SSL connection.: [treename\mycompany\myorganization] Ê Select New Object → NDISPKI key material → custom: 1. Ê Select "Roles and Tasks View". Ê Go to LDAP\Ldap Options\LDAP Group → General tab. Enable a non-SSL connection for LDAP: Ê Open iManager in the Web browser. SSL or TLS 3. However. To enable this certificate for the SSL LDAP connection use iManager: Ê Open iManager in the Web browser Ê Go to LDAP\Ldap Options\LDAP Server → Connection tab. Ê Uncheck "Require TLS for all operations".

Reload the LDAP configuration. Ê Press the "Apply" button of "Other" sheet. Ê Press the "OK" button. Ê Select "ldapBindRestrictions" of "Valued Attributes".User Management Ê Click on that object and select "Modify Object" from the context menu. Ê Open the "Other" sheet in the right-hand (content) frame. Ê Press the "Edit" button. Ê Set the value to "0". Configuring an eDirectory Server ServerView BX900 S1 Management Blade 119 .

Configuring an eDirectory Server

User Management

Test Access to eDirectory Using the LDAP Browser
Once you reach this point, you should be able to connect to the eDirectory server using an LDAP browser utility. Ê Try to log in using the administrator account (in the example below we presume the administrator name is "admin") using an SSL connection. If not successful: Ê Check if SSL is enabled (see “Configure eDirectory for SSL Use” on page 118).

Figure 85: Administrator account with SSL

Ê

Try to log in using the admin account without an SSL connection.

Figure 86: Administrator account without SSL

If not successful: Ê Lower bind (see “Configure eDirectory for Non-SSL Use” on page 118).

6.3.1.5 iRMC Integration in eDirectory Import the iRMC LDIF File to eDirectory
Ê Open iManager in a Web browser. Ê Go to "eDirectory Maintenance" and make use of the ICE (Import Convert Export) Wizard (see figure 87 on page 121). Ê Select "Import data from file on disk" → Next. Ê Browse for your LDIF file.

120

ServerView BX900 S1 Management Blade

User Management Ê Uncheck "exit on error" → Next. Ê Enter the DAP server and admin account data → Next. Ê Press "Finish".

Configuring an eDirectory Server

I 1. Use an SSL connection for import (port 636).
2. Use LDAP protocol version 2.

Figure 87: ICE Wizard

ServerView BX900 S1 Management Blade

121

Configuring an eDirectory Server

User Management

6.3.2 Installation of eDirectory Server
Regrding the installation, please refer to the iRMC LDAP User Guide.

6.3.3 Configuring the LDAP structure
See the example in section “2. Manual creation of an LDAP structure (based on Microsoft Active Directory)” on page 96 above.

Assigning Domain users to the MMB
The next step is to create/edit users who are to be granted access to the Management Blade. Novell iManager is used for this purpose (cf. figure 88). iManager can be found on the eDirectory Server at the URL https://127.0.0.1:8443/nps/. If configuration is to take place from another computer in the network, the IP address (127.0.0.1) must be replaced by that of the server.

Figure 88: Novell iManager login

Select the "Create User" item in the "Users" menu to create new users (cf. figure 89).

122

ServerView BX900 S1 Management Blade

User Management

Configuring an eDirectory Server

Figure 89: Creating a user

After the user information has been specified, the user must be assigned to a context. In this case the context "people" is selected (cf. figure 90).

Figure 90: Selecting the context

ServerView BX900 S1 Management Blade

123

they must be assigned to an appropriate group. 124 ServerView BX900 S1 Management Blade . Clicking on "Modify" causes the dialog for editing the user settings to be opened (cf. Figure 92: Storing the user To permit the newly created user to log in on the Management Blade.Configuring an eDirectory Server User Management Figure 91: User data The user is stored by clicking on "OK". figure 93 and figure 94).

User Management Configuring an eDirectory Server Figure 93: Editing user settings Figure 94: Group assignment The user must be included in an "AuthorizationRole" in order to guarantee that they can log in on the Management Blade. ServerView BX900 S1 Management Blade 125 . These AuthorizationRoles are contained in the department created using LDAPDeployer within the eDirectory Server's directory structure. figure 95 shows how an AuthorizationRole is selected in the "DeptX" department.

Configuring an eDirectory Server User Management Figure 95: Selecting the AuthorizationRole Figure 96: Accepting the settings 126 ServerView BX900 S1 Management Blade .

Special User Account: Special user who takes over communication between the MMB und LDAP-Server (e.3.g. and the time on the Management Blade must be synchronized with that on the eDirectory Server. LDAP Type: eDirectory 2. for the user specified under item 7 The IP settings and the DNS Server must also be adjusted to the network concerned.4 Settings on the Management Blade figure 97 shows an example of the settings required for communication with an eDirectory Server.User Management Configuring an eDirectory Server 6. LDAP Base DN: Assigned automatically 5. User LDAP Department: Department configured by LDAPDeployer 7.ou=people. Root Domain Name: Name of the domain 4.: cn=principal.dc=sbrd4) 8. 1. Special User Password: Password. User LDAP Base DN: ou in which the users are stored 6. Figure 97: Settings on the Management Blade ServerView BX900 S1 Management Blade 127 . LDAP Server IP: IP of the Domain Controller 3.

3.Configuring an eDirectory Server User Management 6.5 Logging in on the Management Blade as an LDAP user Figure 98: Logging in on the Management Blade as an LDAP user Figure 99: User is logged in 128 ServerView BX900 S1 Management Blade .

Abbreviations AC Alternating Current AD Active Directory ARP Address Resolution Protocol ASCII American Standard Code for Information Interchange ASR Automatic Server Restart BIOS Basic Input Output System BTU/h British Thermal Unit per hour CA Certification Authority CD-ROM Compact Disk-Read Only Memory CLI Command Line Interface CLP Command Line Protocol CMOS Complementary Metal Oxide Semiconductor CPU Central Processor Unit CSR Certificate Signing Request CSS Customer Self Service DC Direct Current DHCP Dynamic Host Configuration Protocol DIMM Dual-in-Line Memory Module DIP Dual In-Line Package ServerView BX900 S1 Management Blade 129 .

DNS Domain Name Server DST Daylight Saving Time DVD Digital Versatile Disk EEPROM Electrical Eraseable Programmable Read Only Memory EULA End User License Agreement EMP Emergency Management Port EPOW Early Power Off Warning FC Fibre Channel FRU Field Replaceable Unit GbE Gigabit Ethernet GUI Graphical User Interface GUID Globally Unique Identifier HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol Secure HW Hardware IBP Intelligent Blade Panel ICE Import Convert Export ICMP Internet Control Message Protocol ID Identifier IP Internet Protocol 130 ServerView BX900 S1 Management Blade .

Video.IPMB Intelligent Platform Management Bus IPMI Intelligent Platform Management Interface iRMC integrated Remote Management Controller ITS Invitation to Send KVM Keyboard. Mouse L2 Layer 2 (Data Link Layer) LAN Local Area Network LCD Liquid Crystal Display LDAP Lightweight Directory Access Protocol LDIF Lightweight Directory Interchange Format LED Light Emitting Diode MAC Media Access Control MB Megabyte MD5 Message Digest 5 MMB Management Blade MUX Multiplexer NDS Novell Directory Services NIC Network Interface Card NMI Non-Maskable Interrupt NTP Network Time Protocol ServerView BX900 S1 Management Blade 131 .

Adleman RTC Real Time Clock RX Receiver Cross SDR Sensor Data Records SDRAM Synchronous Dynamic Random Access Memory SEL System Event Log 132 ServerView BX900 S1 Management Blade . Shamir.OEM Original Equipment Manufacturer OCP OverCurrent Protection OVP Over Voltage Protection OS Operating System PCI Peripheral Component Interconnect PDA Prefailure Detection Analysis PROM Programmable Read Only Memory PSU Power Supply Unit PXE Preboot eXecution Environment PWOK Power OK RBS Role-Based Services REMCS Remote Emergency Monitoring and Control System ROM Read Only Memory RPM Rotations / Revolutions Per Minute RSA Rivest.

SHA Secure Hash Algorithm SMASH Systems Management Architecture for Server Hardware SNMP Simple Network Management Protocol SSH Secure Shell SSL Secure Socket Layer TCP/IP Transmission Control Protocol/Internet Protocol TFTP Trivial File Transfer Protocol TLS Transport Layer Security TPM Trusted Platform Module TX Transmitter Cross UART Universal Asynchronous Receiver Transmitter UI User Interface UID Unit Identification Light UPS Uninterruptible Power Supply URL Uniform Resource Locator USB Universal Serial Bus USM User-based Security Model UVP Under Voltage Protection VAC Volt Alternating Current VACM View-based Access Control Model ServerView BX900 S1 Management Blade 133 .

VIOM Virtual-I/O Manager VLAN Virtual Local Area Network WWN World Wide Name 134 ServerView BX900 S1 Management Blade .

ts.fujitsu. [1] PRIMERGY BX900 Basic Unit Operating Manual PRIMERGY BX Blade Server Systems LAN Switch Blade – User Interface Description User Guide ServerView Deployment Manager User Manual BIOS Setup Reference Manual ServerView Installation Manager User Guide ServerView Operations Manager User Guide PRIMERGY ServerView Suite ServerView Virtual-IO Manager User Guide [2] [3] [4] [5] [6] [7] ServerView BX900 S1 Management Blade 135 .Related Publications PRIMERGY manuals are available in PDF format on the ServerBooks DVD. The PDF files for the manuals can also be downloaded free of charge from the Internet. I You will find further useful information in the documentation for your operating system. The overview page showing the online documentation available in the Internet can be found via the URL: http://manuals.com. The ServerBooks DVD is part of the ServerStart Bundle delivered with each server system.

.

62 Programs supported 10 F Fail-over scenario 11 FC Switch Blade 60 R Rear Fan Units 62 Reboot Management Blade (Telnet) 42 ServerView BX900 S1 Management Blade 137 .Index A Account Management (Telnet) 44 Active Directory 95 Active Directory Authentication (Telnet) 35 Alerting 75 Asset Overview 64 Auto Configuration 10 Features ServerView management blade 9 Firmware Update 71 G GbE Switch Blade 58 H B Backup Configuration 59. 79 Power Supplies 62. 48 Power Management 66. 61 Backup/Restoration Management 69 Base Configuration Wizard 77 blade server concept 9 blade Server Management 9 Blue Screen (Telnet) 29 Hardware monitoring 10 I I2C Bus Management (Telnet) 37 L Language 76 Local Service Display 66 Logging 64 login Web GUI 45 Logout option 41 C Certificate Handling 72 Change Management Role To Slave (Telnet) CMOS Backup/Restoration (Telnet) 33 Command Line Interface (Telnet) 43 components 52 concept blade server 9 Connection Blade (Telnet) 25 Connection Blades 58 Console main menu (Telnet) 15 console mode entering (Telnet) 13 Console redirection 11 (Telnet) 40 Controller 9 42 M Main Menu 51 Management Agent Information (Telnet) 17 Management Agent (Telnet) 16 Management Blade (Telnet) 19 Management Blade Event Log (Telnet) Management Blades 53 Mezzanine-2 MUX Configuration 56 multiplexer 56 MUX 56 30 D Date Time 76 Dump Post Mortem 65 N Network Interface 73 NIC Information (Telnet) 24 notational conventions 8 39 E eDirectory 114 Emergency Management Port (Telnet) Event Log 64 Management Blade (Telnet) 30 Server Blade (Telnet) 31 Event Log (Telnet) 30 Event repository 10 Eventlog Filter 64 P Power Consumption (Telnet) 34 Power Consumption Mode 47.

95 User Management (Telnet) 27 user permission rights (Telnet) 27 user roles 27 user. 18 start page 46 Status Overview 52 Storage Blade (Telnet) 25 Storage Blades 57 33 Supported programs 10 System Information (Telnet) 20 System Information Dump 65 System Information Dump (Telnet) System Unit 52 System Unit. settings 73 42 T Target Group 8 Telnet interface 13 TFTP Update (Telnet) 41 U User Management 68. 61 S Server Blade (Telnet) 21 Server Blade CMOS Backup/Restoration (Telnet) Server Blade Control Information 21 Server Blade Event Log (Telnet) 31 Server Blade Information (Telnet) 22 Server Blade Memory (Telnet) 23 Server Blade NIC Information (Telnet) 24 Server Blade Temperature (Telnet) 23 Server Blade Voltage Table (Telnet) 23 Server Blade Watch Dog (Telnet) 24 Server Blades 55 ServerBlade CPU (Telnet) 22 ServerView Management Blade reduncancy 11 Set System Default (Telnet) 32 Settings 73 SNMP 74 SSL 10.Redundancy 11 Refresh 76 Restore Configuration 59. deleting (Telnet) 27 V VLAN information (Telnet) 36 W Watch Dog (Telnet) 24 Web user interface 45 138 ServerView BX900 S1 Management Blade .

Sign up to vote on this title
UsefulNot useful