BX Manblade s1 Uid en

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 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.2 Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 PRIMERGY BX Blade Server Systems – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 The Blade Server Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2 Blade Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.1 Features of the ServerView Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.2 Redundancy of the ServerView Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.3 Console Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 Telnet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 Entering the console mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.2 Console main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 Management Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3.1 Management Agent Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3.2 Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3.3 System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.4 Server Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3.4.1 Server Blade Control Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3.4.2 Server Blade Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.3.4.3 Server Blade CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.3.4.4 Server Blade Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3.4.5 Server Blade Voltage Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3.4.6 Server Blade Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3.4.7 Server Blade NIC Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.3.4.8 Server Blade Watch Dog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.3.5 Storage Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.3.6 Connection Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.3.7 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.8 Blue Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3.9 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.9.1 Management Blade Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.9.2 Server Blade Event Log Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.9.3 Server Blade Power On/Off Event Log Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.9.4 Management Blade Wrap Around Event Log Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.9.5 Backup All Event Log to USB Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.10 Set System Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.11 Server Blade CMOS Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.12 Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.13 Active Directory Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.14 VLAN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.3.15 I2C Bus Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.3.16 Management Blade Configuration Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
ServerView BX900 S1 Management Blade 3

3.3.17 Management Blade Base Configuration Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.4 Emergency Management Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.5 Console Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.6 TFTP Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.7 Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.8 Change Management Role To Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.9 Reboot Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.10 System Information Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.11 Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.12 Account Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4 Web User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.1 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.2 The Start Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.3.1 System (Status Overview) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.3.2 System Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.3.3 Management Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.3.4 Server Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.3.5 Storage Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.3.6 Connection Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.3.7 Rear Fan Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.3.8 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.4 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.4.1 Asset Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.4.2 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.4.2.1 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.4.3 System Information Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.4.4 Dump Post Mortem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.5 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.5.1 Local Service Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.5.2 Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.5.3 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.5.3.1 Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.5.3.2 New Local User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.5.3.3 Global Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.5.3.4 User Session Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.5.4 Backup/Restoration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.5.4.1 Backup/Restoration Management – BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.5.4.2 Backup/Restoration Management – iRMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.5.5 Firmware Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.5.6 Certificate Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.5.6.1 System Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.5.6.2 User Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.6 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.6.1 System Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.6.1.1 Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.6.1.2 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.6.1.3 Alerting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.6.1.4 Date Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4 ServerView BX900 S1 Management Blade

4.6.2 Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.6.3 Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.6.4 Base Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5 Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.1 Power Consumption display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

5.2 Control via tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
5.2.1 Monitoring tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
5.2.2 Control tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
5.2.3 Configuration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
5.2.3.1 Dynamic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
5.2.3.2 No Dynamic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.1 Configuring an Active Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

6.2 Configuring an openLDAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
6.3 Configuring an eDirectory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.3.1 Installation and Setup of eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.3.1.1 Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.3.1.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.3.1.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.3.1.4 Configuration of eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
6.3.1.5 iRMC Integration in eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.3.2 Installation of eDirectory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6.3.3 Configuring the LDAP structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6.3.4 Settings on the Management Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.3.5 Logging in on the Management Blade as an LDAP user . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

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

Notational Conventions Introduction
1.1 Notational Conventions

The following notational conventions are used in this manual:
V Caution This symbol points out hazards that can lead to personal injury, loss of data, or
damage to equipment.
I This symbol highlights important information and tips.
Ê This symbol refers to a step that you must carry out in order to continue with the
procedure.
italic Commands, menu items, names of buttons, options, file names, and path names are
written in italic letters in text.
<variable> Marked variables that must be replaced by current values.
fixed font System output is written using a fixed font.
semi-bold fixed font Commands to be entered through the keyboard are written in a semi-bold fixed font.
[Key symbols] Keys are presented according to their representation on the keyboard. If capital
letters are to be entered explicitly, then the Shift key is shown, e.g. [SHIFT] - [A] for A.
If two keys need to be pressed at the same time, then this is indicated by placing a
hyphen between the two key symbols.
If there are references to text or sections of text in this manual, then the chapter or section heading is placed in
the reference, and the page stated refers to the page on which the chapter or section begins.
1.2 Target Group

This manual is intended for system administrators, network administrators, and service technicians that have a
basic knowledge of hardware and software. The manual informs the reader of the fundamentals of blade server
monitoring and documents the requirements for the use of the ServerView management blade.

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

When performing administrative tasks for the blade server system, the user relies on functions provided by a
system component called the ServerView management blade. There are two ServerView management blades in
a blade server system, in order to ensure redundancy.
The user gets access to the functions provided by the ServerView management blade, either via a web user
interface, or via a console menu using the Telnet protocol. 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”).
2.2.1 Features of the ServerView Management Blade

Within the blade server system the ServerView management blade is equipped with a number of features, which
are described in this section.
Controller
The ServerView management blade is equipped with an AMCC PPC405EP controller.

Blade Server Management BX Blade Server System Overview
Supported programs
The ServerView management blade is compliant with IPMI (Internet Protocol Multicast Iniative) 1.0. It supports
schemes like FRU (Field Replaceable Units), SEL (System Event Log), and SDR (Sensor Data Records). It also
allows the configuration of a watchdog timer.
Communication with the server blades

The ServerView management blade communicates with the server blades via an I2C bus. An IPMB interface is
provided to support the user, when performing hardware monitoring tasks for the server blades.
Communication with the switch blades

To enable communication with the switch blades, a CLI interface is provided. It allows to configure settings of the
switch blades, such as the IP address, the IP mask, or the IP gateway address.
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, i. e. if they have been opened, and other impacts on air flow condi-
tions
– 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, the ServerView management blade is
equipped with an event repository, providing a 2 x 32 MB SDRAM.
Auto configuration
The management function auto configuration is used to back up system parameters to a ROM, which is located
on the management blade. It also provides the possibility to restore these paramters if required. This reduces the
risk if system configuration data have been corrupted or lost.
SSL (Secure Socket Layer)

The Manager Blade provides SSL for network data privacy for Telnet as well as for HTTP connections.

BX Blade Server System Overview Blade Server Management
2.2.2 Redundancy of the ServerView Management Blade

Of the two ServerView management blades within the blade server system, one will take over the role of the
master, who is in charge of the server management, while the other one will remain in a standby status as a
redundant component. The two components have the same IP address, but their MAC adresses differ from each
other.
When the system is powered up, it depends on which of the two ServerView management blade first outputs a
heartbeat. This is then the one that will be the master.
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, for instance, when unplugged by the system administrator,
the standby component will take over control of the server management.
Fail-over scenario
When the redundant ServerView management blade takes over control from the master, it will behave according
to the following scenario:
– Issue an ICMP broadcast ping to update the ARP table and switch the IP filtering table, in order to adjust them
with regard to the new MAC address
– Define a proprietary protocol in L2, which is used for remote communication
If communication between master and redundant component via the serial interface has broken down, these
components can continue to communicate by sending IP broadcast packages, using the MAC addresses.
2.2.3 Console Redirection

When using the console redirection feature, the management of the blade server system may be executed in
remote control mode. To support this mode, the ServerView management blade acts as the console redirection
agent.
The KVM (Keyboard/Video/Mouse) input is captured and sent to the ServerView management blade. The
ServerView management blade will in turn send this input to a server blade, where the appropriate actions will be
executed.

3 Telnet Interface
Within the blade server system a console menu is provided for server management, using the Telnet protocol. A
number of configuration activities can be performed via this menu, e.g. IP address configuration or hardware status
monitoring. The menu is described in this chapter.
3.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 estab-
lished first. For this purpose a RS232 cable (null modem cable) is used. An RX/TX signal will then be exchanged
via this cable.
After the connection has been established, the HyperTerminal option is called up on the PC.
The parameters for this option are to be set as follows:
Baud rate 115200

Parity bits None
Data bits 8
Stop bits 1
Flow control None
Terminal type VT100
The console mode can also be entered via LAN. In this case, the Telnet client is called up, and the login procedure
is performed using the management blade IP address.
The settings are then as follows:
Host IP address 192.168.224.10 (example for a management blade address)

Telnet port Same as the Telnet port configured for the management blade (default port: 3172)
Connected protocol TCP/IP (Winsock)
Terminal type VT100
After these parameters have been set, the blade server system is started.
When using the serial port, firstly a number of messages concerning the system appears on the screen.
After approximately five seconds a welcome screen is displayed.

Entering the console mode Telnet Interface
The user is requested to enter a user name and eventually a password, to be admitted to the console main menu:
Figure 2: Welcome screen for access to the console menu

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

Management Agent Telnet Interface
3.3 Management Agent

The following items are provided in the Management Agent sub-menu for server management:
1. Management Agent Information (see 3.3.1 on page 17)
2. Management Blade (see 3.3.2 on page 19)
3. System Information (see 3.3.3 on page 20)
4. Server Blade (see 3.3.4 on page 21)
5. Storage Blade (see 3.3.5 on page 25)
6. Connection Blade (see 3.3.6 on page 25)
7. User Management (see 3.3.7 on page 27)
8. Blue Screen (see 3.3.8 on page 29)
9. Event Log (see 3.3.9 on page 30)
10.Set System Default (see 3.3.10 on page 32)
11.Server Blade CMOS Backup/Restore (see 3.3.11 on page 33)
12.Power Consumption (see 3.3.12 on page 34)
13.LDAP Authentication (see 3.3.13 on page 35)
14.VLAN Information (see 3.3.14 on page 36)
15.I2C Bus Management (see 3.3.15 on page 37)
16.Management Blade Configuration Backup/Restore (see 3.3.16 on page 37)
17.Management Blade Base Configuration Backup/Restore (see 3.3.17 on page 38)

Telnet Interface Management Agent
3.3.1 Management Agent Information

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

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

3.3.2 Management Blade

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

3.3.3 System Information

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

3.3.4 Server Blade

The Server Blade option provides general information on the server blades, i.e. information on CPUs, memory
modules, voltage, temperature, CMOS configuration and watchdog timers.
Figure 7: Server Blade menu
3.3.4.1 Server Blade Control Information

This option enables the user to set the following parameters:
Server Power Set server power:
(1) on
(2) off
(3) power-cycle
(4) reset
(5) NMI
(6) force off
Set Server Boot Mode The boot modes init and inventory are supported by VIOM function. For
details, please refer to the VIOM specification.
Set Server Blade Host Name Host name of the server blade. Is overwritten with the host name assigned
in the operating system when ServerView agents are used.
Server LED Control Configuration of the LED control at the front of the blade server: blinking or
off.
Server Power Control Mode Shows the current mode of Consumption Control (if Consumption Mode is
enabled).
Server Memory Dump Flag Indicates the status of the Server Memory Dump Flag (normal or off).
Server Power On/Off Time Control The user can set up a power on/off schedule for server blade.
Server Power Force Power Off Controls the "forced" shutdown (termination of processes is not waited for;
Enabled these are closed immediately).
Server Power Force Power Off If the "proper" shutdown of the server blade fails, the "forced shutdown" is
Control initiated after n minutes.

BIOS Recovery Flash Bit This option can be selected if the server blade’s BIOS has problems or a
flash has failed. After the option has been set, the blade can be started up
"without" the BIOS. It then searches autonomously for a suitable BIOS on
the connected media (floppy, USB stick, CD/DVD) and flashes it.
iRMC Address Configuration Sets up the LAN connection of the iRMC.
3.3.4.2 Server Blade Information

This option displays some information on the server blade parameters. The following parameters are included:
Server Blade Status Displays the server blade health status.
Server Blade Manufacture Displays the server blade manufacturer.
Server Blade Manufacture Date Displays the server blade production date.
Server Blade Serial Number Displays the server blade serial number (systems).
Server Blade Identify Serial Displays the server blade serial number (motherboard).
Number
Server Blade Product Name Displays the server blade product name.
Server Blade Product Version Displays the server blade product version.
Server Blade Model Name Displays the server blade model name.
Server Blade Hardware Version Displays the server blade hardware version.
Server Blade BIOS Version Displays the server blade BIOS version.
Number of CPU Socket Displays how many CPU sockets are available on the server blade.
Number of Memory Socket Displays server blade memory information.
Server Blade OS Type Displays the OS platform currently running on the server blade.
Server Blade OS Version Displays the version of the OS currently running on the server blade.
Server Blade iRMC Firmware Displays the server blade iRMC firmware version.
Version
Server Blade Mezzanine Card Displays whether a Mezzanine card is installed.
Server Blade Active GUID Normally the same value as in the Server Blade Manufacture GUID (see next
entry). However, if the VIOM was enabled, the Active GUID differs from the
Manufacture GUID.
Server Blade Manufacture GUID Globally Unique Identifier which is stored in the BIOS.
3.3.4.3 Server Blade CPU

This option displays some information on the server blade CPU parameters. The following parameters are
included:
CPU Type Displays the CPU type.
CPU Frequency Displays the CPU frequency.
CPU ID Displays the CPU ID.

CPU Status Displays the CPU status. The values displayed will be:
– OK
– NOT_PRESENT
– ERROR
– CRITICAL
– MISSING_TERMINATION
CPU Name Displays the CPU name.
CPU Socket Designation Displays the CPU socket designation.
CPU Manufacturer Displays information on the CPU manufacturer.
CPU Clock Displays the CPU clock.
3.3.4.4 Server Blade Memory

This option provides information on the server blade memory. The information is displayed in two tables:
Server Blade Memory Infor- Displays information on the total size of the memory, as well as on the error
mation Table count, the error reset record and the error count start time.
Server Blade Memory Modules Displays the status of each memory module, together with memory type and
Table error information.
3.3.4.5 Server Blade Voltage Table

This option provides information on the server voltage. The following parameters are displayed:
Server Voltage Designation Displays the voltage designation for the server blade.
Server Voltage Status Displays the voltage status for the server blade. The values displayed will be:
– NOT_AVAILABLE
– OK
– TOO_LOW
– TOO_HIGH
Server Voltage Minimum Value Displays the minimum voltage value for the server blade.
Server Voltage Maximum Value Displays the maximum voltage value for the server blade.
Server Voltage Current Value Displays the current voltage value for the server blade.
Server Voltage Nominal Value Displays the nominal voltage value for the server blade.
3.3.4.6 Server Blade Temperature

This option provides information on the server temperature. Some of the parameters displayed can also be set by
the user:
Server Temperature Sensor Designation Displays the designation of the temperature sensor for the server
blade.

Server Temperature Sensor Status Displays the status of the temperature sensor. 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.
Server Temperature Upper Critical Level This parameter can be set to configure the upper critical level of the
Server Temperature Lower Warning Level This parameter can be set to configure the lower warning level of the
Server Temperature Lower Critical Level This parameter can be set to configure the lower critical level of the
Server Temperature Current Value Displays the current temperature value for the server blade.
3.3.4.7 Server Blade NIC Information

This option displays the IP and MAC address of the server blade.
Server Blade NIC IP Table Address table of the server blade's Network Interface Card.
Server Blade MAC Address Table Table with all MAC addresses of the server blade.
3.3.4.8 Server Blade Watch Dog

This option is used to configure the watchdog timers for the server blade. There are two timers that can bet set
here:
Server Blade Software Watchdog This timer is used to monitor the operation system and the software applica-
tions. A watchdog timer agent that resets the timer must be implemented in
the operation system. When the time-out is reached, a time-out routine will
be started.
Server Blade Boot Watchdog This timer is used to monitor the server blade POST. It will be reset by the
BIOS in periods configured within the POST code. When the time-out is
reached, a time-out routine will be started.

