Error/Message
Codes: |
There are several different sources for errors in Disk
Management. There are currently a number of error codes defined by DSM. These
errors will be reported directly to the client as part of a 4 byte unsigned
integer with a modifier according to the following:
DM Error hex 0000 XXXX
DASD Storage Management Error hex 0001 XXXX
ValidateConfiguration Error hex 0002 XXXX
Clustering Error hex 0003 XXXX
The errors that are returned will be stripped of their leading 0's
DM Errors include all errors not indicated by DASD Storage Management or
ValidateConfiguration errors and include parameter validation errors, and DM
unexpected exceptions.
|
|
Description |
MessageID |
|
Action Related: |
|
Description: Handle not valid. Either the handle was not
used within the specified timeout (DM interface is in closed status), or the
handle is not the one provided by the open session tag.
Recovery: None. You may re-open a session to create a new
handle. |
0x00000001 |
|
Description: Another client (either through the API or
through the green screen interface) is currently using DM function. The
SessionType (GUI or GreenScreen) will be returned in the MessageData.
Recovery: None. You must wait for the other client to
finish. |
0x00000002 |
|
Description: Action Failed
Recovery: An internal server error occurred. |
0x00000004 |
|
Description: Action Successfully Started
Recovery: None. |
0x00000005 |
|
Description: Action cannot be started. Action already in
progress
Recovery: None. |
0x00000006 |
|
Description: Session needs to be opened
Recovery: Open a session before submitting this action. |
0x00000007 |
|
Description: Unknown Error
Recovery: None. An internal server error occurred. |
0x00000008 |
|
Description: No Authority for this action
Recovery: Log into the server with the appropriate authority
required for this action. |
0x00000009 |
|
Description: Unable to perform an override (for the
Override tag)
Recovery: Server is not paused, and does not require an
override. |
0x0000000a |
|
Description: Cannot Open session
Recovery: Close down all clients, ensure no actions are
running. |
0x0000000c |
|
Description: Cannot Close session
Recovery: None. Session is no longer active. No need to
close. |
0x0000000d |
|
XML Parser Related: |
|
Description: XML Parsing Error
Recovery: Unable to parse the XML stream. Check your XML with
the DTD. |
0x00000060 |
|
Description: Tag Invalid
Recovery: Check your XML with the DTD. |
0x00000070 |
|
Description: Tag Missing
Recovery: Check your XML with the DTD. |
0x00000071 |
|
Description: Sub Tag Invalid
Recovery: Check your XML with the DTD. |
0x00000078 |
|
Description: Sub Tag Missing
Recovery: Check your XML with the DTD. |
0x00000079 |
|
Description: Attribute Invalid
Recovery: Check your XML with the DTD. |
0x00000080 |
|
Description: Attribute Missing
Recovery: Check your XML with the DTD. |
0x00000081 |
|
Description: Attribute Value Invalid
Recovery: Check your XML with the DTD. |
0x00000088 |
|
Description: Attribute Value Missing
Recovery: Check your XML with the DTD. |
0x00000089 |
|
Mirroring Related: |
|
Description: Unable to suspend a mirrored disk unit
Recovery: Ensure unit's mirrored pair is not suspended. |
0x00000304 |
|
Description: Disk unit not mirrored
Recovery: Start mirroring on disk unit. |
0x00000305 |
|
Description: Replacement disk unit still active
Recovery: Suspend mirroring on the replacement disk. |
0x00000308 |
|
Description: Unable to mirror load source
Recovery: Enable remote load source mirroring. |
0x0000030c |
|
Description: Mirrored pair not suspended
Recovery: Suspend mirrored pair. |
0x0000030d |
|
Disk Unit Related: |
|
Description: Unable to power off disk unit
Recovery: None. |
0x00000400 |
|
Description: Unable to power on disk unit
Recovery: None. |
0x00000401 |
|
Description: Disk unit has errors
Recovery: Run ScanDisk on unit. |
0x00000402 |
|
Description: Disk unit not found
Recovery: Ensure disk unit exists and that it has reported to
the system. |
0x00000403 |
|
Description: Disk unit configured
Recovery: Remove disk unit from an ASP or select a different
unit. |
0x00000406 |
|
Description: Disk unit in bad Parity state (Failed,
Unprotected, or Rebuilding)
Recovery: If rebuilding, wait for it to finish, if failed,
replace unit and rebuild parity, if unprotected, start parity. |
0x00000407 |
|
Description: Not valid for the load source
Recovery: None. |
0x00000408 |
|
Description: Disk unit not missing
Recovery: None. Disk unit must be missing before this action
may be run. |
0x00000409 |
|
Description: Disk unit has no read error on LDI
Recovery: None. Disk unit does not need to be rebuilt |
0x0000040a |
|
Description: Disk pair have different capacities
Recovery: Choose a disk with the same capacity. |
0x0000040b |
|
Description: Disk pair have different compression
status
Recovery: Chose a disk with the same compression status. |
0x0000040c |
|
Description: Disk unit not eligible for action
Recovery: None. |
0x0000040d |
|
Description: Disk unit not configured
Recovery: Add disk unit to an ASP. |
0x0000040e |
|
Description: Disk unit missing
Recovery: Run AssignDisk Action on this unit. |
0x0000040f |
|
Description: Disk unit not eligible for copying
Recovery: None. |
0x00000410 |
|
Description: Disk unit cannot be renamed to the specified
name (DTDVersion = 10)
Recovery: Ensure the new name follows the naming guidelines
for resource names (10 alphanumeric characters or less, with the first
character not being a number). Next, ensure that the resource name does not
already exist (check the Failed or Missing resources in Hardware Service
Manager). |
0x00000411 |
|
ASP Related: |
|
Description: Unable to add disk unit to a mirrored ASP, or
to Start Mirroring on an ASP (Cannot pair disk units)
Recovery: Ensure disk unit has a mirrored pair. |
0x00000500 |
|
Description: Same original and destination ASP
Recovery: Select a different destination ASP |
0x00000505 |
|
Description: ASP is protected
Recovery: Unprotect ASP. |
0x00000506 |
|
Description: Warning: System is not in an Independent
System Group (ISG)
Recovery: If you choose to continue, the System will be added
to a Stand Alone ISG. You will not be able to put the system in a clustering
environment until you delete the ASP you are creating. If you cancel, and add
the system as part of a Cluster Group First, it will automatically be put in a
Device Domain ISG, and you will not see this warning. |
0x00000507 |
|
Description: ASP not found
Recovery: Ensure ASP is varied on, and reporting. |
0x00000602 |
|
Description: Need to clear ASP before action can be
performed
Recovery: Clear ASP |
0x00000603 |
|
Description: ASP not mirrored
Recovery: Start mirroring on ASP. |
0x00000604 |
|
Description: ASP is mirrored
Recovery: Stop mirroring on ASP. |
0x00000605 |
|
Parity Related: |
|
Description: Disk unit not eligible for this parity
operation
Recovery: None. |
0x00000709 |
|
Description: Parity set needs manual intervention to
start
Recovery: Physically toggle the Parity switch on unit's
IOP. |
0x0000070a |
|
Description: Parity set does not exist
Recovery: Create parity set first. |
0x0000070b |
|
Description: Parity set needs manual intervention to
stop
Recovery: Physically toggle the Parity switch on unit's
IOP. |
0x0000070c |
|
Description: Disk unit is not in Parity Mismatch state
Recovery: None. Do not need to correct parity mismatch. |
0x0000070d |
|
Description: Parity set does not need to be rebuilt
Recovery: None. |
0x0000070e |
|
Cancel Errors: |
|
Description: Cannot Cancel Action
Recovery: None. This action may not be canceled. |
0x00000900 |
|
Description: No action to cancel
Recovery: None. No such action. |
0x00000901 |
|
Description: Action canceled
Recovery: None. Action successfully canceled. |
0x00000902 |
|
General Errors/Warnings: |
|
Description: General DM Error. Some internal error has
caused the DM operation to fail
Recovery: None. |
0x000000ff |
|
Description: IPL has not gone far enough. Not ready
Recovery: Wait for IPL to finish. |
0x00000a00 |
|
Description: Invalid configuration
Recovery: Run ValidateConfiguration action. |
0x00000a01 |
|
Description: A warning was not overridden by the user,
causing the action to fail
Recovery: None. |
0x00000a02 |
|
Description: IOP not found
Recovery: None. |
0x00000a03 |
|
Description: Frame not found
Recovery: None. |
0x00000a04 |
|
Description: Unable to block a task. Blocker already in
use. Shouldn't happen.
Recovery: IPL machine. |
0x00000a05 |
|
Description: The user needs to respond to a warning
message.
Recovery: Respond with an Override or a Cancel tag. |
0x00000a06 |
|
Description: Unable to start the partial IPL. This means
there is a problem with DASD Storage Management.
Recovery: None. |
0x00000a07 |
|
Description: Need to invoke ValidateConfiguration. Checker
returned with an error.
Recovery: Run ValidateConfiguration. |
0x00000a08 |
|
Description: An unknown error occurred while attempting to
do a partial IPL.
Recovery: None. |
0x00000a09 |
|
Description: There is no RIO Bus Adapter associated with
this frame.
Recovery: None. |
0x00000a10 |
|
Description: CRG not found.
Recovery: None. |
0x00000a11 |
|
DASD Storage Management
Errors/Warnings: |
|
Description: Units contained in both cleared and
non-cleared ASPs
Recovery: None. |
0x00010101 |
|
Description: Short delay required to prepare system
Recovery: The system must perform some internal processing to
proceed with the operation you requested. Without doing the internal processing
the system may not be able to perform certain operations related to the storage
management subsystem. Move units, remove units, start mirrored protection, and
start device parity protection are operations the system may not be able to
perform without doing the internal processing. |
0x00010102 |
|
Description: Long delay required for directory
recovery
Recovery: See 0x00010102. |
0x00010103 |
|
Description: No valid disk configuration.
Recovery: You attempted to recover the configuration of a
disk pool, however no valid configuration could be found. Check to see if the
disk pool is owned by another node at this time. |
0x00010104 |
|
Description: Could not find a valid mirror mate for load
source
Recovery: None. |
0x00010105 |
|
Description: User canceled internal function
Recovery: None. |
0x00010145 |
|
Description: Function not allowed after IPL past DST
Recovery: None. |
0x00010147 |
|
Description: Function not allowed in current state
Recovery: None. |
0x00010149 |
|
Description: Not allowed to move unit both to and from
same ASP
Recovery: None. |
0x0001014a |
|
Description: Not allowed to move units to or from a
mirrored ASP
Recovery: None. |
0x0001014b |
|
Description: Command to an IOP failed with no reference
code
Recovery: Check the Product Activity Log (PAL) for IOP
errors, then try the request again. |
0x0001014c |
|
Description: Machine pool is too small
Recovery: The machine pool is not large enough to provide the
storage required by this function. Increase the size of the machine pool with
the CHGSHRPOOL command and retry the operation. Or IPL the system in manual
mode and try the operation in the limited paging environment. |
0x0001014d |
|
Description: Long delay required for mirror
synchronization
Recovery: See 0x00010102. |
0x00010153 |
|
Description: Long delay required to prepare system
Recovery: See 0x00010102. |
0x00010154 |
|
Description: Problem encountered
Recovery: None. |
0x0001015A |
|
Description: Compression recovery needs to be
performed
Recovery: The selected operation can be performed only after
recover from start compression failure has been performed. Recover from start
compression failure can be performed from "Work with disk unit recovery" (Green
Screen). |
0x0001015B |
|
Description: Disk capacity limit exceeded
Recovery: The requested disk configuration change cannot be
completed because the resulting change causes the system's disk capacity limit
to be exceeded. For more information on the disk capacity limit for your system
model, refer to the i5 and iSeries System Handbook. |
0x0001015C |
|
Description: Compression operation failed
Recovery: Compression operation failed during the "Prepare to
Compress data" stage of the operation. To recover from this condition, you need
to perform "Start compression recovery" operation from "Work with disk unit
recovery" menu (Green Screen). |
0x0001015D |
|
Description: Machine pool has insufficient storage to
complete the requested operation.
Recovery: The machine pool is not large enough to provide the
storage required by this request. Increase the size of the machine pool by
using the Change Shared Storage Pool (CHGSHRPOOL) command through the system
command line in the character-based interface. Try the request again. Your
server may need to be fully operational before you change the size of the
machine pool. |
0x0001015F |
|
Description: The node (system) is already in a
SystemGroup
Recovery: Call Service. |
0x00010191 |
|
Description: The node (system) is NOT in a SystemGroup
Recovery: Call Service. |
0x00010192 |
|
Description: Moves to and from an Independent Disk Pool
are not allowed
Recovery: None. |
0x00010194 |
|
Description: Unable to create Independent Disk Pool
because not enough address ranges are available.
Recovery: Call Service. |
0x00010195 |
|
Description: Not allowed to create Independent Disk Pool
because this node must be restarted to clean up address ranges
Recovery: Restart system. |
0x00010196 |
|
Description: Another node has a configuration change in
progress
Recovery: Wait for the other node to finish, and try
again. |
0x0001019B |
|
Description: Node cannot communicate to other node in
cluster.
Recovery: The node cannot communicate to other node in
cluster. Make sure clustering is active. If necessary, start clustering
(STRCLUNOD), or fix the communications error. |
0x0001019C |
|
Description: Failed to initialize data port on target
node.
Recovery: Check IP addresses in the cluster resource group.
Fix the communication failure, and try the request again. |
0x0001019D |
|
Description: Failed to initialize data port on source
node.
Recovery: Check IP addresses in the cluster resource group.
Fix the communication failure, and try the request again.
If the problem persists, contact your technical support provider
|
0x0001019E |
|
Description: Machine pool has insufficient storage to
complete requested operation.
Recovery: The machine pool is not large enough to provide the
storage required by this request. Increase the size of the machine pool by
using the Change Shared Storage Pool (CHGSHRPOOL) command through the system
command line in the character-based interface. Try the request again. Your
server may need to be fully operational before you change the size of the
machine pool. |
0x0001019F |
|
Description: The system could not complete internal
processing successfully.
Recovery: Reclaim IOP cache storage on the target node. Try
the request again. If the problem persists, contact your technical support
provider.
|
0x000101A0 |
|
Description: The system could not complete internal
processing successfully.
Recovery: Reclaim IOP cache storage on the target node. Try
the request again. If the problem persists, contact your technical support
provider.
|
0x000101A1 |
|
Description: Disk capacity limit exceeded.
Recovery: The requested disk configuration change cannot be
completed because the resulting change causes the system's disk capacity limit
to be exceeded. Remove disk units on the target node, or upgrade model to a
larger limit. |
0x000101A2 |
|
Description: An unexpected error occurred.
Recovery: Try the request again. If the problem persists,
contact your technical support provider |
0x000101A3 |
|
Description: Operation causes ASP to exceed capacity
Recovery: The operation you requested is not permitted
because there is insufficient storage in one or more ASPs. You must make room
for the data before the operation you requested can be performed. |
0x00010201 |
|
Description: Operation causes ASP to exceed threshold
Recovery: The operation you requested is not permitted
because performing it will result in the threshold being exceeded in one or
more ASPs. You must make room for the data before the operation you requested
can be performed. |
0x00010202 |
|
Description: Odd number of units of equal capacity
selected
Recovery: A mirrored unit is composed of two sub-units of the
same capacity and the same compression state. The disk configuration change
requested can not be completed because the system could not pair all
unprotected units in the following ASPs to create a valid mirrored
configuration. Press F1 to see the help screen and the recovery
procedures. |
0x00010203 |
|
Description: ASP selected is marked to be cleared
Recovery: None. |
0x00010205 |
|
Description: ASP selected is already mirrored
Recovery: None. |
0x00010207 |
|
Description: ASP has missing units
Recovery: Replace the missing units. |
0x00010208 |
|
Description: ASP selected is not mirrored
Recovery: None. |
0x00010209 |
|
Description: There are no active units for a mirrored
pair.
Recovery: In order to stop mirroring, there must be at least
one active disk unit for each pair in the disk pool. The system detected at
least one pair for which it could not access an active unit. The situation can
occur when one of the units of a pair is suspended and the active mirrored unit
is missing (failed). |
0x0001020A |
|
Description: Duplicate disk pool name
Recovery: Use a different name. |
0x0001020B |
|
Description: Invalid disk pool name
Recovery: Use a different name. |
0x0001020D |
|
Description: This node has no more IASP numbers
Recovery: This node is unable to communicate with other
nodes, and cannot determine if a different node may have available IASP
numbers. Fix cluster communication and retry. |
0x0001020E |
|
Description: There are temporarily no more available IASP
numbers
Recovery: Wait for another node to finish a configuration
change, and try again. |
0x00010212 |
|
Description: Configuration source needs to be restored, or
its disk pool made available.
Recovery: The configuration source has previously been saved.
You will need to either restore the data on the configuration source disk unit,
or make its disk pool available before attempting this action. |
0x00010213 |
|
Description: The configuration source disk unit in the
independent disk pool does not contain the most recent data for the disk
pool.
Recovery: Try to locate the correct configuration source. If
necessary, you may need to replace the missing disk unit. |
0x00010214 |
|
Description: Unknown Configuration Source status
Recovery: Run "Recover Unknown Configuration Source". |
0x00010215 |
|
Description: Missing disk units.
Recovery: This action cannot be performed when a disk unit is
missing. Attempt to locate the missing disk unit. If necessary, replace the
missing disk unit, and retry the operation. |
0x00010216 |
|
Description: Disk pool is only partially restored
Recovery: Retry running "Recover" on the disk pool. If you
get this error again, you may have to clear the disk pool. |
0x00010217 |
|
Description: Start compression failure.
Recovery: Recover configured disk units. |
0x00010218 |
|
Description: LPAR Configuration error.
Recovery: Run LPAR Recovery. |
0x00010219 |
|
Description: Short delay required to prepare system
Recovery: See 0x00010102. |
0x0001021A |
|
Description: Long delay required for directory
recovery
Recovery: See 0x00010102. |
0x0001021B |
|
Description: IASP must be varied off before carrying out
this action
Recovery: Vary off IASP. |
0x0001021C |
|
Description: Long delay required to prepare system
Recovery: See 0x00010102. |
0x0001021D |
|
Description: Long delay required for mirror
synchronization
Recovery: See 0x00010102. |
0x0001021E |
|
Description: Unable to remove units from an IASP and a
User ASP at the same time
Recovery: Remove them from one ASP at a time. |
0x0001021F |
|
Description: Too many disk units are being removed.
Recovery: Remove one less disk unit. |
0x00010220 |
|
Description: Not a valid ASP number
Recovery: None. |
0x00010221 |
|
Description: There are no more available independent disk
pool numbers.
Recovery: The system uses unique numbers to identify each
independent disk pool. There were not enough of numbers available for the disk
pools you were creating. Possible recovery options are:
- Wait for independent disk pool resource recovery to run. Then retry the
request. Independent disk pool resource recovery runs automatically, but all
nodes in the cluster must be active.
- Reduce the number of disk pools being created and try the request
again.
- Delete an existing independent disk pool to free up an independent disk
pool number. Retry the request.
- Remove a node from the device domain group and try the request again.
|
0x00010222 |
|
Description: Internal system resource balancing did not
complete.
Recovery: Informational message - no action required. The
system attempted to balance independent disk pool resource numbers but was
unable to due to lack of numbers available. All nodes are present. |
0x00010223 |
|
Description: Internal system resource balancing did not
complete.
Recovery: The system attempted to balance independent disk
pool resource numbers but was unable to do so because of a lack of numbers
available. There are missing nodes. Start clustering and retry the
request. |
0x00010224 |
|
Description: Independent disk pool is missing.
Recovery: You requested an action on an independent disk pool
that is not currently owned by the system. The disk pool may be owned by
another system in the cluster, or may be corrupted. Check for missing disk
units and try to locate the independent disk pool. If the disk pool is not
owned by any other node, you can try to recover the configuration source. |
0x00010227 |
|
Description: Multiple nodes claim ownership of a disk
pool.
Recovery: All independent disk pools are required for this
action and were present, but the system detected disk pools owned by more than
one node. You may need to delete the disk pool. |
0x00010228 |
|
Description: Internal system resource recovery did not
complete.
Recovery: An internal attempt to recover independent disk
pool unit numbers failed, most likely because not all of the nodes in the ISG
were available. One or more nodes were either not active or were processing
other long running configuration operations. |
0x00010229 |
|
Description: IASP must be varied off before carrying out
this action
Recovery: Vary off IASP. |
0x0001022A |
|
Description: Could not write to configuration source.
Recovery: The requested operation failed. The system could
not write to the configuration source disk unit. Check the Product Activity Log
(PAL) for any errors. |
0x0001022B |
|
Description: Independent disk pool not valid
Recovery: The specified independent disk pool is not valid.
Either select a valid disk pool or create the disk pool. |
0x0001022C |
|
Description: Could not convert disk pool.
Recovery: Your attempt to change the type of disk pool to
primary or secondary could not be completed because the disk pool was not a
UDFS disk pool. |
0x0001022D |
|
Description: The selected disk pool is not a primary disk
pool
Recovery: You must select a primary disk pool when you create
a disk pool group. |
0x0001022E |
|
Description: Disk pools proposed for a disk pool group
cannot be in different cluster resource groups.
Recovery: All disk pools in a disk pool group must be in the
same recovery group. You selected disk pools that are already in another
cluster recovery group. You must select disk pools that are in the same
recovery group as the primary disk pool or that are not in any recovery
group. |
0x0001022F |
|
Description: The independent disk pool cannot be in active
recovery group when converting.
Recovery: You were attempting to make a disk pool either a
primary or secondary pool. The system detected that it was in an active
recovery group. You must end the recovery group and retry the operation. |
0x00010230 |
|
Description: Cluster version not valid
Recovery: You were attempting to make a disk pool either a
primary or secondary disk pool. The version level of the clustering product is
not at v5r2 or higher. You must upgrade the clustering product or remove the
disk pool from the recovery group. If you are using the Simple Cluster
Management utility, you can upgrade the version through the graphical user
interface. You can also use the Change Cluster Version (CHGCLUVER) command in
the character-based interface. |
0x00010231 |
|
Description: The independent disk pool is being blocked by
a cluster recovery group action.
Recovery: A cluster recovery group action is preventing the
disk pool from being available for the configuration change. Retry the
operation. |
0x00010233 |
|
Description:Primary disk pool not available.
Recovery: To delete a secondary disk pool, it needs to be
disassociated from its primary disk pool. The primary disk pool is not owned by
this node so the operation cannot be completed. Possible recovery options are:
- Find the missing primary disk pool and ensure it is owned by the same node
that owns the secondary disk pool.
- Attempt to recover the configuration source for the independent disk
pool.
- Delete the primary disk pool if it no longer exists. Then try to delete the
secondary disk pool again.
|
0x00010234 |
|
Description: The independent disk pool contains failed
disk units.
Recovery: The configuration data for the independent disk
pool was not updated on the disk units because of a disk unit failure. Fix the
failing disk units, and try again. |
0x00010235 |
|
Description: The IAsp is currently remotely mirrored.
Therefore, cannot create mirror copy for it.
Recovery: If mirror copy is missing, deconfigure remote
mirroring and try again. |
0x00010236 |
|
Description: The IAsp is currently owned by this node.
Therefore, cannot create mirror copy for it on this node.
Recovery: Choose different node to create the mirror
copy. |
0x00010237 |
|
Description: The independent disk pool is not owned by any
node.
|
0x00010238 |
|
Description: The independent disk pool is not owned by any
node that responded.
Recovery: The independent disk pool is not owned by any node
that responded. Therefore, cannot create mirror copy for it. Find the missing
original independent disk pool. The missing independent disk pool might be
owned by node that did not respond. Ensure clustering is active on all nodes in
device domain. |
0x00010239 |
|
Description: The independent disk pool is not in a
switchable hardware group.
Recovery: Add the independent disk pool to a switchable
hardware group. |
0x0001023A |
|
Description: The independent disk pool might not be in a
switchable hardware group.
Recovery: The independent disk pool might not be in a
switchable hardware group. Therefore, cannot create mirror copy for it. Ensure
clustering is active so can determine if independent disk pool in switchable
hardware group. |
0x0001023B |
|
Description: Unable to determine if switchable hardware
group is active.
Recovery: The system cannot create a mirror copy for the
independent disk pool in an active switchable hardware group. Make sure that
clustering is active and try the operation again. |
0x0000023C |
|
Description: The switchable hardware group containing the
independent disk pool does not have site specified.
Recovery: Add site name for all nodes in the switchable
hardware group recovery domain. |
0x0001023D |
|
Description: The node creating the mirror copy is at the
same site as the node that owns the original independent disk pool.
Recovery: The system cannot create a mirror copy of the
independent disk pool on a node that is at the same site as the node that owns
the original independent disk pool. Choose a different node on which to create
the mirror copy, or change the site name for one of nodes. |
0x0001023E |
|
Description: The Dasd selected for new mirror copy do not
provide capacity greater than or equal to the original independent disk pool
capacity.
Recovery: . Select more or larger Dasd for the new mirror
copy, or reduce capacity of original independent disk pool. |
0x0001023F |
|
Description: The node previously found as the owner of the
original independent disk pool is no longer communicating with the node
creating the mirror copy.
Recovery: The system cannot create a mirror copy for the
independent disk pool when it is unable to communicate with the node that owns
the original independent disk pool. Make sure that clustering is active on both
the source node and the target node. |
0x00010240 |
|
Description: Duplicate copies of the independent disk pool
exist on more than one node.
Recovery: Eliminate the extra copy of the independent disk
pool. |
0x00010241 |
|
Description: The specified independent disk pool is not
configured for geographic mirroring.
Recovery: The requested operation could not be completed
because the specified independent disk pool is not configured for geographic
mirroring. |
0x00010242 |
|
Description: The specified independent disk pool is not
the production copy.
Recovery: This action must be completed from the node that
owns the production copy of the independent disk pool. |
0x00010243 |
|
Description: The specified independent disk pool is not
the mirror copy or detached mirror copy.
Recovery: This action can only be completed on the mirror
copy or detached mirror copy.
If the problem persists, contact your technical support provider.
|
0x00010244 |
|
Description: An unexpected error occurred.
Recovery: Make sure that clustering is active. If necessary,
start clustering (STRCLUNOD). Try the request again.
If the problem persists, contact your technical support provider.
|
0x00010245 |
|
Description: The node previously found as owner of the
mirror copy is no longer communicating with this node.
Recovery: Make sure that clustering is active on both the
source and target node. Try the operation again.
If the problem persists, contact your technical support provider.
|
0x00010246 |
|
Description: At least one of the independent disk pools is
owned by more than one node.
Recovery: Restart your servers so that each independent disk
pool involved in this action is owned by only one node. Try the operation
again.
If the problem persists, contact your technical support provider.
|
0x00010247 |
|
Description: This system does not own the independent disk
pool.
Recovery: This action must be performed from the node
that owns the production copy. |
0x00010249 |
|
Description: This action is not valid in the current
geographic mirroring state.
Recovery: Change the geographic mirroring state to be allowed
to perform this operation. |
0x0001024A |
|
Description: The node that the mirror copy resides on is
not known.
Recovery: Restart the server and try the operation again.
If the problem persists, contact your technical support provider.
|
0x0001024B |
|
Description: The server does not have enough free storage
to create an object.
Recovery: The machine pool is not large enough to provide the
storage required by this request.
Increase the size of the machine pool by using the Change Shared Storage
Pool (CHGSHRPOOL) command through the system command line in the
character-based interface. Try the request again.
|
0x0001024C |
|
Description: This system does not own the independent disk
pool.
Recovery: This action must be performed from the node that
owns the independent disk pool. |
0x0001024D |
|
Description: This system does not own the independent disk
pool.
Recovery: This action must be performed from the node that
owns the independent disk pool. |
0x0001024E |
|
Description: This node does not own the specified
independent disk pool.
Recovery: Restart your server to assign ownership for the
independent disk pool. Try the operation again.
If the problem persists, contact your technical support provider.
|
0x0001024F |
|
Description: The server could not write to a disk unit in
the independent disk pool.
Recovery: Fix the disk unit error and try the operation
again. |
0x00010250 |
|
Description: Unable to delete the geographically mirrored
independent disk pool.
Recovery: A different node owns the production copy.
Deconfigure geographic mirroring for the independent disk pool from the node
that owns the production copy. Try the operation again. |
0x00010251 |
|
Description: Unable to delete the geographically mirrored
independent disk pool.
Recovery:
Deconfigure geographic mirroring
for the independent disk pool from this
node, the owner of the production copy. Try the operation again. |
0x00010252 |
|
Description: Unable to delete the geographically mirrored
independent disk pool.
Recovery: Deconfigure geographic mirroring
for the independent disk pool from the node that owns the production copy. Try
the operation again. |
0x00010253 |
|
Description: The mirror copy is already detached.
Recovery: Reattach the mirror copy if you want this operation
to perform correctly. |
0x00010254 |
|
Description: The server is unable to suspend geographic
mirroring because it detected a failed disk unit on the production copy.
Recovery: Check the Product Activity Log (PAL), and take any
required action. Replace disk units as necessary. Try the operation again. |
0x00010255 |
|
Description: Unable to detach mirror copy because mirror
copy data state is not synchronized.
Recovery: Synchronize the mirror copy and try the operation
again. |
0x00010256 |
|
Description: Operation not valid when geographically
mirrored disk pool is available.
Recovery: Make the disk pool unavailable and try the
operation again. |
0x00010257 |
|
Description: Operation failed because the system could not
find the mirror copy.
Recovery: The system could not find the mirror copy, even
though all nodes in the device domain are present. Contact your technical
support provider. |
0x00010258 |
|
Description: Operation failed because the system could not
find the mirror copy.
Recovery:
Not all the nodes in the device domain responded. Make sure that clustering
is active. If necessary, start clustering (STRCLUNOD). Try the request
again.
If the problem persists, contact your technical support provider.
|
0x00010259 |
|
Description: Not all of the disk pools in the disk pool
group are geographically mirrored
Recovery: If one disk pool in a disk pool group is
geographically mirrored, all of the disk pools in the disk pool group must be
geographically mirrored. Take one of the following actions:
- Configure geographic mirroring for the disk pools which are not
geographically mirrored.
- Deconfigure geographic mirroring for the disk pools that are geographically
mirrored.
|
0x0001025A |
|
Description: The server did not accept the warning on the
mirror copy.
Recovery: Make sure that clustering is active. If necessary,
start clustering (STRCLUNOD). Try the request again.
If the problem persists, contact your technical support provider.
|
0x0001025B |
|
Description: The server did not accept the warning on the
production copy.
Recovery: Make sure that clustering is active. If necessary,
start clustering (STRCLUNOD). Try the request again.
If the problem persists, contact your technical support provider.
|
0x0001025C |
|
Description: The system cannot resume geographic mirroring
for a detached mirror copy or reattach a mirror copy that is not detached.
Cannot complete requested operation.
Recovery:
You cannot reattach a mirror copy if it is not detached. You may want to
resume geographic mirroring instead.
You may also receive this message if the production copy and mirror copy are
inconsistent or inconsistent with the Cluster Resource Group. To recover,
perform a CHGCRG for the recovery domain, (even if recovery domain is correct)
indicating the primary node. Otherwise, check for locally mirrored disk units
that may exist on two systems, Enterprise Storage Server FlashCopy, or back
level independent disk pool copies. Eliminate duplication and try the request
again.
If the problem persists, contact your technical support provider.
|
0x0001025D |
|
Description: Cluster resource group must be active for
requested operation.
Recovery: Start the cluster resource group and try the
operation again. |
0x0001025E |
|
Description:Disk pools selected for operation have their
mirror copies owned by different target nodes.
Recovery: Use Hardware Service Manager to change tower
ownership to the correct node. Or, change logical partition configuration to
switch the IOP to the correct node. |
0x0001025F |
|
Description: An unexpected error occurred. Try the request
again.
Recovery: If the problem persists, make the disk pool
unavailable and try the request again. If the problem still persists, restart
the target node and try the request again.
If the error continues, contact your technical support provider.
|
0x00010260 |
|
Description: An unexpected error occurred. Try the request
again.
Recovery: If the problem persists, make the disk pool
unavailable and try the request again. If the problem still persists, restart
the target node and try the request again.
If the error continues, contact your technical support provider.
|
0x00010261 |
|
Description: System failed to process mirror copy from
prior make available operation.
Recovery: Make sure clustering is active. If necessary, start
clustering (STRCLUNOD). Try the request again. If the problem persists, make
the disk pool unavailable and try the request again. If the problem still
persists, restart the target node and try the request again.
If the error continues, contact your technical support provider.
|
0x00010262 |
|
Description: The configuration source disk unit in the
independent disk pool does not contain the most recent data for the disk
pool.
Recovery: Contact your technical support provider. |
0x00010263 |
|
Description: Server failed to access mirror copy after
accepting warnings.
Recovery: Verify that clustering is active to the mirror copy
node. Verify that the mirror copy is operational. Try the request again.
If the error continues, contact your technical support provider.
|
0x00010264 |
|
Description: Cannot link a detached link pool.
Recovery: Reattach the disk pool and try the link operation again.
|
0x00010267 |
|
Description: Cannot suspend geographic mirroring with tracking
for the independent disk pool because untracked changes have been made.
Recovery: If need to suspend geographic mirroring to turn off auto
resume, then suspend geographic mirroring without tracking. Otherwise, do nothing because
geographic mirroring is already suspended without tracking. |
0x00010268 |
|
Description: Cannot suspend geographic mirroring with tracking
for the independent disk pool because no tracking resources are available.
Recovery: Suspend geographic mirroring without tracking, or if the
independent disk pool is offline, increase tracking resources and then try the suspend
operation again. |
0x00010269 |
|
Description: Cannot suspend geographic mirroring with tracking for
the independent disk pool for an unknown reason.
Recovery: Suspend geographic mirroring without tracking or contact your
technical support provider. |
0x0001026A |
|
Description: Cannot perform requested function because another node
owns a copy with the same role.
Recovery: Do a CHGCRG of the recovery domain order to resolve the duplicate
roles. |
0x0001026B |
|
Description: Cannot suspend geographic mirroring with tracking
for the independent disk pool because the mirror copy is detached.
Recovery: Suspend geographic mirroring without tracking. |
0x0001026C |
|
Description: Specified tracking resource is too large.
Recovery: Specify a tracking resource capacity that is no more
than 1% of the disk pool's capacity. Reduce tracking resources and try again. |
0x0001026D |
|
Description: The configuration source disk unit selected for
the new independent disk pool has an I/O error.
Recovery: Use the reference codes to determine the cause of the
failure. If you cannot fix the failing disk unit, select another disk unit for
the new independent disk pool. |
0x0001026E |
|
Description: Disk unit I/O failure.
Recovery: None. |
0x00010301 |
|
Description: Disk unit is wrong size to replace
Recovery: None. |
0x00010303 |
|
Description: Disk configuration change not allowed for the
device
Recovery: None. |
0x00010304 |
|
Description: Selected unit did not have read error
Recovery: None. |
0x00010305 |
|
Description: Unit not at a valid load source location
Recovery: Your request could not be completed successfully.
The probable cause is that the unit selected as the replacement unit for the
load source is not at a valid location. To recover from the problem, the
replacement unit must be moved to a valid location. This is an operation that
should only be performed by a trained service person. If you are not a trained
service person, call your service representative. |
0x00010306 |
|
Description: It is not valid to select a missing unit
Recovery: None. |
0x00010307 |
|
Description: Load source is unknown or does not contain
latest code
Recovery: None. |
0x00010309 |
|
Description: Status of other sub-unit is not valid
Recovery: You can not suspend mirrored protection on the
selected sub-units for one of the following reasons: a) Other sub-unit of the
mirrored pair does not have the status of active b) You selected both sub-units
of the mirrored pair to be suspended. |
0x0001030A |
|
Description: Other sub-unit is missing
Recovery: The function requested can not be performed because
the other sub-unit of the mirrored pair is missing. |
0x0001030B |
|
Description: Selected unit is mirror protected
Recovery: The system can not complete the requested device
parity protection function because some of the disk units in the storage
subsystems are currently in ASPs that are mirror protected. In order to
complete this device parity protection function on these disk units you must
first remove them from the ASP or stop mirrored protection on the ASPs that
contain them. |
0x0001030C |
|
Description: Selected unit requires initialization
Recovery: The disk units are not in the correct format to
utilize the advanced features of the storage IOP. These units must be removed
from the configuration and initialized by adding them back to the ASP. |
0x0001030D |
|
Description: Selected unit is in a mirrored ASP
Recovery: None. |
0x00010310 |
|
Description: Cannot replace active unit past DST
Recovery: None. |
0x00010311 |
|
Description: Selected failed disk unit causes data
loss
Recovery: The system can not complete the requested device
parity protection function because some disk units have failed and the
other disk units in their parity sets are sustaining their function. Stopping
device parity protection on these disk units will result in data loss. Remove
these disk units from the ASPs and try the function again. |
0x00010312 |
|
Description: Missing device parity unit requires cleared
ASP
Recovery: There are missing device parity protected units.
The system can not stop device parity protection on the selected parity sets
that are not operational because that might cause data loss. Either make the
parity sets operational or clear all ASPs that contain missing disk units with
the Delete ASP Data function. |
0x00010314 |
|
Description: Wrong device parity status for replace
Recovery: The non-configured unit does not have the same
device parity protection status as the missing unit and is not valid for the
assign missing unit function. |
0x00010315 |
|
Description: Device parity protected unit required
Recovery: See 0x00010315. |
0x00010316 |
|
Description: Disk unit does not have system support
Recovery: None. |
0x00010317 |
|
Description: Cannot replace mirrored unit with device
parity unit
Recovery: A device parity unit is not allowed to be used to
replace a disk unit that is a subunit of a mirrored pair. |
0x00010318 |
|
Description: Selected unit does not have a parity
mismatch
Recovery: None. |
0x00010320 |
|
Description: Mirrored load source mate not attached to
MFIOP
Recovery: Move load source mate to MFIOP. |
0x00010322 |
|
Description: Load source size too small, call for
service
Recovery: Call Service. |
0x00010324 |
|
Description: Could not allocate larger free space map
Recovery: None. |
0x00010325 |
|
Description: Only one mirrored unit is eligible for
compression
Recovery: Only one subunit of a mirrored pair is eligible for
start compression. Check to see if the other subunit of the mirrored pair is
attached to a compression capable IOP. |
0x00010326 |
|
Description: I/O operation not attempted
Recovery: The I/O operation was not attempted. The disk unit
is no longer a candidate for the requested operation. |
0x00010327 |
|
Description: I/O operation failed
Recovery: The I/O operation was not successful. Retry the
operation. |
0x00010328 |
|
Description: I/O operation failed
Recovery: See 0x00010328. |
0x00010329 |
|
Description: Abnormal IOP reset
Recovery: IOP got reset at the end of IOP operation. If you
are attempting to perform start compression operation, you need to perform
start compression recovery. If you are not attempting a start compression
operation, determine whether the operation completed successfully. If it did
not complete successfully, retry the operation. |
0x0001032A |
|
Description: Cannot perform the operation
Recovery: The requested compression operation cannot be
performed. |
0x0001032B |
|
Description: Data not preserved
Recovery: The data on disk units could not be preserved
during the "Stop Compression" operation. |
0x0001032C |
|
Description: Mismatched compression state
Recovery: The compression state of the selected
non-configured disk unit does not match the compression state of the configured
disk unit. If the configured disk unit is compressed, the non-configured disk
unit which you select must also be compressed. If the configured disk unit is
non-compressed, the non-configured disk unit which you select must also be
non-compressed. |
0x0001032E |
|
Description: Mirrored disk unit is suspended
Recovery: The following disk units that were active at the
beginning of the configuration change are now suspended. If the compression
state of the listed disk unit, is different from the active disk unit, perform
"Replace configured unit", otherwise perform "Resume mirrored protection"
operation. After you perform the "Resume mirrored protection" operation, in
some situations you may be required to perform start compression recovery,
before the system is IPLed past DST. |
0x0001032F |
|
Description: I/O operation failed
Recovery: The command that was sent to the following disk
units did not complete because the amount of data moved was not sufficient. Try
the function again. |
0x00010330 |
|
Description: Compressed disk unit not allowed in system
ASP
Recovery: Uncompress disk unit first, the retry the add. |
0x00010343 |
|
Description: There are no more IASP Disk Unit Numbers
Recovery: Remove units or delete an IASP. |
0x00010345 |
|
Description: Cannot determine if there are any additional
IASP Disk Unit Numbers
Recovery: Fix cluster communication and retry. |
0x00010346 |
|
Description: Another node has a configuration change in
progress.
Recovery: Retry AFTER other node is finished. |
0x00010347 |
|
Description: The system has some lost IASP Disk Unit
Numbers
Recovery: Wait for the system to attempt recovery, then
retry. |
0x00010348 |
|
Description: Load source disk unit could not be found.
Recovery: The loud source disk unit on the original system
could not be located. The migration cannot continue until the system can
communicate with that specific disk unit. Check to ensure the disk unit is one
of the units still attached to the system. Check to see if there are errors in
the Product Activity Log (PAL) for that unit. |
0x00010349 |
|
Description: Could not obtain enough disk unit numbers
Recovery: You were adding disk units to an independent disk
pool. The system uses unique numbers to identify each disk unit and there are
not enough of them available for all the disk units you were adding. Possible
recovery options are:
- Wait for independent disk pool resource recovery to run. Then retry the
request. Independent disk pool resource recovery runs automatically, but all
nodes in the cluster must be active.
- Reduce the number of units being added.
- Remove unnecessary disk units from other independent disk pools.
|
0x0001034B |
|
Description: Could not balance the disk unit numbers
across the nodes
Recovery: The system has initiated a recovery action to
balance disk unit numbers for independent disk pools. The recovery action
failed. All nodes are active. Respond to error messages for missing nodes or
missing independent disk pools, then retry the operation. If the operation
still fails, you must either remove some disk units in order to add these disk
units or add fewer disk units. |
0x0001034C |
|
Description: Could not balance the disk unit numbers
across the nodes
Recovery: The system has initiated a recovery action to
balance disk unit numbers for independent disk pools. The recovery action
failed. There were nodes that did not report. Respond to error messages for
missing nodes or missing independent disk pools. Make sure that clustering is
active for all nodes. Then retry the operation. If the operation still fails,
you must either remove some disk units in order to add these disk units or add
fewer disk units. |
0x0001034D |
|
Description: Cannot reclaim cache storage
Recovery: The system is in a state that will not allow the
cache storage to be reclaimed. You can restart to Dedicated Service Tools (DST)
and perform the reclaim storage operation. |
0x0001034E |
|
Description: There is a non-parity disk unit in the
mismatched parity set
Recovery: Bring the system down to DST and retry. |
0x00010350 |
|
Description: The IASP containing one of the mismatched
disk units is varied on
Recovery: Vary off the IASP and retry. |
0x00010351 |
|
Description: Operation not completed successfully.
Recovery: Retry. |
0x00010353 |
|
Description: The selected disk device does not support the
function to retrieve the device logs.
Recovery: Contact your technical support provider. |
0x00010354 |
|
Description: Cannot use disk unit for non-switchable
ASP
Recovery: Other disk units under parent entity are configured
in a switchable IASP. Make conflict switchable IASP non-switchable by removing
it from the CRG. Or, make this non-switchable ASP switchable by putting in the
same CRG. |
0x00010361 |
|
Description: Cannot use disk unit for switchable ASP
Recovery: Other disk units under parent entity are configured
in a non-switchable IASP. Make conflict switchable IASP non-switchable by
removing it from the CRG. Or, make this non-switchable ASP switchable by
putting in the same CRG. |
0x00010362 |
|
Description: Cannot use disk unit for switchable ASP
Recovery: Some nodes in CRG's recovery domain cannot be
accessed. Take the nodes that cannot be accessed out of CRG's recovery domain.
Or, make this switchable ASP non-switchable by removing it from the CRG. Or,
change the hardware topology so nodes can be accessed. |
0x00010363 |
|
Description: Cannot use disk unit for switchable ASP
Recovery: Other disk units under the parent entity are
configured in other IASP(s) which are in a different CRG. Put this IASP and
other IASP(s) in the same CRG. |
0x00010364 |
|
Description: Cannot use disk unit for switchable ASP
Recovery: Disk units are non-switchable. Make this switchable
IASP non-switchable by removing it from the CRG. Or, make the disk units
switchable by putting them in a frame that has no non-switchable disk
units. |
0x00010365 |
|
Description: Invalid disk unit for switchable disk pool
because switchable entity is in different power domain than disk units already
configured in the specified disk pool
Recovery: The specified disk pool is switchable. This disk
unit resides in a switchable entity, but the switchable entity is in a
different SPCN power domain than the disk units already configured in the
specified disk pool. In order to use this disk unit for the specified disk
pool, you can do the following:
- Change the SPCN cabling so that the switchable frame is in the same power
domain as the server owning the disk units that are already configured in the
specified disk pool.
|
0x00010366 |
|
Description: Invalid disk unit for nonswitchable disk pool
because switchable entity blocks access to switchable disk pool
Recovery: The specified disk pool is nonswitchable. This disk
unit resides in a switchable frame that contains only nonconfigured disk units.
However, this frame needs to be switched in order to switch a frame that
contains disk units that are configured in a switchable disk pool.
In order to use this disk unit for the specified disk pool, you can do one
of the following:
- Change the switchable disk pool that has disk units configured in the other
frame to nonswitchable by removing it from its cluster resource group.
- If the specified disk pool is an independent disk pool, make the
independent disk pool switchable by adding it to the same cluster resource
group as the switchable disk pool(s) with disk units in the other frame.
- If the switchable disk pool(s) have sufficient disk units attached to other
switchable entities to store the data, then remove the disk units contained in
this disk unit's switchable entity from the switchable disk pool(s).
- Change the order of the frames so that the frame containing this disk unit
is adjacent to this node. Then make the frame private.
|
0x00010367 |
|
Description: Invalid disk unit for switchable disk pool
because switchable entity is in different power domain than disk units already
configured in the specified disk pool
Recovery: The specified disk pool is switchable. This disk
unit resides in a switchable entity, but the switchable entity is in a
different SPCN power domain than the disk units already configured in the
specified disk pool. In order to use this disk unit for the specified disk
pool, you can do the following:
- Change the SPCN cabling so that the switchable frame is in the same power
domain as the server owning the disk units that are already configured in the
specified disk pool.
|
0x00010368 |
|
Description: Invalid disk unit for switchable disk pool
because Virtual OptiConnect is not configured
Recovery: The specified independent disk pool is switchable.
This disk unit resides in a switchable entity, but Virtual OptiConnect has not
been configured. In order to use this disk unit for the specified disk pool,
you can do one of the following:
- Change the specified independent disk to be nonswitchable by removing it
from the cluster resource group.
- Configure Virtual OptiConnect.
|
0x00010369 |
|
Description: Invalid disk unit for switchable disk pool
because disk unit is nonswitchable, but could be made switchable
Recovery: The specified disk pool is switchable, but this
disk unit resides in a nonswitchable entity. In order to use this disk unit for
the specified disk pool, you can do one of the following:
- If the disk unit resides in a frame, make it switchable by changing the
frame mode from private to switchable.
- If the disk unit resides in a logical partition, make the disk unit
switchable by changing the bus containing the IOP to which this disk unit is
attached from dedicated to shared. Note that all IOPs on that bus become
switchable.
|
0x00010370 |
|
Description: A disk unit is missing from the configuration
of the mirror copy.
Recovery: Find or fix the missing disk unit in the mirror
copy. Check the Product Activity Log (PAL) on target node. Reclaim IOP cache
storage. |
0x00010380 |
|
Description: A disk unit in the mirror copy is partially
restored.
Recovery: Try to restore the disk unit data again. If you get
this error again, you may have to clear the disk pool. |
0x00010381 |
|
Description: The mirror copy unit has no available
alternate sectors.
Recovery: Free up alternate sectors by performing one of the
following actions:
- Remove disk unit
- Replace disk unit
- Do a save/restore of the disk unit
- Perform a PUMP copy of the disk unit
|
0x00010382 |
|
Description: Incorrect device parity protection for disk
unit in the mirror copy.
Recovery: To correct the device parity problem, try one of
the following actions on the mirror copy:
- Start SST or DST in the character-based interface. Select the following:
Work with Disk Units --> Work with Disk Unit Recovery --> Correct
Device Parity Protection Mismatch
- start device parity protection
- Include a disk unit in a parity set
- stop mirroring
|
0x00010383 |
|
Description: Compression failed to start on a disk unit in
the mirror copy.
Recovery: Compression operation failed when trying to prepare
to compress data.
To recover from start compression failure, start SST or DST in the
character-based interface. Select the following:
- Work with Disk Units
- Work with disk unit recovery
- Recover from start compression failure
|
0x00010384 |
|
Description: The configuration source disk unit is missing
for the mirror copy.
Recovery: Attempt to locate the missing disk unit.
See Recover an independent disk pool in the online help for step-by-step
instructions to recover the configuration source.
|
0x00010385 |
|
Description: The system rebuilt the mirror copy of the
independent disk pool with the correct configuration source
Recovery: Try the operation again. |
0x00010386 |
|
Description: A disk unit in the mirror copy is missing a
connection.
Recovery: Check the Product Activity Log (PAL) on the mirror
copy node. Take action and try the operation again.
If the problem persists, contact your technical support provider.
|
0x00010387 |
|
Description: A disk unit in the mirror copy has an
error.
Recovery: Check the Product Activity Log (PAL) on the mirror
copy node. Take action and try the operation again. |
0x00010388 |
|
Description: Device parity command failed - configuration
change
Recovery: After the selections were made, the physical
configuration of the disk units has changed in the parity sets listed below.
Retry the function. |
0x00010401 |
|
Description: Device parity command error
Recovery: The command to these device parity sets was not
successful. Retry the function or call for service. |
0x00010402 |
|
Description: Device parity command error
Recovery: See 0x00010402. |
0x00010403 |
|
Description: Command did not complete within time
limit
Recovery: The command that was sent to the following device
parity sets did not complete within the time limit for that command. Try the
device parity function again or call for service. |
0x00010404 |
|
Description: Device parity operation canceled by user
Recovery: The operation on the following parity sets was
canceled by the user. The required manual intervention was not completed. |
0x00010405 |
|
Description: Device parity function completed
abnormally
Recovery: The device parity protection function requested has
ended abnormally because a reset was issued to the IOP during the device parity
operation. The requested operation may have completed successfully. Verify the
configuration to see if the device parity protection changes that you requested
have been applied to the system. If not, retry the operation. |
0x00010408 |
|
Description: Device parity command failed
Recovery: The command to these device parity sets was not
successful because the amount of data moved was not sufficient. Retry the
function. |
0x00010409 |
|
Description: Disk unit(s) are ineligible for the requested
operation.
Recovery: This operation would violate a parity rule. |
0x0001040A |
|
Description: MFIOP is only supports disk units in 520-byte
format
Recovery: None. |
0x00010503 |
|
Description: Remote load source mirroring is already
enabled
Recovery: The remote load source mirroring function is
already enabled. |
0x00011106 |
|
Description: Remote load source mirroring is already
disabled
Recovery: The remote load source mirroring function is
already disabled. |
0x00011107 |
|
Description: Disk Unit Configuration will not be valid
Recovery: The disk unit configuration will not be valid for
this system. You will not be allowed to continue restarting the server until
you remove some of the disk storage. |
0x00011109 |
|
Description: IPL will occur on primary logical
partition
Recovery: The action you requested will require an IPL on the
primary logical partition when the function has completed. All processing on
secondary partitions will be ended during this IPL. |
0x0001110A |
|
Description: Creating the first independent disk pool in a
device domain group
Recovery: It is possible that you will not be able to add any
more nodes to the device domain group after the independent disk pool has been
created. Add all desired nodes to the device domain group before creating any
independent disk pools. |
0x0001110C |
|
Description: Reclaim IOP cache storage recommended.
Recovery: Check Product Activity Log (PAL) on the target
node. Reclaim IOP cache storage on target node if any action is needed. |
0x0001110D |
|
Description: Unexpected warning from mirror copy node.
Recovery: Check Product Activity Log (PAL) on target node.
Take action, and try the operation again.
If the problem persists, contact your technical support provider.
|
0x0001110E |
|
Description: ASPs will be cleared
Recovery: The indicated ASPs will be cleared to continue. The
probable cause is that the indicated ASPs have missing units or the indicated
user ASPs are overflowed into the system ASP and the system ASP will be cleared
or the load source has been rebuilt. |
0x00011201 |
|
Description: Cannot balance the data on the disk pool.
Recovery: If you are adding disk units to a basic disk pool,
the data on the disk pool will be balanced when your system is started past
Storage Management Recovery. If you are adding disk units to an independent
disk pool, the data will be balanced when you make the disk pool
available. |
0x00011202 |
|
Description: The IASP name is possibly a duplicate.
Recovery: Confirm that IASP name is unique in the group. |
0x00011203 |
|
Description: Should not attempt configuration change.
Recovery: Another node might be using the selected IASP. The
system is unable to communicate with another node in the CRG. |
0x00011205 |
|
Description: This request will cause the system to be
below threshold.
Recovery: The system is low on disk pool numbers. This
message is informational only. |
0x00011206 |
|
Description: IASP configuration may not be valid
Recovery: Accepting it may not give the correct
configuration. If you reject the warning, you can remove the IASP and try
to recreate it. |
0x00011207 |
|
Description: The secondary and primary disk pools must be
in the same cluster resource group.
Recovery: The system cannot determine if the primary and
secondary disk pools are in the same cluster resource group (CRG). It is
recommended that you start clustering before you continue. |
0x00011208 |
|
Description: The cluster resource group may be active.
Recovery: The system cannot determine if the cluster resource
group is active because clustering is not started. Ensure that the cluster
resource group is not active. It is recommended that you start clustering
before you continue. |
0x00011209 |
|
Description: The cluster resource group version may be
wrong.
Recovery: The system cannot determine if the primary disk
pool is in a cluster resource group (CRG) as clustering is not started. The CRG
may not be the correct version. It is recommended that you start clustering
before you continue. |
0x0001120A |
|
Description: Could not find the node that owns the mirror
copy.
Recovery: Could not find the node that owns the mirror copy,
even though all nodes in the device domain are present.
If the problem persists, contact your technical support provider.
|
0x0001120B |
|
Description: Could not find the node that owns the mirror
copy.
Recovery: Not all the nodes in the device domain responded.
Make sure that clustering is active. If necessary, start clustering
(STRCLUNOD). Try the request again.
If the problem persists, contact your technical support provider.
|
0x0001120C |
|
Description: Make sure to select all of the independent
disk pools that belong to the disk pool group.
Recovery: The primary disk pool is missing, so the disk pool
group is unknown. |
0x0001120D |
|
Description: The primary disk pool is missing, so the disk
pool group is unknown.
Recovery:Locate the missing primary disk pool and try the
operation again.
If the problem persists, contact your technical support provider.
|
0x0001120E |
|
Description: Could not find the node that owns the
production copy.
Recovery: Make sure that clustering is active. If necessary,
start clustering (STRCLUNOD). Try the request again.
If the problem persists, contact your technical support provider.
|
0x0001120F |
|
Description:The disk unit is already mirrored.
Recovery: Check for locally mirrored disk units that may
exist on two systems, Enterprise Storage Server FlashCopy, or back level
independent disk pool copies. See the Product Activity Log (PAL) on the mirror
copy node for more information. Eliminate duplication and try the request
again.
If the problem persists, contact your technical support provider.
|
0x00011211 |
|
Description: Unexpected warning from mirror copy.
Recovery: Unexpected warning from mirror copy. Check the
Product Activity Log (PAL) on target node and take any required action. Try the
operation again.
If the problem persists, contact your technical support provider.
|
0x00011212 |
|
Description: The capacity of the disk units that have been
selected for the new mirror copy is less than capacity of the original independent
disk pool and greater than 95% of the capacity of the original independent disk pool.
Recovery: Either proceed with the lower capacity or select more
disk units or disk units with larger capacities for the new mirror copy, or reduce
the capacity of the original independent disk pool. |
0x00011213 |
|
Description: Unable to add non-configured disk units because
the level of mirror protection is lower than the current disk pool.
Recovery: Adding non-configured disk units to a mirrored disk
pool that has a lower level of mirror protection than the current disk pool will
result in a lower level of protection. To correct this situation do one or more of
the following:
- Move hardware.
- Replace the disk unit with a disk unit in a different frame/unit.
- Replace the disk unit with an IOP that has the same level of hardware protection.
|
0x00011214 |
|
Description: The specified tracking resource is insufficient.
If you continue with this operation, tracking will end when the independent disk pool
is made available and a full synchronization will be required.
Recovery: Specify more tracking resources or accept full synchronization.
|
0x00011215 |
|
Description: The specified tracking resource is only slightly greater
to that which is currently being used. If you continue with this operation, tracking might
be ended when the independent disk pool is made available and a full synchronization might
be required.
Recovery: Specify more tracking resources or accept full synchronization.
|
0x00011216 |
|
Description: Cannot determine if unit possibly
configured
Recovery: These non-configured units appear to be configured
units of some other disk configuration and may contain valid data. This option
will clear the data from these units and destroy the other disk
configuration. |
0x00011301 |
|
Description: Some pages on disk unit were not readable
Recovery: Some pages on the disk unit were not able to be
read while analyzing the disk unit surface. The system might have damaged
objects following disk recovery procedures of the unreadable pages on the disk
unit. |
0x00011302 |
|
Description: Some errors were found during the scan.
Recovery: Some of the pages were not able to be read during
the scan disk function. The system might have damaged objects. Follow disk unit
recovery procedures to recover the unreadable pages on the disk unit. |
0x00011303 |
|
Description: Unit possibly configured for IMPI
Recovery: None. |
0x00011305 |
|
Description: Lower level of mirrored protection
Recovery: The requested operation will result in a lower
level of mirrored protection. |
0x00011306 |
|
Description: Cannot determine if unit possibly
configured
Recovery: See 0x00011301. |
0x00011307 |
|
Description: Unprotected disk unit in mirrored ASP
Recovery: Disk units will become unprotected as a result of
running the "Correct device parity mismatch" operation. These units were
originally device parity protected. |
0x00011308 |
|
Description: Selected unit is in a mirrored ASP
Recovery: The system can not complete the requested device
parity protection function because some of the disk units in the storage
subsystems are currently in ASPs that are mirror protected. In order to
complete this device parity protection function on these disk units you must
first remove them from the ASP or stop mirrored protection on the ASPs that
contain them. |
0x0001130A |
|
Description: Install licensed internal code after function
completes
Recovery: You selected to stop device parity protection on
the parity set that contained the load source disk unit which is failed. If
possible, repair the failed load source disk unit and perform "Rebuild disk
unit data" function. If you continue with this operation, the system will fail
and you will be required reinstall Licensed Internal Code and restore your
data. |
0x0001130C |
|
Description: Only one subunit of mirrored pair
selected
Recovery: Only one disk unit of a mirrored pair was selected
for the operation. The system has selected the mate for you. |
0x0001130D |
|
Description: Disk unit compression is stopped
Recovery: The non-configured disk unit is being initialized.
This stops compression on the disk unit. |
0x0001130F |
|
Description: Suspended disk unit will become missing
Recovery: The disk units selected for a compression change,
are not active. The disk units will become missing once the compression state
changes. A replace operation will be necessary. |
0x00011310 |
|
Description: Missing disk unit may become permanently
missing
Recovery: The disk units selected for a compression change
are missing. The disk units may become permanently missing once the compression
state changes. A replace operation will be necessary. If the missing disk units
are not attached to a compression IOP, a replace operation will not be
successful. |
0x00011311 |
|
Description: Storage pool has been cleared.
Recovery: The storage pool you were trying to save has been
cleared. There is no data on the disk units in the pool. |
0x00011321 |
|
Description: A disk unit with multiple connections is
missing a connection. Data may be overwritten if you continue with this
operation.
Recovery: A disk unit with multiple connections is missing a
connection. If a non-configured disk unit in this operation is actually the
missing connection, data will be overwritten if you continue.
Use the ESS Specialist to check the connections that are configured for the
disk unit. Verify that the number of paths enlisting for the disk unit are
correct. If a path has been established via the ESS Specialist, but is not
enlisting, do not proceed with this operation.
If the problem persists, contact your technical support provider.
|
0x00011326 |
|
Description: System will be below threshold after
operation
Recovery: The system is low on disk unit numbers. This
message is informational only. |
0x00011328 |
|
Description: Allowable disk unit for nonswitchable disk
pool, but switchable entity has unknown independent disk pool
Recovery: The specified disk pool is nonswitchable. This disk
unit resides in a switchable entity that contains disk units that are
configured in an independent disk pool. Also, this node is in a device domain,
so the independent disk pool might be switchable. Clustering is not active, so
it cannot be determined if the independent disk pool is switchable. You should
attempt to start clustering on this node to determine if the other independent
disk pool is switchable. In some cases you may be unable to start clustering.
For example, the server may need disk units to restart to i5/OS, and this disk
unit is the only nonconfigured disk unit. In this case, you can add this disk
unit to the specified disk pool. Adding this disk unit may break the
switchability of the independent disk pool that has disk units configured in
the same switchable frame. |
0x00011329 |
|
Description: Allowable disk unit for switchable disk pool,
but switchable entity has unknown independent disk pool
Recovery: The specified disk pool is switchable. This disk
unit resides in a switchable entity that contains disk units configured to an
unknown independent disk pool. Also, this node is in a device domain, so the
unknown independent disk pool might be switchable. Clustering is not active, so
it cannot be determined if the unknown independent disk pool conflicts with the
specified independent disk pool. For example, if the unknown independent disk
pool is switchable they may be in different cluster resource groups. You should
attempt to start clustering on this node to determine if the unknown
independent disk pool is switchable. If you are unable to start clustering, and
the server needs this disk unit to make the disk pool available, you can add
this disk unit to the specified disk pool. Adding this disk unit may break the
switchability of the specified disk pool or the unknown switchable disk pool
with disk units configured in the same switchable entity. |
0x0001132A |
|
Description: Allowable disk unit for switchable disk pool,
but cannot determine if all nodes in the cluster resource group can access the
disk unit
Recovery: The specified disk pool is switchable, but the
server cannot determine if all nodes in the cluster can access this disk unit
because clustering is not active on all nodes in the recovery domain of the
cluster resource group. You should start clustering to determine if each node
in the recovery domain can access this disk unit. You should not select this
disk unit to be added to the specified disk pool at this time, unless you have
a dire need to do so. For example, you cannot start clustering, and you need to
use this specific disk pool with this disk unit as the only nonconfigured disk
unit available to be added. Using this disk unit might break the switchability
of the specified disk pool. |
0x0001132B |
|
Description: Should not use disk unit because it cannot be
determined if the independent disk pool is switchable because clustering is not
active
Recovery: The specified disk pool is independent, but the
server cannot determine if it is switchable because clustering is not active.
This node is in a device domain, so the independent disk pool could be
switchable. You should start clustering to determine if the independent disk
pool is switchable. You should not select this disk unit to be added to the
specified independent disk pool at this time, unless you have a dire need to do
so. For example, you cannot start clustering, and you need to use this specific
disk pool with this disk unit as the only nonconfigured disk unit available to
be added. Using this disk unit might break the switchability of the specified
disk pool. |
0x0001132C |
|
Description: Allowable disk unit for switchable disk pool,
but disk unit may cross power domains.
Recovery: The specified disk pool is switchable, but the
server cannot determine if choosing this disk unit would cause the disk pool to
cross SPCN power domains. You should start clustering to determine if power
domains are crossed. You should not select this disk unit to be added to the
specified disk pool, unless you have a dire need to do so. For example, you
cannot start clustering, and you need to use this specific switchable disk pool
with this disk unit as the only nonconfigured disk unit available to be added.
Using this disk unit might break the switchability of the specified disk
pool. |
0x0001132D |
|
Description: Allowable disk unit for nonswitchable disk
pool, but switchable entity might block switchable disk pool
Recovery: The specified disk pool is nonswitchable. This disk
unit resides in a switchable frame that contains only nonconfigured disk units.
It is recommended that you do not add this disk unit to the specified disk pool
because this frame may need to be switched in order to switch the next frame
that may contain disk units configured in a switchable disk pool. |
0x0001132E |
|
Description: The mirror copy is locally mirrored and the
mirrored pair for this disk unit is missing.
Recovery: Find or fix the missing disk. Check the Product
Activity Log (PAL) on the target node. |
0x00011340 |
|
Description: The mirror copy is locally mirrored and this
unit has a lower level of protection as a result of hardware being moved.
Recovery: Move hardware or replace the disk unit with a disk
unit in a different tower or IOP that has the same level of hardware
protection. |
0x00011341 |
|
Description: A disk unit in the mirror copy would have
better performance if the disk unit were formatted.
Recovery: Remove the disk unit from the disk pool and
format the disk unit
.
Attention: Any information that exists on the disk unit when it is
formatted will be lost.
|
0x00011342 |
|
Description: A parity protected disk unit in the mirror
copy has failed.
Recovery: Refer to
Replace a disk unit
in the online help for step-by-step instructions on
replacing a disk unit and rebuilding the disk unit data. |
0x00011343 |
|
Description: A disk unit in the mirror copy has no
alternate sectors remaining.
Recovery: Replace the disk unit. See
Suspend mirroring
and
Replace a disk unit
in the online help for step-by-step instructions on
suspending and replacing a disk unit. |
0x00011344 |
|
Description: A disk unit in the mirror copy failed during
a start compression operation or during a stop compression operation.
Recovery: To recover from start compression failure, start
SST or DST in the character-based interface. Select the following:
- Work with Disk Units
- Work with disk unit recovery
- Recover from start compression failure
|
0x00011345 |
|
Description: A disk unit in the mirror copy is missing a
connection.
Recovery: Check the Product Activity Log (PAL) on the target
node. Take action and try the operation again.
If the problem persists, contact your technical support provider.
|
0x00011346 |
|
Description: A disk unit in the mirror copy had an
unexpected warning
Recovery: Check the Product Activity Log (PAL) on the target
node. Take action and try the operation again.
If the problem persists, contact your technical support provider.
|
0x00011347 |
|
Description: There is an unknown configuration
source status in the mirror copy.
Recovery: The configuration source disk unit may
be missing. If the disk unit is missing, locate it on the mirror copy
and correct the problem. |
0x00011348 |
|
Description: Manual intervention will be required
Recovery: The storage subsystems you selected require some
kind of manual intervention to complete the procedure. The system will do the
preparation activity and indicate it has finished. Consult the appropriate
device documentation, a service representative, or trained installation
provider for the procedure. The system will notify you when the preparation
work is complete and the manual process can be started. |
0x00011401 |
|
Description: Selected parity set is not operational
Recovery: The selected parity set is not operational at this
time. No data will be lost during this function, but in most cases, it is
better to make the parity set operational before continuing. |
0x00011402 |
|
Description: Device parity protection function problem
Recovery: The system could not complete the internal
processing successfully. The "Reclaim IOP cache storage" operation needs to be
performed again on the same IOP. |
0x00011403 |
|
Description: The device parity status does not match the
configuration.
Recovery: None. |
0x00011405 |
|
Description: The Availability option is selected for
parity set optimization, but at least one of the parity sets selected will not
be in an Availability configuration.
Recovery: You must add or rearrange hardware to allow for the
Availability configuration which is at least three disk units attached to
separate SCSI buses on the input/output adapter. See the Disk Management topic
in the iSeries Information
Center for more information.
If the problem persists, contact your technical support provider, or see
IBM eServer iSeries
and AS/400 Technical Support for information about IBM support and services.
|
0x00011406 |
|
Description: Including a disk unit in a parity set
optimized for Availability may cause the Availability configuration to be
degraded.
Recovery: The Availability configuration contains at least
three disk units attached to separate SCSI buses on the input/output adapter.
You may need to add or rearrange hardware to include disk units in an
Availability parity set.See the Disk Management topic in the
iSeries Information Center
for more information.
If the problem persists, contact your technical support provider, or see
IBM eServer iSeries
and AS/400 Technical Support for information about IBM support and services.
|
0x00011407 |
|
Description: While device parity protection is being
stopped, the remaining disk units in the parity set will become R/W protected.
Recovery: None. |
0x00011408 |
|
Checker Errors/Warnings: |
|
Description: Missing disk configuration
Recovery: None. |
0x00020110 |
|
Description: Restore load source
Recovery: None. |
0x00020118 |
|
Description: DASD subsystem error
Recovery: None. |
0x00020120 |
|
Description: Reclaim IOP cache storage required
Recovery: Reclaim IOP cache storage. |
0x00020122 |
|
Description: Disk capacity limit exceeded
Recovery: Delete some data or add more Disks. |
0x00020124 |
|
Description: Unknown load source status
Recovery: None. |
0x00020306 |
|
Description: Licensed Internal Code has been installed on
the incorrect disk unit of the load source mirrored pair.
Recovery: None. |
0x00020308 |
|
Description: Missing disk units in the configuration
Recovery: Run AssignDisk. |
0x00020310 |
|
Description: Disk unit has incomplete data
Recovery: None. |
0x00020312 |
|
Description: No alternates available
Recovery: None. |
0x00020316 |
|
Description: Load Source not at a valid location
Recovery: Place Load Source in a valid location. |
0x00020318 |
|
Description: Disk units without the system support
Recovery: None. |
0x00020320 |
|
Description: Unprotected device parity units in the
configuration
Recovery: None. |
0x00020322 |
|
Description: Unprotected disk units in a mirrored ASP
Recovery: None. |
0x00020324 |
|
Description: Start compression failure
Recovery: None. |
0x00020326 |
|
Description: Unit has incorrect logical partition
configuration
Recovery: None. |
0x00020327 |
|
Description: New disk configuration
Recovery: None. |
0x00021110 |
|
Description: Bad Load Source Configuration
Recovery: None. |
0x00021118 |
|
Description: Cache storage reclaim query failure
Recovery: None. |
0x00021122 |
|
Description: DASD Subsystem error
Recovery: None. |
0x00021124 |
|
Description: Overflowed ASPs
Recovery: Run AutoOverflowRecovery on ASP and IPL. |
0x00021212 |
|
Description: Missing mirror protected units in the
configuration
Recovery: None. |
0x00021310 |
|
Description: Incorrect Licensed Internal Code install
Recovery: None. |
0x00021312 |
|
Description: Lower level of protection
Recovery: None. |
0x00021316 |
|
Description: Disk unit not formatted for optimal
performance
Recovery: None. |
0x00021317 |
|
Description: Device parity protected units in exposed
mode
Recovery: None. |
0x00021318 |
|
Description: Exceeded capacity for protected disk
Recovery: None. |
0x00021320 |
|
Description: Failure during start or stop compression
Recovery: None. |
0x00021323 |
|
Clustering Errors/Warnings:
|
|
Description: This node is not in a device domain
group.
Recovery: Your request cannot be performed because the node
that owns the frame is not in a device domain group, and all non-configured
units are under the Remote I/O (RIO) bus adapter. |
0x0003000D |
|
Description: This node is not in a device domain
group.
Recovery: Your request cannot be performed because the node
that owns the frame is not in a device domain group, and the independent disk
pool units are configured under the Remote I/O (RIO) bus adapter. |
0x0003000E |
|
Description: The independent disk pool is not
switchable.
Recovery: Your request cannot be performed because one of the
independent disk pools in the frame is not switchable. The node is in a device
domain group, and the disk units in the independent disk pool are configured
under the Remote I/O bus adapter. However, the independent disk pool is not in
a cluster resource group, and is therefore not switchable. Add the independent
disk pool to a cluster resource group, and try again. |
0x0003000F |
|
Description: Independent disk pool may not be
switchable.
Recovery: Your request cannot be performed because one of the
independent disk pools in the frame may not be switchable. The node is in a
device domain group, and the disk units in the independent disk pool are
configured under the Remote I/O bus adapter. However, it cannot be determined
whether the independent disk pool is in a cluster resource group. Start
clustering on all nodes, and try again. |
0x00030010 |
|
Description: The cluster resource group for this
independent disk pool is not active.
Recovery: Your request cannot be performed as the cluster
resource group that contains one of the frame's independent disk pools is not
active. Start clustering on all nodes, and try again. |
0x00030011 |
|
Description: A failure occurred during the processing of
your switch frame request.
Recovery: Check the problem activity log (PAL) for
errors. |
0x00030032 |
|
Description: Unable to complete the operation because a
cluster resource group in the frame is active.
Recovery: Your request cannot be performed because a cluster
resource group in the frame is active. End the active cluster resource group
and try your request again. |
0x00030066 |
|
Description: A hardware failure occurred during the
processing of your request.
Recovery: Check the problem activity log for errors. Try the
request again. If the problem still persists, contact your technical support provider. |
0x0003007E |
|
Description: Could not complete request because buses must
be owned by a single partition.
Recovery: The frame is owned by a system that has logical
partitions (LPAR) enabled. To change the switchable mode of a frame in an LPAR
environment with a high-speed link (HSL) configuration, all of the buses in the
frame must be owned by a single partition. |
0x00030100 |
|
Description: Could not complete request because buses must
be owned by a single partition.
Recovery: The frame is owned by a system that has logical
partitions (LPAR) enabled. To change the switchable mode of a frame in an LPAR
environment with a high-speed link (HSL) configuration, all of the buses in the
frame must be owned by a single partition. |
0x00030103 |
|
Description: Could not make a frame/unit switchable because one
or more resources in the frame/unit are assigned to one or more I/O pools.
Recovery: Remove all of the resources in the frame/unit from I/O
pools and try the request again. |
0x00030106 |
|
Description: Cannot complete request because frame
contains logical partition load source disk unit
Recovery: In order to complete the operation, the frame
cannot contain any buses that contain the load source disk unit of a logical
partition. |
0x0003012E |
|
Description: Remote I/O (RIO) bus adapter contains disk
units that are not configured in a switchable disk pool.
Recovery: None. |
0x00030132 |
|
Description: The bus adapter hardware in the frame does
not support switching.
Recovery: None. |
0x00030146 |
|
Description: A system power control network (SPCN) failure
occurred.
Recovery: Check the problem log for errors. |
0x00030147 |
|
Description: The storage area network manager is not
active.
Recovery: The frame is in a high-speed link (HSL), so the
storage area network (SAN) manager must be enabled in order to change the frame
from private mode to switchable mode. Enable the SAN manager and try the
request again. If the problem still persists, contact your technical support provider. |
0x00030148 |
|
Description: The current high-speed link (HSL)
configuration is not valid.
Recovery: Check the Problem Activity Log for errors. |
0x00030149 |
|
Description: The current high-speed link (HSL)
configuration is not complete.
Recovery: Check the Problem Activity Log for errors. |
0x0003014A |
|
Description: The frame does not contain the most current
system power control network (SPCN) code.
Recovery: None. |
0x0003014B |
|
Description: The specified frame is not owned by the SPCN
system.
Recovery: You can only change the switch mode of a frame when
the frame is owned by the system power control network (SPCN) system. Change
the frame ownership appropriately and try the request again. |
0x00030159 |
|
Description: Current node does not own frame.
Recovery: You can only change the switch mode of a frame from
the system that owns the frame. Also, the system power control network (SPCN)
must own the frame. |
0x00030160 |
|
Description: The frame does not have a specified
owner.
Recovery: None. |
0x00030161 |
|
Description: Current node does not own frame.
Recovery: You can only change the switch mode of a frame from
the system that owns the frame. Also, the system power control network (SPCN)
must own the frame. |
0x00030162 |
|