| Sun Fire Entry-Level Midrange System Administration Guide
|
   
|
Maintenance and Troubleshooting
|
This chapter provides maintenance and troubleshooting information for a system administrator. The chapter describes the following topics:
Setting PCI Mode
This release of system firmware (5.19.0) supports the installation of both PCI and PCI-X cards in PCI-X I/O boards on Sun Fire entry-level midrange systems. By default, the firmware enables PCI-X mode on any I/O cards installed into a PCI-X I/O board.
| Note - Earlier generation (non-PCI-X) PCI I/O boards are ignored by the PCI-X software, and require no additional user administration.
|
|
Caution - While PCI-X I/O boards support both PCI-X and PCI I/O cards, you must use the forcepcicommand to specify the appropriate mode of operation for (non-PCI-X) PCI cards. The forcepcicommand enables you to change the mode from the default (PCI-X mode which has a maximum speed of 100 MHz), to PCI mode (which has a maximum speed of 66 MHz).
|
 To Set a Card in a PCI-X Board to PCI Mode
|
Use the forcepci board_specification on Command
The command in this example, changes the default operating mode of the card in board slot IB6/P0/B0 to PCI mode. The mode change takes effect after the next power cycle of the I/O assembly.
lom> forcepci IB6/P0/B0 on
|
To Display The Mode Status of a Card in a
PCI-X Board
|
Use the forcepci board_specification info Command
This command used in this example displays the mode status of the card in the specified PCI-X board slot.
lom> forcepci IB6/P0/B0 info
IB6/P0/B0 is in forced PCI mode
|
To Reset a Card in a PCI-X Board Slot to PCI-X Mode
|
Use the forcepci board_specification off Command
The command in this example changes the default operating mode of the card in board slot IB6/P0/B0 to PCI-X mode (the default mode). The mode change takes effect after the next power cycle of the I/O assembly.
lom> forcepci IB6/P0/B0 off
|
Device Mapping
The physical address represents a physical characteristic that is unique to the device. Examples of physical addresses include the bus address and the slot number. The slot number indicates where the device is installed.
You reference a physical device by the node identifier--agent ID (AID). The AID ranges from 0 to 31 in decimal notation (0 to 1f in hexadecimal). In the device path beginning with ssm@0,0 the first number, 0, is the node ID.
CPU/Memory Mapping
CPU/Memory board and memory agent IDs (AIDs) range from 0 to 23 in decimal notation (0 to 17 in hexadecimal). The system can have up to three CPU/Memory boards.
Each CPU/Memory board has four CPUs, depending on your configuration. Each CPU/Memory board has up to four banks of memory. Each bank of memory is controlled by one memory management unit (MMU), which is the CPU. The following code example shows a device tree entry for a CPU and its associated memory:
/ssm@0,0/SUNW/UltraSPARC-III@b,0 /ssm@0,0/SUNW/memory-controller@b,400000
|
where:
in b,0
- b is the CPU agent identifier (AID)
- 0 is the CPU register
in b,400000
- b is the memory agent identifier (AID)
- 400000 is the memory controller register
There are up to four CPUs on each CPU/Memory board (TABLE 10-1):
- CPUs with agent IDs 0-3 reside on board name SB0
- CPUs with agent IDs 8-11 on board name SB2, and so on.
TABLE 10-1 CPU and Memory Agent ID Assignment
|
CPU/Memory Board Name
|
Agent IDs On Each CPU/Memory Board
|
|
|
CPU 0
|
CPU 1
|
CPU 2
|
CPU 3
|
|
SB0
|
0 (0)
|
1 (1)
|
2 (2)
|
3 (3)
|
|
SB2
|
8 (8)
|
9 (9)
|
10 (a)
|
11 (b)
|
|
SB4
|
16 (10)
|
17 (11)
|
18 (12)
|
19 (13)
|
|
The first number in the columns of agent IDs is a decimal number. The number or letter in parentheses is in hexadecimal notation.
|
IB_SSC Assembly Mapping
TABLE 10-2 lists the types of I/O assembly, the number of slots each I/O assembly has, and the systems the I/O assembly types are supported on.
TABLE 10-2 I/O Assembly Type and Number of Slots
|
I/O Assembly Type
|
Number of Slots Per I/O Assembly
|
|
PCI
|
6
|
TABLE 10-3 lists the number of I/O assemblies per system and the I/O assembly name.
TABLE 10-3 Number and Name of I/O Assemblies per System
|
Number of I/O Assemblies
|
I/O Assembly Name
|
|
1
|
IB6
|
Each I/O assembly hosts two I/O controllers:
- I/O controller 0
- I/O controller 1
When mapping the I/O device tree entry to a physical component in the system, you must consider up to five nodes in the device tree:
- Node identifier (ID)
- I/O controller agent ID (AID)
- Bus offset
- PCI slot
- Device instance
TABLE 10-4 lists the AIDs for the two I/O controllers in each I/O assembly.
TABLE 10-4 I/O Controller Agent ID Assignments
|
Slot Number
|
I/O Assembly Name
|
Even I/O controller AID
|
Odd I/O Controller AID
|
|
6
|
IB6
|
24 (18)
|
25 (19)
|
|
The first number in the column is a decimal number. The number (or a number and letter combination) in parentheses is in hexadecimal notation.
|
The I/O controller has two bus sides: A and B.
- Bus A, which is 66 MHz, is referenced by offset 600000.
- Bus B, which is 33 MHz, is referenced by offset 700000.
The board slots located in the I/O assembly are referenced by the device number.
This section describes the PCI I/O assembly slot assignments and provides an example of the device path.
The following code example gives a breakdown of a device tree entry for a SCSI disk:
/ssm@0,0/pci@19,700000/pci@3/SUNW,isptwo@4/sd@5,0
|
| Note - The numbers in the device path are hexadecimal.
|
where:
in 19,700000
- 19 is the I/O controller agent identifier (AID)
- 700000 is the bus offset
in pci@3
isptwo is the SCSI host adapter
in sd@5,0
- 5 is the SCSI target number for the disk
- 0 is the logic unit number (LUN) of the target disk
This section describes the PCI I/O assembly slot assignments and provides an example of the device path.
TABLE 10-5 lists, in hexadecimal notation, the slot number, I/O assembly name, device path of each I/O assembly, the I/O controller number, and the bus.
TABLE 10-5 IB_SSC Assembly PCI Device Mapping
|
I/O Assembly Name
|
Device Path
|
Physical Slot Number
|
I./O Controller Number
|
Bus
|
|
IB6
|
/ssm@0,0/pci@18,700000/*@1
|
0
|
0
|
B
|
|
|
/ssm@0,0/pci@18,700000/*@2
|
1
|
0
|
B
|
|
|
/ssm@0,0/pci@18,700000/*@3
|
x
|
0
|
B
|
|
|
/ssm@0,0/pci@18,600000/*@1
|
5
|
0
|
A
|
|
|
/ssm@0,0/pci@18,600000/*@2
|
w
|
0
|
A
|
|
|
/ssm@0,0/pci@19,700000/*@1
|
2
|
1
|
B
|
|
|
/ssm@0,0/pci@19,700000/*@2
|
3
|
1
|
B
|
|
|
/ssm@0,0/pci@19,700000/*@3
|
4
|
1
|
B
|
|
|
/ssm@0,0/pci@19,600000/*@1
|
y
|
1
|
A
|
|
|
/ssm@0,0/pci@19,600000/*@2
|
z
|
1
|
A
|
where:
w = onboard LSI1010R SCSI controller
x = onboard CMD646U2 EIDE controller
y = onboard Gigaswift Ethernet controller 0
z = onboard Gigaswift Ethernet controller 1
and * is dependent upon the type of PCI card installed in the slot.
Note the following:
- 600000 is the bus offset and indicates bus A, which operates at 66 MHz.
- 700000 is the bus offset and indicates bus B, which operates at 33 MHz.
- *@3 is the device number. In this example @3 means it is the third device on the bus.
FIGURE 10-1 Sun Fire Entry-Level Midrange Systems IB_SSC PCI Physical Slot Designations for IB6
where * is dependent upon the type of PCI card installed in the slot.
For instance:
- Dual Differential Ultra SCSI card (375-0006) in Slot 4
- FC-AL card (375-3019) in Slot 3
- FC-AL card (375-3019) in Slot 2
These would generate device paths as follows:
/ssm@0,0/pci@19,700000/scsi@3,1
/ssm@0,0/pci@19,700000/scsi@3,1 (scsi-2)
/ssm@0,0/pci@19,700000/scsi@3,1/tape (byte)
/ssm@0,0/pci@19,700000/scsi@3,1/disk (block)
/ssm@0,0/pci@19,700000/scsi@3 (scsi-2)
/ssm@0,0/pci@19,700000/scsi@3/tape (byte)
/ssm@0,0/pci@19,700000/scsi@3/disk (block)
/ssm@0,0/pci@19,700000/SUNW,qlc@2 (scsi-fcp)
/ssm@0,0/pci@19,700000/SUNW,qlc@2/fp@0,0 (fp)
/ssm@0,0/pci@19,700000/SUNW,qlc@2/fp@0,0/disk (block)
/ssm@0,0/pci@19,700000/SUNW,qlc@1 (scsi-fcp)
/ssm@0,0/pci@19,700000/SUNW,qlc@1/fp@0,0 (fp)
/ssm@0,0/pci@19,700000/SUNW,qlc@1/fp@0,0/disk (block)
|
System Faults
A system fault is any condition that is considered to be unacceptable for normal system operation. When the system has a fault, the Fault LED ( 
) turns on. The system indicators are shown in FIGURE 10-2.
FIGURE 10-2 System Indicators
The indicator states are shown in TABLE 10-6. You must take immediate action to eliminate a system fault.
TABLE 10-6 System Fault Indicator States
|
FRU name
|
Fault indicator lit when fault detected
|
System Fault indicator lit on FRU fault*
|
Top Access lit on FRU fault1
|
Comments
|
|
System Board
|
Yes
|
Yes
|
Yes
|
Includes processors, Ecache and DIMMs
|
|
Level 2 repeater
|
Yes
|
Yes
|
Yes
|
|
|
IB_SSC
|
Yes
|
Yes
|
Yes
|
|
|
System Controller
|
No
|
Yes
|
Yes
|
IB_SSC fault LED lit
|
|
Fan
|
Yes
|
Yes
|
Yes
|
IB Fan fault LED lit
|
|
Power Supply
|
Yes (by hardware)
|
Yes
|
No
|
All power supply indicators are lit by the power supply hardware. There is also a predicted fault indicator. Power supply EEPROM errors do not cause degraded state as there is no indicator control.
|
|
Power distribution board
|
No
|
Yes
|
Yes
|
Can only be degraded.
|
|
Baseplane
|
No
|
Yes
|
Yes
|
Can only be degraded.
|
|
System indicator board
|
No
|
Yes
|
Yes
|
Can only be degraded.
|
|
System configuration card
|
No
|
Yes
|
No
|
|
|
Fan tray
|
Yes
|
Yes
|
No
|
|
|
Main fan
|
Yes
|
Yes
|
No
|
|
|
Media bay
|
No
|
Yes
|
Yes
|
|
|
Disk
|
Yes
|
Yes
|
No
|
|
Customer Replaceable Units
The following topics describe the field replaceable units, by system.
Sun Fire E2900 System
The following FRUs are considered to be ones on which you can deal with faults:
- Hard disks - hot-swappable
- PSUs (PS0/PS1/PS2/PS3) - hot-swappable
- CPU/Memory boards (SB0/SB2/SB4) - can be blacklisted if considered faulty
- Repeater boards (RP0/RP2) - can be blacklisted if considered faulty
If a fault is indicated on any other FRU or a physical replacement of blacklisted FRUs above is required, then Sun Service should be called.
Sun Fire V1280 System
The following FRUs are considered to be ones on which you can deal with faults:
- Hard disks - hot-swappable
- PSUs (PS0/PS1/PS2/PS3) - hot-swappable
- CPU/Memory boards (SB0/SB2/SB4) - can be blacklisted if considered faulty
- Repeater boards (RP0/RP2) - can be blacklisted if considered faulty
If a fault is indicated on any other FRU or a physical replacement of blacklisted FRUs above is required, then Sun Service should be called.
Netra 1280 System
The following FRUs are considered to be ones on which you can deal with faults:
- Hard disks - hot swappable
- PSUs (PS0/PS1/PS2/PS3) - hot-swappable
| Note - Only suitably trained personnel or Sun Service are permitted to enter the Restricted Access Location to hot-swap PSUs or hard disk drives.
|
- CPU/Memory boards (SB0/SB2/SB4) - can be blacklisted if considered faulty
- Repeater boards (RP0/RP2) - can be blacklisted if considered faulty
If a fault is indicated on any other FRU or a physical replacement of blacklisted FRUs above is required, then Sun Service should be called.
Manual Blacklisting (While Waiting for Repair)
The SC supports the blacklisting feature, which allows you to disable components on a board (TABLE 10-7).
Blacklisting provides a list of system board components that will not be tested and will not be configured into the Solaris Operating System. The blacklist is stored in nonvolatile memory.
TABLE 10-7 Blacklisting Component Names
|
System Component
|
Component Subsystem
|
Component Name
|
|
CPU system
|
|
slot/port/physical-bank/logical-bank
|
|
|
CPU/Memory boards (slot)
|
SB0, SB2, SB4
|
|
|
Ports on the
CPU/Memory board
|
P0, P1, P2, P3
|
|
|
Physical memory banks on
CPU/Memory boards
|
B0, B1
|
|
|
Logical banks on CPU/Memory boards
|
L0, L1, L2, L3
|
|
I/O assembly system
|
|
slot/port/bus or slot/card
|
|
|
I/O assembly
|
IB6
|
|
|
Ports on the
I/O assembly
|
P0, P1
|
|
|
Buses on the I/O assembly
|
B0, B1
|
|
|
I/O cards in the I/O assemblies
|
C0, C1, C2, C3, C4, C5
|
|
Repeater system
|
|
<slot>
|
|
|
Repeater board
|
RP0, RP2
|
Blacklist a component or device if you believe it might be failing intermittently or is failing. Troubleshoot a device you believe is having problems.
There are two system controller commands for blacklisting:
| Note - The enablecomponent and disablecomponent commands have been replaced by the setls command. These commands were formerly used to manage component resources. While the enablecomponent and disablecomponent commands are still available, it is suggested that you use the setls command to control the configuration of components into or out of the system.
|
The setls command updates only the blacklist. It does not directly affect the state of the currently configured system boards.
The updated lists take effect when you do one the following:
- Reboot the system.
- Use dynamic reconfiguration to configure the board containing the blacklisted component out of and then back into the system.
In order to use setls on the Repeater boards (RP0/RP2), the system first has to be shut down to Standby using the poweroff command.
When the setls command is issued for a Repeater board (RP0/RP2), the SC will be automatically reset to make use of the new settings.
If a replacement Repeater board is inserted, it is necessary to manually reset the SC using the resetsc command. See the Sun Fire Entry-Level Midrange System Controller Command Reference Manual for a description of this command.
Special Considerations for CPU/Memory Boards
In the unlikely event that a CPU/Memory board fails the interconnect test during POST, a message similar to the following appears in POST output:
CODE EXAMPLE 10-1 CPU/Memory Board Fails Interconnect Test
Jul 15 15:58:12 noname lom: SB0/ar0 Bit in error P3_ADDR [2]
Jul 15 15:58:12 noname lom: SB0/ar0 Bit in error P3_ADDR [1]
Jul 15 15:58:12 noname lom: SB0/ar0 Bit in error P3_ADDR [0]
Jul 15 15:58:12 noname lom: AR Interconnect test: System board SB0/ar0 address repeater connections to system board RP2/ar0 failed
Jul 15 15:58:13 noname lom: SB0/ar0 Bit in error P3_INCOMING [0]
Jul 15 15:58:17 noname lom: SB0/ar0 Bit in error P3_PREREQ [0]
Jul 15 15:58:17 noname lom: SB0/ar0 Bit in error P3_ADDR [18]
Jul 15 15:58:17 noname lom: SB0/ar0 Bit in error P3_ADDR [17]
|
A CPU/Memory board failing the interconnect test might prevent the poweron command from completely powering on the system. The system then drops back to the lom> prompt.
As a provisional measure, before service intervention is obtained, the faulty CPU/Memory board can be isolated from the system using the following sequence of commands at the SC lom> prompt:
lom>disablecomponent SBx
.
.
lom>poweroff
.
.
lom>resetsc -y
|
A subsequent poweron command should now be successful.
Recovering a Hung System
If you cannot log into the Solaris Operating System, and typing the break command from the LOM shell did not force control of the system back to the OpenBoot PROM ok prompt, then the system has stopped responding.
In some circumstances the host watchdog detects that the Solaris Operating System has stopped responding and automatically resets the system.
Assuming that the host watchdog has not been disabled (using the setupsc command), then the Host Watchdog causes an automatic reset of the system.
Also, you can issue the reset command (default option is -x which causes an XIR to be sent to the processors) from the lom> prompt. The reset command causes the Solaris Operating System to be terminated.
|
|
Caution - When the Solaris Operating System is terminated, data in memory might not be flushed to disk. This could cause a loss or corruption of the application file system data. Before the Solaris Operating System is terminated, this action requires confirmation from you.
|
To Recover a Hung System Manually
|
1. Complete the steps in Assisting Sun Service Personnel in Determining Causes of Failure.
2. Access the LOM shell.
See Chapter 3.
3. Type the reset command to force control of the system back to the OpenBoot PROM.
The reset command sends an externally initiated reset (XIR) to the system and collects data for debugging the hardware.
| Note - An error is displayed if the setsecure command has been used to set the system into secure mode. You cannot use the reset or break commands while the system is in secure mode. See the Sun Fire Entry-Level Midrange System Controller Command Reference Manual for more details.
|
4. This step depends on the setting of the Open Boot PROM
error-reset-recovery configuration variable.
- If the error-reset-recovery configuration variable is set to none, the system returns immediately to the OpenBoot PROM. When the OpenBoot PROM takes control, it takes actions based on the setting of the OpenBoot PROM
error-reset-recovery configuration variable. You can type any OpenBoot PROM command from the ok prompt, including rebooting the Solaris Operating System with the boot command. Also, you can force a core file with the sync command. The actions that can be configured by this variable might mean that the system will not return to the ok prompt.
- If the error-reset-recovery configuration variable is not set to none, the OpenBoot PROM automatically takes recovery actions.
- If the error-reset-recovery configuration variable is set to sync (default), the system generates a Solaris Operating System core file and reboots the system.
- If the OpenBoot PROM error-reset-recovery configuration variable is set to boot, the system is rebooted.
5. If the previous actions fail to reboot the system, use the poweroff and poweron commands to power cycle the system.
To power off the system, type:
To power on the system, type:
Moving System Identity
You might decide that the simplest way to restore service is to use a complete replacement system. In order to facilitate the rapid transfer of system identity and critical settings from one system to its replacement, the System Configuration Card (SCC) can be physically removed from the SCC Reader (SCCR) of the faulty system and inserted into the SCCR of the replacement system.
The following information is stored on the System Configuration Card (SCC):
- MAC addresses
- System controller 10/100 Ethernet Port
- Onboard Gigabit Ethernet port NET0
- Onboard Gigabit Ethernet port NET1
- Hostid
- Critical LOM configurations
- LOM password
- escape sequence
- SC network settings (IP address / DHCP / gateway, and so on)
- eventreporting level
- host watchdog enabled/disabled
- On/Standby enabled/disabled
- secure mode enabled/disabled
- Critical OpenBoot PROM configurations
- auto-boot?
- boot-device
- diag-device
- use-nvramrc?
- local-mac-address?
Temperature
One indication of problems might be overtemperature of one or more components. Use the showenvironment command to list current status.
TABLE 10-8 Checking Temperature Conditions Using the showenvironment Command
lom>showenviroment
Slot Device Sensor Value Units Age Status
---- --------- --------- ------ --------- ------- ------
SSC1 SBBC 0 Temp. 0 34 Degrees C 1 sec OK
SSC1 CBH 0 Temp. 0 41 Degrees C 1 sec OK
SSC1 Board 0 Temp. 0 22 Degrees C 1 sec OK
SSC1 Board 0 Temp. 1 22 Degrees C 1 sec OK
SSC1 Board 0 Temp. 2 28 Degrees C 1 sec OK
SSC1 Board 0 1.5 VDC 0 1.49 Volts DC 1 sec OK
SSC1 Board 0 3.3 VDC 0 3.35 Volts DC 1 sec OK
SSC1 Board 0 5 VDC 0 4.98 Volts DC 1 sec OK
/N0/PS0 Input 0 Volt. 0 - - 1 sec OK
/N0/PS0 48 VDC 0 Volt. 0 48.00 Volts DC 1 sec OK
/N0/PS1 Input 0 Volt. 0 - - 5 sec OK
/N0/PS1 48 VDC 0 Volt. 0 48.00 Volts DC 5 sec OK
/N0/FT0 Fan 0 Cooling 0 Auto 5 sec OK
/N0/FT0 Fan 1 Cooling 0 Auto 5 sec OK
/N0/FT0 Fan 2 Cooling 0 Auto 5 sec OK
/N0/FT0 Fan 3 Cooling 0 Auto 5 sec OK
/N0/FT0 Fan 4 Cooling 0 Auto 5 sec OK
/N0/FT0 Fan 5 Cooling 0 Auto 5 sec OK
/N0/FT0 Fan 6 Cooling 0 Auto 5 sec OK
/N0/FT0 Fan 7 Cooling 0 Auto 5 sec OK
/N0/RP0 Board 0 1.5 VDC 0 1.49 Volts DC 5 sec OK
/N0/RP0 Board 0 3.3 VDC 0 3.37 Volts DC 5 sec OK
/N0/RP0 Board 0 Temp. 0 20 Degrees C 5 sec OK
/N0/RP0 Board 0 Temp. 1 19 Degrees C 5 sec OK
/N0/RP0 SDC 0 Temp. 0 55 Degrees C 5 sec OK
/N0/RP0 AR 0 Temp. 0 45 Degrees C 5 sec OK
/N0/RP0 DX 0 Temp. 0 57 Degrees C 5 sec OK
/N0/RP0 DX 1 Temp. 0 59 Degrees C 5 sec OK
/N0/RP2 Board 0 1.5 VDC 0 1.48 Volts DC 5 sec OK
/N0/RP2 Board 0 3.3 VDC 0 3.37 Volts DC 5 sec OK
/N0/RP2 Board 0 Temp. 0 22 Degrees C 5 sec OK
/N0/RP2 Board 0 Temp. 1 22 Degrees C 5 sec OK
/N0/RP2 SDC 0 Temp. 0 53 Degrees C 5 sec OK
/N0/RP2 AR 0 Temp. 0 43 Degrees C 5 sec OK
/N0/RP2 DX 0 Temp. 0 49 Degrees C 5 sec OK
/N0/RP2 DX 1 Temp. 0 52 Degrees C 5 sec OK
/N0/SB0 Board 0 1.5 VDC 0 1.51 Volts DC 5 sec OK
/N0/SB0 Board 0 3.3 VDC 0 3.29 Volts DC 5 sec OK
/N0/SB0 SDC 0 Temp. 0 46 Degrees C 5 sec OK
/N0/SB0 AR 0 Temp. 0 39 Degrees C 5 sec OK
/N0/SB0 DX 0 Temp. 0 45 Degrees C 5 sec OK
/N0/SB0 DX 1 Temp. 0 49 Degrees C 5 sec OK
/N0/SB0 DX 2 Temp. 0 53 Degrees C 5 sec OK
/N0/SB0 DX 3 Temp. 0 48 Degrees C 5 sec OK
/N0/SB0 SBBC 0 Temp. 0 49 Degrees C 5 sec OK
/N0/SB0 Board 1 Temp. 0 24 Degrees C 5 sec OK
/N0/SB0 Board 1 Temp. 1 24 Degrees C 6 sec OK
/N0/SB0 CPU 0 Temp. 0 47 Degrees C 6 sec OK
/N0/SB0 CPU 0 1.8 VDC 0 1.72 Volts DC 6 sec OK
/N0/SB0 CPU 1 Temp. 0 47 Degrees C 6 sec OK
/N0/SB0 CPU 1 1.8 VDC 1 1.72 Volts DC 6 sec OK
/N0/SB0 SBBC 1 Temp. 0 37 Degrees C 6 sec OK
/N0/SB0 Board 1 Temp. 2 24 Degrees C 6 sec OK
/N0/SB0 Board 1 Temp. 3 24 Degrees C 6 sec OK
/N0/SB0 CPU 2 Temp. 0 49 Degrees C 6 sec OK
/N0/SB0 CPU 2 1.8 VDC 0 1.71 Volts DC 6 sec OK
/N0/SB0 CPU 3 Temp. 0 46 Degrees C 6 sec OK
/N0/SB0 CPU 3 1.8 VDC 1 1.72 Volts DC 7 sec OK
/N0/SB2 Board 0 1.5 VDC 0 1.51 Volts DC 6 sec OK
/N0/SB2 Board 0 3.3 VDC 0 3.29 Volts DC 6 sec OK
/N0/SB2 SDC 0 Temp. 0 55 Degrees C 6 sec OK
/N0/SB2 AR 0 Temp. 0 37 Degrees C 6 sec OK
/N0/SB2 DX 0 Temp. 0 47 Degrees C 6 sec OK
/N0/SB2 DX 1 Temp. 0 50 Degrees C 6 sec OK
/N0/SB2 DX 2 Temp. 0 53 Degrees C 6 sec OK
/N0/SB2 DX 3 Temp. 0 47 Degrees C 6 sec OK
/N0/SB2 SBBC 0 Temp. 0 48 Degrees C 6 sec OK
/N0/SB2 Board 1 Temp. 0 23 Degrees C 7 sec OK
/N0/SB2 Board 1 Temp. 1 24 Degrees C 7 sec OK
/N0/SB2 CPU 0 Temp. 0 45 Degrees C 7 sec OK
/N0/SB2 CPU 0 1.8 VDC 0 1.72 Volts DC 7 sec OK
/N0/SB2 CPU 1 Temp. 0 46 Degrees C 7 sec OK
/N0/SB2 CPU 1 1.8 VDC 1 1.73 Volts DC 7 sec OK
/N0/SB2 SBBC 1 Temp. 0 37 Degrees C 7 sec OK
/N0/SB2 Board 1 Temp. 2 24 Degrees C 7 sec OK
/N0/SB2 Board 1 Temp. 3 25 Degrees C 7 sec OK
/N0/SB2 CPU 2 Temp. 0 47 Degrees C 7 sec OK
/N0/SB2 CPU 2 1.8 VDC 0 1.71 Volts DC 7 sec OK
/N0/SB2 CPU 3 Temp. 0 45 Degrees C 7 sec OK
/N0/SB2 CPU 3 1.8 VDC 1 1.71 Volts DC 7 sec OK
/N0/IB6 Board 0 1.5 VDC 0 1.50 Volts DC 7 sec OK
/N0/IB6 Board 0 3.3 VDC 0 3.35 Volts DC 7 sec OK
/N0/IB6 Board 0 5 VDC 0 4.95 Volts DC 7 sec OK
/N0/IB6 Board 0 12 VDC 0 11.95 Volts DC 7 sec OK
/N0/IB6 Board 0 Temp. 0 29 Degrees C 7 sec OK
/N0/IB6 Board 0 Temp. 1 28 Degrees C 7 sec OK
/N0/IB6 Board 0 3.3 VDC 1 3.30 Volts DC 7 sec OK
/N0/IB6 Board 0 3.3 VDC 2 3.28 Volts DC 7 sec OK
/N0/IB6 Board 0 1.8 VDC 0 1.81 Volts DC 7 sec OK
/N0/IB6 Board 0 2.5 VDC 0 2.51 Volts DC 7 sec OK
/N0/IB6 Fan 0 Cooling 0 High 7 sec OK
/N0/IB6 Fan 1 Cooling 0 High 7 sec OK
/N0/IB6 SDC 0 Temp. 0 63 Degrees C 7 sec OK
/N0/IB6 AR 0 Temp. 0 77 Degrees C 7 sec OK
/N0/IB6 DX 0 Temp. 0 69 Degrees C 7 sec OK
/N0/IB6 DX 1 Temp. 0 73 Degrees C 8 sec OK
/N0/IB6 SBBC 0 Temp. 0 51 Degrees C 8 sec OK
/N0/IB6 IOASIC 0 Temp. 0 46 Degrees C 8 sec OK
/N0/IB6 IOASIC 1 Temp. 1 52 Degrees C 8 sec OK
|
Power Supplies
Each power supply unit (PSU) has its own LEDs as follows:
- Power/Active - lit if PSU is supplying main power; blinks if PSU is in Standby mode
- Faulty - lit if PSU has detected a fault condition and has turned off its main output
- Predictive Fail - lit if PSU has detected a pending internal fault but is still providing main output power (degraded PSU fan speed is the only trigger for this condition).
In addition there are two system LEDs labelled SourceA and SourceB. These show the state of the power feeds to the system. There are four physical power feeds and they are split into A and B.
Feed A supplies PS0 and PS1, feed B supplies PS2 and PS3. If either PS0 or PS1 receives input power then the SourceA indicator is lit. If either PS2 or PS3 receives input power then the SourceB indicator is lit. If neither of the supplies receives input power, the indicator is turned off.
These indicators are set on the basis of periodic monitoring at least once every 10 seconds.
Displaying Diagnostic Information
For information on displaying diagnostic information, see the Sun Hardware Platform Guide, which is available with your Solaris Operating System release.
Assisting Sun Service Personnel in Determining Causes of Failure
Provide the following information to Sun service personnel so that they can help you determine the causes of your failure:
- A verbatim transcript of all output written to the system console leading up to the failure. Also include any output printed subsequent to user actions. If the transcript does not show certain user actions, in a separate file include comments on what actions prompted particular messages.
- A copy of the system log file from /var/adm/messages from the time leading up to the failure.
- The following system controller commands output from the LOM shell:
- showsc -v command
- showboards -v command
- showlogs command
- history
- date
- showresetstate
- showenvironment