Service manual
Here is an example of IP addresses and names associated in a hosts le:
192.168.100.11 root_server_1
192.168.101.11 root_server_1_he0
192.168.100.21 root_server_2
192.168.101.21 root_server_2_he0
192.168.100.31 root_server_3
192.168.101.31 root_server_3_he0
192.168.100.41 root_server_4
192.168.101.41 root_server_4_he0
192.168.100.51 root_raid_1
192.168.100.61 root_gige_1
In this example 192.168.100.xx is the control network and 192.168.101.xx is the streaming/FTP
network. Each K2 Media Server has its hostname associated with its control network IP address. In
addition, each K2 Media Server (that has the role of FTP server) has its _he0 hostname associated
with its streaming/FTP network address.
Use SiteCong to dene your networks and devices. When you do so, SiteCong creates the correct
hosts le and copies the hosts le to each network device. This enforces consistent hosts les across
networks and reduces errors introduced by editing and copying hosts les on individual devices.
You can also view hosts les from SiteCong for troubleshooting purposes.
Host Table tips
• If transferring to or from a Prole XP or Open SAN system via UIM, the hosts le 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 le, as
hostname resolution is not required for the media network. If desired, you can enter media network
information in the hosts le 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" sufx 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 specied as the K2 Media Server. However, a common
mistake is to attempt a transfer in which the source/destination is incorrectly specied as the K2
client. The host le aliasing corrects this mistake and redirects to the K2 Media Server, which
is the correct transfer source/destination.
An example of a hosts le entry with this type of aliasing is as follows:
192.168.101.11 server_1_he0 client_1_he0 client_2_he0
42 K2 Installation and Service Manual 2013 07 20
Preparing for installation