3.3.5 Storage Blade

Figure 8: Storage Server Blade menu
Storage Blade Status Displays the storage blade health status.
Storage Blade Manufacture Displays the storage blade manufacture vendor.
Storage Blade Manufacture Date Displays the storage blade manufacture date.
Storage Blade Serial Number Displays the storage blade serial number (systems).
Storage Blade Identify Serial Displays the storage blade serial number (motherboard).
Number
Storage Blade Product Model Displays the type name of the storage blade (e.g. PRIMERGY SX940 S1).
Storage Blade Product Name Displays the storage blade product name.
Storage Blade Product Version Displays the storage blade product version.
Storage Blade Model Name Displays the storage blade model name.
Storage Blade Hardware Version Displays the storage blade hardware version.
3.3.6 Connection Blade

The Connection Blade option is used to display information on the connection blades that are part of the blade
server system.
Currently supported are the following types of connection blades:
1. GbE Switch Blade
2. FC Switch Blade
3. GbE IBP Blade
The menu for all these types is the same and looks like this:

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

3.3.7 User Management

The User Management option is used to change, add and delete users.
The following four user types (roles) with different permission rights are possible:
1. Administrator
2. OEM
3. Operator
4. User
The access rights of the various user roles are as follows:
Administrator
This role allows the user
– to create, update, and delete a user account
– to configure system settings related to the MMB, connection blades, and server blades
– to use commands on the iRMC controller as a result of IPMI permission level assignments of LAN/Serial
for administrators
– to use the functions at the usual user interfaces (Web UI, CLI etc.)
OEM
– to have the same functions as the Administrator and
– to use OEM commands and functions on the iRMC controller
Operator
– to use commands on the iRMC controller as a result of IPMI permission level assignments of LAN/Serial
for operators
User
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, because no explicit entry is provided for this.
We will therefore use an example to describe how you must proceed in this case.
Step 1
Select the user to be deleted, in this example the user Tom – type 2:

Figure 10: User Management – deleting a user
Step 2
Now select the name of the user to be deleted – type 1:

Step 3
To delete the user, simply press the space bar, then enter RETURN:
Step 4
User Tom has been deleted, as you can see in the menu:
3.3.8 Blue Screen

The Blue Screen option is available, if the operating system used supports the blue screen feature, as provided by
UART.
The option will then display which server blades are currently in blue screen status.

3.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.
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.3.9.1 Management Blade Event Log

This sub-option is used to display the events that have been logged on the management blade event log.
All Event All events that have been logged on the management blade.
Informational Event The informational events that have been logged on the management blade.
Minor Event The minor events that have been logged on the management blade.
Major Event The major events that have been logged on the management blade.
Critical Event The critical events that have been logged on the management blade.
Clear All Entries This parameter is used to clear all events from the management blade event log.

3.3.9.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.
After a server blade has been selected, the following parameters are displayed:
All Event All events that have been logged on the server blade.
Informational Event The informational events that have been logged on the server blade.
Minor Event The minor events that have been logged on the server blade.
Major Event The major events that have been logged on the server blade.
Critical Event The critical events that have been logged on the server blade.
Clear All Entries This parameter is used to clear all events from a server blade event log.
3.3.9.3 Server Blade Power On/Off Event Log Enable

This option is used to specify, whether power on/off events for the server blades should be listed in the event log.
3.3.9.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.
enable When the event log repository is full, new event log entries replace the old ones beginning
with the first event log entry.
disable When the event log repository is full, no event log entries are written any longer.
3.3.9.5 Backup All Event Log to USB Device

This option is used to save the MMB’s event log to a USB medium.
USB device selection Selects the USB medium (all the devices connected to the MMB are displayed
here).
Filename (empty default name) Name of the file which will be written to USB – if nothing is entered, a default
name is used.
Enable Starts the backup to the USB medium.

3.3.10 Set System Default

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

3.3.11 Server Blade CMOS Backup/Restore

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

3.3.12 Power Consumption

This option is used to control the power consumption.
Figure 17: Power Consumption menu
Power Budget Control Threshold Displays the max. DC power of the active power supply.
Base Consumption Power consumption of the base system. Includes one management
blade and 6 fan modules.
Total Consumption Current power consumption of the whole blade server system
(including server blades).
Remaining Difference between Power Budget Control Threshold and current Total
Consumption.
System Power Unit Status Table Displays the max. DC power and the voltage range of the power
supply units.
Storage Blade Current Power Shows the current power consumption of the storage blade.
Consumption Table
Server Blade Power Consumption Table Displays the max. DC power consumption of each server blade.
Storage Blade Power Consumption Table Displays the max. DC power consumption of each storage blade.
Connection Blade Power Consumption Displays the max. DC power consumption of each connection blade.
Table
Connection Blade Current Power Shows the current power consumption of the connection blade.
Consumption Table
Set Power Budget Control Settings for power control (redundancy, dynamic, limit values, etc.) –
observe submenus.

3.3.13 Active Directory Authentication

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

3.3.14 VLAN Information

MMB supports up to 10 VLAN IDs.
Figure 19: VLAN Information menu
The following parameters are displayed for each group:
VLAN Group ID Identifies different VLAN group IDs. The integer 2 to 4095 are supported.
VLAN IP Sets the VLAN IP.
VLAN Network Mask Sets the VLAN network mask.
VLAN Enable Enables/Disables the VLAN function.

3.3.15 I2C Bus Management

This function is used to enable/disable I2C bus communication between MMB and server blades. Once I2C bus is
set to disable, MMB cannot update any server blade status.
Figure 20: I2C Bus Management menu
3.3.16 Management Blade Configuration Backup/Restore

This option enables all the MMB settings, including certificates, users, etc., to be backed up/restored.
Figure 21: Management Blade Configuration Backup/Restoration menu

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.
Figure 22: Management Blade Base Configuration Backup/Restoration menu

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.

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.
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 Description
Console Redirect Connection Blade This option is used to configure a connection blade for console
redirection.
Set Return Hotkey, Ctrl+(a character) 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.

Telnet Interface TFTP Update
3.6 TFTP Update

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

Change Management Role To Slave Telnet Interface
3.8 Change Management Role To Slave

This item is used to change the role of the management blade.
I This menu item appears only if the system is redundant in design.
3.9 Reboot Management Blade

This item is used to perform a reboot of the system. The reboot is executed immediately.
I This menu item appears only if the system is not redundant in design.
3.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.
Figure 26: System Information Dump menu
System Configuration/Status Displays a consecutive list of system information, e.g. status, IP address, MAC
address and firmware version of the switch blades.
SEL for Management Blade Displays the management blade event log.
Server Blade Configu- Displays a consecutive list of information about the server blades, e.g. status,
ration/Status BIOS version, iRMC firmware version, OS type and OS version.
SEL for Server Blade Displays the server blade event log.
Dump System Information Provides information about temperatures, voltages, fan speeds, all modules’
FRU data and event logs.
Dump Post Mortem Use in case of problem, to get all necessary information on customer site to
analyze the problem in the development.

Telnet Interface Command Line Interface
Dump System Information/POST Permits the System Information Dump and POST Mortem Dump to be backed
Mortem Backup Configuration up on a USB medium.
3.11 Command Line Interface

This option is used to get chassis information or to manage series of servers.
Figure 27: Command Line Interface menu
SMASH CLI Shell The SMASH (Systems Management Architecture for Server Hardware) Shell
enables a simple and intuitive management of servers in data centers independent
of machine state, operating system state, server system topology or access method.
I Type exit to quit the SMASH CLI submenu.

Account Management Telnet Interface
3.12 Account Management

This option is used to change the user password.
Figure 28: Account Management menu

