HP ProLiant DL145 G3 Server - Manual (Page 54)

Troubleshooting 54
Errors are displayed in the error log
Action: Follow the information provided in the error log, and then refer to the operating system
documentation.
Problems occur after the installation of a service pack
Action: Follow the instructions for updating the operating system (" Operating system updates " on page
53 ).
You are unable to bind NICs during the Protocols Interview with a Factory-Installed Novell
NetWare 5 operating system
Action: Be sure the packet receive buffers are set high enough. Toggle over to the console during the
Protocols Interview and adjust these values to a higher setting that allows you to bind the NICs. A
minimum setting of 50 buffers per port is recommended, and the maximum setting should be 125 more
than the minimum. To make the setting changes:
1. Type the following commands at the System Console screen (where XXX is the new numeric value):
Set Minimum Packet Receive Buffers=XXX
Set Maximum Packet Receive Buffers=XXX
2. Add the commands to the STARTUP.NCF file.
NOTE: When gigabit NICs are installed, the minimum buffers should be set to at least 500,
and the maximum to at least 2000.
During installation of Sun Solaris, the system locks up or a panic error occurs
Action: Disable ACPI support in Sun Solaris. Refer to the Sun website ( http://www.sun.com ) for
documentation on how to disable ACPI.
Restoring to a backed-up version
If you recently upgraded the operating system or software and cannot resolve the problem, you can try
restoring a previously saved version of the system. Before restoring the backup, make a backup of the
current system. If restoring the previous system does not correct the problem, you can restore the current
set to be sure you do not lose additional functionality.
Refer to the documentation provided with the backup software.
When to reconfigure or reload software
If all other options have not resolved the problem, consider reconfiguring the system. Before you take this
step:
1. Weigh the projected downtime of a software reload against the time spent troubleshooting
intermittent problems. It may be advantageous to start over by removing and reinstalling the problem
software.
2. Be sure the server has adequate resources (processor speed, hard drive space, and memory) for the
software.
3. Be sure the server ROM is current and the configuration is correct.
4. Be sure you have printed records of all troubleshooting information you have collected to this point.