Planning for a HyperSwap topology system

You can plan to meet the requirements of a HyperSwap topology system so that active-active relationships can be used.

  • All enclosures and the managed disks of an I/O group must be at one site.
  • There must be another I/O group and managed disks at another site.
  • There must be managed disks at a third site for quorum disks. As an alternative to quorum disks at a third site, you can use IP quorum.
  • There must be enough fiber optic connections between the control enclosures on each site.
  • Before the system topology can be set to HyperSwap, the site attribute must be set to:
    • 1, 2 or 3 for each controller
    • 1, 2 for each enclosure
    • 1, 2 for each host
  • The system must be set to HyperSwap topology before HyperSwap volumes can be created.