A Disk or Riser Card Upgrade Stops Upon a Controller Switchover

Symptoms

1. A disk or riser card upgrade is performed using the CLI.

2. The primary controller is switched to another controller during the upgrade (due to an unexpected reset of the primary controller or other exceptions).

3. The upgrade result is not displayed on the CLI, as shown in the following figure.

   

Alarm Information

N/A

Possible Causes

1. The primary controller is unexpectedly reset (such as Oops or oom).

2. Network connections are normal before the upgrade, but the connection between the primary controller and external gateway becomes abnormal during the upgrade. Therefore, the storage array switches the primary controller to another controller that can connect to the gateway.

Identification Method

1. Verify that the upgrade result is not displayed on the CLI.

2. Log in to a controller using the CLI. On the CLI, go to the developer mode and then minisystem mode.

3. Run the showsysstatus command to find the primary controller. For example, controller 0 is the primary controller, as shown in the following figure.

   

4. Log in to the primary controller using the CLI. On the CLI, go to the developer mode and then minisystem mode.

5. Run the showsystrace command to check whether a flow whose ID is 4 exists. If the flow exists, query the corresponding Date Time information. If the time is later than the upgrade start time, this fault can be identified.

   

Troubleshooting Procedure

Collect storage array logs to find out the reason why the primary controller is switched.

• If the controller switchover is irrelevant to the upgrade, run the upgrade command again.

• If the controller switchover is triggered by the upgrade, stop the upgrade.

Check After Recovery

N/A

Applicable Versions

OceanStor V3 series V300R001

OceanStor V3 series V300R002