John -
You might want to rethink the redundant server model. Most of the Autodesk
network guru's recommend against the redundant model in favor of the
distributed model.
The redundant model requires that there be flawless communication between
the server "partners". If they decide they can't talk they can start
failing. (Note: I have set up a redundant pool before and I didn't
experience any problems, but it was in a test environment, so your mileage
may vary). When I actually set up FlexLM for production, I used a single
server. Worst case I can yank out the network card, stick it in another
machine and have it back up and running in about 15 minutes. What 15 minutes
downtime will cost you depends on your particular environment.
The distributed model generally offers the "eggs in a basket" solution that
people are looking for, without the dependency on network communication that
can be the downfall of the redundant model. Basically you simply divide your
licenses up amongst the servers rather than having them all on all the
servers. Example: you have 30 AutoCAD licenses. You divide them up into
groups of 10 and put 10 on each server (you had to have 3 servers with the
redundant model). Now, if you have a server failure, you've still got 20
licenses up and running (it's not perfect, but it isn't the end of the
world). If 2 servers go down, you've still got 10 licenses (with redundant
licensing if 2 servers die you have no licenses).
I'm not saying don't do the redundant model, just don't dismiss other
implementations.
hth
jason martin
"jah5869" wrote in message
news:f0d8129.-1@WebX.maYIadrTaRb...
> In the redundant model of FlexLm can you use the LM_LICENSE_FILE variable
to point to the master server and its backups or are you forced to use the
licpath.lic?
> If you do have to use the .lic file is there an easy way to copy out this
file with a client deployment?
> Thanks in advance.
> John
>
>
