The following tables contain information about error messages that can be displayed by the HMC during system configuration and operations.
Use this appendix to learn more about a specific error or information
message. The table also includes recovery information (if applicable)
to help you determine a recovery strategy.
Console Events Error Codes | Message | Recovery Action |
---|---|---|
HSCE2066 | A scheduled backup of critical console data failed with a return code of {0}. | The possible return code values are:
|
Inventory Scout Error Codes | Message | Recovery Action |
---|---|---|
HSCI0100 | No managed systems were detected that are attached to this system console. | None |
HSCI0101 | No partitions have been defined for this managed system. | None |
HSCI0102 | A blank or invalid entry was entered in the partition password field. | Enter a valid password value. |
HSCI0103 | A blank or invalid entry was entered in the listening port field. | Enter a valid port value. |
HSCI0104 | A blank or invalid entry was entered in the IP address field. | Enter a valid IP address value. |
HSCI0110 | The Inventory Scout command completed successfully. | None |
HSCI0111 | The Inventory Scout command request failed |
|
HSCI0112 | The removable media cannot be mounted. Please make sure the media is inserted properly in the drive and retry the operation |
|
HSCI0113 | The media specified is write protected. Please adjust the media and retry. | Remove the write protection and try the operation again. |
HSCI0114 | The Inventory Scout request failed. Ensure the removable media is properly inserted in the drive. |
|
HSCI0115 | An error occurred while copying the Inventory Scout data. Verify that a blank formatted diskette is inserted properly in the drive and retry the operation. |
|
HSCI0116 | An error occurred while compressing the Inventory Scout data. Please retry the operation. |
|
HSCI0117 | An error occurred while trying to unmount the media. |
|
HSCI0118 | The Inventory Scout daemon was restarted successfully. | None |
HSCI0119 | The Inventory Scout daemon could not be restarted. |
|
HSCI0120 | The internal managed system name is malformed. Please exit this task and retry the operation. |
|
HSCI0121 | The Inventory Scout request failed. An error occurred while copying data to removable media. |
|
HSCI0122 | The system partition(s) did not respond to query attempts. |
|
Profile Data Error Codes | Message | Recovery Action |
---|---|---|
HSCL0001 | There is no more space for a new profile name. Reuse profile names being used by other profiles or remove the profiles that are no longer needed. | No more space for a new profile name is available. Reuse the profile names that are already used by other profiles, or remove the profiles that are no longer needed. Follow the procedures in this book to perform this action. |
HSCL0002 | Too many drawers are being used in profiles. Remove the drawers that no longer exist or are not needed. | Remove the drawers that no longer exist or are no longer needed. Follow the procedures in this book to perform this action. |
HSCL0003 | The profile data save area is full. Remove any profiles that are no longer needed. | Remove the profiles that are no longer needed. Follow the procedures in this book to perform this action. |
HSCL0004 | A profile with name {0} already exists in the partition with ID {1} in profile data of the managed system. Provide another name for this profile. | Rename the profile to names that are not already in use in this partition. Follow the procedures in this book to perform this action. |
HSCL0005 | Cannot find information regarding profile data of the managed system. Execute a rebuild managed system operation. |
|
HSCL0006 | The managed system's profile data has been corrupted. You must either restore or reinitialize the profile data. | You must either restore or initialize the profile data. Follow the procedures in this book to perform this action. |
HSCL0007 | The profile data of the managed system cannot be accessed or modified. Execute a rebuild managed system operation |
|
HSCL0008 | Could not construct or initialize profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0009 | Could not construct or initialize the profile data from the backup file, {0}. Repeat the operation. | Repeat the operation. Follow the procedures in this guide. If the problem persists, call for HMC software support.. |
HSCL000B | Could not get the activated LPAR profile from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL000C | Could not get the activated system profile from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL000D | Could not get all the system profiles from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL000E | Could not get the default LPAR profile from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL000F | Could not get the default system profile from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0010 | Could not get the LPAR profiles for the partition from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0011 | Could not get the LPAR profiles at this partition from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0012 | Could not get the system profile from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0013 | Could not remove the LPAR profile from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0014 | Could not remove the system profile from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0015 | Could not save the LPAR profile to the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0016 | Could not save the system profile to the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0017 | Could not create the LPAR profile in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0018 | Could not create the system profile in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0019 | Could not set the activated LPAR profile in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL001A | Could not set the activated system profile in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL001B | Could not set the default LPAR profile in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL001C | Could not set the default system profile in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL001D | Could not clean up the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL001E | Could not update the profile data cache. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL001F | Could not check for duplicate LPAR name. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0020 | Could not remove the LPAR profile from the system profile content in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0021 | Could not add the LPAR profile to the system profile in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0022 | Could not get the partition name from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0023 | Could not get all the partition names from the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0024 | Could not set the partition name in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0025 | Could not build the profile data from the local file, {0}. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0026 | Could not write the data to the managed system. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0027 | Could not backup the profile data to a file. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0028 | Could not read profile data from the managed system. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0029 | Could not delete profiles at the partition with ID of {0} in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL002A | Could not modify the system profiles containing the LPAR slot ID of {0} in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL002B | Could not do a priority restore on the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL002C | Could not merge the profile information in profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL002D | Could not merge partition name data in the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL002E | Could not merge default and activated list data in profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL002F | Could not merge drawer and profile infomation data in profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0030 | Unable to initialize the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0031 | The profile data has been cleared. Either restore or reinitialize the profile data save area. | Perform restore profile data task or initialize the profile data. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL0032 | Could not set the system profile's user defined name to the profile data. Perform a Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL0033 | This managed system version, {0}, is unknown to HMC. Update to an HMC release that can handle this version of managed system. |
|
HSCL0034 | The levels of managed system and profile data area are not matching up. Managed system version: {0}, profile data area version: {1}. Upgrade the managed system version "to proper level." |
|
HSCL0035 | Cannot restore profile data with 2 different versions of profile save data. |
|
HSCL0036 | Migrate profile data failed. |
|
HSCL0037 | This level of profile data, {0}, is unknown to this HMC. Please update to an HMC version that can handle this level of profile data. |
|
HSCL0038 | Creation of affinity logical partition profiles failed in profile data save area. |
|
HSCL0039 | Deletion of affinity logical artitions failed in profile data save area. |
|
HSCL003A | Removal system profiles failed at profile data save area. |
|
HSCL003B | Setting of partition information failed in profile data save area. |
|
HSCL003C | Retrieval of all affinity logical partition information failed in profile data save area. |
|
HSCL003D | Retrieval of parition information failed in profile data save area. |
|
HSCL003E | Cannot build LPAR information from profile data save area when the managed system is not LPAR capable. | The capabilities of your managed system are listed on the Machine tab of the property panel. |
HSCL003F | Cannot build affinity logical partition information from profile data save area when the managed system is not Affinity LPAR capable. | The capabilities of your managed system are listed on the Machine tab of the property panel. |
HSCL0040 | No more space for physical location code in the profile data save area. |
|
HSCL0041 | Migration of partition information failed in profile data save area |
|
HSCL0042 | Migration of profile names failed in profile data save area |
|
HSCL0043 | Migration of default profile list failed in profile data save area |
|
HSCL0044 | Migration of activated profile list failed in profile data save area |
|
HSCL0045 | Migration of physical location code information failed in profile data save area |
|
HSCL0046 | Migration of drawer and profile information failed in profile data save area |
|
HSCL0047 | Migration of time stamps of profile data save area failed |
|
HSCL0048 | Migration of checksums of profile data save area failed |
|
Managed System Error Codes | Message | Recovery Action |
---|---|---|
HSCL01F5 | Unable to lock the Service Processor. Perform one of the following steps: (1) Check serial cable connection; (2) Check if another Console is communicating with the Service Processor; (3) Perform the Release Lock task; (4) Perform Rebuild task to re-establish the connection. |
|
HSCL01F6 | Unable to unlock the managed system lock. Perform the Release Hardware Management Console Lock to unlock the managed system. |
|
HSCL01F7 | Unable to get the current time from the managed system. |
|
HSCL01F8 | This property cannot be altered. | None. |
HSCL01F9 | Unable to create managed system instance in object manager. |
|
HSCL01FA | The managed system is already powered off. | None. |
HSCL01FC | The parameter specified is not valid. Specify a different value. | None. |
HSCL01FD | Power on failed. Try again. | Retry the Power On task. If the problem persists, call for HMC software support. |
HSCL01FE | The managed system is already powered on. | None. |
HSCL01FF | Could not rebuild. Shut down and restart the Hardware Management Console. |
|
HSCL0200 | Unable to communicate with Service Processor. Check serial cable connection. |
|
HSCL0201 | Service Processor Command failed after {0} attempts: Invalid Response. | Wait several minutes and try the task again. |
HSCL0202 | Service Processor Socket is corrupted. |
|
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 Recover Partition Data Task. | The recovery partition data task cannot be run until the managed system
is no longer in error state.
|
HSCL0206 | Failed to Power On the Managed System. Unable to continue with the Power On Task |
|
HSCL0207 | Failed to Power Off the Managed System. Unable to continue with the Recover Partition Data Task. |
|
HSCL0209 | Remote virtual terminal sessions are not allowed. Please check the remote virtual terminal settings. | Virtual terminal cannot open remotely at this point. If open virtual terminal remotely is needed, enable your remote virtual terminal setting. Use the Enable/Disable Remote Virtual Terminal task in the System Confiuration menu to enable remote connections. |
HSCL020A | The power on system profile operation timed out. Activate the system profile manually once the managed system is powered on. | Activate the system profile manually after the managed system is powered on. |
HSCL020B | The CUoD activation code you entered is incorrect. Please check the activation code and retry. | Make sure the key is correct, and enter it again. If it still fails, contact your service representative. |
HSCL020C | The managed system does not allow Activation Codes for CUoD operations. | None |
HSCL020D | The command you issued contained incorrect data. | Internal use only. Contact your next level of software support. |
HSCL020E | The sequence number of this activation code indicates it has been used before. Please enter in a newer activation code. | Make sure the key is correct, and enter it again. If it still fails, contact your service representative. |
HSCL020F | The activation code was not entered correctly. Re-enter your activation code. | Make sure the key is correct, and enter it again. If it still fails, contact your service representative. |
HSCL0210 | The managed system cannot currently process an activation code. This condition is temporary, please retry this operation. | The system is processing another CUoD function. Retry the operation. |
HSCL0211 | The requested function is currently disabled. | Power off the managed system, and power it back up. |
HSCL0212 | The managed system is not CUoD capable at the present time. | Make sure that the managed system is powered on. If it is powered on, check the managed system's properties panel to verify that the system is not CUoD capable. Contact your local representative for more information about this feature. |
HSCL0213 | The managed system does not support CUoD upgrades for processors. | Contact your local representative for more information about this feature. |
HSCL0214 | The managed system does not support CUoD 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 the diskette is writable, and retry the operation. If the error persists, contact your service representative. | Verify the diskette is writable, and retry the operation again. If the error persists, contact your service representative. |
HSCL0216 | There was an error trying to send processor order information to the remote system. Verify the network connection to the remote system and that the user has access to the remote system and directory where the file will be copied. If the problem persists, contact your software support representative. | Verify the network connection to the remote system and that user has access to the remote system and directory where the file will be copied. If the problem persists, contact your software support representative. |
HSCL0216 | The managed system cannot process the CUoD task at this time. The function has been disabled. You must power off and then power on the managed system to enable this task. | To enable the CUoD task, power off and then power on the managed system. |
Managed System Resource Error Codes | Message | Recovery Action |
---|---|---|
HSCL03EA | There is an insufficient number of processors: Obtained - {0}, Required - {1}. Check that there are enough processors available to activate the partition. If not, create a new profile or modify the existing profile with the available resources, then activate the partition. If the partition must be activated with the specified number of processors, deactivate any active partitions using the resource, then activate the partition. |
|
HSCL03EB | Unable to allocate the I/O slot for activation in {0}. Check that the specified I/O is available to activate the partition. If not, create a new profile or modify the existing profile with the available resources, then activate the partition. If the partition must be activated with these resources, deactivate any running partition(s) using the resource then activate this partition. |
|
HSCL03EC | There is not enough memory: Obtained - {0}, Required - {1}. Check that there is enough memory available to activate the partition. If not, create a new profile or modify the existing profile with the available resources, then activate the partition. If the partition must be activated with these resources, deactivate any running partition(s) using the resource then activate this partition. |
|
HSCL03ED | The I/O Drawer specified by this ID cannot be found and may have been deleted from the managed system. Modify the profile. | The I/O drawer defined in the profile may have been removed from the server. Check to verify that the I/O drawers defined in the profile are installed. Then, modify the profile to match the server configuration. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL03EE | The specified slot number cannot be found. Make sure the profile is not using I/O drawer slots that do not exist in the managed system. | An I/O slot defined in the profile may have been removed from the server. Verify that the I/O slots defined in the profile are installed. Then, modify the profile to match the server configuration. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL03EF | The number of drawers, slots, and I/O required/desired information stored in the properties do not match. The profile may be corrupted. Perform the Restore Profile Data task. |
|
HSCL03F0 | Unable to allocate the I/O slot for activation in I/O drawer {0}. Slot {1} is currently being used by another partition. Perform one of the following three actions 1) remove this I/O slot from the profile or 2) change the I/O slot from Required to Desired in the profile or 3) remove the I/O slot from the other partition. | Perform one of the following actions:
|
HSCL03F1 | Unable to allocate one or more I/O slots. The following slots are in error state: {0} slot {1}. Please complete one of the following actions: Remove this I/O slot from the profile, or change the I/O slot from required to desired in the profile, or reboot the managed system to restore the PCI slots in error to normal state. | Perform one of the following options:
|
HSCL03F2 | Unable to allocate the I/O slot for activation in I/O drawer {0}. Slot {1} is not present. Remove this I/O slot from the profile or change the I/O slot from Required to Desired in the profile. | Remove this I/O slot from the profile or change the I/O slot from Required to Desired in the profile. |
HSCL03F3 | Unable to allocate the I/O slot for activation in I/O drawer {0}. Slot {1} is system deconfigured. Remove this I/O slot from the profile or change the I/O slot from Required to Desired in the profile. | Remove this I/O slot from the profile or change the I/O slot from Required to Desired in the profile. |
Partition Error Codes | Message | Recovery Action |
---|---|---|
HSCL0591 | Cannot activate logical partition when an affinity logical partition has already been activated since powering on | Activation of logical partitions is not allowed at this point. To
activate this partition, do the following:
|
HSCL0592 | Cannot activate a 8-processor affinity logical partition when a logical partition or other type of affinity logical partition has already been activated since powering on | Activation of an 8-way affinity logical partition is not allowed at this
point. To activate this partition, do the following:
|
HSCL0593 | Cannot activate a 4-processor affinity logical partition when a logical partition or other type of affinity logical partition has already been activated since powering on | Activation of a 4-way affinity logical partition is not allowed at this
point. If you need to activate this partition, do the following
|
HSCL0594 | Managed system is not capable of activating a 4-processor affinity logical partition | The capabilities of your managed system are listed on the Machine tab of the property panel. |
HSCL0595 | Managed system is not capable of activating a 8-processor affinity logical partition | The capabilities of your managed system are listed on the Machine tab of the property panel. |
HSCL0596 | Cannot activate a Full Machine Partition in a non-SMP capable managed system | The capabilities of your managed system are listed on the Machine tab of the property panel. |
HSCL0597 | Cannot activate a logical partition in a non-LPAR capable managed system | The capabilities of your managed system are listed on the Machine tab of the property panel. |
HSCL0598 | Cannot activate an affinity logical partition in a non-Affinity-LPAR capable managed system | The capabilities of your managed system are listed on the Machine tab of the property panel. |
HSCL059A | Cannot activate the partition. The profile's maximum memory amount exceeds the managed system's memory limit. Please change the profile's maximum memory amount. | Change the profile's maximum memory amount, and retry the operation. |
HSCL05DD | Unable to get partition state. Repeat the operation. | Repeat the operation. If the problem persists, call for HMC software support. |
HSCL05DE | A partition in the managed system already uses the name {0}. Provide another name for this partition. | Rename the partition to another name that is not yet used by other partitions in the same managed system. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05DF | The partition is not in a state under which this operation can be performed. Check the state of the partition. | Verify that the operation is allowable under this partition state. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05E0 | The partition {0} is in an undefined state. Rebuild the managed system. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL05E1 | Only 16 partitions per managed system can be allocated. There are no more unallocated partitions available. Delete unused or unwanted partitions for this managed system and retry the operation. Partitions in the ready state are currently not in use. | Delete unused or unwanted partitions. Partitions in the ready state are currently not in use. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05E4 | Unable to delete a full system partition. You do not have the necessary permission to delete a full system partition. | You do not have the necessary permission to delete a full system partition. Contact your user administrator to give you proper access. |
HSCL05E5 | Unable to create partition when the managed system is in {0} state. Make sure that the managed system is in the ready state and was powered on with Partition Standby. | Verify the managed system is in the ready state and in Partition Standby. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05E6 | Partition {0} delete failed. Cannot delete a partition when its state is in {1}. If the partition is not in the ready error state, perform a hard reset operation then delete the partition. | Verify the partition is not in running or booting state. If the state is ready or error state, perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action, then try the task again. |
HSCL05E7 | The profile you tried to activate does not belong to the partition {0} you specified. Select the correct LPAR profile. | Verify that you selected the correct LPAR profile to activate. |
HSCL05E8 | Cannot delete partition {0}. A partition cannot be deleted when the managed system is at the {1} state. Delete the LPAR when the managed system is in the Ready state and in Partition Standby. | If the managed system is in the Ready state and Partition Standby, rebuild the managed system. Follow the procedures in Rebuild is Indicated for Managed System to perform this action, and then try the task again. Also refer to partition error message HSCL05H6. |
HSCL05E9 | Could not activate the partition. Make sure that the partition is not already activated and that the managed system is running. | Verify that the partition is not already activated, and the state and power-on condition of the managed system are correct, try the operation again. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05EA | Cannot activate the partition when it is in state {0}. Make sure the partition is not running, booting or in the open firmware state. | Verify the LPAR is not in the running, booting, or open firmware state. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05EB | Could not create partition. Make sure that all requirements are met for creating a logical partition. | Cannot create a partition. To verify that all the requirements for creating a logical partition are met, refer to Creating Partitions. If all requirements are met, do a rebuild of the managed system, follow the procedures in Rebuild is Indicated for Managed System to perform this action, and try the task again. If the failure still occurs, call for HMC software support. |
HSCL05EC | Could not delete partition {0}. Make sure that all requirements are met for deleting a logical partition. | Cannot delete a partition. Verify that all the requirements for deleting a partition are met, refer to Deleting Partitions. If all requirements are met, rebuild of the managed system Follow the procedures in Rebuild is Indicated for Managed System to perform this action, and try the task again. If it still fails, call for HMC software support. |
HSCL05ED | Could not set the properties for partition {0}. Try again | Repeat the operation. If the operation still fails, call for HMC software support. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05EE | Could not get the managed system's service processor log entry. Try again | Repeat the operation. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05EF | This new partition does not have a user defined name. Specify a name for the partition. | Set the user defined name for this partition. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05F0 | Cannot create the partition when the managed system was powered on with {0}. Make sure the managed system is powered on with Partition Standby. | Verify that the managed system is in Partition Standby. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05F1 | Could not delete partition {0}. A partition cannot be deleted when the managed system was power on with {1}. Make sure that the managed system was powered on with Partition Standby. | Verify that the managed system is in running in Partition Standby. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL05F2 | No port or session number information for opening a virtual terminal partition on {0} with id {1}. Try again. |
|
HSCL05F3 | Could not display the OS reset dialog for partition {0}. Try again. |
|
HSCL05F4 | Could not display the partition activate dialog for partition {0}. Try again. |
|
HSCL05F5 | Could not display the create partition dialog for the managed system: {0}. Try again. |
|
HSCL05F6 | Could not create the partition on the managed system {0} with partition name {1}. Refresh the interface and check whether the operation was performed. If not, try the operation again. | Verify the newly created partition displays on the graphical user interface. If not, retry the create partition task and check the graphical user interface again. If the task still fails, log off and log back on to the HMC, and try the task again. |
HSCL05F7 | Could not open the virtual terminal for partition {0} with ID {1}. |
|
HSCL05F8 | Could not perform the OS reset {0} reset on partition {1} with ID {2}. |
|
HSCL05F9 | Could not delete partition {0}. Refresh the interface and check whether the operation was performed. If not, try the operation again. |
|
HSCL058A | Could not activate the partition on partition {0} with ID {1}. Refresh the interface and check whether the operation was performed. If not, try the operation again. |
|
HSCL058B | Could not read the boot error value task on partition {0} with ID {1}. Refresh the interface and check whether the operation was performed. If not, try the operation again. |
|
Profile Error Codes | Message | Recovery Action |
---|---|---|
HSCL07D1 | This partition profile is currently active in its logical partition and cannot be modified or deleted. To make the profile inactive, perform a hard operating system reset on the partition to bring it to the Ready state, then repeat the operation. | Partition Profiles that are active in a Logical Partition cannot be modified or deleted. Perform a Hard Operating System Reset on the Partition to bring it to the Ready state, at which time the profile will no longer be active. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL07D2 | This partition profile is the logical partition's default profile and cannot be deleted. If you still want to delete it, change the default profile for this logical partition or, if necessary, create another partition profile to be the default profile. | All Logical Partitions must have at least one Partition Profile, which is designated as the Default Profile because it is the Profile implicitly used when the Partition is activated with no Profile specified. If you still wish to delete it, change the Default Profile for this Logical Partition (create another Partition Profile if necessary). Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL07D3 | The partition profile could not be found in the Hardware Management Console save area. The Hardware Management Console is either out of sync with the console save area or the console save area has been corrupted. Rebuild this partition profile's managed system. | The main causes of this condition are:
|
HSCL07D4 | A profile named {0} already exists for this partition in the Hardware Management Console save area. Choose a different name for the new system profile. | All Partition Profiles for a logical partition must have unique names. Choose a different name for the new profile. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL07D5 | Creation of partition profiles for the full system partition is not allowed. You must use one of the predefined partition profiles for the full system partition. | You must use one of the predefined partition profiles for the Full System Partition. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL07D6 | You cannot delete full system partition profiles. | Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL07D7 | You cannot modify the full system partition profile's properties. | None |
HSCL07D8 | Deleting default profile associations within the current context is not allowed. | You can delete the Default partition Profile Association only by:
|
HSCL07D9 | Setting a default profile association is only allowed during create. | You can alter the DefaultLparProfile Association only through createInstance, which overwrites the previous association. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL07DA | The partition profile used for the operation cannot be found in the profile data. | Verify that you enter the correct information. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL07DB | An attempt to create a profile failed. | Try the task again. |
HSCL07DC | An attempt to modify a profile failed. | Try the task again. |
System Profile Error Codes | Message | Recovery Action |
---|---|---|
HSCL09C6 | Could not find the system profile in memory. It may be corrupted. Restore the profile data. | The System Profile may be corrupted.
|
HSCL09C7 | A system profile named {0} already exists for this managed system in the Hardware Management Console save area. Choose a different name for the new system profile. | Every system profile created for an individual managed system must have a unique name. Choose a different name for the new System Profile. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL09C8 | Could not open the Copy System Profile dialog. Try again. |
|
HSCL09C9 | Could not copy the system profile {0}. Try again. |
|
HSCL09CA | Could not delete the system profile. Try again. |
|
HSCL09CC | Cannot activate a Full System Partition profile when the managed system is powered on with Partition Standby. | Check the status of the Managed System from the properties panel and verify that the system was powered on as Full System Partition. If not in Full System Partition, switch the managed system from Partition Standby to Full System Partition. To switch these power-on options, turn off the power for the managed system. Then, turn on the power on and select Full System Partition during the power-on process. |
HSCL09CD | Cannot activate user defined partition profiles when the managed system is powered on with Full System Partition. | Check the status of the Managed System from the properties panel and verify that the system was powered-on as Partition Standby. If not in Partition Standby, switch the managed system from Full System partition to Partition Standby. To switch these power-on options, turn off the power to the managed system. Then, turn on the power and select Partition Standby during the power-on process. |
HSCL09CE | You cannot have LPAR and affinity LPAR profiles in the same System Profile. | Ensure the System Profile contains only profiles that belong to the same partition type. To determine the partition type, select the logical partition and view its properties. |
HSCL09CF | Validation of system profile failed. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL09D0 | Cannot validate system profile if the managed system is not in ready state. | Retry the operation with the managed system in the Ready state. |
HSCL09D1 | Cannot validate system when the managed system is powered-on with the Full System Partition | None |
Operating System Reset Error Codes | Message | Recovery Action |
---|---|---|
HSCL0DAE | The Hardware Management Console was unable to successfully issue an Operating System Reset request to the managed system or Logical Partition |
|
HSCL0DAF | A Hard Operating System Reset can be issued only on a logical partition, not on the managed system. | None |
HSCL0DB0 | A Soft Operating System Reset can be issued for the managed system when it is in the Ready state only if it was powered on in Full System Partition. | If the managed system was not powered on in Full System Partition, turn
off the power to the managed system, and then turn on the power in Full System
Partition. If the managed system is in the No-Power state, perform just
the power-on operation. The managed system should transition to the
Initializing state, then to the Ready state.
If the managed system is in the Error state, or No-Communication state, refer to Managed System States for the HMC and check the state of the managed system. Perform the appropriate actions to recover. |
HSCL0DB1 | A Soft Operating System Reset can be issued for the managed system only if it is in the Initializing or Ready state. | If the managed system is in the No-Power state, apply power to the
system. The managed system should transition to the Initializing state
then to the Ready state.
If the managed system is in an Error state or No-Communication state, refer to Managed System States for the HMC and check the state of the managed system. Perform the appropriate actions to recover. |
HSCL0DB2 | An Operating System Reset can be issued for a logical partition only if the partition is in the Running or Starting state. |
|
Virtual Terminal Error Codes | Message | Recovery Action |
---|---|---|
HSCL0FA1 | The managed system's service processor could not open a virtual terminal session. |
|
HSCL0FA2 | All available virtual terminal sessions have been opened and are in use. To force a new open session, perform a Close Terminal Session operation which frees up the session. | No Virtual Terminal Sessions are available. Perform a Close Terminal Session to forcefully close an open session and free it up to be opened. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL0FA3 | Unable to close the virtual terminal session. Issue a Close Virtual Terminal Connection operation. | An internal error occurred while attempting to close the Virtual Terminal Session. Issue a Close Virtual Connection; if this fails, call for HMC software support. |
HSCL0FA4 | There is no virtual terminal session with session number {0} open. | None |
Backup and Restore Error Codes | Message | Recovery Action |
---|---|---|
HSCL1195 | Unable to back up the profile data to the backup file. Try again. |
|
HSCL1196 | You do not have read access permission on the backup file, {0}. Try the operation again. |
|
HSCL1197 | Unable to read the profile data's backup file, {0}. Try the operation again. |
|
HSCL1198 | Cannot find backup file, {0}, for profile data. Select a valid, existing backup file. |
|
HSCL1199 | A full restore is not permitted when there are logical partitions in the {0} state. A full restore can only be issued when the managed system was powered on with Partition Standby and there are no partitions running, booting, or in the open firmware state. |
|
HSCL119A | There was an I/O error while backing up the profile data. Try again. |
|
HSCL119B | The restore profile data operation failed. Try again. |
|
HSCL119C | Cannot initialize profile data when a partition is in the {0} state and when the managed system is not powered on with Partition Standby, or when there are partitions running, booting, or in the open firmware state. | Cannot initialize the profile data when managed system is not running logical partitions and in the ready state. Also , there should be no partition in running, booting, or open firmware state. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL119D | Cannot restore the profile data if the managed system is in the {0} state. |
|
HSCL119E | Cannot initialize the profile data if the managed system is in the {0} state. |
|
HSCL119F | The backup file {0} used to restore the profile data is not valid. Its file size ({1}) is not correct. Select a valid backup file. | The backup file selected is not valid. The File may be
corrupted.
|
HSCL11A0 | Cannot restore the profile data if the managed system is in the {0} state. The managed system must be in the Ready state and powered on with Partition Standby. |
|
HSCL11A1 | Cannot initialize the profile data if the managed system is in the {0} state. The managed system must be in the Ready state and powered on with Partition Standby. |
|
HSCL11A2 | Could not display the backup dialog for the managed system: {0}. Try again. |
|
HSCL11A3 | Could not back up the profile data for the managed system: {0} to file: {1}. |
|
HSCL11A4 | Cannot back up profile data to the default backup file name: {0}. | Cannot back up the profile data to the default backup file. Choose a different backup file name. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL11A5 | Could not display the remove backup dialog for the managed system: {0}. Try again. |
|
HSCL11A6 | Could not remove the backup file {0} from the managed system {1}. |
|
HSCL11A7 | No backup file has been selected for the operation. Select a backup file. | Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL11A8 | Could not display the restore profile data dialog for the managed system: {0}. Try again. |
|
HSCL11A9 | Could not initialize the profile data task on the managed system {0}. Refresh the interface and check whether the operation was performed. If not, try the operation again. | Refresh the graphical user interface. Check whether the operation has been performed and displays on the graphical user interface. If not, repeat the operation. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL11AA | Could not restore the profile data task on the managed system {0} with backup file {1} of {2} option. Refresh the interface and check whether the operation was performed. If not, try the operation again. |
|
HSCL11AB | Could not display the recover partition data dialog for the managed system {0}. |
|
HSCL11AC | Could not perform the recover partition data task on the managed system {0}. |
|
HSCL11AD | Could not display the Rebuild the Managed System dialog for the managed system {0}. | None |
HSCL11AE | The backup profile data name must start with a numeric or alphabetic character. | Specify the name correctly. |
HSCL11AF | The backup profile data name must not contain / \ ' or " characters. | Specify the name correctly. |
Utility Class Error Codes | Message | Recovery Action |
---|---|---|
HSCL138A | Unable to a get the socket connection to the managed system. Shut down and restart the Hardware Management Console. | Shut down and restart the HMC. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL138C | Unable to find the machine type, model, serial number of this HMC. | Reboot the HMC. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL138D | Could not release the management framework socket. | Reboot the HMC.Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL138F | Unable to get the Hardware Management Console hostname. Check the network settings within the system configuration. | Check the network setting under system configuration, then try the task again. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL1390 | The managed system is not registered in the management framework. Shut down and restart the Hardware Management Console. | Shut down and restart the HMC. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL1391 | The management framework socket is not registered. Make sure to not attempt any operations while the delete, rebuild, or restore profile data tasks are being performed. Perform the Rebuild Managed System task. |
|
HSCL1392 | The management framework socket is either deleted or changed. Do not perform any operations while the delete, rebuild, or restore profile data tasks are being performed. Perform the Rebuild Managed System task. | Make sure not to perform any operation while the Delete, Rebuild, and Restore Profile Data tasks are performed. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL1393 | Unable to load the list of IBM PC product names. |
|
HSCL1395 | Unable to launch the confirmation dialog. Try again. |
|
HSCL1396 | Unable to initialize the HMC-CSP Version compatibility table. | Retry the operation. If it fails, contact HMC Software Support. |
HSCL1397 | Unable to determine what version of firmware is loaded on the service processor. | Try the operation again. If it fails, contact HMC Software Support. |
HSCL1398 | Unable to determine what versions of service processor firmware is compatible with this version of the Hardware Management Console. | Retry the operation. If the error persists, contact HMC software support. |
CIMOM Error Codes | Message | Recovery Action |
---|---|---|
HSCL157F | Cannot find an instance of the object specified. |
|
HSCL1584 | You do not have the proper authorization or permission to perform this task. Log in as the proper user and try again. | Log in with appropriate permissions to perform the task. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL1585 | There was an unknown error while querying the object manager database. |
|
HSCL1586 | Cannot find an Instance with object manager of {0}. |
|
HMC Console Error Codes | Message | Recovery Action |
---|---|---|
HSCL1771 | Unable to create console information and set it with the managed system. Perform the Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL1772 | Could not set Hardware Management Console information. Perform the Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL1773 | Invocation of the Hardware Management Console information method failed. Perform the Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL1774 | Unable to get the defined slot number for Hardware Management Console information slots. Perform the Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL1775 | Could not get host Hardware Management Console information slot ID. Perform the Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL1776 | Could not get the Hardware Management Console information. Perform the Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL1777 | Failed to construct the Hardware Management Console information string. Perform the Rebuild Managed System operation. | Perform a Rebuild Managed System operation. Follow the procedures in Rebuild is Indicated for Managed System to perform this action. |
HSCL177F | Could not delete the Hardware Management Console instance. |
|
WEBSM/AUIML Error Codes | Message | Recovery Action |
---|---|---|
HSCL1965 | Unable to determine the Hardware Management Console server's host name. Check the Hardware Management Console network settings under System Configuration and verify that they are correct. | Check the HMC Network Settings under System Configuration and verify the settings are correct, and that you have a valid host name for the HMC. Contact your System/Network Administrator for network settings help. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL1966 | You must select one profile for powering on the Full System Partition or select Cancel. | Select a profile from the Power-on panel or select Cancel to close the panel. |
HSCL1967 | You must select one system profile to power on with or select Cancel. | Select a system profile from the panel or select Cancel to close the panel. |
HSCL1968 | You must select a power on option or select Cancel. | Select either Full System Partition or Partition Standby to turn on the power or select Cancel to close the panel. |
HSCL1969 | Could not retrieve information from the GUI server. Check your network configuration and connection. | Check the HMC network settings under System Configuration and verify the settings are correct. Follow the procedures in this guide. If the problem persists, contact the HMC support organization. |
HSCL196A | Choose a new default profile from the list or select Cancel. | None |
HSCL196B | The object is not found in the data area. Please refresh the interface. |
|
HSCL196C | Problem obtaining object information. Please refresh the interface |
|
User Management Error Codes | Message | Recovery Action |
---|---|---|
HSCL2329 | The following characters cannot be used in the login name: space , : ( ) [ ] ' | & ; * $ " | Specify a login name using valid characters. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL232A | The user name already exists or may be a user name reserved by the Hardware Management Console. Choose another user name. | User names must be unique. Choose a different user name. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL232B | The user login name cannot be longer than 32 characters. Choose another login name with less than 32 characters. | Choose a new login name that uses less than 32 characters. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL232C | The user must have a role. Select a role from the list. | User must have a role assigned. Choose a role from the menu list. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL232D | Could not modify user's property. |
|
HSCL232E | Could not create user. | Check to see the create command in debug print. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL232F | The Hardware Management Console user cannot be deleted. | None |
HSCL2330 | The new password and confirmation password do not match. Try again. | New password and confirmation password must match. Enter the new password again. |
HSCL2331 | Change user password failed. |
|
HSCL2332 | The Hardware Management Console user properties cannot be changed. | Cannot change the HMC special user properties. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL2333 | Multiple roles are not allowed. Select only one role from the role list. | Select only one role from the role list. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL2334 | Cannot create or modify the user due to the following reasons:
| If the problem persists, call for HMC software support. |
HSCL2336 | The user name is not valid. The user name cannot start with: space, !, @, #, $, %, ^, &, *, (, ), -, +, =. | Specify a user name that contains valid characters. Follow the procedures in this guide. If the problem persists, call for HMC software support. |
HSCL2337 | Cannot delete the user due to the following reasons:
| If the problem persists, call for HMC software support. |
HSCL251E | Failed to set the 'enable remote virtual terminal' option |
|
HSCL251F | The following error was encountered: \n{0}\n. Retry the operation. |
|
HSCL2726 | An affinity LPAR configuration already exists. You must remove this configuration before setting up a new affinity LPAR configuration. |
|
HSCL2727 | The operation failed. It is possible that another user is in the process of creating or updating affinity logical partitions. If this is not the case, restore profile data and retry the operation. |
|
HSCL2728 | Your partition names are not all unique. No partitions have been created. Make sure that all partition names are different from each other and those of already created partitions. | Try setting up an affinity LPAR configuration again, using unique names for every partition, both LPAR and affinity LPAR. |
HSCL2729 | Affinity LPAR creation failed. Retry the operation. |
|
HSCL272A | An error occurred in partition creation. Default profiles and the system profile may have to be created manually. First, rebuild the managed system, and then create items if needed. |
|
HSCL272B | An error occurred in default profile creation. Default profiles and the system profile will have to be created manually. First rebuild the managed system, and then create the needed items. |
|
HSCL272D | An error occurred in default profile creation. The system profile will have to be created manually. First rebuild the managed system, and then create the missing system profile. |
|
HSCL272E | An unknown error occurred during partition creation. |
|
HSCL272F | An error occurred in partition creation. Affinity partitions have been created, but default profiles and the system profile may have to be created manually. First, recover partition data, and then create items if needed. |
|
HSCL2730 | Unable to get the resources of the partition since it is not an affinity logical partition |
|
HSCL2731 | The addition of affinity logical partitions exceeds the maximum limit. Delete other partitions and retry the task. | Delete enough logical partitions and then retry the task. |
HSCL2734 | Cannot create only one affinity logical partition. | The user must create as many affinity LPAR partitions as resources will allow at the same time. To create an affinity LPAR configuration, use the Affinity Partition option. |
HSCL2735 | Cannot delete only one affinity logical partition. | The user must delete all affinity LPAR partitions at the same time. To delete an affinity LPAR configuration, use the Affinity Partition option. |
HSCL2736 | The update operation cannot be performed since there are no affinity logical partitions |
|
HSCL2737 | The operation failed since the update parameter is invalid. |
|
HSCL2738 | The operation failed since the cluster size parameter is invalid. |
|
HSCL2739 | The update operation failed since the hardware resources have not changed. |
|
HSCL273A | The managed system is not affinity LPAR capable. | None. If you are certain that the managed system is or should be affinity LPAR-capable, contact software support. |
HSCL273B | The managed system cannot handle the creation of partitions with the specified cluster size. | None. If you are certain that the managed system supports partitions of the specified cluster size, contact software support. |
HSCL273C | Affinity LPAR deletion failed. Rebuild the managed system and retry the operation. |
|
HSCL273D | Deletion of affinity logical partitions failed. Recover partition data and retry the operation. |
|
HSCL273E | Deletion of partition {0} failed. The partition cannot be deleted in the Running or Initializing state. Stop the partition and retry the task. |
|
HSCL2901 | This partition is not capable of adding, removing, or moving processors dynamically. | If you know that this partition is capable of processor DLPAR operations, make sure the managed system is powered on, wait and retry the task. If this does not work, rebuild the managed system, or reboot the HMC if necessary. Contact your local representative for more information about this feature. |
HSCL2902 | The destination partition is not capable of adding, removing, or moving processors dynamically. | If you know that this partition is capable of processor DLPAR operations, make sure the managed system is powered on, wait and retry the task. If this does not work, rebuild the managed system, or reboot the HMC if necessary. Contact your local representative for more information about this feature. |
HSCL2903 | Your processor request goes below the profile's Required processor limit. You can remove or move {0} or fewer processors. Retry the operation. | Retry the operation, entering a smaller number of processors. |
HSCL2904 | Your processor request exceeds the profile's Maximum processor limit. You can add or move up to {0} processors. Retry the operation. | Retry the operation, entering a smaller number of processors. |
HSCL2905 | This partition is not capable of adding, removing, or moving memory dynamically. | If you know that this partition is capable of DLPAR memory operations, make sure the managed system is powered on, wait and retry the task. If this does not work, rebuild the managed system, or reboot the HMC if necessary. Contact your local representative for more information about this feature. |
HSCL2906 | The destination partition is not capable of adding, removing, or moving memory dynamically. | If you know that this partition is capable of DLPAR memory operations, make sure the managed system is powered on, wait and retry the task. If this does not work, rebuild the managed system, or reboot the HMC if necessary. Contact your local representative for more information about this feature. |
HSCL2907 | Your memory request exceeds the profile's Maximum memory limit. You can add or move up to {0} MBs of memory. Retry the operation. |
|
HSCL2908 | Your memory request goes below the the profile's Minimum memory limit. You can remove or move up to {0} MB of memory. Retry the operation. |
|
HSCL2909 | Your memory requst exceeds the total available memory of the managed system. You can add up to {0} MB of memory. Retry the operation. |
|
HSCL290B | This partition is not capable of adding, removing, or moving IO slots dynamically. | If you know that this partition is capable of DLPAR memory operations, make sure the managed system is powered on, wait and retry the task. If this does not work, rebuild the managed system, or reboot the HMC if necessary. Contact your local representative for more information about this feature. |
HSCL290C | The destination partition is not capable of adding, removing, or moving IO slots dynamically. | If you know that this partition is capable of DLPAR memory operations, make sure the managed system is powered on, wait and retry the task. If this does not work, rebuild the managed system, or reboot the HMC if necessary. Contact your local representative for more information about this feature. |
HSCL290D | Since the managed system is not capable of dynamic logical partitioning, you cannot unassign resources. | None |
HSCL290E | Since the managed system is not capable of dynamic logical partitioning, you cannot correct requested memory values. | None |
HSCL290F | The partition cannot be activated because there are not enough free processors to satisfy the patition's requirements. However, there are stopped processors available which are still assigned to running partitions that you may unassign. | Attempt to restore lost processors. For more information, see Restoring Processor Resources. When you are finished, try to activate partition again. |
HSCL2907 | Your memory request exceeds the profile's Maximum memory limit. You can add or move up to {0} MB's of memory. Retry the operation. |
|
HSCL2908 | Your memory request goes below the the profile's Minimum memory limit. You can remove or move up to {0} MB of memory. Retry the operation. |
|
HSCL2909 | Your memory requst exceeds the total available memory of the managed system. You can add up to {0} MB of memory. Retry the operation. |
|
HSCL2910 | The partition cannot be activated because there are not enough free adapters to satisfy the patition's requirements. However, there are stopped adapters available which are still assigned to running partitions that you may unassign. | Attempt to restore lost adapters. For more information, see Restoring Adapter Resources. When you are finished, activate partition again. |
HSCL2911 | The partition cannot be activated because there is not enough available system memory to satisfy the profile's required amount. However, there is some memory available which was requested by running partitions but is not being used that you may unassign. | Correct the requested memory value. For more information see Restoring Memory Resources. When you are finished, activate the partition again. |
HSCL3001 | LED operations are not supported with this CSP version. For LED operations, please upgrade to CSP version 3.0 or greater. | To upgrade to a higher version of CSP, contact your service representative. |
HSCL3002 | The LED operation failed. | Retry the operation. If the problem persists, contact hardware support. |
HSCL3051 | An error occurred during frame initialization. Not all I/O may have been powered on. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL3052 | An error occurred during frame initialization. Not all managed systems could be powered on. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support |
HSCL3053 | An unknown error occurred during frame initialization. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL3054 | An error occurred during frame initialization. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL3055 | An error occured while deactivating CSPs. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL3056 | An error occurred during the pinhole reset. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL3057 | An error occurred while deactivating I/O drawers. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL3058 | Frame information retrieval failed. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL3059 | The refresh operation failed. Retry the operation. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL305A | The wrong number of cages was received. The I/O cages must be specified in pairs. Retry the operation. | Retry the operation, specifying the adapter drawers in pairs. There should be an even number of drawers specified. If the problem persists, contact HMC software support. |
HSCL305B | The list of I/O drawers to deactivate was not sent correctly. Please send the cage numbers of the I/O drawers in pairs. | Retry the operation, sending the cage numbers of the adapter drawers in pairs. |
HSCL3200 | Unknown lock error. | Contact HMC software support. |
HSCL3201 | Invalid lock type. | Contact HMC software support. |
HSCL3202 | Failed to acquire lock because of timeout. | Retry the operation. If the problem persists, contact HMC software support. |
HSCL3203 | Illegal nested lock type requested. | Contact HMC software support. |
HSCL3204 | Lock not held. | Contact HMC software support. |
Platform Management Error Codes | Message | Recovery Action |
---|---|---|
HSCP0001 | The Backup Critical Data request completed successfully. | None |
HSCP0002 | Please make sure that the media is inserted properly in the drive and retry the operation. | Verify that the media is inserted correctly in the drive and try the operation again. |
HSCP0003 | The Backup Critical Data request failed. | Internal HMC Error. Call for HMC software support. |
HSCP0004 | The media is write protected. Remove the write protection and retry the operation. | Remove the write protection and try the operation again. |
HSCP0005 | The Backup Critical Data request is in progress. Please wait. | None |
HSCP0010 | The Format Removable Media request completed successfully. | None |
HSCP0011 | Please make sure the media is inserted properly in the drive and retry the operation. | None |
HSCP0012 | The media is write protected. Remove the write protection and retry the operation. | None |
HSCP0013 | An unknown error occurred. Replace the media and retry the operation. | Replace the media and try the operation again. If the error persists, call for HMC software support. |
HSCP0014 | The Format Removable Media request failed. |
|
HSCP0015 | Please wait while the media is being formatted. | None |
HSCP0020 | The Save Upgrade Data request completed successfully. | None |
HSCP0021 | The Save Upgrade Data request failed. |
|
HSCP0022 | The Save Upgrade Data request failed. Ensure the removable media is properly inserted in the drive. | Verify the removable media is properly inserted in the drive and try the operation again. If the error persists, call for HMC software support. |
HSCP0023 | The media is write protected. Remove the write protection and retry the operation. | None |
HSCP0024 | An error occurred while copying the upgrade data. Ensure the removable media is properly inserted in the drive and retry the operation. | Verify the removable media is properly inserted in the drive and try the operation again. If the error persists, call for HMC software support. |
HSCP0025 | An error occurred while compressing the upgrade data. Please retry the operation. |
|
HSCP0026 | An error occurred while trying to mount the media. Ensure the removable media is properly inserted in the drive. |
|
HSCP0027 | An error occurred while trying to unmount the media. |
|
HSCP0028 | An error occurred while creating the list of files to save. |
|
HSCP0029 | An error occurred while instantiating the save upgrade data target class. |
|
HSCP0030 | An error occurred while attempting to create the restore trigger file. |
|
HSCP0040 | The corrective service file was successfully downloaded to this system console. Press OK to continue and install this update. | None |
HSCP0041 | The corrective service file was successfully applied. Please quiesce the system console and reboot for the changes to take effect. | None |
HSCP0042 | An unrecoverable error occurred during the corrective service file download. Retry the operation. If the operation fails again, contact your support representative. | Try the operation again. If the error persists, call for HMC software support. |
HSCP0043 | An unrecoverable error occurred during the corrective service installation. Retry the operation. If the operation fails again, contact your service representative. | Try the operation again. If the error persists, call for HMC software support. |
HSCP0044 | The removable media cannot be mounted. Please make sure the media is inserted properly in the drive and retry the operation. |
|
HSCP0045 | The corrective service data is corrupt. Please ensure the correct media is inserted properly in the drive and retry the operation. | Verify the removable media is properly inserted in the drive and try the operation again. If the error persists, call for HMC software support. |
HSCP0046 | An error occurred while attempting to remotely connect to the server. Please try the operation again. If the operation fails again, contact your service representative. | Verify that the remote site is operational and try the operation again. If the error persists, call for HMC software support. |
HSCP0047 | An error occurred while downloading the corrective service file. Please try the operation again. If the operation fails again, contact your service representative. | Verify that the remote site is operational and try the operation again. If the error persists, call for HMC software support. |
HSCP0048 | An unknown error occurred. Retry the operation. If the operation fails again, contact your support representative. | Try the operation again. If the error persists, call for HMC software support. |
HSCP0049 | The Install Corrective Service request is in progress. Please wait. | None |
HSCP0060 | The Customize Date/Time request completed successfully. | None |
HSCP0061 | The Customize Date/Time request failed. |
|
HSCP0070 | Please enter an integer value between 1 and 99. | None |
HSCP0080 | There are no system events. | None |
HSCP0081 | Unable to display the log data. |
|
HSCP0082 | Unable to retrieve log data. |
|
HSCP0083 | An error occurred while processing the exit request. |
|
HSCP0090 | Cannot check both the 'Export default gateway' and 'Silent' options for 'routed'. | Select either 'Export default gateway' or 'Silent' for the Routed option. |
HSCP0091 | You may need to reboot for all Network Settings changes to take effect. | Restart the HMC. |
Service Focal Point Error Codes | Message | Recovery Action |
---|---|---|
HSCS0001 | Unable to access RMC to obtain Serviceable Events. | The HMC could not retrieve the Serviceable Events. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0002 | Unable to process request. | The HMC could not process your request. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0003 | Unable to update the attribute on the Serviceable Event. | The HMC could not process your request to make changes to the Serviceable Event. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0004 | Unable to locate Serviceable Event to update. | The HMC could not locate the Serviceable Event you are trying to view or update. It may have expired or otherwise been closed. Exit the Select Serviceable Event dialog and retry. |
HSCS0005 | Function Failed: Error occurred attempting to display a Serviceable Event panel. | The HMC was unable to locate or launch a panel you have requested.
This is an internal HMC error.
|
HSCS0006 | This Serviceable Event may contain more information that this version of the HMC can display. You may wish to upgrade your HMC to the latest version. | In order to see Serviceable Event data made available in more recent HMC versions, upgrade this HMC to the most recent version or switch to an HMC that has already been upgraded. |
HSCS0008 | Function Failed: An error occurred when retrieving machine names. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0020 | Function Failed: An error occurred when launching the Service Focal Point Settings panel. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0021 | Function Failed: Error occurred getting information to display the Service Focal Point settings. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0022 | Function Failed: An error occurred when updating Service Focal Point settings. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0023 | Function Failed: Error occurred processing button for the Service Focal Point Settings Panel. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0024 | Function Failed: Error occurred processing sort for the Service Focal Point Settings Panel. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0025 | Function Failed: Error occurred processing Double Click for the Service Focal Point Settings Panel. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0026 | Service Focal Point settings have been saved successfully. | None. |
HSCS0032 | Function Failed: An error occurred when updating Extended Error Enable/Disable settings. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0040 | New FRU Location Code and Part Number must be entered. | Enter the requested Location Code and Part Number. |
HSCS0041 | A New FRU Part Number must be entered. | Enter the requested Part Number. |
HSCS0042 | There was nothing to apply. | There were no changes to the FRU list to be added to the Serviceable Event. |
HSCS0043 | The No FRUs to Update box was checked but there are updated FRUs in the in the pending table. If there are no FRUs to update, remove the ones from the pending table. If you want to update the FRUs from the pending table, uncheck the check box. | None |
HSCS0044 | The No FRUs to Update box was unchecked and there are no updated FRUs in the in the pending table. If there are no FRUs to update, check the check box to indicate this. | None |
HSCS0045 | Function Failed: An error occurred when updating FRU information for the Serviceable Event. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0046 | Function Failed: An error occurred when attempting to remove an item from the list. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0047 | Function Failed: An error occurred when attempting to Close the Serviceable Event | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0048 | Function Failed: An error occurred when adding FRU information for the Serviceable Event. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0049 | Function Failed: An error occurred when processing the panel. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0050 | Function Failed: An error occurred when launching panel. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0060 | Cannot change state from Unknown for machine | The requested machine state is not allowed at this time. Close and then restart the Enable/Disable panels for updated machine information. |
HSCS0061 | Insert scratch diskette number {0} of {1}. | Insert a scratch diskette and select the appropriate button. |
HSCS0062 | Insert DVD cartridge and press the {0} button. | Insert a formatted DVD cartridge and push the appropriate button. |
HSCS0064 | No extended error data available. | Select a serviceable event that has extended error data associated with it. |
HSCS0065 | Error writing to floppy diskette: {0} | Make sure there is a floppy diskette in the diskette drive. Try the operation again. |
HSCS0066 | Error writing to DVD cartridge: {0} | Make sure there is a formatted DVD cartridge in the DVD drive. Try the operation again. |
HSCS0067 | Error reading extended error data: {0} | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0068 | Error creating temporary file: {0} |
|
HSCS0069 | Error writing to temporary file: {0} |
|
HSCS0070 | Error formatting floppy diskette: {0} | Make sure there is a floppy diskette in the diskette drive. Try the operation again. |
HSCS0071 | Extended error data has been saved successfully. | None |
HSCS0072 | The saving of extended error data has been cancelled. | No action. The operation was cancelled as a result of your request. |
HSCS0080 | Error encountered while getting the partition information. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0081 | Error encountered while reading the partition information. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0082 | Error encountered while getting the extended error data. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0083 | Unexpected error encountered while saving the extended error data. |
|
HSCS0084 | Error encountered while attempting to call home with the extended error information. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0085 | Error encountered while attempting to call home with the extended error information. The call program returned a value of {0}. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0086 | Request to call home the extended error information has been successfully submitted. See the Service Agent application to monitor the progress of the request. | The operation was successful. Use the Service Agent application to monitor the progress of the request. |
HSCS0087 | Error encountered while attempting to call home the Serviceable Event. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0088 | Error encountered while attempting to call home the Serviceable Event. The callsa program returned a value of {0}. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0089 | Request to call home the Serviceable Event has been successfully submitted. See the Service Agent application to monitor the progress of the request. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0090 | Unexpected return code encountered while creating a temporary packaging file: {0} | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0096 | No items selected when button was pressed. | Not all functions may be operating. Wait and try the previous function again. If error continues, shut down and restart the HMC. If error persists, call for HMC software support. |
HSCS0100 | Please wait while the extended error data is being saved. | The extended error data is being saved to the appropriate removable media. |
HSCS0101 | Error writing to DVD cartridge. | Ensure there is a formatted DVD cartridge in the DVD drive. Try the operation again. |
HSCS0102 | Error unmounting DVD cartridge after writing data successfully. | Ensure there is a formatted DVD cartridge in the DVD drive. Try the operation again. |
HSCS0103 | DVD drive is already mounted. | None |
HSCS0104 | The LED request did not complete successfully. |
|
HSCS0105 | The LED request completed successfully. | None. |
HSCS0106 | Function failed: An error occurred attempting to display the LED Management panel. |
|
HSCS0122 | Function failed: An error occurred attempting to display the Hardware Services panel. |
|
HSCS0123 | The System Attention LED for the selected machine is not supported. The system LED will not be activated | None. |
HSCS0124 | The Identify LED for the selected FRU is not supported. The FRU LED will not be activated. | None. |
When using a virtual terminal (VTERM), you might see an error code
displayed in the bottom-left corner of the VTERM window. The following
table lists the error codes and the recovery actions for each.
Virtual Terminal (VTERM) Error Codes | Message | Recovery Action |
---|---|---|
Comm 654 | The virtual terminal server is unable to process this type of
request.
An unknown error occurred during virtual terminal device-type negotiations. | If the error persists, contact the system administrator for help. |
Comm 655 | The socket connection to the Virtual Terminal server has been established and the session is waiting for negotiation to finish. | If the error persists, contact the system administrator for help. |
Comm 657 | The session is in the process of establishing the TCP/IP connection to
the virtual terminal server.
When you close a session that displays COMM 657, there may be some delay before it closes. | The delay varies. You can close the browser. |
Comm 658 | The session is initializing the TCP/IP connection to the HMC. | If the error persists, contact the system administrator for help. |
Comm 659 | The Virtual Terminal TCP connection to the session has not succeeded or has failed. |
|
In the Contents area, an operating state is listed next to your managed system. Read the next section to learn more about what each of these states mean, and the actions you should take to recover.
The following operating states apply to the managed system itself.
State | Description | Recovery Action |
---|---|---|
Initializing | The managed system is powered on and is initializing. | Wait for initialization to complete. Initialization can take up to an hour, depending on the managed system's hardware and boot configuration. |
Ready | The managed system is powered on and functioning normally. | None |
No Power | The managed system is powered off. | None |
Error | The managed system's operating system or hardware is experiencing errors. | If the managed system is set up to run as a Full System Partition, the system will also indicate an Error state. Read the managed system operator panel. |
Incomplete | The HMC cannot gather complete partition, profile, and resource information from the managed system. | In the Contents area, highlight the managed system icon and select Rebuild the Managed System from the menu. |
No Connection | HMC cannot contact the managed system. |
|
Recovery | The partition and profile data stored in the managed system is corrupted. | In the Contents area, select the managed system icon and choose
Recover Partition Data from the menu.
|
Version Mismatch | Your managed system's service processor level is higher than your HMC's code level. | Contact your service representative to upgrade your HMC's level so that the levels match. |
CUoD CTA | You must accept the CUoD license. | To accept the license, do any of the following:
|
The following operating states describe the logical partition you have
created.
State | Description | Recovery Action |
---|---|---|
Ready | The partition is not yet active but is ready for activation. | None |
Starting | The partition is activated and is going through its booting routines. | None |
Running | The partition has finished its booting routines. The operating system can be performing its booting routines or is in its normal running state. | None |
Error | Activation of this partition failed due to a hardware or operating system error. | Select the partition and choose the Read Boot Error Value task from the menu to see the reasons for the activation failure.Boot Error Values You can also try to activate the partition again. |
Not Available | This partition is not available for use. Reasons can
include:
| Turn on the power to the managed system and select either Full System Partition or Partition Standby during the power-on process. |
Open Firmware | The partition was activated by a profile that specified an OPEN_FIRMWARE boot mode. | None |
The following section has procedures to help you restore partition resources that are stopped but are still assigned to a partition as a result of a failed dynamic logical partitioning operation. These resources are lost, or are unusable by any other partition until they have been unassigned.
When you are dynamically adding processor resources to a partition, the HMC determines if there are any stopped processors in a running partition. If the HMC finds stopped, unused processors, a Processor Information button appears on the panel. When you click this button, the Processor Recovery window opens. This window displays each stopped processor's states, statuses, and the partitions to which they are currently assigned.
If no partition is performing a dynamic logical partitioning processor operations, you can unassign stopped processors from their partitions and free them for system use.
To unassign stopped processors, do the following:
When you are dynamically adding adapter resources to a partition, the HMC determines if there are any stopped adapters in any running partition. If the HMC finds stopped, unused adapters, an Adapter Information button appears on the panel. When you click this button, the Restore Adapters window opens. This window displays each stopped adapter's state, status, and the partition to which it is assigned. If another user is not performing a dynamic logical partition operation, you can unassign stopped adapters from their partitions and free them for system use.
To unassign stopped adapters from a running partition, do the following:
When you are dynamically adding, removing, or moving memory resources to a partition, the HMC determines if there is an inconsistency between the amount of memory being used by the partition and the amount of memory requested by the partition for pending memory changes.
If these amounts are not equal, a Memory Information button appears on the window. When you click this button, the Restore Memory window opens. This window displays each running partition's amount of memory in use, requested memory amount, the maximum and minumum profile memory values, and the total available system memory. If another user is not performing any dynamic logical partitioning memory operations, you can correct a partition's requested memory value amount so that it is equal to the memory amount currently in use. If the requested memory value is greater than the amount of memory actually in use, a correction of the requested memory amount will result in some memory being freed for other partitions to use. If another user is in the middle of performing a dynamic logical partitioning memory operation on a partition, and you correct the requested memory amount for that partition, you will cause the other user's dynamic logical partitioning operation to fail.
To correct requested memory amounts, do the following:
The recovery action for many error messages is to perform a rebuild managed system operation. This section has procedures to help rebuild a managed system. References to this procedure are indicated throughout the error message tables as appropriate.
For messages that indicate that a rebuild managed system operation is needed, do the following to be sure that the operation is necessary:
To rebuild a managed system, do the following:
While this task is running, you cannot perform any other HMC functions. This task can take up to several minutes to complete.
To reboot the HMC, do the following:
In the event of an unexpected power loss or if the white reset button on the HMC is pressed, the system runs a file system check (fsck) on the next system reboot. If the automatic file system check fails, the HMC prompts the user to enter the HMC's root password so that it can perform a manual file system maintenance operation. If the following message displays: Enter the root password or hit Control-D to reboot., do the following to recover the HMC:
OR
Press Ctrl-D to reboot the HMC interface.
If you need to change the host name of the partition manually, before changing the host name of the partition, do the following:
The output displayed will be similar to the following: (If the partition is managed by multiple HMCs, there may be multiple entries, since each HMC has its own entry.)
resource 1: Hostname = "hmc1.mydomain.mycompany.com"
This section describes the states for a managed system that display on the HMC. Follow the procedures in this section to attempt to restore management of a system in one of the listed states.
The HMC has lost contact with the managed system, or power to the service processor has been removed. Do the following:
If the partitions are active, do the following:
The HMC is unable to collect information required to build a complete representation of the managed system. Do the following:
If the status remains Incomplete, verify whether there is a redundant HMC and verify that no one is entering commands from the alternate HMC.
Repeat step 1. If it still fails, go to the next step.
Profile data stored in the managed server has been cleared or corrupted. Do the following:
Error state automatically generates a call to the service support center if the function is enabled. If the function is not enabled, call for HMC software support.
The partition has been activated and is in the Open Firmware state. You can open a virtual terminal to the partition and enter open firmware commands.
The following table contains the boot error values and messages that might
display on the HMC if a problem occurs during the boot process and initial
loading of the console software.
Boot Error Values | Message |
---|---|
0x00 | NO_ERROR |
0x01 | NO_GLOBAL_SERVER |
0x02 | NO_CONTIGUOUS_PAGE_TABLE_MEMORY |
0x03 | NO_CONTIGUOUS_REAL_MODE_MEMORY |
0x04 | NOT_ENOUGH_PARTITION_LOGICAL_MEMORY |
0x05 | ALL_ASSIGNED_PROCESORS_ARE_NOT_WORKING |
0x06 | NO_PROCESSORS_ASSIGNED |
0x07 | INVALID_PROCESSOR_ASSIGNED_FOR_ALPAR_PARTITION |
0x08 | NO_MEMORY_AVAILABLE_FOR_ALPAR_PARTITIONS |
0x60 | ANOTHER_SERVICE_AUTHORITY_PARTITION_IS_ACTIVE |
0x7F | FAIL_TO_BOOT |
0x80 | I/O_SLOT_ASSIGNMENT_ERROR |
0xAC | AIX_OS_TERM_WITH_CRASH_CODE |
If you have two HMCs connected to your managed system, one HMC temporarily locks the other out while it is performing operations. This action prevents the other HMC from operating on the managed system because simultaneous operations could cause conflicting results. If the interface is locked, most console operations automatically wait for the lock to release.
However, in the rare event that an HMC has a problem that prevents the lock from being properly released, you may need to manually unlock the connection to the managed system. Typically, if one HMC has locked the connection, you must unlock it from the other HMC, which then allows other HMCs to communicate with the managed system and run further commands.
To release a lock on a managed system, you must be a member of one of the following roles:
To release an HMC lock, do the following: