| HSCL02xx error codes | Message | Recovery action |
|---|---|---|
| HSCL0201 | Service processor command failed after {0} attempts: Invalid response. | Wait several minutes and try the task again. |
| HSCL0203 | Command sent to service processor failed. Error response {0}. |
|
| HSCL0204 | Command failed. Unknown error. |
|
| HSCL0205 | The managed system is in the error state and is unable to continue with the task. | The recovery partition data task cannot be run until
the managed system is no longer in error state.
|
| HSCL0206 | Unable to power on the managed system. Unable to continue with the power on task. |
|
| HSCL0208 | Unable to power on the managed system. Unable to continue with the power on task. |
|
| HSCL0209 | Remote virtual terminal sessions are not allowed. Check the remote virtual terminal settings. | Virtual terminal cannot open remotely at this time. If this feature is needed, use the Enable/Disable Remote Virtual Terminal task in the HMC Configuration menu to enable remote connections. |
| HSCL020A | The power on system profile operation timed out. Activate the system profile manually after the managed system is powered on. | Activate the system profile manually after the managed system is powered on. |
| HSCL020D | The command you issued contained incorrect data. | Contact your next level of support or your service provider. |
| HSCL0211 | The requested function is currently disabled. | Shut down the managed system, and start it again. |
| HSCL0212 | The managed system is not capable of Capacity on Demand (CoD) at the present time. |
|
| HSCL0213 | The managed system does not support Capacity on Demand upgrades for processors. | Contact your local representative for more information about this feature. |
| HSCL0214 | The managed system does not support Capacity on Demand upgrades for memory. | Contact your local representative for more information about this feature. |
| HSCL0215 | There was an error trying to save processor order information to a diskette. | Verify that the diskette is writable, and retry the operation again. If the error persists, contact your next level of support or your service provider. |
| HSCL0222 | The operation cannot be done because the managed system is not capable of LPAR. |
|
| HSCL0223 | Firmware is not ready to accept the specified command. Try again later. |
|
| HSCL0224 | There was an error dumping the LPAR configuration. Check the console event log. |
|
| HSCL0225 | There was an error clearing the LPAR configuration. Check the console event log. |
|
| HSCL0226 | The firmware power off policy returned from the service processor is not valid. Unable to determine whether the firmware should power off or stay running after last partition powers off. |
|
| HSCL0228 | The managed system could not be found in the database. Rebuild the managed system, and try again. |
|
| HSCL0229 | Memory specified, {0}, is not a multiple of the system memory region size, {1}. Modify the value to be a multiple of the memory region size and try again. |
|
| HSCL022A | i5/OS® partitions are not supported on the managed system. |
|
| HSCL022C | The managed system is not in a valid state to perform the operation. Check the state of the managed system and retry the operation. |
|
| HSCL022D | Unable to perform a get or a set operation on the managed system's platform IPL parameters. |
|
| HSCL022E | Unable to restore the profile data when the managed system is not in the Operating or Standby state. |
|
| HSCL022F | Unable to delete the profile data backup file, {0}. |
|
| HSCL0230 | Unable to get managed system credential information. |
|
| HSCL0231 | Unable to set managed system credential information. |
|
| HSCL0233 | Unable to change the service partition to the partition with ID of {0}. Check your current setting(s) and ensure this change is allowed. | The service partition cannot be changed.
|
| HSCL0234 | Failed to transition out of standby state. Rebuild the managed system and try again. | Rebuild the managed system. For details, see Updating managed system or frame information. Then try the task again. If the problem persists, contact your next level of support or your service provider. |
| HSCL0235 | Cannot change service partition from one partition to another if either one of them is not in the Not Activated state. |
|
| HSCL0236 | The name specified contains unprintable or invalid characters listed: {0}. Remove the invalid characters and try again. |
|
| HSCL0240 | The {0} password is locked and cannot be changed while it is locked. | The password has been locked. Contact your next level of support or your hardware service provider to unlock the password. |
| HSCL0241 | The {0} password is locked. | The password has been locked. Contact your next level of support or your hardware service provider to unlock the password. |
| HSCL0242 | Failed to set i5/OS partition {0} as the service partition for this managed system. Only an AIX® or Linux® logical partition can be designated as the service partition on IBM® System p5® or IBM eServer™ p5 servers. | Choose an AIX or Linux logical partition as the service partition for your managed system. |
| HSCL0243 | The Machine Code on your managed system does not support viewing the Virtualization Engine™ systems technologies activation history log. In order to view the history log on your managed system, you need to update your managed system's Machine Code (Licensed Internal Code). |
|
| HSCL0250 | The managed system machine type, model, and serial number (MTMS) is empty. | |
| HSCL0251 | Service processor command {0} failed. The connection to the hardware server is broken. | Ensure that the network connection is working. If the problem persists, contact your next level of support or your service provider. |
| HSCL0252 | Service processor command {0} failed. The connection to service processor is not available. | Ensure that the network connection is working. If the problem persists, contact your next level of support or your service provider. |
| HSCL0253 | Service processor command {0} failed. The managed system has been deleted. | Ensure that the network connection is working. If the problem persists, contact your next level of support or your service provider. |
| HSCL0254 | Hardware server command {0} failed. No response package. |
|
| HSCL0255 | Hardware server command {0} failed. The request ID has been deleted from the ID table. |
|
| HSCL0256 | Issuing a service processor pass-through failed. HMC server is trying to reconnect to the hardware server. |
|
| HSCL0257 | Issuing a service processor pass-through failed. HMC server re-established a connection to the hardware server after this command was issued. |
|
| HSCL0258 | Issuing a service processor pass through failed. An expected exception with message {0} was thrown. |
|
| HSCL0259 | Service processor lock failed. The lock manager is not active. | Restart the HMC. If the problem persists, contact your next level of support or your service provider. |
| HSCL025A | Service processor lock failed. The conflict lock is owned by HMC: {0}. Its request ID is {1}. Try again later. |
|
| HSCL025B | Query service processor data failed. The error code is {0}. | |
| HSCL025C | Service processor command {0} failed. Service processor authentication needs to be done first. |
|
| HSCL025D | Service processor command {0} failed. The Hypervisor is not ready to accept commands. |
|
| HSCL025E | The lock table in the managed system is full. Try again. | Wait and then try the operation again. |
| HSCL025F | There is a managed system lock. | Wait and then try the operation again. |
| HSCL0260 | Unexpected error happened when trying to acquire a managed system lock. The command return status is {0}. | Wait and then try the operation again. |
| HSCL0261 | Unexpected error happened when trying to acquire a managed system lock. | Report the problem to your next level of support or your service provider. |
| HSCL0262 | Supplement lock operation failed. | Check the input and permission and try the task again. |
| HSCL0263 | Service processor does not support more than one HMC connection. No service processor lock is needed. | contact your next level of support or your service provider. |
| HSCL0264 | The console command manager is not active. |
|
| HSCL0265 | No destination was specified for command {0}. The command cannot be sent. |
|
| HSCL0266 | The request to query data on the managed system failed with error code {0}. |
|
| HSCL0267 | The connection to the service processor has been lost. A long-running task was stopped. | Verify the completion of the long-running task. If the task did not complete successfully, try the task again |
| HSCL0268 | An unexpected error occurred in a long-running task. | Verify the completion of the long-running task. If the task did not complete successfully, try the task again. |
| HSCL0269 | Managed system with IP address {0} cannot be found. | Verify the specified IP address. Specify a valid IP address and try the request again. |
| HSCL026A | The specified managed system name {0} is not valid with the specified IP address {1}. The managed system cannot be removed. | Specify a valid managed system name and a valid IP address. Then try the request again. |
| HSCL026B | Cannot find a managed system with the specified name {0}. | Verify the specified system name. Specify a valid managed system name and try the request again. |
| HSCL026C | The request to add a new managed system with IP address {0} failed. | Verify the specified IP address. Specify a valid IP address and try the request again. |
| HSCL026D | Lock type {0} is not valid for the managed system. |
|
| HSCL026E | The lock manager for managed system {0} is not active. | Try the request again later. If the problem persists, contact your service provider. |
| HSCL026F | Either the managed system name or the IP address is not specified in the request to remove the managed system. | Specify both the managed system name and the IP address. Then try the request again. |
| HSCL0270 | The specified command destination {0} cannot be found. The command {1} cannot be sent. |
|
| HSCL0271 | The connection state of the specified command destination {0} is not valid. The command {1} cannot be sent. | The connection to the managed system has been lost. Try the request again later. |
| HSCL0280 | The service processor managed system state is not valid. The power state is {0}. The run state is {1}. |
|
| HSCL0281 | The operation cannot be done because the managed system is not shared processor capable. | No recovery action is required. |
| HSCL0282 | The virtual Ethernet adapter in virtual I/O slot {0} cannot be defined because the partition with ID {1} already defines a trunk adapter in its virtual I/O slot {2}. Modify the profile accordingly and reactivate the partition. | Modify the profile accordingly and reactivate the partition. |
| HSCL0285 | The managed system does not support SNI message passing. | No recovery action. |
| HSCL0288 | The managed system is not ready for service processor failover. |
|
| HSCL023A | This operation is allowed only when the managed system is powered off. | No recovery action. |
| HSCL023B | This operation is allowed only after the managed system has been powered on at least once, and then powered off. | No recovery action. |