Cisco Cisco TelePresence MCU 4510 Maintenance Manual
4.
Go to Network > SSL certificates:
a.
Scroll to the HTTPS trust store section.
b.
Set Client certificate security to Certificate-based authentication allowed.
Do NOT set Client certificate security to Certificate-based authentication required yet.
c.
Click Apply changes.
5.
Now test that you are able to log in to the MCU over an HTTPS connection using a certificate. Only proceed to
the next step if you can successfully log in with a certificate.
the next step if you can successfully log in with a certificate.
6.
Assuming the previous step succeeded, go to the Client certificate security option again and this time set it to
Certificate-based authentication required.
Certificate-based authentication required.
7.
Click Apply changes and confirm at the prompt.
It is now not possible to log in over HTTP. To log in over HTTPS requires a valid client certificate signed by a
certificate authority, which matches the HTTPS trust store on the MCU.
certificate authority, which matches the HTTPS trust store on the MCU.
8.
Do one of the following, as appropriate for your configuration:
—
Go to Network > Services and disable HTTP.
—
Go to Settings > Security and enable Redirect HTTP requests to HTTPS.
Related Topics
■
■
■
Understanding Clustering
About Clustering
A cluster is a group of MCUs that are linked together to behave as a single unit that provides the combined port count
of all the MCUs in the cluster. A larger port count provides flexibility to have conferences with more participants than
are possible on a single unit, or more smaller conferences.
of all the MCUs in the cluster. A larger port count provides flexibility to have conferences with more participants than
are possible on a single unit, or more smaller conferences.
A cluster of MCU MSE 8510 blades is configured and managed via the Supervisor blade.
MCU MSE 8510 cluster: MCU MSE 8510 blades running software version 4.1 or later support clustering. Currently up
to three blades can be clustered, with one blade acting as a "master" and the other blades being "slaves" to this
master.
to three blades can be clustered, with one blade acting as a "master" and the other blades being "slaves" to this
master.
Clustering provides you with the combined port count of the MCUs in the cluster. For example, on an MCU MSE 8510
cluster of three blades, each with 20 port licenses, the cluster can have either 30 HD ports or 15 HD+ ports and the
master can allocate them to participants in conferences as necessary. This could be one large conference, or several
smaller conferences. Note that in a cluster of MCU MSE 8510 blades, neither SD nor nHD ports are available.
cluster of three blades, each with 20 port licenses, the cluster can have either 30 HD ports or 15 HD+ ports and the
master can allocate them to participants in conferences as necessary. This could be one large conference, or several
smaller conferences. Note that in a cluster of MCU MSE 8510 blades, neither SD nor nHD ports are available.
To configure media ports, on the MCU go to Settings > Media ports.
Master MCU
All of the port or screen licenses allocated to all the MCUs in a cluster are "inherited" by the master MCU; all ports in
the cluster are controlled by the master. Therefore, after you have configured a cluster, you must control conferences
and MCU functionality through the master using either its web interface or through its API. All calls to the cluster are
made through the master.
the cluster are controlled by the master. Therefore, after you have configured a cluster, you must control conferences
and MCU functionality through the master using either its web interface or through its API. All calls to the cluster are
made through the master.
232
Cisco TelePresence MCU Series Online Printable Help