Grass Valley Aurora Browse v.6.5 Installation - Manual (Page 136)

136 Aurora Browse Installation and Configuration Guide November 1, 2008
Appendix C Legacy systems
10.16.37.92 iron-nb-live-2 #Client LAN
#Browse Ethernet Switch
10.16.37.20 iron-nb-2950-client-1 #Client LAN
192.168.30.200 iron-nb-2950-prod-1
Host table tips:
• If you are exporting EDLs to Aurora Edit, the Aurora Edit workstation must be able
to resolve the Profile MDI name (present in the EDL) to the IP address of the
Profile XP system to which the MDI connects. The recommended solution is to
map the MDI name to the Profile IP address in the Aurora Edit workstation’s host
table. Refer to
“MDI and Encoder logical names convention” on page 33 .
• The NAS and MediaFrame server IP address need to be resolved using the Client
side IP address via DNS lookup, not the host table.
• If the server has a canonical name, the host table for any machine that runs MDIs
that are subscribed to by the server must match case for the entire canonical name.
E.g., if the server’s canonical name is “NB-SERVER1.mycorp.net”, then the host
table entry in the MDI server(s) must match; if the entry is
“NB-SERVER1.MYCORP.NET”, then it will not work. Pinging will not show the
problem. The problem doesn’t show up until the MDIs attempt to notify the server.