Go to main content

Oracle® Server CLI Tools for Oracle Solaris 11.3 User's Guide

Exit Print View

Updated: April 2018
 
 

fwupdate Error Codes

The following table lists the fwupdate command error codes.

You can also list the error codes using the fwupdate list error-codes command. See list Subcommand Overview for more information.

Code Number
Error Description
200
Invalid device type.
201
Invalid device target type..
202
Invalid device ID, please run \"fwupdate list all\" to verify id.
203
Reset of component failed.
204
Firmware check failed for component.
205
Firmware download failed for component.
206
Specified component and specified image type do not match.
207
Must specify an image file name when doing an update.
208
Could not read specified image file.
209
Reset of this component type is not supported.
210
Specified component type does not match devices type.
211
Must specify device to update.
212
Update canceled by user.
213
Firmware version information not available. Reset necessary to activate new firmware.
214
Version verification failed.
215
Final version is being reported the same as the starting version. Update may have succeeded, please check update documentation.
216
Missing or corrupt firmware file referenced by firmware metadata file.
217
Metadata file invalid or corrupt.
218
Metadata error. Prerequisite and priority settings conflict.
219
Power control option is not supported for pre-application.
220
Power control option is not supported for post-application.
221
Power Control option is not supported.
222
Requested component not available.
223
Can't verify version information, no XML provided.
224
Metadata does not include support for this host.
225
Could not identify host type.
226
A valid subcommand required.
227
Invalid option entered.
228
Must specify device to reset.
229
Cannot open file to write XML output.
230
Metadata XML file is required.
231
Invalid priority level entered.
232
Cannot read firmware metadata XML file.
233
Missing required command argument.
234
SP has not recovered in the allotted time limit after an update. The default time for the SP to recover after an update is 15 minutes or a value specified in the metadata XML file.