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 S2600 Controller Software Upgrade Fails and then the Controller Fails to be Logged in to, Upgraded

Publication Date:  2012-07-20 Views:  3 Downloads:  0

Issue Description

On the ISM, log in to the S2600 controller A to upgrade the controller software (from V100R001C02SPC010 to V100R002C01SPC001), but the upgrade fails and the ISM exits automatically. Log in to either controller on the ISM, but the login fails.  

Alarm Information


Handling Process

The S2600 in this example is a newly configured one and no configuration information is set; therefore, the following operations can be performed to synchronize the data in coffer disks:
Step 1  Open the handles of coffer disks (0, 1) and (0, 2). Wait at least 10 minutes and then remove the two hard disks.
Step 2  Insert the two coffer disks into each other’s slots.
The DB information on the coffer disks are automatically synchronized to the latest. Data on coffer disk (0, 0) is synchronized to coffer disk (0, 1) while data on coffer disk (0, 2) is synchronized to coffer disk (0, 3).

Root Cause

On the CLI, logging in to controller A fails but controller B succeeds. Run the showsys command and find that the controller versions are inconsistent, that is, controller A fails to be upgraded and remains in the previous version. Therefore, coffer disks need to be replaced to synchronize the controller versions.


The single controller upgrade failure is possible to occur on the ISM. Therefore, it is recommended to upgrade the S2600 dual controllers on the CLI.