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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Blades .1 4. . . . . . . . . . . . . . . . . . . . . . Rear Fan Units . . . . . . . . . . . . . . . . Dump Post Mortem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Certificate . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Log . . . . . . . . . . . . . . . . . . . . . .4. . . .6 3. . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . .10 3. . . . . . . . . . Local Users .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . .6. . . . . . . . . . . . . . . . . . . . . . . . . Asset Overview . . . . . . . . . . . . . . . . .1 4. . 42 System Information Dump . . . . . . . . . . User Session Information . . .5. . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 4. . . . . . . . . . . .5 4. . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 4. . . . . . . . . . . . . . . . . . . . . . . . . . .3 4.5 3. . .2 4. . . . . 43 Account Management . . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . .2 4. . . . . . . . . . . . . . Backup/Restoration Management . . . . . . . . . . .5 4. . . . . . . . . . . . . . . . . . . . . . . . . .9 3. . . . . . . . .5. . . . Server Blades . . . . . . . 41 Change Management Role To Slave . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Blades . . . . . . Power Supplies . . . . . . . . . . . . . . . . . . . . . . . Local Service Display . . . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 3. . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 4. . . . . . . . . . . . . . . . . . . 45 Login . . . . . . 42 Reboot Management Blade . . . . . . . . . . . . . .1. . . . . System Certificate . . . . . . . . . . . . . . . . . . . . . . . . .4 4. . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . Alerting . . . . .4 Management Blade Base Configuration Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Settings . . . . . . . . . . . . . . . . . . . . . .6 4. SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 4. . . . . . . . . Backup/Restoration Management – BIOS . . . Storage Blades . . . . . . . . . . . . . . . . . . User Management . . 40 TFTP Update . . . . . . . . . . . . . . . . . . . . . . . . . . .3 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Logout . . . . . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. .1 4. . . . . . . . . . . . . . . . . . 38 Emergency Management Port . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 4. . . . . . . . . . . . Global Users . . . . . . . . . . . . . . Certificate Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 4. . . . . . . . . . . . . . . . .4 4. . .4 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . .2 4. . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . .5 4.3. . . . . . . . . . . . . . . . . . . . . . . . . . 46 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 4. . . . . . . . . . . .3.2 4. . . . . . . . . . . . . . . . . . . .2 4. . .4. . . . .5. . . . . . . . . . . . . . .4. . . . . . . . .4 4. . . . . . . . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 3. . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Web User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 4 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 The Start Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Unit . .3. . . . . . . . . . . . . . . .6. 42 Command Line Interface . . . . . . . . . Backup/Restoration Management – iRMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Interface . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . Power Management . . . . .3 4. . . . . . . . . . . . . . . .1 4. .1 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 3.5. . . . .2 4. . . . . . System Information Dump . . . . . . . . . . .17 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . Firmware Update . . . . . . . . . .4 3. . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . Logging . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. .4. . . . . . . . . . . . . . . .4 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . .5. . . . . . New Local User Account . . . . . . . . . . . . . . . . . . . . . . . . . . .2 4. . .6 4. . . . . . . . . . . Information .6. . . . . . . . . . . . System (Status Overview) . . . . . . . . .1 4. . . . . . . . . . . . . . Date Time . . . . . . . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . .7 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Console Redirection . . . . . . . . . . . . . . . . . . . .

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

.

see section “Features of the ServerView Management Blade” on page 9. For a complete feature list. redundant ServerView management blades: an integrated management solution for complete remote administration of the blade server system. 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 .1 Introduction The PRIMERGY BX Blade Server Systems accommodate two hot-swapable.

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

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

SEL (System Event Log). It allows to configure settings of the switch blades. 10 ServerView BX900 S1 Management Blade . when performing hardware monitoring tasks for the server blades. An IPMB interface is provided to support the user. or the IP gateway address.Blade Server Management BX Blade Server System Overview Supported programs The ServerView management blade is compliant with IPMI (Internet Protocol Multicast Iniative) 1. and SDR (Sensor Data Records). i. 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. SSL (Secure Socket Layer) The Manager Blade provides SSL for network data privacy for Telnet as well as for HTTP connections. This reduces the risk if system configuration data have been corrupted or lost. Communication with the server blades The ServerView management blade communicates with the server blades via an I2C bus. e. Communication with the switch blades To enable communication with the switch blades. Auto configuration The management function auto configuration is used to back up system parameters to a ROM. the IP mask. It supports schemes like FRU (Field Replaceable Units). if they have been opened. providing a 2 x 32 MB SDRAM. a CLI interface is provided. It also allows the configuration of a watchdog timer. such as the IP address. It also provides the possibility to restore these paramters if required. the ServerView management blade is equipped with an event repository.0. 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. which is located on the management blade.

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

.

firstly a number of messages concerning the system appears on the screen. The menu is described in this chapter. After approximately five seconds a welcome screen is displayed. 3. the blade server system is started.g. using the Telnet protocol. the HyperTerminal option is called up on the PC.3 Telnet Interface Within the blade server system a console menu is provided for server management. The settings are then as follows: Host IP address Telnet port Connected protocol Terminal type 192. the Telnet client is called up. e.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. After the connection has been established. and the login procedure is performed using the management blade IP address. IP address configuration or hardware status monitoring. When using the serial port.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. A number of configuration activities can be performed via this menu. An RX/TX signal will then be exchanged via this cable. 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.224. In this case. ServerView BX900 S1 Management Blade 13 . For this purpose a RS232 cable (null modem cable) is used.168.

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

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

3.5 on page 25) 6.3.12 on page 34) 13.3 Management Agent The following items are provided in the Management Agent sub-menu for server management: 1.Management Agent Telnet Interface 3.10 on page 32) 11. Server Blade (see 3.17 on page 38) 16 ServerView BX900 S1 Management Blade .3 on page 20) 4. Storage Blade (see 3.Management Blade Configuration Backup/Restore (see 3. Event Log (see 3.Management Blade Base Configuration Backup/Restore (see 3. Connection Blade (see 3.3.3.Server Blade CMOS Backup/Restore (see 3.3.3.VLAN Information (see 3.3.3.3. Management Agent Information (see 3. Management Blade (see 3.3.14 on page 36) 15.4 on page 21) 5.3.LDAP Authentication (see 3.2 on page 19) 3.Set System Default (see 3.Power Consumption (see 3. Blue Screen (see 3.3.3. System Information (see 3.8 on page 29) 9.11 on page 33) 12.6 on page 25) 7.I2C Bus Management (see 3.15 on page 37) 16.1 on page 17) 2.3.7 on page 27) 8.13 on page 35) 14. User Management (see 3.3.3.9 on page 30) 10.16 on page 37) 17.3.

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

including Telnet port assignment and Telnet enabling/disabling. Configuration of the management LAN interface of the MMB. Setting Mode allows you to specify which duplex mode should be active after the next reset. which is selected from a time zone table. 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. Configuration of the HTTP settings. 18 ServerView BX900 S1 Management Blade . 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 time zone for the management blade. selecting an SMNP community string and a destination from the SNMP trap table. SMTP relay server and mail user account. SMTP sender. – Sync Always The management blade always syncs the time from NTP server. Configuration of the time-out value for login to the console menu. Configuration of the SSH settings. Configuration of the SNMP settings. 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). Configuration of the Telnet server settings. You can enable or disable the NTP service.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 DNS server address and enabling/disabling DNS support. including port number assignment. including SMTP enabling/ disabling. the management blade syncs the time from NTP server. Configuration of the SMTP settings for mail sending. Configuration of date and time for the management blade. including SNMP enabling/disabling. Configuration of the NTP (network time protocol) service. no matter whether the NTP server time is behind or ahead of management blade. HTTP protocol enabling/disabling and HTTP SSL security control. Execution Mode displays the current duplex mode.

3. Current voltage of the MMB. 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. A number of parameters relating to the management blades is displayed to the user.Telnet Interface Management Agent 3. Standard voltage of the MMB.2 Management Blade Within the blade server management system there are two management blades. Product name of the management blade. The other one is in standby mode to ensure the availability of the system. Name of the manufacturer of the management blade. Hardware version of the management blade. Date of manufacture for the management blade. Serial number of the management blade. Firmware version of the management blade. Maximum voltage of the MMB. ServerView BX900 S1 Management Blade 19 . A message will be displayed if this status is disturbed. Health status of the management blade. One of them is active as the master of the server management system. Physical address (MAC address) of the service LAN interface of the MMB. Name of the management blade model. Minimum voltage of the MMB. Status of the voltage supply of the MMB. Physical address (MAC address) of the management LAN interface of the MMB.

warning level. speed threshold and failure reaction. such as power supply. KVM (= keyboard/video/mouse). and SNMP community.Management Agent Telnet Interface 3. Displays information on the number and status of the system fans. The function is only working for VIOM. Displays chassis UPS (uninterruptable power supply) information. If set to automatic. temperature. Displays information on the power supply units. Displays information on the system chassis. including current value.3. Displays information on the system temperature. as well as the status of all system components. supporting the fan life time monitor. including parameters like nominal speed. Displays the status of the system control: on. type. connect port. including the chassis serial number and if there has been any intrusion into the inside of the chassis. 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 . power supply groups and temperature sensors. the inventory retrieval is automatically performed for inserted server blades or when the basic unit is powered on. fans. excepting CPU blades and switch blades. the automatic inventory retrieval is not done. 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.3 System Information The System Information option provides information on all components of the blade server management system. vendor. critical level. and the slave takes over the role of the master. current speed. including UPS number. If set to manual. Turns on or turns off all server blades. off. sensor status and critical temperature reaction. In dual MMB mode the roles are switched when the LAN connection to the master fails. or blinking. IP address. A fan test is also provided.

The user can set up a power on/off schedule for server blade. Configuration of the LED control at the front of the blade server: blinking or off. Indicates the status of the Server Memory Dump Flag (normal or off). i. Shows the current mode of Consumption Control (if Consumption Mode is enabled). memory modules. Host name of the server blade. these are closed immediately). For details.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 .Telnet Interface Management Agent 3. 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.4. voltage. Is overwritten with the host name assigned in the operating system when ServerView agents are used. the "forced shutdown" is initiated after n minutes. The menu for this option looks like this: Figure 7: Server Blade menu 3. If the "proper" shutdown of the server blade fails. information on CPUs.e.3. please refer to the VIOM specification.4 Server Blade The Server Blade option provides general information on the server blades. temperature. CMOS configuration and watchdog timers.

22 ServerView BX900 S1 Management Blade . if the VIOM was enabled. Displays the server blade manufacturer. the blade can be started up "without" the BIOS. Displays how many CPU sockets are available on the server blade. Displays the server blade product name.3 Server Blade CPU This option displays some information on the server blade CPU parameters.4. Globally Unique Identifier which is stored in the BIOS. Displays server blade memory information. However. Displays the server blade serial number (systems). Displays the OS platform currently running on the server blade.3. CD/DVD) and flashes it. Displays the CPU ID. Displays the version of the OS currently running on the server blade.4. Displays the CPU frequency. iRMC Address Configuration 3. the Active GUID differs from the Manufacture GUID. Displays the server blade iRMC firmware version. Sets up the LAN connection of the iRMC. Displays whether a Mezzanine card is installed. Displays the server blade model name. Displays the server blade production date. Displays the server blade serial number (motherboard). USB stick.2 Server Blade Information This option displays some information on the server blade parameters. The following parameters are included: Parameter CPU Type CPU Frequency CPU ID Description Displays the CPU type. 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.3. It then searches autonomously for a suitable BIOS on the connected media (floppy. Normally the same value as in the Server Blade Manufacture GUID (see next entry). Server Blade Manufacture GUID 3. Displays the server blade product version. Displays the server blade hardware version.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 BIOS version. After the option has been set.

4.3. 3. Displays the CPU socket designation.3. The following parameters are displayed: Parameter Server Voltage Designation Server Voltage Status Description Displays the voltage designation for the server blade. the error reset record and the error count start time. 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 maximum voltage value for the server blade.4 Server Blade Memory This option provides information on the server blade memory.Telnet Interface Management Agent Parameter CPU Status Description Displays the CPU status. 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. 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. as well as on the error count. ServerView BX900 S1 Management Blade 23 . Displays the status of each memory module. Displays information on the CPU manufacturer. 3. 3.6 Server Blade Temperature This option provides information on the server temperature. Displays the CPU clock. Displays the nominal voltage value for the server blade.3. Displays the voltage status for the server blade. 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. together with memory type and error information.4.4.5 Server Blade Voltage Table This option provides information on the server voltage. Displays the current voltage value for the server blade.

It will be reset by the BIOS in periods configured within the POST code.Management Agent Telnet Interface Parameter Server Temperature Sensor Status Description Displays the status of the temperature sensor. a time-out routine will be started. Server Temperature Lower Warning Level This parameter can be set to configure the lower warning level of the temperature sensor for 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.3. Parameter Server Blade NIC IP Table Description Address table of the server blade's Network Interface Card. 3. When the time-out is reached. 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. 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.3.7 Server Blade NIC Information This option displays the IP and MAC address of the server blade.4.8 Server Blade Watch Dog This option is used to configure the watchdog timers for the server blade. Server Blade MAC Address Table Table with all MAC addresses of the server blade. Server Temperature Upper Critical Level This parameter can be set to configure the upper critical level of the temperature sensor for the server blade. Server Blade Boot Watchdog 24 ServerView BX900 S1 Management Blade . a time-out routine will be started. A watchdog timer agent that resets the timer must be implemented in the operation system.4. When the time-out is reached. Displays the current temperature value for the server blade. This timer is used to monitor the server blade POST. 3.

Displays the storage blade manufacture vendor. Displays the storage blade product version. GbE Switch Blade 2.3.Telnet Interface Management Agent 3. GbE IBP Blade The menu for all these types is the same and looks like this: ServerView BX900 S1 Management Blade 25 . 3. PRIMERGY SX940 S1).g.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 hardware version. Displays the storage blade product name. Currently supported are the following types of connection blades: 1. Displays the storage blade serial number (motherboard). Displays the storage blade manufacture date. FC Switch Blade 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 model name.3. Displays the storage blade serial number (systems).

Displays information on the manufacturer. Applies for SB11 connection blades. MMB will be polling switch settings every 5 minutes if this function is enabled. This status can be retrieved by the management blade via a CLI command. Displays the firmware version. Two SB11s which are operated in a fabric (horizontally adjacent to each other) can be interconnected to form "one" switch. Displays the hardware version. Displays the serial number.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. The mode enabled is displayed here. Sets the LED off or blinking. The URL at which the MMB can be reached using a Web browser. GbE connection blades can run in two different modes – Switch and IBP. The name of the connection blade (can be assigned by the user). Possible state: Master or Member. Displays the manufacturing date. Enables/disables the switch period polling function. Applies for SB11 connection blades. A common management interface then exists for the connected connection blades. 26 ServerView BX900 S1 Management Blade . Starts rebooting the connection blade. Displays the model name. Displays the product name. These can be interconnected to form a stack.

CLI etc. 3. add and delete users. CLI etc. Step 1 Select the user to be deleted. connection blades. The following four user types (roles) with different permission rights are possible: 1. 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. 2. in this example the user Tom – type 2: ServerView BX900 S1 Management Blade 27 . because no explicit entry is provided for this. 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. update.3.Telnet Interface Management Agent 3. 4. CLI etc.) User This role allows the user – to use the functions at the usual user interfaces (Web UI. and delete a user account – to configure system settings related to the MMB. We will therefore use an example to describe how you must proceed in this case.) Example: Deleting a user The methods for creating a new user or changing a user name or rights are intuitive and present no problems. The situation is somewhat different when an existing user is to be deleted.7 User Management The User Management option is used to change.

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 .

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

