A single installation of an application on a single device can only consume against one license, so I would imagine from your description that there must be different application installations on a device affected by this consuming against the two different licenses. You may get some more insight into what is going on by looking at a inventory device record that is consuming against both licenses, and under the Applications tab of the device look to see which installations there are consuming against the PROD license you don't want. You may need to do something like exempt those installations from requiring a license, or ensure those applications are linked to the NON-PROD license.
In addition to this, as they are PVU licenses, you are most likely seeing a historical peak consumption. After you have made the changes, you will need to reset the PVU counts.
Perhaps the discussion seen here on managing Production and Non-Production licenses may be of use to describe the issues you are seeing:
This is fantastic information and I've got it working correctly for my "Prod" side licensing. I'm still having a challenge with the Non-Prod licenses. We are assigning "Non-Prod" licensing when a Prod license is installed. I'm thinking this is confusing the system.
I will let you know when I get this to work on both sides.
Thank you for your input,
Hi Shelby, one of the important factors is whether or not the installations of Prod and Non-Prod look different. Are they recognised as different applications in FNMS, or perhaps there is different evidence in FNMS for them?
It's actually pretty common that the installations look identical, hence the challenge to consume the correct license. In these cases we rely on information from the business/CMDB/Application Support to understand which installations are Production and which are Non-Production. Once we know this it is a case of allocating appropriately as per the other thread.
As mentioned, any use of Exemption in FNMS may well prevent a Prod license from being consumed by a Non-Prod installation, but it will also prevent that Non-Prod installation from consuming any other licenses, so is usually not the way to go and you may need to look at the Exemption by Role section of the Use Rights tab in both licenses to make sure this is not impacting your configuration.
Hi @shelby_day !
I have seen behavior like this before in the field. It's very tricky to manage allocations and exemptions - and it's important to understand that exemptions are a special type of allocation. It can be very easy to the same device to multiple licenses and then yes, FlexNet can't handle putting the same device in two places and bad things ensue.
BUT - I have also seen in the field real problems with this behavior, and I have a suspicion that there may be a real underlying problem. If you've validated that you're not double allocating any device, including exemptions, and that you haven't allocated the same host or cluster to multiple licenses, then you probably have something that Support should look at.
Senior Product Manager
I don’t speak for Flexera, and we should all be grateful for that
Thank you for the suggestion! I read the guide early on and perhaps it's time I revisit again as I'm still having just a few little issues.
hey, i was also looking for same suggestions.. thanks all for your responses,it saved my efforts and time.IBM License consumption would have been much easier if https://routerlogin.one/192-168-1-254/ was used for easy router login. best regards!!