How Can I Clear Data of a To-Be-Replaced Controller?

This section describes how to clear data of a to-be-replaced controller. If you cannot log in to the controller, you cannot use commands to clear its data.

1. Log in to the controller you want to replace through a serial port or management network port, and go to the minisystem mode. You can use one of the following methods to go to the minisystem mode.
   • If the following information is displayed on the CLI, you have already entered the minisystem mode.

     Storage: minisystem>

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

     developer:/>minisystem 
     Storage: minisystem>

   • When "System is not ready, Please wait (Ctrl+c to exit or Input minisystem to minisystem mode)" is displayed on the CLI during the system power-on, 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 authorisation from the system administrator before you use this computer. Unauthorised 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. If you cannot log in to the controller to be replaced using the serial port or management network port, log in to another controller in the controller enclosure and run the sshtoremoteExt SlotId command to log in to the controller to be replaced. In the preceding command, SlotId is the controller'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.
   After the command is executed successfully, enter the password as prompted. Then, you are logged in to the system.

   Storage: minisystem> sshtoremoteExt 1
   Ssh to controller(SlotId=1) with admin......
   Warning: Permanently added '127.127.127.11' (ECDSA) to the list of known hosts.
   
   Authorized users only. All activities may be monitored and reported.
   password:

3. Run the showsysstatus command and obtain value of local node id from the command output. Then, check the value of Status corresponding to the local node id value, which is offline.
   If the value of Status is not offline, perform 2 again to go to the specified controller to be replaced.

   Storage: minisystem> showsysstatus
   Show system status
   admin:/diagnose>sys showcls
   mode      : normal
   status    : none
   node cfg  : 2
   node max  : 8
   group cfg : 1
   group max : 4
   product   : 0
   serial    : 210XXXXXXXXXXXXXX002
   WWN       : 0x210XXXXXXX9a020
   local node id  : 1
   normalNodeBitmap : 1 
   faultNodeBitmap  : 0 
   offlineNodeBitmap: 0
   standbyNodeBitmap: 0 
           id                   role                status               group                engine  
   -------------------- -------------------- -------------------- -------------------- --------------------
   0                    master               normal               0                    0 
   1                    slave                offline             0                    0 

4. In the minisystem mode, run the sys.sh clearnode -c command. Wait for the system's automatic data clearing. (Usually, it will take about 6 minutes, and the time in clearing the data does not exceed 30 minutes.)
   If "Clear local node successful." is displayed in the command output, the data is cleared. In this case, you do not need to restart the controller and can directly perform subsequent replacement operations.

   Storage: minisystem> sys.sh clearnode -c
   DANGER: You are going to perform a danger command, this behavior will clear all data on this system.
   1.This operation will cause service data loss and roll back cluster configurations. Have you read danger alert message carefully?(y/n)
   y
   2.This command brings irreversible results. The system cannot be restored to the original status after this command is executed. Are you sure you really want to perform the operation?(y/n)
   y
   DANGER: You are going to perform a danger command.
   Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
   Have you read danger alert message carefully?(y/n)
   y
   Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
   I have read and understand the consequences associated with performing this operation.
   admin:/diagnose>sys clearnode -c
   Start clear, local nid(Id: 1), it will takse about a few minutes, please wait ........................
   *******************  Clear Node info:  ****************** 
   Proc: XXXXXX, Result:       PASS 
   ... ...
   Proc: XXXXXX, Result:       PASS 
   Clear local node successful. If necessary, please continue to clear the other nodes in this engine.
   After that, you must restart the storage system to enable the command to take effect.
   admin:/diagnose>exit