Grass Valley K2 Storage System Instruction Manual v.3.1 - Manual (Page 171)

September 6, 2006 K2 Storage System Instruction Manual 171
Testing the control network
192.168.100.21 root_server_2
192.168.101.21 root_server_2_he0
192.168.100.51 root_raid_1
192.168.100.61 root_gige_1
3. Save the file and exit the text editor.
4. Copy the new hosts file onto all the other machines. This is easier than editing the
file on each machine.
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.
• For each SAN (external storage) K2 Media 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 Media Client’s IP address. Aliasing K2
Media 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 Media 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
• Do not enter media (iSCSI) network IP addresses in the host table, as hostname
resolution is not required for the media network.
Testing the control network
To test the control network use the ping command as follows:
1. On the control point PC, click Start | Run . The Run dialog box opens.
2. Type cmd and click OK . The command prompt window opens.
3. Type ping, then a space, then the name of one of your K2 Storage System devices,
such as the Gigabit Ethernet switch, as in the following example:
ping root_gige_1
4. Press Enter .
The ping command should return the IP address of the device, as in the following
example:
Pinging root_gige_1.mycorp.com [192.168.100.61] with
32 bytes of data:
Reply from 192.168.100.61: bytes=32 time=10ms TTL=127
Reply from 192.168.100.61: bytes=32 time<10ms TTL=127