4 Web User Interface
On the web server an interactive and user-friendly web user interface, known as web console, is provided for
server management. It does not depend on any special operating system for a platform. You log into this interface
via the web browser.
4.1 Login
You log into the web server by entering an IP address in the browser’s URL line, e.g.
http://10.40.36.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.
I If you enter an incorrect password more than three times, the message No Access Right! will appear.

The Start Page Web User Interface
4.2 The Start Page

After you have logged in successfully, a home page (start page) is displayed which provides an overview of the
system configuration, i.e. the installed components and their current status. The start page looks like this:
Figure 30: Frames of the start page
The start page consists of five frames:

banner frame (1), status frame (2), navigation frame (3), main frame (4) and bottom frame (5).
1. Banner frame (1)
The banner frame comprises the following fields:
● The name of the blade server (in this example BX900S1em_172) is displayed in the field on the left below the
logo.
● The name of the current user (in this example the user admin) is displayed in the upper field on the right.
● A link for signing out (Sign out) below the name of the user who is currently logged in.
● A HELP field at the far right below the link to sign out.
The HELP field is in turn subdivided into three fields. These fields become visible as soon as the cursor
points to HELP. The fields are:
– About
Supplies information about the current firmware status.
– On Page
Shows the help text for the selected menu item (see Navigation frame below).
– On BX900 Remote Management
Supplies an overview of all help texts.
The banner frame is collapsible ( ).
2. Status frame (2)
The status frame consists of a number of graphical or text controls or displays. Taking our example in figure 30,
we will describe the various elements below, showing the graphical elements in a list and separating them with
⏐. Viewed from top left to bottom right, the following elements are involved here:

Web User Interface The Start Page
⏐ ⏐
This field displays the overall status of the blade server.
The icon on the left (red) indicates that an error of the type "Critical Error" has occurred in the system.
Such as error must be corrected immediately. The components which are affected are displayed in the
navigation frame (see below). It is possible for more than one error of this type to occur 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. A PDA (Prefailure Detection Analysis) reports problems in hardware components (fans,
CMOS batteries, memory modules and hard disk drives) before these result in a system failure. The
component which is affected is displayed in the navigation frame (see below). It is possible for more than
one error of this type to occur in the system.
The icon on the right (green) indicates that the system is operating without error.
I If errors of the type "Critical Error" and of the type "Warning" or "PDA Error" have occurred simul-
taneously in the system, the higher-ranking error, i.e. the red icon, is always displayed here.
This button enables you to refresh all the blade server data.
Uptime
Specifies the time since the blade server was started.
CSS: ⏐ yellow blinking ⏐

This field indicates errors of the type "CSS" (Customer Self Service), in other words errors which users
can rectify themselves. 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.
When the yellow icon is in the blinking state, it is not a warning but indicates an error of the type "Critical
Error". Detailed information on these error types is provided at the start of this list. The gray icon indicates
that all system components are operating without error.
Error: ⏐ red blinking ⏐

This field indicates errors of the type "Error", in other words errors which cannot be corrected by the user,
but can only be rectified by Customer Service. The component which is affected is displayed in the
navigation frame (see below).
The red icon indicates that an error of the type "Warning" or "PDA Error" has occurred in the system.
When the red icon is in the blinking state, it is not a warning but indicates an error of the type "Critical
Error". Detailed information on these error types is provided at the start of this list. The gray icon indicates
that all system components are operating without error.
Controller Time
This field specifies the blade server’s current data and time.
Power Consumption Mode: disabled⏐Minimum Power⏐ Best Performance

This field is a link to the Power Management → Configuration page in the navigation tree. It indicates the
Operation Mode configured.
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; then you select the
mode you require in the Consumption Control block using the Operation Mode pull-down menu. The
possible modes are: disabled, Minimum Power, Best Performance. After you actuate Apply, the mode
selected is displayed in the status frame after the colon.
For details, please refer to chapter “Power Management” on page 79.

Scheduled
Power Consumption Mode: off⏐on
This field indicates whether Power Consumption Mode is switched on or off.
This icon is optional and is displayed only if a USB stick is connected to the Master Management Blade.
⏐
You use the Locate button to switch the blade server’s and MMB’s ID LED on (blue) or off (gray).
In the 2nd line (bar chart) the current primary input power of the PSUs and the maximum possible power
consumption of the active PSUs are displayed in the form of a bar chart and in figures in watts. The
maximum possible power consumption can vary dynamically if the Dynamic Mode option was enabled on
the Power Management → Configuration page.
The 3rd line provides information about the secondary output power which is still available for the blades
up to the specified upper limit, which is dynamic. 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).
I If you have configured a "Consumption Limitation" (Power Consumption Options → Consumption
Mode → Consumption Limitation) using the Power Management → Configuration menu item, 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, please refer to chapter “Power Management” on page 79.
System Unit Details

This button enables you to collapse the status frame.
I The gray bar at the bottom of the status frame normally only contains the name of the component selected
on the right. However, if you have selected a server blade, 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. You
use the Video Redirection button to open a virtual console for the blade.
The other fields have the same meaning as described above for the status frame.

3. Navigation frame (3)

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

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

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

Components Web User Interface
4.3 Components
The Components function provides information on hardware components of the system. This option has the
following sub-functions: Status Overview, System Unit, Management Blades, Server Blades, Storage Blades,
Connection Blades, Power Supplies.
4.3.1 System (Status Overview)

The Status Overview displays a list of all available components in the main frame, plus their status. Clicking on a
component causes further information to be displayed.
4.3.2 System Unit

System Information
System Name
The name of the system unit. <System Name> may not be longer than 14 characters and must start
with a letter that can be followed by letters, digits and underscores ("_").
The system name is also used for DNS name resolution and as DHCP client identifier and therefore
has to be unique.
System Location
The location of the system unit.
System Contact
The contact information for this system unit.
Rack Name
The rack name of the system unit. <Rack Name> may not be longer than 13 characters and must
start with a letter that can be followed by letters, digits and underscores ("_"). Note that the rack name
can also be empty.
Unique Rack ID
The unique rack ID of the system unit.
Automatic Inventory Retrieval
If set to AUTOMATIC, the inventory retrieval is performed automatically for the server blades which
are inserted or when the system unit is powered on. If set to MANUAL, automatic inventory retrieval
is not performed.
Update All Connection Blade Names On Changing Rack Name
When this function is enabled, 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. Other types of
connection blade are not affected by this function.
Fan Control
Enables the user to configure the reaction when individual fans fail or are unavailable.
All Fans Have Failed
Enables the user to configure the reaction after all fans fail or are unavailable. Possible reactions: "continue"
or "shutdown-and-poweroff".
Fan Test
Daily test time
Sets the fan test time for the system fan. The format should be HH:MM.

Web User Interface Components
Test at every startup

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

Minimum Voltage Value

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

4.3.4 Server Blades
Server Blade-1 ... n
Information
Blade Asset Information
Manufacturer
Displays the manufacturer of the server blade.
Product Model
Displays the server blade product model name.
Product Name
Displays the server blade product name.
Product Version
Displays the server blade product version.
Model Name
Displays the product part number.
Serial Number
Displays the server blade serial number.
Identification Serial Number
Displays the identification serial number.
Firmware Version
Displays the server blade iRMC firmware version.
Hardware Version
Displays the server blade hardware version.
Production Date
Displays the date the server blade was produced.
Active GUID
Displays the active GUID.
Manufacturer GUID
Displays the manufacturer GUID.
Mezzanine Card
Displays whether a Mezzanine card is installed or not.
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.
BIOS Version
Displays the server blade’s BIOS version.
CPU Information
Displays CPU processor information, including type, speed, CPU stepping, and socket type.
Memory Information
Displays the memory module information and configuration.
Network Card Information
Displays the MAC address, IP address, NIC type, BIOS enabled, ekeying enabled and associated
Connection Blade for network card.
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. Events are displayed with the following information.
Time Stamp

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

