Diagnostics - (NF 8500R - Type 8681)


Diagnostics

Server problems can be caused by hardware, software, or a user error.
An example of a user error is pressing the wrong key on the keyboard.
The following tools are available to help identify and resolve hardware-related problems:


Diagnostic programs: The Diagnostics Utility program contains several server diagnostic programs.
These diagnostic programs are stored on electrically erasable programmable read-only memory (EEPROM).
These programs are the primary method of testing the major components of your server and some external devices.

Also, if you cannot determine whether a problem is caused by the hardware or by the software, you can run the diagnostic programs to confirm that the hardware is working properly.

Note: When you run the diagnostic programs, a single problem might cause several error messages.
When this occurs, work to correct the cause of the first error message.
After the cause of the first error message is corrected, the other error messages might not occur the next time that you run the test.


Power-on self-test (POST): When you turn on the server, it performs a series of tests to check the operation of server components and some of the options installed in the server.
This series of tests is called the power-on self-test or POST.


POST does the following:



If you have a power-on password or administrator password set, you must type the password and press Enter before POST will continue.

While the memory is being tested, the amount of available memory appears on the screen.
These numbers advance as the server progresses through POST and the final number that appears on the screen represents the total amount of memory available.
If POST finishes without detecting any problems, a single beep sounds and the first screen of your operating system or application program appears.

If POST detects a problem, more than one beep sounds, or an error message appears on your screen.

Note: A single problem might cause several error messages.
When this occurs, work to correct the cause of the first error message.
After the cause of the first error message is corrected, the other error messages usually will not occur the next time you run the test.


POST beep codes: POST generates beep codes to indicate successful completion or the detection of a problem.


Error messages: Error messages indicate that a problem exists;
they are not intended to be used to identify a failing part.
Troubleshooting and servicing of complex problems indicated by error messages should be performed by trained service personnel.

Hardware error messages that occur can be text, numeric, or both.
Messages generated by your software generally are text messages, but they also can be numeric.


POST error messages: POST error messages occur during startup when POST finds a problem with the hardware or detects a change in the hardware configuration.
For more information, see (below) 'Viewing the test log'.


System-monitoring messages: System-monitoring messages occur as the Advanced System Management PCI Adapter monitors critical system functions.


DIAGNOSTIC PROGRAMS 

Diagnostic error messages: Diagnostic error messages occur when a diagnostic test finds a problem with the server hardware.
These error messages are alphanumeric and they are saved in the test log.
For more information, see (below) 'Viewing the test log'.


Software-Generated error messages: These messages occur if a problem or conflict is found by an application program, the operating system, or both.
Messages are generally text messages, but they also can be numeric.
For information on these error messages, refer to the documentation that comes with your software.


POST error log: The POST error log contains a maximum of three error and warning messages issued during POST and all system status messages from the Advanced System Management PCI Adapter (service processor).
See 'POST error log' for information on how to view the POST error log.


System error log: The system error log contains all error and warning messages issued during POST, all system status messages from the Advanced System Management PCI Adapter (service processor), and all error messages issued during diagnostic testing.
See 'System error log' for information on how to view the system error log.


Option diskettes: An optional device or adapter can come with an Option Diskette.
Option Diskettes usually contain option-specific diagnostic test programs or configuration files.

If your optional device or adapter comes with an Option Diskette, follow the instructions that come with the option.
Different instructions apply depending on whether or not the Option Diskette is startable.


Diagnostic programs: This section includes useful information on running the diagnostic programs.
These programs are designed to test the IBM Netfinity 8500R server.
If you want to test a non-IBM product, refer to the information that comes with that product.

Notes:

  1.  When you run the diagnostic programs, a single problem might cause several error messages.
     When this occurs, work to correct the cause of the first error message.
     After the cause of the first error message is corrected, the other error messages usually will  not appear the next time that you run the test.
  2.  You can also run the diagnostic programs remotely with the Advanced System Management PCI Adapter  in conjunction with the Advanced System Management service capabilities of Netfinity Manager,  a terminal program, or a Web browser.
     Refer to the 'Advanced System Management Information'  section of this Server Library for more information.


