Apple Server Diagnostics User Guide For Version 3X106
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 9 9 9 10 11 Chapter 1: Overview and Requirements 12 12 14 15 16 18 20 Chapter 2: Setup and Installation 21 21 22 22 23 23 24 26 27 27 28 Chapter 3: Starting Up Server Diagnostics 29 29 30 31 32 32 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
33 34 34 35 35 35 36 36 37 38 39 41 41 Customizing Server Diagnostics EFI Test Settings Clearing the Test Log Viewing the Hardware Profile Shutting Down or Restarting the Server 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 42 42 44 44 44 45 45 45 45 48 48 49 49 49 49
Overview and Requirements 1 Apple Server Diagnostics tests your server for hardware issues.
You can test the server by running Server Diagnostics directly on the server. You can also run Server Diagnostics remotely on a computer with a network connection to the server. Note: This guide describes how to use Apple Server Diagnostics version 3X106, which is included on the Admin Tools disc (Mac OS X Server version 10.6 or later). 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.
Option Considerations Use the preinstalled Server Diagnostics EFI Advantages: You can use Server Diagnostics EFI You don’t need a portable storage device ÂÂ Server Diagnostics EFI typically loads faster than any other method ÂÂ No installation is necessary ÂÂ ÂÂ Disadvantages: ÂÂ ÂÂ ÂÂ ÂÂ ÂÂ Install Server Diagnostics EFI on a portable storage device Requires a server with Mac OS X Server 10.
Option Considerations Host a NetBoot server Advantages: You can use Server Diagnostics EFI You don’t need to install Server Diagnostics on an internal volume on the server or on a portable storage device ÂÂ You can use a single Server Diagnostics install image to test multiple servers ÂÂ If you’re testing an Xserve and have access to its front panel, you can start up Server Diagnostics without an input device connected to the Xserve ÂÂ ÂÂ Disadvantages: You need physical access to the server You need a
Option Considerations Install Server Diagnostics Mac OS X on an internal Advantages: volume ÂÂ You can use Server Diagnostics Mac OS X ÂÂ You don’t need physical access to the server to run Server Diagnostics Mac OS X remotely (if you have Apple Remote Desktop) Disadvantages: You need an empty volume on the server with 10 GB free ÂÂ You must install Mac OS X Server on the empty volume ÂÂ Requirements Before you can run Server Diagnostics, you must meet general, storage device, and local and remote requi
In order to You need Run Server Diagnostics EFI A volume on the server that has at least 30 MB free, but doesn’t have Mac OS X or Mac OS X Server installed Run Server Diagnostics Mac OS X An empty volume on the server with at least 10 GB free, which will be be used for a dedicated Mac OS X Server installation Test multiple servers and run Server Diagnostics EFI A USB 2.0 flash drive, or USB 2.
NetBoot Server Requirements To host Server Diagnostics EFI on a NetBoot server, your NetBoot server must: ÂÂ Have Mac OS X Server version 10.5 (10.5.8 or later recommended) installed. ÂÂ Be on the same subnet as the server being tested. ÂÂ Have 30 MB of hard disk space available for a Server Diagnostics NetBoot image.
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.
To create and format empty storage device volumes: 1 Insert the Mac OS X Server Install DVD. 2 Open the Install Mac OS X Server application, click Restart, and authenticate if necessary. The computer restarts and opens the Mac OS X Server Installer. 3 Select a language and click Next (right-arrow). 4 Choose Utilities > Disk Utility. 5 Select the storage device that you want to set up. Make sure you select a storage device, and not volumes within the storage device.
11 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.
c On the server, open a Finder window and select Remote Disc (under Devices on the left). Select the computer with the disc inserted. If the disc isn’t listed, click “Ask to use.” On the computer with the disc inserted, click Accept when a dialog appears asking if you want to give permission for your server to use your DVD drive. After doing this, you can use the disc as if it’s inserted in the server. 2 On the server, open AppleServerDiagnosticsEFI.pkg (located in /Diagnostics/ on the disc).
b On the computer with the optical drive, open System Preferences and click Sharing. Select “DVD or CD Sharing.” c On the server, open a Finder window and select Remote Disc (under Devices on the left). Select the computer with the disc inserted. If the disc isn’t listed, click “Ask to use.” On the computer with the disc inserted, click Accept when a dialog appears asking if you want to give permission for your server to use your DVD drive.
b On the computer with the disc inserted, open Remote Install Mac OS X (located in /Applications/Utilities/). c Continue through the Remote Install Mac OS X assistant, selecting the inserted disc and the network connection that’s on the same subnet as the server. d Restart the server and hold down the Option key while it restarts. e When a list of startup disks appears, select Mac OS X Server Install Disc and click the arrow button.
8 Open a Finder window and drag the AppleServerDiagnostics.app file from /Diagnostics/ on the Admin Tools disc to the /Applications/ folder on the server. 9 If you’re setting up a client server, open a Finder window, select the /Applications/ folder, and choose New Folder from the Action (gear) pop-up menu. Name the folder AppleServerDiagnosticsClient. Client servers are remotely controlled by host computers. 10 Open System Preferences (located in /Applications/).
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, click the Add (+) button and choose Add Server. Enter the IP address of the server in the Address field, enter the user name and password of the server administrator in the User Name and Password fields, and then click Connect. 3 Click the disclosure triangle for the server that will host NetBoot. 4 If NetBoot isn’t listed, select the server and click Settings.
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,” on page 12. 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 need to be able to authenticate as the root account in order 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/).
For information about disabling the firmware password, see “Disabling the Firmware Password” on page 26. 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 the Xserve EFI requires a password, you won’t be able to start up a NetBoot image using the front panel. You need to disable the firmware password before you can use the front panel. To disable the password, you must be able to start up Mac OS X Server on the Xserve. To use the Xserve front panel to start up a Server Diagnostics EFI NetBoot image: 1 Turn off the Xserve. 2 Hold down the system identifier button and press the on/standby button.
5 Press the system identifier button repeatedly until the lower-left light turns on. Lower-left light comes on. 6 While 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 Server Diagnostics EFI NetBoot disk image. After you run Server Diagnostics EFI and restart, the Xserve starts up from its default startup volume.
e When a list of startup disks appears, select Mac OS X Server Install Disc and click the arrow button. If it isn’t listed and you’re connecting to the computer over AirPort, select the AirPort network in the pop-up menu under the startup disk list. 2 After selecting a language, choose Utilities > Firmware Password Utility. 3 In Firmware Password Utility, click Change. 4 Deselect “Require password to change firmware settings,” and click OK. Authenticate when asked.
2 Enter the following: sudo systemsetup -setkernelbootarchitecture x86_64 If you’re asked to authenticate, authenticate as a user with administrator privileges. Temporarily Starting Up Mac OS X Server in 32-Bit Mode You can override the default configuration and start up Mac OS X Server in 32-bit mode. The server reverts to 64-bit mode the next time you restart it. To start up Mac OS X Server in 32-bit mode: 1 Use System Preferences to start up from the volume with Server Diagnostics Mac OS X installed.
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,” on page 21.
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 either: 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. Local The server runs all tests locally.
To remotely test a client server: 1 On the host computer, open Server Diagnostics Mac OS X (typically located in /Applications/). 2 If the host computer is an Intel-based Xserve or a Mac mini 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.
For information about how to temporarily change the startup volume while starting the computer, see Chapter 3, “Starting Up Server Diagnostics,” on page 21. When Server Diagnostics EFI starts up and doesn’t find a host computer, it enters local mode. Testing the Local Server Using Server Diagnostics Mac OS X To test the local server, you must log in as root. If you don’t log in as root, Server Diagnostics Mac OS X automatically enters host mode.
ÂÂ Shut down the server Detailed status Test controls Test Selections list Test Test category Test log Select All and Deselect All buttons For more information about Server Diagnostics EFI, see the following sections. 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 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. ÂÂ To select a specific test within a category of tests, click the disclosure triangle next to the category, and then select individual tests. ÂÂ To select all tests, click Select All. ÂÂ To remove all tests, click Deselect All.
Shutting Down or Restarting the Server You can shut down or restart the server in Server Diagnostics EFI. To shut down or restart the server: mm Click Shut Down or Restart. Viewing Saved Logs When you start up Server Diagnostics EFI from a volume in MS-DOS (FAT) format, it automatically creates a log of its test results in the /AppleServerDiagnosticsLogs/ folder of the volume with Server Diagnostics EFI installed. This log is continually updated as tests complete.
Using Server Diagnostics Mac OS X Server Diagnostics Mac OS X changes based on whether you’re running it locally, as a client, or as a host. In client mode, you can’t change test settings, select different tests, or shut down or restart the server. Therefore, the test log uses most of the window. In local and host mode, you can access all Server Diagnostics Mac OS X features in the main window.
To do this Do this Choose which tests are run In the Test Selections list, do the following: To select a test, select the checkbox next to the test. ÂÂ To select a specific test within a category of tests, click the disclosure triangle next to the category, and then select individual tests. ÂÂ To select all tests, click the Select All (+) button. ÂÂ To remove all tests, click the Deselect All (–) button.
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. Test group Test selections Default All memory, fan, hard drive, sensor, SMC PID sensor, and power supply tests. Ethernet MAC address verification and ROM checksum verification. Quick Test All sensor tests. You can also export a test group to a file.
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. Color Status No circle You haven’t loaded the log during this Server Diagnostics session, or the log hasn’t been created yet. Yellow The log didn’t load. This usually occurs when there isn’t any data in the log. Green The log loaded. To view logs: 1 Open Server Diagnostics Mac OS X. 2 If tests are currently running, wait for them to complete or stop them.
If you use all of the naming options, the log is saved as: AppleServerDiagnostics_serialnumber_mode_autosave_log_date_ethernetMACaddress uniquename.txt The appended values use this format: Value Format Example date DD_Mon_Year 15_Jul_2009 ethernetMACaddress ##_##_##_##_##_## 01_23_45_67_89_ab uniquename -# -1 The unique name is appended only if a file with the same name exists.
Shutting Down or Restarting the Server If you’re running Server Diagnostics Mac OS X on the local server or on a host computer, you can shut down or restart the server by clicking Shut Down or Restart. If the server is in client mode, you can’t shut down or restart the server locally. Quitting Server Diagnostics Mac OS X While a Test is Running If you try to quit Server Diagnostics Mac OS X while a test is running, you won’t be able to print or save any logs from the current Server Diagnostics session.
This reference describes all 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 Ethernet controller % % Different tests are available depending on the tool. % Fan Hard drive % % Different tests are available depending on the tool. Memory (simple) % % In Server Diagnostics EFI, this tests only the first 2.5 GB of memory using a single CPU core. In Server Diagnostics Mac OS X, this tests all memory using a single CPU core.
Server Diagnostics EFI Tests These tests are available if your server is running Server Diagnostics EFI. Startup Tests These tests run automatically when you start up Server Diagnostics EFI. SMBIOS tests check to see if bad memory was detected and mapped out at server startup. When the server tests memory at startup, 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 server. Test Estimated completion time Description MAC Address Verification 1 second Verifies MAC address isn’t all FFs or 00s.
Even though simple memory tests don’t test all memory, you can run these tests to detect intermittent memory issues. In Server Diagnostics EFI, all memory tests (simple, multicore, and extended) are grouped under Memory tests. Note: The time required to complete memory tests correlates to the amount of memory being tested. These estimates are based on testing 2 GB of memory. 46 Test Estimated completion time Description Address as Data 5 seconds Tests memory using the memory address as data.
Multicore Memory Tests Multicore memory tests test the first 2.5 GB of memory using all available CPU cores. In Server Diagnostics EFI, all memory tests (simple, multicore, and extended) are grouped under Memory tests. Note: The time required to complete memory tests correlates to the amount of memory being tested. These estimates are based on testing 1 GB of memory.
Test Estimated completion time Description Extended Memory Test P00F 5 seconds Tests memory using pattern 0. This fails if an error occurs. Extended Memory Test P01F 5 seconds Tests memory using pattern 1. This fails if an error occurs. Extended Memory Test P02F 5 seconds Tests memory using pattern 2. This fails if an error occurs. Extended Memory Test P03F 5 seconds Tests memory using pattern 3. This fails if an error occurs.
Sensor Tests When Server Diagnostics EFI starts, it performs a hardware existence test. All 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.
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 automatically when you start up Server Diagnostics Mac OS X. SMBIOS tests check to see if bad memory was detected and mapped out at server startup. When the server 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.
Bluetooth Tests Test Estimated completion time Description Bluetooth USB Interface 2 seconds Verifies USB interface between host and Bluetooth. MAC Address Verification 2 seconds 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.
Fan Tests When Server Diagnostics Mac OS X 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.
Even though these tests don’t test all memory, run these tests to detect intermittent memory issues. After the first 2.5 GB of memory is tested, the memory test then tests for ECC errors. When an ECC error occurs, memory catches the problem and fixes it. The test detects the number of memory fixes and reports them. 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.
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. 54 Test Estimated completion time Description OpenGL Point 10 seconds Verifies video controller using a 2D point test. OpenGL Line 10 seconds Verifies video controller using a 2D line test.
