Forum Discussion
On 8/31/2020 at 10:42 AM, mnagel said:We have an eventsource for this, originally provided by LM support and tuned a bit since then. It requires SSH access to devices since Cisco lacks a MIB for detecting errdisabled ports (at least in the general case). This in turn means you must be very careful about deploying the eventsource since defining ssh.user/ssh.pass would otherwise bring other things into scope you may not want, like LMConfig (we added an alternate name format to control for that). Lastly, since it is an eventsource you cannot practically acknowledge issues. If you used syslog integration with LM (we do not as it is too limited), you could perhaps feed device logs to the collector and detect them that way without SSH. Another option would be use the same logic as the eventsource and create a datasource, generating datapoint values based on the errdisable cause picked up from the command.
I just published what we have now as H4T9GH. Since it is in Groovy, it will need to be reviewed.
Thank you for the info. I don't believe I would be comfortable adding the SSH info to our system, just too big of a security issue and the err-disabled status problems we see are few and far between.
We do have a syslog upgrade in place, so i'll investigate that option going forward. Appreciate the response.
Josh B.
Related Content
- 4 months ago
- 2 years agoAnonymous
- 6 months ago