Clearing the Controllers That Fail to Be Added

Prerequisites

The cables have been removed from the storage system that has not been added to the cluster to isolate new controllers.

Procedure

1. Log in to the new controllers through their serial ports or management network ports and go to the minisystem mode. You can use one of the following ways to go to the minisystem mode.
   • If the following information is displayed, you are already in minisystem mode.

     Storage: minisystem>

   • Run the change user_mode current_mode user_mode=developer command to go to the developer view. Then run the minisystem command to go to the minisystem mode.

     developer:/>minisystem Storage: minisystem>

   • When the storage system is starting, System is not ready, Please wait (Ctrl+c to exit or Input minisystem to minisystem mode) is displayed on the CLI. Then run the minisystem command to go to the minisystem mode.

     Authorized users only. All activities may be monitored and reported. WARNING! The remote SSH server rejected X11 forwarding request. 
      
     WARNING: You have accessed the system. You are required to have a personal authorization from the system administrator before you use this computer. Unauthorized access to or misuse of this system is prohibited. 
      
     System is not ready, Please wait(Ctrl+c to exit or Input minisystem to minisystem mode).\minisystem     

2. Run the showsysstatus command. Check whether the number of controllers is correct and status of all controllers is normal.
   • If yes, add controllers again using SmartKit.
   • If no, go to 3.

3. In the minisystem mode of each controller, run the sys.sh clearnode -nf command. The system will automatically clear the controller. (The clearing process takes about 2 minutes generally and does not exceed 30 minutes.)
   • In the command output of each controller, if Clear node succeeded is displayed, the controllers are successfully cleared. Go to 4.
   • If a controller fails to be cleared, see introduction to the status of indicators in the Product Description specific to your product model and version to check whether the controller is powered on and whether the controller is running properly. If the status of indicators on the controller is normal, repeat 2. Otherwise, go to 6.
   • The sys.sh clearnode -nf command must be executed on each controller.
   • If you cannot log in to a controller (for example, controller A) using the serial port or management network port, log in to another controller in the controller enclosure (for example, controller B) and run the sshtoremoteExt SlotId command in minisystem mode to log in to controller A. SlotId is controller A's slot ID and its value ranges from 0 to N-1, where N indicates the maximum number of controllers that can be inserted in the current controller enclosure.
   • This operation will restore all services and configurations of the controller to the initial state.
   • This operation will initialize user passwords. For the default password of the system administrator, see the Security Configuration Guide specific to your product model and version.

4. After all controllers have been cleared, log in to any of them and run the sys.sh resetengine -nf command to reset all controllers in the current controller enclosure.
   • If the controller enclosure becomes normal after the controllers have been reset, go to 5.
   • If the controller enclosure fails to restore to normal, go to 6.

5. Use SmartKit to add controllers again.
   • If the expansion is successful, no further action is required.
   • If the expansion fails, go to 6.

6. Collect system logs and contact Huawei technical support.

   To collect system logs:

   • Log in to DeviceManager.

     If you can access the console, choose > Export Data. Click All logs under System Log.

     The warning dialog box is displayed. Select I have read and understand the consequences associated with performing this operation and click OK. The system starts collecting logs.

   • Log in to DeviceManager.

     If Failed to start the system is displayed, click Download Log to download system logs.

   • If the controller fails to be powered on, log in to the controller and go to the minisystem mode. Then run the os_backup_info.sh command to collect logs and access the log path to obtain the logs.