Backburner on multiple subnets

[BrianKitts]

Is anyone operating backburner on more than one network subnet?

 

I'm currently expanding our renderfarm and I have recently found online that backburner can only execute on one subnet, which limits it's maximum nodes to 255.

 

We have 200+ computers so they are networked on two different subnets, of which I now have about 60 of the machines working successfully, but I would like to get the other 40 that are on this floor online as well. The only way I am able to add any of the rest is to manually change their IP over to the correct subnet. A pain....but it works.

 

So the main problem is this, IT wants to keep all the machines on dynamic IPs, so switching to static isn't an option, meaning if a machine is shut off and brought back up later it has the possibility of coming online with the wrong subnet, in which case it can not communicate with the manager. BTW I'm using the IP address to locate the manager not the subnet search already, thought it would help...but didn't.

 

SOO..... hmmm anyone have a workaround for this or any ideas in general??

 

thanks - brian

[RenderSpeed]

A subnet can be 4294967296 ip's. Backburner will work fine outside the subnet if you specify the managers ip.

[Matt Clementson]

It depends on your subnet - sounds like your system is running a 255.255.255.0 subnet mask (and likely 192.168.x.x numbering) which as you rightly say limits you to 256 IPs in that subnet.

 

Talk to your IT team and get them to use a 255.255.0.0 subnet (and therefore 10.x.x.x IP numbering) - this should be easy to swap if everything is dynamic IPs anyway - this will give you 65536 (or 256x256) IP addresses to use and backburner should work fine on that subnet.

[Dave Buchhofer]

yea, we're just working with the 255.255.0.0, I dont know that I'd want all 300 systems hitting the manager, nor the fun of upkeep on those installs (or rather, the login scripts heheh). but it does work across larger subnets

 

Edit, misunderstood the question.. Yea that does seem a sort of backwards way of setting it up.

[RenderSpeed]

Another solution is to just use your own ip range, maybe a 10.0.x.x if your office isnt using that range. Tell backburner to locate the manage by ip and not by autodiscover.