A Storage System Is Successfully Upgraded But an Alarm Indicating that a Controller Cannot Be Monitored Exists

Problem Description

A storage system is successfully upgraded but an alarm indicating that a controller cannot be monitored exists in DeviceManager.

Symptom

A storage system is successfully upgraded. All nodes work properly. However, an alarm indicating that a controller cannot be monitored exists in DeviceManager.

Possible Causes

An abnormal reset or power-off occurred during the upgrade.

Fault Diagnosis

1. Check whether the upgrade path is as follows:
   • The upgrade path for an OceanStor 18000 series storage system is from V100R001C10 or earlier to V100R001C20 or later.
   • The upgrade path for an OceanStor T series storage system is from V200R002C10 or earlier to V200R002C20 or later.
   • The upgrade path for an OceanStor V3 series storage system is from V300R001C00 or earlier to V300R001C10 or later.
2. After the system is upgraded, run the show upgrade package command on the CLI to check whether the current version is the target version.
3. On the CLI, run the show controller general command to check whether the controller status is normal.
4. In DeviceManager, check whether there is an alarm indicating that a controller cannot be monitored.

Solution

Clear the alarm manually.

Check After Recovery

No such alarms exist on DeviceManager.

Applicable Versions

• OceanStor 18000 series V100R001C20 or later
• OceanStor T series V200R002C20 or later
• OceanStor V3 series V300R001C10 or later