Displaying the cluster status of a master MCU

The IP address of a slave MCU or Master.

Possible statuses for the slave MCU are:

• OK: The master and slave are communicating correctly.
• OK (last seen <number> seconds ago): The master has lost contact with the slave. The slave will restart itself and in this way it will rejoin the cluster. Wait a few minutes and then refresh the Status > Cluster page.
• Still starting up: The slave is in the process of starting up. Wait a few minutes and then refresh the Status > Cluster page.
• Lost contact <number> secs ago: The master has lost contact with the slave. The slave will restart itself and in this way it will rejoin the cluster. Wait a few minutes and then refresh the Status > Cluster page.
• Failed, version mismatch: All MCUs in the cluster must be running the same version of software. This status message indicates that this MCU is running different software to the master. This MCU is not part of the cluster. Update all MCUs in the cluster to the same version of software.

If the status of the slave is OK, it is currently functioning in the cluster. For any of the other statuses, the slave MCU is not currently functioning as part of the cluster.

If the slave MCU has a problem that causes it to no longer be part of the cluster, the cluster can continue to operate without the slave. There will just be fewer video ports available.

If the slave MCU fails, participants in conferences will not be disconnected if there are sufficient resources on the master and they will continue to receive audio and video. In the worst case, the video will disappear, but the audio will continue because all audio is processed by the master MCU.

If the master loses contact with the slave, the slave will automatically restart itself. In this way, it can rejoin the cluster.

An overview of the current media loading of each MCU in the cluster. The load may increase during periods of peak conference use.

Conferences are distributed between the MCUs in the cluster. The loads on the MCUs depend on the number of conferences running on each MCU and the sizes of those conferences.

The number of port licenses on the MCU listed in this row.

All port licenses on the slave MCU are controlled by the master MCU. Depending on how you use the MCUs, you might want to allocate all port licenses to the master MCU or you might distribute them between the MCUs. It does not matter to the cluster how you have allocated the port licenses; in any case, the master controls all port licenses and even if an MCU has failed in the cluster, the master will continue to have access to any port licenses allocated to the failed MCU.