02-09-2017 05:26 AM
Hi All
A second issue I have since many versions of PI 3.0 and 3.1 is that after a reboot (or patch installation) the System Jobs aren't working anymore.
The "Next Start Time" then is in the past and they wont ever get started again. Affects nearly all of the "Wireless Monitoring" jobs, but also affects others. I have then to select the ones with a "Next Start Time" in the past, pause the series, select them again, resume the series. This works, until the next reboot or patch installation.
It would be great if this could be fixed.
Do you also have this in your installations?
Maybe it's a time-zone issue? Using CET here and it's synced by NTP.
02-13-2017 04:42 AM
Just discovered that this is probably a known issue:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc24922
Sadly the bug isn't public visible. It's mentioned in the 3.1.5 release notes (the third last bug under open issues):
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-1-5/release/notes/cpi_rn.html#pgfId-195454
01-07-2020 07:49 AM
Same here. Prime 3.4 - System jobs to not reset after reboot. All the times to run are past on a lot of reports.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide