Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi Oktawian,

Are you referring the below option in AAP?

If not, could you please share more details?

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi Oktawian,

Could you give some example where I can edit the playbook for cronjob configuration in AAP?

" use a 'Ansible cron module' to automate the crontab entries via playbooks."

Thanks,

Nagarajan. 

Hi Oktawian,

Are you referring the below option in AAP?

If not, could you please share more details?

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hello Nagarajan,

Sorry for a delay...

I should clarify one thing,
You don't have to create cronjobs in all the endpoints.
'lmt_collect_results.yml' playbook needs to be scheduled on Control node...it means one endpoint.
I'm pretty sure that you will manage to manually create a single crontab entry on Control node.

Hi Oktawian,

Could you give some example where I can edit the playbook for cronjob configuration in AAP?

" use a 'Ansible cron module' to automate the crontab entries via playbooks."

Thanks,

Nagarajan. 

Hi Oktawian,

Are you referring the below option in AAP?

If not, could you please share more details?

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi Oktawian,

Q: you don't have to create cronjobs in all the endpoints.

A: Yeah, I will not create the cron-job in all the endpoints. but in AAP console we have option to schedule the template like below screen shot. 

Using the screenshot option, we could schedule the Upload/collect result.yml file in AAP and Limit we could set for all the Linux platform servers. 

So, there is no cron tab module create for it again, right?

Thanks,

Nagaraj. 

Hello Nagarajan,

Sorry for a delay...

I should clarify one thing,
You don't have to create cronjobs in all the endpoints.
'lmt_collect_results.yml' playbook needs to be scheduled on Control node...it means one endpoint.
I'm pretty sure that you will manage to manually create a single crontab entry on Control node.

Hi Oktawian,

Could you give some example where I can edit the playbook for cronjob configuration in AAP?

" use a 'Ansible cron module' to automate the crontab entries via playbooks."

Thanks,

Nagarajan. 

Hi Oktawian,

Are you referring the below option in AAP?

If not, could you please share more details?

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hello Nagarajan,

Sorry, I have no access to Ansible Automation Platform.
Thus, I wouldn't want to speculate how this whole Dynamic Scheduler is processed internally.
It could be through a cron job or it it could be some kind of dedicated daemon which is processing all those scheduled events...

Hi Oktawian,

Q: you don't have to create cronjobs in all the endpoints.

A: Yeah, I will not create the cron-job in all the endpoints. but in AAP console we have option to schedule the template like below screen shot. 

Using the screenshot option, we could schedule the Upload/collect result.yml file in AAP and Limit we could set for all the Linux platform servers. 

So, there is no cron tab module create for it again, right?

Thanks,

Nagaraj. 

Hello Nagarajan,

Sorry for a delay...

I should clarify one thing,
You don't have to create cronjobs in all the endpoints.
'lmt_collect_results.yml' playbook needs to be scheduled on Control node...it means one endpoint.
I'm pretty sure that you will manage to manually create a single crontab entry on Control node.

Hi Oktawian,

Could you give some example where I can edit the playbook for cronjob configuration in AAP?

" use a 'Ansible cron module' to automate the crontab entries via playbooks."

Thanks,

Nagarajan. 

Hi Oktawian,

Are you referring the below option in AAP?

If not, could you please share more details?

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi Oktawian,

Could you share some example for "cron job" in "lmt_collect_results.yml" edit parameter?

I am not clear where to add what module in it. Could you share the details?

Thanks,

Nagarajan. 

Hello Nagarajan,

Sorry, I have no access to Ansible Automation Platform.
Thus, I wouldn't want to speculate how this whole Dynamic Scheduler is processed internally.
It could be through a cron job or it it could be some kind of dedicated daemon which is processing all those scheduled events...

Hi Oktawian,

Q: you don't have to create cronjobs in all the endpoints.

A: Yeah, I will not create the cron-job in all the endpoints. but in AAP console we have option to schedule the template like below screen shot. 