4.3.5 Storage Blades
Storage Blade-1 ... n

Blade Asset Information
Manufacturer
Displays the manufacturer of the storage blade.
Product Name
Displays the storage blade product name.
Product Model
Displays the storage blade product model name.
Part Number
Displays the storage blade part number.
Serial Number
Displays the storage blade serial number.
Product Version
Displays the storage blade product version.
Production Date
Displays the date the storage blade was produced.
Hardware Version
Displays the storage blade hardware version.
Associated Server Blades
Left Side
The adjacent server blade on the left-hand side.
Right Side
The adjacent server blade on the right-hand side.

4.3.6 Connection Blades
GbE Connection Blade
Information
Manufacturer
Displays the connection blade's production information.
Production Date
Displays the connection blade's production date.
Serial Number
Displays the connection blade’s serial number.
Product Name
Displays the connection blade’s product name.
Model Name
Displays the connection blade’s model name.
Hardware Version
Displays the connection blade’s board version.
Firmware Version
Displays the connection blade's management firmware version.
Firmware Mode
Displays the firmware mode (IBP or Switch).
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).
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"). For connection blades with product name
"PY CB Eth Switch/IBP 10Gb 18/8" the command reset has to be used.
The mode can also be set in the Web interface of the selected GbE connection blade.
Management Port MAC Address
Displays the MAC address of the connection blade's service port.
Administrative URL
URL address to link to the connection blade's web homepage.
Power Management
Power Setting
The user can reset the blade after selecting the power action and clicking the Apply button.
Configuration
User Assigned Name
Enter the connection blade's user assigned name. 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.
The connection blade takes the assigned name and uses it (if it was not overwritten) for the following system
settings:
1. Connection Blade CLI Prompt Name
2. Port Naming
3. Host name
4. DHCP Client Identifier

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

Local Backup Files

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

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

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.
Local Backup Files
Offers you the option of searching for particular versions which have been backed up in local files.
Restoration Status
After you have clicked the Restore button, the status is displayed here. After restoration has been completed,
View Configuration
Displays the current interface data between the MMB and the connection blade.
4.3.7 Rear Fan Units

Unit Information
Manufacturer
Displays the rear fan unit’s manufacturer.
Product Name
Displays the rear fan unit’s product name.
Model Name
Displays the rear fan unit’s model name.
Product Version
Displays the rear fan unit’s product version.
Serial Number
Displays the rear fan unit’s serial number.
Firmware Version
Displays the rear fan unit’s firmware version.
Hardware Version
Displays the rear fan unit’s hardware version.
Production Date
Displays the rear fan unit’s production date.
CSS Component
Displays whether the rear fan unit is a CSS component or not.
Fan Details
Link to the rear fan unit’s details.
4.3.8 Power Supplies
PSU-1 ... 6
Monitoring
Group Status Information
Status
Displays the overall status for the system power supply.
Redundancy
Displays the power redundancy status of this system.
Unit Information
Status Fan1-Fan8
Displays the status of fan1to fan8 in the selected power supply.
OVP 12V Status
Displays the OVP 12V status.

UVP 12V Status

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

Information Web User Interface
4.4 Information
4.4.1 Asset Overview

The Asset Overview supplies general FRU information (FRU = Field Replaceable Unit), i.e. system components
which can be replaced relatively simply on the customer premises when a fault occurs. Clicking on a component
in the table causes its properties and operating status to be displayed.
Each component which is clicked on has a different number of tabs which provide further information.
4.4.2 Logging
The System Event Log function provides information on events that happened on the system. This option has the
following sub-functions.
4.4.2.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.
Export Event Log

Exports all available logs to the selected media as text files.
Event Log Filter

Displays all system events and can be filtered by component and severity by selecting filtering factors and clicking
the "Apply" button.
Component
Management blade or server blades.
Severity
Event Log Content

Time Stamp
Severity
Informational, Minor, Major, Critical.
Description

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

Operation Web User Interface
4.5 Operation
4.5.1 Local Service Display

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

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

4.5.3 User Management

The User Management enables administrators having the appropriate privileges to configure local user accounts.
4.5.3.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.
Permission
Displays the user permission rights. Possible user roles are: Administrator – OEM – Operator – User.
Delete
Deletes a user account.
New User
Switches to the configuration page for a new user account (see section “New Local User Account”).
4.5.3.2 New Local User Account
Configure User Account

Enabled
Checkbox for setting the account status (enabled/disabled).
Name
Configures the user name.
Password
Configures the password for the user account.
Confirm Password
Field for double-checking the password.
Permissions
Administrator
The user has full privileges to access the system.
OEM
The user has full privileges for access system but is not allowed to configure a user account.
Operator
The user can configure I/O modules.
User
The user has read permission.
User Shell
Permits the user to access the remote manager (CLI) or Server Management CLP.
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.
Special Server Blade Privileges

Configure User Accounts
To grant/restrict user accounts, configure permission of server blades.

Configure System Settings

This special privilege enables the iRMC configuration variables (Config Space Variables) to be modified.
This allows a user role with few privileges to be granted an additional special privilege.
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.
Enable Remote Storage
This special privilege enables a storage medium to be accessed which is made available via the server
blade’s iRMC. This allows a user to provide the OS of a server blade with additional IO functionality, e.g. to
install OS patches.
Access Bays
Access to bays can be granted/restricted. 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.5.3.3 Global Users

Defines if the users authenticated by the directory service have to be accessible over additional directory service
types. Two aspects must be observed here:
Disable Local Login
Disables/enables local login. Warning: If your directory server is unreachable and LDAP is enabled, you will
not be able to sign in.
Always use SSL Login
Enables/disables SSL login. If LDAP is disabled, this setting disables the standard Web browser authenti-
cation/login and forces the user to sign in via HTTPS.
4.5.3.4 User Session Information

Provides an overview of the users currently signed in.
4.5.4 Backup/Restoration Management
4.5.4.1 Backup/Restoration Management – BIOS
Backup
Permits the complete parameter set or a subset of a selected server blade to be saved.
BIOS Parameters of Server Blade
Selects available server blades to load the BIOS settings.
Current BIOS Parameters
Displays the current BIOS parameter values of the selected server blade.
Backup Parameter Set
Selects backup parameters by groups or detail items.
Backup Action
Permits the backup destination to be specified and the backup to be started.
Backup Media
Here you select the medium on which the access and configuration data is to be backed up (Memory,
USB or Local File).


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

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. 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. This also ensures that all service processors of the server blades have identical settings.
To permit successful restoration, it is necessary that the voltage status of the BX900 system unit should be at least
"auxiliary", i.e. the status display of the MMB glows green.
4.5.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.
TFTP Boot Image File Name
To set the management blade image file name.
TFTP Update Enable
Enables/disables the TFTP update.
Clicking the "Apply" button causes the TFTP firmware update configuration to be stored and starts the firmware
update if the TFTP update is enabled (enables single MMB firmware update / dual MMB firmware update).
Server Blade iRMC and Server Blade BIOS

TFTP Server IP Address
To set the TFTP server IP address which contains the server blade firmware image file.
TFTP Boot Image File Name
To set the server blade image file name.
">" moves selected blades to the upgrade window.
"<" removes selected blades from the upgrading window.
">>" moves all available blades to the upgrade window.
"<<" removes all available blades from the upgrading window.
Clicking the "Apply" button submits the TFTP update.

4.5.6 Certificate Handling
4.5.6.1 System Certificate
Certificate
Displays the details of the SSL/SSH certificate, including the version, serial number, signature algorithm, validity
and distinguished name of the subject and issuer.
Certificate Upload
The user can paste the private key and certificate in the blank field.
Certificate Signing Request

