Version Rollback
Rollback Rules
Sequence: Roll back the Ascend 910 firmware and then the driver of the Atlas 300T training card (model 9000).
If the upgrade fails and the firmware version is still the source version, you do not need to perform a rollback. A rollback is required in any of the following cases:
- A major fault occurred during the upgrade, and cannot be located and rectified within the specified time.
- After the upgrade is complete, the target version functions abnormally.
- The time left for completing the subsequent upgrade operations is insufficient. To avoid service interruption in peak hours, perform rollback promptly.
After the driver version rollback of a PCIe training card with Ascend 910 Pro B as the NPU, determine whether the device is available based on whether the NPU firmware version can be queried. For details about how to query the NPU firmware version, see 9.
Rollback Operations
- Determine the target version of the rollback.
You are advised to roll back to the source version.
- Roll back the version.
When you roll back to the specified version, the rollback procedure is the same as the upgrade procedure. Roll back all component versions to ensure version consistency. For details, see Upgrading Components.