Running the diagnostic programs: While you are running the diagnostic programs, pressing F1 displays help information. Pressing F1 from within a help screen provides a help index from which you can select different categories. Pressing Esc closes the Help window and returns to running the diagnostic programs.


Notes:

  1.  To run the diagnostic programs, you must start the server with the highest level password.
     That is, if you enter the power-on password and an administrator password is set, you cannot run  the programs.
     You can only view the error messages in the Test Log.
     You must enter the administrator password to run the diagnostic programs.
  2.  If the server stops during testing and you cannot continue, restart the server and try running the  diagnostic programs again.
     If the problem persists, have the system serviced.
  3.  If the diagnostic tests do not find a problem, but the problem persists during normal operations,  see 'Undetermined problems' and look for the problem symptom.
  4.  You might have to install a wrap connector on your active parallel or serial port to obtain  accurate test results for these ports.
     If you do not have a wrap connector, contact your IBM reseller or IBM marketing representative.
  5.  You might need a scratch diskette to obtain accurate test results when testing the diskette drive.
  6.  The keyboard and mouse (pointing device) tests assume that a keyboard and mouse are attached to the server.


Starting the diagnostic programs: To start the diagnostic programs:

  1.  Ensure that there is no diskette in the diskette drive.
     If the diskette drive contains a diskette, remove it.
  2.  Turn on the server and watch for the IBM logo screen.
     If the server is turned on already, shut down your operating system and restart the server.
  3.  After you start the server, several prompts appear on the IBM logo screen.  When the prompt Press F2  for Diagnostics appears, press F2.

     If a power-on password or administrator password is set, the server prompts you for it.
     Type in the appropriate password; then, press Enter.
     The Diagnostics Utility program window appears.

     After you start the Diagnostics Utility program, the following menu headings will appear at the top of the screen:

    1.  Use the cursor control keys (arrow keys) to scroll across the menu headings.
    2.  Press Enter to view the selections under the main headings.
    3.  Use the Up Arrow (  ) and Down Arrow (  ) keys to scroll down to the test that you want to run,  and press Enter.

      Note: If you select Run Normal Test or Run Quick Test from the Extended test menu, omit  steps 4 and 5.

    4.  Select the test components that you want to run.
    5.  Use these keys to tailor your selection:

      •  Space = Select a test component
      •  F1 = Help
      •  F2 = Options (a pop-up window appears)
      •  F3 = Test log
      •  F5 = Run all tests
      •  F10 = Deselect all
      •  Esc = Exit
      •  Enter = Run highlighted tests
      •  CTRL+Enter = Run tests in view

  4.  Select either Extended or Basic from the top of the screen.
  5.  Select the test that you want to run from the list that appears; then, follow the instructions on the screen.

     When the tests have completed, you can view the Test Log by selecting Utility from the top of the screen.

     Also, you can view server configuration information (such as system configuration, memory contents,  interrupt request (IRQ) use, direct memory access (DMA) use, device drivers, and so on) by selecting Hardware Info from the top of the screen.

  6.  When you are finished running the tests or viewing information in the Diagnostics Utility program, select Quit from the top of the screen.


If the hardware checks out OK, but the problem persists during normal server operations, a software error might be the cause.
If you suspect a software problem, refer to the information that comes with the software package.


Using the Online Manual: To obtain detailed descriptions of the available tests, press F1 twice to gain access to the Diagnostics Utility program Online Manual 

The Online Manual  also describes:



In addition, the Online Manual contains a glossary of terms.


Viewing the test log:

If you are already running the diagnostic programs, continue with step 1 in this procedure.
If you have not run the diagnostic programs, follow the instructions in (above) 'Starting the diagnostic programs' then, return here.

To view the Test Log:

  1.  Select Utility from the top of the screen.
  2.  Select View Test Log from the list that appears; then, follow the instructions on the screen.

Back to  Jump to TOP-of-PAGE

Please see the LEGAL  -  Trademark notice.
Feel free - send a Email-NOTE  for any BUG on this page found - Thank you.