I'm having a few problems with my setup, some more important than others, but causing troubles for me all the same (I've listed them in priority)
1) Right now I have the default Scheduled rediscovery set in DFM to run weekly. That's all well and good, except that when it runs, less than 10 of my 664 devices get put into the "known" state, while the rest - after 6-8 hrs - get thrown into the "questioned" state. When I try to suspend the schedule, I get an error (see attached: rediscovery_error.jpg, and associated Rediscovery.txt). I have a case open with the TAC right now about this, but it has not been resolved. The only fix I have at the moment is to rebuild the DFM DB, then re-add all the devices, and then I have to unmanage all the interfaces/ips that I'm not using. Seems like an incredible waste of time.
2) When adding a new device to the DFM (automatically pulled when I add it to the DCR) all the existing devices return to their default managed/unmanaged state. Again, at this point, I have to go back and unmanage all the interfaces/ips, etc... (May be related to above, I'm not sure.)
3) My jrm.log file is currently sitting at over 650MB (not KB). This equates to roughly 7.3 million lines of text, where 99% of the lines are "Test Exception is : java.sql.SQLException: JZ0S2: Statement object has already been closed." (see attached: jrm.jpg)
4) I would also like to know if the emails that are sent out by the DFM can be changed - a lot of the information included in them is not relevant to me, and I would like to add the information that is.
I've also attached the output of pdshow and systeminfo, which seems to be the first thing most people are asked for.
I'm running LMS 3.1, with an updated DFM (3.1.3) on Windows 2003 Enterprise.
Please let me know if there is anything else I can provide that may help.
No, you cannot upgrade 3.1 to 3.2 piecemeal. You must do the entire bundle at once. You can upgrade from 3.1 to 3.2, but I typically recommend one take a backup of 3.1, uninstall 3.1, then install 3.2 from scratch. Once it is installed, then you restore the 3.1 backup, and the data will be migrated. This typically results in a much cleaner upgrade.
The solution to problem 3 is easy. That's known bug CSCsr93277. TAC has a patch for LMS 3.1, but the recommended fix is to upgrade to LMS 3.2. It sounds like problems 1 and 2 may be related to CSCsz08953 which is also fixed in LMS 3.2.
As for changing the emails, this really isn't possible. Only in LMS 3.2 did we add the ability to customize the subject, but the body is fixed. You can, however, disable the body, and only send the subject.