To Configure The System After A Jumpstart Installation - Fujitsu SPARC Enterprise T2000 Product Notes

Hide thumbs Also See for SPARC Enterprise T2000:
Table of Contents

Advertisement

Example of displaying the messages with the fmdump command:
# fmdump -v -u d79b51d1-aca0-c786-aa50-c8f35ea0fba3
TIME UUID SUNW-MSG-ID
Jan 27 22:01:58.8757 d79b51d1-aca0-c786-aa50-c8f35ea0fba3 SUN4-
8000-0Y 100% fault.io.fire.asic
FRU: hc://product-id=SUNW,SPARC-Enterprise-T2000/component=IOBD
rsrc: hc:///ioboard=0/hostbridge=0/pciexrc=0
Jan 27 22:17:36.5980 d79b51d1-aca0-c786-aa50-c8f35ea0fba3 SUN4-
8000-0Y
100% fault.io.fire.asic
FRU: hc://product-id=SUNW,SPARC-Enterprise-T2000/component=IOBD
rsrc: hc:///ioboard=0/hostbridge=0/pciexrc=0

To Configure the System After a JumpStart Installation

This procedure describes how to configure the SPARC Enterprise T2000 server after
a jumpstart installation so that erroneous fault messages are not reported.
1. Install the mandatory patches on the server.
2. Update the /etc/system file.
See
"Mandatory /etc/system File Entry" on page
3. Use the fmadm faulty command to list the UUID of each erroneous fault.
# fmadm faulty
4. Clear each fault that was listed in the preceding step.
# fmadm repair d79b51d1-aca0-c786-aa50-c8f35ea0fba3
5. Clear the persistent logs as shown in the following example.
# cd /var/fm/fmd
# rm e* f* c*/eft/* r*/*
Important Information About the SPARC Enterprise T2000 Server
3.
7

Advertisement

Table of Contents
loading

Table of Contents