Hi @AmazonRobotics-123
Please see FlexNet Publisher License Administration Guide Chapter 14. Ensuring License Availability (page 188).
Because FlexSim licenses are Trusted-Storage-based, only the option "Redundancy using the license search path" (page 188) is available. Essentially this means that your seats have to be spread across multiple license servers, and if one license server goes down, the seats that are hosted there are unavailable, but seats on other additional license servers that are still operational remain available.
So, if you have 12-seats, and spread them across 3 servers, you really will just activate 4 seats to each license server. Then if you lose one server, you still have 8 seats available while you work to restore the missing 4 seats.
In practice, a dedicated license server really does so little, and is so stable, that redundancy has never been an issue. My suggestion is just to maintain a single activated license server. If you really want, you could have a 2nd unlicensed server in reserve that is configured and ready to go, where all you'd need to do is reach out to our support team to recover your seats for activation to the 2nd server. However, I've never seen or heard of a backup license server being necessary or used.
- I'm not sure the exact heartbeat interval. I've heard rumors of 15 minutes, but don't quote me.
- The model won't necessarily crash, but if it uses any licensed features, those will revert to the free Express mode. See FlexSim Feature Limitations by License Type. For instance, reverting to Express means that the random number generator will become locked.
- See above for failover options and details - spreading your seats over multiple license servers is really the only option. In the above example of 12 seats and 3 license servers, the client software would be configured to look for a license from any of the 3 license servers. If it can't contact one license server, or if the seats are all in use, it would move to attempt communication with the next license server, and so on.
Again, we just haven't seen that in practice a high-availability setup is necessary for a simple lmtools-based license server.