-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make a link state monitor task #37
Comments
Noting that the original Zino code collects both I.e. we shouldn't need to care about |
Exploratory coding for this issue reveals that more changes are needed to the base SNMP adapter in Also, none of the current walk implementations support more than one walk variable, while the underlying protocol supports asking for more than one variable per request (whether it be GET-NEXT or GET-BULK). The link state monitor needs to get a bunch of attributes (i.e. columns) per interface, and the best way to do this SNMP-wise is to do what Zino 1 calls a sparse walk. To avoid implementing a sparse walk as a bunch of daisy-chained walks of individual columns, a new getbulk-implementation is needed in |
I've removed the flapping task from this issue, as the flapping detection algorithm is only relevant to SNMP trap processing, which isn't implemented yet. This issue can therefore be closed, as the active link state monitor is more or less complete. |
The link state monitor basically:
Implementation breakdown
ifLastChange
to calculate link state change times #77The text was updated successfully, but these errors were encountered: