To become an active quorum device (tie-break device), it must be visible to all nodes in a cluster. 

In practice, these rules mean: 

GLYPH<SM590000> For Storwize V7000 with a single control enclosure, quorums including active quorum disk are assigned out of its internal drives automatically. No actions required. 

GLYPH<SM590000> For Storwize V7000 with two or more IOgroups and with external storage virtualized, the active quorum will be assigned to an external MDisk. None of the internal drives can become the active quorum, because they are connected to a single control enclosure and visible only by one pair of nodes. 

GLYPH<SM590000> For Storwize V7000 with two or more IOgroups and without external storage, there will be no active quorum selected automatically. IP quorum or FC-attached quorum needs to be deployed. 

To list SVC/Storwize V7000 quorum devices, run the lsquorum  command as shown in Example 2-10. 

IBM_Storwize:V7K-ITSO:superuser>lsquorum quorum_index status id name controller_id controller_name active object_type 0 online 4 no drive 1 online 1 yes drive 2 online 2 no drive 

To move quorum assignment, use the chquorum  command. Note that it is not supported on NVMe drives, so you can move it only  from an NVMe drive, but not to  an NVMe drive. 

## 2.5.1 IP Quorum 

The IP quorum application is a Java application that runs on a separate server or host. 

With respect to the quorum disk, IP quorum is a feature that can enable the use of a low-cost IP network-attached host as a quorum disk for simplified implementation and operation. 

Before IP quorum support was introduced, the third site had to be connected using Fibre Channel, and maintaining this third site and storage controller over FC makes the system costly for site recovery implementation of multi-IOgroup SVC/Storwize V7000. 

To overcome this limitation of maintaining a third site with FC connectivity along with a controller, you can implement Ethernet-attached quorum servers at the third site that can be run on hosts. Ethernet connectivity is generally easier and more economical to provide than FC connectivity, and hosts are typically less expensive than fully fledged network-attached storage controllers. This implementation of using a host application over an Ethernet connection can reduce the implementation and maintenance cost. 

IBM SVC/Storwize V7000 supports up to five IP Quorums at the same time, however, multiple instances of the IP quorum application cannot be run on the same host or server. The host may be physical or deployed as a virtual machine. Note that it must not depend on storage that is presented by the system. The dependent host can result in a situation where the nodes need to detect the IP quorum application to process I/O, but cannot because the IP quorum application cannot access storage. 

In a HyperSwap implementation, it is suggested to have at least IP Quorums. They should be accessible to nodes on both sides independently of the inter-site link state. So in case the 

