HSCL 3xxx

This section lists the HSCL 3xxx error codes.

Note: The following error messages and recovery actions might include procedures that are not available on the DS8000® management console. If in doubt, contact the next level of support. If you are instructed to shut down the management console, then you must first verify that the customer is not currently performing DS8000 actions through the management console ESSNI connection.
Table 1. HSCL: 3xxx error codes
Error codes Message Recovery action
3006 The LED operation failed. Refer to the management console Operations Guide for more details. {0}
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3060 The following managed frames failed to initialize: {0}. If the error persists, contact your software support representative.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3070 The Frame lock action failed. Try the operation again.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3071 The Frame Guided Maintenance operation failed. Try the operation again. Try the operation again. If the problem persists, contact your hardware representative.
3072 The Frame FRU deactivation operation failed. Try the operation again. Try the operation again. If the problem persists, contact your hardware representative.
3073 The Frame FRU activation operation failed. Try the operation again. Try the operation again. If the problem persists, contact your hardware representative.
3074 The frame host information was not saved. Ensure the management console has enough disk space and the correct file permission and try the operation again. Ensure the /opt/hsc/data directory contains free disk space so that the management console can save the frame host information when needed.
3075 The frame host information that was found is not valid. Check the host information you provided and try the operation again. Check the frame host information that was entered into the application program to ensure the host name, password, and frame bulk power controller (BPC) internal identification are valid.
3076 An error has occurred while attempting the bulk power assembly connection operation. Please retry the operation. If the problem persists, contact your service representative.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3077 This operation is not allowed in the frame's current state. In order for this operation to be performed, at least one bulk power assembly (BPA) must be in the Standby state.
  1. Make sure that at least one bulk power assembly is in the Standby state, and try the operation again.
  2. If the problem persists, contact your hardware representative.
3078 The request to power on the drawer or planar for the frame failed. Try the request again. Try the request again. If the problem persists, contact your service provider.
3079 The request to add a drawer to the frame failed. Try the request again. Try the request again. If the problem persists, contact your service provider.
3080 The request to remove a planar from the frame failed. Try the request again. Try the request again. If the problem persists, contact your service provider.
3081 The request to remove a drawer from the frame failed. Try the request again. Try the request again. If the problem persists, contact your service provider.
3200 Unknown lock error. Contact your next level of support.
3201 Lock type not valid.
  1. Restart the management console.
  2. If the problem persists, contact your next level of support.
3202 Failed to acquire lock because of timeout.
  1. Restart the management console.
  2. If the problem persists, contact your next level of support.
3203 Nested lock type requested not valid.
  1. Restart the management console.
  2. If the problem persists, contact your next level of support.
3204 Lock not held.
  1. Restart the management console.
  2. If the problem persists, contact your next level of support.
3205 The managed system is busy, please try the operation again later. The managed system is busy doing another action. Wait and then retry the action.
3351 Code update process is not allowed by the management console. Check the code update status to verify the code update owner.
  1. Check the code update status to verify the code update owner.
  2. Retry the operation if management console is the code update owner.
  3. If the problem persists, contact your next level of support.
3352 Code update is already in progress by another management console or by the firmware. Verify that no other code update is in progress and retry the operation.
  1. Verify that no other code update operation is in progress and retry the operation.
  2. If the problem persists, contact your next level of support.
3353 Code update is not allowed to the specified side. Check the current flash side.
  1. Rebuild the managed operation. See MAP6620 Rebuilding managed system information for details.
  2. Check the power-on side from the managed system property panel and ensure you are not performing code update to the power-on side and then retry the operation.
  3. If the problem persists, contact your next level of support.
3354 Code update is already in progress from this management console. Ensure that no code update operation is in progress on the management console before retrying the operation.
  1. Ensure that no code update operation is in progress on the management console before retrying the operation.
  2. If the problem persists, contact your next level of support.
3355 The code update operation failed with return code {0}.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3356 The code update is not in progress by this management console. The start code update task should have been performed prior to code update complete by this management console.
  1. Ensure that the start code update task has been performed.
  2. Retry the operation.
  3. If the problem persists, contact your next level of support.
3357 The operation failed since another commit or long running code update is in progress.
  1. Ensure that no other code update operation is in progress.
  2. Retry the operation.
  3. If the problem persists, contact your next level of support.
3358 The delete lid operation is not allowed when a write LID is in progress.
  1. Ensure that no other code update operation is in progress.
  2. Retry the operation.
  3. If the problem persists, contact your next level of support.
3359 The code update operation failed since an invalid LID ID was specified.
  1. Check the Lid file ID and retry the operation with a valid lid file ID.
  2. If the problem persists, contact your next level of support.
3360 Error accessing the flash.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3361 An unknown error occurred during code update operation. Please retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3362 An unknown error occurred during reboot service processor. Please retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3363 The size of the LID number array is not the same as the Filename array. Ensure every LID number has a corresponding filename.
  1. Ensure every Lid number has a corresponding filename and retry the operation.
  2. If the problem persists, contact your next level of support.
3364 The read lid operation failed: {0}.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3365 Error: The following file(s) already exist(s): {0}.
  1. Ensure the files to read in the lids do not exists and retry the operation.
  2. If the problem persists, contact your next level of support.
3367 The input parameter arrays should all be of the same length. Check the lengths and retry the operation.
  1. Ensure the lengths of the input parameters are the same and retry the operation.
  2. If the problem persists, contact your next level of support.
3368 The Max write block size for the start code update did not get set. Please retry the operation.
  1. Retry the operation for the LIDs that failed.
  2. If the problem persists, contact your next level of support.
3370 The deletion of the following lid(s) failed: {0}.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3371 The write LID operation failed: {0}.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3372 The following LID filenames are not files: {0}.
  1. Ensure the lid files exist and retry the operation.
  2. If the problem persists, contact your next level of support.
3373 The following LID files are empty: {0}.
  1. Ensure that the LIDs are valid and retry the operation.
  2. If the problem persists, contact your next level of support.
3374 The following LID files do not exists: {0}.
  1. Ensure the lid files exist and retry the operation.
  2. If the problem persists, contact your next level of support.
3376 Invalid value returned from the service processor to indicate whether service partition firmware code lid updates are enabled or disabled.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3377 The start code update operation failed since an invalid component to update was specified. Please retry the operation with the a valid firmware component to update.
  1. Retry the operation with a valid firmware component to update.
  2. If the problem persists, contact your next level of support.
3378 The start code update operation failed since the managed system is not in the valid state. Check the state of the managed system and retry the operation.
  1. Check the state of the managed system and retry the operation.
  2. If the problem persists, contact your next level of support.
3379 There is a permanent error in flash, retry the operation and if the problem persists contact support.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3380 The Code Update operation failed since the managed system is not in the Power Off, Operating, or Standby state. Check the managed system's state and retry the operation.
  1. Check the state of the managed system and retry the operation.
  2. If the problem persists, contact your next level of support.
3381 The Complete Code Update operation failed since an invalid completion type was specified. Please retry the operation with a valid completion type.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3382 The Code Update is not in progress. The start code update operation needs to be performed before the Complete Code Update operation.
  1. Ensure the start code update operation is performed first.
  2. Retry the operation.
  3. If the problem persists, contact your next level of support.
3383 One or more LIDs are invalid in the primary LID list.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3384 For the partial read, the specified length was not read since the end of file flag was reached.
  1. Retry the operation with a valid length to be read.
  2. If the problem persists, contact your next level of support.
3385 Error: The following file(s) specified an invalid data for the Special LID Designator or the code update side: {0}.
  1. Retry the operation with valid special lid designator or the code update side.
  2. If the problem persists, contact your next level of support.
3386 The read partial/special LID operation failed, since writing to the file on the management console got an error. Check the log for the error and retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3387 An unknown error occurred during the open of firmware files. Please retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3388 The following fileid-subid specified an invalid open type: {0}.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3389 The following fileid-subid specified an invalid Force Flag: {0}.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3390 Error: The following files got an exception while trying to open the firmware file: {0}.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3391 The open firmware file operation failed: {0}.The open firmware file operation failed: {0}
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3392 An unknown error occurred during the write operation of firmware files. Please retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3393 An unknown error occurred during the close of firmware files. Please retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3394 An unknown error occurred during the get firmware status update operation. Please retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3395 An unknown error occurred during the start firmware update operation. Please retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3396 Failed to delete the partition with ID {0} since it is the service partition.
  1. Ensure the partition is not the service partition.
  2. Rebuild the managed system. See MAP6620 Rebuilding managed system information for details.
  3. If the problem persists, contact your next level of support.
3397 The secondary service processor is not available for the managed system.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3398 The code update service processor lock is already taken. Check that no other code update operation is running and retry the operation.
  1. Check that no other code update operation is in progress and retry the operation.
  2. If the problem persists, contact your next level of support.
