Maintenance Manual

Slaves MCUs

Slave MCUs do not display the full MCU web interface. Only certain settings are available, such as network

configuration, logging and upgrading. Similarly, a slave blade will only respond to a subset of API calls. For more

information, refer to the relevant API documentation (available on the Support pages of www.cisco.com).

General Points

Some points to note about clustering:

■ Clustering requires the Cluster support feature key.

■ All MCUs in a cluster must be running the same version of software.

■ On the MCU, Call Detail Records (CDRs) are stored on and accessible on the master MCU.

■ Slave MCUs only have admin logins.

■ The MSE 8000 Supervisor blade must be running software version 2.1 or above to configure clustering.

■ 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.

■ Blades that do not support clustering can be installed into an MSE chassis alongside a cluster.

■ You cannot mix the type of blades in a cluster but you can have more than one cluster in the same MSE

chassis. You can also have clusters of different types of blades in the same chassis.

■ 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 follows:

— If you restart or remove the master, the slaves will also restart: all calls and conferences end.

— 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.

Upgrading Clustered MCUs

If you need to upgrade the MCUs in a cluster, first upload the new software images to each MCU in the cluster and

then restart the master. The slave(s) will automatically restart and the upgrade will be completed.