This is one of those points, so I don't really have any choice in the matter. The issue I had/have is with how our network is setup and how MC|UX wants DNS (or IP Addresses) to work).Īs to the seperating of the traffic, it's because the ISIS is on a "TV" (basically only TV equipment, which includes all our Avid gear) network, whereas everyone else is on a "IT" network, so we needed to bridge the gap between the 2 at a few points. (Just for the record I have been able to access the MC|UX web interface via both the Intel and Broadcom ports since day one. The "built-in" network card (the Broadcom) is labeled em0-em3, and the MediaCentral|UX is working/accessible/exported over the em0 port currently. The ISIS connections are currently on an Intel card named eth0 and eth1. Sorry I didn't put this info in my previous post. I guess I will have to bother our angel of support, Marianna, to find the right resource again inside Avid. What is your reason for trying to seperate web traffic from ISIS trafic in your setup and have you also contacted Avid with questions on your findings? So I have setup a VMware EXSI 6 to do functional testing but without a virtual ISIS that is tricky so I'm waiting for the moment to have an ISIS 5500 at our offices (for another customer) which I can use for testing without having to deal with other support/setup related issues at the same time but I've had no luck so far. The thing is that I have an existing setup that has performance issues but I can't use that system for testing. I contacted Avid support with this question and they weren't even aware that using multiple cards was posible. While the documentation indicates this possibility it's default setup is to use only one IP, also with a 1G connection, and for non proxy workflows use 10G connection. for more ISIS bandwith) card for the corect IP + subnet (VLAN) for ISIS. So it seems logical to me that the best or default setup should be to setup the eth0 card in the correct Ip + subnet (VLAN) for all Media central clients and setup the second eth1 (and 2, 3. So it seems logical to me that the web page only communicates through 1 IP (and one network port) only.īut Isis client has always had the ability to select active network cards (regardless of their IP) on Mac OS and Windows and obviously also on the Linux/Unix clients. The Ip address and/or hostname need to match inside the setup of mediacentral with the Ip (or DNS name that is linked to that Ip in the dns server) on that specific 'eth0' card. In interpret that Avid has hardcoded inside the media central software that the 'eth0' card is the one to be used by the MC web server. In the manual it is stated that you have to rename the network card that is to be used by media central (not perse ISIS) to eth0. I'll keep you updated on what happens there. On one of the other connections I have an IP address of 172.19.17.xx, and am trying to get the computers on that address range to work with MC|UX. Works fine for all computers on 172.16.0/1.xx. My current issue (and actually a Google search led me to this page) is that I can't seem to get MC|UX working with a different IP Address range. I attached it to a switch, entered those into the other field (the ignore list), and so far so good. Second NIC is the onboard NIC, a 4xBroadcom Gigabit Ethernet card (named em0,em1,em2,em3). So in my case, I enter Eth0 in the field you're talking about. Special Note: Only enter the first Eth device for ISIS. Just got it up and running, and I still have some work to do to get everything the way I want it, but it is working.įirst NIC is Eth0 (default)/Eth1, running on an Intel 82571EB Dual NIC Card. VLAN's, etc.? I'm not finding a lot of info on other then single connection setups in the documentation. Isn't seperation of these 2 networks (ISIS/Web) a desired default setup for performance reasons and security as journalist pc's will often have (unrestricted) internet connections in seperate networks. If I understand correctly the media central UX web interface is obliged to use the eth0 connection but the ISIS client is not. So I read it is possible to have the communication to the ISIS on a seperate nic ports from the web browser clients that are communicating with the web page simply by selecting eth1,2 or 3 as the ISIS connection nic inside the media central UX system settings (after configuring the eth1,2 or 3 inside redhat of course). Server, you must indicate which network connections are reserved for ISIS, and which are used When you maintain other active connections on the MCS In the installation documentation it writes: I have a question about media central UX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |