Intel® Modular Server System MFSYS25,
Intel® Modular Server System MFSYS35,
Intel® Compute Module MFS5000SI
Tested Hardware and Operating System List
Enterprise Platforms and Services Division
Revision 1.9
March, 2009
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
Revision History
Revision
Date
November, 2007 1.0 Initial Release
January, 2008 1.1 Added support for Windows 2003 Server, clarified Virtualization Software
January 22 , 2008 1.2 Added Fujitsu 146GB 2.5” HDD
January 25 , 2008 1.3 Corrected 146BG FJ HDD – 10K instead of 15K drive
February 1, 008 1.4 Added SLES 10 64-bit Stress Testing and Novell Certification Status for
August, 2008 1.5
December, 2008 1.6
January 9, 2009 1.7
January 16,2009 1.8
March 2009 1.9
Number Modifications
testing/certification details
both 32 & 64-bit versions
Added VMware ESX Server 3.0.2 U1 GA Certification and Windows 2008
Server support. Updated USB Device list.
Updated OS support. Added initial MFSYS35 HDD information.
Corrected Hard Drive FW revisions in Table 5.2 Tested Hard Drives
Corrected Xyratec external array information, added note for 3.5” drives-
mixing of SAS and SATA not supported.
Updated Table 4.6 External Tape Drives and Table 5.2 Tested HDDs
Revision 1.9
ii
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
Disclaimers
THE INFORMATION IN THIS DOCUMENT IS PROVIDED "AS IS" WITH NO WARRANTIES WHATSOEVER,
INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY
WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE.
Information in this document is provided in connection with Intel
estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's
Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any
express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to
fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property
right. Intel products are not intended for use in medical, life saving, or life sustaining applications.
Intel retains the right to make changes to its test specifications at any time, without notice.
The hardware vendor remains solely responsible for the design, sale and functionality of its product, including any
liability arising from product infringement or product warranty.
Intel, the Intel logo, and EtherExpress are trademarks or registered trademarks of Intel Corporation or its subsidiaries
in the United States and other countries.
*Other names or brands may be claimed as the property of others.
®
products. No license, express or implied, by
Revision 1.9
iii
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
Table 4.2 Intel® Modular Server System MFSYS25 Supported Peripherals..............................17
Table 5.1 Tested Operating System Identifier Numbers.............................................................18
Table 5.2 Tested Hard Drives.....................................................................................................19
Revision 1.9
5
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
1. Introduction
This document is intended to provide users of the Intel® Modular Server System
MFSYS25/MFSYS35 and Intel® Compute Module MFS5000SI with a guide to the different
operating systems, expansion cards, and peripherals Intel plans to test on this platform.
This document will continue to be updated as new expansion cards, peripherals, and operating
systems are tested or until the Intel® Modular Server System MFSYS25/MFSYS35 and Intel®
Compute Module MFS5000SI are no longer in production. Each new release of the document
will present updated information as well as continue to provide the information from previous
releases.
Intel will only provide support for those expansion cards and peripherals under the specified
system configuration (System BIOS and Firmware revisions) and operating systems versions
with which they were tested.
1.1 Test Overview
Testing performed on the Intel® Modular Server System MFSYS25/MFSYS35 and Intel®
Compute Module MFS5000SI is classified under two separate categories: Basic Installation
Testing, and Expansion Card/ Peripheral Compatibility and Stress Testing.
1.1.1 Basic Installation Testing
Basic installation testing is performed with each supported operating system. Basic installation
testing validates that the server board can install the operating system and that the base
hardware feature set is functional. A small set of peripherals is used for installation purposes
only. No expansion cards are tested. Testing includes network connectivity and running of
proprietary and industry standard test suites.
The latest version of an operating system signifies the latest supported version
1.1.1.1 Support Commitment for Basic Installation Testing
Intel commits to provide the following level of customer support for operating systems that
receive only basic installation testing:
• Intel will provide and test operating system drivers for each of the server board’s
• Intel will support customer issues that involve installation and/or functionality of
at the time of the actual test run. Each new release of this document may have
a newly supported release of a given operating system. Previous releases of a
supported operating system may not be tested beyond the basic installation
test process.
integrated controllers, provided that the controller vendor has a driver available upon
request. Vendors will not be required by Intel to develop drivers for operating systems
that they do not already support. This may limit the functionality of certain server board
integrated controllers.
operating system with the server board’s integrated controllers only if a driver has been
made available.
Revision 1.9
6
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
•Intel will NOT provide support for issues related to use of any 3
rd
party expansion cards
or peripherals installed in the server system when an operating system that received
basic installation testing only is in use.
•Support is defined as assistance in root causing issues, and determining a customer
acceptable resolution to the issue associated with the operating system. The resolution
may include, but is not limited to on-board controller driver changes, engaging the
vendor for resolution, BIOS changes, firmware changes, or determining a customer
acceptable workaround for the issue.
1.1.2 I/O Expansion Card / Peripheral Compatibility and Stress Testing
I/O Expansion Card / Peripheral Compatibility and Stress testing is performed only on the most
current release of a supported operating system at the time of a given validation run. The I/O
Expansion Card / Peripheral Compatibility and Stress testing process consists of three areas:
Base Platform, I/O Expansion Card Compatibility, and Stress.
Base Platform: Each base platform will successfully install a given operating system,
successfully run a disk stress test, and successfully run a network stress test.
I/O Expansion Card Compatibility: I/O Expansion Card compatibility validation (CV) testing
uses test suites to gain an accurate view of how the server performs with the available
expansion card under the primary supported operating systems. These tests are designed to
show hardware compatibility between the cards and the server platform and include functional
testing only. No heavy stressing of the systems or the cards is performed for CV testing.
Stress Testing: This test sequence uses configurations that include expansion cards in all
available slots, for a minimum 72-hour test run without injecting errors. Each configuration
passes an installation test, a Network/Disk Stress test, and tape backup test. Any fatal errors
that occur will require a complete test restart.
1.1.2.1 Support Commitment for I/O Expansion Card / Peripheral Compatibility and
Stress Testing
Intel commits to provide the following level of customer support for operating systems that
receive I/O Expansion Card / Peripheral Compatibility and Stress testing:
Intel commits to provide the following level of customer support for operating systems that
receive I/O Expansion Card / Peripheral Compatibility and Stress testing:
•Intel will provide support for customer issues with these operating systems involving
installation and/or functionality of the server board with or without the I/O Expansion
Card and peripherals listed in this document as having been tested under the particular
operating system.
•Support is defined as assistance in root causing issues, and determining a customer
acceptable resolution to the issue associated with the operating system. The resolution
may include, but is not limited to on-board controller driver changes, engaging the
vendor for resolution, BIOS changes, firmware changes, or determining a customer
acceptable workaround for the issue.
•Intel will provide and test operating system drivers for each onboard video, network, and
storage controller.
Revision 1.9
7
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
•Intel will enable vendors to provide driver support for I/O Expansion Cards using these
operating systems.
•Intel will go through some of the steps to achieve certification to ensure its customers do
not run across any problems, but the actual certification is the responsibility of the
individual customer.
For operating systems, adapter cards, and peripherals not listed in this
document, there is no support commitment. Intel will consider support requests
on a case-by-case basis.
1.2 Pass/Fail Test Criteria
For each operating system, I/O Expansion card, and peripheral configuration, a test passes if
specific criteria are met. Specific configurations may have had particular characteristics that
were addressed on a case-by-case basis. In general, a configuration passes testing if the
following conditions are met:
The operating system installed without error.
- Manufacturer’s installation instructions or Intel’s best-known methods (BKMs) were
used for the operating system installation.
- In some cases rKVM BKMs used involve workarounds and were required during the
operating system installation.
- The server system behaved as expected during and after the operating system
installation.
- Application software installed and executed normally.
Hardware compatibility tests ran to completion without error.
Test software suites executed successfully
- Test and data files were created in the correct directories without error.
- Files copied from client to server and back compare to the original with zero errors
reported.
- Clients remain connected to the server system.
- Industry standard test suites run to completion with zero errors reported.
All Intel® Compute Module MFS5000SI testing was performed using the Intel® Server Modular
System MFSYS25 or the Intel® Server Modular System MFSYS35.
Revision 1.9
8
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
2. MFS5000SI / MFSYS25 / MFSYS35 Base System
Configurations
The following table lists the base system configurations tested. Base system configurations will
change as new revisions of the Intel® Compute Module MFS5000SI or the Intel® Modular
Server System MFSYS25/MFSYS35 are released and/or new system software stacks are cut
onto the boards in the factory. Each base system configuration is assigned an identifier number
that is referenced in the tables throughout this document. New base system configurations are
added with each new release of this document.
Intel will only provide support for I/O expansion cards and peripherals under the
The following table lists the base system configuration tested.
Table 2.1 Base System Configurations Tested
specified base system configuration and operating systems versions with which
they were tested.
Note: All base system configurations tested used the Intel® Compute Module MFS500SI
BIOS
Rev
BMC
FW Rev
Switch
Rev SCM Rev
Revision 1.9
9
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
r
Module MFS5000SI
3. Supported Operating Systems & Software
The following table provides a list of the operating systems and software applications that Intel
plans to test with the Intel® Compute Module MFS5000SI. Each of the listed operating systems
was tested for compatibility with the base system configuration listed in Section 2 of this
document. Operating systems are supported only with the specified base system
configuration(s) with which they were tested.
The following table also indicates whether each operating system received Basic Installation
Testing, or Adapter / Peripheral Compatibility and Stress Testing. For information on the
support commitments for Basic Installation Testing vs. Adapter / Peripheral Compatibility and
Stress Testing, please reference Section 1 of this document.
Any variations to the standard operating system installation processes are documented in the
Installation Guidelines section of this document. If no installation guidelines are noted in the
following table, then the operating system installed as expected using manufacturer’s
installation instructions or Intel’s best-known methods.
Operating systems supported by Intel® System Management Software may be
different than the operating systems supported by the Intel® Compute Module
MFS5000SI. Please reference the Readme and User Guide documents that
are included as part of the Intel System Management Software distribution fo
operating systems that are supported by that release.
Table 3.1 Operating Systems Tested
Operating System Type of Testing Notes
Intel’s testing was completed with
Microsoft Windows Server 2003
Microsoft Windows* 2003 Enterprise
(32-bit), R2 SP2
Microsoft Windows* 2003 Enterprise
(64-bit), R2 SP2
Configuration 1 - Compatibility
& Stress
Configuration 1 -Compatibility &
Stress
Enterprise R2 SP2, 32-bit. Although not
specifically tested on this product, the
MFS5000SI compute module also
supports Microsoft Windows Server
2003 R2, 32-bit.
Intel’s testing was completed with
Microsoft Windows Server 2003
Enterprise R2 SP2, 64-bit. Although not
specifically tested on this product, the
MFS5000SI compute module also
supports Microsoft Windows Server
2003 R2, 64-bit.
Microsoft Windows* 2008 Enterprise
(32-bit)
Microsoft Windows* 2008 Enterprise
(64-bit)
Red Hat Enterprise Linux AS 5.0 U1
(64-bit)
Red Hat Enterprise Linux AS 5.0
U1(32-bit)
Revision 1.9
10
Configuration 1 -Compatibility &
Stress
Configuration 1 -Compatibility &
Stress
Configuration 1 -Compatibility &
Stress
Configuration 1 Basic Installation
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
VMware ESX Server 3.5 Configuration 1 -Compatibility
VMware ESXi Server 3.5 Configuration 1 -Compatibility
Client Web Browsers (for CMM
interface)
Microsoft Internet Explorer 6.0 Configuration 1 -Compatibility
Microsoft Internet Explorer 7.0 Configuration 1 -Compatibility
Mozilla Firefox 2.0 Configuration 1 -Compatibility
Client Java Engines (for CMM
interface and remote KVM)
Sun Java Plugin 6.3 Configuration 1 -Compatibility Sun Java Plugin 6.3 or above
Configuration 1 - Basic
Installation, Compatibiltiy Only
Configuration 1 - Compatibility
& Stress
Type of Testing Notes
Type of Testing Notes
Operating system was tested and is
supported by SCO. In addition, this OS
is currently only supported in a sincle
SCM environment.
http://www.sco.com/chwp
Operating system was tested and is
supported by SCO. In addition, this OS
is currently only supported in a sincle
SCM environment.
http://www.sco.com/chwp
Client OS Type of Testing Notes
Microsoft Windows* XP
Professional, SP3
Microsoft Vista* Business (32-bit )
SP1
Red Hat Enterprise Linux 5.0
Desktop (32-bit)
Novell SuSe Linux Desktop 10.1 (32bit)
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
3.1 Operating System Certifications
Listed below are the operating systems that Intel plans to certify with the Intel® Compute
Module MFS5000SI. However, the customer is responsible for their own certification from the
individual operating system vendors. In many cases, the customer may leverage their operating
system certifications from Intel’s testing. See the “Comments” section next to each operating
system in the table below for additional information. Intel’s certifications, pre-certification, and
operating system testing may help reduce some of the risk in achieving customer certifications
with the operating system vendors.
Table 3.2 Operating System Certifications
Operating System Certification Listing Comments
®
Intel
Modular Server
Microsoft Windows* 2003
Enterprise Server (32 & 64-bit )
Microsoft Windows* 2008
Enterprise Server (32 & 64-bit )
System MFSYS25/
MFS5000SI
SID# 1270300
®
Intel
Modular Server
System MFSYS25/
MFS5000SI
SID# 129928
Certification available at launch. OEM must request
certification by Microsoft for their specific product.
Certification available.
OEM must request certification by Microsoft for their specific
product.
Certification available at launch.
®
Intel
Red Hat* Enterprise Linux
Adavanced Server 5.0 (32 &
64-bit)
SuSE Linux Enterprise Server
10 (32 & 64-bit), SP1
Red Hat checks Intel’s results, certifies (if appropriate), and
posts the certificate on their web site. Customer can
leverage the Intel certification, if customer product meets the
operating system vendor standard.
Not Supported Not Supported
Not Supported Not Supported
Not Supported Not Supported
Not Supported Not Supported
Not Supported Not Supported
Not Supported Not Supported
Shared LUN
Dual SCM
Revision 1.9
13
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
4. I/O Expansion Cards & Peripherals
I/O Expansion card and peripheral compatibility and stress testing will only be performed with
the latest version of an operating system at the time the validation testing occurred. The
following table shows the operating system and base system configurations used to validate
each device. The expansion cards and peripherals are divided into categories based on their
functionality. All integrated on-board devices are tested by default and are therefore not
included in the following tables.
Note that not all expansion cards or peripherals were tested under all operating systems. The
following notation is used in the tested adapters and peripherals table below to indicate the
support level that Intel provides for a particular adapter under a particular operating system:
This expansion card or peripheral has been tested and is supported under the specific
Number (i.e. 1)
Number in brackets (i.e. [1])
configuration identified in the Base System Configurations Table in Section 2 of this
document.
This expansion card or peripheral has been tested, but is NOT supported under the
specific configuration identified in the Base System Configurations Table in Section 2
of this document.
NT
ND
SD (Similar Device)
This expansion card or peripheral has not been tested under this operating system
and is not supported under this operating system.
This expansion card or peripheral has not been tested under this operating system
due to limitations in IHV driver availability, and is not suported under this operating
system.
This expansion card/peripheral is supported, but not tested. This expansion
card/peripheral model has not been tested with this server board, but Intel will support
it based on successful testing of a similar expansion card/peripheral from the same
family. Intel has high confidence that this expansion card/peripheral will function
correctly with the server board. This expansion card/peripheral uses the same
firmware and drivers, and has a nearly identical system interface to another
expansion card/peripheral of the same family that has been successfully tested with
this server board. In addition, Intel has secured IHV commitment to support the
similar expansion card/peripheral equally. Customers should always test expansion
card/peripheral as part of the final system configuration prior to deployment. All
installation guidelines for the tested expansion card/peripheral also apply to the
similar device.
Any variations to the standard adapter installation process or to expected adapter functionality
are documented in the Installation Guidelines section of this document. If there are installation
guidelines affecting a particular expansion card/peripheral and operating system combination,
these are referenced in the following table. If there are no installation guidelines noted in the
following table, then the expansion card/peripheral installed and functioned as expected using
manufacturer’s installation instructions or Intel’s best-known methods.
Revision 1.9
14
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
bit, 64-bit), SP2
2003 Enterprise (32-
Manufacturer Model Name Model Number Interface
TEAC USB Floppy FD-05-PUB USB 1 1 1 1
NEC USB Floppy UF0002 USB 1 1 1 1
IOMega
Lexar USB Keyfob
Lexar USB Keyfob
SanDisk USB Keyfob
SanDisk USB Keyfob
IOMega USB Optical Drive
Liteon USB Optical Drive SHM-165P6SX USB 1 1 1 1
Liteon USB Optical Drive SOSW-1673SU USB 1 1 1 1
USB Storage
Drive
80GB Silver
Portable
USB Jumpdrive
1GB
USB Jumpdrive
2GB
USB Cruzer
Micro 1GB
USB Cruzer mini
2GB
DVD R/W
(Super 16xU2)
USB 1 1 1 1
USB 1 1 1 1
USB SD SD SD SD
USB 1 1 1 1
USB 1 1 1 1
USB 1 1 1 1
Microsoft Windows*
bit, 64-bit)
Microsoft Windows
2008 Enterprise (32-
bit, 64-bit)
SuSE Linux
Red Hat Enterprise
Linux AS 5.0 U1 (32-
U1 (32-bit, 64-bit),
Enterprise Server 10
Comments
Liteon USB Optical Drive DX-20A4H USB 1 1 1 1
Sony USB Optical Drive DRX-830UL-G USB 1 1 1 1
Sony USB Optical Drive DRX-840U USB 1 1 1 1
HP USB Optical Drive DVD1040E USB 1 1 1 1
Revision 1.9
16
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
Table 4.2 Intel® Modular Server System MFSYS25 Supported Peripherals
Manufacturer Model Name Model Number Interface
4.4 Ethernet Switch Modules
Intel
Intel® Gigabit
Ethernet Switch
AXXSW1GBS
Gbit
Ethernet
4.5 Storage Controller Modules
Intel® Storage
Intel
Controller
AXXSCM3SS SAS 1 1 1 1
Module
4.6 External Tape Drives
Quantum
Quantum LTO-3
HH
LTO-3 HH SAS
LTO
Drive
4.7 External Storage
bit, 64-bit), SP2
2003 Enterprise (32-
Microsoft Windows*
Microsoft Windows
2008 Enterprise (32-
bit, 64-bit)
bit, 64-bit)
SuSE Linux
Red Hat Enterprise
Linux AS 5.0 U1 (32-
U1 (32-bit, 64-bit),
Enterprise Server 10
Comments
1 1 1 1
Tested by vendor.
Intel tested with the
following
configurations:
1 1 1 1
Windows 2003*
with Symantec
Backup Exec 11 &
Windows 2008*
with Symantec
Backup Exec 12
Promise VTrak E310sS VTE310sS SAS 1 1 1 1
Promise VTrak E310sD VTE310sD SAS 1 1 NT 1
Promise VTrak E610sS VTE610sS SAS 1 1 1 1
Promise VTrak E610sD VTE610sD SAS 1 1 NT 1
Single storage
controller
Dual storage
controller
Single storage
controller
Dual storage
controller
Intel® Storage
Intel
Server
SSR212MC2 NAS 1 1 1 1
SSR212MC2
Intel® Storage
Intel
Server
SSR212PP GbE 1 1 1 1
SSR212PP
SVPM v2.4 or
Xyratex Xyratex E5412E E5412E SAS
See
comment
See
comment
See
comment
See
comment
above. Supported
by vendor in single
SCM configuration
Revision 1.9
17
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
5. Hard Disk Drives
The hard drives listed in the following table have been tested with the Intel® Modular Server
System MFSYS25 / MFSYS35 by Intel validation labs and/or by individual drive vendors. The
following operating system identifiers are used in the table to specify which operating system
each drive was tested under.
Table 5.1 Tested Operating System Identifier Numbers
Identifier Number Operating System
1 Microsoft Windows* 2003 Enterprise (32-bit), R2 SP2
2 Microsoft Windows* 2003 Enterprise (64-bit), R2 SP2
3 Red Hat Enterprise Linux AS 5.0 U164-bit)
4 SuSE Linux Enterprise Server 10 U1(32-bit),
5 SuSE Linux Enterprise Server 10 U1(64-bit),
6 Microsoft Windows 2008 Enterprise (64-bit)
7 Red Hat Enterprise Linux AS 5.0 U1(32-bit)
Not all hard drives were tested under all operating systems. The following notation is used in
the tested hard drives table below to indicate the support level that Intel provides for a particular
hard drive with a particular operating system:
Number (i.e. 1)
Number in brackets (i.e. [1])
SD (Similar Drive)
This hard drive has been tested and is supported under the operating system
identified by the operating system identification number.
This hard drive has been tested, but is NOT supported under the operating system
identified by the operating system identification number.
The hard disk drive is supported, but not tested. This hard drive model/capacity has
not been tested with this server board, but Intel will support it based on successful
testing of a larger capacity hard drive from the same hard drive family. Intel has high
confidence that this hard drive will function correctly with the server board. This drive
uses the exact same firmware and drivers as a larger capacity hard drive that has
been successfully tested with this server board. The only difference between this
drive and the one that was used in testing is the storage capacity. Intel provides the
same level of support for all hard drives listed in this document, regardless of whether
the drive was tested or not. Customers should always test hard drives as part of the
final system configuration prior to deployment. Given the fact that a larger capacity
hard drive from the same drive family has successfully completed testing on this
server board, this particular hard drive capacity point will not be tested.
The hard disk drive was tested according to Intel-approved guidelines and test
IHVT (IHV Tested)
Revision 1.9
18
procedures by the Independent Hardware Vendor (IHV) that manufactured the drive.
Intel provides the same level of support for all hard drives listed in this document,
regardless of whether the drive was tested in an Intel lab or not. IHV test reports
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
Number (i.e. 1)
This hard drive has been tested and is supported under the operating system
identified by the operating system identification number.
remain the property of the IHV (Intel cannot provide copies of these reports).
(a) Firmware revisions listed in this column are the minimum revision levels supported. As they become available,
listed drives with newer revisions of firmware are also supported. OEM specific versions of drive firmware are not
supported. Mixed firmware levels within the same storage pool is not supported.
(b) MFSYS35 currently does not support a mix of SAS and SATA drives within the same chassis. All drives within the
MFSYS35 subsystem must have the same interface.
Revision 1.9
19
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
6. Installation Guidelines
6.1 Slipstreamed install for Windows 2003 Enterprise Edition (32 &
64 bit)
Method for performing Slipstreamed install for Windows 2003 Installation via
CD-ROM drive. Both the CD-ROM and Floppy can not be simultaneously
redirected on the MFSYS25 system.
Implication:
Guideline: To create a merged Windows 2003 CD perform the following:
Status: Intel has no plans to add support for concurrent Remote Floppy and Remote
The MFS500SI compute module will only support remote installation of the
Windows 2003 Enterprise Edition R2 SP2 slipstreamed version. Local installation
can be performed by either concurrent CD/floppy installation or via slipstreamed
installation CD.
For remote install the LSI SAS driver must be slipstreamed into the installation
media as both CD-ROM and Floppy can’t be simultaneously redirected.
1. Download and install the freeware program nLite from
(http://www.nliteos.com/index.html)
2. Launch nLite
3. Select language desired and hit next
4. On the next screen browse to the location of the Windows 2003 CD
5. nLite will prompt for a location to copy the CD to for modification (C:\temp),
it’ll then copy the install CD to that folder
6. When the copy completes, hit next
7. Hit next on the presets screen
8. On the next screen, select “Integrate -> Drivers” and “Create -> Bootable
ISO”, hit Next.
9. Download and extract the 1.25.5 driver for the appropriate version of the OS
(32-bit or 64-bit) and extract to a known location
10. Hit the Insert tab in the bottom left (single driver), browse to the location with
the driver and select the “lsi_sas.inf”
11. Select “Textmode driver”, click on the description in the box, and hit OK
12. Hit Next to begin the process
13. When the process completes, hit next to bring up the Bootable ISO screen
14. Select the appropriate options for your system and hit “burn” to create the
CD
15. When finished, the CD is ready for remote installation with no requirement
for a driver floppy
CD/DVD.
Revision 1.9
20
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
Method for performing Remote Windows 2003 Installation via CD-ROM drive.
Guideline: Note: Prepare a Slipstreamed CD per section 6.1.
1. Plug your slipstreamed CD of your Windows operating system CD-ROM into
the CD on your remote system.
2. Log in to the Modular Server and select the Storage Tab at the top.
3. If you have not already done so create a storage Pool and select it.
4. Select the Create Virtual Drive option under Actions.
5. Enter a Name for the Virtual Disk.
6. Select a Raid Level appropriate for your application. The Raid levels that are
available will be dependant on the number of drives used to create the
storage pool.
7. Enter the size in GB for the virtual disk.
8. Select the Server that the virtual disk will be assigned
9. Select the Drive # for the virtual disk. For loading an operating system on a
boot drive set the value to 0(boot device).
Revision 1.9
21
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
10. Confirm all your settings then Hit Apply. Hit OK when the confirmation dialog
is displayed.
11. With the mouse, select the Chassis Front Tab.
12. Click on Server 1 on the Chassis picture with the Mouse.
13. Click on the Remote KVM & CD option under Server 1 Actions.
14. Select the video display color resolution.
Revision 1.9
22
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
15. Choose the Device Menu Option and then click on the CDROM check box.
16. Choose the Redirect CDROM drive to select the CDROM on your system as
the device to load the operating system from.
17. Choose the drive letter of the CDROM to redirect the CD.
Revision 1.9
23
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
18. Return to the Modular Server screen and select the Chassis Front TAB. Do
not close out the KVM screen.
19. Select Server 1 and then hit the Power On option under “Server 1” Actions.
20. Select OK when requested to power on Server 1.
21. Return to the KVM screen and observer the bootup screen.
22. Continue with Windows setup following the directions for the operating
installation.
Revision 1.9
24
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
6.3 Red Hat Enterprise Linux 5.0 (32 & 64 bit) Remote Installation
Method
Method for performing Remote Red Hat Enterprise Linux 5.0 Installation with DVD
media via FTP
Guideline: Configure the MFSYS25 system as follows:
1. Ensure P2.0.5 or later SW stack is loaded
2. Management Module, Ethernet Switch (Ext 1 port and the compute
module’s ports in default vlan 1 setup) and client (desktop/laptop) in
the same network
3. Client requires DVD unit installed direct or via USB port
4. Disable client’s Firewall
5. Download and install Filezilla-Server application on the client. Application can
be downloaded from
6. When Filezilla Server is installed onto the client there will be a dialog popup
7. Click OK with the default listing
http://www.filezilla-project.org. Version test: 0-9.24
8. The Filezilla session should indicate “Logged on”
9. From Filezilla Server session, Click Edit
10. Select Users - The Users dialog pops up
11. Click “Add”. A popup will appear - enter anonymous in the first field (user
account). Accept default of <none> for second field then click OK.
Revision 1.9
25
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
12. From Filezilla server session click “Shared Folders”, then click “Add”, navigate
down and select the client’s DVD’s unit drive-letter, in the example case below
it was E,then click OK.
13. To verify your FTP setup is correct:
Open client’s CMD prompt window and type:
C:> ftp localhost
Revision 1.9
26
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
User: anonymous
Password: (just hit enter key)
ftp> dir
14. You should see the whole directory tree of the RHEL-5 DVD media you are
trying to install from
15. The Filezilla FTP server is now setup and ready to use
16. Log in CMM-GUI
17. Create a Storage Pool and Virtual Drive
18. Assign to a compute module as LUN 0
19. Via GUI select the compute module’s Remote KVM session and select CDROM Redirection and map to the DVD-drive-letter (x) on client
20. Power on the compute module via GUI
21. When presented with Red Hat Boot Option table, hit F2 then type following at
the boot prompt:
linux text askmethod
Revision 1.9
27
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
or
hit F2 then type same command there.
Revision 1.9
28
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
22. When asked for Installation Method - Select FTP then click OK
23. When asked for Networking Device - Select (hi-lite) eth0 as your main
interface then click OK (Use TAB key to move around)
24. When presented dialog Configure TCP/IP - Select IPv4 and deselect IPv6 and
OK
25. On the RedHat’s FTP Setup page, enter as:
FTP site name: x.x.x.x (your client IP)
RH Enterprise Linux Server Directory: /
Revision 1.9
29
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
26. Select DHCP mode when asked for network configuration for Eth0 and Eth1
Revision 1.9
30
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
6.4 SuSE Linux Enterprise Server 10 (32 & 64 bit) Remote
Installation Method
Method for performing SuSE Linux Enterprise Server 10 Installation via SMB
Guideline: Configure the MFSYS25 system as follows:
1. Ensure P2.0.5 or later SW stack is loaded
2. Management Module, Ethernet Switch (1 port and with compute module
ports in default vlan 1 setup) and client (desktop/laptop) in same network
3. Client requires DVD unit installed direct or via USB port
4. Disable client’s Firewall
5. Share the client’s DVD-unit with “all read/write permissions”
6. Log into CMM and via GUI create a Storage Pool and Virtual Drive and
assign it to the compute module as LUN 0.
7. Via GUI select the compute module’s Remote KVM session and select CDROM Redirection and map to the DVD-drive-letter (E) on client
8. Select Video color resolution = High
9. Power on the compute module via the GUI
Revision 1.9
31
Intel® Modular Server System MFSYS25, Intel® Modular Server System MFSYS35, Intel® Compute
Module MFS5000SI
10. When server boots to the option table, use down-arrow key to select
second option from the given list “Installation” then type (Boot Options line):
install=smb://x.x.x.x/drive-letter
where:
x.x.x.x : your client’s IP
drive-letter : the client’s DVD unit drive letter assigned by OS (in
example it is E)
11. The installation process will result in a reboot in about 25 minutes
12. The whole SLES installation will finish in about 45 minutes
Revision 1.9
32
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.