这篇博文介绍了如何从 ALOM 在 T1000/T2000 服务器上强制执行故障转储。
通常，当系统挂起时，需要收集故障转储。
在这种情况下，ALOM 中断命令是将系统置于 OBP（ok 提示符）的命令，然后允许用户运行“ok>sync”以保存故障转储。
但是，如果“break”命令不能将系统降到ok提示符，则该命令的“-D”选项可能允许用户直接获取coredump。
这是系统固件 6.3.0 或者更高版本中引入的新选项，并且还需要 Solaris [TM] 10 内核更新 118833-24 或者更高版本。

'break' 命令的选项：

-D: Forces a panic coredump of the managed system OS (not supported
by all OS versions).
-y: Instructs ALOM CMT to proceed without first asking the confirmation
question: Are you sure you want to send a break to the system [y/n]?
-c: Instructs ALOM CMT to connect to the system console after performing the operation.

例子：

sc> break -Dyc
SC Alert: SC Request to Dump core host.
Enter #. to return to ALOM.
100% done: 53847 pages dumped, compression ratio 5.54, dump succeeded
rebooting...

执行该命令时，我们将看到以下紧急消息和 FMA MSG-ID：SUNOS-8000-0G。

Nov  8 17:35:27 eslab63 unix: [ID 760255 kern.warning] WARNING: Panic - Error Descriptor 0x5  invalid in non-resumable error handler
Nov  8 17:35:27 eslab63 genunix: [ID 843051 kern.info] NOTICE: SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major
Nov  8 17:35:29 eslab63 unix: [ID 836849 kern.notice]
Nov  8 17:35:29 eslab63 panic[cpu0]/thread=2a10001fcc0:
Nov  8 17:35:29 eslab63 unix: [ID 400509 kern.notice] Unrecoverable hardware error
Nov  8 17:35:29 eslab63 unix: [ID 100000 kern.notice]
Nov  8 17:35:29 eslab63 genunix: [ID 723222 kern.notice] 000002a10001f6e0 unix:process_nonresumable_error+224 (2a10001f8d0, 0, 107c000, 40, 0, 5)Nov  8 17:35:30 eslab63 genunix: [ID 179002 kern.notice]   %l0-3: 0000000000000040 0000000003000000 0000000000000001 0000000000000000
Nov  8 17:35:30 eslab63   %l4-7: 000000000180c5c0 0000000100000000 00000000ffffffff 0000000000000001
Nov  8 17:35:30 eslab63 genunix: [ID 723222 kern.notice] 000002a10001f820 unix:ktl0+64 (0, 0, d77e, ffffffffffffffff, 0, 12)
Nov  8 17:35:30 eslab63 genunix: [ID 179002 kern.notice]   %l0-3: 000000000180c000 0000000000000000 0000000000001406 0000000001023534
Nov  8 17:35:30 eslab63   %l4-7: 0000000000000000 0000000000000000 0000000000000000 000002a10001f8d0
Nov  8 17:35:31 eslab63 genunix: [ID 723222 kern.notice] 000002a10001f970 unix:cpu_halt+b8 (0, 0, 300013c8000, 16, 180c000, 1)
Nov  8 17:35:31 eslab63 genunix: [ID 179002 kern.notice]   %l0-3: 000000000184ca08 0000000000000001 0000000000000002 0000000000000000
Nov  8 17:35:31 eslab63   %l4-7: 0000000000000000 0000000000000000 0000000000000000 000000000103af04
Nov  8 17:35:31 eslab63 genunix: [ID 723222 kern.notice] 000002a10001fa20 unix:idle+128 (1819c00, 10, 180c000, ffffffffffffffff, 1, 1818800)
Nov  8 17:35:32 eslab63 genunix: [ID 179002 kern.notice]   %l0-3: 0000000001846420 000000000000001b 0000000000000000 ffffffffffffffff
Nov  8 17:35:32 eslab63   %l4-7: 0000000000000000 0000000000000000 0000000000000000 000000000103af04
Nov  8 17:35:32 eslab63 unix: [ID 100000 kern.notice]
Nov  8 17:35:32 eslab63 genunix: [ID 672855 kern.notice] syncing file systems...
Nov  8 17:35:32 eslab63 genunix: [ID 733762 kern.notice]  1
Nov  8 17:35:34 eslab63 genunix: [ID 904073 kern.notice]  done
Nov  8 17:35:35 eslab63 genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c1t0d0s1, offset 429654016, content: kernel
Nov  8 17:36:18 eslab63 genunix: [ID 409368 kern.notice] 100% done: 53847 pages dumped, compression ratio 5.54,
Nov  8 17:36:18 eslab63 genunix: [ID 851671 kern.notice] dump succeeded