Comments
-
I have failed to understand how a basic feature for any network administrator has not been incorparated in any of the previous releases for Solarwinds. Anyway, I have managed to get this working in v9.5.1 by use of custom SQL scripting which groups # of flaps by its hostname. This report is then displayed on the home page…
-
Is anyone able to answer the above? I have not found a solution to this yet. Solarwinds has also been unable to provide any examples of how this would be achieved. This leads me to believe, is this even possible? The 'unplugged' feature is only to surpress alerts on specified interfaces.
-
Thanks for the reply. The solution you have suggested I still think it does not really answer the question of detecting a flapping port/interface. We would like to detect ANY flapping port. Whether this may be a:- * Uplink * User interface * Serial Connection * Server Interface etc tec As I understand it from SW, Orion…
-
Any further joy on this? I seem to be having the same problem...
-
Following on from above. The syslog message of "link flap" is not detected for some certain end devices. Switch log only reports up/down status. Advanced alert manager has been configured to show up/down status but does not pick up the flapping. I have also configured syslog alerts to notify me when there is a flapping…
-
I am in the same scenario as above. Has anyone found a solution to reporting on flapping interfaces, correctly?
-
Hi. Yes, I have also looked at the port channel members (i.e. physical gig links). They are also reporting around 1-2% utilisation. Are other suggestions?
-
Yes thats all good if Cisco switch/router is reporting it as 'flapping' in the logs then syslog on SW would pick it up. However, if the logs on the Cisco device is not seeing/reporting it as 'flapping' but only 'up' and 'down' status (10-50 times a minute or >) then syslog does not really work. If I was to use the method…
-
Hi, I have encountered a similar issue monitoring port-channels made up of gig links. The strange thing is, I am getting similar readings to yourself. Real utilisation is between 40% - 75% on these links. Is this a bug in the software? Has anyone else come across this issue?