| HSCL3006 |
The LED operation failed. Refer to the HMC Operations Guide for more details.
{0} |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3060 |
The following managed frames failed to initialize:
{0}. If the error persists, contact your software service representative. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3070 |
The Frame lock action failed. Try the operation
again. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3071 |
The Frame Guided Maintenance operation failed. Try
the operation again. |
Try the operation again. If the problem persists,
contact your hardware representative. |
| HSCL3072 |
The Frame FRU deactivation operation failed. Try
the operation again. |
Try the operation again. If the problem persists,
contact your hardware representative. |
| HSCL3073 |
The Frame FRU activation operation failed. Try the
operation again. |
Try the operation again. If the problem persists,
contact your hardware representative. |
| HSCL3074 |
The frame host information was not saved. Ensure
the Hardware Management Console has enough disk space and the correct file
permission and try the operation again. |
Ensure that the /opt/hsc/data directory contains
enough disk space so that the HMC can
save the frame host information when needed. |
| HSCL3075 |
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. |
| HSCL3076 |
An error has occurred while attempting the bulk
power assembly connection operation. Retry the operation. If the problem persists,
contact your service representative. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3077 |
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. |
- Make sure that at least one bulk power assembly is in the Standby state,
and try the operation again.
- If the problem persists, contact your hardware representative.
|
| HSCL3078 |
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. |
| HSCL3079 |
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. |
| HSCL307A |
This operation cannot be performed because the HMC
is not connected to side {0} of the bulk power assembly (BPA). Check the connection
and try the operation again. |
- Check the connection.
- Try the operation again.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3080 |
The request to remove a planar from the frame failed.
Try the request again. |
Try the request again. If the problem persists,
contact your next level of support or your service provider. |
| HSCL3081 |
The request to remove a drawer from the frame failed.
Try the request again. |
Try the request again. If the problem persists,
contact your next level of support or your service provider. |
| HSCL3082 |
The request to send the frame IP information to
the managed system has failed. |
Try the request again. If the problem persists,
contact your next level of support or your service provider. |
| HSCL3083 |
This operation is not allowed when the cage is powered
on. Before this operation can be performed, all the cages must be powered
off. |
|
| HSCL3084 |
This operation is not allowed when the BPA is in
any of the following states: Incomplete, No Connection,
or Not Available. After you have established a connection
from the HMC to the BPA,
and have entered a valid HMC access
password, try the operation again. |
|
| HSCL3200 |
Unknown lock error. |
Contact your next level of support or your service
provider. |
| HSCL3201 |
Lock type not valid. |
- Restart the HMC.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3202 |
Failed to acquire lock because of timeout. |
- Restart the HMC.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3203 |
Nested lock type requested not valid. |
- Restart the HMC.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3204 |
Lock not held. |
- Restart the HMC.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3205 |
The managed system is busy, try the operation again
later. |
The managed system is busy doing another action.
Wait and then retry the action. |
| HSCL3351 |
Code update process is not allowed by the HMC. Check the code update status
to verify the code update owner. |
- Check the code update status to verify the code update owner.
- Retry the operation if HMC is
the code update owner.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3352 |
Code update is already in progress by another HMC or by the firmware. Verify
that no other code update is in progress and retry the operation. |
- Verify that no other code update operation is in progress and retry the
operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3353 |
Code update is not allowed to the specified side.
Check the current flash side. |
- Rebuild the managed operation. For details, see Updating managed system or frame information.
- 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.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3354 |
Code update is already in progress from this HMC. Ensure that no code update
operation is in progress on the HMC before
retrying the operation. |
- Ensure that no code update operation is in progress on the HMC before
retrying the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3355 |
The code update operation failed with return code
{0}. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3356 |
The code update is not in progress by this HMC. The start code update task
should have been performed prior to code update complete by this HMC. |
- Ensure that the start code update task has been performed.
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3357 |
The operation failed since another commit or long
running code update is in progress. |
- Ensure that no other code update operation is in progress.
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3358 |
The delete LID operation is not allowed when a write
LID is in progress. |
- Ensure that no other code update operation is in progress.
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3359 |
The code update operation failed since an invalid
LID ID was specified. |
- Check the LID file ID and retry the operation with a valid LID file ID.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3360 |
Error accessing the flash. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3361 |
An unknown error occurred during code update operation.
Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3362 |
An unknown error occurred during reboot service
processor. Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3363 |
The size of the LID number array is not the same
as the Filename array. Ensure every LID number has a corresponding filename. |
- Ensure every LID number has a corresponding filename and retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3364 |
The read LID operation failed: {0}. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3365 |
Error: The following file(s) already exist(s): {0}. |
- Ensure the files to read in the LID files do not exists and retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3367 |
The input parameter arrays should all be of the
same length. Check the lengths and retry the operation. |
- Ensure the lengths of the input parameters are the same and retry the
operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3368 |
The Max write block size for the start code update
did not get set. Retry the operation. |
- Retry the operation for the LID files that failed.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3370 |
The deletion of the following LID(s) failed: {0}. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3371 |
The write LID operation failed: {0}. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3372 |
The following LID filenames are not files: {0} |
- Ensure the LID files exist and retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3373 |
The following LID files are empty: {0} |
- Ensure that the LID files are valid and retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3374 |
The following LID files do not exists: {0} |
- Ensure the LID files exist and retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3376 |
Invalid value returned from the service processor
to indicate whether service partition firmware code LID updates are enabled
or disabled. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3377 |
The start code update operation failed since an
invalid component to update was specified. Retry the operation with the a
valid firmware component to update. |
- Retry the operation with a valid firmware component to update.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3378 |
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. |
- Check the state of the managed system and retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3379 |
There is a permanent error in flash, retry the operation
and if the problem persists contact support. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3380 |
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. |
- Check the state of the managed system and retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3381 |
The Complete Code Update operation failed since
an invalid completion type was specified. Retry the operation with a valid
completion type. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3382 |
The Code Update is not in progress. The start code
update operation needs to be performed before the Complete Code Update operation. |
- Ensure the start code update operation is performed first.
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3383 |
One or more LIDs are invalid in the
primary LID list. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3384 |
For the partial read, the specified length was not
read since the end of file flag was reached. |
- Retry the operation with a valid length to be read.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3385 |
Error: The following file(s) specified an invalid
data for the Special LID Designator or the code update side: {0} |
- Retry the operation with valid special LID designator or the code update
side.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3386 |
The read partial/special LID operation failed, since
writing to the file on the HMC got
an error. Check the log for the error and retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3387 |
An unknown error occurred during the open of firmware
files. Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3388 |
The following fileid-subid specified an invalid
open type: {0} |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3389 |
The following fileid-subid specified an invalid
Force Flag: {0} |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3390 |
Error: The following files got an exception while
trying to open the firmware file: {0} |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3391 |
The open firmware file operation failed: {0} |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3392 |
An unknown error occurred during the write operation
of firmware files. Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3393 |
An unknown error occurred during the close of firmware
files. Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3394 |
An unknown error occurred during the get firmware
status update operation. Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3395 |
An unknown error occurred during the start firmware
update operation. Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3396 |
Failed to delete the partition with ID {0} since
it is the service partition. |
- Ensure the partition is not the service partition.
- Rebuild the managed system. For details, see Updating managed system or frame information.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3397 |
The secondary service processor is not available
for the managed system. |
- Check the FSP configuration and make sure that the service processor is
installed and available for failover.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3398 |
The code update service processor lock is already
taken. Check that no other code update operation is running and retry the
operation. |
- Check that no other code update operation is in progress and retry the
operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3399 |
The code update service processor lock is not taken.
Ensure the lock is taken before trying to release the code update service
processor lock. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3400 |
The service processor target that was specified
is not valid. Verify the service processor target name and try the request
again. |
- Rebuild the managed frame. For details, see Updating managed system or frame information.
- Try the task again.
- If the problem persists, contact your service provider.
|
| HSCL3401 |
The get power domain operation failed. Retry the
operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3402 |
The get power domain power state operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3403 |
The set service lock operation failed. Retry the
operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3404 |
The reset service lock operation failed. Retry the
operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3405 |
The FRU level activate operation failed. Retry the
operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3406 |
The FRU level deactivate operation failed. Retry
the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3407 |
The vary off power domain platform operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3408 |
The vary off power domain platform operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3409 |
The vary on power domain platform operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3410 |
The vary off power domain partition operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3411 |
The vary off power domain partition operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3412 |
The vary on power domain partition operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3413 |
No Partitions are defined for the managed system.
Check the user interface to see if partitions are defined and then retry the
operation. |
- Rebuild the managed system. For details, see Updating managed system or frame information.
- Retry the task.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3414 |
The start I/O concurrent maintenance operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3415 |
The I/O concurrent maintenance operation failed.
Retry the operation. |
- The I/O concurrent maintenance command failed. Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3416 |
The get configuration ID operation failed. Retry
the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3417 |
The set configuration ID operation failed. Retry
the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3418 |
The get IO unit configuration ID and MTMS operation
failed. Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3419 |
The set IO unit MTMS operation failed. Retry the
operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3420 |
The set IO unit configuration ID operation failed.
Retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3421 |
This operation is not allowed in the managed system's
current state. Check the state of the managed system and retry the operation. |
- Check the state of the managed system and retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3422 |
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. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3423 |
Invalid data {0} was specified for this operation.
Check the data and retry the operation. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3424 |
The I/O concurrent maintenance operation failed
with return code: {0}. |
- Retry the operation.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3431 |
The command display service effect failed {%0}.
Please retry the operation again. |
|
| HSCL3432 |
The system level deactivation failed {%0}. Please
retry the operation. |
|
| HSCL3433 |
The system level deactivation failed {%0}. Please
retry the operation. |
|
| HSCL3437 |
The managed system does not have Concurrent Maintenance
capability. Please upgrade the firmware and retry the operation. |
- Upgrade the firmware that supports Platform Hardware Concurrent Maintenance
and retry the operation. For details, see Obtaining firmware updates.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3438 |
The managed system does not have PHYP Concurrent
Maintenance capability. Please upgrade the firmware and retry the operation. |
- Upgrade the firmware that supports Platform Hardware Concurrent Maintenance
and retry the operation. For details, see Obtaining firmware updates.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3439 |
Query FSP CM Service Lock failed. Please retry the
operation. |
- Please retry the operation
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3500 |
The function completed successfully. |
|
| HSCL3501 |
The operation failed because of a non-trivial reason. |
- Restart the HMC and
retry the task.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3503 |
Input error: The specified value is out of range
or undefined. |
Contact your next level of support or your service
provider. |
| HSCL3504 |
An invalid input file or an error has occurred during
an operation on the specified file. |
- Restart the system.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3505 |
An error occurred while contacting the access control
system. Retry the operation. |
- Restart the system.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL350A |
Invalid input parameter(s). |
- Check the input and try the task again.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL350B |
The user does not have the appropriate authority. |
- Try the task again.
- Restart the system.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL350C |
Input error: An invalid operation has been specified. |
- Check the input and try the task again.
- Restart the system.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL350D |
Input error: An invalid user ID has been specified. |
- Check the input and try the task again.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL350E |
Input error: An invalid task has been specified. |
- Check the input and try the task again.
- Restart the system.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL350F |
Input error: The input resource is not valid or
conflicts with the role in the operation. - Check the input and try the task again.
- Reboot the system.
- If the problem persists, contact your next level of support or your service
provider.
|
- Check the input and try the task again.
- Restart the system.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3510 |
Input error: An invalid role or parent role has
been specified. |
- Check the input and try the task again.
- If the problem persists, contact your next level of support or your service
|
| HSCL3511 |
Input error: An invalid subsystem has been specified. |
- Check the input and try the task again.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3512 |
Input error: An invalid option has been specified. |
- Check the input and try the task again.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3513 |
Input error: An invalid managed resource role name
has been specified. |
- Check the input and try the task again.
- Restart the HMC.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3514 |
The role specified already exists. |
A duplicate role name has been specified in the
operation. Select a different name. |
| HSCL3532 |
An unknown error, such as an exception, has occurred
during the operation. |
- Try the task again.
- Restart the HMC.
- If the problem persists, contact your next level of support or your service
provider.
|
| HSCL3533 |
Invalid operation. The input role is a system predefined
role. |
The operation is not allowed. |
| HSCL3534 |
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. |
| HSCL3563 |
The function specified is not available in the current
release. |
|