Fujitsu PRIMERGY BX400 User manual

User Guide - English
PRIMERGY BX400 Blade Server Systems
ServerView Management Blade S1
User Interface Description
October 2012

Copyright and Trademarks
Certified documentation
according to DIN EN ISO 9001:2008
To ensure a consistently high quality standard and
user-friendliness, this documentation was created to
meet the regulations of a quality management system which complies
with the requirements of the standard
DIN EN ISO 9001:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de

ServerView BX400 Management Blade S1
Copyright © 2012 Fujitsu Technology Solutions GmbH.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trade names and/or trademarks of their respective manufacturers.
– The contents of this manual may be revised without prior notice.
– Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information in this manual.
– No part of this manual may be reproduced in any form without the prior written permission of Fujitsu.
Microsoft, Windows, Windows Server, and Hyper V are trademarks or registered trademarks of Microsoft Corporation in the USA and other
countries.
Intel and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the USA and other countries.

Before reading this manual
High safety use
This product has been designed and manufactured for general uses such as general office use, personal use, domestic
use and normal industrial use. It has not been designed or manufactured for uses which demand an extremely high level
of safety and carry a direct and serious risk to life or body if such safety cannot be ensured.
These uses include control of nuclear reactions in nuclear power plants, automatic airplane flight control, air traffic
control, traffic control in mass transport systems, medical devices for life support, and missile guidance control in
weapons systems (hereafter, "high safety use"). Customers should not use this product for high safety use unless
measures are in place for ensuring the level of safety demanded of such use. Please consult the sales staff of Fujitsu if
intending to use this product for high safety use.
Technology controlled by the Foreign Exchange and Foreign Trade Control Law of Japan
Documents produced by FUJITSU may contain technology controlled by the Foreign Exchange and Foreign Trade
Control Law of Japan. Documents which contain such technology should not be exported from Japan or transferred to
non-residents of Japan without first obtaining authorization in accordance with the above law.

ServerView BX400 Management Blade S1

ServerView BX400 Management Blade S1

