Multiple partitions on a machine!

Hello forum community!

We currently have the following problem with Deadline 5.2:

On each machine in our house, we have 2 Windows partitions installed, one for production (machine01-CAD), the other as a render partition (machine01-render).
On Both of these partitions, there is installed 3ds-max and they should be render able.

When a user starts the production partition, 2 slaves with the following Names would be created and started by Deadline: machine01-CAD + machine01-render.

So there are running 2 slaves on one Partition and thus two tasks. This is not what we want.
This leads to problems with 3D Studio Max (access violations, license overflow).

To avoid this error, I can only disable one of the two over Deadline monitor, in this case the machine01-render.

The behavior seems logical to me, because a machine has only one MAC address with a total of two IP addresses. For Deadline is thus difficult to distinguish which is running on the machine, and then instructs both slaves to a machine.

Currently, the following happens:

“Machine01” with MAC Address: “AA:BB:CC:DD:EE:FF”

2 Windows partitions with 2 slaves with different IP addresses:
192.168.1.5 = machine01-CAD + machine01-render
192.168.1.6 = machine01-render + machine01-CAD

However, the following is required:

“Machine01” with MAC Address: “AA:BB:CC:DD:EE:FF”

2 Windows partitions, each with a slave with different IP addresses:
192.168.1.5 = machine01_CAD (for production and rendering above day)
192.168.1.6 = machine01_render (for stable/secure 3dsMax Installation and rendering above night, Fallback when _CAD Partition has problems)

A solution which we have already tried without success:
Set “_CAD” partition to IPV6
Set “_render” partition to IPV4

Is this problem already known?
Has anyone of you a solution to my problem?

Hope you can understand my issue g

Greetings from Austria (Europe)

Dominik

Hi Dominik,

I think this issue might be solved in Deadline 6 (which is currently in beta). In Deadline 5, we added a feature that allowed you to run multiple slaves on the same machine, but it didn’t take into account situations like net-booting (where all systems share the same disk), or cases like yours. This resulted in multiple slaves launching on each machine. We have addressed this issue in version 6, which in theory should resolve the issue you’re seeing.

The Deadline 6 beta is still open, so if you want to join and test it out, shoot an email to beta@thinkboxsoftware.com.

Cheers,

  • Ryan