Cisco Cisco TelePresence MCU 4510 Maintenance Manual
■
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.
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.
Media
processing
load
processing
load
An overview of the current media
loading of each MCU in the
cluster. The load may increase
during periods of peak
conference use.
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 loads on the MCUs depend on the number of conferences
running on each MCU and the sizes of those conferences.
On a slave MCU, the audio load will always be zero: the master is
responsible for all the audio.
responsible for all the audio.
Port
licenses
licenses
The number of port licenses on
the MCU listed in this row.
the MCU listed in this row.
All port licenses on slave blades are controlled by the master
blade. Depending on how you use the blades in the MSE chassis,
you might want to allocate all port licenses to the slot that houses
the master blade or you might distribute them between the slots
in the cluster. 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 a blade has failed in the cluster, the
master will continue to have access to any port licenses
allocated to the failed blade's slot.
blade. Depending on how you use the blades in the MSE chassis,
you might want to allocate all port licenses to the slot that houses
the master blade or you might distribute them between the slots
in the cluster. 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 a blade has failed in the cluster, the
master will continue to have access to any port licenses
allocated to the failed blade's slot.
Related Topics
■
■
■
■
■
Displaying the Cluster Status on a Slave MCU
This topic applies only to MCUs that are configured as part of a cluster.
To display cluster status, go to Status > Cluster.
The table below describes the Status > Cluster page that displays on a slave in a cluster. For information about the
details displayed on a master MCU, see
details displayed on a master MCU, see
A slave MCU does not present the full MCU web interface. Some settings are only available on the master MCU.
The master MCU in a cluster inherits all the ports and port licenses from the slave MCU. Configure conferences and
other MCU functionality from the web interface of the master MCU (accessible using the IP address displayed on the
Status > Cluster page).
other MCU functionality from the web interface of the master MCU (accessible using the IP address displayed on the
Status > Cluster page).
When you look at the Status > Cluster page on the slave MCU, it shows the status of the master MCU.
Field
Field Description
Usage Tips
197
Cisco TelePresence MCU Series Online Printable Help