ServerView BX400 Management Blade S1 7
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2 Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 PRIMERGY BX blade server system – overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 The blade server concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Blade server management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.1 Features of the ServerView management blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.2 Redundancy of the ServerView management blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.3 Console redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3 Web user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3 The system page for advanced mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.4 Changing the user name and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4 Power management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.1 Power consumption display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2 Control via tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2.1 Monitoring tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2.2 Control tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.3 Configuration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2.4 Sequence Power-On/Off Time tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5 Global user management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1 Configuring an Active Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1.1 Installing the Windows Active Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1.2 Creating the LDAP structure (based on Microsoft Active Directory) . . . . . . . . . . . . . . . . . . . 44
5.1.3 Assigning domain users to the MMB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.1.4 Setting up the management blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.1.5 Logging in on the management blade as an AD user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.2 Configuring an openLDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.2.1 Base configuration of openLDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.2.2 Creating the LDAP structure (based on openLDAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.2.3 Assigning domain users to the MMB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.2.4 Setting up the management blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.2.5 Logging in on the management blade as an openLDAP user . . . . . . . . . . . . . . . . . . . . . . . . 53

8 ServerView BX400 Management Blade S1
5.3 Configuring an eDirectory server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.3.1 Installating the eDirectory server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.3.2 Creating the LDAP structure (based on eDirectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.3.3 Assigning domain users to the MMB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.3.4 Setting up the management blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.3.5 Logging in on the management blade as an eDirectory user . . . . . . . . . . . . . . . . . . . . . . . . 57
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

ServerView BX400 Management Blade S1 9

ServerView BX400 Management Blade S1 11
1 Introduction
The Fujitsu PRIMERGY BX400 S1 Blade Server is a completely dynamic server infrastructure in a single chassis
for branch offices and medium-size businesses.
The PRIMERGY BX400 S1 Blade Server offers the following advantages:
– Easy OS Installation
– Dynamic Power & Cooling
– Dynamic Virtualization: very large memory capacities and state of the art I/O performance
– Dynamic High Availability: Redundance with ServerView Resource Coordinator VE
– Dynamic Scalability: high density combined with stacking ability allow flexible scaling
The PRIMERGY BX400 S1 system unit can accommodate up to 8 server blades (or a mixture of server blades
and up to 4 single slot storage blades) in a 6U chassis for 19-inch racks or in a floorstand case.
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 13.
Figure 1: ServerView management blade
Further information is provided on the PRIMERGY ServerView Suite DVD2:
– PRIMERGY BX400 Blade Server – Operating Manual
– PRIMERGY ServerView Suite – ServerView Deployment Manager
– PRIMERGY BX400 Blade Servers – Manuals for various connection blades
– ServerView Operations Manager User Guide
IFor further information on updating BX components please refer to the Operating Manual of your BX system.

Notational conventions Introduction
12 ServerView BX400 Management Blade S1
1.1 Notational conventions
The following notational conventions are used in this manual:
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.
VCaution This symbol points out hazards that can lead to personal injury, loss of data, or
damage to equipment.
IThis 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 the 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.

ServerView BX400 Management Blade S1 13
2 PRIMERGY BX blade server system –
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
connection 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.
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
14 ServerView BX400 Management Blade S1
Supported programs
The ServerView management blade is compliant with IPMI (Internet Protocol Multicast Iniative) 2.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 connection blades
To enable communication with the connection blades, a CLI interface is provided. It allows to configure settings of
the connection 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 temperature of each server blade via the IPMB interface
– Monitoring the status of the system fans
– Setting the the system fans to an optimum speed
– Monitoring the status ot the power supply modules
– Monitoring the temperature of the connection 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 Management Blade provides SSL for network data privacy for Telnet as well as for HTTP connections.

BX Blade Server System Overview Blade Server Management
ServerView BX400 Management Blade S1 15
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.
The management blade in slot 1 becomes the master management blade by default.
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.

Blade Server Management BX Blade Server System Overview
16 ServerView BX400 Management Blade S1

ServerView BX400 Management Blade S1 17
3 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.
3.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 (example for a management blade address)
– Default IP address: 192.168.1.10
– HTTP SSL disabled: Port 80
– HTTP SSL enabled: Port 443
– Supported Web browsers: Internet Explorer and Firefox (always the current and the antecessor version)
– Maximum number that can be connected at the same time:
SM CLP: 4
SSH: 4
http/https: 3 Dashboard users, 10 Advanced users
A pop-up window will then open in which you enter your user name and password:
Figure 2: Input mask for login (Internet Explorer)
The default user name and the default password are both admin.
VAttention
The following special characters are not permitted in a password:
–"=22(hex)
–'=27(hex)
–\=5C(hex)
Likewise all non-printable characters inclunding blank character (= 0-20 hex) are not permitted either.

Dashboard Web user interface
18 ServerView BX400 Management Blade S1
It is strongly recommended that you change the password immediately.
If you enter an incorrect password more than three times, the message No Access Right! will appear.
3.2 Dashboard
After you have logged in successfully, a home page (start page) is displayed which provides
– an overview status and
– the most important daily operations
Figure 3: Frames of the Dashboard
The "Experience" drop-down list at the top right can be used to switch from the dashboard site (Standard) to the
WebUI configuration site (Advanced) and vice versa (see section “The system page for advanced mode” on
page 20).
The dashboard is divided into four working areas:
– System Unit (1)
– Front View - Rear View (2)
–Power(3)
– Event Log / Resolutions (4)
System Unit
Provides, among other things, information on the health and power status of the system unit.
Front View - Rear View
Front View

Web user interface Dashboard
ServerView BX400 Management Blade S1 19
Provides, among other things, information on the health status and shows a schematic overview of the front
side system unit components:
– server blades
– storage blades
– front-side I/O module
Rear View
Provides, among other things, information on the health status and shows a schematic overview of the rear
side system unit components:
– management blade
– connection blades
– rear fan units
–PSUs
Power
Provides information on the health status and power status of the system unit.
On the right the consumption mode is displayed with the current mode being marked by a green rectangle.
Clicking on the "Configuration" button leads the user to the Power Management/Configuration page of the
advanced WebUI where he/she can change the consumption mode. The different modes are explained
there.
Event Log
Provides a table with the newest 10 event log entries from the management blade and the server blades.

The system page for advanced mode Web user interface
20 ServerView BX400 Management Blade S1
3.3 The system page for advanced mode
After you have logged in successfully, and you click „Advanced“ in the navigation frame, an overview of the system
configuration is displayed, i.e. the installed components and their current status. The start page looks like this:
Figure 4: Frames of the start page in advanced mode
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 a BX400 system unit) is displayed in the field on the left below
the ServerView 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) beside the name of the user who is currently logged in.
●A HELP field at the far right below the Fujitsu logo.
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 BX400 Remote Management
Supplies an overview of all help texts.