Originally posted by: kahn

Hi,

We have some files such as below:

8286-42A_XXXXXXXXX_FLRT_20191111060621256-emgr.txt
8286-42A_XXXXXXXXX_FLRT_20191111060621256-lslpp.txt

  Once in a while, those files were automatically created and it looks like FLRT software is creating those files. Could somebody answer how these file is created and put those files in /tmp directory?

Originally posted by: janhar

Hello, Kahn

It seems the technical owner of the case you had opened thought FLRT was an AIX Toolbox package.  I noticed this and have asked an internal team to review your question on this forum.

I apologize for this error.  For future reference, if you have issues with FLRT, Select the "Feedback" button from the FLRT page. This will initiate a support ticket for the team which supports this tool. You will get an automated message, then will get a direct message from an FLRT team member.

Someone should provide an answer to your question soon.  

Cheers!

Originally posted by: Joel R.

Hi Kahn,

Those appear to be input files that are used with our FLRT Vulnerability Checker (FLRTVC), available through the FLRT website.

However, we do not generate any input files through our FLRT tools directly.  Indirectly, those files are generated by the users of our tool, or through IBM services like Call Home, which is setup on the HMC.  I'm not familiar with your environment, so it is difficult to identify the source.  

Does your team use any automated services that collect inventory?  

Please share any other information that may help.

Thanks!

Joel

Originally posted by: kahn

Hi Joel,

Thanks for your reply. I asked my co-worker and manager but nobody know how this files were generated so I don't think we create files to use FLRT tool. Regarding the setting of HMC, how could we check the IBM service such as "Call Home" from HMC to create those files?

Also how to create files to use the FLRT tool? So I can research more.

Kahn

Originally posted by: Joel R.

Hi Kahn,

We are still inquiring internally to find out which service might be generating these files.  

To generate the FLRT input files, there are several ways...

To use FLRT Vulnerability Checker (FLRTVC):
lslpp -Lcq > lslpp.txt
emgr -lv3 > emgr.txt

To use FLRT Microcode Discovery:
Users can use the inventory scout tool to generate a *.mup file
https://www.ibm.com/support/knowledgecenter/en/ssw_aix_72/i_commands/invscout.html

For the FLRT Recommendation Report:
We have a sample script that can be used by clients, Script #1 here:
https://www14.software.ibm.com/webapp/set2/flrt/sas?page=scripting

We will let you know as soon as we discover who is generating those FLRTVC input files.  The naming scheme of the lslpp/emgr txt files is a big clue we can use.  

Also, what tool does your team use for security?  PowerSC/BigFix/other?

Thanks!

Joel

Originally posted by: kahn

Hi Joel, 

Thanks for your reply. I am still looking for the answer so please let me know when you find anything.

Originally posted by: Joel R.

What tool does your team use for security?  PowerSC/BigFix/other?

Thanks,
Joel

Originally posted by: kahn

I am not sure. We use security tool such as Semantic and some of other security tools. Is the security tool cause this issue?

Originally posted by: Joel R.

It is unlikely, but I am trying to cover all areas.  

Originally posted by: kahn

Hi Joel,

I checked the URL that you gave in this topic and found that it check the IBM database via internet and give us the report that what we need to do. Is there any way that we can use FLRT to upgrade software in the server with a FLRT script ? (For example of Linux, we can upgrade a server using the repository that is located in the internet)