Integrating Dell PowerEdge Servers into an Environment Managed by HP Systems Insight Manager 4.0

Transcription

1 Integrating Dell PowerEdge Servers into an Environment Managed by HP Systems Insight Manager 4.0 Dell OpenManage Systems Management Dell White Paper By Niven Brooks Onsite Systems Engineer June 2004 Version 1

2 Contents Introduction...4 Test Configuration...5 Typographical Conventions...5 Loading and Configuring Server Administrator...6 What SNMP configuration should I use?...6 Using Dell Server Assistant to load the OS and SNMP...6 SNMP Configuration after OS installation...7 Loading Server Administrator...8 Enabling Volume Capacity Monitoring...11 Testing...11 Loading the Dell MIBs...13 Uploading the Dell MIBs...13 Compiling the MIBs...14 Registering the MIBs...14 Device Type Manager...15 Discovering New Dell Servers...20 Setting Global Protocol Settings...20 Creating a New Discovery Range...21 Testing for Events...23 Generate an Event...23 Results...25 Limitations and Caveats:...25 Appendix A Dell MIBs...26 Essential Server MIBs...26 Network Interface Adapters...26 Other Adapters, Devices, and Software...27 Legacy MIBs...27 June 2004 Page 2

3 Figures Figure 1: Architecture of the Tested Environment... 5 Figure 2: Setting Security and Trap Destinations... 8 Figure 3: Managed System Software Installation Options... 9 Figure 4: Server Administrator Options Figure 5: Testing the PowerEdge Server with SNMPWALK Figure 6: Retrieve OID from system Figure 7: Retrieve variable from MIB Figure 8: Get response Figure 9: Completed System Type Dialog Figure 10: Global Protocol Settings Figure 11: Automatic Discovery - General Settings Figure 12: All Systems Figure 13: All Events June 2004 Page 3

4 Section 1 Introduction In response to the pressure for increased productivity of system administrators, server vendors have responded with management tools. Dell s offering is the Dell OpenManage suite of products. While these products cover software deployment, hardware configuration, asset management, remote support, and system health monitoring, this paper is focused on monitoring system health on a collection of servers. To do this using Dell s OpenManage tools, OpenManage Server Administrator is loaded on every Dell PowerEdge server to be managed, and one instance of OpenManage IT Assistant is installed and configured for monitoring all the PowerEdge servers. Errors detected by Server Administrator are then forwarded via Simple Network Management Protocol (SNMP) to IT Assistant, where they are logged and can generate and paging notifications. Since a Hewlett-Packard Systems Insight Manager 4.0 environment has the same architecture, it is possible to integrate Dell PowerEdge servers by taking advantage of the industry standard interfaces of SNMP and Hypertext Transport Protocol Secure (HTTPS) in Server Administrator. The advantage would be for administrators to continue to use their existing HPSIM-based notification processes while fully benefiting from the use of Server Administrator on Dell servers. This paper details the specific steps needed to add a Dell PowerEdge 2650 server running Microsoft Windows 2000 Server and 2003 Standard Server to an environment currently being managed by HPSIM 4.0. To add a server running NetWare or Linux, the HPSIM and OpenManage Server Administrator configuration would be the same, with the primary difference being how SNMP is configured at each managed PowerEdge server. At a high level, and ordered for ease of troubleshooting, the steps are: 1. Load and configure the OpenManage Server Administrator on the Dell server so it can communicate with HPSIM 2. Load Dell MIBS into HPSIM so it can properly communicate with Server Administrator 3. Configure HPSIM to recognize Dell servers 4. Generate some test events June 2004 Page 4

5 Section 2 Test Configuration The scenario that was tested for this paper was a Server Administrator running on a Dell PowerEdge 2650 and 500SC and HPSIM running in a VMWare Workstation 4.5 virtual machine. To prove multi-version compatibility, Windows 2003 was installed on the virtual machine and the Dell PowerEdge 500SC, whereas Windows 2000 was installed on the PowerEdge The OpenManage Applications CD which includes Server Administrator 1.7 and Array Manager 3.5 were installed on both Dell PowerEdge servers. Microsoft s Data Engine (MSDE) database and HP Systems Insight Manager 4.0 were installed and configured as the management console on the virtual machine. Figure 1: Architecture of the Tested Environment Typographical Conventions For clarity of navigation, the following conventions are used: Underscore is used to indicate an HTML hot link, hot spot, or button within an applet Bold indicates the title of a dialog box, button, or applet Italics indicates notes June 2004 Page 5

6 Section 3 Loading and Configuring Server Administrator The first step is to properly load and configure the Dell server as the managed system to talk to HPSIM 4.0. If the operating system (OS) has not yet been loaded, then the easiest process is to use the Dell Server Assistant CD to load both Microsoft Windows and SNMP. If the OS was already loaded, then only SNMP needs to be loaded and configured. Once SNMP is configured, the OpenManage Server Administrator can be installed. What SNMP configuration should I use? The default SNMP community name is public, but using that could allow a rogue management station to access your servers. The SNMP community name is like a password both HPSIM and Server Administrator need to communicate. To enhance security, access can be Read Only. This prohibits using SNMP to make changes to the server, such as changing threshold settings or shutting it down, but allows Server Administrator to send alerts to a console when status changes. With a Dell PowerEdge Server, users will not lose functionality during this process. It is possible that other systems need SNMP set to Read Write, so be sure the total environment is well understood. If the intent were for HPSIM and IT Assistant to coexist in the network to provide the full OpenManage capabilities, then it would be necessary to configure the Dell PowerEdge server with Read Write SNMP permissions. Note that Dell secures Read Write operations using SNMP only to come from Dell OpenManage IT Assistant. SNMP trap destinations also need to be specified. These are the hostnames or IP addresses of one or more systems that are to receive notification of events. For this paper, the community name of showcase with Read Only rights was used with a single trap destination to the virtual machine running HPSIM. These settings need to be made on each Dell server added to the environment. Using Dell Server Assistant to load the OS and SNMP There are three CDs that ship with every Dell PowerEdge server: the Dell OpenManage Server Assistant CD, the Dell OpenManage Systems Management June 2004 Page 6

7 CD, and the Product Documentation CD. The Server Assistant CD is bootable and is used to perform a complete installation from local media. It can also be used with a running system and brings up a menu for access to drivers and BIOS/FW update diskettes. The PowerEdge 2650 and 500SC in the configuration tested for this paper were booted from the Server Assistant CD and the menus were followed until the Enter Configuration Information for: Microsoft Windows 200x Server screen was reached. On that screen, click the Advanced button to show the additional settings that can be set by Server Assistant. The default is Configure SNMP, but it is also necessary to enter a Community Name and Trap Destination and change the Accepted Community Names from public:read_only to showcase:read_only. The rest of the defaults should be left unchanged. At the very bottom of the screen, past the NIC configuration, the Install Server Administrator box is checked by default. Uncheck it to allow explicit setting of the appropriate options instead of taking the Express Options. These are described later in the Loading Server Administrator section. If missed, just select Cancel when prompted for the System Management CD after the system reboots and continue with the section below: Loading Server Administrator. SNMP Configuration after OS installation If the Server Assistant CD has not been used to load the OS and configure SNMP, then the following steps should be performed. The first is to ensure that the SNMP component is installed. After selecting the Add/Remove Windows Components in the left hand of the Add/Remove Programs dialog box of the Control Panel, the Windows Components are displayed. Highlighting Management and Monitoring Tools and then selecting Details brings up the option to check Simple Network Management Protocol (SNMP). After the SNMP service is installed, its parameters can be set by right clicking on the SNMP service in Service Manager to open the Properties panel. Here the community name of showcase and trap destination can be set in the security and traps tabs. These are shown in Figure 2. June 2004 Page 7

8 Figure 2: Setting Security and Trap Destinations Loading Server Administrator Server Administrator is distributed on the Dell OpenManage Systems Management CD. Documentation is available online at or on the Product Documentation CD. Note that the CD has a version that denotes the release of all OpenManage applications (such as version 3.7), but that the specific version of OpenManage (such as 1.7) is on that CD. Although manually loading Server Administrator on a single server is covered in this paper, it is possible to completely script and automate the install. For more information see &cs=555&l=en&s=biz. After inserting the Systems Management CD it will AUTORUN. The user input is as follows: 1. At the welcome screen click Next>>. 2. Read the License Agreement and click Accept if you agree with its terms. The Setup Wizard Preparation screen will appear. 3. Click the Install Managed System button. The OpenManage tools can be installed in two modes: Managed System which is intended for installation on a managed node, and Management Station which is intended to be installed on the management console. June 2004 Page 8

9 4. Click the Custom Setup button. 5. Choose the destination of the OpenManage applications and click Next>>. The Managed System Software window will appear. Figure 3: Managed System Software Installation Options 6. If a DRAC II is installed in the PowerEdge server, the DRAC II checkbox should be checked. If not click More Info>> for suggestions. 7. If a DRAC III or ERA or ERA/O is installed, the Remote Access checkbox should be checked. If not click More Info>> for suggestions. 8. The Storage Management checkbox should be checked. If not click More Info>> for suggestions. A common message here is FW out of date. The PERC RAID controller FW level needed is on the Server Assistant CD of the same release as the Server Management Applications CD. Once Server Administrator is installed, it can be used to update firmware, but at this point a boot diskette is needed. 9. If all of the prerequisites have been met, a Settings>> button will appear beside Storage Management. Click this button. 10. By default, Array Manager (Dell s storage management software) replaces local disk management. This is not recommended because some storage vendors use the native Windows Disk Management to support some of their June 2004 Page 9

10 tools. Uncheck the Replace Logical Disk Management checkbox to get a parallel install, and click OK. 11. Beside Dell OpenManage Server Administrator click the Settings>> button. 12. The User and Password sections listed here are used when performing actions from IT Assistant to this server, such as powering it off. It is recommended that this password be changed so that only those with this password can perform actions on this server from an installation of IT Assistant. Change the password and click OK. Figure 4: Server Administrator Options 13. Since HPSIM does not use the Common Information Model (CIM), uncheck the Install CIM checkbox to close a potential security opening and click OK. 14. Click Next>>. The Installation Summary window will appear. 15. Click Yes to begin the installation. 16. Select Yes, reboot my system now and click Finish. 17. Click the OK button to confirm the reboot. During this, the process also saves InstallSummary.htm, unattend.txt and DOMSA_SETUP.txt files in C:\ for reference. June 2004 Page 10

11 Enabling Volume Capacity Monitoring Volume Capacity Monitoring was also enabled on the PowerEdge 2650 so that free disk space warning and error events would be sent to HPSIM when 90% and 98% thresholds were reached on the C: drive. It was deemed that the notification was worth the additional overhead of having this service running. To enable Volume Capacity Monitoring: 1. Click Start -> Programs -> Dell OpenManage Applications -> Array Manager -> Array Manager Utilities 2. Check the Volume Capacity Monitoring checkbox, then click Apply, then click Close. Testing After the reboot, Server Administrator was checked to see that it was operating correctly. This was done in the following steps: 1. Login to the server as Administrator or other account with administrator membership. 2. Launch Server Administrator from the desktop icon or open a browser and enter The address can be used from any system with network access to the server to access Server Administrator. 3. Log in to Server Administrator as Administrator or other account with administrator membership. 4. Select Main System Chassis in the left-hand navigation tree. The status icons should all be green checks to indicate an error free status To check and clear storage errors: 1. Click Start -> Programs -> Dell OpenManage Applications -> Array Manager -> Array Manager Console. 2. Close the welcome screen. 3. Select the Events tab. 4. Review the event list for any critical errors. Right-click the event list and select Clear All Events. At this point, everything should be working correctly on the Dell system. A further check would be to use snmpwalk, which is part of Win32tools available at As shown in Figure 5 below, the command saves all available SNMP information available via community string showcase on system to the file dellserver.txt. Provided that DNS or June 2004 Page 11

12 WINS is properly configured for the new Dell Server system, its name can be used instead of the IP address. Snmpwalk cshowcase >dellserver.txt Figure 5: Testing the PowerEdge Server with SNMPWALK When opening dellserver.txt with Notepad, there should be entries with in the OID that were returned from Server Administrator. Specifically, will contain the model of the server. Running this from the Insight Manager 7 system tests the following: network connectivity, that the community string is correct, and that Server Administrator is providing the expected information. June 2004 Page 12

13 Section 4 Loading the Dell MIBs Uploading the Dell MIBs The MIB files are located in the directory \support\dcpemibs on the Systems Management Applications CD and are well documented in the included README. The two essential MIBS are: , which provides 36 traps from the server motherboard such as: system type, voltages, temps, etc. It is the primary MIB for PowerEdge systems. Detailed information can be found at Arymgr, which provides 80 server related traps from the RAID and SCSI subsystem. Detailed information can be found at tm A number of other MIBs are included on the Dell OpenManage Systems Management Applications CD, but are beyond the scope of this paper. A description of all the MIBS and their use is documented in Appendix A. Uploading the MIBs is simply copying them from the OpenManage Applications CD to the \Program Files\HP\Systems Insight Manager\mibs folder 1. Insert the Dell OpenManage Systems Management Applications CD To prevent the Dell Systems Management installer from autoplaying, hold down the Shift key on the keyboard. 2. If the Dell Systems Management Applications installer has started, click Exit, and confirm the installer termination by clicking Yes. 3. Copy mib and arymgr.mib from the \support\dcpemibs folder on the CD to \Program Files\HP\Systems Insight Manager\mibs 4. Because HPSIM generates an error when a MIB has a filename that contains only numbers, rename \Program Files\HP\Systems Insight Manager\mib\10892.mib to new10892.mib, and for consistency also rename arymgr.mib to newarymgr.mib. dell10892.mib and arymgr.mib already exist in this folder. It is recommended that this name be avoided for the new file to avoid confusion with the HP- and Dellprovided MIBs. June 2004 Page 13

14 Compiling the MIBs Compiling the MIBs creates an intermediate.cfg file that HPSIM can later register. To compile the Dell MIBs: 1. Using the cd command, change working directories to \Program Files\HP\Systems Insight Manager\mibs. 2. Enter the command mcompile new10892.mib. The MIB should compile and return the message Mib Compilation completed successfully. 3. Enter the command mcompile arymgr.mib. The MIB should compile and return the message Mib Compilation completed successfully. Registering the MIBs Registering MIBs to HPSIM is the process that maps the SNMP information received from the Dell server to numbers and character strings that can then be used for identification and notification messages. Register both essential MIBs as follows: 1. Enter the command mxmib a new10892.cfg. The cfg file should register and return the message COMMAND COMPLETED SUCESSFULLY!. 2. Enter the command mxmib a arymgr.cfg. The cfg file should register and return the message COMMAND COMPLETED SUCESSFULLY!. June 2004 Page 14

15 Section 5 Device Type Manager Devices are discovered and added to the HPSIM database by its Device Type Manager when a new system is detected via a ping sweep or when receiving a SNMP Trap. The Device Type Manager then does a sequence of queries to the new device to determine its identity. The default configuration includes definitions for all the HP devices and even the Dell devices that use the older Desktop Management Interface (DMI), such as an OptiPlex desktop running the OpenManage Client Instrumentation (OMCI), and older Dell servers. The steps below configure HPSIM to look for specific information in the Dell MIBs to tell that the device found is a PowerEdge server. This only needs to be done once, as all Dell servers running Server Administrator appear the same way within HPSIM. The steps used to configure the Device Type Manager to recognize a Dell Server are: 1. Start and log in to HPSIM. 2. Select Options -> Discovery -> Manage System Types. 3. On the Rules list, scroll down and select Dell Server. 4. To prevent confusion and simplify administration, click the Delete button to delete the existing Dell Server entry, and click OK to confirm. 5. Click the New button. The New Rule pane will open below. While values may be manually entered in the dialog boxes presented in the New Rule window, querying a Dell server for these values prevents typographical errors and provides verification that SNMP communication is working properly. In this vane, the querying tools within the New Rule window will be used. 6. Beside System object identifier click the Retrieve from system button. 7. In the Retrieve from system window change the Community string to showcase. 8. Enter the hostname or IP address of the target Dell system in the following text box. June 2004 Page 15

16 9. Click Get Response. Note that the response value of is displayed below. This is a generic Windows response value and indicates that SNMP communication is working properly. Figure 6: Retrieve OID from system 10. Click the OK button to accept this value and return to the Device Type manager window. 11. Beside MIB variable object identifier click the Retrieve from MIB button. The Retrieve from MIB window will appear. 12. Beside MIB definition file name choose new10892.mib from the list. June 2004 Page 16

17 13. Beside MIB variable name choose systemmanagementsoftwarename. Figure 7: Retrieve variable from MIB 14. Click the OK button to accept this value and return to the Device Type manager window. 15. Beside Object value click the Retrieve from System button. The Retrieve from system window will appear. 16. Change the Community string to showcase. June 2004 Page 17

18 17. Click the Get response button. Note that the response value is Server Administrator. Figure 8: Get response 18. Click the OK button to accept this value and return to the Device Type manager window. 19. Beside Compare rule select starts with. 20. Beside Product name enter Dell Server. June 2004 Page 18

19 21. Leave the Custom management page field blank and click the OK button. HPSIM is already programmed to redirect users to Server Administrator for server administration on Dell servers. Figure 9: Completed System Type Dialog June 2004 Page 19

20 Section 6 Discovering New Dell Servers Now that the new Dell Server device type has been added to the HPSIM database, HPSIM can properly discover and identify Dell PowerEdge servers. Like Dell OpenManage IT Assistant, HPSIM discovers systems by IP address. The following is an example of setting discovery ranges for the purpose of providing an example for this paper. In your environment the discovery settings will most likely be different. Setting Global Protocol Settings Even though the community string of showcase was set in SNMP setting previously, the community string of public is set as the default in HPSIM s Global Protocol Settings. To change this setting: 1. Click Options -> Protocol Settings -> Global Protocol Settings. The Global Protocol Settings window will appear. 2. Scroll down to the Default SNMP settings section and enter showcase beside Default 1. Figure 10: Global Protocol Settings June 2004 Page 20

21 3. Click the OK button at the bottom of the window to accept this change. Creating a New Discovery Range 1. Click Options -> Discovery-> Automatic Discovery. The Automatic Discovery General Settings window will appear. 2. Scroll to the bottom of the screen and enter the range of IP addresses that HPSIM should query to discover your Dell servers in the Ping inclusion ranges text box. For this paper, the IP addresses of and were used for the Dell servers Figure 11: Automatic Discovery - General Settings 3. Click the Save and Run button to continue. 4. The Automatic Discovery - General Settings window will re-appear, and the status of the discovery cycle will be shown in the Status section of the window. 5. When the discovery cycle has completed, the status will display a date and time instead of 100%. When this happens click the All Systems link under the Systems Lists pane. June 2004 Page 21

22 6. The All systems window will appear and will display all of the discovered systems. Figure 12: All Systems June 2004 Page 22

23 Section 7 Testing for Events Of the information in the MIB files, the traps or error indications sent by Server Administrator are of primary interest to an administrator. These are the events that can be used to cause a notification such as an or page. They have names like alertcoolingdevicenormal with a text description, a severity, and a category. For the server MIB, there are only 36 traps and for arymgr there are only 80 server-related events. The default notification tasks within HPSIM are based on Severity with Informational Events being traps of Informational severity and Important events being those with critical, major, or minor. Generate an Event A complete end-to-end test can be performed by using OpenManage Server Administrator to change a threshold setting. Pulling a power cord or power supply can also generate an error event. Here are the steps used for this paper: 1. As described in the Loading and Configuring Server Administrator section, browse to Server Administrator and log in with administrative privileges. 2. Expand Main System Chassis in the left-hand navigation tree. 3. Select Voltages. 4. Select BP 3.3V in the action pane. 5. Select Set to Values then enter a Minimum Warning Threshold value that is greater than the current Reading. For example, if the reading is currently V, enter a value of Click Apply Changes. 7. The status for the probe should then change from green check to a yellow warning symbol. Server Administrator will now also generate a warning SNMP trap and forward it to the HPSIM server. 8. To set the voltage warnings back to their defaults, ensure that Set to Default is selected and click Apply Changes. Server Administrator will also generate a normal trap and forward it to the HPSIM server. June 2004 Page 23

24 9. In HPSIM, select All Events from the left-hand pane and note the events that have been generated. Figure 13: All Events 10. Click the server name of the Dell server to open its System Page. 11. Click the Links tab. 12. Click Server Administrator to link to Server Administrator from within HPSIM. June 2004 Page 24

