MCS 2.7 Installation and Configuration Guide
16
Remote Client Connections
MediaCentral UX web or mobile clients that connect through the public Internet require VPN
access into the server network. All connections pass through the VPN router/firewall through
identified ports. Once the data has passed into the “house network”, it is secured using the
customer’s existing network security infrastructure.
For more information on networking in an Avid environment, see “Network Requirements for
ISIS and Interplay PAM and MAM” located on the Avid Knowledge Base at:
http://avid.force.com/pkb/articles/en_US/compatibility/en244197
For information on port usage and network firewall information, see the Avid Networking Port
Usage Guide at:
http://avid.force.com/pkb/articles/en_US/readme/Avid-Networking-Port-
Usage-Guide
Planning for the Mongo Arbiter
MediaCentral v2.6 introduced a new Mongo database in a “sharded” configuration. In MCS
cluster and multi-zone configurations, multiple servers host a copy or “shard” of the Mongo
database. If you are running a local (non-multi-zone) Corosync cluster that consists of only two
nodes, a 3
rd
instance of Mongo must be configured to provide a tiebreaker vote in the event of a
failover. This 3
rd
instance or “arbiter” must be installed on another Linux server or a Windows-
based system. If you have a 2-node cluster, plan which system will host the Mongo arbiter.
For more information, see P
ART VI: SHARDED MONGO on page 133 as well as the “MongoDB”
section of the MediaCentral Platform Services Concepts and Clustering Guide.
Note: If you are running a single-server, non-multi-zone system, no additional configuration steps for
sharded Mongo are required.
Accessing the MCS Server(s)
The initial configuration of the MCS server(s) must be completed using a directly connected
monitor and keyboard to the server, or through a KVM (keyboard, video and mouse) device.
Note: Some KVMs present virtual USB devices to the operating system. These devices might
be assigned a device name (sda, sdb) by RHEL during the installation, which results in a failed
installation. Disable this option on your KVM if applicable.
Once the initial configuration is complete, Avid recommends connecting to MCS indirectly
through SSH (Secure Shell). SSH is preferable for the following reasons:
Allows for an expandable view of the RHEL interface (adjustable window size)
Allows for multiple sessions to the host server or to multiple servers
Allows for simplified copy/paste of commands between SSH windows
Allows for logging of all session output
On Windows, PuTTY.exe is an example of a SSH client:
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
At the appropriate point in the installation procedure, you will be given the option to switch
from a direct connection to an indirect connection.