Unsolved
This post is more than 5 years old
1 Rookie
•
29 Posts
0
11990
September 26th, 2012 08:00
Inventory Schedule did not run at all
Hello All,
Could you give some directions here. The discovery and inventory schedules have been setup to run nightly. However, only discovery schedule ran. The inventory schedule did not run at all. OME version is 1.0.1.1253
Thanks
Joshua
No Events found!


DELL-Abhijit P
Community Manager
•
711 Posts
0
September 26th, 2012 08:00
Hi Joshua,
Thanks for your post. What data are you looking at to determine if the inventory tasks ran? Is this a fresh install? Are you saying that inventory tasks never ran after you installed? Do you see any inventory information for the discovered devices?
Regards
Abhijit
Joshua_n
1 Rookie
•
29 Posts
0
September 26th, 2012 15:00
Hi Abhijit,
Thank you very much for your help. Here is my problem. OME was installed on Aug, 2012 and inventory schedule showed the same day as installation. However, discovery and inventory schedules have been enabled and scheduled run nightly. The discovery schedule has run correctly but inventory have not. I can run inventory manually but not schedule. I found out because I ran some firmware update manually on three servers. However, OME still shows those servers firmware out of date (non-compliance). If I run inventory manually, then everything is up to date on OME.
Please, let me know if you have any questions.
Joshua
DELL-Abhijit P
Community Manager
•
711 Posts
0
September 26th, 2012 16:00
Hi Joshua,
Thanks for the update.
If you see compliance report, it is possible that the inventory is running on schedule. Inventory is responsible for getting the installed versions of components which is used as input to generate compliance reports.
OME has the logic to kick off inventory on completion of updates. Sometimes if the server is rebooted as part of update or the update completion is not reported back to OME, it may not kick off the inventory cycle. That would explain why you had to manually run inventory after the updates.
Another thing to look at is the "Last Inventory Details". You can find that entry by going to Manage->Discovery and Inventory->Discovery Portal" That will show you the date and time for last inventory run.
Regards
Abhijit
Joshua_n
1 Rookie
•
29 Posts
0
September 27th, 2012 06:00
Abhijit,
I do not understand this. Can you give me some ideas? I looked at last inventory details by Manage-->Discovery and Inventory ---> Discovery Portal: it showed the inventory ran last night as schedule. However, if I checked the last inventory detail at Discovery Portal---> Discover range---> Include ranges: IP address range. Then the inventory did not ran last night. However, it showed the date that I ran manually. Again, this IP range inventory has been enabled to run nightly.
Thank you very much for your help!
Joshua.
DELL-Abhijit P
Community Manager
•
711 Posts
0
September 27th, 2012 07:00
Hi Joshua,
Thanks for the updates.
I agree the display does cause some confusion. Currently the discovery/inventory tasks in OME are not really separated by IP ranges. When discovery/inventory is run on schedule, it is run for all IP ranges. Since it is not granular, the data is not really stored for inventory run for each range. This results in last inventory time not available for the individual ranges. We are looking at improving this behavior in future and having granular discovery/inventory schedules so that each range can run separately on separate schedule.
For now, if the discovery portal specifies the time for last inventory run, it does mean that inventory was executed. As I mentioned earlier, if inventory is not run, you will not see most of the inventory information and you will not see any data in compliance reports for servers.
Regards
Abhijit
Joshua_n
1 Rookie
•
29 Posts
0
September 27th, 2012 07:00
Abhijit,
Thank you very much for your info.
Best regards,
Joshua
DELL-Abhijit P
Community Manager
•
711 Posts
0
September 27th, 2012 08:00
Thanks for your feedback. As I mentioned we will surely look at cleaning this up to avoid any confusion.
Regards
Abhijit