The major events that have been logged on the management blade.9. The minor events that have been logged on the management blade.1 Management Blade Event Log This sub-option is used to display the events that have been logged on the management blade event log. The informational 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. This parameter is used to clear all events from the management blade event log. The critical events that have been logged on the 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.3.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.Management Agent Telnet Interface 3. 30 ServerView BX900 S1 Management Blade .

Enable Starts the backup to the USB medium. no event log entries are written any longer.9. This parameter is used to clear all events from a server blade event log.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.3. The critical events that have been logged on the server blade. Parameter USB device selection Description Selects the USB medium (all the devices connected to the MMB are displayed here). a default name is used.9. After a server blade has been selected. Filename (empty default name) Name of the file which will be written to USB – if nothing is entered. When the event log repository is full. 3. new event log entries replace the old ones beginning with the first event log entry.3.3 Server Blade Power On/Off Event Log Enable This option is used to specify.5 Backup All Event Log to USB Device This option is used to save the MMB’s event log to a USB medium.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. The minor events that have been logged on the server blade.9.3. The informational events that have been logged on the server blade. The major events that have been logged on the server blade. 3. ServerView BX900 S1 Management Blade 31 . Parameter enable disable Description When the event log repository is full.Telnet Interface Management Agent 3.3. 3.9. whether power on/off events for the server blades should be listed in the event log. 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.

