Toisolate an intermittent failure, it may be helpful to maintain a prtdiag history
log. Use prtdiag with the -l (log) option to send output to a log file in /var/adm.
Note - Refer to the prtdiag man page for additional information.
An example of prtdiag output follows. The exact format of prtdiag output
depends on which version ofthe Solaris operating environment is running on your
system.
prtdiagoutput:
ok /usr/platform/sun4u/sbin/prtdiag -v
System Configuration: Sun Microsystems sun4u Sun Enterprise 220R (UltraSPARC-
II 450MHz)
System clock frequency: 112 MHz
Memory size: 128 Megabytes
========================= CPUs ========================
Run Ecache CPU CPU
Brd CPU Module MHz MB Impl. Mask
--- --- ------- ----- ------ ------ ----
0 0 0 450 4.0 US-II 10.0
========================= IO Cards =========================
Bus
Brd Type MHz Slot Name Model
--- ---- ---- ---- ------------------ ----------------------
0 PCI 33 1 network-SUNW,hme
0 PCI 33 3 scsi-glm/disk (block) Symbios,53C875
0 PCI 33 3 scsi-glm/disk (block) Symbios,53C875
No failures found in System
===========================
====================== HW Revisions ======================
ASIC Revisions:
PCI: pci Rev 4
Cheerio: ebus Rev 1
System PROM revisions:
----------------------
OBP 3.23.0 1999/06/30 14:57 POST 2.0.2 1998/10/19 10:46
ok
Diagnostics and Troubleshooting 217