Cisco Cisco TelePresence MCU 4510 Administrator's Guide
Understanding clustering
About clustering
A cluster is a group of MCUs that are linked together to behave as a single unit that provides the combined
port count of all the MCUs in the cluster. A larger port count provides flexibility to have conferences with
more participants than are possible on a single unit, or more smaller conferences.
port count of all the MCUs in the cluster. A larger port count provides flexibility to have conferences with
more participants than are possible on a single unit, or more smaller conferences.
A cluster of MCU MSE 8510 blades is configured and managed via the Supervisor blade.
MCU MSE 8510 cluster: MCU MSE 8510 blades running software version 4.1 or later support clustering.
Currently up to three blades can be clustered, with one blade acting as a "master" and the other blades being
"slaves" to this master.
Currently up to three blades can be clustered, with one blade acting as a "master" and the other blades being
"slaves" to this master.
Clustering provides you with the combined port count of the MCUs in the cluster. For example, on an MCU
MSE 8510 cluster of three blades, each with 20 port licenses, the cluster can have either 30 HD ports or 15
HD+ ports and the master can allocate them to participants in conferences as necessary. This could be one
large conference, or several smaller conferences. Note that in a cluster of MCU MSE 8510 blades, neither
SD nor nHD ports are available.
MSE 8510 cluster of three blades, each with 20 port licenses, the cluster can have either 30 HD ports or 15
HD+ ports and the master can allocate them to participants in conferences as necessary. This could be one
large conference, or several smaller conferences. Note that in a cluster of MCU MSE 8510 blades, neither
SD nor nHD ports are available.
To configure media ports, on the MCU go to
Settings > Media ports
.
Master MCU
All of the port or screen licenses allocated to all the MCUs in a cluster are "inherited" by the master MCU; all
ports in the cluster are controlled by the master. Therefore, after you have configured a cluster, you must
control conferences and MCU functionality through the master using either its web interface or through its
API. All calls to the cluster are made through the master.
ports in the cluster are controlled by the master. Therefore, after you have configured a cluster, you must
control conferences and MCU functionality through the master using either its web interface or through its
API. All calls to the cluster are made through the master.
Slaves MCUs
Slave MCUs do not display the full MCU web interface. Only certain settings are available, such as network
configuration, logging and upgrading. Similarly, a slave blade will only respond to a subset of API calls. For
more information, refer to the relevant API documentation (available on the Support pages of
configuration, logging and upgrading. Similarly, a slave blade will only respond to a subset of API calls. For
more information, refer to the relevant API documentation (available on the Support pages of
).
General points
Some points to note about clustering:
n
Clustering requires the Cluster support feature key.
n
All MCUs in a cluster must be running the same version of software.
n
On the MCU, Call Detail Records (CDRs) are stored on and accessible on the master MCU.
n
Slave MCUs only have admin logins.
n
The MSE 8000 Supervisor blade must be running software version 2.1 or above to configure clustering.
n
Always keep a recent backup of the Supervisor.
n
If the Supervisor restarts or is removed, the cluster continues to function, conferences continue, and the
cluster does not restart when the Supervisor reappears.
cluster does not restart when the Supervisor reappears.
n
Blades that do not support clustering can be installed into an MSE chassis alongside a cluster.
Cisco TelePresence MCU Series Administrator Guide
Page 262 of 300
Advanced topics
Understanding clustering