Mac Pro Apple Server Diagnostics User Guide For Version 3X108
KKApple Inc. © 2010 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. Apple, the Apple logo, AirPort, Exposé, FireWire, Mac, Macintosh, the Mac logo, and Mac OS are trademarks of Apple Inc., registered in the U.S. and other countries. Finder and the FireWire logo are trademarks of Apple Inc. The Apple logo is a trademark of Apple, Inc., registered in the U.S. and other countries.
Contents 5 7 9 9 9 10 10 Chapter 1: Overview and Requirements 11 11 13 14 14 16 18 Chapter 2: Setup and Installation 19 19 20 20 21 21 22 Chapter 3: Starting Up Server Diagnostics 24 24 25 27 27 28 29 30 30 30 Chapter 4: Using Server Diagnostics Overview of Server Diagnostics Configurations Requirements General Requirements Storage Device Requirements Local and Remote Requirements NetBoot Server Requirements Setting Up a Storage Device for Server Diagnostics Installation Installing Server Diagn
30 31 31 32 33 34 35 36 36 Viewing Saved Logs Taking Screenshots Using Server Diagnostics Mac OS X Customizing Server Diagnostics Mac OS X Test Settings Working with Test Groups Viewing Logs Setting Log Preferences Shutting Down or Restarting the Server Quitting Server Diagnostics Mac OS X While a Test Is Running 37 37 38 38 39 39 40 40 43 43 43 43 43 44 44 44 45 45 46 47 47 48 48 Appendix: Server Diagnostics Test Reference 4 Comparison of Available Tests Server Diagnostics EFI Tests Startup Tests
Overview and Requirements 1 Apple Server Diagnostics tests your server for hardware issues.
You can run Apple Server Diagnostics in Extensible Firmware Interface (EFI), which is referred to as Server Diagnostics EFI, or in Mac OS X Server, which is referred to as Server Diagnostics Mac OS X. By running Server Diagnostics EFI, you can diagnose hardware issues that prevent Mac OS X Server from successfully starting up. You can also run tests without interference from Mac OS X Server.
Overview of Server Diagnostics Configurations You can install and run Server Diagnostics in a variety of ways, so choose the method that best suits your needs. There are several options, each with advantages and disadvantages: Option Considerations Use the preinstalled Server Diagnostics EFI Advantages: You can use Server Diagnostics EFI. You don’t need a portable storage device. ÂÂ No installation is necessary. ÂÂ ÂÂ Disadvantages: You need physical access to the server.
Option Considerations Start up the Server Diagnostics EFI located on the Advantages: Admin Tools disc ÂÂ You can use Server Diagnostics EFI. ÂÂ You can use the same disc to test multiple servers. Disadvantages: ÂÂ ÂÂ You need network access to the server. You can’t save logs locally. Install Server Diagnostics Mac OS X on a portable Advantages: storage device ÂÂ You can use Server Diagnostics Mac OS X. ÂÂ You can use a single portable storage device to test multiple servers.
Requirements Before you can run Server Diagnostics, you must meet general, storage device, and local and remote requirements. General Requirements To run Server Diagnostics, you need the following: ÂÂ A Mac Pro with Mac OS X Server v10.6 or later installed ÂÂ The Mac OS X Server Install DVD and Admin Tools disc included with the Mac Pro (both discs should be version 10.
Local and Remote Requirements To run Server Diagnostics locally on the server, you need to connect a keyboard, mouse, and display. To run Server Diagnostics remotely, you need the following: ÂÂ A Macintosh computer with Mac OS X v10.6 or later installed. This computer is referred to as the host computer. ÂÂ A server with Mac OS X Server v10.6 or later installed. This server is referred to as the client server.
Setup and Installation 2 Before you can run Server Diagnostics, you must set up your testing environment and install Server Diagnostics. Make sure you meet Server Diagnostics requirements before attempting setup and installation. For information, see “Requirements” on page 9. Server Diagnostics EFI is preinstalled on the server. The instructions in this chapter show you how to install Server Diagnostics in a different location or set up a NetBoot server.
WARNING: The following instructions could erase all data on your storage device. Back up critical data before performing the following instructions. To create and format empty storage device volumes: 1 Insert the Mac OS X Server Install DVD. 2 Restart the server and hold down the server’s Option key while it restarts. 3 When a list of startup disks appears, select Mac OS X Server Install Disc and click the arrow button.
If you’re installing Server Diagnostics Mac OS X on a volume, select the volume and choose Mac OS Extended (Journaled). 11 Click Partition. 12 Choose Disk Utility > Quit Disk Utility, and then choose Mac OS X Installer > Quit Mac OS X Installer. After you finish setting up volumes, you can install Server Diagnostics EFI or Server Diagnostics Mac OS X.
5 If you want to connect a host computer directly to the server and the host computer doesn’t provide DHCP service on the port used to directly connect to the server, do the following: a Open TextEdit (located in /Applications/). b In a new file, enter an IP address that’s not in use by the host computer. For example, enter: 123.123.123.123 If TextEdit doesn’t open with a new blank file, choose File > New. c Choose Format > Make Plain Text. d Choose File > Save As.
If you perform this task to install Server Diagnostics Mac OS X on an internal volume on the server, you need administrator access to the server. If you perform this task to install Server Diagnostics Mac OS X on a portable storage device, you can use any computer you have administrator access to. Installing Server Diagnostics Mac OS X involves three steps: ÂÂ Install Mac OS X Server with minimal options selected. ÂÂ Copy Server Diagnostics Mac OS X from the Admin Tools disc to /Applications/.
10 Open a Finder window and drag the AppleServerDiagnostics.app file from /Diagnostics/ on the Admin Tools disc to the /Applications/ folder on the server. 11 If you’re setting up a client server, open a Finder window, select the /Applications/ folder, choose New Folder from the Action (gear) pop-up menu, and name the folder AppleServerDiagnosticsClient. Client servers are remotely controlled by host computers.
To set up a NetBoot server: 1 Open Server Admin (located in /Applications/Server/). 2 If the server that will host NetBoot isn’t listed, do the following: a Click the Add (+) button and choose Add Server. b Enter the IP address of the server in the Address field and enter the user name and password of the server administrator in the User Name and Password fields. c Click Connect. 3 Click the disclosure triangle for the server that will host NetBoot.
Deleting the Server Diagnostics NetBoot Image You can’t use System Image Utility to delete the Server Diagnostics NetBoot image. Instead, you must delete the Server Diagnostics NetBoot image in the NetBoot image folder, which is located at: /Volumes/volumename/Library/NetBoot/NetBootSP# Replace volumename with the name of the volume that you’re installing the Server Diagnostics NetBoot image onto. The number (#) varies, depending on whether you’re using several NetBoot volumes.
Starting Up Server Diagnostics 3 This chapter describes several methods that let you change the startup disk to the volume with Server Diagnostics installed. Before you start up Server Diagnostics, make sure everything is properly installed and configured. For information, see Chapter 2, “Setup and Installation.” Changing the Startup Disk Server Diagnostics is usually installed on a dedicated volume to minimize the risk of server processes interrupting the tests.
If you insert the Admin Tools CD in another computer and run Remote Install Mac OS X (located in /Applications/Utilities/ on the computer), you can hold down the Option key and choose the Administration Tools volume before starting up Mac OS X to run Server Diagnostics EFI from the disc. The Startup Disk pane of System Preferences can start up Server Diagnostics Mac OS X, but not Server Diagnostics EFI.
You must be able to authenticate as the root account to change the startup disk using the command-line interface. Note: The Terminal commands described in this task are case-sensitive, and must be entered as shown. To change the startup disk using the command-line interface: 1 Open Terminal (located in /Applications/Utilities/).
To temporarily change the startup disk at startup: 1 Restart the server. 2 While the server is restarting, hold down 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 haven’t erased the preinstalled Mac OS X Server volume with Server Diagnostics EFI, you can start up Server Diagnostics EFI by holding down the D key instead of the Option key.
4 After selecting a language, choose Utilities > Firmware Password Utility. 5 In Firmware Password Utility, click Change. 6 Deselect “Require password to change firmware settings,” and click OK, then authenticate when asked. 7 Choose Firmware Password Utility > Quit Firmware Password Utility. 8 Choose Mac OS X Installer > Quit Mac OS X Installer. 9 Click Startup Disk, select the startup disk with Mac OS X Server installed, and then click Restart.
Using Server Diagnostics 4 Server Diagnostics Mac OS X and Server Diagnostics EFI have different interfaces and functionality. This chapter describes how to use both sets of Server Diagnostics. Before you can use Server Diagnostics, make sure you’ve properly started up the tools. For information, see Chapter 3, “Starting Up Server Diagnostics.
The following table describes the three modes: Mode Description Automatically enters mode if Host The computer searches for servers that are on the same subnet and start Server Diagnostics in remote mode. When one is found, the host computer controls Server Diagnostics on the client server. You run Server Diagnostics Mac OS X and: Client The server can be controlled by a host computer. You’re running Server Diagnostics EFI and a host computer is on the same subnet or is directly connected.
To remotely test a client server: 1 On the host computer, open Server Diagnostics Mac OS X (typically located in /Applications/). 2 Choose from the following: ÂÂ If the host computer is a Mac Pro with Mac OS X Server installed and you’re logged in as root, when Server Diagnostics Mac OS X opens, a dialog asks you to choose which mode to enter. Choose “Connect to remote server” and click OK.
Testing the Local Server Using Server Diagnostics EFI To test the local server, make sure none of the computers on the same subnet as the server is running Server Diagnostics Mac OS X in host mode. If a computer on the same subnet is running Server Diagnostics Mac OS X tools in host mode, the server automatically enters client mode.
Using Server Diagnostics EFI In Server Diagnostics EFI, the test controls and test selections are split across two panes.
Customizing Server Diagnostics EFI Test Settings You can customize Server Diagnostics test settings by choosing which tests are run, whether to loop tests, and whether to stop or continue testing when an error occurs. To customize Server Diagnostics EFI test settings: 1 In Server Diagnostics EFI, select the test settings you want. To do this Do this Choose which tests are run Do any of the following: To select a test, select the checkbox next to the test.
Clearing the Test Log The test log contains all test messages that have occurred during the current Server Diagnostics session. If you quit Server Diagnostics, the log is cleared. To clear the test log without quitting Server Diagnostics, click Clear Test Data. Viewing the Hardware Profile The hardware profile lists all hardware components in the server. You can view the hardware profile by choosing Hardware Profile > Display Hardware Profile.
Taking Screenshots You can take screenshots of Server Diagnostics EFI, which are saved as BMP files in the root folder of the volume with Server Diagnostics EFI installed. If you run Server Diagnostics EFI from the Admin Tools disc, a NetBoot disc image, or a volume that isn’t in MS-DOS (FAT) format, you can’t take screenshots. To take a screenshot: mm In Server Diagnostics EFI, press Command-Shift-3. After you press Command-Shift-3, the system pauses for a few seconds and then takes the screenshot.
Customizing Server Diagnostics Mac OS X Test Settings You can customize Server Diagnostics 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 Server Diagnostics Mac OS X test settings: 1 In Server Diagnostics Mac OS X, select the test settings you want.
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. There are several test groups included with Server Diagnostics Mac OS X. These test groups stop when an error occurs, and they aren’t looped.
Viewing Logs You can view the following types of logs in Server Diagnostics Mac OS X: Log type Description Test All messages from tests run in the current Server Diagnostics Mac OS X session. Hardware Info Listing and description of all installed hardware. When you view logs in Server Diagnostics Mac OS X, a colored circle next to the log name indicates whether the log is able to be loaded.
Setting Log Preferences You can set up log preferences so the Server Diagnostics test logs are saved to a file at a location you choose. Server Diagnostics test logs are created when you start a Server Diagnostics session. When Server Diagnostics Mac OS X saves a log, it overwrites any log of the same name. Log preferences can customize the name of the log file so that the log files aren’t overwritten.
To set log preferences: 1 In Server Diagnostics Mac OS X, choose AppleServerDiagnostics > 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 Server Diagnostics Test Reference This reference describes the tests available in Server Diagnostics and gives estimates for how long the tests take to complete. The types of tests available depend on if you’re using Server Diagnostics EFI or Server Diagnostics Mac OS X, and on your server model and configuration. Comparison of Available Tests The following table compares the tests available by component, depending on if you’re using Server Diagnostics EFI or Server Diagnostics Mac OS X.
Component tested Available in Server Diagnostics EFI Available in Server Diagnostics Mac OS X Notes Hard drive % % Different tests are available, depending on the tool and whether solid state drives are installed. Memory (simple) % This tests all memory using a single CPU core. Memory (multicore) % This tests all memory using all available CPU cores. Memory (extended) % Tests all memory.
Test Estimated completion time Description Boot ROM Headers and Data Checksum 15 seconds Verifies headers and data checksum for all firmware volume regions throughout the Boot ROM. Verify BOF Flash with CRC 1 second Verifies that the low and high limits for testing sensors are correctly set. 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.
Hard Drive Tests When Server Diagnostics EFI starts, it performs a hardware existence test. Hard drives found during this test can be tested individually using hard drive tests. Test Estimated completion time Description Full Read 3 hours for a 1 TB drive Performs a DMA full-read scan at 1250 RPM. This checks the entire hard drive for slow-read failures. This test is available for hard drives, but not solid-state drives. Abbreviated Read 2 minutes Performs a DMA scan at 1250 RPM.
Test Estimated completion time Description Random 45 seconds Uses pseudo-random values. Block Checkerboard 32 15 seconds Alternates 32-bit words with all 1s and all 0s, and then with all 0s and all 1s. Bit Checkerboard 32 15 seconds Alternates bits with all 1s and all 0s, and then with all 0s and all 1s. Sequential Byte Block 32 32 minutes Fills bytes sequentially with patterns starting at 0x00 and ending at 0xFF. Walking One 32 15 minutes Walks 1s up and down memory.
Test Estimated completion time Description MP Walking Bit Flip 7 minutes Alternates words with walking 1 and walking 0, and then alternates words with walking 0 and walking 1. Check Hardware Errors 2 seconds Tests specific registers for memory related errors. Running this test at the end of memory testing may help catch memory errors generated during other memory tests. Extended Memory Tests Extended memory tests test all available 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. Test Estimated completion time Description L1 Cache Test 3 seconds Verifies that the L1 cache is good on all processor cores. Processor Tests Sensor Tests When Server Diagnostics EFI starts, it performs a hardware existence test.
Server Diagnostics Mac OS X Tests These tests are available if your server is running Server Diagnostics Mac OS X. Startup Tests These tests run when you start up Server Diagnostics Mac OS X. Test Estimated completion time Description Hardware Existence 1 second Compares a table of sensors and fans with what’s connected to the logic board. If a sensor or fan isn’t found, an error occurs. Sensors, and hard drives found can be individually tested using sensor, hard drive tests.
Bluetooth Tests Test Estimated completion time Description Bluetooth USB Interface 1 second Verifies USB interface between host and Bluetooth. MAC Address Verification 1 second Verifies MAC address isn’t all FFs or 00s. Bluetooth Power Cycle 10 seconds Verifies USB interface between host and Bluetooth after turning Bluetooth power off and then turning Bluetooth power on. Ethernet Controller Tests Data loop tests can add to network traffic.
Hard Drive Tests When Server Diagnostics Mac OS X starts, it performs a hardware existence test. Hard drives and solid-state drives found during this test can be tested individually using hard drive tests. Test Estimated completion time Description Threaded Surface Scan 3 hours for a 1 TB drive Scans the entire surface of a hard drive. This test is available for hard drives, but not solid-state drives. Threaded Surface Short Scan 2 minutes Scans the first 10 GB of a hard drive.
Sensor Tests When Server Diagnostics Mac OS X starts, it performs a hardware existence test. Sensors found during this test can be tested individually using sensor tests. Test Estimated completion time Description Sensor Reads 1 second Verifies that the sensor reads are within the preset sensor limits. SMC PID Sensor Tests The System Management Controller (SMC) monitors the Proportional Integral Derivative (PID) controller which controls several important temperature sensors.
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 that supports 1024 by 768 or higher resolution must be attached to graphics cards being tested. The displays can’t be in sleep mode. For example, if you have two graphics cards, they both need a display attached and both displays must not be in sleep mode.
