Skip to content
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

Connection between BFD/BGP alarms and its outgoing interface #267

Open
runborg opened this issue Jun 24, 2024 · 1 comment
Open

Connection between BFD/BGP alarms and its outgoing interface #267

runborg opened this issue Jun 24, 2024 · 1 comment
Labels
enhancement New feature or request post-zino2.0 These are features Zino1 does not have, but might be desired later

Comments

@runborg
Copy link

runborg commented Jun 24, 2024

Today, when a bgp or bfd neighbor goes down there are no connection between this alarm and what physical interface it is connected to.

But as zino collects at least all ip adresses used on each device (and probably also its subnet-mask?) it could be possible to trace back its connected interface for this neighborship. This information could then be available to the client so it could be displayed to the user to make it easier to show the connection between "port down" and "bgp alarms".

This will only work for directly connected neighbours, and not for multihop neighbours, but i think at least in our net we have 99% singlehop neighbors.. so this will work for almost all neighbors but might not for all.

@runborg
Copy link
Author

runborg commented Jun 24, 2024

i think both outgoing ifname and ifalias could at least be fetched to the bgp and bfd cases.

@lunkwill42 lunkwill42 added enhancement New feature or request post-zino2.0 These are features Zino1 does not have, but might be desired later labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request post-zino2.0 These are features Zino1 does not have, but might be desired later
Projects
None yet
Development

No branches or pull requests

2 participants