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
As you are working on Netbox integration anyway, please provide the feature to request a vlan ID (pool) and IPv4 and IPv6 range (from a pool) and assign them to a tenants (perhaps even to a specific port on a device ... )
It will allow the peering-manager to assist in setting up BGP transit sessions towards customers and make it easier and faster to deploy them. ( especially across various devices with multiple sessions. )
The text was updated successfully, but these errors were encountered:
This is definitively some kind of NetBox interaction that we could have for better automation. We do need to track the interconnections, VLANs and device ports. It would probably be smart to think about this while dealing with #246.
For our use case, we mainly want to allocate the link nets for the connection from a specific pool associated the device/site, and have that pushed back into Netbox as well. I was planning on doing this as a plugin for Netbox that pushed the BGP creation request to Peering-Manager, which what my current standalone provisioning tool does. But we don't use VLAN's for most of our connections, so it would be good to have that be optional.
As you are working on Netbox integration anyway, please provide the feature to request a vlan ID (pool) and IPv4 and IPv6 range (from a pool) and assign them to a tenants (perhaps even to a specific port on a device ... )
It will allow the peering-manager to assist in setting up BGP transit sessions towards customers and make it easier and faster to deploy them. ( especially across various devices with multiple sessions. )
The text was updated successfully, but these errors were encountered: