Setup guide

Testing Wire Using sw_framestore_dump
Use sw_framestore_dump to identify the Wire hosts that are reachable from one workstation. You should
do this if you are having any problems with Wire or after you configure Wire for the first time. You must
have at least two Wire hosts set up to test Wire connectivity:
1 Run: /usr/discreet/sw/tools/sw_framestore_dump. A list of all the available framestores appears in
the terminal. Review the output and verify that all the framestores on your Wire network appear in
the list. You can also verify that each framestore on your network is using a unique framestore ID.
■ If You are unable to see other Wire hosts on your network, check:
■ The filesystem and networking configurations in sw_framestore_map.
■ The sw_probed.cfg port number.
■ You may also have problems with your Wire network. Use sw_ping to test that you can connect
to other Wire hosts.
■ If you see only some of the Wire hosts (as opposed to all or none), check that each framestore has
a unique Framestore ID.
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. :
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 hostname.
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
Using sw_ping to Test Wire Communication
If you are unable to connect to a Wire host, use sw_ping to determine if you can connect to the other Wire
host over the Wire network:
1 Run sw_ping: /usr/discreet/sw/sw_ping -framestore <framestore_name> -r -w -size <packetsize>
-loop <n> where <host_name> is the name of the host to ping, <count> is the number of times to
execute this test, <packetsize> is the size of the read/write buffer (in bytes). Results similar to the
following are reported to the terminal:
Using Stone+Wire API 2009 [ProductSW_1166] (64 bits).
Stone+Wire TCP port set to 7000.
Ping successful to host tunisia (186)
Buffer size = 9043968
Sending data to tunisia, filesystem id 186
MB/sec: 111.460127
Ping successful.
Buffer size = 9043968
Sending data to tunisia, filesystem id 186
MB/sec: 111.509057
Ping successful.
Buffer size = 9043968
Sending data to tunisia, filesystem id 186
MB/sec: 111.500577
Advanced Configuration and Troubleshooting | 75