Troubleshooting 33
iLO boot hang
Solaris becomes unresponsive intermittently, but frequently at boot, just after the Solaris copyright banner
appears. If the console is viewed from iLO, the virtual console goes blank. A power cycle or reset is
required to restore the system.
• OS releases affected—Solaris 10 6/06
• Servers affected—All supported ProLiant servers
• Description—A change to the Solaris device enumeration during boot that conflicts with iLO was
introduced in the 6/06 release. It causes the system to become unresponsive intermittently during
boot.
This issue is also documented as Customer Advisory c00775941.
• Resolution—This issue has been corrected in the Solaris 10 11/06 release.
• Workaround—Disable iLO
AMD memory scrubber
System becomes unresponsive after a fixed amount of uptime (usually between 1 and 6 hours), regardless
of system load.
• OS releases affected—Solaris 10 6/06, 11/06, and 1/06 with patches
• Servers affected—HP ProLiant DL385, DL585, BL25p, BL35p, BL45p
• Description—Beginning with the Solaris 10 6/06 release and equivalent kernel patches, Solaris is
enabling the AMD™ memory scrubber. However, there is a known issue with AMD processors in
which the memory scrubber causes the system to become unresponsive with certain memory
configurations. First-generation AMD-based ProLiant servers with 4GB or more of system memory are
subject to this known issue.
A reproducible state of unresponsiveness after a constant amount of uptime regardless of system
load is an excellent indicator of this issue.
• Workaround—Disable the memory scrubber by adding the following line to /etc/system and
then reboot for the setting to take effect:
set cpu\.AuthenticAMD\.15:ao_scrub_rate_dram = 0
SNMP master agent
The System Management Homepage shows no data and other SNMP clients are unable to get data from
the Insight Management Agents.
• OS releases affected—Solaris 10 6/06, 11/06
• Servers affected—All supported ProLiant servers
• Description—A change was introduced with the Solaris 10 6/06 release that causes SNMP
subagents, such as the HP Insight Management Agents, to be unable to communicate with the master
agent when the system is running in 64-bit mode.
With the 6/06 release, Sun has introduced a 64-bit version of the master agent, which is started if
the system is running in 64-bit mode. Prior to this release, only a 32-bit version of the master agent
was available. The 64-bit master agent is unable to communicate with any subagent, including the
HP Insight Management Agents, which results in SNMP clients, such as the System Management
Homepage, being unable to collect MIB data provided by subagents. The 32-bit master agent does
not have this issue.