V Please note that all configured values are lost and the management blade has to be configured newly after using this option.Management Agent Telnet Interface 3.3. 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. The password for the user root is set to the default (“root“).10 Set System Default The Set System Default option is used to restore the default values. Set Username/Password Default All configured user names with the exception of root are deleted. Set CMOS Backup Default All switch blade configuration backups and all server blade BIOS backups are deleted. 32 ServerView BX900 S1 Management Blade .

BIOS version and MAC address have been verified. The server blade must be powered on before backup/restore processing.Telnet Interface Management Agent 3. force-restore The backup file is restored without verification. the backup file of the selected server blade is restored. After selecting the server blade whose BIOS is to be backed up or whose backup file is to be restored. If the backup is successful. the backup file will be displayed in the CMOS backup file table.11 Server Blade CMOS Backup/Restore This option is used to backup and restore server blade BIOS parameters. smart-restore After the slot id.3. 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 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. Displays the CMOS ID with MAC address Displays date and time of the backup file generation. Displays the CMOS ID with BIOS version. ServerView BX900 S1 Management Blade 33 .

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 and the voltage range of the power supply units. Shows the current power consumption of the connection blade. DC power consumption of each connection blade. Displays the max. Includes one management blade and 6 fan modules. Current power consumption of the whole blade server system (including server blades). Difference between Power Budget Control Threshold and current Total Consumption. Displays the max.12 Power Consumption This option is used to control the power consumption. Settings for power control (redundancy. Storage Blade Power Consumption Table Displays the max. Power consumption of the base system. 34 ServerView BX900 S1 Management Blade .) – observe submenus. DC power of the active power supply. etc. Shows the current power consumption of the storage blade. limit values. DC power consumption of each server blade.Management Agent Telnet Interface 3.3. Displays the max. DC power consumption of each storage blade. dynamic.

OpenLDAP. "Department" of the user in the LDAP directory. Needed to set up a connection to the LDAP server. Password for setting up a connection to the LDAP server. Distinguished Name.3. Selects the LDAP type (Windows Active Directory. IP addresses of the primary and. Domain name which was assigned by the LDAP server. 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. Selects whether LDAP is to use a secure SSL connection.13 Active Directory Authentication Use Active Directory to login to the MMB through the Web-based or a CLI interface.Telnet Interface Management Agent 3. ServerView BX900 S1 Management Blade 35 . eDirectory). a unique object name in LDAP directories. if present. Name of the domain in which the user logs in.The login syntax is: username@domain (where username is an ASCII string of 1-256 bytes). secondary LDAP server.

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.3.14 VLAN Information MMB supports up to 10 VLAN IDs. 36 ServerView BX900 S1 Management Blade . Sets the VLAN network mask. The integer 2 to 4095 are supported. Sets the VLAN IP. Enables/Disables the VLAN function.Management Agent Telnet Interface 3.

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

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

Management Blade Image File Name Setting of a file and path name for the management blade image. 3. 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.7 Logout This option is provided to perform a logout from the Telnet console menu. I For further information on updating BX components please refer to the Operating Manual of your BX system. This option is used to enable/disable the update and to display the TFTP status. After setting the parameter to enable. The default value for this parameter is disable. This option is used to enable/disable the update and to display the TFTP status.Telnet Interface TFTP Update 3. Upgrading of the management blade firmware. ServerView BX900 S1 Management Blade 41 . the TFTP server must be started. The update will then be performed as the system powers up. Upgrading of the Server Blade iRMC firmware.6 TFTP Update The TFTP Update option is used to perform an update of the management blade firmware. Update Server Blade BIOS Table Update Server Blade iRMC Table Upgrading of the Server Blade BIOS. and the management blade must be rebooted.

all modules’ FRU data and event logs.g. MAC address and firmware version of the switch blades. fan speeds. Displays the management blade event log. I This menu item appears only if the system is not redundant in design. 3. iRMC firmware version.g. 3.8 Change Management Role To Slave This item is used to change the role of the management blade. Use in case of problem.Change Management Role To Slave Telnet Interface 3. OS type and OS version.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. I This menu item appears only if the system is redundant in design. BIOS version. The reboot is executed immediately. 42 ServerView BX900 S1 Management Blade . status. voltages. Displays a consecutive list of information about the server blades. to get all necessary information on customer site to analyze the problem in the development. e. status. 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.9 Reboot Management Blade This item is used to perform a reboot of the system. IP address. e. Displays the server blade event log. Provides information about temperatures.

operating system state.11 Command Line Interface This option is used to get chassis information or to manage series of servers. 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. ServerView BX900 S1 Management Blade 43 .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. server system topology or access method. 3. I Type exit to quit the SMASH CLI submenu.

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

You log into this interface via the web browser. e. ServerView BX900 S1 Management Blade 45 .40. 4. http://10.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.4 Web User Interface On the web server an interactive and user-friendly web user interface. is provided for server management. known as web console.g. It does not depend on any special operating system for a platform. the message No Access Right! will appear. I If you enter an incorrect password more than three times.36.

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

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

if you have selected a server blade. The other fields have the same meaning as described above for the status frame. I If you have configured a "Consumption Limitation" (Power Consumption Options → Consumption Mode → Consumption Limitation) using the Power Management → Configuration menu item. The maximum possible power consumption can vary dynamically if the Dynamic Mode option was enabled on the Power Management → Configuration page. 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. I The gray bar at the bottom of the status frame normally only contains the name of the component selected on the right. ⏐ You use the Locate button to switch the blade server’s and MMB’s ID LED on (blue) or off (gray). 48 ServerView BX900 S1 Management Blade . The 3rd line provides information about the secondary output power which is still available for the blades up to the specified upper limit. However. please refer to chapter “Power Management” on page 79. which is dynamic. Web User Interface This icon is optional and is displayed only if a USB stick is connected to the Master Management Blade. System Unit Details This button enables you to collapse the status frame. You use the Video Redirection button to open a virtual console for the blade.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. 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). 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.

Web User Interface 3. The individual blades are clickable. The individual components are clickable. a tooltip with the relevant name is displayed. the associated information is displayed in the main frame. I When the power supply is switched off (via Information / Operation – Power Management – Control – – Rear View Current System Power). ServerView BX900 S1 Management Blade 49 . or ). i. a tooltip with the relevant name is displayed (see the picture below). I Hardware components which are not integrated into the BX900 base unit are not displayed in the navigation frame. i. When you point the cursor to a component. 5. after they have been clicked on.e. the associated information is displayed in the main frame.e. 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). This power-off status is also indicated by the LED at the bottom right glowing orange instead of green. The individual items are clickable. no blades are displayed. It contains information about the option/component which was selected via one of the two views or the navigation menu. Displays the BX900 components at the rear (power supplies. the associated information is displayed in the main frame. Main frame (4) The main frame supplies information about the BX900 base unit. 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. fan. after they have been clicked on. i. either. the unit is totally black. MMB.e. after they have been clicked on. Bottom frame (5) The bottom frame only contains a copyright notice at the bottom left. i. When you point the cursor to a blade. etc. Each of the three views of the navigation tree is collapsible ( 4.e.).

and in the main menu. which is a general indicator in the status frame for an error in the system. 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).The Start Page Web User Interface Error handling Errors and warnings are displayed simultaneously in the status frame. in each case the same error is indicated. This enables you to see precisely in which component the error has occurred (in our example in "Server Blade 8"). In other words. 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 icon. 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. the navigation frame and the main frame. twice in the navigation frame (in the Front View and in the navigation tree).

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

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

It is essential that there is at least one management blade installed to handle server management.3. Management LAN MAC Address Physical address (MAC address) of the management LAN interface of the MMB. If this function is checked. Maximum Voltage Value Displays the maximum voltage value of the management blade.Web User Interface Components Test at every startup Sets the fan behavior when the system powers on. There are up to two management blades in the system. 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. Model Name Displays the management blade model name.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. The management blade that is the first to have its heartbeat detected will be the master. Product Name Displays the management blade product name. Service LAN MAC Address Physical address (MAC address) of the service LAN interface of the MMB. Voltage Status Displays the voltage status of the management blade. Possible reactions: "continue" or "shutdown-and-poweroff". Hardware Version Displays the management blade hardware version. all the fans present will rotate at full speed for a while. 4. Service LAN IP Address IP address of the service LAN interface of the MMB. Both management blades will then start to boot up at the same time. Status Displays the current status of the management blade. Manufacturer Displays the management blade manufacturing information. and the other one is there to ensure redundancy. ServerView BX900 S1 Management Blade 53 . One of these plays the master role for server management. Serial Number Displays the management blade serial number. Production Date Displays the production date of the management blade. Firmware Version Displays the management blade management firmware version. Management LAN IP Address IP address of the management LAN interface of the MMB. MAC Address Displays the MAC address of the management blade network controller. one of them will be selected for the master role in the boot phase. If there are two management blades (recommended). 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.

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

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

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

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

