Troubleshooting Global Mirror sessions

Use this information to understand, isolate, and resolve problems with Global Mirror sessions.

After you suspend a session, other sessions also become suspended
This condition occurs when you suspend a Metro Mirror session or Global Mirror session.
Existing Global Mirror sessions are not recognized
This condition occurs in environments that migrated to a later version of Copy Services Manager.
Starting a session does not restart pairs outside the SAN Volume Controller or Storwize consistency group
This condition occurs when you issue a Start command for a Metro Mirror session or Global Mirror session with SAN Volume Controller or Storwize® storage systems.
Session does not change to prepared state after session failback
This condition occurs during a Global Mirror session failback.
Copy Services Manager Session is in Severe status, but Global Master state is showing as running on the Global Mirror Info tab
This condition occurs when a Global Mirror master session is created on the IBM System Storage DS8700DS8000 using the same logical subsystem (LSS) pairs as an existing master session.