3399 The code update service processor lock is not taken. Ensure the lock is taken before trying to release the code update service processor lock.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3400 The service processor that was specified as the target is not valid. Verify the service processor name and try the request again.
  1. Rebuild the managed frame. See MAP6620 Rebuilding managed system information for details.
  2. Try the task again.
  3. If the problem persists, contact your service provider.
3401 The get power domain operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3402 The get power domain power state operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3403 The set service lock operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3404 The reset service lock operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3405 The FRU level activate operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3406 The FRU level deactivate operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3407 The vary off power domain platform operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3408 The vary off power domain platform operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3409 The vary on power domain platform operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3410 The vary off power domain partition operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3411 The vary off power domain partition operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3412 The vary on power domain partition operation failed. Please retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3413 No Partitions are defined for the managed system. Check the user interface to see if partitions are defined and then retry the operation.
  1. Rebuild the managed frame. See MAP6620 Rebuilding managed system information for details.
  2. Try the task again.
  3. If the problem persists, contact your service provider.
3414 The start I/O concurrent maintenance operation failed. Retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3415 The I/O concurrent maintenance operation failed. Retry the operation.
  1. The I/O concurrent maintenance command failed. Retry the operation.
  2. If the problem persists, contact your next level of support.
3416 The get configuration ID operation failed. Retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3417 The set configuration ID operation failed. Retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3418 The get IO unit configuration ID and MTMS operation failed. Retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3419 The set IO unit MTMS operation failed. Retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3420 The set IO unit configuration ID operation failed. Retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3421 This operation is not allowed in the managed system's current state. Check the state of the managed system and retry the operation.
  1. Check the state of the managed system and retry the operation.
  2. If the problem persists, contact your next level of support.
3422 This operation cannot be completed because a conflicting concurrent maintenance operation is already in progress. Ensure that the other operation has completed and then retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3423 Invalid data was specified for this operation. Check the data and retry the operation.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3424 The I/O concurrent maintenance operation failed with return code: {0}.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
3500 The function completed successfully.  
3501 The operation failed because of a non-trivial reason.
  1. Restart the management console and retry the task.
  2. If the problem persists, contact your next level of support.
3503 Input error: The specified value is out of range or undefined. Contact your next level of support.
3504 An invalid input file or an error has occurred during an operation on the specified file.
  1. Reboot the system.
  2. If the problem persists, contact your next level of support.
3505 An error occurred while contacting the access control system. Please retry the operation.
  1. Reboot the system.
  2. If the problem persists, contact your next level of support.
350A Invalid input parameter(s).
  1. Check the input and try the task again.
  2. If the problem persists, contact your next level of support.
350B The user does not have the appropriate authority.
  1. Try the task again.
  2. Reboot the system.
  3. If the problem persists, contact your next level of support.
350C Input error: An invalid operation has been specified.
  1. Check the input and try the task again.
  2. Reboot the system.
  3. If the problem persists, contact your next level of support.
350D Input error: An invalid user ID has been specified.
  1. Check the input and try the task again.
  2. If the problem persists, contact your next level of support.
350E Input error: An invalid task has been specified.
  1. Check the input and try the task again.
  2. Reboot the system.
  3. If the problem persists, contact your next level of support.
350F Input error: The input resource is not valid or conflicts with the role in the operation.
  1. Check the input and try the task again.
  2. Reboot the system.
  3. If the problem persists, contact your next level of support.
  1. Check the input and try the task again.
  2. Reboot the system.
  3. If the problem persists, contact your next level of support.
3510 Input error: An invalid role or parent role has been specified.
  1. Check the input and try the task again.
  2. If the problem persists, contact your next level of support.
3511 Input error: An invalid subsystem has been specified.
  1. Check the input and try the task again.
  2. If the problem persists, contact your next level of support.
3512 Input error: An invalid option has been specified.
  1. Check the input and try the task again.
  2. If the problem persists, contact your next level of support.
3513 Input error: An invalid managed resource role name has been specified.
  1. Check the input and try the task again.
  2. Restart the management console.
  3. If the problem persists, contact your next level of support.
3514 The role specified already exists. A duplicate role name has been specified in the operation. Please select a different name.
3532 An unknown error, such as an exception, has occurred during the operation.
  1. Try the task again.
  2. Restart the management console.
  3. If the problem persists, contact your next level of support.
3533 Invalid operation. The input role is a system predefined role. The operation is not allowed.
3534 An invalid assignment has been specified. The resource type of the assignment is invalid or conflicts with the user's role. The resource type specified in the assignment is not valid or conflicts with the user role. Give the user a different assignment or role and retry the operation.
3563 The function specified is not available in the current release.