Troubleshooting 32
Troubleshooting
This chapter describes common problems and probable causes, known issues, and provides general
troubleshooting advice.
To begin troubleshooting deployment problems, review the list of Known Issues below first to see if any
issues match the environment and symptoms. If none of the known issues apply, see “Common problems”
for issue diagnosis. For general troubleshooting advice, see “Basic troubleshooting techniques.”
Known issues
The following is a list of known issues associated with Solaris deployment and ProLiant servers.
Disabled PCI devices
Solaris stops responding or halts due to kernel “panic” when one or more PCI devices have been
disabled using ROM-Based Setup Utility (RBSU).
• OS releases affected—All
• Servers affected—All supported ProLiant servers
• Description—Disabling PCI devices in RBSU might cause Solaris to stop responding, halt due to
kernel panic, or produce other undesirable behavior.
• Workaround—Unless otherwise indicated, HP does not support using RBSU to disable PCI devices
while running Solaris. Add-on PCI devices should be removed from the system instead of disabling
them in RBSU.
Network configuration fails during interactive installation
Solaris installation fails during network configuration or Solaris is unable to configure network interfaces
after the post-installation reboot.
• OS releases affected—Solaris 10 1/06, 6/06, and 11/06
• Servers affected—All supported ProLiant servers
• Description—There is a known issue with network setup at installation time, and the installation might
fail, or Solaris will be unable to initialize the network after rebooting. This issue occurs if driver
updates (DUs) or installation time updates (ITU), such as the Smart Array driver, are added during
installation.
This issue is not reported if the extra drivers are installed into the miniroot beforehand, as they might
be for a network-based installation.
• Workaround—When prompted during the Solaris installation, select non-networked. After the
installation is complete and the system has rebooted, run sys-unconfig(1M). The system reboots and
the network can then be configured properly.