Using the screenshot option, we could schedule the Upload/collect result.yml file in AAP and Limit we could set for all the Linux platform servers. 

So, there is no cron tab module create for it again, right?

Thanks,

Nagaraj. 

Hello Nagarajan,

Sorry for a delay...

I should clarify one thing,
You don't have to create cronjobs in all the endpoints.
'lmt_collect_results.yml' playbook needs to be scheduled on Control node...it means one endpoint.
I'm pretty sure that you will manage to manually create a single crontab entry on Control node.

Hi Oktawian,

Could you give some example where I can edit the playbook for cronjob configuration in AAP?

" use a 'Ansible cron module' to automate the crontab entries via playbooks."

Thanks,

Nagarajan. 

Hi Oktawian,

Are you referring the below option in AAP?

If not, could you please share more details?

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hello Nagarajan,

Following is simple example how to schedule the cron job to run  "lmt_collect_results.yml" playbook:

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi Oktawian,

Could you share some example for "cron job" in "lmt_collect_results.yml" edit parameter?

I am not clear where to add what module in it. Could you share the details?

Thanks,

Nagarajan. 

Hello Nagarajan,

Sorry, I have no access to Ansible Automation Platform.
Thus, I wouldn't want to speculate how this whole Dynamic Scheduler is processed internally.
It could be through a cron job or it it could be some kind of dedicated daemon which is processing all those scheduled events...

Hi Oktawian,

Q: you don't have to create cronjobs in all the endpoints.

A: Yeah, I will not create the cron-job in all the endpoints. but in AAP console we have option to schedule the template like below screen shot. 

Using the screenshot option, we could schedule the Upload/collect result.yml file in AAP and Limit we could set for all the Linux platform servers. 

So, there is no cron tab module create for it again, right?

Thanks,

Nagaraj. 

Hello Nagarajan,

Sorry for a delay...

I should clarify one thing,
You don't have to create cronjobs in all the endpoints.
'lmt_collect_results.yml' playbook needs to be scheduled on Control node...it means one endpoint.
I'm pretty sure that you will manage to manually create a single crontab entry on Control node.

Hi Oktawian,

Could you give some example where I can edit the playbook for cronjob configuration in AAP?

" use a 'Ansible cron module' to automate the crontab entries via playbooks."

Thanks,

Nagarajan. 

Hi Oktawian,

Are you referring the below option in AAP?

If not, could you please share more details?

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj. 

Hi Oktawian,

Excuse me for more questioning, 

Q: <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored

A: It mean you are referring in AAP servers where the playbook stored and execute/create the cron job in AAP server itself? 

Also, If we scheduled the cron job using "collect result.yml" file and "inventory.yml" plybook on AAP servers then how the manage node will share the results files to ILMT Datasources?

Could you please give some more details?

We are using AAP in Red-hat cloud platform. 

Thanks,

Nagarajan. 

Hello Nagarajan,

Following is simple example how to schedule the cron job to run  "lmt_collect_results.yml" playbook:

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi Oktawian,

Could you share some example for "cron job" in "lmt_collect_results.yml" edit parameter?

I am not clear where to add what module in it. Could you share the details?

Thanks,

Nagarajan. 

Hello Nagarajan,

Sorry, I have no access to Ansible Automation Platform.
Thus, I wouldn't want to speculate how this whole Dynamic Scheduler is processed internally.
It could be through a cron job or it it could be some kind of dedicated daemon which is processing all those scheduled events...

Hi Oktawian,

Q: you don't have to create cronjobs in all the endpoints.

A: Yeah, I will not create the cron-job in all the endpoints. but in AAP console we have option to schedule the template like below screen shot. 

Using the screenshot option, we could schedule the Upload/collect result.yml file in AAP and Limit we could set for all the Linux platform servers. 

So, there is no cron tab module create for it again, right?

Thanks,

Nagaraj. 

Hello Nagarajan,

Sorry for a delay...

