Setup guide

You can also verify that each framestore on your network is using a
unique framestore ID.
Then:If:
Check:You are unable to see other Wire hosts on your
network
■ The filesystem and networking configurations
in the sw_framestore_map file.
■ The sw_probed.cfg port number.
■ You may also have problems with your Wire
network. Use sw_ping to test that you can con-
nect to other Wire hosts. See Using sw_ping to
Test Wire Communication (page 228).
Check that each framestore has a unique Framestore
ID.
You see only some of the Wire hosts (as opposed
to all or none)
2 Repeat this procedure on each Wire host.
Using ping to Test Network Communication
Try to ping your local host from a client machine. If this works, ping all other
machines that should be accessible through Wire.
To use ping to test network communication:
1 Type the following command:
ping <host_name>
2 If ping fails, try using the machine's IP address (for example,
172.16.100.23) instead of its name. Type:
ping<IP_address>
If this is successful, verify how the machine resolves host names on the
network. You should set the order of host name resolution to first look
at the local setup file, then validate on the network. The /etc/nsswitch.conf
file should include a “hosts” line that has the name validation process
in the following order:
hosts: files nis dns
Visual Effects and Finishing Troubleshooting | 227