Developer Forums | About Us | Site Map
Search  
HOME > TUTORIALS > SERVER SIDE CODING > ADMINISTRATION TUTORIALS > PUTTING LINUX RELIABILITY TO THE TEST


Sponsors





Useful Lists

Web Host
site hosted by netplex

Online Manuals

Putting Linux reliability to the test
By Li Ge & Linda Scott & Mark VanderWiele - 2004-01-19 Page:  1 2 3 4 5 6

Test infrastructure

Hardware and software environment

Table 1 shows the hardware environment.

Table 1. Hardware environment

SystemProcessorsMemoryDiskSwap partitionNetwork
pSeries 650 (LPAR) Model 7038-6M2 2 - POWER4+(TM) 1.2GHz 8GB (8196MB) 36GB U320 IBM Ultrastar (other disks present, but unused) 1GB Ethernet controller: AMD PCnet32
pSeries 630 Model 7026-B80 2 - POWER3(TM)+ 375 MHz 8GB (7906MB) 16GB 1GB Ethernet controller: AMD PCnet32

The software environment was the same for both the pSeries 630 Model 7026-B80 and the pSeries 650 (LPAR) Model 7038-6M2. Table 2 shows the software environment.

Table 2. Software environment

ComponentVersion
Linux SuSE SLES 8 with Service Pack 1
Kernel 2.4.19-ul1-ppc64-SMP
LTP 20030514

Methodology

System stability and reliability are generally measured as continuous hours of operation and reliable uptime of a system.

The runs started with a set of 30-day baseline runs and progressed to 60- and 90-day Linux test runs on xSeries and pSeries servers. Initial emphasis was placed on kernel, networking, and I/O testing.



View Putting Linux reliability to the test Discussion

Page:  1 2 3 4 5 6 Next Page: Test tool

First published by IBM developerWorks


Copyright 2004-2017 GrindingGears.com. All rights reserved.
Article copyright and all rights retained by the author.