Showing results for 
Show  only  | Search instead for 
Did you mean: 

IBM Power 8 and 9 Server agent

How can our enterprise get data on IBM Power 8 and/or 9 servers in our enterprise since there is not an agent in Flexera for these ?

(8) Replies

@JimHott2 - Support for Linux on IBM PowerPC was added in FNMS 2022 R1.

Go to the following link, and scroll down to review the platforms supported by the 2022 R1 Inventory Agent, the section is labeled FlexNet Inventory Agent.


We can verify agent is installed and running on ~2000 Linux servers, but oddly 105 are not showing in inventory. We are running or on FNMS current version - 2020 R1.

Currently, if we can verify that the agent is installed and running, that’s all we can do from the Unix side.

Can you direct us how we can determine why the 105 non-power agents are not showing in Flexera inventory ?

The most likely scenario is that the agent is not able to get a connection to a beacon server over port 80/443.  In other words, the agent is running and gathering inventory but is not able to successfully upload the inventory file to a beacon.

On Linux, the Flexera Agent Log files are found in /var/opt/managesoft/log 

I would start by looking at TRACKER.LOG (which is the log file generated by the agent when running the inventory scan.  At the end of the log file is the results of attempting to upload to a Beacon, which you will be able to tell if successful or not.

For O/S releases for Linux on Power, it’s big-endian support we need. Will there ever be a future version of FNMS that supports it ?

Hi Jim, 

Thanks for reaching out, current Linux on PowerPC supports ppcle architecture. based on the research, LE becomes the predominate application compilation for Power Systems, that is why we have gone for Linux on ppcle architecture support.

At this stage, we have not considered BE support and will keep on watching if the current demand changes.

Is your company plan to stick with BE or have any future transition plans to move from BE to LE?



We have a Cognos implementation that requires BE,  so we will not be moving from that.


In checking servers in our list, I do not see the "TRACKER.LOG" referred to.

[root@aiawlgpp01 log]# pwd
[root@aiawlgpp01 log]# ls -la
total 1328
drwxr-xr-x. 2 root root 90 Oct 7 2021 .
drwx------. 7 root root 72 Oct 7 2021 ..
-rw-r--r-- 1 root root 725790 Mar 13 01:05 installation.log
-rw-r--r-- 1 root root 368084 Mar 13 01:05 policy.log
-rw-r--r--. 1 root root 245368 Mar 13 01:05 schedule.log
-rw-r--r--. 1 root root 1675 Mar 12 02:15 usageagent.log
[root@aiawlgpp01 log]#

JAHOTT@AEP.COM | D:614.716.1623 | A:8.200.1623

@JimHott2 - That means that the agent is not able to connect to a beacon and download the Policy, which contains the inventory schedule.  Please review the Installation, Policy and Schedule log files.