Hi team!
Here's a case that Controller Enclosure IDs Become Inconsistent After a Disk Enclosure Is Connected to One Controller of a Storage System and Networking Is Being Changed Without Powering Off the Disk Enclosure.
Symptoms
After connecting a disk enclosure to a storage system, change the networking without powering off the disk enclosure. When connecting the disk enclosure to a controller, observe the LED indicators on the backplane of the disk enclosure.
The enclosure ID of the connected controller becomes different from the enclosure ID of the other controller.
After the disk enclosure is connected to both controllers, their enclosure IDs become the same.
Cause
The disk enclosure is not powered off when the networking is being changed, so the controller enclosure IDs remain unchanged.
In addition, the disk enclosure must be connected to one controller and then the other controller,
so the status of a connection to a single controller must exist.
In this status, the enclosure ID of the controller first connected is changed,
while the enclosure ID of the other one remains unchanged, resulting in inconsistent controller enclosure IDs.
Identification Method
1. Check whether the device version is earlier than V300R002C10.
If yes, go to the next step.
2. Observe the LED indicators of the two controllers on the backplane of the disk enclosure.
If the controller enclosure IDs become different after the disk enclosure is connected to one controller,
and then become the same after the disk enclosure is connected to both controller, this problem can be identified.
Solution
Step 1:
When changing the networking without powering off the disk enclosure, connect the disk enclosure to controller A first.
The system delivers a new enclosure ID to controller A, and controller B retains its current enclosure ID,
resulting in different controller enclosure IDs.
Then, connect the disk enclosure to controller B.
The enclosure IDs of the two controllers become the same.
Otherwise, go to the next step.
Step 2:
Check whether a single-link alarm is reported on the DeviceManager,
because controller B fails to receive the enclosure ID delivered by the system in the case of a single link.
If the alarm is reported, handle the problem by referring to the single-link alarm case.
Otherwise, go to the next step.
Step 3:
Collect related information and contact Huawei technical support.
Check After Recovery
The enclosure IDs of controller A and B are the same and the system is running properly.
