Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Understanding clustering
Cisco TelePresence MCU Version 4.2 Printable online help
Page 251 of 252
All blades in a cluster must be running the same version of software.
You assign the cluster roles (master/slave) to the slots in the chassis; if a blade fails, you can
replace it with a blade of the same type and the cluster configuration will persist; however, what
happens to active calls and conferences varies, as described below.
replace it with a blade of the same type and the cluster configuration will persist; however, what
happens to active calls and conferences varies, as described below.
If you restart or remove the master, the slaves will also restart: all calls and conferences end.
Blades that do not support clustering can be installed into an MSE chassis alongside a cluster.
If the clustering configuration on the Supervisor and a blade disagree, then the Supervisor pushes
the clustering configuration to the blade. (This might happen if you replace a slave blade with
another blade of the same type.) The clustering configuration only includes clustering information;
it does not configure network settings or anything else on the blade. If the Supervisor has pushed
a configuration change to a blade, the Supervisor will prompt you to restart the blade.
the clustering configuration to the blade. (This might happen if you replace a slave blade with
another blade of the same type.) The clustering configuration only includes clustering information;
it does not configure network settings or anything else on the blade. If the Supervisor has pushed
a configuration change to a blade, the Supervisor will prompt you to restart the blade.
Always keep a recent backup of the Supervisor.
If the Supervisor restarts or is removed, the cluster continues to function, conferences continue,
and the cluster does not restart when the Supervisor reappears.
and the cluster does not restart when the Supervisor reappears.
On the MCU, Call Detail Records (CDRs) are stored on and accessible on the master blade.
Slave blades only have admin logins.
Upgrading clustered blades
If you need to upgrade the blades in a cluster, first upload the new software images to each blade in
the cluster and then restart the master. The slaves will automatically restart and the upgrade will be
completed.
the cluster and then restart the master. The slaves will automatically restart and the upgrade will be
completed.