Maintenance Manual

Status The status of the master can only
be OK which means that this
MCU is operating correctly in the
cluster.
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.
■ Cluster support not
enabled: There is no
Cluster support feature
key on this blade.
■ Blade not configured as
slave: The Supervisor has
told the master that the
blade is a slave, but the
blade is not a slave. This
indicates that someone
has removed the slave
blade and replaced it with
a different blade.
■ Blade incorrect type:
Someone has removed
the blade in this slot and
replaced it with a different
blade type after the
cluster was configured.
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 a slave MCU has a problem that causes it to no longer be part of
the cluster, the cluster can continue to operate without that
slave. For example, in a cluster of three blades if one slave fails,
the master and the other slave can continue to operate and
accept calls. There will just be fewer video ports available.
Similarly, in a cluster of two blades, if the slave fails, the master
continues to operate.
If a slave MCU fails, participants in conferences will not be
disconnected: if there are sufficient resources on another MCU in
the cluster, 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 a slave, the slave will
automatically restart itself. In this way, it can rejoin the cluster.
196
Cisco TelePresence MCU Series Online Printable Help