No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The two ID of EXP cards on the disk enclosure are different after online upgrade

Publication Date:  2016-06-01 Views:  281 Downloads:  0

Issue Description

The storage array's software was online upgraded from V300R001C20 to V300R003C00SPC100, then the ID of A EXP board display as 001 and the ID of B EXP board display as 002. And on the second disk enclosure, the ID of A EXP baord display as 002 and the ID of B EXP board display as 001. 

Alarm Information

Handling Process

1.Confirm the old and current software version of the storage, there is such problem only when upgrade from the version which doesn't have the enclosure ID refresh function to a version which has enclosure ID refresh function. 

Below versions have the enclosure ID refresh function:
OceanStor V3 Series V300R001C20SPC100 and later versions
OceanStor V3 Series V300R002C10SPC200 and later versions
OceanStor V3 Series V300R003C00SPC100 and later versions

2.Confirm if expanded the new disk enclosure before.

3.Confirm the network topology of the disk enclosure: 
From the SAS interface of Controller A to each disk enclosures, check if the deepth and the display ID are consistent and also if it is consistent with controller B. 

Root Cause

There were two disk enclosures in the loop 0, added one more enclosure to DAE001. But DAE001 has been assign to the original disk enclosure, the new disk enclosure's ID will be assign to DAE002.
But after online upgrade from V3R1C20 to V3R3C00SPC100, it has disk enclosure ID refresh function in V3R3 during booting period. But the ID will be assigned by Controller A.
When Controller B was upgraded successfully and booting up, Controller A was still old version. So the enclosure ID will not be refreshed, all the disk enclosure EXP boards which connected to Controller B will keep the old ID.
After Controller A was upgraded successfully, the Controller A will refresh the enclosure ID, so all the disk enclosure EXP boards connected to Controller A will refresh the ID. But Controller A doesn't synchronize to Controller B, so that is why the ID of A and B EXP boards are different.


Reboot the Controller B:
Run 'change user_mode current_mode user_mode=developer' to enter the developer mode
Run 'reboot controller controller=0B' to reboot the Controller B