The physical connections between computers running Rivendell and/or NetJack should be done with a bit of thought. There are some special considerations in any network that carries real time audio or files that must be served on an exact schedule. This “real time” requirement is different than most computer needs where a document or web page can be served at some time in the future, as long as it is soon. Audio streams and playout systems need their data NOW.
Rivendell requires Internet access for its rdcatch feature, as well as to access audio files, logs, ssh management, icecast servers. ftp servers and podcast servers, etc. A Jack server should have access to the internet for the same reasons, plus network time, printers, sending email alerts, etc. I will call this a connection to the “Office Network” since it includes mostly non-real time traffic.
The safest way (I have thought of) is to have the Rivendell Workstations and Rivendell Server(s) connect to two separate networks. One network, the “Office Network” carries all the normal traffic, connection to the internet, uploading of logs, printing reports, VoIP, etc.. The other network I call the “Music Network” carries only NetJack traffic, NFS traffic for audio files, and MySQL traffic and some network management traffic. Rivendell also requires that the Ethernet addresses for these purposes are STATIC, meaning that they are maintained permanently and setup manually. The “Office Network” could be automatically assigned using DHCP, or can be STATIC, although there are good reasons that the server interface to the “Office Network” should be STATIC also.
Below is a graphic showing a possible configuration of a Rivendell – NetJack system in a small radio station, or station cluster. It is not set up for redundancy to provide high reliability, but later additions will permit this:
The “Music Network” should use Gigabyte Ethernet interfaces on the computers and switch. It should use Cat-5e or Cat-6 cables in a unique color to distinguish it from the office network. If patch panels are used, they should be separate panels from the office network to avoid confusion. As you can see, only the machines that have real time functions are connected to this net. There could be a Network Attached Storage device on this network also, but it should not be used for backups, etc.; only for music and playout traffic should be on this network.
In this installation I have arbitrarily assigned the “Music Network” to a class C non-routable set of addresses:
Parameters -192.168.60.0 netmask 255.255.255.0 Gateway 192. 168.60.1 (The server) Broadcast 192.168.60.255.
This means that any device on the “Music Network” assigned an address beginning with 192.168.60. will be a member of this network. It does not require a router, just a switch since the knowledge of the members of this network and the needed data routes will be known by each of the computers involved. This network could possibly have 254 devices attached, but you would never want that many.
The “Office Network” is a conventional internet connected network configured to be efficient for its size. It carries all the regular business and computer traffic of the operation, in addition to providing audio file upload services and possibly streaming sources for Internet Streaming. Conventional network design considerations are appropriate here. A small station could possibly use the firewall – router provided by the Internet Service Provider (ISP), or another solution with more than one ISP and a load balancing router, a router using DD-Wrt or other open source router software, or Cisco or other “heavy iron” solution.
Not shown here, but for radio stations that need to deliver programming to remote transmitters, there may be a third ethernet interface on the Rivendell Server for a “STL Network” whose exclusive purpose is program delivery, transmitter control and communications to the station transmitters. The traffic on this network should be separated from the other networks. This network will interconnect using dedicated microwave channels, landline T-1, and/or other methods of data transport requiring well thought out routing protocols for high reliability.