Grass Valley Aurora Browse v.7.0 Installation - Manual (Page 30)

30 Aurora Browse Installation and Configuration Guide April 6, 2010
Chapter 3 Understanding network system concepts
Ethernet switch or by separate switches. Static IP addresses are required for the media
network. Name resolution is not necessary, so media network IP addresses are not
required in host files.
The media network applies to Encoders and SmartBin servers connected to the online
K2 SAN. It also would apply to machines hosting the News MDI if the MDI is
configured to the iSCSI connection. Most systems should have the News MDI
running on the MDI server using an CIFS mount connection so typically the media
network is not needed for the News MDI. Nearline K2 SANs do not have a media
network.
Corporate LAN network
The Corporate LAN connects the Aurora Browse/MediaFrame system to the external
customer LAN. The MediaFrame server, Aurora Browse or Aurora Edit LD clients,
and low-res NAS machines must have network access to the external LAN. Work
with the IT personnel at the site to connect these devices to the site’s Domain and
network. This would include DNS, DHCP, and WINS settings.
Firewall considerations
Some sites require that there be a firewall between the MediaFrame equipment and
their corporate network. The firewall should allow incoming HTTP (TCP port 80)
connections to the MediaFrame server. Additionally, ports should allow incoming
packets so requests to the Proxy NAS can be properly processed. The port that needs
to be open is port 445 for TCP and UDP for Windows and SAMBA Shares.
Networking tips
• Before configuring any devices for networks, determine the full scope of IP
addresses and names needed for all the machines in your Aurora Browse/
MediaFrame system.
• It is recommended that you use the patterns offered in SiteConfig by default to
establish a consistent convention for machine names and IP addresses. You can
plan, organize, and enter this information in SiteConfig as you develop a system
description. You can do this even before you have devices installed or cabled.
• If configuring a HAAR platform, bear in mind that these servers use four different
subnets for the internal virtual network and co-server links. Avoid these subnets
when planning a network on a HAAR platform:
• 192.168.1
• 192.168.2
• 192.168.3
• 192.168.4
• Work with the network administrator at your facility to have IP addresses and
names available for your use.