IBM License Metric Tool (ILMT)

IBM License Metric Tool (ILMT)

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only
Back to discussions
Expand all | Collapse all

ILMT importing incorrect Last Seen date from disconnected scans

  • 1.  ILMT importing incorrect Last Seen date from disconnected scans

    Posted Tue March 08, 2022 10:12 PM

    The "Last Seen" date of a large number of disconnected scans are being imported incorrectly (as many months in the past) by ILMT.

    The disconnected scan file names are in the correct format - <YYYYMMDDHHMM>-<endpoint_ID>.zip and, the date is also current.

    The contents of these scan packages are being imported successfully, just the Last Seen date is way in the past.

    e.g. computers with scan files starting with 202203070435- are showing up with a Last Seen date of 03/10/21.

    Was wondering if anyone else is encountering this and what the issue might be?

    ILMT version is 9.2.26

    Thanks,

    -nb



    #AIX
    #Support
    #SupportMigration


  • 2.  RE: ILMT importing incorrect Last Seen date from disconnected scans

    Posted Wed March 09, 2022 06:40 PM

    "Last Seen" means "Data and time when last connected to the Bigfix Server"

    This is a disconnected scanner, so it never connects to the bes Server.

    I have noted that our documentation no longer lists "Last Seen" in the reported columns. https://www.ibm.com/docs/en/license-metric-tool?topic=reports-report-columns#gloss_L You can see the column description by mousing over the the name in that column.



    #AIX
    #Support
    #SupportMigration


  • 3.  RE: ILMT importing incorrect Last Seen date from disconnected scans

    Posted Wed March 09, 2022 08:39 PM

    Hi.

    Thank you for your response. What you mentioned is indeed correct. However, the Last Seen field is still in ILMT and appears to be used to "decommission" servers and this is happening incorrectly because the Last Seen date is not being populated correctly in ILMT.

    In our environment, there are 30k endpoints. We have configured the following parameters in order to automatically decommission any computer not seen for more than 90 days:

    Automatically decommission inactive computers = trueMaximum visibility of data for inactive computers = 90 days

    So, a large number of computers are being decommissioned even though they are active and a fresh disconnected scan has just been received.

    ---

    I did the following test:

    One server with a scan date of 07-March-2022 was imported and it's Last Seen date was set to 03/10/21. Original disconnected scan file:

    202203070452-ABCD1873-abf74e6f-7952-4d2f-9778-d17836968049-1611730671.zip

    I changed the filename to reflect 08-March-2022 and reimported the scan - it imported with a correct Last Seen date of 03/08/22.

    Changed filename:

    202203080452-ABCD1873-abf74e6f-7952-4d2f-9778-d17836968049-1611730671.zip

    ---

    This is happening to quite a few computers. So I am wondering whether there is an ILMT bug or some issue with the disconnected scan files.



    #AIX
    #Support
    #SupportMigration


Related Content