Replies: 1 comment 1 reply
-
|
We defined all vlans to be not associated with a site or group within a VRF. If a vlan is not locally scoped to a single/pair of routers it gets a binary custom field to indicate it is global based or multi router (SPB, vxlan, etc) . The vlan description holds a special description if it is a L2 only vlan. Our prefixes get a custom field (device objects) which indicates what L3 device(s) are associated with it. That last part is the key to understand the L3 domains. It does the job very well to understand the network. Hope that helps. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've got a VLAN topology and VLAN/Prefix mapping that doesn't seem possible to model accurately in NetBox.
It is misleading to use a global VLAN because the L2 domains for the tags are sometimes unique to one site and sometimes span sites, and the ones that span sites have different prefixes.
The problem is that I've got VLANs which span sites but I can't see any way to model them correctly because site to site_group; vlan_group to scope; and prefix to VLAN are all 1:1 mappings which makes it impossible to create a VLAN group that encompasses sites A and B and another that encompasses sites B and C.
I could, technically stick all the prefixes on one global VLAN but frankly that's gross and misleading.
Is there any way to accurately map this in NetBox?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions