Hi Flexera Support Team,

We are using FlexNet license server version FLX_VERSION_LONG "2019.04.0.246634" in a main/backup HA setup for floating licenses.

Currently, when the main server is down, the backup server serves licenses only for about 3 days and then stops due to the backup maintenance interval.

We would like to understand:

1. Can server.backupMaintenance.interval be set to infinite?
2. If yes, are there any known risks or unexpected behaviors with long-term backup operation?
3. Is there a recommended value for customers who need a DR window longer than 72 hours?

We are also evaluating a license server upgrade, so any guidance on best practices or limitations for this setting would be helpful.

Environment:

80 windows 11 computers.

30-40 have flexnet service license agent installed

Products that use flexnet in our environment include ARCGIS, EFI, MathCad, and Autodesk.

Problem:

Flexnet service broadcasts arp requests ever 2 minutes from each computer. This results in an unusually high amount of broadcast traffic on our network. Because the computers are not in a cloud environment, they never receive an answer and they continue to send the requests.

Why is this a problem?:

ARP traffic on this network consists of about 60% of the broadcast traffic and 20% of these requests are from the flexnet service. This is unnecessary as we are not in a cloud environment.

Request:

I would request a way to disable this feature in the service.

Is this possible?

Thanks,

James

Hi,

Migrating from FlexNet Device Manager version 5.1.2 (Avid Floating Licence Server) to FlexNet License Server Manager version 2021.12.2.

I’m struggling to find the same data in the new API calls. For years I’ve been parsing XML data from the API endpoint ‘/fne/xml/features‘ and ‘/fne/xml/devices’ to plot usage:

From ‘/fne/xml/features‘ for each feature name I get the count.

From ‘/fne/xml/devices’ for each device feature name I get the served count, reserved count and reserved used.

From ‘/api/1.0/features’ I can get the featureName, featureCount, used and reserved.

But ‘/api/1.0/clients’ does not return the feature name used or whether it’s reserved.

Seems what was previously quite simple may be quite a complex lookup and cross-reference of hostid’s. It looks like you’d have to lookup all of the reservationgroup id’s to get a list of reserved hostid's, then lookup these hostid's in the clients json, to see whether a reserved licence is in use.

Has anyone experienced this? Just wanted to check I’m not missing something before I start trying to migrate my code!

Kenny