CSR Generation
Key size
Selects the key size for the key.
Country
Selects the country.
State/Province
The state of your locality.
Location
The locality where your organization is located or registered.
Organization
The official name of the organization.
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. If the certificate is to be used on an
intranet (or internal network), the common name can consist of one word, and it can also be the name of
the server.
Email Address
The contact email address.
The following information may be needed for CSR generation:
Download CSR and Private Key
4.5.6.2 User Certificate
User Certificate
User name
The user name for which the MMB will issue the certificate.
Password for User Certificate
Enter the password for the user certificate.
Confirm Password
Enter the password for the user certificate again for confirmation.
Start User Certificate Generation
Starts to generate the user certificate.
Download User Certificate
Downloads the generated user certificate. If the user certificate is not generated yet, error messages will be
displayed asking the user to generate the user certificate first.

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

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

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

Auth Type
Selects the authentication type. Auth-Login, Auth-Plain and Auth-Cram-md5 are supported.
AUTH User Name
Enter the authentication user name.
AUTH Password
Enter the authentication password.
Mail Format-dependent Configuration
The user can configure the sender email address, administrator name and phone number here. Up to 5 user
email addresses that can be modified are supported.
4.6.1.4 Date Time

Controller Time
Sets the date and time for the MMB. The format is (MM/DD/YYYY) and (HH:MM:SS).
Date/Time
Sets the time zone of this system and enables the Daylight Saving Time.
Network Time Protocol
Enable NTP
Enables/disables the NTP function.
NTP Server 1
Enter the NTP server IP address.
NTP Server 2
Enter an alternative NTP server IP address (if "Redundancy" is set, the MMB takes this second
address if the first one cannot be reached).
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.
Last Sync Date/Time
Displays the latest date/time that the management blade synchronizes with the NTP Server.
4.6.2 Refresh
Automatic Refresh
Enable Automatic Refresh
Enables/disables the Automatic Refresh Function.
Refresh Cycle
Sets the refresh interval for automatic refresh. The valid value is 1 to 15 minutes.
4.6.3 Language
The user can set the language of the Web UI and/or of the Local Service Display.

4.6.4 Base Configuration Wizard

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


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).
The example below is based on a system unit with 4 activated PSUs, as can be seen on the Power Management →
Configuration page. In addition to these 4 PSUs, 2 fans are also used (see figure).
Figure 38: System unit with 4 PSUs and 2 fans

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). The reason is that a fan can also be mounted in a PSU slot. In the status
overview on the welcome page both devices are specified correctly as fans (see figure):
Figure 39: Power Supply Status display
I If a PSU fails, the number of Available PSUs is decremented (in the example from 4 to 3):
Figure 40: Number of Available PSUs
The power consumption of a PSU depends on its type. Information on the type and power consumption can be
found on the sticker on the underside of the PSU (see figure).
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).

Power Management Power Consumption display
5.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, all of which are activated (available
status). 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). In the case of this maximum performance, the PSUs draw 19200W from the
supply network.
In the 2nd line (bar chart) the current primary input power of the PSUs and the maximum possible power
consumption of the active PSUs are displayed in the form of a bar chart and in figures in watts. The maximum
possible power consumption can vary dynamically if the Dynamic Mode option was enabled on the Power
Management → Configuration page (see section “Dynamic Mode” on page 89).
The 3rd line provides information about the secondary output power which is still available for the blades up to the
specified upper limit, which is dynamic. This value is changed by the system if Dynamic Mode is set.

Control via tabs Power Management
5.2 Control via tabs

On the Power Management page three tabs are available which are described in detail below:
1. Monitoring tab
2. Control tab
3. Configuration tab
5.2.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. Various settings can also be made in the "Power History Options" box.
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 Config-
uration tab. See also figure 61 on page 92 and figure 62 on page 93 below.

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.
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". If a hard power-off is
selected for the unit or the Force Power-Off has occurred, the server blades assume the status which is set in the
iRMC (see figure) after the system unit has been powered on.
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.
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.

5.2.3 Configuration tab

Various settings for and dependencies on the power consumption are controlled in the Configuration tab.
Figure 46: Power Management – Configuration tab

Re number 1 in figure 46 (Consumption Mode)

The following modes can be selected:
Figure 47: Consumption modes
Depending on the mode selected, the Apply buttons of the following boxes are shaded dark gray/enabled (can be
used) or shaded light gray/disabled (cannot be used).
The mode selected is also displayed at the top in the Status Frame:
Figure 48: Consumption modes

Re a) in figure 48 (Consumption Control)

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

Re b) in figure 48 (Consumption Limitation)

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

Re c) in figure 48 (Scheduled Power Consumption Mode)

If "Scheduled Power Consumption Mode" is selected, 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.
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

5.2.3.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.
Example 1: Dynamic Mode and Redundancy 3+3 (= Full Redundancy)

In the case of minimal power consumption, PSU-1 is active and PSU-6 is on active standby. All other PSUs are on
standby. If more power is required, Dynamic Mode switches PSU-2 to active and PSU-5 to active standby. PSU-3
and PSU-4 remain on standby (see figure).
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)".
Example 3: Dynamic Mode and Redundancy 5+1

In the case of minimal power consumption, PSU-1 is active and PSU-6 is on active standby. All other PSUs are on
standby. If more power is required, Dynamic Mode switches PSU-2 to active. PSU-3, PSU-4 and PSU-5 remain
on standby. If more power is required, Dynamic Mode switches PSU-3 to active, and PSU-4 and PSU-5 remain on
standby, and so on.

5.2.3.2 No Dynamic Mode

No Dynamic Mode means that the power currently needed is not calculated. All the PSUs which have been
configured are powered on.
Example 1: Redundancy 3+3 (= Full Redundancy)

PSU-1, 2, 3 active and PSU-4, 5, 6 on active standby (see figure).
Figure 57: No Dynamic Mode and Redundancy 3+3
Example 2: No Redundancy
All PSUs are active.
Example 3: Redundancy 3+1 (and 6 PSUs)

PSU-1, 2, 3 are active and PSU-6 is on active standby. PSU-4 and 5 are on standby. If one PSU-1 through PSU-
3 now switches to defective, PSU-4 becomes active (see figure).
Figure 58: No Dynamic Mode and Redundancy 3+1

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

Display for "Threshold Definition = Relative": in percent:
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

Configuration tab:
Figure 62: Metric power unit – Configuration tab

6 User Management
There are three interfaces to User Management:
1. Active Directory (for Windows systems)
2. OpenLDAP (for Linux systems)
3. eDirectory (for Windows and Linux systems)
6.1 Configuring an Active Directory Server

1. Installing a Windows Server
First a Windows Server Operation System (Microsoft Windows Server 2003 or 2008, in the example Windows
Server 2003) is installed on any server.
After installation has taken place, 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

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