I should clarify one thing,
You don't have to create cronjobs in all the endpoints.
'lmt_collect_results.yml' playbook needs to be scheduled on Control node...it means one endpoint.
I'm pretty sure that you will manage to manually create a single crontab entry on Control node.

Hi Oktawian,

Could you give some example where I can edit the playbook for cronjob configuration in AAP?

" use a 'Ansible cron module' to automate the crontab entries via playbooks."

Thanks,

Nagarajan. 

Hi Oktawian,

Are you referring the below option in AAP?

If not, could you please share more details?

Thanks,

Nagaraj. 

Hello Nagarajan,

I believe that you could use a 'Ansible cron module' to automate the crontab entries via playbooks.
(One small correction to my last post:   'lmt_inventory.yml' -> 'lmt_collect_results.yml').

Hi Oktawian,

yeah, my question is that "how we can schedule the cronjob using "Collect result.yml" file from AAP console?
or we have to create the cronjob manually in all the endpoints?

Thanks,

Nagaraj. 

Hello Nagarajan,

I don't fully understand your question...
However,  'lmt_inventory.yml' execution (to collect result/upload result) can be scheduled within crontab configuration.

Hi Oktawian,

Thanks for the update and If we see the upload (collect result) yml task from AAP mean it is working properly in ILMT property value and files also moved from endpointes to ILMT data sources. 

So we have option to schedule the scan time using (inventory.yml) file with Install/upgrade task. like that do we have such option for collect result/upload result from playbook itself?

Thanks,

Nagarajan.

We have manually ran the "collect result" yml job in AAP mean the scanned file not there in endpoints, maybe it moved to "data sources" directory. But the actual server I can see "Last software Scan Attempt" is running as per scheduled. 

below are the screen shot from task scheduler from the same server. 

The concern here I am not seeing the updated date/details in ILMT web console for "Last scan Attempt" property. it is always showing very old date even the scan running multiple times as per scheduled on endpoint. 

Is there any advice do I need to follow to overcome this issue. 

Thanks,

Nagaraj. 

Hi Oktawian,

Could we do the schedule option from collect result playbook over AAP ?

Like we are scheduling the scan in "inventory.yml" and deploying the Install/upgrade scanner playbook right. because we have 100+ servers and below cmd need to Initiate in every endpoint?

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Corrent me if I am wrong. 

Thanks,

Nagaraj. 

Hello Nagarajan,

From that output I don't see 'lmt_collect_results.yml' playbook being listed.
Please make sure to add a cron job to cover that....
  

For example, to schedule the command to run every day at 2:30 AM use the following syntax for crontab configuration :

30 2 * * * "ansible-playbook <LMT_upload_playbook_files_directory>/lmt_collect_results.yml -i <LMT_upload_playbook_files_directory>/lmt_inventory.yml"
where <LMT_upload_playbook_files_directory> is the directory where the playbook files are stored.

Hi, Cron job is scheduled for scan process. also Import is running with out any error. 

Hello Nagarajan,

Do you see any updates within '../logs/log.txt' file of disconnected scanner directory ?

You've mentioned that there is cron task for weekly base scan...
The thing is that in the Ansible case, the schedule of daily collection of scan results is done by means of 'lmt_collect_results.yml' playbook.
Is that playbook listed in crontab setup ?

At last, perhaps there are some import issues of that disconnected scanner package...
to find out, it's ILMT import logs to be verified...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Mon July 10, 2023 10:18 AM
From: Nagarajan Singaram
Subject: ILMT Wb-console Property Not updating

Hi All,

I am using ILMT v9.2.0.31 with Ansible automation platform in my infra. here we are facing one Issue in ILMT web-console property name called "Data delayed upload" is showing "Yes" and Last Scan Attempt showing "very old date". But in endpoints cron task running for weekly base scan (Initiate scan) process. 

Is there any way to updat the "Last scan attempt" property value in ILMT console. or how to troubleshoot the process to see the current scan date & time for the property.

Thanks,

Nagaraj.