IP quorum applications

In some HyperSwap® configurations, IP quorum applications can be used at the third site as an alternative to third-site quorum disks.

No Fibre Channel connectivity at the third site is required to use an IP quorum application as the quorum device. The IP quorum application is a Java™ application that runs on a host at the third site. The IP network is used for communication between the IP quorum application and node canisters in the system. If you currently have a third-site quorum disk, you must remove the third site before you use an IP quorum application.

There are strict requirements on the IP network and some disadvantages with using IP quorum applications. Unlike quorum disks, all IP quorum applications must be reconfigured and redeployed to hosts when certain aspects of the system configuration change. These aspects include adding or removing a node canister from the system or when node service IP addresses are changed. Other examples include changing the system certificate or experiencing an Ethernet connectivity issue. An Ethernet connectivity issue prevents an IP quorum application from accessing a node that is still online. If an IP application is offline, the IP quorum application must be reconfigured because the system configuration changed. To view the state of an IP quorum application in the management GUI, select Settings > System > IP Quorum.

Even with IP quorum applications at the third site, quorum disks at site one and site two are required, as they are used to store metadata. Quorum disks for each site are selected automatically and can be configured in the management GUI, by selecting Pools > MDisks by Pools.

An IP quorum application can also act as the quorum device for systems that are configured with a standard topology that do not have any external storage configured. This configuration gives a system tie-break capability, automatically resuming I/O processing if half of the system's node canisters are inaccessible.

The maximum number of IP quorum applications that can be deployed is five. Applications can be deployed on multiple hosts to provide redundancy.

For stable quorum resolutions, an IP network must provide the following requirements:

Connectivity from the servers that are running an IP quorum application to the service IP addresses of all node canisters. The network must also deal with possible security implications of exposing the service IP addresses, as this connectivity can also be used to access the service assistant interface if the IP network security is configured incorrectly.
Port 1260 is used by IP quorum applications to communicate from the hosts to all node canisters.
The maximum round-trip delay must not exceed 80 milliseconds (ms), which means 40 ms each direction.
A minimum bandwidth of 2 megabytes per second is guaranteed for node canister-to-quorum traffic.

The following minimum requirements must be met on the hosts that are used to run IP quorum applications:

The host must not depend on storage that is presented by the storage system. Doing so might result in a deadlock situation where the nodes in the system need to detect the IP quorum application to process I/O, but the IP quorum application needs to access storage on the system to answer.
Supported operating systems:
- Red Hat Enterprise Linux 6.5, Red Hat Enterprise Linux 7
- SUSE Linux Enterprise Server 11 SP3, SUSE Linux Enterprise Server 12
- Microsoft Windows Server 2012
Supported Java Runtime Environments: IBM® Java 7.1, IBM Java 8