What Can I Do If Controller Expansion Fails Because the Process Lasts for Over 24 Hours After the Controllers to Be Added Are Powered On?
Question
What can I do if controller expansion fails because the process lasts for over 24 hours after the controllers to be added are powered on?
Answer
If a controller expansion lasts for over 24 hours after the controllers to be added are powered on, the AD process in the storage system will be disabled. As a result, controllers in the cluster cannot communicate with each other, leading to a controller expansion failure. You can enable the AD process as follows:
An AD process is used for message forwarding among controllers during controller expansion.
- Log in to the CLI of any controller in the new controller enclosure.
- Run the change user_mode current_mode user_mode=engineer command to go to the engineer view.
- Run the change ad_process action=startup command to enable the AD process.
- For versions earlier than V500R007C60SPC300, the command for starting the AD process 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 the minisystem view to log in to controller A. SlotId is the slot number of controller A 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.
- For V500R007C60SPC300 and later versions, the command for starting the AD process is executed on any controller, and the AD process is enabled on all controllers in the controller enclosure.
- Run the show ad_process status command to check whether the status of the AD process is Online. If the status is Online, the AD process has been enabled.
For details, see the Advanced O&M Command Reference specific to your product model and version.