This MR enhances fernglas to support routing-instances for BGP and BMP Sessions. Following three methods to gather routing-instance information have been implemented:
BMP: evaluate RD in the MessagePeerHeader - no configuration necessary
MP-BGP: routing-instances are signaled over VPNv4/VPNv6 address families - no configuration necessary
BGP: Session itself belongs to a routing instance - BGP Session has to be assigned to a routing-instance in configuration
There has been a breaking change in the API to expose the routing-instance information. The frontend has been updated accordingly.
Possible outstanding improvement: Make Routing-Instance names configurable. Currently the Route-Distinguisher associated with the routing-instance is used as the name.
Hi, sorry for the long delay. I can not properly test this at the moment (or for a while), but we'll just take it as-is and then fix any breakages as they appear.
This MR enhances fernglas to support routing-instances for BGP and BMP Sessions. Following three methods to gather routing-instance information have been implemented:
There has been a breaking change in the API to expose the routing-instance information. The frontend has been updated accordingly.
Possible outstanding improvement: Make Routing-Instance names configurable. Currently the Route-Distinguisher associated with the routing-instance is used as the name.