User Management Configuring an Active Directory Server
(Group) SerialUser
(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
figure 65 shows the context menu for creating an organizational unit. The OUs must be configured in accordance
with the schema shown above.
Figure 65: Creating an organizational unit
As described above, groups must be created within the OUs (cf. figure 66 on page 98). The group scope "Global"
and the group type "Distribution" must be selected here. The group name (pre-Windows 2000) is a unique name.
If it already exists, it must be modified (cf. figure 67 on page 98).

Figure 66: Creating a group
Figure 67: New group
Finally, members must be assigned to the groups from Domain/SVS/Declarations/AuthorizationRoles. These come
from the path Domain/SVS/Declarations/Privileges/iRMC_MMB and can be selected freely by the administrator as
required.

Figure 68: Members of the Administrator group

Assigning Domain users to the MMB

To enable a user to log in on the management blade as a domain user, AuthorizationRoles must be set in the next
step (cf. figure 69 on page 100).
1. Create a user if none exists
2. In the AD Management select the AuthorizationRoles item (SVS – Departments – XY – AuthorizationRoles)
3. Add users to roles to grant the particular authorization (multiple selection is permitted for a user)
Figure 69: AD AuthorizationRoles
3. Settings on the Management Blade

figure 70 shows an example of the settings required for communication with an Active Directory.
1. LDAP Type: Windows Active Directory
2. LDAP Server IP: IP of the Domain Controller
3. Root Domain Name: Name of the domain
4. LDAP Base DN: Assigned automatically
5. User LDAP Base DN: Not required
6. User LDAP Department: Department configured by LDAPDeployer
7. Special User Account/Password: Not required
The IP settings and the DNS server must also be adjusted to the network concerned, and the time on the
management blade must be synchronized with that on the AD 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, the domain is appended in the login mask. The
syntax is: "user-name@domain" (e.g.: ad@qa2.local, cf. figure 71).
Figure 71: Logging in as an AD user
Whether a login was correct can be checked on the web interface (cf. figure 72).

Figure 72: AD user logged in

User Management Configuring an openLDAP Server
6.2 Configuring an openLDAP Server

1. Installing the openLDAP Server
A Suse Linux Enterprise Server 10 is taken as a basis. 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. Among other things, the domain "qa2.local
- dc=qa2,dc=local" and the root DN "cn=Administrator" which were assigned during installation can be recognized.
Both of these values are required for further configuration activities.
Figure 73: Configuration of openLDAP with Yast

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. This installation can be
performed later or while the overall system is being installed.
Figure 74: DHCP Server

Figure 75: DHCP Server card selection
Figure 76: DHCP Server LDAP support

Figure 77: DHCP Server address range

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.
figure 78 shows the result of a successful configuration:
Figure 78: LDAP structure


The next step is to create/edit users who are to be granted access to the management blade. The easiest way to
do this is to use Yast's user management (cf. figure 79).
Figure 79: User management

After the required users have been created, the LDAP browser is started from Yast. The password assigned when
the LDAP server was installed is required to do this.
Figure 80: LDAP browser

The path "ou=AuthorizationRoles" of the department concerned is selected in the tree structure (cf. figure 81).
Figure 81: LDAP authorization roles

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

4. Settings on the Management Blade

figure 83 shows an example of the settings required for communication with an openLDAP Server.
1. LDAP Type: OpenLDAP
5. User LDAP Base DN: ou in which the users are stored
7. Special User Account: Special user who takes over communication between the MMB and LDAP Server (e.g.
"cn=Administrator,dc=qa2,dc=local")
8. 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, and the time on the
management blade must be synchronized with that on the AD Server.
Figure 83: LDAP settings on the management blade

5. 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.
Figure 84: Logging in on the management blade as an LDAP user

Configuring an eDirectory Server User Management
6.3 Configuring an eDirectory Server
6.3.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)), providing LDAP connectivity over SSL.
The following requirements apply:
– eDirectory shall have a defined structure.
– The SSL certificate shall have a key size of1024 bits and algorithm md5RSAEnc.
– eDirectory shall be installed on Linux. The following was tested on SLES 10.
6.3.1.1 Software Components

– eDirectory 8.8 (20060526_0800_Linux_88-SP1_FINAL.tar.gz)
– eDirectory 8.8 (eDir_88_iMan26_Plugins.npm)
– iManager (iMan_26_linux_64.tgz for SuSE, otherwise iMan_26_linux_32.tgz)
– ConsoleOne (c1_136f-linux.tar.gz)
6.3.1.2 System Requirements

Ê OpenSSL must be installed. If it is not yet installed, install it before proceeding with eDirectory installation.
512 MB main memory is required.
6.3.1.3 Installation
A Linux server system must be fully installed and running.
The firewall must be configured to allow connections to ports 8080, 8443, 9009, 81, 389, 636, e.g. for OpenSuSE:
Ê Edit the file /etc/sysconfig/SuSEfirewall2.
Ê Add the ports to FW_SERVICES_EXT_TCP, in other words FW_SERVICES_EXT_TCP="8080 8443 9009 81
389 636".
According to the installation guide, the system shall be enabled for multicast routing. In order to do that for SuSE,
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.
This file must contain the following line (in addition):
224.0.0.0 0.0.0.0 240.0.0.0 eth0
eDirectory
eDirectory must be installed with root privileges. Below we assume that /home/eDirectory is the directory where all
the files needed for installation are stored, i.e. 20060526_0800_Linux_88-SP1_FINAL.tar.gz, iMan_26_linux_64.tgz
and c1_136f-linux.tar.gz have been copied into this directory.
Ê Get root privileges (su) and change into /home/eDirectory:
cd /home/eDirectory.
Ê Extract eDirectory:
tar -xzvf 20060526_0800_Linux_88-SP1_FINAL.tar.gz.
After the archive has been extracted, there is a new directory called eDirectory.

User Management Configuring an eDirectory Server
Ê Change to the setup of eDirectory: cd eDirectory/setup.

Ê Invoke the installation script: ./nds-install .
Ê Accept the EULA with "y".
Ê Press [ENTER].
Installation of Novell eDirectory Server

Ê Enter "1" when prompted for what to install.
Ê Press [ENTER].
Ê eDirectory packages will then be installed.
After installation you need to update some environment variables with the paths to eDirectory:
Ê Edit your configuration file (in the example, /etc/bash.bashrc).
Ê Insert the following lines before "# End of …"
1. export PATH=/opt/novell/eDirectory/bin:/opt/novell/eDirectory/sbin:$PATH.
2. export LD_LIBRARY_PATH=/opt/novell/eDirectory/lib:/opt/novell/eDirectory/lib/ndsmodules:
/opt/novell/lib:$LD_LIBRARY_PATH.
3. export MANPATH=/opt/novell/man:/opt/novell/eDirectory/man:$MANPATH.
4. export TEXTDOMAINDIR=/opt/novell/eDirectory/share/locale.
Close the terminal and open a new terminal again in order to enable the exported environment variables.
Installation of Novell eDirectory Administration Utilities

Ê Change to the setup of eDirectory: cd eDirectory/setup.
Ê Invoke the installation script: ./nds-install.
Ê Accept the EULA with "y".
Ê Press [ENTER].
Ê Enter "2" when prompted for what to install.
Ê Press [ENTER].
Ê Administration utilities will then be installed.
iManager
iManager is the recommended utility to administrate eDirectory. Use the *_64.tgz archive to install it on SLES10
and OpenSuSE.
Ê Get root privileges (su) and change to /home/eDirectory:
Ê Extract iManager: tar -xzvf iMan_26_linux_64.tgz.
After the archive has been extracted, there is a new directory called iManager.
Ê Change to installs of iManager: cd iManager/installs/linux.
Ê Invoke the installation script: ./iManagerInstallLinux.bin.
Ê Choose the language for installation messages.
Ê Go through the EULA step by step and accept it.
Ê Choose "1-Novell iManager 2.6, Tomcat, JVM" for installation.
– Choose "1-Yes" to download the plug-in.

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

1. #Syntax: TREENAME. FQDN:PORT

2. MY_TREE. mycomputer.mydomain:81
To start ConsoleOne later: /usr/ConsoleOne/bin/ConsoleOne.
6.3.1.4 Configuration of eDirectory
Create an NDS Tree