Product Name Displays the connection blade’s product name. Firmware Version Displays the connection blade's management firmware version. 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. The mode can also be set in the Web interface of the selected GbE connection blade. 2. Serial Number Displays the connection blade’s serial number. Changing the rack name (via the menu item System Unit in the Web UI) may overwrite the here defined name. The user assigned name may not be longer than 31 characters and may not begin with an underscore ("_") or a digit. Management Port MAC Address Displays the MAC address of the connection blade's service port.3. 4. The connection blade takes the assigned name and uses it (if it was not overwritten) for the following system settings: 1. For connection blades with product name "PY CB Eth Switch/IBP 10Gb 18/8" the command reset has to be used. Connection Blade CLI Prompt Name Port Naming Host name DHCP Client Identifier 58 ServerView BX900 S1 Management Blade . Configuration User Assigned Name Enter the connection blade's user assigned name. Firmware Mode Displays the firmware mode (IBP or Switch). Administrative URL URL address to link to the connection blade's web homepage. 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). 3. Hardware Version Displays the connection blade’s board version. Model Name Displays the connection blade’s model name.6 Connection Blades GbE Connection Blade Information Manufacturer Displays the connection blade's production information.Components Web User Interface 4. 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").

If the setting "Login User Name/Password" or "Enable Polling Password" is invalid for the connection blade. USB or Local File). Memory/USB Backup File You can change the name of the file containing the backed-up data here by clicking the New Name button. Reset Configuration Settings to default Resets the configuration settings listed below to their default values. the status is displayed here. The MMB will also disable the period polling function if it is enabled. Polling Settings Enable Period Polling Enables/disables the connection blade's period polling function. 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. Login Password Enter the login password for the polling function. This is necessary as the parameters can also be changed via the connection blade's own management functions. Memory/USB Backup Status After you have clicked the Backup button. IP Address / Subnet Mask / Gateway Address Displays the connection blade's management IP address / subnet mask / gateway address. USB or Local File). Enable DHCP Sets the IP mode (DHCP or NO-DHCP) for the management IP settings of the connection blade.Web User Interface Components The current status of the parameters is queried using the Refresh button. Enable Polling Password Enter the enable password for the polling function. 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 . A new file name consisting of an identification tag and the current date is then generated. 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. you can click the Refresh Status button to return to the default status Not Started. Current Value The IP address / subnet mask / gateway address [Current Value] is the current connection blade management IP address / subnet mask / gateway address. The MMB will poll the connection blade's settings every 5 minutes if this function is enabled. the MMB will issue the event log. After the backup has been completed. this means that the parameter has not been changed by the connection blade up to this point in time. If no change is displayed after the button has been pressed. 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"). Management Port Settings Displays the connection blade's network setting information. Login User Name Enter the login user name for the polling function.

Date Manufactured Displays the connection blade's production date. Connection Blade CLI Prompt Name 2. Afterwards the blade will reboot automatically. 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). FC Connection Blade Information Manufacturer Displays connection blade's production information. the status is displayed here. Native or Interop). WWN Address Displays the WWN address for FC connection blade. Administrative URL URL address to link to the connection blade's web homepage. View Configuration Displays the current interface data between the MMB and the connection blade. Product Name Displays the connection blade’s product name. Product Number Displays the connection blade’s product number. The mode can also be set in the Web interface of the selected FC connection blade. Host name 60 ServerView BX900 S1 Management Blade . Serial Number Displays the connection blade’s serial number. After restoration has been completed. Restoration Status After you have clicked the Restore button. Configuration User Assigned Name Enter the connection blade's user assigned name.Components Web User Interface Local Backup Files Offers you the option of searching for particular versions which have been backed up in local files. Power Management Power Setting The user can reset the blade after selecting the power action and clicking the Apply button. you can click the Refresh Status button to return to the default status Not Started. Hardware Version Displays the connection blade’s board version. Port Naming 3. The connection blade takes the assigned name and uses it (if it was not overwritten) for the following system settings: 1. 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. Management Port MAC Address Displays the MAC address of the connection blade's service port. Firmware Mode Displays the firmware mode (Access Gateway. Firmware Version Displays the connection blade's management firmware version.

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

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

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

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

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

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

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

