Note:
If the new activation state is the same as the existing state nothing is done and a
success code is returned.
The mirroring can't be activated:
v If the time stamps of the last_replicated snapshots on the Master and the Slave
do not match.
v If the command is issued on a Master that did not receive acknowledgment from
the Slave following a cg_add_volume - or - cg_remove_volume command (until
that command timed out or due to any unexpected failure), the command will
fail and a new completion code will be returned
(MIRROR_CONS_GROUP_MEMBERSHIP_MISMATCH - meaning that the
member lists of the mirror Consistency Group peers are not the same).
v If the command is issued on a Master that did not receive acknowledgment from
the Slave following a vol_resize command (until that command timed out or due
to any unexpected failure), the command will fail and a new completion code
will be returned (MIRROR_SIZE_MISMATCH - meaning that The sizes of the
mirror volume peers are not the same).
Access Control:
User Category Permission
Storage administrator Allowed
Storage integration administrator Allowed
Application administrator Disallowed
Security administrator Disallowed
Read-only users Disallowed
Technicians Disallowed
Completion Codes:
v VOLUME_BAD_NAME
Volume name does not exist
v VOLUME_NO_MIRROR
Local volume does not have remote mirroring definitions
v CONS_GROUP_BAD_NAME
Consistency Group name does not exist.
v CONS_GROUP_NO_MIRROR
Local Consistency Group does not have remote mirroring definitions
v LOCAL_PEER_IS_NOT_MASTER
Local peer is not the master
v MIRROR_CONFIGURATION_ERROR
Mirror local configuration does not match remote configuration
v REMOTE_MAX_VOLUMES_REACHED
Maximum number of volumes already defined on remote machine
v SYNC_ALREADY_ACTIVE
Synchronization is already active
v VOLUME_BELONGS_TO_MIRRORED_CONS_GROUP
Volume mirror is part of Consistency Group mirror.
204 IBM XIV Storage System User Manual
To Next Page
Loading...
Need help?
General
