Cisco TelePresence Server 7010 Product User Manual page 11

Field Field description
Status The status of the master blade can only be OK which
means that this blade is operating correctly in the
cluster.
Possible statuses for a slave blade are:
OK: The master and slave are communicating
n
correctly.
OK (last seen <number> seconds ago): The
n
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
Still starting up: The slave blade is in the process
n
of starting up. Wait a few minutes and then refresh
the Status > Cluster
Lost contact <number> secs ago: The master has
n
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
page.
Cluster support not enabled: There is no Cluster
n
support feature key on this blade.
Failed, version mismatch: All blades in the cluster
n
must be running the same version of software.
This status message indicates that this blade is
running different software to the master blade. This
blade is not part of the cluster. Update all blades in
the cluster to the same version of software.
Blade not configured as slave: The Supervisor has
n
told the master that the blade is a slave, but the
blade is not a slave. Possibly the slave blade was
replaced.
Blade incorrect type: Possibly the slave blade was
n
replaced with a different blade type after the
cluster was configured.
Media An overview of the current media loading of each
processing blade in the cluster. The load may increase during
load periods of peak conference use.
Cisco TelePresence Server Product User Guide
page.
page.
Status > Cluster
System status
Usage tips
If the status of the slave is OK, it is
currently functioning in the cluster. For
any of the other statuses, the slave
blade is not currently functioning as
part of the cluster.
If a slave blade 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 blade fails, participants in
conferences will not be disconnected:
if there are sufficient resources on
another blade 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 blade.
If the master loses contact with a
slave, the slave will automatically
restart itself. In this way, it can rejoin
the cluster.
Conferences are distributed between
the blades in the cluster. The loads on
the blades depend on the number of
conferences running on each blade
and the sizes of those conferences.
On a slave blade, the audio load will
always be zero: the master is
responsible for all the audio.
Page 11 of 151