Specific Issues And Workarounds - Fujitsu SPARC Enterprise T2000 Product Notes

Specific Issues and Workarounds

TABLE 1
Specific Issues and Workarounds
TABLE 1
CR ID Description
6997177 When you use the console command of ALOM to
log in to OS via the virtual console device, and then
use an editor such as vi to cut & paste a large amount
of data to a file, that virtual console may hang.
6949047 After the shutdown -i5 command was executed,
though Solaris OS normally terminates, system
power-off process may fail to complete.
Event example in failure:
# shutdown -i5 -g0 -y
Shutdown started.
JST 2011
Changing to init state 5 - please wait
Broadcast Message from root (console) on
XXXXXX Thu May 19 10:32:49...
THE SYSTEM erie0 IS BEING SHUT DOWN NOW ! !
!
Log off now or risk your files being
damaged
# svc.startd: The system is coming down.
Please wait.
svc.startd: 106 system services are now
being stopped.
May 19 10:33:38 XXXXXX syslogd: going down
on signal 15
svc.startd: The system is down.
syncing file systems... done
lists known issues. The table also lists possible workarounds for these issues.
Thu May 19 10:32:49
Important Information About the SPARC Enterprise T2000 Server
Workaround
Note - Fixed in System Firmware 6.7.12 or later.
None.
If you would like to cut & paste a large amount
of data to a file on OS, log in to OS via TELNET
or SSH and use the relevant editor.
When this event occurred, use the OS shutdown
command to normally stop the system and then
execute the ALOM reset operation.
For the execution example, see
May Hang When You Using vi Editor (CR
6997177)" on page 15.
Note - Fixed in System Firmware 6.7.12 or later.
This can be avoided according to the following
procedures.
1. From OS, execute the shutdown -i0 (init 0)
command
2. From ALOM, execute the poweroff
command
This event can be recovered by executing the
poweroff command from ALOM.
"Virtual Console
9