3. Recable the system, as needed.
If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber
optic cables.
4. Complete the reinstallation of the controller module. The controller module begins to boot as soon as it is
fully seated in the chassis. Be prepared to interrupt the boot process.
a. With the cam handle in the open position, firmly push the controller module in until it meets the
midplane and is fully seated, and then close the cam handle to the locked position.
Do not use excessive force when sliding the controller module into the chassis to avoid
damaging the connectors.
The controller begins to boot as soon as it is seated in the chassis.
b. If you have not already done so, reinstall the cable management device.
c. Bind the cables to the cable management device with the hook and loop strap.
d.
When you see the message
Press Ctrl-C for Boot Menu, press Ctrl-C to interrupt the boot
process.
If you miss the prompt and the controller module boots to ONTAP, enter halt, and then
at the LOADER prompt enter
boot_ontap, press Ctrl-C when prompted, and then
boot to Maintenance mode.
e. Select the option to boot to Maintenance mode from the displayed menu.
Step 5: Run system-level diagnostics
After installing a new DIMM, you should run diagnostics.
Your system must be at the LOADER prompt to start System Level Diagnostics.
All commands in the diagnostic procedures are issued from the controller where the component is being
replaced.
1. If the controller to be serviced is not at the LOADER prompt, perform the following steps:
a. Select the Maintenance mode option from the displayed menu.
b.
After the controller boots to Maintenance mode, halt the controller:
halt
After you issue the command, you should wait until the system stops at the LOADER prompt.
During the boot process, you can safely respond y to prompts:
▪ A prompt warning that when entering Maintenance mode in an HA configuration, you must ensure
that the healthy controller remains down.
2. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to
function properly:
boot_diags
During the boot process, you can safely respond y to the prompts until the Maintenance mode prompt (*>)
appears.
61
To Next Page
Loading...
