Cisco TelePresence 7010 Help Manual page 12

System status
Table 7: Cluster status (continued)
Field Field description
Status The status of the master can only be OK which means
that the master is operating correctly in the cluster.
The following options are possible for slave status:
OK: The master and slave are communicating
n
correctly.
OK (last seen <number> seconds ago): The master
n
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
page.
Still starting up: The slave is in the process of starting
n
up. Wait a few minutes and then refresh the
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
Cluster support not enabled: There is no Cluster
n
support feature key on this TelePresence Server.
Failed, version mismatch: All TelePresence Servers
n
in the cluster must be running the same version of
software. This status message indicates that this
slave is running different software to the master, and
hence the TelePresence Server is not part of the
cluster. Update all units in the cluster to the same
version of the 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.
Software The software version on each TelePresence Server in
version the cluster.
Media An overview of the current media loading of each
processing TelePresence Server in the cluster. The load may
load increase during periods of peak conference use.
Cisco TelePresence Server 7010 and MSE 8710 in Remotely Managed Mode Printable Help (4.0)
Status > Cluster
page.
Status > Cluster
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 is
not currently functioning as part of the
cluster.
If a slave has a problem that causes it to
no longer be part of the cluster, the
cluster can continue to operate without
the slave.
If a slave fails, participants in
conferences will not be disconnected: if
there are sufficient resources in the
Status >
cluster, they will continue to receive
audio and video. In the worst case,
participants may lose video. The audio
will continue because all audio is
processed by the master.
page.
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 TelePresence Servers in the cluster.
The load on each depends on the
number and size of the conferences
running on them.
On a slave blade, the audio load will
always be zero: the master is
responsible for all the audio.
Page 12 of 92