as of Jan 17th, 2005
Express5800/120Ba-4
Distribution Red Hat Enterprise Linux ES Ver3 Update2
(KERNEL 2.4.21-15.ELsmp)

The following letters given to evaluation results stand for:
'A'---operational on the distributed OS
'B'---operational with update driver applied to the distributed OS
'C'---not operational
'D'---not supported
Installation in standard composition / CPU additionMemory addition
/ LAN additionHDD additionEthernet Bonding

Installation in standard composition Top

No. Model/Device Code qty Result Evaluation
1 Express5800/120Ba-4
Xeon 3.20DGHz/memory-less)
N8400-021 1 A Installation using DeploymentManagerLite OK.(*1)
Keyboard and Mouse recognizable/operational
Built-in LAN recognizable/operational
CPU Hyper-Threading/SMP operational
2 73.2GB HDD(SCSI) N8450-007 1
3 1GB Memory Module N8402-011 1
4 Keyboard(USB) N8870-001 1
5 Mouse (USB/two buttons) N8870-010 1
6
Blade Server Assemble Unit N8405-013 1

(*1)
Installation using DeploymentManagerLite ( DPM ).
Refer to manual of DPM and kickstart for details.

- Download

  1. Download a archive ( filename: DPM_120Ba-4_RHES3U2.zip ) from [HERE] and extract it to get 'ks.cfg' and 'syslinux.cfg'.

- Setting up network servers

  1. Set up DHCP server for the Bladeserver to get IP address via network.
  2. Set up NFS server to export '/exports/CD' folder. And copy all included in Red Hat Linux installation CDs there.
    *This location is specified in 'ks.cfg'.
  3. Set up NFS server to export '/exports/KS' folder. And set 'ks.cfg' there.
    *This location is specified in 'syslinux.cfg'.
  4. Customise 'ks.cfg' according to your environment. At least, you must set up the following item
    • IP address of NFS server.
    • Root passward.
    • Partitions of HDDs. Set up with 'sda','sdb',... as scsi drives, 'hda',hdb',... as IDE drives.
    • Packages you plan to install.
    * For details, refer to Red Hat Linux documentation about kickstart.
    * 'ks.cfg' dose not approve anything except 'LF' as newline-code. Take care some meddlesome editor would automatically insert 'CR+LF'.

- Setting up DPM server (* See the documentation about DPM for details.)

  1. Connect DPM server, NFS server, DHCP server and the Bladeserver to the same network segment.
  2. Install DPM in a Windows from the EXPRESSBUILDER CDROM.
  3. Make folder "C:¥Program Files¥NEC¥DeploymentManager¥PXE¥Images¥pxelinux¥RHES3" And Copy files 'vmlinuz' and 'initrd.img' from 'images/pxeboot' folder in Red Hat instration CD1 there.
    * These location are specified in 'syslinux.cfg'.
  4. Copy syslinux.cfg to C:¥Deploy¥AnsFile¥Linux¥.
    * If you install optional LAN adapter, you may need to append kernel parameter 'ksdevise=eth1' to /etc/grub.conf according to the order of ether intarfaces.
  5. Start DPM software and make scenario-file for installation.
  6. Registar the Bladeserver into the DPM server.

- Execution of the scenario

Execute the scenario on DPM and installation start automatically.

CPU addition Top

No. Model/Device Code qty Result Evaluation
1 CPU Kit N8401-010 1 A Hyper-Threading, smp operational

Memory Addition Top

No. Model/Devic Code qty Result Evaluation
1 512MB Memory Module N8402-010 1 A Capacity recognizable/operational
2
1GB Memory Module N8402-011 1 A Capacity recognizable/operational
3
2GB Memory Module N8402-012 1 A Capacity recognizable/operational

LAN addition Top

No. Model/Devic Code qty Result Evaluation
1 1000BASE-T N8403-013 1 A Confirmed by telnet and ftp.

HDD addition Top

No. Model/Devic Code qty Result Evaluation
1 73.2GB HDD N8450-007 1
A Connected with built-in SCSI controller.
Confirmed by writing and reading data.
2 146.5GB HDD N8450-008 1
A Connected with built-in SCSI controller.
Confirmed by writing and reading data.

Ethernet Bonding Top
  Confirmed ethernet bonding function using OS standard Bonding driver

No. Evaluation Code qty Result Evaluation
FT LB
1 Onboard(1000BASE-T) standard equipment 2 A - Confirmed fault tolerance function.(*2)
It is necessary to test performance of load balancing on your own system.
(*2)
Confirmed refer to the following kernel source documentation
/usr/src/linux-2.4/Documentation/networking/bonding.txt
go back Top