You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: