540 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
The priority in this state is to recover the link to restore the relationship or consistency.
No configuration activity is possible (except for deletes or stops) until the relationship 
becomes connected again. At that point, the relationship changes to a connected state. The 
exact connected state that is entered depends on the state of the other half of the relationship 
or Consistency Group, which depends on the following factors:
/SM590000The state when it became disconnected
/SM590000The write activity since it was disconnected
/SM590000The configuration activity since it was disconnected
If both halves are IdlingDisconnected, the relationship becomes Idling when it is 
reconnected.
While IdlingDisconnected, if a write I/O is received that causes the loss of synchronization 
(synchronized attribute transitions from true to false) and the relationship was not already 
stopped (either through a user stop or a persistent error), an event is raised to notify you of 
the condition. This same event also is raised when this condition occurs for the 
ConsistentSynchronized state.
InconsistentDisconnected
InconsistentDisconnected is a disconnected state. The target volumes in this half of the 
relationship or Consistency Group are all in the auxiliary role, and do not accept read or write 
I/O. Except for deletes, no configuration activity is permitted until the relationship becomes 
connected again.
When the relationship or Consistency Group becomes connected again, the relationship 
becomes InconsistentCopying automatically unless either of the following conditions are 
true:
/SM590000The relationship was InconsistentStopped when it became disconnected.
/SM590000The user issued a stop command while disconnected.
In either case, the relationship or Consistency Group becomes InconsistentStopped.
ConsistentDisconnected
ConsistentDisconnected is a disconnected state. The target volumes in this half of the 
relationship or Consistency Group are all in the auxiliary role, and accept read I/O but not 
write I/O.
This state is entered from ConsistentSynchronized or ConsistentStopped when the auxiliary 
side of a relationship becomes disconnected.
In this state, the relationship or Consistency Group displays an attribute of FreezeTime, which 
is the point when Consistency was frozen. When it is entered from ConsistentStopped, it 
retains the time that it had in that state. When it is entered from ConsistentSynchronized, the 
FreezeTime shows the last time at which the relationship or Consistency Group was known to 
be consistent. This time corresponds to the time of the last successful heartbeat to the 
other system.
A stop command with the -access flag set to true transitions the relationship or Consistency 
Group to the IdlingDisconnected state. This state allows write I/O to be performed to the 
auxiliary volume and is used as part of a Disaster Recovery scenario.