4. Password Configures the password for the user account.Operation Web User Interface 4. Possible user roles are: Administrator – OEM – Operator – User. 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.5. 68 ServerView BX900 S1 Management Blade . Delete Deletes a user account.2 New Local User Account Configure User Account Enabled Checkbox for setting the account status (enabled/disabled). Permission Displays the user permission rights.5. 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. User Shell Permits the user to access the remote manager (CLI) or Server Management CLP. configure permission of server blades.3.3 User Management The User Management enables administrators having the appropriate privileges to configure local user accounts. OEM The user has full privileges for access system but is not allowed to configure a user account.1 Local Users Local User Account Enabled Displays the status of account(s) (enabled or disabled) Name Displays the user name. The administrators can configure the user account by clicking the user name hyperlink. Operator The user can configure I/O modules. User The user has read permission. Name Configures the user name. 4. Permissions Administrator The user has full privileges to access the system. Confirm Password Field for double-checking the password.3.5.

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

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. Restore Permits the specified BIOS parameters to be restored to one or more server blades. 70 ServerView BX900 S1 Management Blade . it is necessary that the voltage status of the BX900 system unit should be at least "auxiliary". the status is displayed here. Memory/USB Backup Status After you have clicked the Backup button. A new file name consisting of an identification tag and the current date is then generated. Memory/USB Backup Status After you have clicked the Backup button.4. 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). 4. you can click the Refresh Status button to return to the default status Not Started. the status display of the MMB glows green. Restore Action Permits the restoration destination to be specified and starts restoration. Restore Loads the iRMC settings from source media and modifies the settings to restore selected parameters to selected blades.2 Backup/Restoration Management – iRMC Backup Selects available server blades to load the iRMC settings. 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. Memory/USB Backup File You can change the name of the file containing the backed-up data here by clicking the New Name button. USB or Local File). A new file name consisting of an identification tag and the current date is then generated. and backs up the iRMC settings using the selected parameters. Backup Action Backup Media Here you select the medium on which the access and LAN configuration data is to be backed up (Memory. Restoration Parameter Set Selects restoration parameters by groups or detail items.5. To permit successful backup. After the backup has been completed. 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.e. you can click the Refresh Status button to return to the default status Not Started. the status is displayed here. i. After the backup has been completed. MMB memory).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.

e. This also ensures that all service processors of the server blades have identical settings. ">" moves selected blades to the upgrade window. "<<" removes all available blades from the upgrading window. 4.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. "<" removes selected blades from the upgrading window.5. To permit successful restoration. 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. 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. ">>" moves all available blades to the upgrade window. i. TFTP Update Enable Enables/disables the TFTP update. Clicking the "Apply" button submits the TFTP update. TFTP Boot Image File Name To set the management blade image file name.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. the status display of the MMB glows green. TFTP Boot Image File Name To set the server blade image file name. it is necessary that the voltage status of the BX900 system unit should be at least "auxiliary". ServerView BX900 S1 Management Blade 71 . 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).

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

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

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

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

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

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

Settings Web User Interface 78 ServerView BX900 S1 Management Blade .

5 Power Management The power consumption of a BX900 S1 depends on the number of PSUs which are equipped in the system unit. 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). as can be seen on the Power Management → Configuration page. 2 fans are also used (see figure). In addition to these 4 PSUs. The example below is based on a system unit with 4 activated PSUs. Figure 38: System unit with 4 PSUs and 2 fans ServerView BX900 S1 Management Blade 79 .

Information on the type and power consumption can be found on the sticker on the underside of the PSU (see figure).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). 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. 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 reason is that a fan can also be mounted in a PSU slot. 80 ServerView BX900 S1 Management Blade .

Power Management Power Consumption display 5. 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). 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).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. In the case of this maximum performance. The 3rd line provides information about the secondary output power which is still available for the blades up to the specified upper limit. the PSUs draw 19200W from the supply network. all of which are activated (available status). which is dynamic. 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. This value is changed by the system if Dynamic Mode is set. ServerView BX900 S1 Management Blade 81 .

Monitoring tab 2.2. 82 ServerView BX900 S1 Management Blade .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. See also figure 61 on page 92 and figure 62 on page 93 below.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. Configuration tab 5. Various settings can also be made in the "Power History Options" box. Control tab 3.

the server blades assume the status which is set in the iRMC (see figure) after the system unit has been powered on. 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. 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". a hard power-off is enforced for the server blade. If a hard power-off is selected for the unit or the Force Power-Off has occurred. ServerView BX900 S1 Management Blade 83 . 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".Power Management Control via tabs 5.2.2 Control tab The Control tab is used to control how the system unit and server blades are powered on and off.

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

the Apply buttons of the following boxes are shaded dark gray/enabled (can be used) or shaded light gray/disabled (cannot be used).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 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 . "Minimum Power" or "Best Performance" can be enabled as Operation Mode: Figure 49: Operation modes When "Minimum Power" or "Best Performance" is selected. the Apply button of the box is shaded dark gray (enabled) so that "disabled".Control via tabs Power Management Re a) in figure 48 (Consumption Control) If "Consumption Control" has been selected as the Consumption Mode.

2.Power Management Control via tabs Re b) in figure 48 (Consumption Limitation) If "Consumption Limitation" is selected. Best practice: 1. server blades which are still powered off will not be allowed to power on. the system shuts down the server blades in descending order from 18. but only as many as required to ensure that the limit is fallen below. 16. 17. the system shuts down (starting with row 1) as many as required to ensure that the limit is fallen below. all server blades which are expected to be used during operation must be powered 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. If server blades are entered in the right-hand box. The Consumption Limitation function must disabled prior to the power-on procedure of additional blades.. etc. Consumption Limitation should be activated when the system is up and running and constraints occur that require power consumption reduction activities. Before Consumption Limitation is activated. Only server blades (slots) which are already powered on and therefore known to the Consumption Limitation function can be powered on/off. 3. Figure 53: Consumption Limitation: shutdown I If Consumption Limitation is activated. ServerView BX900 S1 Management Blade 87 .

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

3. All other PSUs are on standby. and PSU-4 and PSU-5 remain on standby. PSU-1 is active and PSU-6 is on active standby. PSU-4 and PSU-5 remain on standby. All other PSUs are on standby.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. and so on. Example 3: Dynamic Mode and Redundancy 5+1 In the case of minimal power consumption. ServerView BX900 S1 Management Blade 89 . If more power is required. PSU-1 is active and PSU-6 is on active standby. Dynamic Mode switches PSU-3 to active. Dynamic Mode switches PSU-2 to active. If more power is required. Example 1: Dynamic Mode and Redundancy 3+3 (= Full Redundancy) In the case of minimal power consumption. If more power is required.2.Power Management Control via tabs 5. PSU-3. 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)". PSU-3 and PSU-4 remain on standby (see figure). Dynamic Mode switches PSU-2 to active and PSU-5 to active standby.

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

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). Display for "Threshold Definition = Absolute": in watt: Figure 59: Threshold Definition = Absolute ServerView BX900 S1 Management Blade 91 .

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

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

.

6 User Management There are three interfaces to User Management: 1. OpenLDAP (for Linux systems) 3.1 Configuring an Active Directory Server 1. in the example Windows Server 2003) is installed on any server. Active Directory (for Windows systems) 2. After installation has taken place. eDirectory (for Windows and Linux systems) 6. Installing a Windows Server First a Windows Server Operation System (Microsoft Windows Server 2003 or 2008. 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 .

etc.Configuring an Active Directory Server User Management 2. In addition. figure 64 on page 96). You must ensure the names of the OUs and groups are spelt correctly. otherwise correct operation cannot be guaranteed. 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 . 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.). Declarations. this means that they must have the names described in the section “Example of an LDAP structure” on page 96 (SVS. the OU SVS must be located on the first level below the domain (cf. you must set up a particular structure consisting of so-called Organizational Units (OUs) and Groups and assign the Groups to OUs. The groups contained in this must be derived from the path Domain/SVS/Declarations/AuthorizationRoles. Here only the OU AuthorizationRoles which must be created within a department need be borne in mind. How many departments there are and what they are called is determined by the administrator ("QA2" in the example). A sample configuration is described here. Specifically.

it must be modified (cf. figure 67 on page 98). ServerView BX900 S1 Management Blade 97 . If it already exists. groups must be created within the OUs (cf. The OUs must be configured in accordance with the schema shown above. The group name (pre-Windows 2000) is a unique name. The group scope "Global" and the group type "Distribution" must be selected here. figure 66 on page 98).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. Figure 65: Creating an organizational unit As described above.

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

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

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

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

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

Both of these values are required for further configuration activities. 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.dc=local" and the root DN "cn=Administrator" which were assigned during installation can be recognized. Among other things. 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.2 Configuring an openLDAP Server 1.dc=qa2. the domain "qa2.User Management Configuring an openLDAP Server 6.local .

Figure 74: DHCP Server 104 ServerView BX900 S1 Management Blade . This installation can be performed later or while the overall system is being installed.Configuring an openLDAP Server User Management 2. 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 .

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. Manual creation of an LDAP structure (based on Microsoft Active Directory)” on page 96 above.

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. Figure 79: User management 108 ServerView BX900 S1 Management Blade . The easiest way to do this is to use Yast's user management (cf. figure 79).

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

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

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

Special User Account: Special user who takes over communication between the MMB and LDAP Server (e. LDAP Type: OpenLDAP 2. and the time on the management blade must be synchronized with that on the AD Server.g. Settings on the Management Blade figure 83 shows an example of the settings required for communication with an openLDAP Server. LDAP Server IP: IP of the Domain Controller 3. User LDAP Base DN: ou in which the users are stored 6. 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 Department: Department configured by LDAPDeployer 7. Root Domain Name: Name of the domain 4. Figure 83: LDAP settings on the management blade 112 ServerView BX900 S1 Management Blade .dc=local") 8. 1.dc=qa2. "cn=Administrator.Configuring an openLDAP Server User Management 4.

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. Figure 84: Logging in on the management blade as an LDAP user ServerView BX900 S1 Management Blade 113 .

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

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

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

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

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

Ê Open the "Other" sheet in the right-hand (content) frame. Ê Press the "OK" button. Ê Press the "Edit" button. Ê Press the "Apply" button of "Other" sheet.User Management Ê Click on that object and select "Modify Object" from the context menu. Reload the LDAP configuration. Ê Select "ldapBindRestrictions" of "Valued Attributes". Ê 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

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

figure 95 shows how an AuthorizationRole is selected in the "DeptX" department. These AuthorizationRoles are contained in the department created using LDAPDeployer within the eDirectory Server's directory structure.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 .

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

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

3.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 .Configuring an eDirectory Server User Management 6.

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 .

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

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 .

The ServerBooks DVD is part of the ServerStart Bundle delivered with each server system. [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.fujitsu.ts. I You will find further useful information in the documentation for your operating system.com. The PDF files for the manuals can also be downloaded free of charge from the Internet. The overview page showing the online documentation available in the Internet can be found via the URL: http://manuals.

.

79 Power Supplies 62.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. 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 . 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.

deleting (Telnet) 27 V VLAN information (Telnet) 36 W Watch Dog (Telnet) 24 Web user interface 45 138 ServerView BX900 S1 Management Blade .Redundancy 11 Refresh 76 Restore Configuration 59. 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. 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.