theguard! ApplicationManager System Linux Data Collector

Transcription

1 theguard! ApplicatinManager System Linux Data Cllectr Status: June 20, 2007

2 Table f Cntents Intrductin...3 The Perfrmance Features f the ApplicatinManager Data Cllectr fr Linux...4 Overview f the Linux Operating System...5 Linux Applicatins...6 Using the Linux System...7 The basic tasks f the Linux perating system are:...7 Ntes t the Linux Operating System...9 The System Linux Data Cllectr...10 Mnitring Hardware and Sftware Resurces...11 Hst - Infrmatin abut the Hardware view f the System...12 Disk - Infrmatin abut the Mnitring f Hard Disks...12 Partitin - Infrmatin and Mnitring f single partitins f a hard disk...14 Prcessr - Infrmatin abut the Available Prcessrs...15 OS - Infrmatin abut the Sftware f the System...16 CPU Mnitring the Prcessrs Wrking in the System...19 FileSystem - Infrmatin abut Mnitring the File Systems...20 Prcess Grups - Infrmatin and Mnitring f Prcesses and/r their Grupings...21 Standard Reprting and Service Level Analysis...22 Case Study f a Mnitred System...23 Availability and Platfrms...25 Cpyright REALTECH 2007 Page 2 f 25

3 Intrductin There's mre t efficient applicatin management than maximizing availability. Targeted tuning can increase the perfrmance and stability f business-critical applicatins withut having t invest in additinal hardware (prcessrs, RAM, disk space). A number f data cllectrs have been develped fr theguard! ApplicatinManager that prvide cmprehensive mnitring and generate detailed data analyses. Data cllectrs d mre than simply cllect events accrding t pre-defined rules. They deliver every perfrmance value and the current status f each applicatin bject in real time. They als prvide insight int cnfiguratin attributes, such as the release status r the applicatin's parameter settings. Data cllectrs mdel an applicatin in bjects and sub-bjects, enabling a dedicated handling f alerts, mnitring, reprting, service level management, r status messages. This mdel ensures that infrmatin is clearly structured and that messages are easy t allcate t a prblem. Pre-defined and reusable plicies fr each type f applicatin facilitate the implementatin f the slutin and the adaptatin f mnitring t dynamic landscapes. The ease with which threshlds are set ensures the early recgnitin f ptential errrs. Cmprehensive reactin management enables flexible alerting fr mre than 100 different devices and alarm cnsles. The autmatic discvery f new applicatin instances and bjects, including the autmatic allcatin f plicies, enables autmatic mnitring even in thse cases in which system administratrs have cmpletely recnfigured the applicatin, fr example, by adding new instances r bjects. Central reprting at the applicatin instance and applicatin bject level prvides fr a detailed and effective capacity management f all resurces. Integrated Service Level Management ensures that the service levels fr applicatin availability and perfrmance are achieved, while Operatinal Level Agreements (OLAs) can be easily defined at the applicatin bject level. Cpyright REALTECH 2007 Page 3 f 25

4 The Perfrmance Features f the ApplicatinManager Data Cllectr fr Linux The perating system, its cmpnents and their reliability, availability, and usability, in shrt the system's verall "availability," is the basis f a prperly functining server. Cmpanies generally run their business-critical applicatins n ne r mre servers. These servers must functin prperly t ensure the availability f the applicatins. Technical prblems result in failures. Defects r insufficient system resurces, such as a faulty CPU and r faulty hard drives, insufficient swap space etc., result in prcessing bttlenecks. Failures and/r bttlenecks can render applicatins unmanageable and incur high csts. The perating system data cllectr hereafter referred t as OS DC enables a cmprehensive mnitring f a live server running a Linux perating system. With the OS DC, a number f perating system parameters, such as prcesses and prcess grups, running n a server can be mnitred in parallel and cmpared t each ther. All f a server's imprtant hardware and sftware resurces, such as prcessrs, memry, virtual memry, file systems, prcesses, etc. are defined and analyzed individually within the framewrk f the CIM mdel as Managed Objects (MOs). This structures the infrmatin and enables the plicies and reactins t be cntrlled individually. With ApplicatinManager's event and threshld mnitring resurce, bttlenecks, and system verlads can be detected and reprted at an early stage. Tgether with tw ther data cllectrs, File Parser DC: Custm DC: Cnfiguratin file and security-related system file management User-defined system bject mnitring OS DC prvides the best security fr yur system. Administratrs and/r ther authrized users can access a machine by simply clicking n the managed nde. The Applicatin Launcher functin, which is integrated in the interface, enables the cntext-based cnfiguratin f a detail analysis applicatin, in this case a Telnet sessin. The OS DC is a pwerful applicatin that cnsists f a number f bjects, event categries, and perfrmance cunters. All f the infrmatin is described in the data cllectr's nline dcumentatin. This dcument prvides an verview f the mst imprtant functins. Cpyright REALTECH 2007 Page 4 f 25

5 Overview f the Linux Operating System Linux - r even GNU/Linux - is a free perating system that is similar t UNIX. It is a multi-platfrm and multiuser perating system fr e.g. x86, PwerPC, Sparc etc.. Linux was utilized the first time in 1991 with the GNU- GPL licensing f the Linux kernel (see belw). The perating system, cnsisting f several parts, is develped by sftware develpers wrking n the varius prjects wrld-wide. Enterprises, nn-prfit rganizatins, as well as enthusiastic individuals are invlved. Fr the practical use, mstly s-called Linux distributins are available bundling varius sftware t a ready-t-use packet. The scpe f applicatin f Linux is diverse and includes the usage n desktp cmputers, servers, mbile phnes, ruters, multimedia end devices and super cmputers. 1 Figure 1: Brief histry f UNIX (Surce: The UNIX perating system was cnceived and implemented in the 1960s and first released in Its wide availability and prtability meant that it was widely adpted, cpied and mdified by academic institutins and businesses, with its design being influential n authrs f ther systems. The GNU Prject, with the gal f creating a Unix-like, POSIX-cmpatible perating system cmpsed entirely f free sftware, had begun develpment in 1984, and a year later Richard Stallman had created the Free Sftware Fundatin and wrte the first draft f the GNU General Public License (GPLv1). 1 Surce: Cpyright REALTECH 2007 Page 5 f 25

6 By the early 1990s, the prject had prduced r cllected many necessary perating system cmpnents, including libraries, cmpilers, text editrs, and a UNIX shell, and the upper level culd be supplied by the X Windw System, but develpment f the lwer level, which cnsisted f a kernel, device drivers and daemns had stalled and was incmplete. MINIX, a Unix-like system intended fr academic use, was released by Andrew S. Tanenbaum in While surce cde fr the system was available, mdificatin and redistributin were restricted. In additin, MINIX's 16-bit design was nt well adapted t the increasingly cheap and ppular Intel 386 architecture fr persnal cmputers. In 1991, Linus Trvalds began t wrk n a nn-cmmercial replacement fr MINIX while he was attending the University f Helsinki. This eventually became the Linux kernel. Trvalds intended Linux t be specifically tailred t the capabilities f the 32-bit Intel 386 platfrm. Linux was dependent n the MINIX userspace at first. With cde frm the GNU system freely available, it was advantageus if this culd be used with the fledgeling OS. Cde licensed under the GNU GPL can be used in ther prjects, s lng as they t are released under the GPL. In rder t make the Linux kernel cmpatible with the cmpnents frm the GNU prject, Trvalds changed his riginal license (which prhibited cmmercial redistributin) t the GPLv2. Linux and GNU develpers wrked t integrate GNU cmpnents with Linux. Thus Linux became a cmplete, fully functinal free perating system. Linux Applicatins Mst business-critical applicatins are client/server applicatins (2, 3 r 4-tier). The applicatin server prcesses (hereafter referred t as applicatin prcesses) run n Linux, while the client interface is either a brwser r a Windws applicatin n a frnt-end PC. Applicatins cnsist f several applicatin prcesses that may even cmmunicate with each ther beynd the cmputer's bundaries. The services f these prcesses, which are started by a system user, must always be highly available and highly perfrming t respnd t client requests as best as pssible. Figure 2: Multi-user and multiprcess system (schematic) Cpyright REALTECH 2007 Page 6 f 25

7 Using the Linux System Each user wh lgs in t a Linux system pens a s-called shell, the envirnment in which the users' cmmands are interpreted and executed. General structure The perating system is the interface between the hardware and the user and/r the applicatins. Figure 3: General structure f Linux The hardware is the basis. The hardware mainly cnsists f the memry, where the prcesses are stred during their executin (swapping is als an ptin), the CPU's central cmputing unit, the hard disks n which the files and prgrams are permanently stred, and the netwrk that cnnects yur cmputer t ther cmputers. The Linux perating system runs n the hardware. Its main task is t cntrl and manage the hardware and prvide all f the prgrams with a standard system call interface. The system calls, which nly run in kernel mde, enable user prgrams, prcesses, files, and ther resurces t be generated and managed. The basic tasks f the Linux perating system are: Prcess Management Lad, start, interrupt, and end prcesses. Allcate prcessr time t prcesses (scheduling). Synchrnize the wrklad distributin n multiprcessr machines. Memry Management Allcate, manage, and release memry t prcesses. Mnitr and prtect the memry frm ther prcesses accessing it. Temprarily mve prcesses (swapping) t mass strage devices. Cpyright REALTECH 2007 Page 7 f 25

8 Device and file management, and I/O cntrl Organize and manage the data n the mass strage devices in a hierarchical file structure. Manage access permissins t the file system. Efficiently allcate I/O devices and switching units (data channels, cntrl units) t prevent cnflicts. Initialize and mnitr the executin, schedule I/O prcesses, cnvert data, and lgically cntrl the file system. Manage cmputer resurces such as terminals, mass strage devices, I/O prts, the netwrk, etc. Transfer cmmn read/write peratins t device-specific cntrl signals. Crdinate cncurrent accesses t I/O resurces. Authenticatin and Access Cntrl Manage users and their access permissins t system resurces. Lg users in t and ut f the system. Prtect system resurces frm users that d nt have the crrect permissins. Lg Prcessing and Errr Handling Recrd imprtant functins and events such as errr statuses in the system lg. Recgnize errr statuses and prcess them accrdingly. User Interfaces The shell and additinal/ther service prgrams, amng ther things, administratin prgrams. Text-based (cnsle) and graphical user interface fr cmmunicatin between man and machine. Cpyright REALTECH 2007 Page 8 f 25

9 Ntes t the Linux Operating System The prbably mst characteristic feature with Linux is its freedm and publicity; means the cmplete surce cde f the perating system is free and freely available and therefre can be mdified and extended at will. As a result f this, wrld-wide varius creatrs and distributrs came int being like e.g. Debian, SuSE- Nvell and Red Hat that, in each case, prvide their wn distributins (sftware packages) t the user. Mrever, this can be seen as the basis fr a decisive criticism because, thrugh the variety f distributrs and versins that came int being, the basic idea f a standardizatin f Linux with it cnstantly mves t the distance. With the intrductin f kernel 2.6 a lt f imprvements, cncerning perfrmance and resurce handling, flew int the kernel. A simple example, which the user can directly see, when using the cmmands ps and tp, is the internal handling f prcesses and their display. The previus kernels had a display prblem, based n special internal prcess scheduling strategies; this means that a prcess especially prcesses with a lt f threats culd nt be identified at first glance. A prcess was always displayed with its pssible threads, what appeared as that an applicatin has been started several times. With kernel 2.6 it cmes mre user-friendly. Like everywhere else, here als are sme exceptins. The Linux distributr Red Hat fr example has imprved his enterprise prduct line - RHEL with the kernel 2.4, with s-called Backprts, s that even with these kernels a user-friendly display f prcesses was available. Cpyright REALTECH 2007 Page 9 f 25

10 The System Linux Data Cllectr The System Linux data cllectr mnitrs the hard- and sftware peratin f a Linux system. With it, the data cllectr is divided int tw views. The physical view Hst as well as the sftware view OS. Thrugh this separatin future develpments f this platfrm shuld be better integrate able int the cncept f theguard! ApplicatinManager. Hst: This name describes the mdel f the used hardware Disk: The available hard disks Partitin: The partitins n a hard disk Prcessr: The physically available prcessrs OS: The installed perating system CPU: The prcessrs, used by this perating system FileSystem: The file systems, managed by this perating system PrcessGrup: The prcesses, cnfigured by the user individually int grups Figure 4: DC tree (verview) The managed bjects, the cncrete physical bjects f the MOTs, are hierarchically arranged and clearly structured. This is clearly displayed in the abve figure, fr example, by the MOs OSDC, tgam, and ALL, which belng t the MOT Prcess Grups. Presenting the infrmatin in this way displays the current status at a glance. Mnitring parameters can be set individually fr each cmpnent. Cpyright REALTECH 2007 Page 10 f 25

11 Mnitring Hardware and Sftware Resurces T ensure the perating system and hence the live applicatins runs smthly, mnitring hardware and sftware resurces such as prcessrs, memry, hard disk space, virtual memry, prcesses, etc. is very imprtant. The resurces are mnitred fr sufficient capacity and perfrmance. If nly ne f the resurces is verladed r used up, the perfrmance f the entire system decreases dramatically. This can have a negative impact n the server's live envirnment, and in many cases, even results in erratic behavir. In the wrst case, the stability f the entire system is at risk. By cntinuusly mnitring the system resurces, the Linux DC reprts verlads and highly used resurces at an early stage. This enables the system administratr t react early t resurce bttlenecks and remve them befre they impact r bring dwn the live system. The Linux DC prvides a variety f statistical values regarding the current usage and perfrmance f the mnitred server's hardware and sftware resurces. Threshlds, which are used t generate alerts when they are vilated, can be defined fr all f the statistical values. Resurce bttlenecks are detected at an early stage and can be remved in a cntrlled manner. Operability and perfrmance mnitring can be carried ut at the same time. All f the statistical values can be mnitred and cmpared in the (Real-time) Perfrmance Mnitr. These values can be used t ptimize the perfrmance and the capacity. Figure 5: Current utilizatin f the system resurces prcessr, memry and swap space, in percent Cpyright REALTECH 2007 Page 11 f 25

12 The different servers' resurce usage and perfrmance data can be cmpared. This infrmatin is particularly useful fr ptimizatin tasks such as the efficient distributin f the lad acrss several servers. The statistical values can als be cllected in the ApplicatinManager database and evaluated using REALTECH Reprting. This infrmatin can be used t generate lng-term trend analyses, fr example, fr the usage f system resurces such as CPU, memry, and disk space, and as a basis fr cst and capacity planning. Hst - Infrmatin abut the Hardware view f the System The hardware related view Hst prvides data abut the hard disks and physical prcessrs, available in the system. Infrmatin, respectively perfrmance characteristics f available memry was mved t the OS tree. This als is valid fr the swap space. Figure 6: Prperties f the hst PrLiant ML370 G3" Disk - Infrmatin abut the Mnitring f Hard Disks The infrmatin prvided here refers t the hard disks available in the system. Figure 7: Prperties f the hard disk sda" Cpyright REALTECH 2007 Page 12 f 25

13 The Statistical Values abut the Mnitring f a Disk The number f read accesses, since the hard disk is available t the perating system The number f read sectrs, since the hard disk is available t the perating system The number f write accesses, since the hard disk is available t the perating system The number f written sectrs, since the hard disk is available t the perating system The current read rati (accesses per secnd) The current write rati (accesses per secnd) The currently read sectrs (sectrs per secnd) The currently written sectrs ( sectrs per secnd) The read data, since the hard disk is available t the perating system (megabyte) The written data, since the hard disk is available t the perating system (megabyte) The current read transfer rati (kilbyte per secnd) The current write transfer rati (kilbyte pre secnd) An example heret: Figure 8: Currently, abut 64 kb are written t disk sda Cpyright REALTECH 2007 Page 13 f 25

14 Partitin - Infrmatin and Mnitring f single partitins f a hard disk Figure 9: Prperties f hard disk partitin sda3 The Statistical Values f a Mnitred Partitin The number f read accesses, since the partitin has been integrated int the file system The number f read sectrs, since the partitin has been integrated int the file system The number f write accesses, since the partitin has been integrated int the file system The number f written sectrs, since the partitin has been integrated int the file system The current read rati (accesses per secnd) The current write rati (accesses per secnd) The currently read sectrs (sectrs per secnd) The currently written sectrs (sectrs per secnd) The read data, since the partitin has been integrated int the file system (megabyte) The written data, since the partitin has been integrated int the file system (megabyte) The current read transfer rati (kilbyte per secnd) The current write transfer rati (kilbyte per secnd) An example heret: Figure 10: Currently, abut 22 MB are written t partitin sda3 Cpyright REALTECH 2007 Page 14 f 25

15 Prcessr - Infrmatin abut the Available Prcessrs The Hst branch f the data cllectr displays the hardware view. The perfrmance data, respectively statistics f a prcessr unit yu can find in the sftware parts OS and CPU in branch OS. One f the reasns frt his separatin is, beynd ther things, the pssibility t multiply the prcessrs in the x86' prcessr architecture, als knwn as Hyper Threading. With it, ne prcessr unit is physically existent nly ne time e.g. a single prcessr system while the perating system is prvided with tw prcessr units. As an example, the new Dual Cre" technlgy can be mentined here. Figure 11: Prperties f prcessr 0 Cpyright REALTECH 2007 Page 15 f 25

16 OS - Infrmatin abut the Sftware f the System The OS prvides data abut prcessrs, file systems, prcesses, respectively prcess grups f the perating system. It prvides static infrmatin, like e.g. the system name, and the IP address, as well as infrmatin abut the user grups and their members. Figure 12: Cmmn infrmatin abut the OS, the perating system Figure 13: Infrmatin abut the users and grups knwn t the system Cpyright REALTECH 2007 Page 16 f 25

17 The Statistical Values f Mnitring the OS These values are divided int grups by CPU, memry and swap space. All f the perfrmance data, listed fr OS, refer t the verall system. This means that the prcessr utilizatin, in case f multi-prcessr systems, is the average ver the number f available prcessrs. In the sub-lcated structure CPU, each prcessr unit is evaluated fr itself. CPU: The idle time f the verall system (percent) CPU: The time, the verall system was running in system mde (percent) CPU: The time, the verall system was running in user mde (percent) CPU: The time, the verall system was running in system + user mde (percent) CPU: The time, the verall system was waiting n I/O (percent) CPU: The time, the verall system was wrking, including I/O waiting time (percent) Memry: The verall size (megabyte) Memry: The free part (megabyte) Memry: The used part (megabyte) Memry: The part that is fr the hard disk cache (megabyte) Memry: The part withut the hard disk cache (megabyte) Memry: Number f swapped in memry pages since the system started Memry: Number f swapped ut memry pages since the system started Memry: Current number f swapped ut memry pages per secnd Memry: Current number f swapped in memry pages per secnd Memry: The free part (percent) Memry: The used part (percent) Memry: The part that is fr the hard disk cache (percent) Memry: The part withut the hard disk cache (percent) Swap file: The verall size (megabyte) Swap file: The free part (megabyte) Swap file: The used part (megabyte) Swap file: The free part (percent) Swap file: The used part (percent) Examples heret: Figure 14: Currently, the verall system is utilized by abut 75%, whereby the majr part can be attributed t I/O Cpyright REALTECH 2007 Page 17 f 25

18 Figure 15: Currently, the system has a free memry capacity f abut 1.3% Figure 16: Currently, the system utilizes n swap space Cpyright REALTECH 2007 Page 18 f 25

19 CPU Mnitring the Prcessrs Wrking in the System The Prcessr branch f the data cllectr displays the sftware view. These are the perfrmance data, respectively statistics f a prcessr unit, which are apprpriately displayed by the OS branch. One f the reasns frt his separatin is, beynd ther things, the pssibility t multiply the prcessrs in the x86' prcessr architecture, als knwn as Hyper Threading. With it, ne prcessr unit is physically existent nly ne time e.g. a single prcessr system while the perating system is prvided with tw prcessr units. As an example, the new Dual Cre" technlgy can be mentined here. The Statistical Values f a Mnitred CPU The idle time f this prcessr unit (percent) The time, this prcessr unit spent in system mde (percent) The time, this prcessr unit spent in user mde (percent) The time, this prcessr unit spent in system- and user mde (percent) The time, this prcessr unit was waiting fr I/O (percent) The time, this prcessr unit wrked including I/O waiting time (percent) An example heret: Figure 17: Currently, the cpu2 has a utilizatin f abut 12% Cpyright REALTECH 2007 Page 19 f 25

20 FileSystem - Infrmatin abut Mnitring the File Systems Figure 18: The prperties f a file system, like e.g. type, muntpint and the device The Statistical Values f a Mnitred File System The available space fr the user rt (megabyte) The ccupied space fr the user rt (megabyte) The available space fr nrmal users (megabyte) The ccupied space fr nrmal users (megabyte) The available space fr the user rt (percent) The ccupied space fr the user rt (percent) The available space fr nrmal users (percent) The ccupied space fr nrmal users (percent) The number f available Indes The number f used Indes The number f available Indes (percent) The number f used Indes (percent) The verall size (megabyte) An example heret: Figure 19: Currently, the file system extdata02 is ccupied by abut 60% Cpyright REALTECH 2007 Page 20 f 25

21 Prcess Grups - Infrmatin and Mnitring f Prcesses and/r their Grupings After the user has created, cnfigured and added a prcess grup it shuld apprximately be displayed as fllws (the prcesses and their number displayed here, basically nly refer t the system and the pint in time at which the figures were created). Figure 20: The prperties f the prcess grup ALL with all f the prcesses, withut a filter The related prcess list lks as fllws (graphic is shrtened): Figure 21: The prcess list f the prcess grup ALL, displayed abve Accrding t the displayed grup, individual grups can be created. Their cntent will be defined by cnfiguring an apprpriate prcess filter. A grup Oracle fr example can cntain all database related prcesses, r a grup SAP can cntain all SAP related prcesses. Cpyright REALTECH 2007 Page 21 f 25

22 The Statistical Values f a Mnitred Prcess Grup The number f prcesses in a grup The prcessr utilizatin thrugh this grup (percent) The memry utilizatin f this grups (megabyte) An example heret: Figure 22: Currently there are 89 prcesses Furthermre, the fllwing events will be reprted: Ntificatin, if a new prcess was started that matches t the prcess pattern f a prcess grup Ntificatin, if a prcess was ended that was a member f a prcess grup Standard Reprting and Service Level Analysis Besides the perfrmance mnitrs and the display and alerting f critical perating statuses, histrical infrmatin can be evaluated with theguard! ApplicatinManager fr mnitring Service Levels r fr the capacitive planning: Service Level Analysis Cnfiguratin f Object Level Agreements (OLAs) fr applicatins (prcess r prcess grup) Measurement f the availability against the defined rules and reprts Standard Reprting (Perfrmance and Capacity) Availability f an applicatin (prcess r prcess grup) Lad and resurce cnsumptin f an applicatin (prcess r prcess grup) Overall prcessr utilizatin Single prcessr utilizatin Memry Cpyright REALTECH 2007 Page 22 f 25

23 Case Study f a Mnitred System The fllwing figures shw hw the lad can be measured and mnitred n a system. Accrdingly it is shwn, hw the system behaves referring t the available perating resurces. In the example tw files f 800 MB are created with the cmmand fllwing hereafter t prduce a lad t the system. Befrehand, pssibly present files are deleted with rm. fr x in 1 2 ; d dd if=/dev/zer f=/extdata02/tmp/xxx_$x bs=4096k cunt=200 ; sleep 1 ; dne The Perfrmance Mnitrs, mnitring different perating resurces, shw hw the system behaves. The fllwing mnitrs were cmpiled: CPU: T display the verall prcessr lad f the system Single CPUs: T display the caused lad per CPU Disk+Filesystem: T display the caused peak lad and fill rate f the hard disk memry Memry: T display the memry utilizatin, the utilizatin f the hard disk cache in ppsite t memry utilizatin Figure 23: Case study with different Perfrmance Mnitrs during executin Cpyright REALTECH 2007 Page 23 f 25

24 As can be seen in the previus figure, when deleting the present files the hard disk cache in memry will be drpped. This causes a small lad peak in the system fr cpu2. Just as the fill rati f the used file system sinks. The fill rati again rises as sn as the cmmand shwn abve is executed and bth f the files are created. Accrdingly, the hard disk cache in memry rises and with it the verall memry utilizatin. The prcessr lad f the verall system rises, which can bee seen by the lad peaks f the individual prcessrs. After prcessing the cmmand the system ges back t idle mde. The requested hard disk cache will be kept until the system has t serve ther prcesses with different resurce utilizatin. Cpyright REALTECH 2007 Page 24 f 25

25 Availability and Platfrms The System Linux DC is available frm nw n. It supprts the 32Bit x86 prcessr architecture, as well as the 64Bit variant, whereby the 32Bit variant can run n a 64Bit system. It is currently available fr the platfrm IDs 59 and 60'. The platfrm ID 59 crrespnds t the enterprise series f the Linux Distributr SuSE/Nvell, frm versin 9 n (Als usable fr the cmmunity variant SuSE Linux, respectively pensuse, accrding t the apprpriate versin). The platfrm ID 60 crrespnds t the enterprise series f the Linux Distributr Red Hat, frm versin 3 n (Als usable fr the cmmunity variant Fedra Cre ). Fr mre infrmatin abut REALTECH s sftware slutins: REALTECH AG Industriestr. 39c Walldrf, Germany Tel.: +49-(0) Fax: +49-(0) custmer-services@realtech.cm Cpyright REALTECH 2007 Page 25 f 25