CLI message reference

Edit online

CLI messages are listed in alphanumeric order.

CMMVC4041E
You must use an 0x parameter for the -lba and -vdisklba parameters.
CMMVC4042E
You must use an 0x parameter for the -lba and -mdisklba parameters.
CMMVC4043E
You must use an 0x parameter for the -mdisklba parameter.
CMMVC4044E
You must use an 0x parameter for the -drivelba parameter.
CMMVC5000I
No message was found for major rc MAJOR_RC , minor rc MINOR_RC , for action/view id ACTION_VIEW_ID .
CMMVC5700E
The parameter list is not valid.
CMMVC5701E
No object ID was specified.
CMMVC5702E
VALUE is below the minimum level.
CMMVC5703E
The value or list starting with VALUE is above the maximum permitted for that value or has exceeded the number of items allowed in a list.
CMMVC5704E
VALUE is not divisible by the permitted step value.
CMMVC5705E
A required parameter is missing.
CMMVC5706E
An invalid argument has been entered for the PARAMETER parameter.
CMMVC5707E
Required parameters are missing.
CMMVC5708E
The PARAMETER parameter is missing its associated arguments.
CMMVC5709E
VALUE is not a supported parameter.
CMMVC5711E
VALUE is not valid data.
CMMVC5712E
Required data is missing.
CMMVC5713E
Some parameters are mutually exclusive.
CMMVC5714E
The parameter list is empty.
CMMVC5715E
The parameter list does not exist.
CMMVC5716E
Non-numeric data was entered for the numeric field FIELD. Enter a numeric value.
CMMVC5717E
No match was found for the specified unit.
CMMVC5718E
An unexpected return code was received.
CMMVC5719E
A value of VALUE requires the parameter PARAMETER to be specified.
CMMVC5721E
VALUE is not a valid time stamp format. The valid time stamp format is YYMMDDHHMMSS.
CMMVC5722E
VALUE contains a month value that is not valid. The valid time stamp format is YYMMDDHHMMSS.
CMMVC5723E
VALUE contains a day value that is not valid. The valid time stamp format is YYMMDDHHMMSS.
CMMVC5724E
VALUE contains an hour value that is not valid. The valid time stamp format is YYMMDDHHMMSS.
CMMVC5725E
VALUE contains a minutes value that is not valid. The valid time stamp format is YYMMDDHHMMSS.
CMMVC5726E
VALUE contains a seconds value that is not valid. The valid time stamp format is YYMMDDHHMMSS.
CMMVC5727E
VALUE is not a valid filter.
CMMVC5728E
%1 is not a valid time format. The valid time format is MMDDHHmmYYYY with YYYY<2070.
CMMVC5729E
One or more components in the list is not valid.
CMMVC5730E
VALUE is only valid when VALUE has a value of VALUE .
CMMVC5731E
VALUE can only be entered when VALUE has been entered.
CMMVC5732E
The command cannot be initiated because it was not run on the configuration node.
CMMVC5733E
Enter at least one parameter.
CMMVC5734E
A combination of values was entered that is not valid.
CMMVC5735E
The name entered is not valid. Enter an alphanumeric string that does not start with a number.
CMMVC5737E
The parameter PARAMETER has been entered multiple times. Enter the parameter only one time.
CMMVC5738E
The argument ARGUMENT contains too many characters.
CMMVC5739E
The argument ARGUMENT does not contain enough characters.
CMMVC5740E
The filter flag VALUE is not valid.
CMMVC5741E
The filter value VALUE is not valid.
CMMVC5742E
A specified parameter is out of its valid range.
CMMVC5743E
A specified parameter does not comply with the step value.
CMMVC5744E
Too many objects were specified in the command.
CMMVC5745E
Too few objects were specified in the request.
CMMVC5746E
The requested operation cannot be applied to the object specified.
CMMVC5747E
The action requested is invalid - internal error.
CMMVC5748E
The action requested is invalid - internal error.
CMMVC5749E
The memory dump file name that is specified exists.
CMMVC5750E
The dump file could not be created - the file system is probably full.
CMMVC5751E
The dump file could not be written to.
CMMVC5752E
Request failed. The object contains child objects, these must be deleted first.
CMMVC5753E
The specified object does not exist or is not a suitable candidate.
CMMVC5754E
The specified object does not exist, or the name supplied does not meet the naming rules.
CMMVC5755E
Cannot create as the sizes of the specified objects do not match.
CMMVC5756E
Cannot perform the request as the object id is already mapped to another object or is the subject of an FC or RC relationship.
CMMVC5757E
Self Defining Structure (SDS) defaults not found - internal error.
CMMVC5758E
Object name already exists.
CMMVC5759E
An internal error has occurred - memory could not be allocated.
CMMVC5762E
The request did not complete before the timeout period expired.
CMMVC5763E
The node failed to go online.
CMMVC5764E
The mode change request is invalid - internal error
CMMVC5765E
The object specified is no longer a candidate - a change occurred during the request.
CMMVC5767E
One or more of the parameters specified are invalid or a parameter is missing.
CMMVC5769E
The requested operation requires all nodes to be online - one or more nodes are not online.
CMMVC5770E
The SSH key file supplied is invalid.
CMMVC5771E
The operation requested could not complete, usually due to child objects existing. To force the operation, specify the force flag.
CMMVC5772E
The operation requested could not be performed because an update is in progress.
CMMVC5773E
The object selected is in the wrong mode to perform the requested operation.
CMMVC5774E
The userid supplied is not valid.
CMMVC5775E
The directory attribute specified is not valid.
CMMVC5776E
The directory listing could not be retrieved.
CMMVC5777E
The node could not be added to the IO Group, because the other node in the IO Group is in the same power domain.
CMMVC5778E
Cannot create another cluster, a cluster already exists.
CMMVC5780E
The action could not be completed using the Remote Cluster name. Use the Remote Cluster Unique ID instead.
CMMVC5810E
The action failed because the specified resource was unavailable.
CMMVC5781E
The cluster ID specified is invalid.
CMMVC5782E
The object specified is offline.
CMMVC5783E
The information is not available to complete this command.
CMMVC5784E
The cluster name specified is not unique, specify the cluster using the cluster ID.
CMMVC5785E
The file name that is specified contains an invalid character.
CMMVC5786E
The action failed because the cluster is not in a stable state.
CMMVC5787E
The cluster was not created because a cluster already exists.
CMMVC5788E
The service IP address is not valid.
CMMVC5789E
The cluster was not modified because the IP address, subnet mask, service address, SNMP address, or gateway address is not valid.
CMMVC5790E
The node was not added to the cluster because the maximum number of nodes has been reached.
CMMVC5791E
The action failed because an object that was specified in the command does not exist.
CMMVC5792E
The action failed because the I/O group is used for recovery.
CMMVC5793E
The node was not added to the cluster because the I/O group already contains a pair of nodes.
CMMVC5794E
The action failed because the node is not a member of the cluster.
CMMVC5795E
The node was not deleted because an update is in progress.
CMMVC5796E
The action failed because the I/O group that the node belongs to is unstable.
CMMVC5797E
The node was not deleted because this is the last node in the I/O group and there are volumes associated with the I/O group.
CMMVC5798E
The action failed because the node is offline.
CMMVC5799E
The shut down was not successful because there is only one online node in the I/O group.
CMMVC5800E
The action failed because an entity that was specified in the command does not exist.
CMMVC5801E
The update of the cluster could not proceed because every node in the cluster must be online. Either delete the node that is offline or bring the node online and resubmit the command
CMMVC5802E
The update of the cluster could not proceed because there is an I/O group in the cluster that contains only one node. The update requires that each node in an I/O group be shut down and restarted. If there is only one node in an I/O group, I/O operations could be lost if I/O operations are not stopped before beginning the update.
CMMVC5803E
The entry in the event log was not marked because the error is already fixed or unfixed, or the sequence number could not be found.
CMMVC5804E
The action failed because an object that was specified in the command does not exist.
CMMVC5805E
The progress information was not returned because the FlashCopy statistics are not ready yet.
CMMVC5806E
The action failed because an object that was specified in the command does not exist.
CMMVC5807E
The action failed because the managed disk (MDisk) cannot be changed to the specified mode.
CMMVC5808E
The action failed because the managed disk (MDisk) does not exist.
CMMVC5809E
The tracing of I/O operations was not started because it is already in progress.
CMMVC5811E
The quorum index number for the object was not set because the quorum disk does not exist.
CMMVC5812E
The action failed because the managed disk (MDisk) is not in managed mode.
CMMVC5813E
The quorum index number for the object was not set because the object has a sector size that is not valid.
CMMVC5814E
The quorum index number for the managed disk (MDisk) was not set because quorum is not allowed on one or more associated controllers.
CMMVC5815E
The storage pool was not created because an entity that was specified in the command does not exist.
CMMVC5816E
The action failed because an entity that was specified in the command does not exist.
CMMVC5817E
The specified storage pool was invalid.
CMMVC5818E
The storage pool was not deleted because there is at least one MDisk in the group.
CMMVC5819E
The managed disk (MDisk) was not added to the storage pool because the MDisk is part of another storage pool.
CMMVC5820E
The managed disk (MDisk) was not added to the storage pool because an entity that was specified in the command does not exist.
CMMVC5821E
The managed disk (MDisk) was not added to the storage pool because not enough MDisks were included in the list.
CMMVC5822E
The managed disk (MDisk) was not added to the storage pool because too many MDisks were included in the list.
CMMVC5823E
The managed disk (MDisk) was not deleted from the storage pool because the MDisk is part of another storage pool.
CMMVC5824E
The managed disk (MDisk) was not deleted from the storage pool because it does not belong to the storage pool.
CMMVC5825E
The managed disk (MDisk) was not deleted from the storage pool because a volume is allocated from one or more of the specified MDisks. A forced deletion is required.
CMMVC5826E
The volume was not created because an entity that was specified in the command does not exist.
CMMVC5827E
The command failed as a result of either an inconsistency between two or more of the entered parameters, or an inconsistency between a parameter and the requested action.
CMMVC5828E
The volume was not created because the I/O group contains no nodes.
CMMVC5829E
The image-mode or sequential-mode volume was not created because more than one managed disk (MDisk) is specified.
CMMVC5830E
The image-mode volume was not created because no managed disk (MDisk) was specified in the command.
CMMVC5831E
The volume was not created because the preferred node for I/O operations is not part of the I/O group.
CMMVC5832E
The property of the volume was not modified because an entity that was specified in the command does not exist.
CMMVC5833E
The property of the volume was not modified because there are no nodes in the I/O group.
CMMVC5834E
The I/O group for the volume was not modified because the group is a recovery I/O group. To modify the I/O group, use the force option.
CMMVC5835E
The volume was not expanded because an entity that was specified in the command does not exist.
CMMVC5836E
The volume was not shrunk because it is locked.
CMMVC5837E
The action failed because the volume is part of a FlashCopy mapping.
CMMVC5838E
The action failed because the volume is part of a Remote Copy mapping.
CMMVC5839E
The volume was not shrunk because an object that was specified in the command does not exist.
CMMVC5840E
The volume was not deleted because it is mapped to a host, or it is part of a FlashCopy mapping or Remote Copy relationship, or a cloud snapshot or restore operation is in progress, or it is involved in an image mode migration.
CMMVC5841E
The volume was not deleted because it does not exist.
CMMVC5842E
The action failed because an object that was specified in the command does not exist.
CMMVC5843E
The host mapping was not created because the volume does not have a capacity greater than zero bytes.
CMMVC5844E
The host mapping was not created because the SCSI logical unit number (LUN) ID is not valid.
CMMVC5845E
The extent was not migrated because an object that was specified in the command does not exist.
CMMVC5846E
The volume was not migrated because an object that was specified in the command does not exist.
CMMVC5847E
The volume was not migrated because its associated managed disk (MDisk) is already in the storage pool.
CMMVC5848E
The action failed because the volume does not exist or it is being deleted.
CMMVC5849E
The migration failed because some or all of the extents are already being migrated.
CMMVC5850E
The extent was not migrated because there is a problem with the source extents.
CMMVC5851E
The extent was not migrated because there is a problem with the target extents.
CMMVC5852E
The migration failed because there are too many migrations in progress.
CMMVC5853E
The action failed because there was a problem with the group.
CMMVC5854E
The extent information was not returned because the extent is not used or does not exist.
CMMVC5855E
The extent information was not returned because the managed disk (MDisk) is not used by any volume.
CMMVC5856E
The action failed because the volume does not belong to the specified storage pool.
CMMVC5857E
The action failed because the managed disk (MDisk) does not exist or it is not a member of the storage pool.
CMMVC5858E
The action failed because the volume is in the wrong mode, the managed disk (MDisk) is in the wrong mode, or both are in the wrong mode.
CMMVC5859E
The migration did not complete because an error occurred during the migration of the last extent on an image-mode volume.
CMMVC5860E
The action failed because there were not enough extents in the storage pool.
CMMVC5861E
The action failed because there were not enough extents on the managed disk (MDisk).
CMMVC5862E
The action failed because the volume is being formatted.
CMMVC5863E
The migration failed because there are not enough free extents on the target managed disk (MDisk).
CMMVC5864E
The extent information was not returned because the source extent is not used.
CMMVC5865E
The action failed because the extent is out of range for the managed disk (MDisk) or volume specified.
CMMVC5866E
The action failed because the extent contains internal data.
CMMVC5867E
The action failed because the worldwide port name is already assigned or is not valid.
CMMVC5868E
The action failed because an entity that was specified in the command does not exist.
CMMVC5869E
The host object was not renamed because the host ID or name is not valid.
CMMVC5870E
The host object was not deleted because an entity that was specified in the command does not exist.
CMMVC5871E
The host object was not deleted because it is mapped to one or more volumes.
CMMVC5872E
The port (WWPN) was not added to the host object because an object that was specified in the command does not exist.
CMMVC5873E
No matching WWPN.
CMMVC5874E
The action failed because the host does not exist.
CMMVC5875E
The action failed because the volume does not exist.
CMMVC5876E
The host mapping was not created because the maximum number of mappings has been reached.
CMMVC5877E
The host mapping was not created because the maximum number of SCSI LUNs has been allocated.
CMMVC5878E
The host mapping was not created because this volume is already mapped to this host.
CMMVC5879E
The host mapping was not created because a volume is already mapped to this host with this SCSI LUN.
CMMVC5880E
The volume was not created because a capacity of zero bytes is not allowed for image mode disks.
CMMVC5881E
The FlashCopy mapping was not created because an entity that was specified in the command does not exist.
CMMVC5882E
The FlashCopy mapping was not created because a mapping for the source or target volume already exists.
CMMVC5883E
The FlashCopy mapping was not created because the recovery I/O group is associated with the source or target volume.
CMMVC5884E
The FlashCopy mapping was not created because the source or target volume cannot be a member of a Remote Copy mapping.
CMMVC5885E
The FlashCopy mapping was not created because this source or target volume cannot be a member of a FlashCopy mapping.
CMMVC5886E
The FlashCopy mapping was not created because the source or target volume is associated with the recovery I/O group.
CMMVC5887E
The FlashCopy mapping was not created because the source or target volume must not be in router mode.
CMMVC5888E
The action failed because an entity that was specified in the command does not exist.
CMMVC5889E
The FlashCopy mapping was not deleted because an entity that was specified in the command does not exist.
CMMVC5890E
The FlashCopy mapping or consistency group was not started because starting consistency group 0 is not a valid operation.
CMMVC5891E
The FlashCopy consistency group was not created because the name is not valid.
CMMVC5892E
The FlashCopy consistency group was not created because it already exists.
CMMVC5893E
The action failed because an entity that was specified in the command does not exist.
CMMVC5894E
The FlashCopy consistency group was not deleted because you are trying to delete consistency group 0 or the name of the consistency group is not valid.
CMMVC5895E
The FlashCopy consistency group was not deleted because it contains mappings. To delete this consistency group, a forced deletion is required.
CMMVC5896E
The FlashCopy mapping was not deleted because the mapping or consistency group is in the preparing state. The mapping or consistency group must be stopped first.
CMMVC5897E
The FlashCopy mapping was not deleted because the mapping or consistency group is in the prepared state. The mapping or consistency group must be stopped first.
CMMVC5898E
The FlashCopy mapping was not deleted because the mapping or consistency group is in the copying state. The mapping or consistency group must be stopped first.
CMMVC5899E
The FlashCopy mapping was not deleted because the mapping or consistency group is in the stopped state. To delete the mapping, a forced deletion is required.
CMMVC5900E
The FlashCopy mapping was not deleted because the mapping or consistency group is in the suspended state. The mapping or consistency group must be stopped first.
CMMVC5901E
The FlashCopy mapping was not prepared because the mapping or consistency group is already in the preparing state.
CMMVC5902E
The FlashCopy mapping was not prepared because the mapping or consistency group is already in the prepared state.
CMMVC5903E
The FlashCopy mapping was not prepared because the mapping or consistency group is already in the copying state.
CMMVC5904E
The FlashCopy mapping was not prepared because the mapping or consistency group is already in the suspended state.
CMMVC5905E
The FlashCopy mapping or consistency group was not started because the mapping or consistency group is in the idle state. The mapping or consistency group must be prepared first.
CMMVC5906E
The FlashCopy mapping or consistency group was not started because the mapping or consistency group is in the preparing state.
CMMVC5907E
The FlashCopy mapping or consistency group was not started because the mapping or consistency group is already in the copying state.
CMMVC5908E
The FlashCopy mapping or consistency group was not started because the mapping or consistency group is in the stopped state. The mapping or consistency group must be prepared first.
CMMVC5909E
The FlashCopy mapping or consistency group was not started because the mapping or consistency group is in the suspended state.
CMMVC5910E
The FlashCopy mapping or consistency group was not stopped because the mapping or consistency group is in the idle state.
CMMVC5911E
The FlashCopy mapping or consistency group was not stopped because the mapping or consistency group is in the preparing state.
CMMVC5912E
The FlashCopy mapping or consistency group was not stopped because the mapping or consistency group is already in the stopped state.
CMMVC5913E
The properties of the FlashCopy mapping were not modified because the mapping or consistency group is in the preparing state.
CMMVC5914E
The properties of the FlashCopy mapping were not modified because the mapping or consistency group is in the prepared state.
CMMVC5915E
The properties of the FlashCopy mapping were not modified because the mapping or consistency group is in the copying state.
CMMVC5916E
The properties of the FlashCopy mapping were not modified because the mapping or consistency group is in the suspended state.
CMMVC5917E
The FlashCopy mapping was not created because there is no memory in which to create the bitmap.
CMMVC5918E
The FlashCopy mapping was not prepared, either because there are no online nodes in the I/O group or because there are unrecovered FlashCopy mappings or unrecovered Global Mirror or Metro Mirror relationships in the I/O group.
CMMVC5919E
The FlashCopy mapping or consistency group was not started, either because there are no online nodes in the I/O group or because there are unrecovered FlashCopy mappings or unrecovered Global Mirror or Metro Mirror relationships in the I/O group.
CMMVC5920E
The FlashCopy mapping was not created because the consistency group is not idle.
CMMVC5921E
The properties of the FlashCopy mapping were not modified because the consistency group is not idle.
CMMVC5922E
The FlashCopy mapping was not created because the destination volume is too small.
CMMVC5923E
The FlashCopy mapping cannot be created, either because there are no online nodes in the I/O group or because there are unrecovered FlashCopy mappings in the I/O group.
CMMVC5924E
The FlashCopy mapping was not created because the source and target volumes are different sizes.
CMMVC5925E
The remote cluster partnership was not created because it already exists.
CMMVC5926E
The remote cluster partnership was not created because there are too many partnerships.
CMMVC5927E
The action failed because the cluster ID is not valid.
CMMVC5928E
The action failed because the cluster name is a duplicate of another cluster.
CMMVC5929E
The Remote Copy partnership was not deleted because it has already been deleted.
CMMVC5930E
The Remote Copy relationship was not created because an object that was specified in the command does not exist.
CMMVC5931E
The Remote Copy relationship was not created because the master or auxiliary volume is locked.
CMMVC5932E
The Remote Copy relationship was not created because the master or auxiliary volume is a member of a FlashCopy mapping.
CMMVC5933E
The Remote Copy relationship was not created because the master or auxiliary volume is in the recovery I/O group.
CMMVC5934E
The Remote Copy relationship was not created because the master or auxiliary volume is in the router mode.
CMMVC5935E
The action failed because an object that was specified in the command does not exist.
CMMVC5936E
The action failed because an object that was specified in the command does not exist.
CMMVC5937E
The action failed because an object that was specified in the command does not exist.
CMMVC5938E
The Remote Copy consistency group was not deleted because the consistency group contains relationships. To delete the consistency group, the force option is required.
CMMVC5939E
The action failed because the cluster is not in a stable state.
CMMVC5940E
The cluster that contains the auxiliary volume is unknown.
CMMVC5941E
The cluster that contains the master volume has too many consistency groups.
CMMVC5942E
The cluster that contains the auxiliary volume has too many consistency groups.
CMMVC5943E
The specified relationship is not valid.
CMMVC5944E
The specified consistency group is not valid.
CMMVC5945E
The specified master cluster is not valid.
CMMVC5946E
The specified auxiliary cluster is not valid.
CMMVC5947E
The specified master volume is not valid.
CMMVC5948E
The specified auxiliary volume is not valid.
CMMVC5949E
The specified relationship is unknown.
CMMVC5950E
The specified consistency group is unknown.
CMMVC5951E
The operation cannot be performed because the relationship is not a stand-alone relationship.
CMMVC5952E
The relationship and consistency group have different master clusters.
CMMVC5953E
The relationship and group have different auxiliary clusters.
CMMVC5954E
The master and auxiliary volumes are different sizes.
CMMVC5955E
The maximum number of relationships has been reached.
CMMVC5956E
The maximum number of consistency groups has been reached.
CMMVC5957E
The master volume is already in a relationship.
CMMVC5958E
The auxiliary volume is already in a relationship.
CMMVC5959E
There is a relationship that already has this name on the master cluster.
CMMVC5960E
There is a relationship that already has this name on the auxiliary cluster.
CMMVC5961E
There is a consistency group that already has this name on the master cluster.
CMMVC5962E
There is a consistency group that already has this name on the auxiliary cluster.
CMMVC5963E
No direction has been defined.
CMMVC5964E
The copy priority is not valid.
CMMVC5965E
The volumes are in different I/O groups on the local cluster.
CMMVC5966E
The master volume is unknown.
CMMVC5967E
The auxiliary volume is unknown.
CMMVC5968E
The relationship cannot be added because the states of the relationship and the consistency group do not match.
CMMVC5969E
The Remote Copy relationship was not created, either because there are no online nodes in the I/O group or because there are unrecovered FlashCopy mappings or unrecovered Global Mirror or Metro Mirror relationships in the I/O group.
CMMVC5970E
The Remote Copy relationship was not created because there is not enough memory.
CMMVC5971E
The operation was not performed because the consistency group contains no relationships.
CMMVC5972E
The operation was not performed because the consistency group contains relationships.
CMMVC5973E
The operation was not performed because the consistency group is not synchronized.
CMMVC5974E
The operation did not complete because one or more volumes in the consistency group are offline or inaccessible, or the Remote Copy feature is not licensed.
CMMVC5975E
The operation was not performed because the cluster partnership is not connected.
CMMVC5976E
The operation was not performed because the consistency group is in the freezing state.
CMMVC5977E
The operation was not performed because it is not valid given the current consistency group state.
CMMVC5978E
The operation was not performed because the relationship is consistent but is not synchronized. Restarting the relationship by using the -force parameter will make the relationship inconsistent until the background copy has completed.
CMMVC5980E
The operation was not performed because the master and auxiliary clusters are not connected.
CMMVC5981E
The operation was not performed because the relationship is in the freezing state.
CMMVC5982E
The operation was not performed because it is not valid given the current relationship state.
CMMVC5983E
dump file was not created. This might be due to the file system being full.
CMMVC5984E
The dump file was not written to disk. This might be due to the file system being full.
CMMVC5985E
The action failed because the specified directory is not permitted for this command.
CMMVC5986E
The tracing of I/O operations was not started because the volume or managed disk (MDisk) failed to return any statistics.
CMMVC5987E
VALUE is not a valid command line option.
CMMVC5988E
command should not be run by the root userid. Use the admin userid.
CMMVC5989E
The operation was not performed because the relationship is offline or the Remote Copy feature is not licensed.
CMMVC5990E
The FlashCopy consistency group was not stopped as there are no FlashCopy mappings within the group.
CMMVC5991E
The Remote Copy consistency group was not stopped as there are no Remote Copy relationships within the group.
CMMVC5992E
The Remote Copy consistency group was not stopped as there are no Remote Copy relationships within the group.
CMMVC5993E
The specified update package does not exist.
CMMVC5994E
Error in verifying the signature of the update package.
CMMVC5995E
An error prevented the unpacking of the update package.
CMMVC5996E
The specific update package cannot be installed over the current version.
CMMVC5999W
Featurization for this facility has not been enabled.
CMMVC6000W
Featurization for this facility has not been enabled.
CMMVC6001E
The FlashCopy consistency group was not started as there are no FlashCopy mappings within the group.
CMMVC6002E
This command can only be run on a node that is in the service state.
CMMVC6003E
This command cannot be run on a node that is in the service state.
CMMVC6004E
The delimiter value VALUE is invalid.
CMMVC6005E
The view request failed as the specified object is not a member of an appropriate group.
CMMVC6006E
The managed disk (MDisk) was not deleted because the resource was busy.
CMMVC6007E
The two passwords that were entered do not match.
CMMVC6008E
The key already exists.
CMMVC6009E
Unable to allocate a block of memory in which to copy the returned data.
CMMVC6010E
Unable to complete the command as there are insufficient free extents, or the command requested an expansion of 0 size.
CMMVC6011E
This cluster is part of a remote cluster partnership. Because this update package will make changes to the cluster state, it cannot be applied to the current code level until all remote cluster partnerships are deleted.
CMMVC6012W
The virtualized storage capacity is approaching the amount that you are licensed to use.
CMMVC6013E
The command failed because there is a consistency group mismatch on the aux cluster.
CMMVC6014E
The command failed because the requested object is either unavailable or does not exist.
CMMVC6015E
A delete request is already in progress for this object.
CMMVC6016E
The action failed as there would be, or are, no more disks in the storage pool.
CMMVC6017E
A parameter or argument contains invalid characters. Ensure that all characters are ASCII.
CMMVC6018E
The update pre-install process failed.
CMMVC6019E
The update failed because a node pended.
CMMVC6020E
The update failed because the system was unable to distribute the package to all of the nodes.
CMMVC6021E
The system is currently busy performing another request. Try again later.
CMMVC6022E
The system is currently busy performing another request. Try again later.
CMMVC6023E
The system is currently busy performing another request. Try again later.
CMMVC6024E
The auxiliary volume entered is invalid.
CMMVC6025E
The RC consistency group Master cluster is not the local cluster.
CMMVC6026E
The RC consistency group is not in the stopped state.
CMMVC6027E
The RC consistency group is not the primary master.
CMMVC6028E
This package cannot be applied to the current code level because it contains changes to the cluster state and there are remote cluster partnerships defined.
CMMVC6029E
All nodes must have identical code level before a concurrent code update can be performed.
CMMVC6030E
The operation was not performed because the FlashCopy mapping is part of a consistency group. The action must be performed at the consistency group level.
CMMVC6031E
The operation was not performed because the FlashCopy consistency group is empty.
CMMVC6032E
The operation was not performed because one or more of the entered parameters is invalid for this operation.
CMMVC6033E
The action failed due to an internal error.
CMMVC6034E
The action failed because the maximum number of objects has been reached.
CMMVC6035E
The action failed as the object already exists.
CMMVC6036E
An invalid action was requested.
CMMVC6037E
The action failed as the object is not empty.
CMMVC6038E
The action failed as the object is empty.
CMMVC6039E
The action failed as the object is not a member of a group.
CMMVC6040E
The action failed as the object is not a parent.
CMMVC6041E
The action failed as the cluster is full.
CMMVC6042E
The action failed as the object is not a cluster member.
CMMVC6043E
The action failed as the object is a member of a group.
CMMVC6044E
The action failed as the object is a parent.
CMMVC6045E
The action failed, as the -force flag was not entered.
CMMVC6046E
The action failed as too many candidates were selected.
CMMVC6047E
The action failed as too few candidates were selected.
CMMVC6048E
The action failed as the object is busy.
CMMVC6049E
The action failed as the object is not ready.
CMMVC6050E
The action failed as the command was busy.
CMMVC6051E
An unsupported action was selected.
CMMVC6052E
The action failed as the object is a member of a FlashCopy mapping.
CMMVC6053E
An invalid WWPN was entered.
CMMVC6054E
The action failed as not all nodes are online.
CMMVC6055E
The action failed as an update is in progress.
CMMVC6056E
The action failed as the object is too small.
CMMVC6058E
The action failed as the object is in the recovery HWS.
CMMVC6059E
The action failed as the object is in an invalid mode.
CMMVC6060E
The action failed as the object is being deleted.
CMMVC6061E
The action failed as the object is being resized.
CMMVC6062E
The action failed as the object is being moved between HWS.
CMMVC6063E
The action failed as there are no more disks in the group.
CMMVC6064E
The action failed as the object has an invalid name.
CMMVC6065E
The action failed as the object is not in a group.
CMMVC6066E
The action failed as the system is running low on memory.
CMMVC6067E
The action failed as the SSH key was not found.
CMMVC6068E
The action failed as there are no free SSH keys.
CMMVC6069E
The action failed as the SSH key is already registered.
CMMVC6070E
An invalid or duplicated parameter, unaccompanied argument, or incorrect argument sequence has been detected. Ensure that the input is as per the help.
CMMVC6071E
The host mapping was not created because the volume is already mapped to a host.
CMMVC6073E
The maximum number of files has been exceeded.
CMMVC6074E
The command failed as the extent has already been assigned.
CMMVC6075E
The expand failed as the last extent is not a complete extent.
CMMVC6076E
The command failed because the volume cache is not empty. Either wait for the cache to flush or use the force flag to discard the contents of the cache.
CMMVC6077E
WARNING - Unfixed errors should be fixed before applying an update. Depending on the nature of the errors, they might cause the update process to fail. It is highly recommended to fix these errors before proceeding. If a particular error cannot be fixed, contact the support center.
CMMVC6078E
The action failed because the object is in an invalid mode.
CMMVC6079E
Metadata recovery could not complete the operation because a parameter is invalid.
CMMVC6081E
Metadata Recovery is busy processing the previous operation.
CMMVC6082E
The attempt to abort metadata recovery failed because the previous operation has completed.
CMMVC6083E
Metadata recovery could not find a valid dumpfile required for the rebuild operation.
CMMVC6084E
Metadata recovery could not create/open/write the scan file, the disk might be full.
CMMVC6085E
Metadata recovery could not create/open/write the dump file, the disk might be full.
CMMVC6086E
Metadata recovery could not create/open/write the progress file, the disk might be full.
CMMVC6087E
Metadata recovery could not map the buffers necessary to complete the operation.
CMMVC6088E
The lba at which metadata recovery was requested does not contain metadata.
CMMVC6089E
The metadata at the requested lba is flagged as invalid.
CMMVC6090E
The metadata header checksum verification failed.
CMMVC6091E
The metadata region checksum verification failed.
CMMVC6092E
The metadata recovery operation was aborted.
CMMVC6093E
Metadata recovery internal error - (read only)
CMMVC6095E
Metadata recovery encountered the end of the disk.
CMMVC6096E
The metadata recovery task could not be initiated because the required back-end resource could not be found.
CMMVC6097E
The metadata recovery task could not be initiated because the system was unable to send the required I/O to the back-end resource.
CMMVC6098E
The copy failed as the specified node is the configuration node.
CMMVC6100E
OPTION not consistent with ACTION
CMMVC6101E
OPTION not consistent with OPTION
CMMVC6102E
OPTION and OPTION are alternatives
CMMVC6103E
Problem with FILENAME : DETAILS
CMMVC6104E
Action ACTION not run
CMMVC6105E
Different names for source SOURCE_CLUSTER_NAME and target TARGET_CLUSTER_NAME clusters
CMMVC6106W
Target cluster has non-default id_alias ALIAS .
CMMVC6107E
NUMBER_OF_OBJECTS io_grp objects in target cluster; NUMBER_OF_REQUIRED_OBJECTS are required
CMMVC6108I
Disk controller system with a WWNN of WWNN_VALUE found.
CMMVC6109E
Backup file version version_id is not compatible with current version version_id
CMMVC6110E
Bad code level: VALUE .
CMMVC6111E
The cluster code level could not be determined from VALUE .
CMMVC6112W
OBJECT_TYPE OBJECT_NAME has a default name.
CMMVC6113E
The command COMMAND has failed with return code RETURN_CODE .
CMMVC6114E
No help for action ACTION .
CMMVC6115W
Feature FEATURE_PROPERTY mismatch: VALUE expected; VALUE found.
CMMVC6116I
Feature match for FEATURE .
CMMVC6117E
FIX_OR_FEATURE is not available.
CMMVC6118I
TYPE with PROPERTY PROPERTY_VALUE and PROPERTY PROPERTY_VALUE found.
CMMVC6119E
TYPE with PROPERTY PROPERTY_VALUE not found.
CMMVC6120E
Target is not the configuration node
CMMVC6121E
No cluster id or id_alias in backup configuration.
CMMVC6122E
No TYPE with PROPERTY VALUE is present in the table.
CMMVC6123E
No PROPERTY for TYPE NAME .
CMMVC6124E
No TYPE with PROPERTY VALUE
CMMVC6125E
No unique ID for TYPE NAME
CMMVC6126E
No TYPE with unique ID VALUE
CMMVC6127I
The SSH key IDENTIFIER for USER is already defined; the SSH key will not be restored
CMMVC6128W
DIRECTORY
CMMVC6129E
Host mapping objects have VDisk_UID values that are not consistent.
CMMVC6130W
Inter-cluster PROPERTY VALUE will not be restored.
CMMVC6131E
No location cluster information
CMMVC6132E
The object OBJECT of type TYPE has a property PROPERTY with an incorrect value INCORRECT_VALUE . The operation cannot proceed until the property has the correct value CORRECT_VALUE . Take administrative action to change the value and try again.
CMMVC6133E
Required TYPE property PROPERTY not found
CMMVC6134E
No argument for OPTION
CMMVC6135E
Argument VALUE for OPTION is not valid.
CMMVC6136W
No SSH key file FILENAME
CMMVC6137W
No SSH key file FILENAME; key not restored
CMMVC6138E
OPTION is required
CMMVC6139E
Incorrect XML tag nesting in FILENAME
CMMVC6140E
No default name for type TYPE
CMMVC6141E
The option OPTION does not support an argument.
CMMVC6142E
Existing OBJECT_TYPE OBJECT_NAME has a non-default name.
CMMVC6143E
The required configuration file FILENAME does not exist.
CMMVC6144W
The object with default name NAME has been restored as SUBSTITUTE_NAME .
CMMVC6145I
First use the COMMAND -prepare command.
CMMVC6146E
Problem parsing OBJECT_TYPE data: LINE
CMMVC6147W
TYPE NAME has a name beginning with PREFIX .
CMMVC6148E
Target cluster has NUMBER_OF_EXISTING_OBJECTS objects of type TYPE instead of NUMBER_OF_REQUIRED_OBJECTS .
CMMVC6149E
An action is required.
CMMVC6150E
The action ACTION is not valid.
CMMVC6151E
The option OPTION is not valid.
CMMVC6152E
Volume VDISK_NAME instance number INSTANCE_NUMBER is not valid.
CMMVC6153E
OBJECT not consistent with ACTION
CMMVC6154E
Required OBJECT_TYPE property PROPERTY_NAME has a null value.
CMMVC6155I
The command COMMAND processing has completed successfully.
CMMVC6156W
COMMAND processing completed with errors.
CMMVC6157E
Object is required.
CMMVC6164E
variable_error_message
CMMVC6165E
The target is not the original configuration node with a WWNN of WWNN_VALUE .
CMMVC6166E
The property PROPERTY of the object OBJECT has changed during svcconfig restore -execute.
CMMVC6169E
variable_error_message
CMMVC6171I
percentage% metadata compression
CMMVC6174I
Pausing for num_minutes minute(s) after node addition(s)
CMMVC6175I
Resuming after pause
CMMVC6180E
object_type [ object_id] not restored because [object_type | object_property] is missing
CMMVC6180W
object_type object_identifier not restored because object with property property_value is missing
CMMVC6181E
object_type object_id has property property_value; should be property_value_in_backup[; use -force to override | overridden ]
CMMVC6182E
object_type object_name with property property_value cannot be [restored | backed up].
CMMVC6186E
io_grp io_group_name restored with id new_id instead of old_id .
CMMVC6187W
Extraneous object_type object_name discovered
CMMVC6188W
VARIANT #1: Current Config inconsistent with backup object_type object_id does not exist in backupVARIANT #2: Current Config inconsistent with backup object_type object_id now has wrong_property wrong_value was correct_value
CMMVC6189W
E-mail server settings could not be restored due to missing configuration information
CMMVC6200E
Discovery did not complete within time limit - check that this is expected
CMMVC6201E
System layer must be changed to new_layer using chsystem before configuration can be restored
CMMVC6202E
This command can only be run by the superuser
CMMVC6203E
Enclosure serial number serial_no was found for enclosure ID enclosure_1 but it is already in use for enclosure ID enclosure_2
CMMVC6204E
Node node_name in backup is part of io_grp io_group_1, but the node is currently set to io_grp io_group_2
CMMVC6205E
Cannot retrieve VPD for node node_name because it is currently in service mode.
CMMVC6206E
Timeout exceeded waiting for object_type object_id to have expected property_name expected_value, actual actual_value.
CMMVC6207E
Cannot restore encryption as more USB devices are required. Required req_number_devices device(s) but found actual_number_devices device(s).
CMMVC6208E
The feature_id feature cannot be partially configured prior to a restore operation. The current state is current_state.
CMMVC6209E
Unable to determine system code version.
CMMVC6210E
Current Config inconsistent with backup because metadatavdisk with vdisk_id volume_id already exists.
CMMVC6211E
The system contains fewer USB ports than required to recover encryption automatically. Manually set up encryption and then run the -prepare command again.
CMMVC6212E
The host port mode did not change to transitional within the time limit.
CMMVC6213E
Active-active remote copy relationship relationship_id not added to consistency group group_id.
CMMVC6214E
The system could not be restored because the backup configuration contains a hybrid system of Storwize V7000 Gen1 and Storwize V7000 Gen2 nodes. Currently this cluster is not Storwize V7000 Gen1 compatible.
CMMVC6215W
Ensure that the system certificate is trusted by all key servers before running execute.
CMMVC6216E
Failed to generate key server certificates from the backup file.
CMMVC6218E
Before you continue with the T4 recovery, the key server username and password that are configured on the system must match username and password settings in the backup file of the configuration. Current settings: username_set:%1, password_set:%2. Backup settings: username_set:%3, password_set:%4
CMMVC6219E
The key server SSL certificates cannot be restored automatically from the backup. Manually set up key server encryption and then run the -prepare command again.
CMMVC6220E
The LDAP administrator password cannot be restored automatically from the backup. Manually set the password and then run the -prepare command again.
CMMVC6221W
The superuser cannot be locked automatically and must be manually locked.
CMMVC6222W
Multi-factor authentication for the superuser cannot be enabled automatically and must be manually enabled.
CMMVC6223E
Before you can continue with the restore, the multi-factor authentication credentials for IBM Security Verify must be entered manually to match the credentials of the previous configuration. The credentials can be obtained for your application from IBM Security Verify.
CMMVC6224E
Before you can continue with the restore, the single sign-on credentials must be entered manually to match the credentials of the previous configuration.
CMMVC6225W
The system certificate must be manually exported using the chsystemcert-export command and installed as a signer certificate in IBM Security Verify, using the id_alias from the lssystem command as the friendly name.
CMMVC6231E
The action failed as the audit table is full.
CMMVC6296E
One or more managed disks (MDisks) have failed validation tests. The first failing MDisk ID is MDISK_ID.
CMMVC6300E
The create failed because the source and target volumes are members of FlashCopy mappings that belong to different I/O groups.
CMMVC6301E
The create failed because the specified consistency group does not exist.
CMMVC6302E
The create failed because the resulting tree of FlashCopy mappings would exceed the upper limit.
CMMVC6303E
The create failed because the source and target volumes are the same.
CMMVC6304E
The create failed because the source volume does not exist.
CMMVC6305E
The create failed because the target volume does not exist.
CMMVC6306E
The create operation failed because the source volume is the member of a FlashCopy mapping whose grain size is different to that specified.
CMMVC6307E
The create operation failed because the target volume is the member of a FlashCopy mapping whose grain size is different to that specified.
CMMVC6308E
The create operation failed because the source volume is the member of a FlashCopy mapping whose IO group is different to that specified.
CMMVC6309E
The create operation failed because the target volume is the member of a FlashCopy mapping whose IO group is different to that specified.
CMMVC6310E
The modify failed because the specified FlashCopy mapping does not exist.
CMMVC6311E
The command failed because the source volume is the target of a FlashCopy mapping that is in the specified consistency group.
CMMVC6312E
The command failed because the target volume is the source of a FlashCopy mapping that is in the specified consistency group.
CMMVC6313E
The command failed because the specified background copy rate is invalid.
CMMVC6314E
The command failed because the specified cleaning rate is not valid.
CMMVC6315E
The command failed because the specified grain size is not valid.
CMMVC6319E
The command has failed because a combination of IPv4 and IPv6 parameters were entered.
CMMVC6320E
The command has failed because the IPv4 address is not valid.
CMMVC6321E
The command has failed because the IPv4 subnet mask is not valid.
CMMVC6322E
The command has failed because the IPv4 gateway address is not valid.
CMMVC6323E
The command has failed because the IPv6 address is not valid.
CMMVC6324E
The command has failed because the IPv6 prefix is not valid.
CMMVC6325E
The command has failed because the IPv6 gateway address is not valid.
CMMVC6326E
The command has failed because the IPv4 service state address is not valid.
CMMVC6327E
The command has failed because the IPv6 service state address is not valid.
CMMVC6328E
The command has failed because the console address is not valid.
CMMVC6329E
The command has failed because the IP address or DNS is not valid.
CMMVC6330E
The command has failed because an IPv6 address was specified and the cluster does not have an IPv6 address.
CMMVC6331E
The command has failed because an IPv4 address was specified and the cluster does not have an IPv4 address.
CMMVC6332E
The command has failed because an IPv6 email server address was specified and the cluster does not have an IPv6 address.
CMMVC6333E
The command has failed because an IPv4 email server address was specified and the cluster does not have an IPv4 address.
CMMVC6334E
The command failed as the email port number supplied is invalid.
CMMVC6335E
The command failed as the combination of parameters provided are either mutually incompatible or would leave the cluster without a functioning protocol stack.
CMMVC6336E
The volume copy was not created because the grain size must be 32, 64, 128 or 256.
CMMVC6337E
The action failed because the warning size must be a multiple of 512 bytes.
CMMVC6338E
The action failed because the warning size can not be larger than the virtual size.
CMMVC6339E
The volume copy was not created because the virtual size was not provided.
CMMVC6340E
The action failed because the value supplied for real size is not a multiple of 512 bytes.
CMMVC6341E
The action failed because the volume copy is not thin-provisioned or compressed.
CMMVC6342E
The volume copy was not shrunk because its real size cannot be less than its used size.
CMMVC6343E
The volume copy was not shrunk because its real size can not be negative.
CMMVC6344E
The repair operation cannot start because the volume copy is already being repaired.
CMMVC6345E
The repair operation cannot start because the volume copy was created using -import but the cluster could not recognize its format.
CMMVC6346E
The repair operation cannot start because the thin-provisioned volume copy was created using -import with a real size that is too small.
CMMVC6347E
The specific update package cannot be installed on this hardware level.
CMMVC6348E
The command failed as there was not enough information provided to process successfully.
CMMVC6349E
The command was not initiated because the volume cache has been lost and you have not specified the -force option.
CMMVC6350E
The command failed because there is insufficient mirror bitmap space.
CMMVC6351E
The command failed because the volume is not mirrored.
CMMVC6352E
The command failed because the number of copies of this volume would exceed the limit.
CMMVC6353E
The command failed because the copy specified does not exist.
CMMVC6354E
The command failed because a copy is not synchronized.
CMMVC6355E
The command failed because an image mode copy is not synchronized.
CMMVC6356E
The command failed because a copy is not synchronized and -force was not specified.
CMMVC6357E
The command failed because the copy specified is not synchronized and -force was not specified.
CMMVC6358E
The command failed because the copy specified is the only synchronized copy or in fast formatting state.
CMMVC6359E
The command failed because there are insufficient online synchronized copies.
CMMVC6363E
The command failed because the Logical Block Address (LBA) specified is invalid for this volume.
CMMVC6364E
The command failed because the logical block address (LBA) requested is too large for the disk.
CMMVC6365E
The command timed out.
CMMVC6366E
One or more nodes in the cluster has hardware that is not supported by the new code.
CMMVC6367E
A remote cluster is running software that is incompatible with the new software package.
CMMVC6368E
The new code might be incompatible with the remote cluster.
CMMVC6369W
The FlashCopy storage capacity that the cluster is using is approaching the FlashCopy storage capacity that is licensed.
CMMVC6370W
The Remote Copy storage capacity that the cluster is using is approaching the Remote Copy storage capacity that is licensed.
CMMVC6372W
The virtualized storage capacity that the cluster is using is approaching the virtualized storage capacity that is licensed.
CMMVC6373W
The virtualized storage capacity that the cluster is using exceeds the virtualized storage capacity that is licensed.
CMMVC6374W
The FlashCopy storage capacity that the cluster is using exceeds the FlashCopy storage capacity that is licensed.
CMMVC6375W
The Remote Copy storage capacity that the cluster is using exceeds the Remote Copy storage capacity that is licensed.
CMMVC6394E
The command failed because an attempt to make the volume cache empty took too long.
CMMVC6399E
The command failed because there is not enough memory available for reservation.
CMMVC6400E
The command failed because a specified managed disk (MDisk) is already in use.
CMMVC6401E
The command failed because one or more of the specified managed disks (MDisks) that you have specified are not in the required storage pool.
CMMVC6402E
The command failed because the managed disk (MDisk) is not in the required storage pool.
CMMVC6403E
The command failed because the target managed disk (MDisk) is not in the required storage pool.
CMMVC6404E
The command failed because the source and target storage pools must be different.
CMMVC6405E
The command failed because the target copy was not specified.
CMMVC6406E
The command failed because the specified storage pool does not exist.
CMMVC6407E
The command failed because the storage pool is invalid.
CMMVC6408E
The command failed because too few storage pools were specified.
CMMVC6409E
The command failed because too many storage pools were specified.
CMMVC6410E
The command failed because too few managed disks (MDisks) were specified.
CMMVC6411E
The command failed because too many managed disks (MDisks) were specified.
CMMVC6412E
The command failed because the storage pool extent size is above maximum permitted size.
CMMVC6413E
The command failed because the managed disk (MDisk) is invalid.
CMMVC6414E
The command failed because the managed disk (MDisk) is currently being migrated.
CMMVC6415E
The command failed because the storage pool warning threshold is too low.
CMMVC6416E
The command failed because the storage pool warning threshold is too high.
CMMVC6417E
The command failed because the storage pool warning threshold is invalid.
CMMVC6418E
The command failed because the volume is in the process of being resized.
CMMVC6419E
The command failed because one or more of the specified managed disks (MDisks) are in the process of being deleted.
CMMVC6421E
The specified size exceeds the maximum permitted for this feature.
CMMVC6422E
The specified size is too big. Total size of memory across all features exceeds maximum permitted.
CMMVC6423E
The Send Inventory email operation failed because email is not started.
CMMVC6424E
The Send Inventory email operation failed because there are no inventory email users.
CMMVC6425E
The action failed because the maximum number of objects has been reached.
CMMVC6426E
The command failed because a specified managed disk (MDisk) is already in use.
CMMVC6427E
The command failed because one or more of the specified managed disks (MDisks) are not in the required storage pool.
CMMVC6428E
The command failed because the source managed disk (MDisk) is not in the required storage pool.
CMMVC6429E
The command failed because the target managed disk (MDisk) is not in the required storage pool.
CMMVC6430E
The command failed because the target and source storage pools must be different.
CMMVC6431E
The command failed because the target copy was not specified.
CMMVC6432E
The command failed because the specified storage pool does not exist.
CMMVC6433E
The command failed because the storage pool is invalid.
CMMVC6434E
The command failed because too few storage pools were specified.
CMMVC6435E
The command failed because too many storage pools were specified.
CMMVC6436E
The command failed because too few managed disks (MDisks) were specified.
CMMVC6437E
The command failed because too many managed disks (MDisks) were specified.
CMMVC6438E
The command failed because the storage pool extent size is above maximum permitted size.
CMMVC6439E
The command failed because the managed disk (MDisk) is invalid.
CMMVC6440E
The command failed because the managed disk (MDisk) is currently being migrated.
CMMVC6441E
The command failed because the storage pool warning threshold is too low.
CMMVC6442E
The command failed because the storage pool warning threshold is too high.
CMMVC6443E
The command failed because the storage pool warning threshold is invalid.
CMMVC6444E
The command failed because the volume is in the process of being resized.
CMMVC6445E
The command failed because one or more of the specified managed disks (MDisks) are in the process of being deleted.
CMMVC6446E
The command failed because the storage pools have different extent sizes.
CMMVC6447E
The command failed because the volume is currently being migrated.
CMMVC6448E
Deleting this node will cause data loss for resources associated with the I/O group of this node.
CMMVC6449E
The operation was not performed because the partnership owns Global or Metro Mirror relationships or consistency groups.
CMMVC6450W
A FlashCopy mapping was created but physical_flash is not enabled.
CMMVC6451W
A Global Mirror or Metro Mirror relationship was created but physical_remote is not enabled.
CMMVC6452W
You are using the physical disk license scheme but the values for physical_flash and physical_remote are not set.
CMMVC6453W
You have disabled the physical disk license scheme but the capacity license scheme is not set.
CMMVC6454E
The command failed because the physical disk license scheme is not enabled.
CMMVC6455E
The command failed because a capacity license scheme parameter was specified but the physical disk license scheme is enabled.
CMMVC6456E
The command failed because a physical disk license scheme parameter was specified but the capacity license scheme is enabled.
CMMVC6457E
One or more quorum disks are on the specified controller.
CMMVC6458E
The specified controller cannot support quorum disks.
CMMVC6459E
The mkrcrelationship command failed because the same volume was specified as the master and auxiliary volume.
CMMVC6460E
The command failed because the migration source is offline.
CMMVC6461E
The command failed because starting the migration will result in volumes going offline in the source storage pool.
CMMVC6462E
The command failed because starting the migration will result in volumes going offline because the target storage pool is offline.
CMMVC6463E
The command failed because Starting the migration will result in volumes going offline because a target MDisk is offline.
CMMVC6464E
The Create FlashCopy mapping task cannot be initiated because the size of the source volume is being changed by a previously submitted task.
CMMVC6465E
The Create FlashCopy mapping task cannot be initiated because the size of the target volume is being changed by a previously submitted task.
CMMVC6466E
The Create FlashCopy mapping task cannot be initiated because an identical map already exists.
CMMVC6467E
The Create FlashCopy mapping task cannot be initiated because a FlashCopy map with the same target volume already exists in the consistency group.
CMMVC6468E
The Start or Prepare FlashCopy mapping task cannot be initiated because the target volume is the source of a different FlashCopy map that is being restored.
CMMVC6469E
The Split stop FlashCopy map task cannot be initiated because the mapping is either being restored or is not in the copy complete state.
CMMVC6470E
The Start or Prepare FlashCopy mapping task cannot be initiated because the target volume is being used by a different FlashCopy map.
CMMVC6471E
The Create cluster partnership task cannot be initiated because a cluster in the existing partnership has a downlevel code version that does not support this configuration.
CMMVC6472E
The Create cluster partnership task cannot be initiated because the remote cluster with which you are attempting to create a partnership has a downlevel code version that does not support this configuration.
CMMVC6473E
The partnership task cannot be initiated because the supported maximum number of accessible remote clusters would be exceeded.
CMMVC6474E
The Create partnership task cannot be initiated because there is a Global Mirror or Metro Mirror relationship or consistency group that has a deleted partnership.
CMMVC6475E
The Add relationship to group task cannot be initiated because the master cluster of the relationship that you are attempting to add to the group is the auxiliary cluster of the group, and the auxiliary cluster of the relationship that you are attempting to add to the group is the master cluster of the group.
CMMVC6478E
The Enable remote authentication service task cannot be initiated because the server settings are not configured.
CMMVC6479E
The task cannot be initiated because the user group table is full.
CMMVC6480E
The task cannot be initiated because the user group that you have specified is not defined.
CMMVC6481E
The Modify user group task cannot be initiated because you have specified a default user group.
CMMVC6482E
The Delete user group task cannot be initiated because you have specified a default user group.
CMMVC6483E
The task cannot be initiated because the user group name that you have specified already exists.
CMMVC6484E
The task cannot be initiated because the role that you have specified is not supported.
CMMVC6485E
The Delete user group task has failed because there is at least one user that is defined as a member of the group, and you did not specify the -force parameter.
CMMVC6486E
The task cannot be initiated because the user table is full.
CMMVC6487E
The task cannot be initiated because the user name that you have specified already exists.
CMMVC6488E
The task cannot be initiated because you have specified a user group ID that is not correct.
CMMVC6489E
The task cannot be initiated because you have specified more than one password.
CMMVC6490E
The task cannot be initiated because you have specified both a user group and the use of the remote authentication service.
CMMVC6491E
The task cannot be initiated because an SSH key and password were not specified for the remote authentication service.
CMMVC6492E
The task cannot be initiated because you have specified a local user but you have not specified a user group.
CMMVC6493E
The task cannot be initiated because the user that you have specified is not defined.
CMMVC6494E
The task cannot be initiated because you cannot remove a default user.
CMMVC6495E
The task cannot be initiated because the user superuser must be a local user.
CMMVC6496E
The task cannot be initiated because you cannot remove the superuser password.
CMMVC6497E
The task cannot be initiated because the user that you have specified does not have a password defined.
CMMVC6498E
The task cannot be initiated because the user that you have specified does not have an SSH key defined.
CMMVC6499E
The task has failed because the SSH key that you have specified is already defined for another user.
CMMVC6500E
The action failed because the source and destination volumes are the same.
CMMVC6501E
The action failed because the node hardware is incompatible with the current I/O group member.
CMMVC6502E
The FlashCopy mapping was not prepared because preparing consistency group 0 is not a valid operation.
CMMVC6503E
The FlashCopy mapping or consistency group was not stopped because stopping consistency group 0 is not a valid operation.
CMMVC6504E
The task cannot be initiated because the SSH key file that you have specified does not contain a valid SSH key.
CMMVC6505E
The task has failed because an error has occurred while communicating with the authentication service.
CMMVC6506E
The task has failed because a timeout has occurred while communicating with the authentication service.
CMMVC6507E
The task has failed because the authentication service reports an incorrect user name or password.
CMMVC6508E
The task has failed because the authentication service reports that the authentication token has expired.
CMMVC6510E
The task has failed because the user name or password is not correct.
CMMVC6511E
The task has failed because the cluster is not configured correctly to use the authentication service.
CMMVC6512E
The task has failed because you cannot both create a new quorum disk and set that new disk to active using the same command.
CMMVC6513E
The task has failed because you cannot activate a quorum disk until all of the quorum disks have been initialized.
CMMVC6514E
The task has failed because the disk that you have selected to activate is not online.
CMMVC6515E
The task has failed because at least one quorum disk is in the Excluded state.
CMMVC6516E
The command has failed because an IPv4 cluster address cannot be removed while remote IPv4 services are configured.
CMMVC6517E
The command has failed because an IPv6 cluster address cannot be removed while remote IPv6 services are configured.
CMMVC6518E
The task has failed because no roles are defined for the current user on the cluster.
CMMVC6519E
The task has failed because you cannot change the user group of the 'superuser' account to anything other than 'SecurityAdmin'.
CMMVC6520E
You cannot use this task to modify the properties of the current user because those properties are only defined by an authentication service.
CMMVC6521E
The task cannot be initiated because it would have resulted in a user account definition for a local user that specifies neither a password, an SSH key nor a certuid.
CMMVC6522E
Authorization has failed.
CMMVC6523E
The URL that you have entered is not valid.
CMMVC6524E
The name that you have entered is not valid. The name cannot begin or end with a space character, and the name cannot contain any of the following characters: * : , \' %
CMMVC6525E
The password that you have entered is not valid. The password cannot begin or end with a space character.
CMMVC6526E
The Create Volume task cannot be initiated because the number of copies that you have requested is not equal to the number of unique storage pools that you have specified.
CMMVC6527E
The name that you have entered is not valid. The name can contain letters, numbers, spaces, periods, dashes, and underscores. The name must begin with a letter or an underscore. The name must not begin or end with a space.
CMMVC6528E
The command cannot be initiated because the MDisk mode is not set to Array.
CMMVC6529E
The command cannot be initiated because the maximum supported number of MDisks already exists.
CMMVC6530E
The command cannot be initiated because the maximum supported number of arrays already exists.
CMMVC6532E
The command cannot be initiated because there is insufficient free memory that is available to the I/O group.
CMMVC6533E
The command cannot be initiated because the specified array member does not exist in the selected array.
CMMVC6534E
The command cannot be initiated because the drive that you have specified does not exist.
CMMVC6535E
The command cannot be initiated because you have specified an incorrect number of drives to configure an array using the RAID geometry that you have specified.
CMMVC6536E
The command cannot be initiated because you have specified more drives than the specified RAID geometry permits.
CMMVC6537E
The command cannot be initiated because the drive that you have specified has a Use property that is not supported for the task.
CMMVC6538E
The command cannot be initiated because at least one of the drives that you have specified has a Use property that is not Candidate.
CMMVC6539E
The command cannot be initiated because the array does not have sufficient redundancy.
CMMVC6540E
The task cannot be initiated because the thin-provisioned grain size is too small to accommodate the provisioned capacity that you have requested for the volume.
CMMVC6541E
The task cannot be initiated because the provisioned capacity that you have requested for the volume is larger than the maximum capacity that is supported for the extent size.
CMMVC6542E
The remote authentication task has failed.
CMMVC6543E
The task cannot be initiated because you can only specify a direct-attached managed drive when you submit the task.
CMMVC6544E
The task cannot be initiated at this time because the direct-attached managed drive that you have specified is too busy. Resubmit the task when the drive is less busy.
CMMVC6545E
The Apply Drive Software task has failed to access the software download image.
CMMVC6546E
A drive error was detected during the Apply Drive Software task.
CMMVC6547W
The Download FPGA firmware task has been initiated. The MDisk remains Offline while the task is in progress. Do not remove power from the drive or node while the task in is progress.
CMMVC6548E
The FPGA firmware cannot be applied because the drive has a use other than candidate.
CMMVC6549E
The Authentication task has failed because the authentication service URL that you have specified is not a valid URL.
CMMVC6550E
The Authentication task has failed because the network address that is specified in the authentication service URL cannot be resolved.
CMMVC6551E
The Authentication task has failed because the combination of user name and password that is defined in the cluster for authorization by the authentication service is not defined on the authentication service.
CMMVC6552E
The Authentication task has failed because an SSL connection could not be established with the authentication service.
CMMVC6553E
The task cannot be initiated because at least one quorum disk is not in the correct state.
CMMVC6554E
The Authentication task has failed because the user name that was received from the authentication service is not a valid cluster user name.
CMMVC6555E
The Authentication task has failed because the authentication service either sent an incorrect response, or it sent a response that indicates that the authentication request has failed for a reason other than incorrect authentication credentials.
CMMVC6556E
The task cannot be initiated because an error has occurred while attempting to read a file.
CMMVC6557E
The task cannot be initiated because the file that you have specified is too large.
CMMVC6558E
The command cannot be initiated because it might cause volumes to go Offline. Refer to the cluster Command-Line Interface (CLI) command help for this command.
CMMVC6559E
The Add or Change email user command has failed because you have specified a user type of 'support' and you have specified either the -warning or -info parameter value as 'on'.
CMMVC6560E
The command has failed because the specified IP address is already in use by the cluster.
CMMVC6561E
The set quorum active task has failed because either another set quorum active task is in progress or the selected disk cannot be set as the active quorum disk.
CMMVC6562E
The requested size exceeds the maximum supported value.
CMMVC6563E
The command has failed because a user that you have specified is not configured to receive email notifications.
CMMVC6564E
You cannot make this user a remote user because the password type is not valid for a remote user.
CMMVC6565E
The command has failed because the specified node is not online.
CMMVC6566E
The command cannot be submitted because specifying the -failover parameter requires that you also specify either the -name, -iscsialias or -noiscsialias parameter.
CMMVC6567E
The Apply Drive Software task cannot be initiated because no download images were found in the package file.
CMMVC6568E
The Apply Drive Software task cannot be initiated because for at least one of the specified drives, the specified file does not contain an image for that drive's technology.
CMMVC6569E
The Apply Drive Software task has failed because no download images were found in the package file of this software type.
CMMVC6570E
The command was not initiated because the cache mode of the volume is already in the state that you had requested.
CMMVC6571E
The command has failed because the I/O group that manages the volume that you specified was offline when you submitted the command. You can use the -force flag to force the operation, which might result in the loss of cache data.
CMMVC6572E
The command has failed because the I/O group that manages the volume that you specified is not stable.
CMMVC6573E
The command has failed because the volume that you specified is a source or target of a FlashCopy mapping that is in the prepared state.
CMMVC6574E
The command has failed because the volume that you specified is a source or target of a FlashCopy mapping that is in the suspended state.
CMMVC6575E
The command has failed because the volume that you specified is a source or target of a FlashCopy mapping that is in the preparing state.
CMMVC6576E
The command has failed because the volume that you specified is a source or target of a FlashCopy mapping that is in the stopping state.
CMMVC6577E
The command has failed because the volume that you specified is a source or target of a FlashCopy mapping that is in the copying state.
CMMVC6578E
The command has failed because the iSCSI name is already assigned or is not valid.
CMMVC6579E
The command cannot be initiated because the cluster Ethernet port 1 must always be fully configured in either the IPv4 or IPv6 format.
CMMVC6580E
The command cannot be initiated because the iSCSI alias that you specified contained either leading or trailing space characters.
CMMVC6581E
The command has failed because the maximum number of allowed iSCSI qualified names (IQNs) has been reached, or the IQN is already assigned or is not valid.
CMMVC6582E
The task has failed because the host that you specified is not mapped to an I/O group.
CMMVC6583E
The command has failed because the name that you specified contains a character that is not supported for a node or cluster name.
CMMVC6584E
The command cannot be initiated because it would unconfigure the remote authentication service while the service is enabled.
CMMVC6585E
The command cannot be initiated because the array that you have specified has a geometry of RAID 0, which is not a redundant geometry.
CMMVC6586E
The command cannot be initiated because the action would cause array data loss due to the unsynchronized state of the array.
CMMVC6587E
The command did not complete because I/O for the array was not quiesced within the allotted time period.
CMMVC6588E
The command cannot be initiated because a drive that you have specified has a capacity that is smaller than the minimum capacity that is required for the array that you have specified.
CMMVC6589E
The command was not initiated because the drive that you have specified does not sufficiently match the array member goals and you did not specify the -balanced parameter.
CMMVC6590E
The command cannot be initiated because you did not specify the -allowdegraded parameter and the associated array member has insufficient spare protection.
CMMVC6591E
The command cannot be initiated because the specified sequence number does not match the sequence number of any events in the event log.
CMMVC6592E
The command cannot be initiated because at least one parameter that was specified is not supported when submitting a command to view the details of an event log entry.
CMMVC6593E
The command cannot be initiated because the event log entry has a status that is not supported for the command.
CMMVC6594E
The command cannot be initiated because a drive was specified twice in the drive list.
CMMVC6595E
The command cannot be initiated because a drive that you have specified has a technology type that is not supported for the command.
CMMVC6596E
The command has failed because you have specified an I/O group that does not exist.
CMMVC6597E
The command has failed because the email settings are not configured.
CMMVC6608E
The command cannot be initiated because Easy Tier is active on the volume copy.
CMMVC6609E
The command cannot be initiated because the size of the Mdisk is smaller than the extent size of the storage pool.
CMMVC6610E
The update cannot start because one or more I/O groups are in maintenance mode.
CMMVC6611E
The command has failed because the specified enclosure is offline.
CMMVC6612E
The command has failed because of a hardware error.
CMMVC6613E
The command has failed because the specified enclosure type is not supported.
CMMVC6614E
The command has failed because the specified canister is offline.
CMMVC6615E
The command cannot be initiated because nodes from this enclosure cannot be added to the specified I/O group, or another enclosure is in the process of being added.
CMMVC6616E
All available quorum disks are dependent on the MDisks that you have specified.
CMMVC6617E
All available quorum disks are dependent on the drives that you have specified.
CMMVC6618E
All available quorum disks are dependent on the enclosure that you have specified.
CMMVC6619E
All available quorum disks are dependent on the canister that you have specified.
CMMVC6620E
The command cannot be initiated because the drives that you have specified are in different I/O groups.
CMMVC6621E
The command cannot be initiated because the array member that you have specified already exists.
CMMVC6622E
The command cannot be initiated because the drive has failed validation tests.
CMMVC6623E
The command cannot be initiated because the drive validation test has timed out.
CMMVC6624E
The command cannot be initiated because the drive is not in an appropriate state to perform the task.
CMMVC6625E
The command cannot be initiated because a task is in progress on the drive.
CMMVC6626E
The task was not initiated because a command was rejected by the drive that you have specified.
CMMVC6627E
The enclosure that you have specified cannot be changed to managed mode because of a SAS configuration problem that is described in the event log.
CMMVC6628E
The enclosure that you have specified cannot be changed to unmanaged mode because one or more drives are in use.
CMMVC6630E
A drive dump was not created because a command was rejected by the drive that you have specified.
CMMVC6631E
The task was not completed because the drive that you have specified was unavailable.
CMMVC6917E
Authorization failed.
CMMVC6953E
The action cannot be completed because volumes are dependent on the specified mdisk. Force is required.
CMMVC6972E
The command cannot be initiated because the maximum number of extents for an MDisk would be exceeded.
CMMVC6974E
The command cannot be initiated because there are too many bad blocks on the MDisk.
CMMVC6976E
The command cannot be initiated because the MDisk has an array parity rebuild ongoing.
CMMVC6977E
The command cannot be initiated because the MDisk has an array initialization ongoing.
CMMVC6978E
The command cannot be initiated because the MDisk has an array member rebuild ongoing.
CMMVC6979E
The command cannot be initiated because the MDisk has an array member exchange ongoing.
CMMVC6988E
The command cannot be initiated because the maximum number of iSCSI qualified names (IQNs) for the cluster has been reached.
CMMVC6998E
The maximum number of iSCSI qualified names (IQNs) plus WWPNs for the cluster is already configured.
CMMVC6999E
The command cannot be initiated because the maximum number of iSCSI qualified names (IQNs) for the host has been reached.
CMMVC7003E
The command cannot be initiated because the power supply unit (PSU) that you have specified is offline.
CMMVC7004E
The command cannot be initiated because the node canister port that you have specified does not exist.
CMMVC7005E
The command cannot be initiated because enclosures do not exist for the I/O group that you have specified.
CMMVC7006E
The command failed because no enclosures are viewable through the specified canister port.
CMMVC7007E
The task cannot be initiated because the enclosure that contains the specified drive is not supported.
CMMVC7008E
The task cannot be initiated because the enclosure containing the specified drive is unmanaged and cannot be managed because of an enclosure cabling problem.
CMMVC7009E
The task cannot be initiated because the maximum number of managed enclosures has been reached.
CMMVC7010E
The command cannot be initiated because the MDisk mode is set to Array.
CMMVC7011E
The array cannot be created because no quorum disks are currently configured.
CMMVC7012E
The command cannot be initiated because the action will cause the array to go offline.
CMMVC7013E
The command cannot be initiated because a drive within the enclosure that you have specified is configured as a spare or array member.
CMMVC7014E
The command cannot be initiated because one or more of the drives are not supported for this RAID level.
CMMVC7015E
The command cannot be initiated because one or more of the drives are located in the wrong node.
CMMVC7016E
Authorization has failed because the private key is not valid for the user name that you have specified.
CMMVC7017E
Login has failed because the maximum number of concurrent CLI sessions has been reached.
CMMVC7018E
The command failed because the requested volume size is too large.
CMMVC7019E
The command failed because the volume size is not a multiple of 512 bytes.
CMMVC7020E
The command failed because the maximum number of volumes for this I/O group already exist.
CMMVC7021E
The command failed because the maximum number of volume copies already exist.
CMMVC7022E
The command failed because NTP is active.
CMMVC7023E
The command failed because the requested node name is in use as the failover name of another node.
CMMVC7024E
The command failed because the maximum number of file systems already exist.
CMMVC7025E
The command failed because the volume is associated with a file system and cannot be removed under your current user role.
CMMVC7026E
The command failed because volumes exist in the file system.
CMMVC7027E
The command failed because the requested action is not permitted on a volume that is in a file system.
CMMVC7028E
The task cannot be completed because the FlashCopy target volume that you have specified is in a Metro Mirror or Global Mirror relationship, and the I/O group of the volume is different than that of the proposed FlashCopy mapping.
CMMVC7029E
The task cannot be completed because one or more of the target volumes of the FlashCopy mappings is the primary of a mirroring Metro Mirror or Global Mirror relationship.
CMMVC7030E
The task cannot be completed because the target volume of the FlashCopy mapping is the primary of a mirroring Metro Mirror or Global Mirror relationship.
CMMVC7031E
The task cannot be completed because the FlashCopy mapping target volume is a secondary in a Metro Mirror or Global Mirror relationship, or is the primary in an active relationship.
CMMVC7032E
The task cannot be completed because one or more of the target volumes of the FlashCopy mappings is either a secondary in a Metro Mirror or Global Mirror relationship or the primary of an active relationship.
CMMVC7033E
The task failed because the current hardware configuration is not valid.
CMMVC7036E
The action failed because quorum is not permitted on the drive that you have specified.
CMMVC7037E
The action failed because the drive cannot be found.
CMMVC7038E
The action failed because the system was unable to initialize the quorum disk.
CMMVC7039E
The action failed because the specified drive is not online.
CMMVC7040E
The action failed because the specified MDisk is not online.
CMMVC7041E
The action failed because a better quorum candidate is available for use as quorum and override has not been enabled.
CMMVC7042E
The action failed because the -override yes parameter was used without a specified drive or MDisk.
CMMVC7043E
The action failed because the required extents could not be allocated.
CMMVC7044E
The action failed because the specified drive is either degraded or excluded.
CMMVC7045E
The action failed because the specified MDisk is either degraded or excluded.
CMMVC7046E
The action failed because the -rsize option must be set to auto.
CMMVC7047E
The action failed because the validate parameter is not supported for compressed volumes.
CMMVC7048E
The action failed because the compressed volume copies are not all corrupted.
CMMVC7049E
The command failed because volumes are obstructing resources required by the compression function.
CMMVC7050E
The command failed because at least one node in the I/O group does not support compressed volumes.
CMMVC7051E
The command failed because the I/O group contains compressed volumes. The node being added does not support compressed volumes.
CMMVC7052E
The nested group search parameter is not valid for the target LDAP server type.
CMMVC7053E
The task cannot be initiated because the nested group search value (server) is not valid for the target LDAP server type.
CMMVC7054E
The task cannot be initiated because the user name or password of the LDAP administrator was not specified.
CMMVC7055E
The task cannot be initiated because the specified IP address, port, and base distinguished name (DN) are already configured on an LDAP server.
CMMVC7056E
The task cannot be initiated because the number of LDAP servers has reached the supported maximum.
CMMVC7057E
The task cannot be initiated because the specified LDAP server is the only configured LDAP server.
CMMVC7058E
The task cannot be initiated because no LDAP server is configured.
CMMVC7059E
The task cannot be initiated because some remote users are not configured with an SSH key and password for the specified remote authentication service.
CMMVC7060E
The task cannot be initiated because the parameters that you have specified are not valid for the LDAP authentication service.
CMMVC7061E
The task cannot be initiated because the LDAP administrator user name that you have specified is not valid.
CMMVC7062E
The task cannot be initiated because you have specified an LDAP attribute that is not valid.
CMMVC7063E
The task cannot be initiated because the Distinguished Name that you have specified is not valid.
CMMVC7064E
User authentication failed because one or more LDAP servers could not be contacted.
CMMVC7065E
User authentication failed because a timeout occurred while communicating with one or more LDAP servers.
CMMVC7066E
User authentication failed because an SSL connection could not be established with one or more LDAP servers.
CMMVC7067E
User authentication failed because one or more LDAP servers rejected an anonymous bind attempt.
CMMVC7068E
User authentication failed because one or more LDAP servers rejected an attempt to bind with the LDAP administrator credentials configured on the cluster.
CMMVC7069E
User authentication failed because one or more LDAP servers report an incorrect user name or password.
CMMVC7070E
User authentication failed because the LDAP user attribute is incorrectly configured on one or more LDAP servers.
CMMVC7071E
User authentication failed because the LDAP group attribute is incorrectly configured on one or more LDAP servers.
CMMVC7072E
User authentication failed because the LDAP group attribute is not in a valid format on one or more LDAP servers.
CMMVC7073E
User authentication failed because the LDAP audit log attribute is not configured correctly on one or more LDAP servers.
CMMVC7074E
The task cannot be initiated because the user could not be found on any of the configured LDAP servers.
CMMVC7075I
The LDAP task completed successfully.
CMMVC7076E
VOLUME cannot be created with VALUE without VALUE.
CMMVC7077E
The command failed because adding a thin provisioned copy to a file system volume is not allowed.
CMMVC7078E
The command cannot be initiated because adding a copy to the storage pool of file system volumes is not allowed.
CMMVC7079E
The command failed because a volume copy must be different when added to a file system volume.
CMMVC7080W
The compressed storage used by the cluster is approaching the capacity that is licensed.
CMMVC7081W
The compressed storage used by the cluster has exceeded the capacity that is licensed.
CMMVC7082W
The number of control enclosures with compressed volumes exceeds the number that are licensed.
CMMVC7083E
The specified number of control enclosures is not valid.
CMMVC7084E
The action failed because the command is not permitted for compressed volumes.
CMMVC7102E
The action could not be performed because one or more of the requested secondary volume is the target of an active FlashCopy mapping.
CMMVC7143E
The command cannot be initiated because nodes from another cluster are visible.
CMMVC7144E
The command cannot be initiated because it is not supported by this hardware type.
CMMVC7145E
The command cannot be initiated because one or more partnerships are defined.
CMMVC7146E
The command cannot be initiated because a host object is associated with SAN Volume Controller ports.
CMMVC7147E
The command cannot be initiated because one or more MDisks are provided by a storage system that does not support the system layer changing.
CMMVC7154E
The task cannot be completed because the specified FlashCopy mapping is controlled by a Metro Mirror or Global Mirror relationship.
CMMVC7155E
The Create FlashCopy mapping task cannot be initiated because the source or target volume is being used as a change volume for a Metro Mirror or Global Mirror relationship.
CMMVC7156E
The change volume could not be associated because it is already a source or target volume in an existing FlashCopy mapping.
CMMVC7157E
The change volume could not be associated because the Metro Mirror or Global Mirror relationship has a volume on this cluster that is the target of a FlashCopy mapping in a different I/O group.
CMMVC7158E
The change volume could not be associated because the Metro Mirror or Global Mirror relationship has a volume on this cluster that is already involved in the maximum number of FlashCopy mappings.
CMMVC7159E
The change volume could not be associated because the relationship has a volume on this cluster that is in an I/O group with no online nodes or because there are unrecovered FlashCopy mappings in the I/O group.
CMMVC7160E
The change volume could not be associated because the I/O group has insufficient free bitmap space.
CMMVC7161E
The change volume could not be associated because the master change volume can only be configured from the master cluster, and the auxiliary change volume from the auxiliary cluster. The change volume must be configured from the remote cluster.
CMMVC7162E
The change volume could not be associated because one is already configured for the specified Metro Mirror or Global Mirror relationship.
CMMVC7163E
The change volume could not be associated because it is already involved in a Metro Mirror or Global Mirror relationship.
CMMVC7164E
The change volume could not be associated because its size is different from those in the Metro Mirror or Global Mirror relationship.
CMMVC7165E
The change volume could not be disassociated because the Metro Mirror or Global Mirror relationship does not have one configured.
CMMVC7166E
The change volume could not be disassociated because it is currently in use by the Metro Mirror or Global Mirror relationship.
CMMVC7167E
The change volume could not be associated because it is mapped to a host.
CMMVC7168E
The host mapping was not created because the volume is a change volume for a Metro Mirror or Global Mirror relationship.
CMMVC7169E
The Remote Copy relationship could not be deleted because this would corrupt the secondary volume.
CMMVC7170E
The Remote Copy relationship could not be created because the specified master volume is already a change volume for a different relationship.
CMMVC7171E
The Remote Copy relationship could not be created because the specified auxiliary volume is already a change volume for a different relationship.
CMMVC7172E
Enabling access to the secondary volume of the Remote Copy relationship could not be completed in a reasonable time.
CMMVC7173E
Enabling access to the secondary volumes of the Remote Copy consistency group could not be completed in a reasonable time.
CMMVC7174E
The task cannot be completed because the other cluster is running a software version that is not recent enough.
CMMVC7175E
Enabling access to the secondary volumes of the Remote Copy consistency group could not be completed because the relationships in the group are not mutually consistent.
CMMVC7176E
The Remote Copy relationship could not be added to the consistency group because the cycling modes do not match.
CMMVC7177E
The Remote Copy relationship could not be added to the consistency group because the cycling periods do not match.
CMMVC7178E
The Remote Copy relationship could not be started in a reasonable time. It is now stopped.
CMMVC7179E
The Remote Copy consistency group could not be started in a reasonable time. It is now stopped.
CMMVC7180E
The Remote Copy relationship could not be started because no master change volume is defined.
CMMVC7181E
The Remote Copy relationship could not be started because no auxiliary change volume is defined.
CMMVC7182E
The Remote Copy consistency group could not be started because no master change volume is defined.
CMMVC7183E
The Remote Copy consistency group could not be started because no auxiliary change volume is defined.
CMMVC7184E
The task cannot be completed as the Remote Copy object is not stopped.
CMMVC7185E
The change volume could not be associated because the Metro Mirror or Global Mirror relationship has a volume on this cluster that is in a different I/O group.
CMMVC7186E
The Remote Copy relationship was not created because the master VDisk is owned and has restricted use.
CMMVC7187E
The Remote Copy relationship was not created because the auxiliary VDisk is owned and has restricted use.
CMMVC7188E
The command failed because the master volume is in a file system.
CMMVC7189E
The change volume could not be associated because it is in a file system.
CMMVC7203E
The command failed because the hardware configuration of the local cluster is not compatible with the code of a partnered cluster.
CMMVC7204E
Cannot remove the last I/O group from the volume access set.
CMMVC7205E
The command failed because it is not supported.
CMMVC7206E
The command failed because a parameter is not supported.
CMMVC7210E
The command failed because it would create too many compressed volume copies that are contained within regular pools in the I/O group.
CMMVC7211E
The command failed because it is not supported for image-mode MDisks.
CMMVC7218E
The task cannot be initiated because an invalid license key was specified.
CMMVC7219E
The task cannot be initiated because an invalid function id was specified.
CMMVC7220E
The task cannot be initiated because an invalid function license key file path was specified.
CMMVC7221E
The command has failed because the machine signature in the license does not match this machine.
CMMVC7222E
The command has failed because the function specified by the license key has not been recognized.
CMMVC7223E
The command has failed because the trial specified has previously been used.
CMMVC7224E
The command has failed because the specified function is currently in use.
CMMVC7226E
The command has failed because the license key file specified is not in a supported format
CMMVC7233W
Easy Tier® is active without a license for each enclosure.
CMMVC7234W
FlashCopy® is enabled without a license for each enclosure.
CMMVC7235W
Remote copy is enabled without a license for each enclosure.
CMMVC7236W
Multiple functions are enabled without a license for each enclosure.
CMMVC7238E
The cycling mode may only be changed for Global Mirror relationships or groups.
CMMVC7239E
The node could not be added because the number of configured hosts exceeds the supported limit for the node type being added.
CMMVC7240E
The node could not be added because at least one host has more volumes mapped than is supported for the node type being added.
CMMVC7241E
System code update cannot start because a component firmware update is in progress.
CMMVC7242E
No help available for [%1].
CMMVC7243E
The specified port mask cannot be applied because insufficient paths would exist for node communication.
CMMVC7248E
You must use an 0x parameter for the -drivelba parameter.
CMMVC7249E
The name that you have entered is not valid. The name can contain letters, numbers, spaces, periods, dashes, and underscores. The name must not begin or end with a space. The name must not begin with a period.
CMMVC7300E
The maximum number of volumes already exist.
CMMVC7301E
The command failed because the volume would be smaller than the minimum size.
CMMVC7302E
The command failed because insufficient extents are available.
CMMVC7304E
The command cannot be initiated because a spare is already configured.
CMMVC7305E
The command cannot be initiated because the drive fault is unrecoverable.
CMMVC7306E
The command cannot be initiated because no array currently exists.
CMMVC7307E
The command cannot be initiated because the battery slot number specified is invalid.
CMMVC7308E
The command cannot be initiated because an array already exists.
CMMVC7309E
The command cannot be initiated because the specified raid level is unsupported on this platform.
CMMVC7310E
The command cannot be initiated because one or more drives is in the failed state.
CMMVC7311E
The command cannot be initiated because the number of drives is unsupported.
CMMVC7312E
The command could not be initiated because one or more volumes are using the array.
CMMVC7313E
The specified array does not require recovery as it is not corrupt.
CMMVC7314E
The specified array cannot be recovered due to failed drives.
CMMVC7315E
The command cannot be initiated because the specified slot does not exist.
CMMVC7316E
The specified array cannot be recovered due to failed drives.
CMMVC7317E
The command cannot be initiated because the specified PSU does not exist.
CMMVC7318E
Open access is not enabled.
CMMVC7319E
The air filter must be enabled to change the period.
CMMVC7320E
Invalid port mask supplied.
CMMVC7321E
Mask cannot be applied because insufficient paths exist for node communication.
CMMVC7322E
Another volume uses this SCSI ID.
CMMVC7323E
The command cannot be initiated due to a hardware fault.
CMMVC7324E
The command cannot be initiated because the drive task is not supported.
CMMVC7325E
Open Access setting not changed because hosts exist.
CMMVC7326E
Cannot create logical host because open access is enabled.
CMMVC7329E
The maximum number of Infiniband GIDs for the host is already configured.
CMMVC7330E
An invalid Infiniband GID was entered.
CMMVC7331E
A supplied Infiniband GID is already assigned to another host.
CMMVC7332E
The array does not exist.
CMMVC7334E
The array could not be removed because it is initializing.
CMMVC7335E
The encryption state cannot be changed when an array exists.
CMMVC7336E
The topology and speed are not compatible with the specified port.
CMMVC7337E
The command cannot be initiated because the encryption key was not found.
CMMVC7338E
The command cannot be initiated because the encryption key is not valid.
CMMVC7339E
The command cannot be initiated because the drive did not unlock.
CMMVC7340E
The command cannot be initiated because the array is offline.
CMMVC7341E
The update cannot be resumed at this time.
CMMVC7342E
The array is already encrypted.
CMMVC7343E
A software upgrade is in progress and must finish before battery reconditioning can be started.
CMMVC7344E
Battery reconditioning is not currently running.
CMMVC7348E
One of the batteries is currently reconditioning. Wait until reconditioning finishes.
CMMVC7349E
The other battery in the enclosure is not in a good and charged state.
CMMVC7350E
The selected battery cannot be reconditioned.
CMMVC7351E
Encryption cannot be disabled while an encrypted array exists.
CMMVC7352E
The array cannot be encrypted because system encryption is disabled.
CMMVC7353E
The command cannot be initiated because a rekey operation is in progress.
CMMVC7354E
Rekey operation failed.
CMMVC7355E
The command cannot be initiated because system encryption is not enabled.
CMMVC7356E
Unable to validate the key on the current USB drive.
CMMVC7357E
The command cannot be initiated because a drive has failed.
CMMVC7358E
Rekey commit not allowed until keys have been copied.
CMMVC7359E
Operation not applicable when encryption is disabled.
CMMVC7360E
The command cannot be executed because the array is not online.
CMMVC7361E
The command cannot be initiated because another operation is in progress on the array.
CMMVC7362I
The encryption copy tool should only be used with the assistance of support.
CMMVC7363E
The system is unable to mount/unmount the USB drive.
CMMVC7364E
The system is unable to collect the information needed to provide the proper output from the lsencryption command.
CMMVC7365E
The system could not complete the key copy operation because it could not read the new key file.
CMMVC7366E
The system could not complete the key copy operation because it could not read the current key file.
CMMVC7367E
The key file is not valid.
CMMVC7368I
%1 additional copy has been made.
CMMVC7369E
No additional key copies were written to the USB drive; all required keys already exist on the drive.
CMMVC7370W
Only the new key file has been copied to the USB drive; the current key was already on the drive.
CMMVC7371E
Only the current key file has been copied to the USB drive; the new key was already on the drive.
CMMVC7372E
The current key on the USB drive does not match the key that was previously read.
CMMVC7373E
The attempted write of the new key to the USB drive has failed.
CMMVC7374E
The attempted write of the current key to the USB drive has failed.
CMMVC7375E
No keys were written to the USB drive. Do not proceed without Support assistance.
CMMVC7376E
The command cannot be run because an encryption key has not been created.
CMMVC7377E
The command cannot be executed because the array does not exist.
CMMVC7378E
The command cannot be executed because the array is not encrypted.
CMMVC7379E
System encryption cannot be disabled because an encrypted array already exists.
CMMVC7380E
The command cannot be executed because an encrypted array exists.
CMMVC7381E
The rekey failed because the current encryption key was not found on the USB drive.
CMMVC7382E
The rekey failed because the new encryption key was not found on the USB drive.
CMMVC7383E
The rekey failed because the proposed new encryption key could not be generated.
CMMVC7384E
The rekey operation failed because one of the drives failed to prepare for the rekey.
CMMVC7385E
The rekey operation failed because one of the drives failed to commit to the rekey.
CMMVC7386E
The rekey operation failed because one of the drives failed to cancel the rekey.
CMMVC7387E
The command cannot be initiated because the rekey is not in an expected state.
CMMVC7388E
Rebuild options are not supported for this array RAID level.
CMMVC7391E
Specified drive is in the incorrect enclosure.
CMMVC7392E
The enclosure is already managed by a different cluster.
CMMVC7393E
The enclosure cannot be unmanaged as there is an array present.
CMMVC7394W
Encryption feature is being used without system license entitlement.
CMMVC7395E
The command cannot be executed because the enclosure is not a part of the cluster.
CMMVC7396E
The command failed because the target managed disk (MDisk) is in offline state.
CMMVC7399E
The command cannot be run as the enclosure is not yet managed.
CMMVC7402E
The command has failed because the IP address is not valid.
CMMVC7403E
The command cannot be initiated because it is not supported for the specified enclosure type
CMMVC7404E
The command cannot be initiated because it is not supported for the specified drive type
CMMVC7405E
The command cannot be initiated because it is not supported for the specified array type
CMMVC7406E
The command failed because the requested volume size is too large. Reduce the array's reserved capacity to free space.
CMMVC7407E
The array has insufficient free space to reserve for performance.
CMMVC7408E
The command has failed because one or more of the parameters entered is not valid for the specified enclosure type.
CMMVC7409E
The command cannot be initiated because the port is not online.
CMMVC7410E
The command has failed because one or more of the parameters entered is not valid for the specified drive type.
CMMVC7411E
The command has failed because one or more of the parameters entered is not valid for the specified array type.
CMMVC8000E
Cannot execute on an active node.
CMMVC8001E
Cannot execute on a candidate node.
CMMVC8002E
Cannot execute on a service-state node.
CMMVC8003E
Cannot execute on a node in a cluster-recovery state.
CMMVC8004E
Cannot execute on a node with a location error.
CMMVC8005E
Cannot execute on a node displaying hardware errors.
CMMVC8006E
Cannot execute on a node displaying errors.
CMMVC8007E
Cannot execute on a node which is charging.
CMMVC8008E
Command not supported on this hardware platform
CMMVC8009E
Cannot execute on a node canister.
CMMVC8010E
Not from a USB stick.
CMMVC8011E
Version too high for this client.
CMMVC8012E
The operation did not complete in the time allowed.
CMMVC8013E
Incompatible parameters set.
CMMVC8014E
Bad parameter value.
CMMVC8015E
Failed.
CMMVC8016E
Node would be clustered if not in service state.
CMMVC8017E
Info value not recognised.
CMMVC8018E
Provided buffer was too small.
CMMVC8019E
Task could interrupt IO and force flag not set.
CMMVC8020E
Attempting to create cluster while there is a stored cluster ID.
CMMVC8021E
Invalid panel name.
CMMVC8022E
New cluster created but node cannot leave service state.
CMMVC8023E
Partner node is clustered.
CMMVC8024E
Gateway or subnet/prefix required.
CMMVC8025E
DHCP Failed.
CMMVC8026E
No suitable donor.
CMMVC8027E
T3 prepare failed.
CMMVC8028E
T3 prepare incomplete.
CMMVC8029E
T3 execute failed.
CMMVC8030E
Another instance of this command is already running.
CMMVC8031E
file not found.
CMMVC8032E
The specific update package cannot be installed over the current version.
CMMVC8033E
Password reset disabled.
CMMVC8034E
A compulsory parameter is missing.
CMMVC8035E
The service assistant CLI is not ready - try again.
CMMVC8036E
No help available.
CMMVC8037E
A required parameter is missing.
CMMVC8038E
Required parameters are missing.
CMMVC8039E
The [%1] parameter is missing its associated arguments.
CMMVC8040E
[%1] is not a supported parameter.
CMMVC8041E
[%1] is not a valid command line option.
CMMVC8042E
Invalid or inconsistent arguments.
CMMVC8043E
This command can only be run by the superuser.
CMMVC8044E
Command completed successfully.
CMMVC8045E
Authentication failed.
CMMVC8046E
Partner node has lost cluster data.
CMMVC8047E
Not a valid ssh key.
CMMVC8048E
Invalid file permissions.
CMMVC8049E
Invalid cluster name.
CMMVC8050E
Files cannot be unpacked from the update package. The system must unpack them.
CMMVC8051E
Utilities package installed.
CMMVC8052E
The signature of the utility package has failed verification.
CMMVC8053E
The specific update package cannot be installed on this hardware.
CMMVC8054E
The update failed as the package is missing files.
CMMVC8055E
The command cannot be run because the node is busy.
CMMVC8056E
An error occurred in communicating with the target node.
CMMVC8057E
Files cannot be copied to a node which is not part of the source cluster.
CMMVC8058E
Cannot create file, file already exists.
CMMVC8059E
The update package supplied cannot be installed using service state whilst maintaining the cluster configuration on this node. To maintain the cluster configuration on this node, this package can only be installed with applysoftware or pacedccu mode. This package can be installed in service state using the -ignore flag, however the cluster state will be destroyed and cluster configuration will be lost from the node.
CMMVC8060E
DHCP fallback is not supported on this platform.
CMMVC8061E
The enclosure does not support setting a machine part number.
CMMVC8062E
The machine type and model is not valid for this enclosure.
CMMVC8063E
The machine part number is not valid for this enclosure.
CMMVC8064E
The machine part number and machine type and model are not valid for this enclosure.
CMMVC8065E
An enclosure property has already been set and cannot be modified.
CMMVC8066E
A new enclosure VPD field does not match the node copy.
CMMVC8070E
The specified IP addresses are not in the same sub-network.
CMMVC8071E
The specified IP address is already in use.
CMMVC8072E
The above parameters are invalid or missing from cfgtask.txt.
CMMVC8085E
The command failed because the node does not support technician port functionality.
CMMVC8086E
The command failed because the node already has a dedicated technician port.
CMMVC8087E
The command failed because the file specified is a valid USVNID file but it is for a different node.
CMMVC8088E
The command failed because the file specified is not a valid USVNID file.
CMMVC8091E
No upload in progress.
CMMVC8092E
An error occurred in communicating with the remote server.
CMMVC8093E
No download in progress.
CMMVC8094E
The command failed because the available space is inadequate for the download.
CMMVC8095E
The command failed because the target Ethernet port does not exist.
CMMVC8096E
The command failed because insufficient paths would exist for the IP connection between the nodes in the same IP discovery zone.
CMMVC8097E
The command failed because a duplicate WWNN has been detected.
CMMVC8098E
The command failed because the specified ethernet port is not an RDMA capable port.
CMMVC8099E
The command failed because the target Ethernet port is set to non default MTU value.
CMMVC8100E
The command failed because clustering is not supported on the specified Ethernet port.
CMMVC8202E
To perform this task, a system board mismatch node error must be active.
CMMVC8203E
To perform this task, the number of boot drives present must be correct.
CMMVC8204E
To perform this task, the boot drive owners (actual_node_sn) must be the same.
CMMVC8206E
The command failed because the IP address is a reserved/special IP.
CMMVC8207E
Backup data for the midplane is unavailable.
CMMVC8208E
The maximum number of discovery subnets are already configured on the node.
CMMVC8209E
This subnet conflicts with one that is already configured on the node.
CMMVC8210E
This discovery subnet conflicts with the one reserved by IANA.
CMMVC8211E
This subnet is too big to be set as a discovery subnet.
CMMVC8212E
Node rescue is not supported in this platform.
CMMVC8216E
An insecure password was chosen.
CMMVC8217E
Cannot execute on a spare node.
CMMVC8261E
The command failed because the hardware configuration of the local cluster is not compatible with the software of a partnered cluster.
CMMVC8262E
Cannot remove the host from the specified I/O groups because host mappings exist in multiple I/O groups.
CMMVC8263E
The command failed because the volume is associated with a file system and your requested action can not be completed under your current user role.
CMMVC8264E
The command failed because the volume associated with a file system and only the real capacity of a compressed file system volume can be changed.
CMMVC8265E
The action failed because the specified port is for management only.
CMMVC8266E
The action failed because the specified port is not installed.
CMMVC8267E
The attempt to add the node to the system failed because the node is being manually updated. The system must be prepared for update by using the same package that is currently installed on the node that is being updated.
CMMVC8268E
The attempt to prepare the cluster for update has failed because the cluster has already been prepared with a different package level. The update must first be cancelled before reattempting the update.
CMMVC8269E
The attempt to prepare the cluster for update has failed because the previous update is in prepare_failed state. The previous update must first be aborted before reattempting the update.
CMMVC8270E
The applysoftware prepare timed out because an attempt to make the volume cache empty took too long. The command will be completed asynchronously. Use lsupdate to monitor the progress.
CMMVC8272E
Access iogrp parameter not valid when creating a file system volume.
CMMVC8273E
Host cannot be removed as there is a volume that is accessible from multiple iogrps including one of the iogrps specified.
CMMVC8274E
The entry in the event log cannot be fixed because the given sequence number is out of range.
CMMVC8275E
An entry with the given sequence number cannot be found in the event log.
CMMVC8276E
The entry in the event log cannot be fixed because it has expired or is in the monitoring state.
CMMVC8277E
The MTM format must be XXXX-YYY where X is a numeric value, and Y is numeric or upper case character.
CMMVC8278E
The volume is accessible through more than one I/O group, and the host being mapped to the volume does not support volumes being mapped from multiple I/O groups.
CMMVC8279E
The volume is accessible through more than one I/O group, and the host being mapped to the volume has an iSCSI name. iSCSI hosts do not support volumes being mapped from multiple I/O groups.
CMMVC8280E
The host has at least one volume mapped which is accessible through more than one I/O group, and the port being added is from a host system which does not support volumes being mapped from multiple I/O groups.
CMMVC8281E
The host has at least one volume mapped which is accessible through more than one I/O group, and the port being added is from a host with an iscsi name. Iscsi hosts do not support volumes being mapped from multiple I/O groups.
CMMVC8282E
At least one host mapped to the volume does not support volumes being mapped from multiple I/O groups.
CMMVC8283E
At least one host mapped to the volume has an iscsi name. Iscsi hosts do not support volumes being mapped from multiple I/O groups.
CMMVC8284E
The enclosure does not support setting a machine part number.
CMMVC8285E
The machine type and model is not valid for this enclosure.
CMMVC8286E
The machine part number is not valid for this enclosure.
CMMVC8287E
The machine part number and machine type and model are not valid for this enclosure.
CMMVC8289E
A new enclosure VPD field does not match the node copy.
CMMVC8290E
The action failed because the requested combination of notification settings is not permitted.
CMMVC8291E
The command failed because it is not supported.
CMMVC8292E
The command failed because a parameter is not supported.
CMMVC8293E
The command failed because it is not supported for image-mode volumes.
CMMVC8294E
The command failed because the FlashCopy feature is not active and the maximum number of FlashCopy target volumes already exist.
CMMVC8295E
The command failed because a licensed feature is not activated.
CMMVC8296E
The command failed because it is not supported for image-mode MDisks.
CMMVC8297E
The drive cannot be managed because it has become unreachable.
CMMVC8298E
The system cannot open the file.
CMMVC8299E
The system ran out of temporary resource while opening the file.
CMMVC8300E
The specified file cannot be used because it contains too many drive software images.
CMMVC8301E
The system cannot read drive software from the specified file because the file contains an invalid drive firmware version string.
CMMVC8302E
The system cannot read drive software from the specified file.
CMMVC8303E
The system can only program the FPGA of one drive at a time.
CMMVC8304E
The system cannot apply the task because an earlier drive update task is still in progress.
CMMVC8305E
The system cannot apply drive software to the specified drives because some of them are not online.
CMMVC8306E
Some of the specified drives are offline. The system cannot apply drive software to an offline drive, even if the -force option is specified.
CMMVC8307E
None of the drives can be scheduled for drive software upgrade.
CMMVC8309E
The task cannot be initiated because some of the specified drives have an unsupported drive technology.
CMMVC8310E
The task cannot be applied to unused drives when multiple drives are specified.
CMMVC8311E
The system cannot open the file.
CMMVC8313E
The specified file cannot be used because it contains too many drive software images.
CMMVC8314E
The system cannot read drive software from the specified file because the file contains an invalid drive firmware version string.
CMMVC8315E
The system cannot read drive software from the specified file.
CMMVC8316E
The system can only program the FPGA of one drive at a time.
CMMVC8317E
The system cannot apply the task because an earlier drive update task is still ongoing.
CMMVC8318E
The system cannot apply drive software to the specified drives because some of them are not online.
CMMVC8319E
Some of the specified drives are offline. The system cannot apply drive software to an offline drive, even if the -force option is specified.
CMMVC8320E
None of the drives can be scheduled for drive software upgrade.
CMMVC8321E
The '-all' or '-drive' option is required to specify the drive(s) you want to upgrade.
CMMVC8323E
The task cannot be applied to unused drives when multiple drives are specified.
CMMVC8324E
There are no drive software upgrades scheduled.
CMMVC8325E
None of the specified drives needed to be upgraded or downgraded.
CMMVC8326E
The task cannot be initiated because the drive use changed.
CMMVC8327E
The -allowreinstall and -allowdowngrade options cannot be used with option -type fpga.
CMMVC8328E
No package file is specified or invalid package file name is used.
CMMVC8329E
The task cannot be initiated because downloading to one or more drives could cause volumes to go offline.
CMMVC8330E
The %1 of %2 %3 in backup is %4; should be %5
CMMVC8331E
The command failed because at least one of the specified MDisks can only be used in image mode.
CMMVC8332E
No MDisks were removed from the storage pool because at least one of the specified MDisks can only be used in image mode.
CMMVC8333E
The task failed because it is not supported for image mode only MDisks.
CMMVC8335E
Cannot change attribute for IP address in an active partnership.
CMMVC8336E
Site was not specified. Site must be specified because topology is stretched.
CMMVC8337E
Site specified not valid. System topology is stretched and the other member has been configured to the same site.
CMMVC8338E
Site parameter is not supported until the current update completes.
CMMVC8339E
Not supported on this system.
CMMVC8340E
Cannot modify site because system topology is stretched.
CMMVC8341E
Site value is not valid. Can only specify site 1 or site 2.
CMMVC8342E
Cannot set stretched topology because some nodes do not have a configured site.
CMMVC8343E
Cannot set stretched topology because some I/O groups have 2 nodes in the same site.
CMMVC8344E
Cannot change site because controller has one or more managed MDisks and the system topology is stretched or Hyperswap.
CMMVC8345E
Cannot change site because the controller is a SAS RAID Controller.
CMMVC8346E
Cannot change quorum disk because there is already a quorum disk defined at that site, and the cluster topology is stretched or hyperswap.
CMMVC8347E
Cannot modify rcauthmethod due to the presence of unstopped IP partnerships.
CMMVC8348E
Cannot modify chapsecret due to rcauthmethod set to chap and the presence of unstopped IP partnerships.
CMMVC8349E
The rc authentication method specified is not valid.
CMMVC8350E
The command failed because the specified battery is offline.
CMMVC8351E
The command has failed because the specified battery is not redundant.
CMMVC8352E
The task cannot be initiated because the download type is not valid.
CMMVC8353E
CHAP authentication failure
CMMVC8354E
Unreachable cluster IP address
CMMVC8355E
Remote Copy port groups not configured or incorrectly configured.
CMMVC8356E
Remote Copy port groups not configured or incorrectly configured.
CMMVC8357E
Maximum number of allowed partnerships exceeded.
CMMVC8358E
No local cluster IPs for the partnership type configured.
CMMVC8359E
Partner already exists in candidate list. Cannot create partnership.
CMMVC8360E
Specified partner cluster IP address is used on local cluster. Cannot create partnership.
CMMVC8361E
All IP addresses of the partnership type are either down or not configured.
CMMVC8362E
The action failed because the cluster ID is not valid.
CMMVC8363E
The remote cluster partnership was not created because it already exists.
CMMVC8364E
Unsupported partnerships type specified.
CMMVC8365E
Cannot change parameter if partnership is not in stopped state.
CMMVC8366E
Incorrect remote cluster IP specified.
CMMVC8367E
Incorrect operation of FC partnership.
CMMVC8368E
Cannot set or reset attributes for unconfigured ports.
CMMVC8369E
The action failed because the cluster ID is not valid.
CMMVC8370E
The remote cluster partnership was not created because it already exists.
CMMVC8371E
Unable to setup partnership due to partnership type mismatch.
CMMVC8372E
Unable to set up Remote Copy data paths with partner due to unavailability of matching Remote Copy port groups.
CMMVC8373E
Easy Tier is active without a license for each enclosure.
CMMVC8374E
The command failed because the source volume has pinned data.
CMMVC8375E
The command failed because the volume has pinned data.
CMMVC8376E
Cannot change quorum disk because there is already a quorum disk defined at that site, and the cluster topology is stretched or hyperswap.
CMMVC8377E
Cannot change the site for a quorum drive.
CMMVC8378E
Cannot modify cluster IP due to the presence of unstopped IP partnerships.
CMMVC8379E
Partner state is stopped.
CMMVC8380E
Partner software version mismatch.
CMMVC8381E
The task cannot be cancelled as it has completed all drive downloads.
CMMVC8382E
The system cannot apply the task because a delay has been imposed between commands. (About 270 seconds)
CMMVC8383E
System layer mismatch.
CMMVC8384E
The command has failed because the specified fan module is offline.
CMMVC8386E
Sync operation not possible.
CMMVC8387E
Partner cluster ID mismatch.
CMMVC8389E
[-size] is not a supported parameter for the specified mdiskgrp.
CMMVC8390E
Cannot set easy_tier_option for child storage pool, the value must be same as parent storage pool's easy tier setting.
CMMVC8412E
Cannot add mdisks to a child pool.
CMMVC8415E
The command cannot be initiated because the maximum supported number of drives already exists.
CMMVC8423E
The command failed because the storage pool size is not a multiple of extent size.
CMMVC8424E
The command failed because the source or target storage pool is a child storage pool, and source and target are in different parent storage pools.
CMMVC8425E
The command failed because the storage pool has child storage pools.
CMMVC8427E
The command failed because the child storage pool can not be shrunk below its used capacity.
CMMVC8452E
The command failed because the specified parent mdiskgrp is a child pool.
CMMVC8455E
The command cannot be initiated because the maximum supported number of drives already exists.
CMMVC8456E
At least one drive on the enclosure cannot find drive update package.
CMMVC8457E
The mapping cannot be removed because the volume being unmapped has received I/O within the defined volume protection period.
CMMVC8458E
The volume cannot be removed because the volume has received I/O within the defined volume protection period.
CMMVC8459E
The volume cannot be removed because the volume has received I/O within the defined volume protection period.
CMMVC8460E
The storage pool cannot be deleted because at least one volume in the pool has received I/O within the defined volume protection period.
CMMVC8461E
The host cannot be removed because the host being deleted is mapped to volumes which have received I/O within the defined volume protection period.
CMMVC8462E
The host I/O group cannot be removed because at least one volume in the I/O group(s) being removed from the host has received I/O within the defined volume protection period.
CMMVC8463E
The port cannot be removed because the host is mapped to at least one volume which have received I/O within the defined volume protection period and the port is the last port associated with the host.
CMMVC8469E
The node cannot be added because it does not meet minimum hardware requirements.
CMMVC8470E
The system update cannot be completed because it is not required.
CMMVC8471E
The system update cannot be resumed because it is not stalled.
CMMVC8472E
The action cannot be performed because paced update is not in progress.
CMMVC8473E
The next node cannot be updated because it is not ready for update.
CMMVC8474E
The node cannot be updated because it would cause VDisks to go offline.
CMMVC8475E
The node cannot be updated because it is offline.
CMMVC8476E
The node cannot be added because it would cause a paced update but the system has not completed its current update.
CMMVC8477E
The command failed because firmware applicable to a drive was not found in the package.
CMMVC8478E
The mapping cannot be removed because the volume being unmapped has received I/O within the defined volume protection period.
CMMVC8479E
The volume cannot be removed because the volume has received I/O within the defined volume protection period.
CMMVC8481E
The storage pool cannot be deleted because at least one volume in the pool has received I/O within the defined volume protection period.
CMMVC8482E
The host cannot be removed because the host being deleted is mapped to volumes which have received I/O within the defined volume protection period.
CMMVC8483E
The host I/O group cannot be removed because at least one volume in the I/O group(s) being removed from the host has received I/O within the defined volume protection period.
CMMVC8484E
The port cannot be removed because the host is mapped to at least one volume which have received I/O within the defined volume protection period and the port is the last port associated with the host.
CMMVC8485E
The command cannot be initiated because the drive that you have specified has not been formatted with the correct protection information scheme.
CMMVC8518E
The command failed because image-mode volumes are not supported in child storage pools.
CMMVC8519E
The command failed because sequential-mode volumes are not supported in child storage pools.
CMMVC8523E
The command failed because the specified storage pool is a child storage pool.
CMMVC8525E
The command failed because mdisks cannot be added to a child storage pool.
CMMVC8526E
The command failed because mdisks cannot be removed from a child storage pool.
CMMVC8528E
The system does not support encryption.
CMMVC8529E
The encryption function has not been activated.
CMMVC8530E
A rekey operation is in progress.
CMMVC8531E
Encryption cannot be disabled while functions are configured to use encryption.
CMMVC8532E
The encryption function is not enabled.
CMMVC8533E
No rekey operation in progress.
CMMVC8534E
node [X] has insufficient entropy to generate key material.
CMMVC8535E
The system does not have access to current encryption keys.
CMMVC8536E
The system does not have sufficient USB flash drives attached.
CMMVC8537E
Not enough USB copies made, needs (%1).
CMMVC8538E
System is busy commit in progress.
CMMVC8539E
Encryption is not supported on drives IO group
CMMVC8540E
Key not accepted by SAS adapter because of an internal error.
CMMVC8541E
The command cannot be initiated because the object is being used by an automatic system configuration task.
CMMVC8542E
The system update test utility has not been run before updating the system.
CMMVC8544E
The command cannot be initiated because the object is being used by an automatic system configuration task.
CMMVC8549E
The command failed because the source volume is from a child pool.
CMMVC8550E
Cluster ID alias cannot be changed whilst encryption is enabled.
CMMVC8567E
A host of type adminlun is required to be mapped to all IO groups.
CMMVC8570E
A subsidiary volume may only be mapped to hosts of type adminlun.
CMMVC8571E
The volume is already mapped as a subsidiary volume.
CMMVC8573E
The action failed because there is one special volume owned by metadata volume in this storage pool.
CMMVC8574E
The action failed because some volumes with owner type vVol depend on the metadatavdisk and -ignorevvolsexist was not specified.
CMMVC8575E
The action failed because it depends on NTP server but NTP server is not configured.
CMMVC8587E
The command failed because the volume is fast formatting.
CMMVC8590E
The command failed because the Compare Volume ID or name is invalid.
CMMVC8591E
The command failed because the Base Volume ID or name is invalid.
CMMVC8592E
The command failed because the Compare Volume does not exist.
CMMVC8593E
The command failed because the Base Volume does not exist.
CMMVC8594E
The command failed because the Base and Compare Volumes are the same.
CMMVC8595E
The command failed because the startlba of the scan segment is invalid.
CMMVC8596E
The command failed because the lbacount of the scan segment is invalid.
CMMVC8597E
The command failed because the chunk size is invalid.
CMMVC8598E
The command failed because the volume and the base volume are not in the same dependency chain.
CMMVC8599E
The command failed because a node is offline.
CMMVC8600E
The command failed because the write cache could not be flushed in time.
CMMVC8601E
The command failed because the start of the scan segment is not chunk aligned.
CMMVC8620E
The active-active relationship could not be created because the master and auxiliary volumes do not have different well-defined sites.
CMMVC8621E
The active-active relationship could not be created because the system topology is not HyperSwap.
CMMVC8622E
The active-active relationship could not be created because the master and auxiliary volumes are not in the same system.
CMMVC8623E
I/O group was not specified. I/O group must be specified because topology is HyperSwap.
CMMVC8624E
Cannot set Hyperswap topology because some nodes do not have a configured site.
CMMVC8625E
Cannot set HyperSwap topology because an I/O group has nodes assigned to different sites.
CMMVC8626E
Cannot modify site because topology is HyperSwap.
CMMVC8627E
Site was not specified. Site must be specified because topology is Hyperswap.
CMMVC8628E
The host mapping was not created because the volume is not the host accessible volume in an active-active relationship.
CMMVC8629E
Site specified is not valid. System topology is Hyperswap and the other member of the IO group has been configured to a different site.
CMMVC8630E
Site specified is not valid. System topology is Hyperswap and the node or control enclosure was previously configured with a different site.
CMMVC8631E
The change VDisk could not be disassociated because it is configured in an active-active relationship.
CMMVC8632E
The copy type of an active-active relationship or group cannot be changed.
CMMVC8633E
The relationship could not be added to the consistency group because it does not have an up-to-date copy in the same site as a set of up-to-date copies in the group.
CMMVC8634E
The host mapping was not created because the host does not have a site defined and the volume is in an active-active relationship.
CMMVC8635E
Cannot un-set the host site as the host is mapped to a volume in an active-active relationship.
CMMVC8636E
The active-active relationship was not created because one or more hosts mapped to the master volume do not have a site defined.
CMMVC8637E
The active-active relationship could not be created because there are one or more host mappings to the auxiliary volume.
CMMVC8638E
An active-active relationship or group may not be manually started unless it has a state of idling and access has previously been enabled to an out-of-sync consistent copy.
CMMVC8639E
An active-active relationship or group may not be manually stopped unless it has a state of consistent_copying and access is required to the out-of-sync consistent copy.
CMMVC8640E
Active-active relationships and groups alter their direction automatically and cannot have their direction switched manually.
CMMVC8642E
The command failed because the copy specified is not synchronized. The copy must be synchronized to create an active-active relationship.
CMMVC8643E
The active-active relationship could not be created because the existing and new volumes do not have different well-defined sites.
CMMVC8644E
The command failed because the auxiliary volume does not contain an up-to-date copy or have host access enabled.
CMMVC8646E
The active-active relationship could not be created, either because the master or auxiliary volume is the target of a FlashCopy mapping or because the master or auxiliary volume is the source of a FlashCopy mapping with a target volume in a different site.
CMMVC8649E
Cannot change topology because active-active relationships are defined, and only supported in Hyperswap topology.
CMMVC8650E
System topology is Hyperswap or stretched, and the site of the MDisk being added does not match that of the storage pool.
CMMVC8652E
The command failed because the volume is owned and has restricted use.
CMMVC8653E
The command failed as an MDisk group is owned and has restricted use.
CMMVC8654E
The storage pool specified is not valid. The volume is a participant in an active-active relationship, and the storage pool for the new copy is in a different site to the volume's current site.
CMMVC8655E
The volume being moved is a participant in an active-active relationship, and the target storage pool is in a different site to the volume's current site.
CMMVC8657E
The command failed as the specified storage pool is offline.
CMMVC8658E
The create failed because there are no iogroups supporting compression.
CMMVC8659E
The Create FlashCopy mapping task cannot be initiated because the target volume is in an active-active relationship.
CMMVC8660E
The Create FlashCopy mapping task cannot be initiated because the source volume is in an active-active relationship and the target volume and map are not in the same site as the source volume.
CMMVC8661E
The command has failed because the specified volume is a target of a FlashCopy mapping with a source volume in an active-active relationship and the new I/O group is in a different site to the source volume.
CMMVC8662E
The command has failed because the specified volume is a target of a FlashCopy mapping with a source volume in an active-active relationship and the target storage pool is in a different site to the source volume.
CMMVC8663E
The command has failed because the specified volume is a target of a FlashCopy mapping with a source volume in an active-active relationship and the storage pool for the new copy is in a different site to the source volume.
CMMVC8664E
The change volume could not be associated because it does not have the same well-defined site as the associated volume in the relationship.
CMMVC8665E
The FlashCopy mapping was not started because the source volume is in an active-active relationship and does not contain an up-to-date copy or have host access enabled.
CMMVC8666E
The FlashCopy consistency group was not started because one or more of the source volumes are in an active-active relationship and do not contain an up-to-date copy or have host access enabled.
CMMVC8667E
The command failed because a specified host port has more than four logins on a node.
CMMVC8668E
The host mapping was not created because the SCSI logical unit number (LUN) ID is not valid for this particular host type.
CMMVC8670E
Cannot modify host type since it has subsidiary mappings.
CMMVC8671E
An existing volume is mapped with a SCSI ID which exceeds the maximum for this host type.
CMMVC8672E
The command failed because the access IO group set of a subsidiary volume may not be modified.
CMMVC8673E
The volume is already mapped as a SCSI LUN which must first be unmapped/removed in order to create a subsidiary volume mapping.
CMMVC8674E
The volume is not mapped as a subsidiary LUN.
CMMVC8676E
The command failed because the volume is not a master volume in an active-active relationship.
CMMVC8677E
Retaining access to the auxiliary VDisk failed because either the master or the auxiliary VDisk is in mirrored mode.
CMMVC8696E
The command failed because the volume or a volume copy is in the deleting state.
CMMVC8697E
The command failed because the source or target volume is in the deleting state.
CMMVC8698E
The command failed because the volume has host mappings, use -removehostmappings.
CMMVC8699E
The command failed because the volume is image mode and has FlashCopy maps, either remove the FlashCopy maps first or use -force.
CMMVC8706E
The command failed because the primary copy's autodelete flag is on, meaning type conversion is in progress.
CMMVC8707E
The command failed because the caching IO groups for the volume are not in two independent sites.
CMMVC8708E
The command failed because the system does not have a hyperswap topology.
CMMVC8709E
The command failed because the caching IO groups are not in the same sites as the storage pools.
CMMVC8710E
The command failed because there were not enough extents in storage pool storage_pool.
CMMVC8711E
The command failed because too many IO groups were specified.
CMMVC8712E
The command failed because too many storage pools were specified.
CMMVC8713E
The command failed because the storage pool must be in site 1 or 2.
CMMVC8714E
The command failed because the number of IO groups specified was different to the number of storage pools specified.
CMMVC8715E
The command failed because the storage pools for the volume are not in two independent sites. Volumes can only be created using storage in site 1 and site 2.
CMMVC8716E
The create failed because there are no iogroups in site site_number.
CMMVC8717E
The create failed because there are no iogroups supporting compression in site site_number.
CMMVC8718E
The command failed because the managed disk must be in site 1 or 2.
CMMVC8719E
The command failed because one or more service IP addresses aren't set.
CMMVC8720E
The command failed because the IP address provided is already configured as a DNS server.
CMMVC8721E
The command failed because the IP address provided is already in use by this system.
CMMVC8722E
The command has failed because DNS server cannot be removed while DNS clients are configured.
CMMVC8723E
The command failed because the system does not support the cloud gateway function.
CMMVC8724E
The command failed because the candidate does not support cloud snapshots and there is a configured cloud account.
CMMVC8725E
The command failed because DNS servers are not configured.
CMMVC8726E
The command failed because the encryption capability is not currently available on this system.
CMMVC8727E
The command failed because the cloud gateway service is offline.
CMMVC8728E
The command failed because the cloud account is with a different provider.
CMMVC8729E
The command failed because the maximum number of systems are already using the cloud account.
CMMVC8730E
The command failed because of a problem accessing metadata objects in the cloud storage.
CMMVC8731E
The command failed because the metadata objects were created by a more recent version of code that is incompatible with this system.
CMMVC8732E
The command failed because the new credentials identify different cloud storage.
CMMVC8733E
The command failed because there is at least one cloud account configured.
CMMVC8734E
The command failed because the system cannot resolve the hostname of the cloud provider.
CMMVC8735E
The command failed because the system cannot contact the cloud provider server on the management network.
CMMVC8736E
The command failed because the system cannot establish a connection with the cloud provider software.
CMMVC8737E
The command failed because the system does not have a CA SSL certificate for the cloud provider server.
CMMVC8738E
The command failed because the SSL certificate has expired.
CMMVC8739E
The command failed because the SSL certificate is not valid.
CMMVC8740E
The command failed because the account credentials were rejected by the cloud provider.
CMMVC8741E
The command failed because the account credentials do not give permission to access the cloud storage containers.
CMMVC8742E
The command failed because of an error communicating with the cloud provider.
CMMVC8743E
The command failed because the region specified is not valid.
CMMVC8744E
The command failed because the bucket prefix or container prefix is already in use.
CMMVC8745E
The command failed because the system is in Gen1 compatibility mode.
CMMVC8746E
The command failed because an account with an SSL certificate must have an https endpoint.
CMMVC8748E
The command failed because the cloud data is encrypted with the wrong key.
CMMVC8749E
The command failed because the specified volume group is not empty.
CMMVC8750E
The command failed because the specified volume group already contains the maximum number of volumes.
CMMVC8751E
A new cloud snapshot could not be created because the volume group does not contain any volumes.
CMMVC8752E
A cloud snapshot could not be created because the cloud FlashCopy function is not enabled for all the volume group members.
CMMVC8753E
A new cloud snapshot could not be created because a cloud snapshot operation is already in progress.
CMMVC8754E
A cloud snapshot could not be created because a restore operation is already in progress.
CMMVC8755E
The command failed because the system does not support the volume group function.
CMMVC8756E
A new cloud snapshot could not be created because the volume is part of a volume group.
CMMVC8757E
Cannot change facility because CADF reporting is set.
CMMVC8758E
Cloud snapshots cannot be enabled because there are insufficient free volume copy IDs in the system.
CMMVC8759E
Cloud snapshots cannot be enabled because there are insufficient free volume copy IDs in the caching I/O group of the volume.
CMMVC8760E
Cloud snapshots cannot be enabled because there is insufficient free capacity in the storage pool.
CMMVC8761E
Cloud snapshots cannot be enabled because the maximum number of FlashCopy mappings in the system has been reached.
CMMVC8762E
Cloud snapshots cannot be enabled because there is insufficient memory available for FlashCopy.
CMMVC8763E
Cloud snapshots cannot be enabled because this volume is part of a FlashCopy mapping.
CMMVC8764E
Cloud snapshots cannot be enabled because this volume is part of a Metro Mirror or Global Mirror relationship.
CMMVC8765E
Cloud snapshots cannot be enabled because this is a HyperSwap volume.
CMMVC8766E
Cloud snapshots cannot be enabled because the volume is mirrored between two different pools.
CMMVC8767E
Cloud snapshots cannot be enabled because the volume is being migrated between pools.
CMMVC8768E
Cloud snapshots cannot be enabled because the volume capacity is zero bytes.
CMMVC8769E
Cloud snapshots cannot be disabled because there is a cloud snapshot of the volume in progress.
CMMVC8771E
The specified parameter lists must be of equal length.
CMMVC8772E
The command cannot be completed because the I/O group of the drive class has the maximum number of arrays configured.
CMMVC8773E
Unable to create the array due to insufficient available drives.
CMMVC8774E
An array cannot be created with the drive count, stripe width and rebuild areas entered.
CMMVC8775E
Command cannot be initiated because the distributed array does not have an available rebuild space. Replace failed member drives or swap members occupying rebuild spaces before retrying.
CMMVC8776E
A parameter is not supported for this array type.
CMMVC8777E
The command failed because the maximum number of encryption keys has been reached.
CMMVC8778E
The command failed because the object is the last active copy of its volume.
CMMVC8779E
The provided information was not sufficient to identify a specific volume copy.
CMMVC8780E
The volume copy was not deleted because it is part of a FlashCopy mapping.
CMMVC8810E
The volume was not deleted because it is configured as a change volume for a Remote Copy relationship. Either disassociate the volume from the relationship or use -removefcmaps to force delete the volume, which might result in the loss of data.
CMMVC8782E
The volume copy was not deleted because the copy has an image mode mdisk and a change volume is providing the consistent image.
CMMVC8783E
The volume copy was not deleted because the volume is part of a consistency group.
CMMVC8784E
The command failed because an additional feature activation is required to use remote copy
CMMVC8785E
The command failed because the node does not support encryption, and encryption is required in the IO group.
CMMVC8786E
The node cannot be added because it does not support encryption, and encryption is in use for some SAN MDisks.
CMMVC8787E
The volume was not deleted because it is mapped to a host.
CMMVC8788E
The volume was not deleted because it is part of Metro Mirror or Global Mirror relationship.
CMMVC8789E
The volume was not deleted because it is part of a FlashCopy mapping.
CMMVC8790E
The volume was not deleted because it would result in inconsistent data on an image mode mdisk.
CMMVC8791E
There is already an outstanding certificate request. Use the -force flag to discard the request and then generate a new certificate request.
CMMVC8792E
Cannot install certificate because there is no outstanding certificate request.
CMMVC8793E
Cannot install certificate because it has the wrong key.
CMMVC8794E
Invalid certificate file.
CMMVC8795E
This command is no longer supported. Use the CLI command 'chsystemcert' to manage the SSL certificate for the system.
CMMVC8796E
Cannot make unencrypted MDisk Group as parent MDisk Group [%1] has an encryption key.
CMMVC8797E
Unable to change mdisk property while being part of an MDisk Group with an encryption key.
CMMVC8798E
Cannot add unencrypted MDisk to encrypted MDisk Group
CMMVC8799E
It is not possible to create an encrypted image disk.
CMMVC8800E
Cannot migrate as pool storage_pool is encrypted.
CMMVC8801E
Insufficient drive count specified.
CMMVC8802E
The command failed because the parent pool contains an unencrypted external MDisk.
CMMVC8803E
Stripe width incorrect for RAID type.
CMMVC8804E
The number of rebuild areas specified must be greater than or equal to the rebuild area goal parameter.
CMMVC8805E
An array of this RAID level cannot be created using this drive capacity.
CMMVC8806E
The specified drive count exceeds available drives in the drive class.
CMMVC8807E
A duplicate drive class ID was entered in the list.
CMMVC8808E
Cannot create the encrypted child pool because the parent pool contains an array that is provided by a non-encryption capable IO group.
CMMVC8809E
Cannot create the encrypted child pool because the parent pool contains an unencrypted DRAID array.
CMMVC8811E
The command is not supported for this array type.
CMMVC8812E
The command failed because the existing volume may have only one mirrored copy.
CMMVC8813E
The command failed because the existing volume has mirrored copies in different sites.
CMMVC8814E
The command failed because the existing volume has mirrored copies in storage pools whose site is not 1 or 2.
CMMVC8815E
The command failed because the IO group is not in the same site as the storage pool.
CMMVC8816E
The command failed because the specified FlashCopy mapping is controlled by FlashCopy.
CMMVC8818E
The command failed because the volume already has a copy in the specified site. Use the addvdiskcopy command to add a second copy in the same site.
CMMVC8819E
The volume copy could not be created because the existing source copy is not compressed.
CMMVC8820E
The command failed because the specified volume group did not meet all the requirements to be associated with a Safeguarded policy.
CMMVC8821E
The command failed because a volume group cannot be associated with a Safeguarded policy and have an ownership group.
CMMVC8822E
The command failed because the -retentiondays parameter must be specified when a target volume is a Safeguarded backup.
CMMVC8823E
The command failed because all the FlashCopy mappings in a consistency group must have a Safeguarded backup as their target volume to copy the data.
CMMVC8824E
The command failed because the user's role is not authorized to submit the command.
CMMVC8825E
The command failed because the -backup parameter cannot be specified when the specified volume is a Safeguarded source.
CMMVC8826E
The command failed because the selected volume in the volume group does not meet all the requirement to be a Safeguarded source.
CMMVC8827E
The command failed because with the current user role, the requested action cannot be completed on Safeguarded backups that depend on FlashCopy mapping.
CMMVC8828E
The command failed because an ownership group cannot be assigned to Safeguarded backup location.
CMMVC8829E
The command failed because the -grainsize parameter cannot be specified when the target volume is a Safeguarded backup.
CMMVC8830E
The command failed because with the current user role the requested action cannot be completed on a Safeguarded FlashCopy mapping.
CMMVC8831E
The command failed because the current user role is not authorized to submit the command when FlashCopy consistency group contains Safeguarded FlashCopy mappings.
CMMVC8832E
The command failed because the safeguarded backup start time format is invalid.
CMMVC8833E
The command failed because the predefined Safeguarded policies cannot be modified or removed.
CMMVC8834E
The -copyrate and the -autodelete cannot be modified if the target volume is a Safeguarded FlashCopy mapping.
CMMVC8835E
The command failed because with the current user role, the requested action cannot be completed.
CMMVC8836E
The command failed because the Safeguarded Copy operations are suspended.
CMMVC8837E
The command failed because the Safeguarded backup location that is associated with the Safeguarded source volume cannot be removed.
CMMVC8838E
The command failed because the system does not support Safeguarded Copy.
CMMVC8839E
A target volume in a Safeguarded FlashCopy mapping cannot be mirrored.
CMMVC8870E
The volume was not created because a capacity of zero bytes is not allowed for Hyperswap volumes.
CMMVC8879E
I/O group specified is not present.
CMMVC8880E
Some of the nodes in the cluster/specified IO group are not in online state.
CMMVC8881E
Discovery cannot be run as the source port ID is invalid for one or more nodes in the system or specified iogroup.
CMMVC8882E
Some of the specified source Ethernet ports are not configured for iSCSI use.
CMMVC8883E
Link state is inactive for one or more source Ethernet ports in the system or specified IO group.
CMMVC8884E
IP type mismatch between IP of source ports and target IP specified.
CMMVC8885E
New controller cannot be discovered as limit of managed iSCSI controllers has been reached.
CMMVC8886E
The targetip/ targetip6 parameters do not adhere to the standard IPv4/ IPv6 formats.
CMMVC8887E
Authentication with target controller using the credentials specified did not succeed
CMMVC8888E
Discovery could not start as a connection could not be established to the backend controller.
CMMVC8889E
Discovery could not be completed due to problems at target or initiator.
CMMVC8890E
Sessions cannot be established as there are no discovered controllers for the specified id.
CMMVC8891E
The specified target IP must not refer to the IP of a system management port
CMMVC8892E
The specified target IP must not refer to an iSCSI port on the system
CMMVC8893E
Sessions cannot be established as discovery has not been done through the iogroup specified.
CMMVC8894E
Limit of max IQN+IP tuples per external iSCSI storage system has been reached.
CMMVC8895E
Sessions cannot be established as maximum session count per node has been reached.
CMMVC8896E
One source port cannot have more than one session to the same target IQN through different target ports.
CMMVC8897E
One node cannot have more than one session with same target IQN+IP through different source ports.
CMMVC8898E
Sessions cannot be torn down as the session does not exist.
CMMVC8901E
Enter at least one throttle parameter.
CMMVC8902E
Volume is invalid or does not exist.
CMMVC8903E
Throttle is already associated with this volume.
CMMVC8904E
Throttle parameter missing or invalid.
CMMVC8905E
Offload IO throttle already exists.
CMMVC8906E
Throttle object does not exist.
CMMVC8910E
The specified IP is a reserved or special IP and cannot be used.
CMMVC8911E
Limit of IQNs per target controller has been reached.
CMMVC8912E
The specified Ethernet port is not configured for connectivity with external storage systems.
CMMVC8913E
The port IP address cannot be unconfigured as there are active sessions established to backend controller(s) through the port.
CMMVC8914E
Storage flag cannot be reset as the IP is already in use for backend controller(s) connectivity.
CMMVC8915E
Changing the IP address attributes may cause mdisks to go into a degraded state for some time.
CMMVC8919E
The command failed because the requested transition is invalid.
CMMVC8920E
The command failed because one or more host ports are currently failed over.
CMMVC8922E
The command failed because the volume copies would not be in two independent sites.
CMMVC8923E
The command failed because a volume in a Metro Mirror or Global Mirror relationship cannot have copies in two sites using HyperSwap.
CMMVC8924E
The command failed because the volume already has a copy in the specified site.
CMMVC8925E
The command failed because the cache state for an image mode volume or copy is corrupt.
CMMVC8926E
The volume copy was not deleted because a change volume is providing the consistent image for a copy on the other site.
CMMVC8927E
The requested operation cannot be applied to sra_monitor and sra_privileged.
CMMVC8928E
User names sra_monitor and sra_privileged are reserved, please try again with a different name.
CMMVC8929E
Cannot stop email when support assistance is enabled.
CMMVC8930E
The command failed because the support assistance feature has not been enabled.
CMMVC8931E
Cannot remove email user of usertype support when support assistance is enabled.
CMMVC8932E
Cannot delete email server configurations when support assistance is enabled.
CMMVC8933E
Limit of host clusters has been reached.
CMMVC8934E
Host already belongs to a host cluster.
CMMVC8935E
Host cluster does not exist.
CMMVC8936E
Host cluster has shared mappings. Use -keepmappings or -removemappings flag.
CMMVC8937E
Limit of hosts in the host cluster has been reached.
CMMVC8938E
Host is not part of the host cluster.
CMMVC8939E
Some source Ethernet ports are temporarily unavailable due to failover.
CMMVC8940E
Discovery has not been initiated from nodes of specified site.
CMMVC8941E
Sessions cannot be added to the target controller due to conflict with existing connectivity or discovery output.
CMMVC8942E
The volume copy was not deleted because the volume is part of a FlashCopy mapping. All FlashCopy mappings must be removed from the volume before this copy can be deleted.
CMMVC8943E
The command failed because the consistent image on an image mode copy is being provided by a FlashCopy map.
CMMVC8944E
The command failed because the volume already has copies in two sites using HyperSwap. Use the addvdiskcopy command to add a second copy in the same site.
CMMVC8945E
The command failed because it would allow access to an image mode copy in a Metro Mirror or Global Mirror relationship that does not contain consistent data.
CMMVC8946E
The command failed because an image mode copy is not synchronized with the host-accessible copy.
CMMVC8947E
The target controller is not in the storage layer.
CMMVC8948E
Storwize V7000 Gen1 compatibility mode cannot be disabled because the system contains a Storwize V7000 Gen1 enclosure.
CMMVC8949E
Storwize V7000 Gen1 compatibility mode cannot be reenabled.
CMMVC8950E
Storwize V7000 Gen1 compatibility mode cannot be disabled because it is not in use on this system.
CMMVC8951E
The Storwize V7000 Gen1 control enclosure cannot be added because Storwize V7000 Gen1 compatibility mode is not enabled.
CMMVC8952E
The action failed because there was a mismatch with authentication credentials previously specified for same target.
CMMVC8953E
There are no nodes in the site and/or I/O group specified.
CMMVC8954E
The system is not in the replication layer.
CMMVC8956E
The command failed because the volume is the auxiliary volume in an active-active relationship.
CMMVC8957E
The command failed because the volume specified does not exist.
CMMVC8958E
The command failed because the volume has vVol ownership and may not have copies in two sites using HyperSwap.
CMMVC8959E
The command failed because the master volume has vVol ownership and may not participate in a Remote Copy relationship.
CMMVC8960E
The command failed because the specified node is the last node of the cluster.
CMMVC8961E
The action failed because the node hardware is incompatible with the previous node.
CMMVC8962E
The action failed because the specified node is not online.
CMMVC8964E
The command failed because the support assistance feature has already been enabled.
CMMVC8965E
The command failed because volumes are dependent on the specified node and -permitofflinevolumes was not specified.
CMMVC8966E
This node cannot be added to the IO Group due to having lower configured RAM than required.
CMMVC8967E
The command failed because the auxiliary volume has vVol ownership and may not participate in a Remote Copy relationship.
CMMVC8968E
This operation cannot be completed because iSCSI Initiator sessions are present.
CMMVC8969E
This operation cannot be completed because migration to different parent storage pool is not supported.
CMMVC8970E
The storage pool was not deleted because there are volumes associated with the storage pool. A forced deletion is required.
CMMVC8971E
The command failed because data in the cache has not been committed to disk.
CMMVC8972E
The command failed because the MDisk is an array.
CMMVC8973W
The IO group io_group_name has been restored with ID new_id instead of old_id .
CMMVC8974E
The action failed because of incompatible code.
CMMVC8975E
The node could not be added because of incompatible code. The status code is status_code .
CMMVC8976E
The cluster was not modified because the IP address is not valid.
CMMVC8977E
The action failed because the directory that was specified was not one of the following directories: /dumps, /dumps/iostats, /dumps/iotrace, /dumps/feature, /dumps/config, /dumps/elogs, /dumps/ec or /dumps/pl.
CMMVC8978E
The action failed as the resulting disk size would be less than, or equal to, zero.
CMMVC8979E
The action failed as the resulting disk size would be less than, or equal to, zero.
CMMVC8980E
Metadata recovery can not use the provided MDisk id - invalid or destroyed.
CMMVC8981E
The update failed as a file containing the code for the specified MCP version was not found.
CMMVC8982E
The action failed because the volume is part of a Remote Copy relationship.
CMMVC8983E
The action failed because the volume is part of a FlashCopy mapping.
CMMVC8984E
The FlashCopy mapping or consistency group could not be started in a reasonable time. The mapping or group is instead being prepared.
CMMVC8985E
The command has failed because a virtual medium error exists on the image mode volume or copy.
CMMVC8986E
The command failed as a migrate to image was in progress.
CMMVC8987E
You are trying to recover region data that was created by a code level different from the one you are currently running on the node.
CMMVC8988E
Failed to recreate the cluster you are trying to rebuild.
CMMVC8989E
The FlashCopy mapping was not created or modified because the consistency group already contains the maximum number of mappings.
CMMVC8990E
The Remote Copy relationship was not created because the master or auxiliary volume is a member of a Remote Copy relationship.
CMMVC8991E
The maximum number of hosts for the cluster is already configured.
CMMVC8992E
The maximum number of host/IO group pairs for the cluster is already configured.
CMMVC8993E
The maximum number of WWPNs plus iSCSI qualified names (IQNs) for the cluster is already configured.
CMMVC8994E
The maximum number of hosts for one or more IO groups is already configured.
CMMVC8995E
The maximum number of WWPNs for one or more IO groups is already configured.
CMMVC8996E
The maximum number of WWPNs for the host is already configured.
CMMVC8997E
The host does not belong to one or more of the IO groups specified or inferred.
CMMVC8998E
The host already belongs to one or more of the IO groups specified.
CMMVC8999E
An IO group cannot be removed from a host because of one or more associated volumes.
CMMVC9000E
The action was not completed because the cluster has reached the maximum number of extents in storage pools.
CMMVC9001I
The package installed successfully.
CMMVC9002E
The cluster was recovered and the CLI functionality is limited until the cause of the failure is determined and any corrective action taken. Contact technical support for assistance.
CMMVC9003E
The action failed as the SSH key has been revoked.
CMMVC9004E
The action failed as the SSH key index (SSH_LABEL_ID) is invalid.
CMMVC9006E
This operation cannot be performed because the cluster is currently cancelling the previous update command.
CMMVC9007E
This operation cannot be performed because, either an update has not been started, or an update is in progress but is not in a state where it can be aborted.
CMMVC9008E
The update cannot be cancelled because at least one node has already committed to a new code level.
CMMVC9009E
An invalid response has been entered. The command has not been executed. Input is case sensitive. Enter either yes or no.
CMMVC9010E
The command has not completed. A limited availability parameter has been entered without the required environment setting being set.
CMMVC9011E
The command failed as the remote cluster does not support global mirror.
CMMVC9012E
The copy type differs from other copies already in the consistency group.
CMMVC9013E
The FlashCopy mapping was not prepared because the mapping or consistency group is in the stopping state. The mapping or consistency group must first complete the stop operation and then be prepared
CMMVC9014E
The properties of the FlashCopy mapping were not modified because the mapping or consistency group is in the stopping state.
CMMVC9015E
The FlashCopy mapping was not deleted because the mapping or consistency group is in the stopping state. The mapping or consistency group must be stopped first.
CMMVC9016E
The FlashCopy mapping or consistency group was not started because the mapping or consistency group is in the stopping state. The mapping or consistency group must first complete the stop operation and then be prepared.
CMMVC9017E
The FlashCopy mapping or consistency group was not stopped because the mapping or consistency group is already in the stopping state.
CMMVC9018E
The FlashCopy mapping was not created because the source volume cannot be the target for a FlashCopy mapping.
CMMVC9019E
The FlashCopy mapping was not created because the source volume is already in the maximum number of FlashCopy mappings.
CMMVC9020E
The FlashCopy mapping was not created because the target volume is already a source volume in a FlashCopy mapping.
CMMVC9021E
The FlashCopy mapping was not created because the target volume is already a target volume in a FlashCopy mapping.
CMMVC9022E
The command failed because the authorization table is full.
CMMVC9023E
The command failed because the authorization record was not found or is already set to the default role.
CMMVC9024E
The command failed because the authorization record is not set to the default role. Use rmauth to set the default role.
CMMVC9025E
The command failed because the specified role was not found.
CMMVC9026E
The command failed authorization because the session SSH key is invalid or was deleted.
CMMVC9027E
The task has failed because the user's role is not authorized to submit the command.
CMMVC9028E
The command failed because the specified SSH key was not found. NOTE This command must specify an admin key.
CMMVC9029E
The command cannot set the authorization record to the default role. Use rmauth to set the default role.
CMMVC9030E
The command failed because the SSH key already exists or there is a duplicate SSH key.
CMMVC9031E
The command failed because one of the nodes in the specified I/O group was offline when a memory change was attempted.
CMMVC9032E
The Add E-mail User operation failed because there is no space left in the user list.
CMMVC9033E
The operation failed because there is already a user with that name.
CMMVC9034E
The operation failed because the specified user does not exist.
CMMVC9035E
The Remove E-mail User operation failed because this is the last entry in the user list.
CMMVC9036E
Sendmail error EX_USAGE. A command or configuration line has been used incorrectly.
CMMVC9037E
Sendmail error EX_DATAERR. Address is wrong, or the message is too large for the mailbox.
CMMVC9038E
Sendmail error EX_NOINPUT. An input file (not a system file) did not exist or was not readable.
CMMVC9039E
Sendmail error EX_NOUSER. The sendmail command could not recognize a specified user.
CMMVC9040E
Sendmail error EX_NOHOST. The sendmail command could not recognize the specified host name.
CMMVC9041E
Sendmail error EX_UNAVAILABLE. A required system resource is not available.
CMMVC9042E
Sendmail error EX_SOFTWARE. An internal error occurred (including bad arguments).
CMMVC9043E
Sendmail error EX_OSERR. A system resource error prevented the sending of an email.
CMMVC9044E
Sendmail error EX_OSFILE. Failed to open a critical system file.
CMMVC9045E
Sendmail error EX_CANTCREAT. An output file could not be written to by sendmail.
CMMVC9046E
Sendmail error EX_IOERR. A system I/O error occurred during a sendmail operation. This could be due to a disk failure.
CMMVC9047E
Sendmail error EX_TEMPFAIL. The sendmail command could not create a connection to a remote system.
CMMVC9048E
Sendmail error EX_PROTOCOL. The remote system returned something that was incorrect during a protocol exchange.
CMMVC9049E
Sendmail error EX_NOPERM. The user does not have permission to perform the requested operation.
CMMVC9050E
Sendmail error EX_CONFIG. There is a fatal problem with the sendmail configuration.
CMMVC9051E
An unknown error occurred. Ensure your SMTP server is running.
CMMVC9052E
The email command timed out. Check your email server settings as listed on the cluster.
CMMVC9053E
The email service has not been enabled.
CMMVC9054E
The user specified does not exist.
CMMVC9055E
The command failed because a target volume has dependent FlashCopy mappings.
CMMVC9056E
The create failed because the source and target volumes are members of FlashCopy mappings that have different grain sizes.
CMMVC9061E
Cannot disable key server type because key server objects of this type exist.
CMMVC9062E
Cannot disable key server type because it is not currently enabled.
CMMVC9064E
This host is the only host in the host cluster. The host cluster will lose all of its shared mappings after removing this host. Use -force flag to continue.
CMMVC9065E
Host cluster does not contain any hosts.
CMMVC9066E
Volume already has a shared mapping to the host cluster.
CMMVC9067E
Volume is mapped as a subsidiary LUN (Virtual Volume).
CMMVC9068E
Hosts in the host cluster have conflicting SCSI ID's for their private mappings.
CMMVC9069E
Volume does not have a shared mapping to this host cluster.
CMMVC9070E
Either -keepmappings or -removemappings flag must be specified.
CMMVC9071E
Cannot remove a mapping because it is a shared mapping.
CMMVC9072E
The host cluster mapping was not created because a volume is already mapped to this host cluster with this SCSI LUN.
CMMVC9073E
The host cluster mapping was not created because this volume is mapped to one of the hosts in the host cluster with a different SCSI LUN.
CMMVC9074E
The host cluster mapping was not created because this volume is mapped to a host not in this host cluster. Use -force to create the mapping.
CMMVC9075E
The host cluster mapping was not created because the limit of mapped volumes supported for a host in this host cluster has been reached.
CMMVC9076E
The host cluster mapping was not created because no free SCSI LUN could be found for this shared mapping.
CMMVC9077E
The host cluster mapping was not created because of conflicting SCSI LUNs. One of the hosts in the host cluster already has a mapping to this volume, however, another host in the host cluster has a mapping to a different volume but with the same SCSI LUN.
CMMVC9078E
A volume listed in the -ignoreseedvolume list does not have a mapping to any of the hosts specified in the -seedfromhost list.
CMMVC9079E
Cannot delete all the hosts, because at least one of the hosts has mappings. After deleting all the hosts, all of their mappings will be deleted as well. Use -force flag to continue.
CMMVC9080E
The host cluster I/O group(s) cannot be removed because at least one volume in the I/O group(s) has received I/O within the defined volume protection period.
CMMVC9081E
Duplicate host IDs were entered.
CMMVC9082E
Too many hosts supplied in the list.
CMMVC9083E
A new cloud snapshot could not be created because the volume is not ready.
CMMVC9084W
Volumes that are enabled for cloud snapshots exist without a license for each enclosure.
CMMVC9085E
The command failed because the cloud account is still being initialized.
CMMVC9086E
A new cloud snapshot could not be created because the cloud account configured for the volume is in import mode.
CMMVC9087E
A new cloud snapshot cannot be created because the volume is not enabled for cloud snapshots.
CMMVC9088E
A new cloud snapshot could not be created because the maximum number of cloud snapshots already exists for the volume.
CMMVC9089E
The command failed because no cloud snapshots for the specified volume exist.
CMMVC9090E
The command failed because the specified cloud snapshot does not exist.
CMMVC9091E
The command failed because an existing delete operation is in progress for this volume.
CMMVC9092E
The command failed because the specified cloud snapshot is the most recent complete cloud snapshot for the volume.
CMMVC9093E
The command failed because a restore operation is in progress from this cloud snapshot.
CMMVC9094E
The command failed because a restore operation is in progress from one of the cloud snapshots for this volume.
CMMVC9095E
The command failed because a volume with the UID specified with the -fromuid parameter already exists on the local system.
CMMVC9096E
The command failed because an existing restore operation is in progress on this volume.
CMMVC9097E
The command failed because the specified version of the cloud snapshot is not the latest cloud snapshot for the volume. The -deletelatergenerations parameter must be specified if the latest version of the cloud snapshot is not specified.
CMMVC9098E
The command failed because an existing restore operation is in progress from this volume cloud snapshot.
CMMVC9099E
The command failed because no restore operation is in progress for this volume.
CMMVC9100E
The command failed because there is no uncommitted restore operation for this volume.
CMMVC9101E
The command failed because the -fromuid parameter was specified and the specified local volume has cloud snapshot enabled.
CMMVC9102E
The command failed because the -restoreuid parameter was specified when the existing volume has mappings to hosts.
CMMVC9103E
A restore operation could not be started because the volume is not ready.
CMMVC9104E
A cloud snapshot could not be deleted because the volume is not ready.
CMMVC9105E
The command failed because the local volume is a different size than the specified cloud snapshot.
CMMVC9106E
The command failed because the -createtemporaryvolume option can be used only if the volume is enabled for cloud snapshots.
CMMVC9107E
A temporary volume could not be created for the restore process because there are insufficient free volume IDs or volume copy IDs in the system.
CMMVC9108E
The volume cannot be resized because the volume is enabled for cloud snapshots.
CMMVC9109E
A temporary volume could not be created for the restore process because there is insufficient free capacity in the storage pool.
CMMVC9110E
The restore operation could not be started because the maximum number of FlashCopy mappings in the system has been reached.
CMMVC9111E
The command failed because the specified volume is part of a Metro Mirror or Global Mirror relationship.
CMMVC9112E
The command failed because the specified volume is a HyperSwap volume.
CMMVC9113E
Cloud snapshots are already enabled for the specified volume.
CMMVC9114E
Cloud snapshots cannot be disabled because they are not enabled on this volume.
CMMVC9115E
Cloud snapshots cannot be enabled because the maximum number of cloud snapshot-enabled volumes in the system has been reached.
CMMVC9116E
Cloud snapshots cannot be enabled because the specified cloud account is in import mode.
CMMVC9117E
The volume was not deleted because a cloud snapshot operation is in progress.
CMMVC9118E
The volume was not deleted because a restore operation is in progress and it would allow access to an image mode copy that does not contain consistent data.
CMMVC9119E
The volume copy was not deleted because a restore operation is in progress and it might allow access to an image mode copy that does not contain consistent data.
CMMVC9120E
The remote copy relationship was not created because the master or auxiliary volume is enabled for cloud snapshots.
CMMVC9121E
The change volume could not be associated because the volume is enabled for cloud snapshots.
CMMVC9122E
The FlashCopy mapping was not created because the source or target volume is enabled for cloud snapshots.
CMMVC9123E
The command failed because a key server type has not been enabled.
CMMVC9124E
The command failed because a primary key server already exists.
CMMVC9125E
The command failed because the -primary flag must be set when creating the first ISKLM key server.
CMMVC9126E
The command failed because the -primary flag can only be set for ISKLM key servers.
CMMVC9127E
The command failed because an SSL certificate is required.
CMMVC9128E
Cannot enable key server type because it would exceed the permitted number of enabled key server types.
CMMVC9129E
The command has failed because an IPv4 address was specified and each node does not have an IPv4 service IP address.
CMMVC9130E
The command has failed because an IPv6 address was specified and each node does not have an IPv6 service IP address.
CMMVC9131E
The command failed because the key server reported an error.
CMMVC9132E
This will change the site of at least one host in the host cluster that already has a site defined. Use -force flag to continue.
CMMVC9134E
The command failed because the key server is not supported.
CMMVC9135E
The command failed because there was a problem establishing a connection to the key server.
CMMVC9136E
The command failed because the key server's response was not understood.
CMMVC9137E
The command failed because no primary key server exists.
CMMVC9138E
The command failed because no key servers exist.
CMMVC9139E
The command failed because not all key servers are online.
CMMVC9140E
The key server could not be deleted because it is the only key server of the enabled key server type.
CMMVC9141E
The validate command is not valid for key servers. Use the testkeyserver command to validate a key server.
CMMVC9142E
The command failed because another encryption function is already enabled.
CMMVC9143E
The command failed because the key server reported that the primary has been misconfigured on the system.
CMMVC9144E
The command failed because the system cannot retrieve the current key from the primary key server.
CMMVC9145E
Unable to perform LBA lookup due to unreadable metadata.
CMMVC9146E
Cannot add or remove support center objects when support assistance is enabled.
CMMVC9148E
The command has failed because the default support center cannot be deleted.
CMMVC9157E
The command has failed because the specified secondary expansion module is offline.
CMMVC9158E
The command has failed because the specified display panel is offline.
CMMVC9159E
Host is invalid or does not exist
CMMVC9160E
Throttle is already associated with this host.
CMMVC9161E
Host already has an associated host cluster throttle.
CMMVC9162E
Hostcluster is invalid or does not exist.
CMMVC9163E
Throttle is already associated with this hostcluster.
CMMVC9164E
Host cluster has a member host which has a throttle defined for it.
CMMVC9165E
Mdiskgroup is invalid or does not exist.
CMMVC9166E
Throttle is already associated with this mdiskgroup.
CMMVC9167E
Host and hostcluster already have associated throttles.
CMMVC9168E
Seeding host has a throttle associated with it.
CMMVC9173E
The pool specified is a data reduction pool. Thin provisioned or compressed volume copies created from a data reduction pool must use -autoexpand.
CMMVC9175E
The pool specified is a data reduction pool. Volumes or volume copies which are thin provisioned or compressed and created from a data reduction pool can not be striped specifying an mdisk, sequential or image mode.
CMMVC9176E
The pool specified is a data reduction pool. For volumes or volume copies which are thin provisioned or compressed and created from a data reduction pool, the volume cannot have a cache mode of none or readonly.
CMMVC9177E
The pool specified is a data reduction pool. Thin provisioned or compressed volume copies created from a data reduction pool can not use -noautoexpand.
CMMVC9179E
The command failed as the resource required for a data reduction pool could not be allocated.
CMMVC9180E
The data reduction pool can not be created as the maximum number of data reduction pools already exists.
CMMVC9181E
Data reduction can only be set to on for a parent pool.
CMMVC9184E
The volume specified is a thin or compressed volume in a data reduction pool. Autoexpand must be on and can not be changed.
CMMVC9185E
The volume or volume copy specified is a thin or compressed volume in a data reduction pool and the action requested is not supported on volumes of this type.
CMMVC9186E
The pool specified is a data reduction pool. It is not possible to migrate thin or compressed volumes to a data reduction pool.
CMMVC9190E
The pool specified is a data reduction pool, creating thin or compressed volumes from this type of pool must have autoexpand on.
CMMVC9191E
The command failed because the volume is enabled for cloud snapshots.
CMMVC9193E
The command failed because the system requested for import does not have data in the account.
CMMVC9194E
The command failed because at least one volume is using the account.
CMMVC9195E
The account cannot be deleted because it is being used by volumes.
CMMVC9196E
All available quorum disks are dependent on the sem that you have specified.
CMMVC9197E
Cloud snapshot and restore operations are not allowed because of a generation delete abandon. Use rmvolumebackupgeneration to retry the delete operation.
CMMVC9198E
A previous rmvolumebackupgeneration -all command was abandoned. Use rmvolumebackupgeneration -all to retry the delete operation.
CMMVC9199E
A previous rmvolumebackupgeneration or cloud restore with -deletelatergenerations command was abandoned. Use rmvolumebackupgeneration specifying the lowest deleting generation to retry the delete operation.
CMMVC9202E
The task failed because the volume is part of a Metro Mirror or Global Mirror relationship to a system which is running software which does not support resize of volumes in a relationship.
CMMVC9203E
The expandvdisksize task failed because there is not enough memory available for this feature.
CMMVC9204E
The task failed because the volume is part of a relationship that is configured to operate in Global Mirror in cycling mode.
CMMVC9205E
The task failed because the volume is part of a HyperSwap relationship.
CMMVC9206E
The task failed because the volume is part of a relationship that is not consistent_synchronized.
CMMVC9207E
The task failed because the volume being expanded is a primary in a Metro Mirror or Global Mirror relationship and would make the primary volume size different than the secondary volume size.
CMMVC9208E
The task failed because the volume being expanded is a secondary in a Metro Mirror or Global Mirror relationship and has already been expanded so is larger than the associated primary volume.
CMMVC9209E
The task failed because the volume being shrunk is a secondary in a Metro Mirror or Global Mirror relationship and would make the secondary volume size different than the associated primary volume.
CMMVC9210E
The task failed because the volume being shrunk is a primary in a Metro Mirror or Global Mirror relationship and has already been shrunk so is already smaller than the associated secondary volume.
CMMVC9211E
Cannot perform task because primary is different size to the secondary.
CMMVC9212E
Cannot perform task because one or more of the primaries is a different size to the corresponding secondary
CMMVC9215E
The action failed as the tier cannot be changed for MDisks from this controller.
CMMVC9218E
The action failed because remote support is either in connected or active state.
CMMVC9219E
The command failed because the remote support feature has already been enabled.
CMMVC9220E
The command failed because the name of the support center started with the prefix associated with default support centers.
CMMVC9224E
The command failed because the specified node is not a part of the site or I/O group specified, or both.
CMMVC9225E
The command failed because the maximum limit for the initiator node-specific authentication credentials was exceeded.
CMMVC9226E
The command failed because the specified iSCSI storage port is configured for single username/password credentials across all nodes. Per SVC node credentials cannot be specified.
CMMVC9227E
The command failed because the specified iSCSI session does not exist.
CMMVC9228E
The command failed because some parameters are missing or invalid parameters were entered.
CMMVC9230E
The command failed because the system cannot retrieve the current key from a USB flash drive.
CMMVC9231E
The command failed because a USB rekey operation is in progress.
CMMVC9232E
The command failed because a key server rekey operation is in progress.
CMMVC9233E
The command failed because a USB rekey operation is required.
CMMVC9234E
The command failed because the cloud account is in import mode.
CMMVC9235E
The pool specified is a data reduction pool. Volumes or volume copies which are thin provisioned and created from a data reduction pool can not use the -grainsize parameter.
CMMVC9236E
The pool specified is a data reduction pool. Volumes or volume copies which are thin provisioned and created from a data reduction pool can not use the -warning parameter.
CMMVC9237E
The volume specified is a thin or compressed volume in a data reduction pool. Cache can not be set to none or readonly.
CMMVC9238E
The volume specified is a thin volume in a data reduction pool. The -warning parameter can not be used.
CMMVC9240E
The action requested is not supported on volumes or volume copies in data reduction pools.
CMMVC9241E
The action cannot be completed because the Quorum device is unavailable.
CMMVC9242E
The volume or volume copy specified is a thin or compressed volume in a data reduction pool. Thin provisioned or compressed volume copies created from a data reduction pool can not use the -rsize parameter.
CMMVC9243E
Node VPD is unavailable for inactive spare nodes. Use sainfo lsservicenodes instead.
CMMVC9245E
The pool specified is a data reduction pool and the IO group selected already contains compressed volumes within a regular pool. An IO group using software compression can not contain compressed volumes from regular and data reduction pools at the same time.
CMMVC9246E
The pool specified is a regular pool and the IO group selected already contains compressed volumes within a data reduction pool. An IO group using software compression can not contain compressed volumes from regular and data reduction pools at the same time.
CMMVC9247E
The pool specified is a data reduction pool. Thin or compressed volumes or volume copies in data reduction pools cannot have the easytier status set or changed.
CMMVC9248E
The volume or volume copy specified is a thin or compressed volume in a data reduction pool. The easytier status cannot be changed.
CMMVC9249E
Data reduction pools can not have child pools.
CMMVC9250E
The pool specified is a data reduction pool. Thin provisioned or compressed volume copies created from a data reduction pool can not use the -buffersize parameter.
CMMVC9251E
The command failed because the -deletelatergenerations parameter was specified and the specified local volume has cloud snapshot not enabled.
CMMVC9252E
The command failed because the I/O group contains compressed volumes. The new hardware configuration does not support compressed volumes.
CMMVC9253E
An IO group using software compression can not contain compressed volumes from regular and data reduction pools at the same time.
CMMVC9254E
The command failed because the maximum number of spare nodes have already been assigned to this cluster.
CMMVC9256E
The specified node is not an active spare node.
CMMVC9257E
The command failed because -deactivatespare was not specified.
CMMVC9258E
The command failed because -deactivatespare was specified.
CMMVC9259E
The upgrade is currently not paused
CMMVC9260E
The command failed because the specified node has been replaced by a spare.
CMMVC9261E
The command failed because the specified node does not have a status of candidate.
CMMVC9262E
The pool specified is a data reduction pool. The action requested is not supported with pools of this type.
CMMVC9264E
The task failed because unable to format the newly expanded area in the original volume's last grain
CMMVC9265E
The volume specified has a thin or compressed volume copy in a data reduction pool. Thin provisioned or compressed volumes created from a data reduction pool can not use -size parameter to reduce the size of the volume.
CMMVC9266E
The command has failed because specified host port group id is different from the failover port's host port group id.
CMMVC9267E
The command has failed because more than 4 ports are being assigned the same host port group id.
CMMVC9268E
Network connection refused.
CMMVC9269E
The specified storage was not found.
CMMVC9270E
Invalid username or key.
CMMVC9271E
Storage access control error, possibly due to duplicate iSCSI qualified name (IQN) on IBM Cloud.
CMMVC9272E
The specified storage has already been configured.
CMMVC9273E
The specified storage is already in use by another cluster.
CMMVC9274E
Some of the serial numbers are not correct.
CMMVC9277E
The command failed because there are out of sync volume mirrors and some copies are in data reduction pools that may also be deleted.
CMMVC9279E
The task failed because there is no up-to-date node in the IO group that contains the volume.
CMMVC9280E
The command did not complete because creating mirror bitmap is not finished within the allotted time period.
CMMVC9281E
One or more of the nodes in the selected I/O group has no working compression hardware.
CMMVC9282E
The specified iSCSI Storage port uses per node credentials. Resetting credentials for all nodes can temporarily cause MDisks to go offline. Use the -force option to make this change.
CMMVC9283E
The command failed because one of the storage pools for the volume is a data reduction pool that has insufficient capacity.
CMMVC9284E
The command failed because the pool specified is a data reduction pool that contains offline volumes.
CMMVC9285E
A thin or compressed volume in a data reduction pool cannot be created within this I/O group because the amount of memory configured for FlashCopy is greater than 1.5 gigabytes (GB) and there is insufficient free memory in the I/O group.
CMMVC9286E
The amount of memory configured for FlashCopy cannot be greater than 1.5 gigabytes (GB) because data reduction volumes exist in this I/O group
CMMVC9287E
The volume or volume copy cannot be deleted because the data reduction pool is corrupt.
CMMVC9288E
The node could not be added as a data reduction pool containing a thin or compressed volume exists within this I/O group and the new node does not meet the minimum CPU requirements.
CMMVC9289E
The command failed because the drives selected have an incompatible combination of technology type and transport protocol.
CMMVC9290E
The mkarray command failed because -level raid5 and raid6 are not supported by this IO group.
CMMVC9291E
Task failed because volume is non-mirrored with fully allocated copy and is part of a Metro Mirror or Global Mirror relationship with -nofmtdisk specified
CMMVC9292E
An IO group can not contain deduplicated volumes or volume copies in data reduction pools at the same time as compressed volumes or volume copies in regular storage pools.
CMMVC9294E
Unable to add host to storage.
CMMVC9295E
The command failed because this raid level is not supported with compressed drives.
CMMVC9296E
The command has failed because the volume logical block address (LBA) supplied is not recoverable and contains a virtual medium error.
CMMVC9298E
The command has failed because there is already an analysis in progress on the specified volume.
CMMVC9299E
The command has failed because there is not an analysis in progress on the specified volume.
CMMVC9300E
The specified IO group does not support deduplication.
CMMVC9301E
One of the pools specified is not a data reduction pool and cannot be used to create a deduplicated volume or volume copy.
CMMVC9302E
The command failed because it is not possible to mix compressed and non-compressed drives in an array.
CMMVC9303E
The command failed because one or more required drives did not complete format.
CMMVC9304E
The command failed because the driveclass does not support the specified number of rebuild areas.
CMMVC9305E
The Cloud Call Home feature is not supported on this platform.
CMMVC9306E
The Cloud Call Home feature is not enabled.
CMMVC9307E
No response from the Cloud Call Home service.
CMMVC9308E
The command failed because the requested certificate is incompatible with the current SSL protocol level.
CMMVC9309E
The command failed because the SSL protocol level is incompatible with the current system certificate.
CMMVC9310E
The command failed because one or more drive format was still in progress.
CMMVC9312E
The command failed because a compressed drive cannot be exchanged with a compressed drive of a different drive class.
CMMVC9315E
The create failed because there are no IO groups supporting deduplication.
CMMVC9316E
The create failed because there are no IO groups supporting deduplication in site
CMMVC9318E
Compressed volumes in the selected I/O group must be in a data reduction pool.
CMMVC9319E
Volumes or volume copies which are thin provisioned or compressed and created from a data reduction pool can only be repaired with the assistance of support.
CMMVC9321E
Inventory data is not yet available. Please retry the command in a few minutes.
CMMVC9323E
The command failed because the specified host protocol is not compatible with the specified port type.
CMMVC9324E
The command failed because the specified host type is not compatible with the specified protocol.
CMMVC9325E
The command failed because the maximum number of host ports for the system would be exceeded.
CMMVC9326E
The command failed because the maximum number of host ports for an I/O group would be exceeded.
CMMVC9327E
The command failed because the maximum number of NQNs for an I/O group would be exceeded.
CMMVC9328E
The command failed because one of the specified NQNs is already assigned to a host.
CMMVC9329E
The command failed because the specified host type is not compatible with the current host protocol.
CMMVC9330E
The command failed because the specified host protocol is not compatible with the current host type.
CMMVC9331E
The host protocol cannot be changed because the host has ports configured.
CMMVC9332E
The host protocol cannot be changed because there are volumes mapped to the host.
CMMVC9334E
The command failed as the volume is already mapped to host/s with a protocol inconsistent with the specified host.
CMMVC9335E
The command failed as the -scsi parameter is not supported for hosts with protocol set as NVMe.
CMMVC9336E
The command failed because the system does not support NVMe host attachment.
CMMVC9337E
The command failed because the specified port type is not compatible with the host protocol.
CMMVC9338E
The command failed because the maximum number of ports for the host would be exceeded.
CMMVC9339E
The command failed because the maximum number of NQNs for the host would be exceeded.
CMMVC9340E
The command failed because the specified NQN is not assigned to the specified host.
CMMVC9341E
The command failed because Source IP Address specified via -src_ip parameter does not exist or port id specified via -src_port_id parameter does not exist.
CMMVC9342E
The command failed because Node ID specified via -node_id parameter does not exist or is in OFFLINE state.
CMMVC9343E
The command failed because the host protocol does not match the existing hosts in the host cluster.
CMMVC9344E
The command failed because the protocols of the specified hosts are different.
CMMVC9345E
The host protocol cannot be changed because the host is a member of a host cluster.
CMMVC9352E
The command failed as the volume is already mapped to hosts with a protocol inconsistent with the specified host cluster.
CMMVC9353E
The command failed as the -scsi parameter is not supported for host clusters with protocol set as NVMe.
CMMVC9354E
The command failed because the array has an expansion ongoing.
CMMVC9355E
The command failed because the array has a member resync ongoing.
CMMVC9356E
The command failed because an array in the parent pool has an expansion ongoing.
CMMVC9357E
The command failed because the array does not support expansion.
CMMVC9358E
An unknown error condition occurred while setting up the self encrypting drives.
CMMVC9359E
The command failed because the system has reached the maximum number of ongoing expansions.
CMMVC9360E
The command failed because the array specified is offline.
CMMVC9361E
The command failed because the array has rebuild areas in use
CMMVC9362E
The command failed because authentication credentials are not set by chiscsiportauth CLI.
CMMVC9363E
The command failed because the array specified has a component in doubt.
CMMVC9364E
The command failed because the array status was not stable when the command was executed. Please retry the command if you want to carry on with the expansion.
CMMVC9365E
The node cannot be removed because it would result in an I/O group outage. Use -force flag to override.
CMMVC9366E
The command failed because the additional drive count must exceed the additional rebuild area count.
CMMVC9368E
The command failed because the additional rebuild area count would result in the array exceeding the maximum rebuild area count.
CMMVC9369E
The command failed because there are no IO groups that support both compression and deduplication
CMMVC9370E
The command failed because there are no IO groups that support both compression and deduplication in site site_id.
CMMVC9371E
The command failed because the I/O group specified is not in the same site as the storage pool.
CMMVC9372E
The command failed because the storage pool specified is not in the same site as the volume.
CMMVC9373E
The command failed because the drive is only supported for Distributed Arrays, which do not use spares.
CMMVC9374E
The command failed because volume mappings exist and the host is a member of a host cluster.
CMMVC9375E
The command failed because the volume is already mapped to another host. Use -force to create the mapping.
CMMVC9376E
The node could not be added as the code level of new node is different with the code level of the cluster in this platform.
CMMVC9377W
There are dependent FlashCopy mappings not in your ownership group.
CMMVC9378E
The command failed because the specified ownership group is associated with one or more objects. To continue specify -keepobjects.
CMMVC9379E
The command failed because it cannot be executed by a user in an ownership group.
CMMVC9380E
The command failed because quorum site cannot be set in standard quorum mode.
CMMVC9381E
The required update package can not be found and downloaded from the support server in this platform.
CMMVC9383E
The command failed because changing MTU value is not allowed for ethernet port which is already configured for RDMA clustering.
CMMVC9384E
The command failed because the specified ownership group does not exist.
CMMVC9385E
The command failed because one or more parameters cannot be specified by a user in an ownership group.
CMMVC9386E
The command failed because it would result in inconsistent ownership groups and the -inconsistentownershipgroup parameter was not specified.
CMMVC9387E
The command failed because the seeding hosts are in more than one ownership group.
CMMVC9388E
The command failed because seeding hosts were owned and that ownership group needs to be specified using the -ownershipgroup parameter.
CMMVC9389E
The command failed because there are already max iSCSI (initiator + target) sessions present on node.
CMMVC9390E
The command failed because the SecurityAdmin group and ownership groups are mutually exclusive.
CMMVC9391E
The command failed because the thin provisioned array is write protected.
CMMVC9392E
The command failed because the cache state for a volume or copy is corrupt.
CMMVC9393E
The network is unreachable.
CMMVC9394E
The node is not authorized to complete this operation.
CMMVC9395E
The specified local managed disk is not in a valid state.
CMMVC9396E
The system already manages the maximum number of local managed disks.
CMMVC9397E
The local managed disks were not attached to the node in the allotted time.
CMMVC9399E
The command failed because the EasyTier FCM over allocation max ratio is out of range.
CMMVC9402E
The SCSI LUN ID currently allocated to the volume mapping is not available in all of the new access IO groups.
CMMVC9403E
The SCSI LUN IDs currently allocated to the volume mapping are different in existing access IO groups.
CMMVC9404E
An identical SCSI LUN ID is not available in all access IO groups.
CMMVC9405E
The command failed as the -allowmismatchedscsiids parameter is not supported for hosts with protocol set as NVMe.
CMMVC9406E
The FlashCopy mapping or consistency group could not be started as a target volume has received I/O within the defined volume protection period.
CMMVC9407E
The Remote Copy relationship could not be created as the specified secondary volume has received I/O within the defined volume protection period.
CMMVC9408E
The volume snapshot could not be restored as the volume has received I/O within the defined volume protection period.
CMMVC9409E
The volume caching IO group must be included in the volume access IO group set.
CMMVC9410E
The new caching IO group for the volume must be in the volume access set.
CMMVC9411E
The volume caching IO group cannot be removed from the volume access IO group set.
CMMVC9412E
The command failed because cloud call home requires an active connection.
CMMVC9413E
Cloud call home failed to send remote support assist information.
CMMVC9420E
The storage pool cannot be deleted because it has an out of sync volume copy in a storage pool with volume protection active, this copy will be deleted and the volume has received I/O within the defined volume protection period.
CMMVC9439E
The command failed because the thin provisioned array does not have sufficient free physical capacity to start expansion.
CMMVC9440E
The command failed because the snmp engine id format is invalid.
CMMVC9441E
The command failed because a post-update background task is in progress.
CMMVC9442E
The command failed because the specified volume is not a HyperSwap® volume.
CMMVC9443E
The command failed because the volume is part of a Remote Copy consistency group.
CMMVC9444E
The command failed because the volume is part of a FlashCopy mapping.
CMMVC9445E
The command failed because not all copies of the volume are synchronized.
CMMVC9446E
The command failed because there is not enough memory available for the Remote Copy feature in I/O group ID [%1].
CMMVC9447E
The command failed because there is not enough memory available for the FlashCopy feature in I/O group ID [%1].
CMMVC9448E
The command failed because there is not enough memory available for the Mirroring feature in I/O group ID [%1].
CMMVC9449E
The command failed because the volume has one or more fully allocated copies.
CMMVC9450E
The command failed because the volume has multiple copies in a site.
CMMVC9451E
The command failed because the last grain of a volume copy has not been fully formatted.
CMMVC9452E
The command failed because the volume has one or more image mode copies.
CMMVC9453E
The command failed because there are nodes offline or because there are unrecovered Remote Copy relationships or FlashCopy mappings.
CMMVC9454E
The command failed because one or more HyperSwap volumes have a copy or a change volume in this pool that must be removed first.
CMMVC9455E
The command failed because both [-engineid] and [-securityname] are required to change to version 3 security.
CMMVC9456E
The command failed because both [-authprotocol] and [-authpassphrase] are required to set up snmp authentication.
CMMVC9457E
The command failed because authentication must be setup if privacy is to be used.
CMMVC9458E
The command failed because both [-privprotocol] and [-privpassphrase] are required to set up snmp privacy.
CMMVC9459E
The command failed because the total drive count adds more drives than it is supported to add in a single expansion at this distributed RAID array level
CMMVC9460E
The command failed because the total drive count is less or equal to the current drive count.
CMMVC9461E
The command failed because the total rebuild area count is less than the current rebuild area count.
CMMVC9463E
The command failed because the specified driveclass does not meet or exceed the goals of the array. Please select a driveclass with lscompatibledriveclass.
CMMVC9470E
The command failed because the FlashCopy map concerned is associated with an access point.
CMMVC9471E
The command failed because remote users cannot specify a password.
CMMVC9473E
The command failed because the superuser password must be changed before the system can be configured.
CMMVC9474E
The command failed because an insecure password was chosen.
CMMVC9475E
The node cannot be added because it does not support compressed volume copies in a standard storage pool.
CMMVC9476E
The command failed because one or more options are not allowed for 3site RC Relationships.
CMMVC9477E
The command failed because one or more options are not allowed for 3site RC Consistency Groups.
CMMVC9478E
Orchestrator service is inactive.
CMMVC9479E
All mutually inclusive parameters should be present.
CMMVC9480E
Object list must contain exactly one object from each of the three sites.
CMMVC9481E
3-Site Orchestrator is busy processing another command.
CMMVC9482E
Specified IP address [%s] is not a valid SVC cluster IP address.
CMMVC9483E
Specified 3-site remote copy consistency group does not exist.
CMMVC9484E
Maximum number of 3-site remote copy consistency group limit has been reached.
CMMVC9485E
One or more sites are unreachable.
CMMVC9486E
This CLI action is not supported by orchestrator.
CMMVC9491E
Specified 2-site remote copy relationship does not exist.
CMMVC9492E
Specified volume name already exists on the auxiliary-far site.
CMMVC9493E
Failed to create 3-site configuration file.
CMMVC9496E
Specified cluster IPs [%1] and [%2] do not belong to same SVC cluster.
CMMVC9497E
Each pair of sites must have a valid remote copy partnership configured.
CMMVC9498E
Specify IP addresses for 3 different SVC clusters.
CMMVC9499E
Specified user is not a valid 3SiteAdmin user.
CMMVC9500E
3-site configuration already exists.
CMMVC9501E
3-site configuration does not exist.
CMMVC9503E
3-site configuration cannot be removed if it has 3-site consistency groups.
CMMVC9505E
SSH Authentication failed with site [%s].
CMMVC9507E
SSH Connection failed with site [%s].
CMMVC9510E
Enter at least one parameter.
CMMVC9511E
Failed to remove 3-site configuration backup file.
CMMVC9513E
Specified cycling period is invalid.
CMMVC9514E
A partially converted relationship already exists in 3-site consistency group.
CMMVC9515E
Specified periodicsrc or cycleperiod does not match.
CMMVC9516E
Invalid periodic source or target specified.
CMMVC9518E
State or type of specified 3-site consistency group is not valid.
CMMVC9519E
Specified relationship must be part of a remote copy consistency group.
CMMVC9520E
Specified 3-site remote copy consistency group is in partial state.
CMMVC9521E
3-site consistency group is processing another configuration change command.
CMMVC9522E
3-site remote copy consistency group was partially converted.
CMMVC9523E
State or type of specified relationship is not valid.
CMMVC9524E
Another relationship is being added to 3-site consistency group.
CMMVC9525E
Specified 2-site remote copy relationship is not a standalone relationship.
CMMVC9526E
Specified relationship attributes do not match with target 3-site consistency group.
CMMVC9527E
Specified relationship must be present between near sites in 3-site configuration.
CMMVC9528E
Specified site is not a suitable candidate.
CMMVC9529E
Specified relationship is already being added to given 3-site consistency group.
CMMVC9546E
The host port cannot be added as a host cannot have both iSCSI names and WWPNs.
CMMVC9564E
3-Site Orchestrator crash recovery failed.
CMMVC9568E
The command failed because only svctask applysoftware -abort is allowed.
CMMVC9571E
Two channel start failed because of interruption.
CMMVC9573E
Cannot add accesspoint to HyperSwap volume because change volumes haven't been configured.
CMMVC9574E
This command failed because the links that are specified in the partnership are not valid. .
CMMVC9575E
The command failed because [-encrypt] is not applicable for a data reduction child pool
CMMVC9576E
Cannot create a child pool of a different type to the parent pool
CMMVC9577E
The command failed because the argument [-noquota] is not applicable
CMMVC9578E
The argument [-size] is not applicable for a data reduction child pool
CMMVC9579E
Cannot remove a data reduction child pool with associated volumes.
CMMVC9580E
The command failed because the password does not meet the minimum length requirement.
CMMVC9581E
The command failed because strip value 128 is no longer supported, strip value 256 should be used instead.
CMMVC9583E
The command failed because a user cannot lock their own account.
CMMVC9584E
The command failed because the specified user cannot be locked.
CMMVC9585E
The command failed because the identical link portset IDs or portset names are specified for a partnership.
CMMVC9587E
The command failed because a host can only be added to a host cluster with the same ownership group.
CMMVC9588E
The command failed because a parent pool cannot be assigned an ownership group.
CMMVC9589E
Invalid flag, must be 3SiteAdmin user
CMMVC9590E
The command failed because the argument [-warning] is not applicable for a quotaless child pool.
CMMVC9597E
The command failed because the invalid portset ID or the portset name was specified for the IP partnership.
CMMVC9598E
The command failed because an both the portsets cannot be removed from the partnership.
CMMVC9601E
The command failed because volume has image mode copy.
CMMVC9602E
The command failed because volume has formatting corrupt copy.
CMMVC9603E
The command failed because unable to resize the bitmap for the volume.
CMMVC9604E
The command failed because the current user's password has expired and must be changed.
CMMVC9605E
The command failed because superuser locking is only supported on platforms with a dedicated technician port.
CMMVC9609E
The command failed because the specified user is locked.
CMMVC9610E
The command failed because users cannot remove themselves.
CMMVC9611E
The command failed because the maximum limit for IP addresses with the gateway per physical port is reached. Use another Ethernet port to configure an IP address with gateway.
CMMVC9612E
The command failed because the port is disabled for the connection type specified by the portset.
CMMVC9613E
Sharing IP addresses across different Ethernet ports are not allowed.
CMMVC9614E
Shared IP addresses must have an identical VLAN.
CMMVC9615E
-shareip applies to 2 different portsets. You cannot share IP address within the same portset.
CMMVC9616E
The command failed because the maximum limit of IP addresses on a node is reached. Use another node_id for the IP allocation.
CMMVC9617E
The command failed because the maximum limit of IP addresses that can be associated to an Ethernet port ID is reached. Use another portset ID for IP allocation.
CMMVC9618E
The command failed because the maximum limit of IP addresses that can be associated to a portset ID is reached. Use another portset ID for IP association.
CMMVC9619E
Mixing IP address types within an IP replication type portset is not allowed.
CMMVC9620E
The command failed because multiple IP addresses from a port are not allowed with the same portset.
CMMVC9623E
The system update test utility has not been run recently. Run the system update test utility using the drive test options and ensure that no fatal drive errors are outstanding before attempting this command again.
CMMVC9624E
The system update test utility has found fatal errors related to all the drives selected for upgrade.
CMMVC9625E
The command failed because the password entered matches a previously used password.
CMMVC9626E
The command failed because the password has been recently changed. Users must wait [%1] days between password changes.
CMMVC9627E
The command failed because the password history feature is not supported on this platform.
CMMVC9628E
The command failed because superuser locking cannot be enabled while superuser password reset is disabled.
CMMVC9629E
The command failed because superuser password reset cannot be disabled while superuser locking is enabled.
CMMVC9630E
The command failed because this IP address is the last live connection to backend storage controller.
CMMVC9631E
The command failed because last IP address in the host-attach portset is linked with the host object.
CMMVC9632E
The command failed because an IPv4 or IPv6 address is associated with remote service portset that is used by an active partnership.
CMMVC9633W
Your password has expired. It must be changed now.
CMMVC9634W
Your password will expire in %1 days.
CMMVC9635E
The command failed because the number of lower case characters supplied does not meet the system policy.
CMMVC9636E
The command failed because the number of upper case characters supplied does not meet the system policy.
CMMVC9637E
The command failed because the number of numeric characters supplied does not meet the system policy.
CMMVC9638E
The command failed because the number of special characters supplied does not meet the system policy.
CMMVC9651E
Cannot activate new hardware configuration because additional memory is installed.
CMMVC9652E
The command failed because no recent node statistics file was found.
CMMVC9653E
Cluster topology for specified master is not hyperswap.
CMMVC9654E
Shared IP addresses must have identical gateway.
CMMVC9655E
Shared IP addresses must have identical prefix.
CMMVC9656E
The IP address that is not configured in the system cannot be shared.
CMMVC9657E
The command failed because only a single IP partnership is allowed with the remote-copy systems at software version before 8.4.2.0.
CMMVC9658E
The command failed because the VDisk is the source volume of an incremental FlashCopy mapping and the target VDisk of such mapping cannot be smaller than the source.
CMMVC9659E
The command failed because a non-mirrored volume cannot be expanded with the -nofmtdisk parameter if the volume is the source or target volume of an incremental FlashCopy mapping.
CMMVC9660E
One or more of the volumes are the source VDisk of an incremental FlashCopy mapping and the target VDisk of such mapping cannot be smaller than the source VDisk.
CMMVC9661E
The VDisk cannot be expanded because it is associated with a FlashCopy mapping that cannot be expanded.
CMMVC9662E
The command failed because the VDisk is the target volume of more than one incremental FlashCopy mapping.
CMMVC9663E
The command failed because the FlashCopy mapping cannot be started if the source volume and the target volume have different virtual sizes.
CMMVC9664E
The FlashCopy consistency group cannot be started because one or more mappings in the group have different virtual capacity.
CMMVC9665E
The action failed because the -activeactive parameter is not supported.
CMMVC9666E
The command failed because the specified parent storage pool already has a Safeguarded backup location.
CMMVC9667E
The -owner parameter cannot be specified when a new child pool created into a Safeguarded backup location.
CMMVC9669E
The action failed because the virtual disk is a part of a HyperSwap volume.
CMMVC9670E
A portset must be empty and unmapped from the host or partnership objects before deletion.
CMMVC9671E
The command failed because portset of type replication can be owned and created by global owner only.
CMMVC9672E
The command failed because new portset of type storage cannot be created.
CMMVC9673E
The command failed because the specified parameters of portset type storage or replication cannot be modified.
CMMVC9674E
The command failed because the port is in use by one or more portsets of this type.
CMMVC9675E
The command failed because not all the volumes in the volume groups belong to parent pools that have a Safeguarded backup location (child pool).
CMMVC9677E
The command failed because the selected parameters cannot have their values as 0 if the specified volume groups are Safeguarded backup locations.
CMMVC9678E
The command failed because the selected parameters cannot be used if the specified volume groups are Safeguarded backup locations.
CMMVC9679E
The command failed because some of the required parameters are not specified when the storage pool is a Safeguarded backup location.
CMMVC9681E
The command failed because multiple I/O groups cannot be configured when the preferred access node is detected.
CMMVC9682E
The command failed because default portset 0 and portset 3 cannot be removed by any ownership group user.
CMMVC9683E
The VDisk cannot be shrunk because it is associated with a FlashCopy mapping that cannot be shrunk.
CMMVC9684E
A VDisk cannot be shrunk if it is the target of a FlashCopy mapping.
CMMVC9685E
The VDisk cannot be shrunk because it has dependent FlashCopy mappings with a starting virtual capacity that is larger than the proposed virtual capacity.
CMMVC9686E
The pool specified is a Safeguarded backup location. The action requested is not supported with pools of this type
CMMVC9687E
The command failed because the maximum limit of per node IP addresses associated with the replication portset is reached.
CMMVC9688E
The addvolumecopy command cannot be used to add a mirror copy to Safeguarded backup if the topology system is not standard.
CMMVC9690E
The volume cannot be expanded as it is in a migration relationship.
CMMVC9691E
The relationship type was not changed as migration relationships cannot be changed.
CMMVC9692E
The relationship was not added to the consistency group as migration relationships do not support consistency groups.
CMMVC9693E
The change volume was not associated as migration relationships do not support change volumes.
CMMVC9695E
The command failed because the Safeguarded policy is associated with one or more volume groups.
CMMVC9696E
The command failed because an IP partnership requires at least one link to be specified.
CMMVC9697E
The relationship cannot not be created as migration relationships are only allowed to be created to a remote system.
CMMVC9698E
The relationship could not be started as migration relationships do not support the -clean flag
CMMVC9699E
The command failed because the provided portset object is not a type of host attach.
CMMVC9700E
The command failed because the argument [-removefromvolumegroups] is not allowed for the current user role.
CMMVC9703E
Host and portset object ownership must match. Restricted owner of the host object can be mapped to globally owned portset.
CMMVC9704E
The system is unable to generate encryption keys.
CMMVC9706E
The command failed because ODX cannot be set whilst a migration relationship exits.
CMMVC9707E
The command failed because the specified provisioning policy does not exist
CMMVC9708E
The command failed because a host using the NVMe protocol was not mapped to a migration relationship volume.
CMMVC9709E
The relationship could not be stopped as migration relationships do not support the -access flag.
CMMVC9710E
The migration relationship could not be created as the master system has ODX enabled.
CMMVC9711E
The migration relationship could not be created as the aux system has ODX enabled.
CMMVC9712E
The migration relationship could not be created as the master volume is using persistent reservations and migration of volumes using persistent reservations is unsupported.
CMMVC9713E
The migration relationship could not be created as the master volume is mapped to a host using the NVMe protocol.
CMMVC9714E
The command failed because the new portset does not have an overlapping port so this action can cause a host outage. Specify a portset with one or more common ports or turn off VDisk protection to force the change.
CMMVC9715E
The command failed because the auxiliary volume has host mappings.
CMMVC9716E
The command failed because the secondary volume was not mapped to an online host.
CMMVC9717E
The command failed because the specified provisioning policy has incompatible properties with the specified properties for the pool.
CMMVC9718E
The source and the target volumes in a FlashCopy mapping must have the same preferred node.
CMMVC9719E
The command failed because the source and the target volumes in a FlashCopy mapping are not in the same parent storage pool.
CMMVC9720E
The command failed because a Safeguarded Policy is not assigned to the source volume.
CMMVC9721E
The command failed because the volume is a target volume of an existing FlashCopy mapping.
CMMVC9722E
The command failed because the -autodelete parameter cannot be specified when the target volume is a Safeguarded backup.
CMMVC9724E
The command failed because the -iogrp parameter cannot be specified when the target volume is a Safeguarded backup.
CMMVC9725E
Cannot create a distributed RAID array with this number of member drives for this drive class.
CMMVC9726E
The command failed because migration relationships can not be deleted. Use rmvolume to delete the secondary volume instead.
CMMVC9727E
The command failed because the volume is the primary in a migration relationship. The secondary volume must be deleted first.
CMMVC9728E
The command failed because the volume is in a migration relationship and should be deleted using rmvolume.
CMMVC9729E
The command failed because the managed disk (MDisk) is not compatible with the provisioning policy that is associated with the storage pool.
CMMVC9730E
The command failed because the specified pools use different provisioning policies.
CMMVC9731E
The migration relationship could not be created because the UUID already exists on the remote cluster.
CMMVC9733E
The command failed because a multi-factor authentication service is already enabled.
CMMVC9732E
The command failed because the portset must be empty and unmapped from host, partnership, or storage objects before deletion.
CMMVC9733E
The command failed because a multi-factor authentication service is already enabled.
CMMVC9734E
The command failed because there are users or user groups configured to use the multi-factor authentication service.
CMMVC9735E
The command failed because the multi-factor authentication credentials have not been set.
CMMVC9736E
The command failed because there was a problem configuring multi-factor authentication on the system.
CMMVC9737E
The command failed because the portset parameter is applicable only for the host with an iSCSI name.
CMMVC9738E
The command failed because the maximum number of allowed partnerships are exceeded.
CMMVC9739E
Portset type mismatch.
CMMVC9740E
The auto-delete option cannot be used in a HyperSwap scenario.
CMMVC9741E
The command failed because the specified provisioning policy has incompatible properties with the specified properties for the MDisks.
CMMVC9742E
Empty portset is not allowed.
CMMVC9743E
IP addresses cannot be shared across multiple replication type portsets.
CMMVC9744E
Mixing IP address types for link1 and link2 is not allowed.
CMMVC9745E
The command failed because the multi-factor authentication hostname is not specified.
CMMVC9748E
The command failed because a multi-factor authentication service has not been enabled.
CMMVC9749E
The command failed because the provisioning policy that is attached to a pool cannot be removed.
CMMVC9751E
The command failed because multi-factor authentication cannot be enabled for the superuser unless Remote Support Assistance has been enabled.
CMMVC9752E
The command failed because Remote Support Assistance cannot be disabled while multi-factor authentication is enabled for the superuser.
CMMVC9754E
The command failed because a duplicate iSCSI qualified name (IQN) was specified. iSCSI names are case-insensitive.
CMMVC9769E
The action failed because the specified portset is not valid.
CMMVC9770E
The action failed because the Fibre Channel port is already added to the portset.
CMMVC9771E
The action failed because the specified Fibre Channel port is not part of the specified portset.
CMMVC9772E
The action failed because limit of maximum Fibre Channel port types per node for a portset is reached.
CMMVC9776E
The command failed because the backend storage or the replication function is not supported on this Ethernet port.
CMMVC9778E
The command failed because default Fibre Channel portset cannot be removed.
CMMVC9779E
The command failed because portset and Fibre Channel port mapping exist.
CMMVC9780E
The command failed because the maximum limit of a VLAN on an Ethernet port_id is reached. Use another port_id for a new VLAN allocation.
CMMVC9781E
The command failed due to portset type mismatch.
CMMVC9782E
The action failed because it may result in loss of VDisk access.
CMMVC9783E
The action failed because neither storage or replication functionality is supported for Fibre Channel portset.
CMMVC9785E
The command failed because mapping of iSCSI host to a 100 Gbps Ethernet port is currently restricted by default. You may use -force flag to override the restriction. Note that currently iSCSI bandwidth is similar for 100G and 25G ports.
CMMVC9786E
The command failed because the single sign-on authentication service is already enabled. .
CMMVC9788E
The command failed because the single sign-on authentication credentials have not been set.
CMMVC9789E
The command failed because the OpenID Connect configuration endpoint has not been set.
CMMVC9790E
The command failed because there was a problem configuring single sign-on authentication on the system.
CMMVC9792E
The command failed because the volume has prepared snapshots.
CMMVC9797E
The command failed because the user group contains users who do not have both a password and an SSH key set.
CMMVC9798E
The command failed because the user does not have both a password and an SSH key set.
CMMVC9806E
The command failed because the port does not support the specified connection types.
CMMVC9818E
The command failed because superuser password key required cannot be enabled while superuser password reset is disabled.
CMMVC9819E
The command failed because superuser password reset cannot be disabled while superuser password key required is enabled.
CMMVC9823E
The command failed because the user group cannot have all the login methods disabled.
CMMVC9828E
The command failed because the shared disk feature is not enabled on the local managed disks.
CMMVC9851E
The command failed because there is already a distributed RAID array with compressing drives in the storage pool.
CMMVC9858E
The command failed because snapshots cannot be added to mirrored volumes.
CMMVC9859E
The command failed because a copy cannot be added to a VDisk with snapshots without autodelete.
CMMVC9865E
The command failed because a management port can only be configured with a management IP address.
CMMVC9871E
The command failed because distributed RAID-5 arrays are not supported for this IO group.
CMMVC9872E
The command failed because a copy cannot be added to a VDisk that is used to support a snapshot without autodelete.
CMMVC9875E
3-site consistency group has only one relationship, use convertrcconsistgrp command.
CMMVC9876E
3-site RC relationship was partially converted.
CMMVC9877E
Operation failed, run stop3sitercconsistgrp command and retry.
CMMVC9878E
Another relationship is being removed from 3-site consistency group.
CMMVC9912E
The command failed because the specified Ethernet port can only be used for system management.
CMMVC9918E
The command failed because the maximum number of hyperswap volumes have already been created.
CMMVC9965E
Failed to complete request.
CMMVC9966E
Operation cannot be performed with specified standby orchestrator configuration.
CMMVC9967E
Operation cannot be performed while standby orchestrator is functionality is running.
CMMVC9970E
Operation cannot be performed as active orchestrator is not configured.

Parent topic: Command-line interface messages