Xserve Apple Xserve Diagnostics User Guide For Version 3X104
KKApple Inc. © 2009 Apple Inc. All rights reserved. Under the copyright laws, this manual may not be copied, in whole or in part, without the written consent of Apple. The Apple logo is a trademark of Apple, Inc., registered in the U.S. and other countries. Use of the “keyboard” Apple logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may constitute trademark infringement and unfair competition in violation of federal and state laws.
Contents 5 6 7 7 8 8 9 Chapter 1: Overview and Requirements 10 10 11 12 13 14 Chapter 2: Setup and Installation 17 17 18 18 19 19 20 22 Chapter 3: Starting Up AXD Tools 23 23 24 25 25 26 27 28 28 28 Chapter 4: Using AXD Tools Overview of AXD Configurations Requirements General Requirements Storage Device Requirements Local and Remote Requirements NetBoot Server Requirements Setting Up a NetBoot Server Deleting the AXD NetBoot Image Setting Up a Storage Device for AXD Tools Installation Installi
28 29 29 30 31 32 33 34 34 Viewing Saved Logs Taking Screen Shots Using AXD Mac OS X Tools Customizing AXD Mac OS X Tools Test Settings Working with Test Groups Viewing Logs Setting Log Preferences Shutting Down or Restarting the Xserve Quitting AXD Mac OS X Tools While a Test is Running 35 35 37 37 38 38 38 39 39 40 41 41 42 42 42 42 42 43 43 43 44 45 45 46 46 47 47 47 47 48 48 Appendix: AXD Tools Test Reference 4 Comparison of Available Tests AXD EFI Tools Tests Startup Tests Boot ROM Tests Ether
Overview and Requirements 1 Apple Xserve Diagnostics tests your Intel-based Xserve computer for hardware issues.
Note: This guide describes how to use AXD version 3X104, which is included on the Admin Tools disc (version 10.5 or later). If you’re using a different version of AXD tools, the instructions in this guide might not work. You can find out which version of AXD tools you’re using by opening AXD Mac OS X tools and choosing AXD > About Apple Xserve Diagnostics. Overview of AXD Configurations You can install and run AXD tools in a variety of ways, so choose the method that best suits your needs.
Option Considerations Start up the AXD EFI tools located on the Admin Tools disc Advantages: ÂÂ You can use AXD EFI tools ÂÂ You can use the same disc to test multiple Xserve computers Disadvantages: ÂÂ You need physical access to the Xserve ÂÂ You must insert the disc in the Xserve ÂÂ You can’t save logs or take screen shots Install AXD Mac OS X tools on an internal volume Advantages: ÂÂ You can use AXD Mac OS X tools ÂÂ You don’t need physical access to Xserve to run AXD Mac OS X tools remotely (if yo
Storage Device Requirements Depending on whether you want to run AXD EFI tools, AXD Mac OS X tools, or both, you need empty volumes on the Xserve or on a portable storage device. If you want to run AXD Mac OS X tools, the storage device must use the GUID Partition Table partition scheme. If you’re running only AXD EFI tools on the storage device, you don’t need to use the GUID Partition Table partition scheme.
ÂÂ If the client Xserve is running AXD Mac OS X tools, you must be able to log in as the root account. The root account gives a system administrator complete access to the Xserve. If you want to run AXD tools entirely remotely (for situations where the Xserve is physically inaccessible or if you want to save AXD EFI tools test results), in addition to meeting the network requirements, the Xserve must be able to start up Mac OS X Server.
Setup and Installation 2 Before you can run AXD tools, you must set up your testing environment and install AXD. Make sure you meet AXD requirements before attempting setup and installation. For more information, see “Requirements” on page 7. Setting Up a NetBoot Server Before you set up a NetBoot server, make sure you have an available server that meets the requirements described in “NetBoot Server Requirements” on page 9. After you set up a NetBoot server, you install the AXD NetBoot image.
If multiple network interfaces are listed, it’s likely that only one of the interfaces is on the same subnet as your Xserve. If you’re not sure which interface is on the same subnet, open Network Utility (located in /Applications/Utilities/) on your NetBoot server and your Xserve. In the Info pane, choose different network interfaces on the NetBoot server and your Xserve and compare the IP Address fields.
Setting Up a Storage Device for AXD Tools Installation To set up an internal volume or portable storage device for AXD tools installation, you must have at least 30 MB of available space for AXD EFI tools or at least 7 GB of available space for AXD Mac OS X tools, which requires installing Mac OS X Server. These requirements are described in detail in “Storage Device Requirements” on page 8.
To do this Do this Display a partition’s size Click the partition and review the Size field. Set the size of the partition Edit the Size field. Create more partitions Select a partition and click the Add (+) button. Delete partitions Select it and click the Delete (–) button. Name a partition Select it and enter a name in the Name field. If you’re installing AXD EFI tools, name the volume AXDEFI3X104.
If you want to connect a host computer directly to the Xserve, and the host computer doesn’t provide DHCP service on the port used to directly connect to the Xserve, you’ll need to create a file on the Xserve that assigns an IP address to the Xserve. However, if the host computer provides DHCP service, don’t create this file. For information about how to find out if a computer is providing DHCP service, see Network Services Administration at: www.apple.
Installing AXD Mac OS X tools involves three steps: ÂÂ Install Mac OS X Server with minimal options selected ÂÂ Copy AXD Mac OS X tools from the Admin Tools disc to /Applications/ ÂÂ Configure Mac OS X Server By dedicating a minimal installation of Mac OS X Server for use with AXD Mac OS X tools, you reduce the risk of server processes interrupting AXD testing. To install AXD Mac OS X tools: 1 Insert the Mac OS X Server Install DVD.
12 Open System Preferences (located in /Applications/). Change the following options in System Preferences panes. System Preferences pane Recommended configuration Accounts Select the System Administrator account, and click Login Items. Click Add (+), select /Applications/AXD.app, and click Add. CDs & DVDs In all pop-up menus, choose Ignore. Desktop & Screen Saver In the Screen Saver pane, drag the “Start screen saver” slider to Never.
Starting Up AXD Tools 3 This chapter describes several methods that let you change the startup disk to the volume with AXD tools installed. Before you start up AXD tools, make sure you’ve properly installed and configured the tools. For more information, see Chapter 2, “Setup and Installation,” on page 10. Changing the Startup Disk AXD tools is usually installed on a dedicated volume to minimize the risk of server processes interrupting the tests.
The Xserve becomes unavailable whenever you use AXD tools. Before starting tests, alert your users that the server will be unavailable. Changing the Startup Disk in System Preferences If Mac OS X Server starts up by default on your Xserve, you can use System Preferences to change the startup disk. The list of startup volumes includes internal volumes and connected portable storage device volumes.
To change the startup disk using the command-line interface: 1 Open Terminal (located in /Applications/Utilities/). 2 If you want to connect to a remote server, enter the following in the Terminal window, and authenticate when requested: ssh username@serveraddress Replace username with the short name of a user who can authenticate as the root account on the server. Replace serveraddress with the URL, IP address, or host name of the server.
To temporarily change the startup disk at startup: 1 Restart the Xserve. 2 While the Xserve is restarting, press and hold the Option key until a list of volumes appears. If you’re asked to authenticate, enter the firmware password and click the Continue (right-arrow) button. If you have the Admin Tools disc inserted, you can start up using AXD EFI tools located on the disc by pressing and holding the D key instead of the Option key.
To use the Xserve front panel to start up an AXD EFI tools NetBoot image: 1 Turn off the Xserve. 2 Press and hold the system identifier button and press the on/standby button. On/standby button System identifier button 3 Continue holding the system identifier button until the top row of lights blink right to left. Release the system identifier button. Top row of lights blink right to left, then left to right.
7 When the lower-left light is on, press and hold the system identifier button until all the lights in the top row are on. Release the system identifier button. Top row of lights comes on. When you release the button, the Xserve starts up from the AXD EFI tools NetBoot disk image. After you run AXD EFI tools and restart, the Xserve starts up from its default startup volume.
Using AXD Tools 4 AXD Mac OS X tools and AXD EFI tools have different interfaces and functionality. This chapter describes how to use both sets of AXD tools. Before you can use AXD tools, make sure you’ve properly started up the tools. For more information, see Chapter 3, “Starting Up AXD Tools,” on page 17.
The following table describes the three modes: Mode Description Automatically enters mode if Host You run AXD Mac OS X tools The computer searches for and either: Xserve computers that are on the same subnet and start AXD ÂÂ The computer isn’t an Inteltools in remote mode. When based Xserve one is found, the host computer ÂÂ You’re not logged in as root controls AXD tools on the client Xserve. Client The Xserve can be controlled by You’re running AXD EFI tools a host computer.
2 If the host computer is an Intel-based Xserve and you’re logged in as root, when AXD Mac OS X tools opens, a dialog asks you to choose which mode to enter. Choose “Connect to remote Xserve” and click OK. If your computer isn’t an Intel-based Xserve, the dialog doesn’t appear, and AXD Mac OS X tools automatically enters host mode. 3 On the client Xserve, change the startup disk to a volume with AXD tools and restart it.
To test the local Xserve using AXD Mac OS X tools: 1 Change the startup disk of the Xserve to a volume with AXD Mac OS X tools, restart it, and log in as root. 2 If AXD Mac OS X tools doesn’t open automatically, open it (located in /Applications/). 3 When AXD Mac OS X tools opens, choose “Local” from the dialog that appears and click OK. Using AXD EFI Tools In AXD EFI tools, the test controls and test selections are split across two panes.
ÂÂ “ Viewing the Hardware Profile” on page 28 ÂÂ “Shutting Down or Restarting the Xserve” on page 28 ÂÂ “ Viewing Saved Logs” on page 28 ÂÂ “ Taking Screen Shots” on page 29 Customizing AXD EFI Tools Test Settings You can customize AXD test settings in several ways by choosing which tests are run, whether to loop tests, and whether to stop or continue testing when an error occurs. To customize AXD EFI tools test settings: 1 In AXD EFI tools, select the test settings you want.
Clearing the Test Log The test log contains all test messages that have occurred during the current AXD session. If you quit AXD, the log is cleared. To clear the test log without quitting AXD, click Clear Test Data. Viewing the Hardware Profile The hardware profile lists all hardware components in the Xserve. You can view the hardware profile by choosing Hardware Profile > Display Hardware Profile. Shutting Down or Restarting the Xserve You can shut down or restart the Xserve in AXD EFI tools.
Taking Screen Shots You can take screen shots of AXD EFI tools, which are saved as BMP files in the root folder of the volume with AXD EFI tools installed. If you run AXD EFI tools from the Admin Tools disc, NetBoot disc image, or from a volume that is not in MS-DOS (FAT) format, you can’t take screen shots. For more information about formatting volumes, see “Setting Up a Storage Device for AXD Tools Installation” on page 12. To take a screen shot: mm In AXD EFI tools, press Command-Shift-3.
ÂÂ “ Viewing Logs” on page 32 ÂÂ “Setting Log Preferences” on page 33 ÂÂ “Shutting Down or Restarting the Xserve” on page 34 ÂÂ “Quitting AXD Mac OS X Tools While a Test is Running” on page 34 Customizing AXD Mac OS X Tools Test Settings You can customize AXD test settings in several ways by choosing which tests are run, whether to loop tests, and whether to stop or continue testing when an error occurs.
3 To run the test, click Start Testing. 4 When the test completes, a PASSED or FAILED message appears on screen. Click anywhere to close the message. If you stop the test before it completes, no message appears. Working with Test Groups You can create test groups based on your customized test settings. These are similar to templates because they allow you to reuse your test settings without having to change each setting individually. After choosing a test group, you can still change its settings.
Viewing Logs You can view the following types of logs in AXD Mac OS X tools: Log type Description Test All messages from tests run in the current AXD Mac OS X tools session. Hardware Info Listing and description of all installed hardware. System All of the logs that are also available in System Profiler (located in /Applications/Utilities/) You can also view logs stored on other volumes.
To do this Do this Clear logs Choose Logs > Clear current Log, or choose Logs > Clear All Logs. The name of the currently viewed log replaces current. Refresh logs Choose Logs > Refresh Current Log, or choose Logs > Refresh All Information Logs. Setting Log Preferences You can set up log preferences so that the AXD test logs are automatically saved to a file at a location you choose. AXD test logs are created every time you start a new AXD session.
To set log preferences: 1 In AXD Mac OS X tools, choose AXD > Preferences. 2 To automatically save test logs, select “Auto-save test log.” If you don’t select this option, you can’t perform the steps that follow. 3 To choose the location of the automatically saved log, click “Choose auto-save location,” select a location, and then click Open. 4 Configure the test log naming options. To do this Do this Ensure newly created log files don’t overwrite old Select “Use unique name.
Appendix AXD Tools Test Reference This reference describes all the tests available in AXD tools and gives estimates for how long the tests take to complete. The types of tests available depend on if you’re using AXD EFI tools or AXD Mac OS X tools, and on your Xserve model and configuration. Comparison of Available Tests The following table compares the tests available by component, depending on if you’re using AXD EFI tools or AXD Mac OS X tools.
Component tested Available in AXD EFI tools Available in AXD Mac OS X tools Notes Hard drive % % Different tests are available depending on the tool. Memory (simple) % % In AXD EFI tools, this tests only the first 2.5 GB of memory using a single CPU core. In AXD Mac OS X tools, this tests all memory using a single CPU core. Memory (multicore) % % In AXD EFI tools, this tests the first 2.5 GB of memory using all available CPU cores.
AXD EFI Tools Tests These tests are available if your Xserve is running AXD EFI tools. Startup Tests These tests run automatically when you start up AXD EFI tools. SMBIOS tests check to see if bad memory was detected and mapped out at Xserve startup. When the Xserve tests memory at start up, it automatically maps out bad memory. Mac OS X doesn’t see this mapped-out memory, so the non-SMBIOS memory tests don’t test it. The SMBIOS test reports these mapped-out DIMMS.
Boot ROM Tests Test Estimated completion time Description Boot ROM Checksum 1 second Verifies the Boot ROM checksum. Boot ROM FW GUID MAC Addr Checksum 1 second Verifies the Boot ROM FireWire GUID MAC address checksum. Ethernet Controller Tests The availability of Ethernet controller tests depends on the Enternet controller installed in the Xserve. Test Estimated completion time Description MAC Address Verification 1 second Verifies MAC address isn’t all FFs or 00s.
Memory Tests All memory tests are listed under Memory. These tests are described here. Simple Memory Tests Simple memory tests test the first 2.5 GB of memory. To test all memory, run extended memory tests. Even though simple memory tests don’t test all memory, run these tests to detect intermittent memory issues. In AXD EFI tools, all memory tests (simple, multicore, and extended) are grouped under Memory tests.
Test Estimated completion time Description Walking Spread Bit 32 5 minutes Walks 0b01 up and then walks 0b10 down memory. Walking Bit Flip 32 5 minutes Alternates words with walking 1 and walking 0, and then alternates with walking 0 and walking 1. Multicore Memory Tests Multicore memory tests test the first 2.5 GB of memory using all available CPU cores. In AXD EFI tools, all memory tests (simple, multicore, and extended) are grouped under Memory tests.
Extended Memory Tests Extended memory tests test all available memory. In AXD EFI tools, all memory tests (simple, multicore, and extended) are grouped under Memory tests. The availability of extended memory tests depends on the Xserve model you test. Note: The time required to complete memory tests correlates to the size of memory being tested. These estimates are based on testing 1 GB of memory.
Power Supply Tests Test Estimated completion time Description Good 1 second Checks if the power supply’s good bit is set. If it’s not set, this could indicate that the power supply isn’t seated well or is bad, or that there’s no AC connected. Quick 5 seconds This is available only if you have more than one power supply. This turns off the redundant power supplies so that only one power supply is used.
Video Controller Tests The availability of video controller tests depends on the video controller installed in the Xserve. Test Estimated completion time Description PCI-E 8 LinkWidth Verification 1 second Verifies PCI link width is 8. Framebuffer Address as Data 2 minutes Tests the framebuffer using framebuffer addresses as data. AXD Mac OS X Tests These tests are available if your Xserve is running AXD Mac OS X tools.
Ethernet Controller Tests The availability of Ethernet controller tests depends on the Enternet controller installed in the Xserve. Data loop tests can add to network traffic. Consider disconnecting from the network before running the data loop tests. 44 Test Estimated completion time Description MAC Address Verification 1 second Verifies MAC address is not all FFs or 00s. Ethernet ROM Checksum 1 second Verifies Ethernet ROM checksum is valid.
Fan Tests When AXD Mac OS X tools starts, it performs a hardware existence test. All fans found during this test can be tested individually using fan tests. Test Estimated completion time Description Verify Motor +/– 10%, 10 Reads High, 20 Low 2 minutes Verifies the minimum and maximum fan speeds. Sets the minimum and maximum builds within 10% of the threshold and then does 10 consecutive reads at the maximum and 20 at the minimum.
Test Estimated completion time Description Short Random Multi-block 2 minutes Performs a threaded, random multi-block read of random ranges of the target hard drive. This is not a full surface scan, but it will cause rapid seeking and reading of hard drive blocks. If a block can’t be read, an error occurs. This test is available for hard drives, not solid-state drives. SSD Threaded Media Scan Not available Scan’s the entire accessible area of a solid-state drive.
SMBIOS Memory Tests Test Estimated completion time Description SMBIOS Self-Test 1 second Checks the SMBIOS tables for 32-bit errors (type 18) and 64bit errors (type 33). Also verifies that the mapped-in DIMM size is appropriate for the slot it’s inserted into. If there’s a size mismatch, an error occurs. Test Estimated completion time Description ECC Error Count 1 second Reports the number of ECC errors, and then resets the count.
USB Tests Connect USB devices before running USB tests. Test Estimated completion time Description Presence 1 second Verifies that a USB device is connected. Video Controller Tests To run these tests, a display must be attached to any graphics cards being tested. The displays can’t be in sleep. For example, if you have two graphics cards, they both need a display attached and both displays must not be in sleep.