Before creating the NDS tree, please define essential information about the tree which is to be to created:
TREE NAME:
Name that you want to give your tree, e.g. MY_TREE. Must be unique in your network.
Server Name:
The representation of the instance of a server object in eDirectory, i.e. the name of the machine the LDAP
server runs on, e.g. lin36-root-0.
Server Context:
The fully distinguished name of the container under which the server object resides, e.g. dc=organi-
zation.dc=mycompany.
Admin User:
E.g. cn=admin.dc=organization.dc=mycompany.
NCP Port:
81.
Instance location:
/home/root/instance0.
Configuration file:
/home/root/instance0/nds.conf
Password for the admin user:
Ê Open a terminal box.
Ê Change to /home/eDirectory.
Ê Start "ndsmanage".
Ê Enter "c" to create a new instance.
Ê Enter "y" to continue.
Ê Enter "y" to create a new tree.
Ê Enter TREE NAME.
Ê Enter Server Name.
Ê Enter …
I After finishing configuration of your NDS tree, please reboot the server so that the configuration takes effect.
Configure eDirectory for LDAP
Log in to iManager using a Web browser and an admin account.
Install Role-Based Services

Ê Go to "Configure/Role Based Services/ RBS configuration".
Ê Run the RBS configuration wizard.
Ê Assign RBS2 to the container to be managed, in the example above, "mycompany".

Install Plug-Ins
Ê Go to "Configure/Plug-in installation/Available Novell Plug-in Modules".
Ê Browse for the eDirectory-specific plug-in package "eDir_88_iMan26_Plugins.npm".
Ê Select Install.
Configure Role-Based Services
Ê Click on available modules:
Ê Install all modules needed for LDAP.
If you are not sure, install all.
Configure eDirectory for SSL Use

The use of SSL/TLS is enabled by default in eDirectory. A temporary certificate is created during installation.
However, BMC FW is configured to use RSA/MD5 certificates for the SSL connection.
You can use ConsoleOne to create an RSA/MD5 certificate 1042 bytes in length.
Ê Open ConsoleOne. Use your administration account to provided authentication for the LDAP server.
Ê Go to the root of your company structure, e.g.: [treename\mycompany\myorganization]
Ê Select New Object → NDISPKI key material → custom:
1. key 1024
2. SSL or TLS
3. signature RSA/MD5
A new certificate of the desired type is created.
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. This tab has a drop-down list showing all installed
certificates in this system.
Ê Select the desired certificate in the certificate drop-down list.
Configure eDirectory for Non-SSL Use

Anonymous logins and plaintext passwords over unsecured channels are disabled by default. This means it is not
possible to log in and browse an eDirectory server without an SSL connection. In order to use LDAP without SSL:
1. Enable a non-SSL connection for LDAP:
Ê Open iManager in the Web browser.
Ê Log in to iManager using valid credentials.
Ê Select "Roles and Tasks View".
Ê Go to LDAP\Ldap Options\LDAP Server → Connection tab.
Ê Uncheck "Require TLS for all operations".
Ê Go to LDAP\Ldap Options\LDAP Group → General tab.
Ê Uncheck "Require TLS for Simple binds with password".
2. Lower Bind Restrictions
Ê Log in to iManager using valid credentials.
Ê Select "View Objects" .
Ê Step down the object-tree to the "LDAP Server" object.

Ê Click on that object and select "Modify Object" from the context menu.
Ê Open the "Other" sheet in the right-hand (content) frame.
Ê Select "ldapBindRestrictions" of "Valued Attributes".
Ê Press the "Edit" button.
Ê Set the value to "0".
Ê Press the "OK" button.
Ê Press the "Apply" button of "Other" sheet.
Reload the LDAP configuration.

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.

Ê Uncheck "exit on error" → Next.

Ê Enter the DAP server and admin account data → Next.
Ê Press "Finish".
I 1. Use an SSL connection for import (port 636).
2. Use LDAP protocol version 2.
Figure 87: ICE Wizard

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.

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

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

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

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

Figure 95: Selecting the AuthorizationRole
Figure 96: Accepting the settings

6.3.4 Settings on the Management Blade

figure 97 shows an example of the settings required for communication with an eDirectory Server.
1. LDAP Type: eDirectory
5. User LDAP Base DN: ou in which the users are stored
7. Special User Account: Special user who takes over communication between the MMB und LDAP-Server (e.g.:
cn=principal,ou=people,dc=sbrd4)
8. Special User Password: Password, for the user specified under item 7
The IP settings and the DNS Server must also be adjusted to the network concerned, and the time on the
Management Blade must be synchronized with that on the eDirectory Server.
Figure 97: Settings on the Management Blade

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

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

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

IPMB
Intelligent Platform Management Bus
IPMI
Intelligent Platform Management Interface
iRMC
integrated Remote Management Controller
ITS
Invitation to Send
KVM
Keyboard, Video, 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

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, Shamir, Adleman
RTC
Real Time Clock
RX
Receiver Cross
SDR
Sensor Data Records
SDRAM
Synchronous Dynamic Random Access Memory
SEL
System Event Log

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

VIOM
Virtual-I/O Manager
VLAN
Virtual Local Area Network
WWN
World Wide Name

Related Publications
PRIMERGY manuals are available in PDF format on the ServerBooks DVD. The ServerBooks DVD is part of the Server-
Start Bundle delivered with each server system.
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.ts.fujitsu.com.
I You will find further useful information in the documentation for your operating system.
[1] PRIMERGY BX900 Basic Unit
Operating Manual
[2] PRIMERGY BX Blade Server Systems

LAN Switch Blade – User Interface Description
User Guide
[3] ServerView Deployment Manager

User Manual
[4] BIOS Setup

Reference Manual
[5] ServerView Installation Manager

User Guide
[6] ServerView Operations Manager

User Guide
[7] PRIMERGY ServerView Suite

ServerView Virtual-IO Manager
User Guide

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

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

BX Manblade s1 Uid en

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

BX Manblade s1 Uid en

Enviado por

Direitos autorais:

Formatos disponíveis

PRIMERGY BX900 Blade Server Systems

ServerView Management Blade S1

Edition March 2010

Copyright and Trademarks

All rights reserved.

1.1 Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 PRIMERGY BX Blade Server Systems – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 The Blade Server Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1 Entering the console mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

ServerView BX900 S1 Management Blade 3

4 Web User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4 ServerView BX900 S1 Management Blade

5.1 Power Consumption display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6.1 Configuring an Active Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

ServerView BX900 S1 Management Blade 5

Figure 1: ServerView management blade – BX900 S1

Further information is provided on the PRIMERGY ServerBooks DVD:

ServerView BX900 S1 Management Blade 7

1.1 Notational Conventions

I This symbol highlights important information and tips.

1.2 Target Group

8 ServerView BX900 S1 Management Blade

2.1 The Blade Server Concept

2.2 Blade Server Management

2.2.1 Features of the ServerView Management Blade

ServerView BX900 S1 Management Blade 9

Communication with the server blades

Communication with the switch blades

SSL (Secure Socket Layer)

10 ServerView BX900 S1 Management Blade

2.2.2 Redundancy of the ServerView Management Blade

2.2.3 Console Redirection

ServerView BX900 S1 Management Blade 11

3.1 Entering the console mode

Baud rate 115200

Host IP address 192.168.224.10 (example for a management blade address)

ServerView BX900 S1 Management Blade 13

Figure 2: Welcome screen for access to the console menu

14 ServerView BX900 S1 Management Blade

3.2 Console main menu

Figure 3: Console main menu

There are nine items in the console main menu:

ServerView BX900 S1 Management Blade 15

3.3 Management Agent

16 ServerView BX900 S1 Management Blade

3.3.1 Management Agent Information

Figure 4: Agent Information menu

ServerView BX900 S1 Management Blade 17

These options are used to perform the following activities:

18 ServerView BX900 S1 Management Blade

3.3.2 Management Blade

Figure 5: Management Blade menu

The following parameters are displayed:

ServerView BX900 S1 Management Blade 19

3.3.3 System Information

Figure 6: System Information menu

The menu offers the following subordinate options to the user:

20 ServerView BX900 S1 Management Blade

3.3.4 Server Blade

Figure 7: Server Blade menu

3.3.4.1 Server Blade Control Information