text: In the unusual case where the master and the auxiliary are still synchronized (perhaps 
  following a user stop, and no further write I/O was received), a**start**command takes the 
  relationship to ConsistentSynchronized. No**-force**option is required. Also, in this case, you 
  can enter a**switch**command that moves the relationship or Consistency Group to 
  ConsistentSynchronized and reverses the roles of the master and the auxiliary. 
  
  If the relationship or Consistency Group becomes disconnected, the auxiliary changes to 
  ConsistentDisconnected. The master changes to IdlingDisconnected. 
  
  An informational status log is generated whenever a relationship or Consistency Group enters 
  the ConsistentStopped state with a status of Online. You can configure this event to generate 
  an SNMP trap that can be used to trigger automation or manual intervention to issue a**start**
  command after a loss of synchronization. 
  
  **ConsistentSynchronized**
  ConsistentSynchronized is a connected state. In this state, the master volume is accessible 
  for read and write I/O, and the auxiliary volume is accessible for read-only I/O. Writes that are 
  sent to the master volume are also sent to the auxiliary volume. Either successful completion 
  must be received for both writes, the write must be failed to the host, or a state must change 
  out of the ConsistentSynchronized state before a write is completed to the host. 