Grass Valley K2 Summit Storage Area Network v.7.1 - Manual (Page 59)

26 October 2009 K2 Storage Area Network Installation and Service Manual 59
Host table tips
Use SiteConfig to define your networks and devices. When you do so, SiteConfig
creates the correct hosts file and copies the hosts file to each network device. This
enforces consistent hosts files across networks and reduces errors introduced by
editing and copying hosts files on individual devices. You can also view hosts files
from SiteConfig for troubleshooting purposes.
Host table tips
• If transferring to or from a Profile XP or Open SAN system via UIM, the hosts file
must also follow UIM naming conventions for those systems. Refer to the UIM
Instruction Manual.
• Do not enable name resolutions for media (iSCSI) network IP addresses in the
hosts file, as hostname resolution is not required for the media network. If desired,
you can enter media network information in the hosts file as commented text as an
aid to managing your networks.
• Use the following tip with care. While it can solve a problem, it also introduces a
name resolution “anomaly” that might be confusing if not considered in future
troubleshooting activities.
For each SAN (shared storage) K2 client, add the “_he0” suffix to the hostname but
then associate that hostname with the K2 Media Server’s FTP/streaming network
IP address, not the K2 client’s IP address. Aliasing K2 client hostnames in this way
would not be required if the transfer source/destination was always correctly
specified as the K2 Media Server. However, a common mistake is to attempt a
transfer in which the source/destination is incorrectly specified as the K2 client.
The host file aliasing corrects this mistake and redirects to the K2 Media Server,
which is the correct transfer source/destination.
An example of a hosts file entry with this type of aliasing is as follows:
192.168.101.11 server_1_he0 client_1_he0 client_2_he0