Fujitsu siemens PRIMERGY BX Blade Server Systems User Interface Description
PRIMERGY BX Blade Server Systems
RemoteView Management Blade
User Interface Description
Edition November 2007
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@fujtsu-siemens.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 © 2007 Fujitsu Siemens Computers 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 . . . . . . . . . . . . . . . . . . . 10
2.2.1 Features of the RemoteView Management Blade . . . . . . . . 10
2.2.2 Redundancy of the RemoteView Management Blade . . . . . . 12
2.2.3 Console Redirection . . . . . . . . . . . . . . . . . . . . . . . 12
3 Telnet interface . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1 Entering the console mode . . . . . . . . . . . . . . . . . . 15
3.2 Console main menu . . . . . . . . . . . . . . . . . . . . . . 17
3.3 Management Agent . . . . . . . . . . . . . . . . . . . . . . . 19
3.3.1 Management Agent Information . . . . . . . . . . . . . . . . . 20
3.3.2 Management Blade . . . . . . . . . . . . . . . . . . . . . . . 24
3.3.3 System Information . . . . . . . . . . . . . . . . . . . . . . . 26
3.3.4 Server Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3.4.1 Server Blade Control Information . . . . . . . . . . . . . . 28
3.3.4.2 Server Blade Information . . . . . . . . . . . . . . . . . . . 29
3.3.4.3 ServerBlade CPU . . . . . . . . . . . . . . . . . . . . . . 30
3.3.4.4 Server Blade Memory . . . . . . . . . . . . . . . . . . . . 31
3.3.4.5 Server Blade Voltage Table . . . . . . . . . . . . . . . . . 32
3.3.4.6 Server Blade Temperature . . . . . . . . . . . . . . . . . . 32
3.3.4.7 Server Blade NIC Information . . . . . . . . . . . . . . . . 34
3.3.4.8 Server Blade Watch Dog . . . . . . . . . . . . . . . . . . . 34
3.3.5 Switch Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.6 Username and Password . . . . . . . . . . . . . . . . . . . . 37
3.3.7 Blue Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.8 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.8.1 Management Blade Event Log . . . . . . . . . . . . . . . . 39
RemoteView Management Blade
Contents
3.3.8.2 Server Blade Event Log . . . . . . . . . . . . . . . . . . . . 39
3.3.8.3 Server Blade Power On/Off Event Log Enable . . . . . . . . 40
3.3.8.4 Management Blade Wrap Around Event Log Enable . . . . . 40
3.3.9 Set System Default . . . . . . . . . . . . . . . . . . . . . . . . 41
3.3.10 Server Blade CMOS Backup/Restore . . . . . . . . . . . . . . 43
3.3.11 Switch Blade Configuration Backup/Restore . . . . . . . . . . . 45
3.3.12 Deployment Parameter . . . . . . . . . . . . . . . . . . . . . . 46
3.3.13 Power Consumption . . . . . . . . . . . . . . . . . . . . . . . 49
3.3.14 PPP and Modem Setting . . . . . . . . . . . . . . . . . . . . . 51
3.4 Emergency Management Port . . . . . . . . . . . . . . . . . 55
3.5 Console Redirection . . . . . . . . . . . . . . . . . . . . . . . 57
3.6 TFTP Update . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.7 Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.8 Reboot Management Blade . . . . . . . . . . . . . . . . . . . 61
3.9 System Information Dump . . . . . . . . . . . . . . . . . . . 62
4 Web user interface . . . . . . . . . . . . . . . . . . . . . . . . 63
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2 System Property . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.2.1 System Event Log . . . . . . . . . . . . . . . . . . . . . . . . 66
4.2.1.1 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.2.1.2 Alarm handler . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.2.2 Environment/Maintenance . . . . . . . . . . . . . . . . . . . . 69
4.2.2.1 Firmware Update . . . . . . . . . . . . . . . . . . . . . . . 69
4.2.2.2 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.2.2.3 UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.2.2.4 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.2.2.5 Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.2.2.6 Reset Management Blade . . . . . . . . . . . . . . . . . . . 75
4.2.3 LAN Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.2.3.1 Internet Protocol . . . . . . . . . . . . . . . . . . . . . . . . 76
4.2.3.2 Domain Name Server . . . . . . . . . . . . . . . . . . . . . 77
4.2.3.3 HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.2.3.4 Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.2.3.5 NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.2.3.6 SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.2.3.7 Duplex Mode . . . . . . . . . . . . . . . . . . . . . . . . . 78
RemoteView Management Blade
Contents
4.2.4 SNMP Interface . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.2.4.1 SNMP Communities . . . . . . . . . . . . . . . . . . . . . 79
4.2.4.2 SNMP Trap Destination . . . . . . . . . . . . . . . . . . . 79
4.2.5 Console Redirection . . . . . . . . . . . . . . . . . . . . . . . 80
4.2.5.1 KVM Switch for Local . . . . . . . . . . . . . . . . . . . . 80
4.2.5.2 IP Filters for Telnet, HTTP and SNMP . . . . . . . . . . . . 80
4.2.6 System Information . . . . . . . . . . . . . . . . . . . . . . . 82
4.2.7 User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.2.8 Deployment Table . . . . . . . . . . . . . . . . . . . . . . . . 83
4.2.9 PPP and Modem Setting . . . . . . . . . . . . . . . . . . . . 84
4.3 Management Blade . . . . . . . . . . . . . . . . . . . . . . . 85
4.4 Switch Blade . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.4.1 Switch Blade Info . . . . . . . . . . . . . . . . . . . . . . . . 86
4.4.2 Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.5 Adv. KVM Blade . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.5.1 Adv. KVM Blade Info . . . . . . . . . . . . . . . . . . . . . . . 88
4.5.2 Adv. KVM Blade Configuration . . . . . . . . . . . . . . . . . . 89
4.5.3 Global Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.5.3.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . 90
4.5.3.2 Global Viewer Control Elements . . . . . . . . . . . . . . . 92
4.5.3.3 Global Viewer Operating Tasks . . . . . . . . . . . . . . . 95
4.5.4 Adv. KVM Blade Update . . . . . . . . . . . . . . . . . . . . . 97
4.6 Server Blade . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.6.1 Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.6.1.1 Automatic Server Restart (ASR) . . . . . . . . . . . . . . . 99
4.6.1.2 Auto Configuration . . . . . . . . . . . . . . . . . . . . . . 99
4.6.1.3 Power Control . . . . . . . . . . . . . . . . . . . . . . . . 100
4.6.1.4 Boot Option . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.6.2 Blade Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.6.2.1 Blade Info . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.6.2.2 Memory Module . . . . . . . . . . . . . . . . . . . . . . . 101
4.6.2.3 Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.6.2.4 Temperature . . . . . . . . . . . . . . . . . . . . . . . . . 102
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
RemoteView Management Blade
1 Introduction
The PRIMERGY BX Blade Server Systems accommodate two hotswapable,
redundant RemoteView 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 RemoteView Management
Blade” on page 10.
Figure 1: RemoteView management blade
Further information is provided on the PRIMERGY ServerBooks CD:
– PRIMERGY BX300 Blade Server System – Operating Manual
– PRIMERGY BX600 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.
RemoteView Management Blade 7
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.
<italic> Marked variables that must be replaced by current values.
fixed font System output is written using a fixed font.
semi-bold
fixed font
[Key symbols] Keys are presented according to their representation on
Commands to be entered through the keyboard are
written in a semi-bold fixed font.
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.
Table 1: Notational conventions
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 RemoteView management
blade.
8 RemoteView 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
RemoteView 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.
RemoteView Management Blade 9
Blade Server Management BX Blade Server System Overview
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 RemoteView
management blade. There are two RemoteView management blades in a blade
server system, in order to ensure redundancy.
The user gets access to the functions provided by the RemoteView
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 RemoteView Management Blade
Within the blade server system the RemoteView management blade is
equipped with a number of features, which are described in this section.
Controller
The RemoteView management blade is equipped with a Qlogic Zircon V2
controller.
Supported programs
The RemoteView 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 RemoteView management blade communicates with the server blades via
2
an I
C 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.
10 RemoteView Management Blade
BX Blade Server System Overview Blade Server Management
Hardware monitoring
The hardware monitoring functions provided by the RemoteView 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 conditions
– Setting the the system fans to an optimum speed
– Monitoring the status ot the power supply modules
2
– Monitoring the temperature of the switch blades via the I
C bus
Event repository
To store messages on events that occur in the system environment, the
RemoteView management blade is equipped with an event repository, providing
a 16 KB access EEPROM.
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.
RemoteView Management Blade 11
Blade Server Management BX Blade Server System Overview
2.2.2 Redundancy of the RemoteView Management Blade
Of the two RemoteView 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 RemoteView
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 RemoteView 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 RemoteView management blade acts as the console redirection agent.
The KVM (Keyboard/Video/Mouse) input is captured and sent to the
RemoteView management blade. The RemoteView management blade will in
turn send this input to a server blade, where the appropriate actions will be
executed.
12 RemoteView Management Blade
BX Blade Server System Overview Blade Server Management
With the adv. KVM blade, advanced server management functions are
available, such as graphic mode console redirection and remote USB CD-ROM
and floppy disk emulation (PRIMERGY BX600 only).
RemoteView Management Blade 13
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 established 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.
RemoteView Management Blade 15
Entering the console mode Telnet interface
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.
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
16 RemoteView Management Blade
Telnet interface Console main menu
3.2 Console main menu
The console main menu looks like this:
Figure 3: Console main menu
There are seven items in the console main menu:
– Management Agent (see 3.3 on page 19)
This item provides several options for the management of the whole blade
server system, including management blades and switch blades.
– Emergency Management Port (see 3.4 on page 55)
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.
– Console Redirection (see 3.5 on page 57)
This item is used to configure the console redirection mode. The selected
console redirection target will be active after the next boot.
– TFTP Update (see 3.6 on page 59)
This item is used to update the management blade firmware.
RemoteView Management Blade 17
Console main menu Telnet interface
– Logout (see 3.7 on page 61)
This item is used to logout from the system.
– Reboot Management Blade (see 3.8 on page 61)
This item is used to perform a reboot of the system. The reboot is executed
immediately.
– System Information Dump (see 3.9 on page 62)
This item is used to display consecutive lists of information.
The items of the console main menu are described in more detail in the following
sections.
18 RemoteView Management Blade
Telnet interface Management Agent
3.3 Management Agent
The following items provided in the Management Agent sub-menu for server
management:
– Management Agent Information (see 3.3.1 on page 20)
– Management Blade (see 3.3.2 on page 24)
– System Information (see 3.3.3 on page 26)
– Server Blade (see 3.3.4 on page 28)
– Switch Blade (see 3.3.5 on page 35)
– Username And Password (see 3.3.6 on page 37)
– Blue Screen (see 3.3.7 on page 38)
– Event Log (see 3.3.8 on page 38)
– Set System Default (see 3.3.9 on page 41)
– Server Blade CMOS Backup/Restore (see 3.3.10 on page 43)
– Switch Blade Configuration Backup/Restore (see 3.3.11 on page 45)
– Deployment Parameter (see 3.3.12 on page 46)
– Power Consumption (see 3.3.13 on page 49)
– PPP and Modem Setting (see 3.3.14 on page 51)
RemoteView Management Blade 19
Management Agent Telnet interface
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
20 RemoteView Management Blade
Telnet interface Management Agent
These options are used to perform the following activities:
Option Description
Set Management Agent IP
Address
Set Management Agent Network
Mask
Configuration of the management blade IP
address.
Configuration of the management blade IP
network mask.
Set Management Agent Gateway Configuration of the management blade IP
gateway address.
Set Management Agent Default
Route
Set Management Agent DHCP
Configure
Configuration of the default route:
LAN or PPP.
Configuration of the auto-assigned IP
address mask and enabling of the
gateway via DHCP.
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 URL
Automatically Adjust Clock for
Daylight Saving Changes
Display of the home page URL for the
management blade.
Configuration of the adjustment for
daylight saving changes (enable/disable,
start date, end date). See also section
“Daylight Saving Time Format Example”
on page 82.
Agent HTTP Configuration of the HTTP settings,
including port number assignment, HTTP
protocol enabling/disabling and HTTP
SSL security control.
RemoteView Management Blade 21
Management Agent Telnet interface
Option Description
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 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.
22 RemoteView Management Blade
Telnet interface Management Agent
Option Description
Change Management Role To
Slave
Change the role of the master
management blade to slave
(only displayed if there are two
management blades installed).
RemoteView Management Blade 23
Management Agent Telnet interface
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 Displays the health status of the
management blade. A message will be
displayed if this status is disturbed.
Management Blade
Manufacture
24 RemoteView Management Blade
Displays the name of the manufacturer of
the management blade.
Telnet interface Management Agent
Parameter Description
Management Blade
Manufacture Date
Management Blade Serial
Number
Management Blade Product
Name
Management Blade Model
Name
Management Blade Hardware
Version
Management Blade Firmware
Version
Displays the date of manufacture for the
management blade.
Displays the serial number of the
management blade.
Displays the product name of the
management blade.
Displays the name of the management blade
model.
Displays the hardware version of the
management blade.
Displays the firmware version of the
management blade.
Management MAC Address Displays the NIC physical address of the
management blade.
RemoteView Management Blade 25
Management Agent Telnet interface
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:
Parameter Description
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.
26 RemoteView Management Blade
Telnet interface Management Agent
Parameter Description
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 temper-
ature, 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.
System KVM Specifies, which server blade should get
accessed via KVM.
System LED Control Displays the status of the system control: on,
off, or blinking.
NIC Status Detection Detect whether the network signal of the
management blade‘s NIC is ok or fail.
NIC Status Detection enable
If management blade NIC detection is
fail for the master and ok for the slave, the
master sends out an event log message
and the roles of the management blades
are changed. The role change takes
place after the NIC Detection Timeout
has expired.
NIC Status Deteiction disable
The NIC Status Detection is disabled.
Turn on/off all server blades Turns on or turns off all server blades.
RemoteView Management Blade 27
Management Agent Telnet interface
3.3.4 Server Blade
The Server Blade option provides information on the server blades, i. e. information on CPUs, memory modules, voltage, temperature, CMOS configuration
and watchdog timers.
The menu for this option looks like this:
Figure 7: Server Blade menu
3.3.4.1 Server Blade Control Information
This option enables the user to set the following parameters:
Parameter Description
Server Power Set server power:
(1) on
(2) off
(3) power-cycle
(4) reset
(5) NMI
(6) force off
28 RemoteView Management Blade
Telnet interface Management Agent
Parameter Description
Set Server Maximum
Restart Retries
Configuration of the maximum number for server
restart retries. If the failure count reaches this
value, the configured reaction will be executed.
Server LED Control Configuration of the LED control at the front of the
blade server: blinking or off.
Server CPU Mode Configuration of the CPU mode: battery or perfor-
mance mode. If the parameter is set to battery
mode, this will save electric power.
Server Administrative URL Configuration of an URL address for the server.
3.3.4.2 Server Blade Information
This option displays some information on the server blade parameters. The
following parameters are included:
Parameter Description
Server Blade Status Displays the server blade health status.
Server Blade Manufacture Displays server blade manufacture vendor infor-
mation.
Server Blade Manufacture
Date
Server Blade Serial
Displays server blade manufacture date information.
Displays server blade serial number information.
Number
Server Blade Product
Displays server blade product name information.
Name
Server Blade Product
Displays server blade product version information.
Version
Server Blade Model Name Displays server blade model name information.
Server Blade Hardware
Version
Server Blade BIOS
Displays server blade hardware version information.
Displays server blade BIOS version information.
Version
Number of CPU Socket Displays how many CPU sockets are available on
the server blade.
RemoteView Management Blade 29
Management Agent Telnet interface
Parameter Description
Number of Memory
Socket
ServerBlade OS Type Displays the OS platform currently running on the
ServerBlade OS Version Displays the version of the OS currently running
Server Blade BMC
Firmware Version
Server Blade PCI Add-In
Card
Server Blade FC Daughter
Card
3.3.4.3 ServerBlade CPU
This option displays some information on the server blade CPU parameters.
The following parameters are included:
Displays server blade memory information.
server blade.
on the server blade.
Displays server blade BMC firmware version.
Displays whether a PCI card is installed.
Displays whether a FC (Fibre Channel) daughter
card is installed (only relevant for BX600 Blade
Server Systems).
Parameter Description
CPU Type Displays the CPU type.
CPU Frequency Displays the CPU frequency.
CPU Step Displays the CPU stepping.
30 RemoteView Management Blade
Loading...