Enable and Verify Newly Installed DIMMs

Language:

Access the Oracle ILOM prompt.
Refer to Servers Administration for instructions.

Use the show faulty command to determine how to clear the fault.
- If show faulty indicates a POST-detected fault, go to Step 3.
- If show faulty output displays a UUID, which indicates a host-detected fault, skip Step 3 and go directly to Step 4.

Use the set command to enable the DIMM that was disabled by POST.
In most cases, replacement of a faulty DIMM is detected when the service processor is power cycled. In those cases, the fault is automatically cleared from the server. If show faulty still displays the fault, the set command will clear it.
```
-> set /SYS/MB/CM0/CMP/MR3/BOB1/CH0/D0 requested_config_state=Enabled
```
Note - Use requested_config_state rather than component_state, which existed in earlier versions of Oracle ILOM.

For a host-detected fault, perform the following steps to verify the new DIMM:
1. Set the virtual keyswitch to diag so that POST will run in Service mode.
```
-> set /HOST keyswitch_state=Diag
Set 'keyswitch_state' to 'Diag'
```
2. Power cycle the server.
```
-> stop /System
Are you sure you want to stop /System (y/n)? y
Stopping /System
-> start /System
Are you sure you want to start /System (y/n)? y
Starting /System
```
3. Check if the host has been powered off.
  Allow approximately one minute before performing this step. Type the show /HOST command. When the host is powered off, the console displays status=Powered Off.
4. Switch to the system console to view POST output.
  Watch the POST output for possible fault messages. The following output indicates that POST did not detect any faults:
```
-> start /SYS/console
...
0:0:0>INFO:
0:0:0>    POST Passed all devices.
0:0:0>POST:    Return to VBSC.
0:0:0>Master set ACK for vbsc runpost command and spin...
```
  Note - The server might boot automatically at this point. If so, go directly to . If the server remains at the OpenBoot prompt (ok) go to .
5. If the server remains at the OpenBoot prompt, type boot.
6. Return the virtual keyswitch to Normal mode.
```
-> set /HOST keyswitch_state=Normal
Set 'keyswitch_state' to 'Normal'
```
7. Switch to the system console and type the Oracle Solaris fmadm faulty command.
```
# fmadm faulty
```
  If any faults are reported, refer to the diagnostics instructions described in Check for Faults.

Switch to the Oracle ILOM command shell.

Run the show faulty command.

-> show faulty
Target              | Property               | Value
--------------------+------------------------+-------------------------------
/SP/faultmgmt/0     | fru                    | /SYS/MB/CMP0/MR1/BOB1/CH0/D0
/SP/faultmgmt/0     | timestamp              | Dec 14 22:43:59
/SP/faultmgmt/0/    | sunw-msg-id            | SUN4V-8000-DX
faults/0            |                        |
/SP/faultmgmt/0/    | uuid                   | 3aa7c854-9667-e176-efe5-e487e520
faults/0            |                        | 7a8a
/SP/faultmgmt/0/    | timestamp              | Dec 14 22:43:59 
faults/0            |                        |

If the show faulty command reports a fault with a UUID go to Step 7. If show faulty does not report a fault with a UUID, you are done with the verification process.

Switch to the system console and type the fmadm repair command with the UUID.
Use the same UUID that was displayed from the output of the Oracle ILOM show faulty command.
```
# fmadm repair 3aa7c854-9667-e176-efe5-e487e520
```