25 Section 8 Results This paper has shown how a Dell PowerEdge server can be integrated into an HP Systems Insight Manager environment following these basic steps: Loading and configuring the Dell PowerEdge Server Recognizing the Dell PowerEdge Server in HPSIM Discovering the Dell servers Testing the configuration. The result was that an error such as a voltage warning or power failure could be received as a Minor Event that triggers an or page action. Notifications of specific drive and memory module pre-failure alerts are also recognized as an indication of impending device failure. The full terms of when this can be used for service parts dispatch can be found at &cs=04&l=en&s=bsd Limitations and Caveats: Finally, it is worth mentioning that the Hardware status in the All Systems query will continue to show green until HPSIM loses communication (no ping response), when it will go red or critical. Also, as the PowerEdge server does not have the necessary software version agent, the MP and SW status will always be unknown or missing. Dell s IT Assistant console provides the best manageability for Dell servers, including detailed status, inventory information, and Remote Access (out of band remote) launch. But the method of integration to HPSIM shown here does provide an adequate solution by extending the notification and alerting to Dell servers and allowing the in-context launch of Server Administrator for full server management. June 2004 Page 25

26 Appendix A Appendix A Dell MIBs Essential Server MIBs MIB file Registration Results Comments mib OK Information including 36 traps from the server motherboard such as system type, voltages, temps, etc. It is the primary MIB for PowerEdge systems. Arymgr.mib OK Provides detailed information about storage hardware components and RAID configurations monitored by the array Manager Agent. It provides 80 server related traps. Network Interface Adapters MIB file Adaptino.mib BaspConfig, BaspStat, BaspTrap.mib Registration Results Error defining object OK Comments Defines the Broadcom NetXtreme Adapter Extended Information Set. Collectively provides detailed information about Broadcom Gigabit adapters such as embedded in PowerEdge 2650 models. It only provides one trap indicating teamed adapter fail-over. Intel.mib OK Registering this MIB is a pre-requisite to both Intelnic.mib and Intel-LAN-Adapters-MIB.mib. Intelnic.mib Intellan.mib Error defining object Cannot not compile DMTF-DMI Provides detailed information about the PRO 100+ Intel NIC adapter. Provides detailed information but no traps for Intel PRO 100s, PRO 1000xt, PRO 100+ Dual Port, and PRO 1000F adapters. Cnstattrap.mib OK This provides one trap from the Broadcom June 2004 Page 26

27 CryptoNetX SSL accelerator adapter if present. Other Adapters, Devices, and Software MIB file DRAC2.mib Symmib.mib Registration Results Could not compile DMTF-DMI Could not compile DMTF-DMI Comments Provides detailed information about the components monitored by the DRAC II software agent available in some older PowerEdge Servers. Provides detailed information about the components monitored by LSIʹs Symbios agent. The Symbios agent monitors LSI/Symbios controllers and the devices connected to them on PowerEdge 8450 systems. Legacy MIBs The following MIBS are from earlier versions of OpenManage and would not be needed if the current version of Server Administrator is used throughout the environment. MIB file Registration Results Comments CIO400.mib OK Adaptec Comprehensive Input/Output. Since OpenManage 3.3, arymgr.mib now has this information. AAC.mib OK Provides detailed information about the devices and configurations monitored by the now obsolete PERC 2 software agent. Dellserv.mib PERC.mib Duplicate object Warning, but successful Provides detailed information about the various hardware components monitored by the now obsolete HIP3.5.2 software agent. Provides detailed information about SCSI storage hardware components and RAID configurations monitored by the PERC Console Package software agent. The PERC Console Package monitors the hard-disk drive subsystem(s) of servers installed with PERC, PERC 2/SC, and PERC 2/DC. June 2004 Page 27

28 THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. Dell, OpenManage, PowerEdge and OptiPlex are trademarks of Dell Inc. Microsoft and Windows are registered trademarks of Microsoft Corporation. NetWare is a registered trademark of Novell. Linux is a registered trademark of Linus Torvalds. Insight Manager is a trademark of Hewlett- Packard. VMWare is a trademark of VMWare, Inc.. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others. Copyright 2004 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell. Information in this document is subject to change without notice. June 2004 Page 28