I recently installed LMS 3.2 on a virtual machine running Windows 2003 R2 Standard on VMware ESX 3.5 cluster to replace our current installation of LMS, which is 2.5 running on Solaris. This is a brand new installation and not an upgrade. For the most part, everything seems to be functioning properly with the exception of Syslog. After importing all of our network devices (about 200) into LMS 3.2, I started noticing issues with Syslog. When I run Syslog reports in RME, such as a 24 hour report for all devices, there are large and small time frames where there is no syslog data in the report. For example, when I ran a 24 hour report the other day there were the following time frames where there was no syslog data in the report for any of my devices:
Feb 08 2010 18:19:04 - Feb 08 2010 18:28:33
Feb 08 2010 23:05:39 - Feb 08 2010 23:10:15
Feb 09 2010 01:07:47 - Feb 09 2010 01:41:56
Feb 09 2010 05:03:46 - Feb 09 2010 06:38:00
During those times, there was syslog data being written to the syslog.log file on the server and we do not have any special syslog filters configured. Furthermore, since I still have my old LMS 2.5 server running, I can also verify on it that there should be syslog data in the report for those time frames. Both servers are pretty configured the same.
I have had a TAC case open since the beginning of February but they have made no progress on this issue. Furthermore, since this issue surfaced it has gotten worse.
Please assist. Thanks.