This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
A new Flexera Community experience is coming on November 25th. Click here for more information.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Knowledge Base
- :
- Different computers map to the same compliancecomputer
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Subscribe
- Article History
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Summary
This article covers the enhancement that was created to support LDOMs.Symptoms
We have here that different computers report inventory, they appear as different within the inventory database and in the ImportedComputer table in the compliance database and then are mapped to just one compliance computer.As far as we were able to investigate this, this happens to several global zones on the same hardware (Solaris M9000). The global zones have the very same firmware serial number, but have all different systemid, identifying number and so on. The configuration in Solaris must be via LDOMs, which allows to partition one hardware machine into several hardware machines having their own global zone (one of these global zones is attributed as "master" though).
There must be an error in the matching process during recon (matcher step). For these cases the matcher must not match machines with the same firmwareserialnumber into just one compliancecomputer.
Resolution
The enhancement around support for LDOM is tracked under FNMS-39933 and has been addressed in FlexNet Manager Suite 2017 R1May 31, 2018 02:11 AM
Labels:
No ratings
