1.

/N0/SB0/P1 disabled - untest UltraSPARC-IV+, 1800MHz, 32M ECache

2.
3.
4.
5.

/N0/SB0/P1/B0/L0
/N0/SB0/P1/B0/L2
/N0/SB0/P1/B1/L1
/N0/SB0/P1/B1/L3

disabled
disabled
disabled
disabled

untest
untest
untest
untest

1024M
1024M
1024M
1024M

DRAM
DRAM
DRAM
DRAM

6. /N0/SB2/P2 disabled - untest UltraSPARC-IV+, 1800MHz, 32M ECache

7. /N0/SB2/P3 disabled - untest UltraSPARC-IV+, 1800MHz, 32M ECache
8. /N0/SB2/P2/B0/L0 disabled - untest 2048M DRAM
9. /N0/SB2/P2/B0/L2 disabled - untest 2048M DRAM
10. /N0/SB2/P2/B1/L1 disabled - untest 2048M DRAM
11. /N0/SB2/P2/B1/L3 disabled - untest 2048M DRAM
12. /N0/SB2/P3/B0/L0 disabled - untest 2048M DRAM
13. /N0/SB2/P3/B0/L2 disabled - untest 2048M DRAM
14. /N0/SB2/P3/B1/L1 disabled - untest 2048M DRAM
15. /N0/SB2/P3/B1/L3 disabled - untest 2048M DRAM
Action Plan :1)
a.
b.
2)
a.
b.
c.
d.
e.
f.

Enable the components using setls as bellow

setls -s enable -l /N0/SB0/P1 ( Example )
Apply the same to all the disabled components ( Listed above)
Capture the below commands op s
showchs
showenvironment
showlogs
showboards -p version ( to check the firmware level on the boards)
showcomponent
showboards -v

diagnostic-related information is provided in the Status column for a component.

Components that have a Failed or Disabled status are deconfigured from the syst
em. The Failed status indicates that the board failed testing and is not usable.
Disabled indicates that the board has been deconfigured from the system, because
it was disabled using the setls command or because it failed POST
Note Disabled components that have a POST status of chs cannot be enabled by usi
ng the setls command.
================================================================================
===========================
Once back from POST, enter the
e phone waiting of course.)

service

command at the LOM (with sun backline on th

lom>service
The use of service commands can be destructive and destabilize the
system.
Use of service mode is authorized only by personnel trained in its use.
Enter Password:
Invalid password.

HostID: 83129c1a
ScApp version: 5.20.2
RTOS version: 45
Read them the info and they will send you a password.
Once in service mode, unblacklist components as follows:
lom[service]>showchs -b
Component Status
--------------- -------/N0/SB0/P3 Faulty
/N0/SB0/P0 Faulty
/N0/SB0/P1 Faulty
/N0/SB2/P3 Faulty
/N0/SB2/P0 Faulty
/N0/SB4/P2/B0/D0 Suspect
/N0/SB4/P2/B0/D1 Suspect
/N0/SB4/P2/B0/D2 Suspect
/N0/SB4/P2/B0/D3 Suspect
/N0/SB4/P2/B1/D0 Suspect
/N0/SB4/P2/B1/D1 Suspect
/N0/SB4/P2/B1/D2 Suspect
/N0/SB4/P2/B1/D3 Suspect
lom[service]>setchs -s OK -r "This CPU believed to be good" -c /N0/SB0/P3
NOTE: If a component was marked Faulty, it will not be back in the configuratio
n until it is run through POST.
This can be accomplished by executing a setlkeyswitch on or DR operation. When p
erforming this action, monitor POST to assure that no errors are detected on thi
s newly reset device.
Always question the recent history of the machine and any maintenance activity w
hen you have a CHS disabled component, before proceeding to re-enable it. A word
of caution - do not just 'blindly' re-enable a component, since the system disa
bled it for a reason.
Example: POST fails test ID 6.1, with an error in like: ERROR: TEST=Memory Test
s,SUBTEST=Memory Addressing ID=61.1
In this situation, the CPU is failed in order to disable the memory it controls,
but the CPU is fine. It is the memory DIMM(s) which need to be replaced. For th
e case of bad memory, here is what you need to do:
- Use setchs to re-enable the cpu.
- Verify with showchs that the pending status is 'ok'.
- DR the SB out and replace the memory.
- DR the SB back in.
When you reinsert the SB, the local tests will be sufficiant to make the chs sta
tus 'current' vs 'pending'. You don't need to do a setkeyswitch off on the doma
in !
================================================================================
=================================
# fmadm faulty
STATE RESOURCE / UUID
-------- ----------------------------------------------------------------------

degraded dev:////ssm@0,0/pci@19,700000
47b86ff0-6743-ceff-ba0d-b452d09b0b65
-------- ---------------------------------------------------------------------degraded dev:////ssm@0,0/pci@19,700000/lpfc@1
47b86ff0-6743-ceff-ba0d-b452d09b0b65
-------- ---------------------------------------------------------------------degraded mod:///mod-name=lpfc/mod-id=54
47b86ff0-6743-ceff-ba0d-b452d09b0b65
-------- ---------------------------------------------------------------------degraded mod:///mod-name=pcisch/mod-id=25
47b86ff0-6743-ceff-ba0d-b452d09b0b65
-------- ---------------------------------------------------------------------NOTE: Once you see the faulty components, run the fmadm repair command to clear
the fault.
# fmadm repair dev:////ssm@0,0/pci@19,700000
NOTE: After you have run the repair command on each component that has been repl
aced, re-run the fmadm faulty command to ensure that the fault has been cleared.
If there are no faults, you will not see any output other than the column head
ings:
# fmadm faulty
STATE RESOURCE / UUID
-------- ---------------------------------------------------------------------#