Redundant Servers: defining the master

In a redundant server configuration, the first three lines of the license file look like the following:

SERVER SERVER1 000000000000 27005
SERVER SERVER2 000000000000 27005
SERVER SERVER3 000000000000 27005

With these settings the master server may change at every restart of the services. This could make license borrowing a little trickier and the log file would be written across the three servers causing difficulties to maintenance, analysis and reporting.
To avoid this you can define the master server adding the “PRIMARY_IS_MASTER” attribute to the first line of the license file:

SERVER SERVER1 000000000000 27005 PRIMARY_IS_MASTER
SERVER SERVER2 000000000000 27005
SERVER SERVER3 000000000000 27005

With this parameter, if the primary server goes down, when the primary server comes back up again, it will always become the master. If this is not set and the primary server goes down, the secondary server becomes the master and remains the master even when the primary server comes back up.
Note: You must be running a version 10.8 or later vendor daemon to use this parameter.