This document provides instructions to clear an amber LED on an E-Series Controller Firmware drive that does not clear after a reboot or hardware replacement. It involves running shell commands with the drive's tray ID and component address to submit a control request and update the state machine. Running additional commands can help acquire the necessary IDs and understand the syntax.
This document provides instructions to clear an amber LED on an E-Series Controller Firmware drive that does not clear after a reboot or hardware replacement. It involves running shell commands with the drive's tray ID and component address to submit a control request and update the state machine. Running additional commands can help acquire the necessary IDs and understand the syntax.
This document provides instructions to clear an amber LED on an E-Series Controller Firmware drive that does not clear after a reboot or hardware replacement. It involves running shell commands with the drive's tray ID and component address to submit a control request and update the state machine. Running additional commands can help acquire the necessary IDs and understand the syntax.
This document provides instructions to clear an amber LED on an E-Series Controller Firmware drive that does not clear after a reboot or hardware replacement. It involves running shell commands with the drive's tray ID and component address to submit a control request and update the state machine. Running additional commands can help acquire the necessary IDs and understand the syntax.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 2
This article describes the steps to be performed to clear the amber LED on an E-Series Controller Firmware 7.
xx drive that does not clear up even after a reboot or a hardware replacement. Procedure Perform the following steps: 1. Run the following shell command: ssmSubmitDriveCR <trayID>,<componentAddress>,1,0,0,0,0,2,0,0,0 2. Run the following command to acquire the component address and the tray ID: Note: This is the address for the drive that is misreporting. ssmShowDrives Example output: [Storage Array] [0x0101 - Enclosure - Tray ID: 0, ELI: 0000000000000000, Status: Okay] 0x0106 - Drive - Status: Okay 0x0107 - Drive - Status: Okay 0x0108 - Drive - Status: Okay 0x0109 - Drive - Status: Okay 0x010a - Drive - Status: Missing 0x010b - Drive - Status: Missing 0x010c - Drive - Status: Missing 0x010d - Drive - Status: Okay 0x010e - Drive - Status: Okay 0x010f - Drive - Status: Okay 0x0110 - Drive - Status: Okay 0x0111 - Drive - Status: Okay 3. Run the command using the component address: ssmSubmitDriveCR 0,0x0106,1,0,0,0,0,2,0,0,0 In this example, the syntax will appear as above. 4. Run the following command to access the Help menu and understand the syntax: ssmSubmitDriveCR help Example output: Usage: ssmSubmitDriveCR <trayId>, <componentAddress>, <updateStateMachine>, <present>, <warning>, <online>, <identify>, <sar>, <saa>, <rebuild>, <rebuildAbort> Description: Submit a control request of a particular type to an EAC. Parameters: trayId - id of tray to submit to (invoke ssmShowTree) componentAddress - address of component to change (invoke ssmShowTree()) updateStateMachine - boolean indicating whether to update state machine 0 = bypass state sachine 1 = update state machine command(s) - Ex. sar = turn on/off Service Action Required LED: 0 = No Change (default) 1 = turn on 2 = turn off Example: submitXXXCR 0, 0x101, 1, ... Use ssmSubmitUnspecifiedCR to (re)set Swap & Bypass bits. Note: If issues persist, contact NetApp Support.
