Hi, The concerned product in query is not a Flexera Product but it belongs to "OutBack Powers". you may need to redirect your query in respective forum. Regards, AP ... View more

Hi, "FLEXnet insists on demanding a license for the Ethernet-connected NIC rather than the "dongle"." - Can you elaborate? What's the observation - error? Message box? Any error code? It looks like your Ethernet cable has taken a priority over the dongle NIC, hence when Flexlm code does an IP tagging, it finds the IP of Ethernet first and NIC later - Found first will be treated as the IP address of device (Networking). I believe your license is bound with NIC IP address, which doesn't take precedence over the Ethernet one. You can play with the priority of adapter(s) or manage who gets taken first by managing the "Automatic Metric" and prioritize the dongle NIC. I doubt if it has anything to do with the FlexLM. Regards, AP ... View more

Hi, I vaguely remember from past experiences that "51315" represented the "FLX_ACT_TRAN_ERR_RSP_REQUEST_UNTRUSTED" i.e. Can't invoke non-Config response actions when matching request UNTRUSTED Hope it helps. Regards, AP ... View more

Great news...... Happy to help. Regards, AP ... View more

Hi Ap, yes, maybe in the next release .... ... View more

Hi Quan , I believe Carmen Man should be in touch with you by now. If that's not the case, then kindly update. Regards, Abhay ... View more

Hi Bastian, My confusion here is whether the attempt is to do activation borrow or normal certificate side borrow? Reason of confusion is that, a duration of value 4380 = 1 year, such a long value can't be given for certificate borrow. So it must be an activation borrow. But, for activation borrow no registry entry is created. By any means have you been doing an activation borrow of a feature and normal borrow of another and both? Regards, AP ... View more

I believe 'Paul Catalano' is already in touch with you. Isn't it the case? Regards, AP ... View more

It looks like this is a redundant server (3 server) setup. And from the lmstat output it seems that either server is down or the specific unix system is not able to connect to the primary server here. You may try with a simple ping and check if the primary server is reachable from the problematic system here. If yes, then try with "lmstat -a -c 27018@dldeffmimp05lic,27018@dldeffmimp06lic,27018@dldeffmimp07lic" (check for the comma or semi comma in between the port@host combinations). ... View more

HI There, I believe you got confused in between BORROW and LINGER functionalities. BORROW: With this particular keyword in your licensing rights (license file), you can borrow a license from server and return it when client wishes (only if early borrow return is supported by server - through lsvendor.c) In borrow, a borrow cache is ceeated at server system as well as on client (look into the document for the locations of those files). LINGER: This functionality allows the licenses to be checked out from a particular client, even after checkin. So, unless and untill the duration is over, it can't be returned. In case of LINGER only server side borrow cache is created. So, (its a kind of hack) if you have the server hosted locally, then go to the server borrow cache location and delete the file. Restart the server. It should solve your issue. A word of advise though, only use LINGER in case of applications which take no more than 60 seconds to complete. Regards, Abhay ... View more

Hi, I believe FNP kind of always supported the conventional Ethernet interface names i.e. eth(0) to eth(9). Starting FNP 11.11 (Ladakh) release, it also started supporting non-conventional ethernet interface names (for ex: eth_pc1, nan_phys ... etc). Be advised that there were few bugs as well in FNP 11.11 (in regards to the interface hostid detection behavior), which were resolved in later releases. Regards, Abhay ... View more

This could be a case of clients not able to communicate outside the network. Insure that's not the case by simply pinging the triad systems from each client (from different zones). Also insure that you are setting the license path as in designated structure for 3 server (something like port1@host1,port2@host2,poprt3@host3). This varies in case of windows and non windows. Please refer to the document, which kind of elaborates in a much better way. (helped me in past) ... View more

Probably you mean about the diskless network, where we can either have a dedicated network storage or router storage , which means that each client doesn't have its own disk volume but shares (or not) a networked storage which boot through PXE. From my experiance, i havn't seen any notifications from Flexera about this. But i believe a carefully choosen licensing model should work with FNP and diskless environment. Howover the DISK_SER_NUM is used only in case to distinguish in between different clients, (becasue VSN are supposed to be unique). I am not sure how would using this particular attribute will help you. You might wanna try with either IP address or FQDN. Regards, Abhay ... View more

there seems more to the issue here. Probably a formal support ticket would be the best way to get Flexera Engineering people involved. Regards, Abhay ... View more

If my memory serves me correct, then in recent past (probably with FNP 11.14.1) couple of issues with checkout performance were resolved. Having said that if you are using FNLS (Flexnet Licensing Service), then there are chances to have a slight performance degradation (since virtualization checks as a prerequisite has been added in recent Flexnet SDK). If you have not installed Flexnet Licensing Service (installanchor), then next step should be install it and try. If problem persists then probably Flexera Support is the right place to give a call. The release note from a previous version states: "License administrators administering certificate-only license servers that use virtualization features now need to install the FNLS. Additionally, when installing the license server as a Windows service, a start-permission DACL needs to be applied to the FNLS – this allows the license-server-service to start the FNLS. This can be done in lmtools by selecting the “FlexNet Licensing Service Required” checkbox, which applies the DACL to a pre-installed FNLS. Lmadmin applies the DACL automatically when installing itself as a service, provided FNLS has been pre-installed. Note: producers must ensure FNLS is installed before configuration of the license server as a service: neither lmadmin nor lmtools attempt installation of the FNLS." ... View more