EZOP/3/UPGRADE_FAIL
Possible Causes
The reasons for an EasyDeploy upgrade failure include but not limit to the following:
- 1: The file specified on the Commander or DHCP server does not exist.
- 2: The file server is unreachable or the password used to access the file server is incorrect.
- 3: The specified system software package already exists on the device.
- 4: When a user performs a batch upgrade, another user performs operations on the client, causing the downloaded file to be deleted mistakenly.
- 5: The Commander and clients did not have the shared key configured simultaneously.
- 6: Shared key authentication failed.
- 7: The URL of the file server fails to be converted to an IP address in pre-configured device deployment.
- 8: No file server is configured.
Procedure
- For causes 1 to 4: Modify the configuration according to the reason displayed in the log. In an unconfigured device deployment, pre-configured device deployment or faulty device replacement scenario, restart the device after modifying the configuration. In a batch upgrade scenario, issue the EasyDeploy upgrade command.
- For cause 5: Check whether both the Commander and client have a shared key configured. If not, configure the same shared key on the device that does not have a shared key configured.
- For cause 6: Check whether the Commander and client have the same shared key configured. If not, run the easy-operation shared-key cipher key-string command on the Commander and client to reconfigure the same shared key.
- For cause 7: Check whether the URL is correct. If the address is incorrect, modify it.
- For cause 8: Configure a file server.