46 SPARC Enterprise T5120 and T5220 Servers Product Notes • October 2007
If you run consolehistory -e with a value greater than 1000 lines, you could
encounter that some of the SP commands appear to not function and report
Unknown or Unable to get value type of errors. If this happens, the only way to
recover is to reboot the SP (resetsc from the SP ILOM CLI). Refer to the Integrated
Lights Out Manager 2.0 User’s Guide for details on how to reboot the SP.
reset /SP With SP ILOM CLI SSH Connection Results in
Error Message (CR 6588999)
When you connect to the SP ILOM CLI with SSH and the SP is reset, you could see
an error message similar to the following:
This error can be ignored. The command actually succeeds and the SP is reset. When
the SP resets, you lose the SSH connection to the SP.
Missing Fan Board Module Output is Displayed in prtdiag
and ILOM CLI and BUI (CR 6595955)
If a component is not physically present on a system (such as the fan module), the
status field in the prtdiag -v (Environmental Status Section) output shows no
value and is blank.
Remove Boot and Run Options From consolehistory
Usage (RFE 6510082)
For users familiar with ALOM CMT and using the ALOM CMT compatibility CLI,
the help for the consolehistory command displays both a boot and a run option.
Both options result in the same output because ILOM makes no distinction between
the run and boot buffers.
SP useradd and usershow Errors Followed by Hang (CR
6585114)
During automated testing, the SP could encounter problems with useradd and
usershow commands, then soon after all login attempts could fail.
Workaround: AC power-cycle the system.
Performing hard reset on /SP failed
reset: Transport error - check errno for transport error
