Setup guide
Verify Stone and Wire connectivity from the background processing network
Render nodes on a background processing network access frames on storage devices attached to the
workstation using the Wire network. To ensure these storage devices are available to the render node:
1 Log in as root to a render node on the background processing network. In a terminal, view all storage
devices available to the render node: /usr/discreet/sw/tools/sw_framestore_dump. All storage devices
attached to the Wire network appear.
2 If a storage device does not appear in the list of devices available to the render node, check:
■ The workstation is on the same network as the render node.
■ The workstation to which the device is attached is available on the network and can be pinged.
■ The probed daemon running on the workstation is using the same port as the rest of the network.
See the entries for sw_probed and sw_probed.cfg in the Creative Finishing Installation and
Configuration Guide.
■ Verify that the sw_framestore_map file on the workstation contains only the local media storage:
as root, open for editing /usr/discreet/sw/cfg/sw_framestore_map. Verify that only the local
media storage appears in this file. If other media storage devices appear, delete them, unless server
self-discovery is not enabled for Stone and Wire. Media storage devices must be explicitly listed in
the sw_framestore_map file if server self-discovery is not enabled for Stone and Wire, such as when
you are using legacy disk arrays. Use sw_framestore_dump to see if storage devices for other
workstations on the network can be viewed. Save and close the file.
Checking Burn Licensing for Render Nodes
The following applies to all render nodes as well as the workstation or render node being used as the License
Server for the background processing network. Render nodes must get Burn licenses from the License Server
to process jobs. If the License Server is not working, or if licenses cannot be checked out, jobs are not
rendered. To ensure that licensing for Burn is working on the render nodes:
1 Log in as root to the render node or workstation running the License Server for the background
processing network and check if the License Server is set to start automatically: chkconfig --list |
grep license_server
2 If the License Server is not set to start running automatically, configure it to do so: chkconfig
license_server on. If the License Server was not started, start it: /etc/init.d/license_server start
3 View the usr/discreet/licserv/log/boot.log file for the License Server to ensure that the Burn license
is being read by the server and check:
■ The versions of Burn that are licensed for the network
■ The start and expiry dates for Burn licenses
■ The workstation or render node running as the License server for the background processing network
■ The availability of each Burn license for render nodes
4 View the /usr/discreet/licserv/licenses/DL_license.dat file to see the number of Burn licenses
purchased.
To check Burn licensing on a render node:
1 Log in as root to a render node that is not running the License Server.
2 Contact the render node or workstation running the License Server: ping <hostname> where <hostname>
is the hostname or IP address of the render node or workstation running the License Server. If this step
fails, check the network connection between the render node and the render node or workstation
running the License Server, then retry ping. Otherwise, continue to the next step.
Burn | 129