If you have Firewalls sending logs to LMS, this could bring heavy load on the server.
Another issue could be the name resolution mechanism for syslog messages and a slow or even failing DNS for these requests.
In LMS 2.6 - LMS 3.0.1 this could be enabled/disabled in
Common Services > Server > Admin > System Preferences
But it seems that they removed this config point in LMS 3.1 - at least I cannot find it...
These log files could shed some light on this:
Also the defined syslog filters could have an impact and slow down the process.
As a last resort, you also can try to just restart SyslogAnalyzer and SyslogCollector process and see if the problem goes away. You should do this in a one-liner to avoid a manual resubscription of the SyslogCollector
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...