Grass Valley Profile XP Service Manual - Manual (Page 69)

Testing the Fibre Channel Video network
23 July 2004 Profile XP Service Manual 69
Testing the Fibre Channel Video network
Use this procedure to test your Fibre Channel video network setup.
Testing the Ethernet name resolution and connectivity
The Fibre Channel video network relies on Ethernet connectivity and name
resolution.This procedure uses the ping command which requests a response from the
named Profile XP system. If the remote system does not respond, you’ll try ping using
the IP address of the remote system. If the system responds, you have a name
resolution problem. If there is no response, there may be problems with the Ethernet
adapter or cabling.
To test the Ethernet network:
1. Open the Windows NT command prompt by selecting Start | Programs | Command
Prompt .
2. Type ping, then the Ethernet name of one of the Profile XP systems on the network,
then press Enter . For Example:
ping Profile1
If this command returns:
Pinging Profile1 with 32 bytes of data:
Reply from 192.168.99.100: bytes=32 time<10ms TTL=128
Reply from 192.168.99.100: bytes=32 time<10ms TTL=128
Reply from 192.168.99.100: bytes=32 time<10ms TTL=128
Reply from 192.168.99.100: bytes=32 time<10ms TTL=128
You have successfully resolved the name Profile1 and you have Ethernet network
connectivity.
If, however, the ping command returns:
Pinging Profile1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
There is a connectivity problem or the Ethernet IP address could not resolve
properly. Continue with step 3.
3. Type ping, then, this time, use the IP address of one of the Profile XP systems on
the network, then press Enter . For Example:
ping 192.168.99.100
If this command returns:
Pinging 192.168.99.100 with 32 bytes of data:
Reply from 192.168.99.100: bytes=32 time<10ms TTL=128
Reply from 192.168.99.100: bytes=32 time<10ms TTL=128
Reply from 192.168.99.100: bytes=32 time<10ms TTL=128
Reply from 192.168.99.100: bytes=32 time<10ms TTL=128
You have connectivity to the network, so there must be a name resolution problem
for the IP address. You need to re-check your HOSTS file for accuracy. Refer to
Manually Edit the hosts file on each Profile XP in the Profile XP System Guide.