Hello, everyone!
This case will share with you how to solve the failure to replace the faulty controller.
Symptoms
When SmartKit is used to replace a controller, the configuration file fails to be exported and the controller replacement is blocked.
Cause
Export logs and search for the keyword [SYNC]. Check whether the failure cause is that the CCDB fails to be exported and the startup disk is offline.
The controller is faulty and the boot disk is offline.
As a result, the configuration data cannot be exported and cannot be replaced using a tool.
Analysis
1. On DeviceManager, check the alarm of the faulty controller to be replaced. The error code is 0x4000cf05.
2018-11-26 05:50 0xF0CF0003 Major 2018-11-26 05:50 The controller (Controller Enclosure CTE0, controller B) is faulty with error code 0x4000cf05.
2. Run the following command to export the configuration file: Manually export the configuration data to the local storage device. Set the IP address to the IP address of the storage management port and the password to the storage password. The system returns "unknow" and the manual export fails.
export configuration_data ip=? user=admin password=xxx db_file=/home/permitdir/testdb.dat port=22 protocol=SFTP clean_device_file=yes
Solution
1. Run the show controller general command to confirm the active and standby controllers.
2. Enter the developer mode and run the change cluster master new_master_node=XX command to switch the master controller to another controller.
Use SmartKit to replace the controller again.
If the preceding problems occur on both controllers, manually replace the controller offline.
1. Check the path redundancy. No disk single-link alarm is generated. Bring the controller offline.
change controller offline controller=?
2. Remove the faulty controller and replace it.
3. After 30 minutes, run the show controller general command to check whether the dual controllers are normal and check whether the system status is normal.
This is my solution, how about yours? Go ahead and share it with us!
