Installation guide

24 IBM Eserver xSeries 366 Technical Introduction
– System-independent installation eliminates the need to install service processor
drivers, helps save IT staff time, and reduces installation complexity.
򐂰 Remote diskette and CD-ROM drive support
– Enables remote booting and software loading of the server for application or operating
system installation and updates.
– Performs configuration remotely; helps save IT time and money by reducing on-site
presence and server downtime.
򐂰 Scriptable command-line interface and text-based serial console redirect
– Command-line interface supports program control of server management functions
using scripts.
– Serial text redirect provides access to text-mode BIOS and text-based system
consoles such as Linux, NetWare, and Windows EMS (Emergency Management
Services).
– Program control of text-based console using scripts.
– PPP support.
򐂰 User authentication and authority features
– User IDs, passwords, and login permission attributes can be stored in an LDAP server.
– Enhanced user authority levels set the access rights for users to match job
responsibilities for managing your xSeries servers.
– Secure Sockets Layer (SSL) encrypts the data transmitted between the LDAP server
and the Remote Supervisor Adapter II.
򐂰 Investment protection
– Integrates with IBM Director and Director Agent.
Operating system support
Table 4 on page 25 lists the supported operating systems for the x366 and the level of support
for Hyper-Threading technology provided by the operating system.
In the column titled Hyper-Threading:
򐂰
Yes indicates that the operating system recognizes the logical processors and can execute
threads on them but is not optimized for Hyper-Threading. From a licensing perspective, if
Hyper-Threading is enabled, the operating system must be licensed for twice the number
of physical processors to take full advantage of the processors’ capabilities.
򐂰
Optimized indicates that the operating system recognizes the logical processors and that
the operating system code has been designed to take full advantage of the technology.
For example, consider a server with two physical processors with Hyper-Threading
enabled (that is, four logical processors). If the operating system's scheduler is unaware of
Hyper-Threading (“Yes” in the Hyper-Threading column), it would treat all four logical
processors the same. As a result, if two processes are eligible to run, the scheduler might
put those processes on the two logical processors that are part of the one physical
processor. Thus, one physical CPU would be busy while the other CPU is idle, leading to
poor overall performance.
From a licensing perspective, the logical processors do not count toward the number of
processors for which an operating system is licensed.