After installing a new NVMEM battery, you should run diagnostics.
Before you begin
Your system must be at the LOADER prompt to get to the maintenance menu to start System Level Diagnostics.
About this task
All commands in the diagnostic procedures are issued from the controller where the component is being replaced.
- At the LOADER prompt, type boot_ontap menu.
- Select option 5 from the menu that appears to access the special drivers specifically designed for system-level diagnostics to function properly. During the boot process, you can safely respond y to the prompts until the Maintenance mode prompt (*>) appears.
- Run diagnostics on the NVMEM memory: sldiag device run -dev nvmem
- Verify that no hardware problems resulted from the replacement of the NVMEM battery: sldiag device status -dev nvmem -long -state failed
System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of failures resulting from testing the component.
- Proceed based on the result of the preceding step:
| If the system-level diagnostics tests... | Then... |
|---|
| Were completed without any failures | - Clear the status logs: sldiag device clearstatus
Verify that the log was cleared: sldiag device status The following default response is displayed: SLDIAG: No log messages are present. Exit Maintenance mode by typing halt The controller displays the LOADER prompt. - Boot the controller from the LOADER prompt: boot_ontap
- Return the controller to normal operation by typing: storage failover giveback -ofnode replacement_node_name
|
| Resulted in some test failures | Determine the cause of the problem:Exit Maintenance mode by typing halt After you issue the command, wait until the system stops at the LOADER prompt. - Verify that you have observed all the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system.
Fully seat the controller module you are servicing in the chassis. The controller module boots up when fully seated. - Boot the controller module you are servicing, interrupting the boot by pressing Ctrl-C when prompted to get to the LOADER prompt.
Type boot_ontap menu. - Select Boot to maintenance mode from the menu.
Exit Maintenance mode by entering the following command: halt After you issue the command, wait until the system stops at the LOADER prompt. - Rerun the system-level diagnostic test.
|