General information about SU Clusters

Prerequisites

• An SU Cluster between two Server Units in different SE Servers can be set up only after a Management Cluster is configured.
• An SU Cluster between two SU x86 in an SE Server does not require a Management Cluster.
  However, external configuration disks (CRD) are required, which must also be configured on the Management Units of the server.
• A SAN-X configuration of the RAID peripheral is needed for SU Clusters. (Every external configuration disk must be reachable from every unit participating in the SU Cluster.)
• The same data and administration networks (DANPUnn and MANPU/MONPU) must be available on the participating SE Servers for an SU Cluster (or for the LM functionality) based on a Management Cluster.
  The network communication between the participating SE Servers must be realized in the same network segment or without routers/gateways.
  Only in such a way it can be assured that the network connections of the BS2000 systems still function correctly after the LM.
  Further details about the networks of the SE Server can be found in the manual “Administration and Operation“ [1].

Recommandations and notes

• After a Live Migration the migrated BS2000 system accesses the storage systems from the remote location.
  Thus for performance reasons a maximal distance of 15 km between the locations is recommended.
• Longer distancies and lower data transfer rates are conceivable but the realization must be tested in practice in the customer's specific configuration.
• Note:
  The cluster software does not check whether the above conditions are met. This has to be ensured by the customer through a suitable configuration of the infrastructure.

Configuration

• The configuration of the SU Cluster consists of a cluster name and a selection of both Server Units between which the Live Migration function should be made possible.
• Multiple SU Clusters can be configured within a Management Cluster. However, an SU can belong to only one SU Cluster.

SU Cluster in deactivated state

An SU Cluster can be deactivated (status summary INACTIVE). No LM can be performed in the deactivated state.
We recommend deactivating an SU Cluster in maintenance situations, for example, to avoid sending unnecessary alarms.