Upgrading from non-SHA256 signatures to SHA256 signature packages requires two upgrade cycles to update the signature files to SHA256 signatures for LP-auto-upgrade to use the SHA256 signatures for manifest file signature check.
Note
Refer to the latest version of the Extreme NetIron Release Notes for the list of images.
When upgrading from a release that does not support SHA256 signatures to a release that does, upgrade twice to the same release as follows. First upgrade to the release that supports SHA256 signatures. Reload the device. Then upgrade again to the same release that supports SHA256 signatures, and reload the device again. This ensures that the device will have the SHA256 signatures on the device.
Note
LP auto-upgrade is not supported in FIPS mode.