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
The VLANGroup model isn't currently useful to us because you can't have a VLAN be a member of more than one group. We'd like to use VLANGroups to logically group VLANs for sets of equipment (currently we use a custom field in each VirtualChassis to specifiy the list of VLANs that are carried on the stack and the list is use to validate what can be set on Interfaces in the stack and used to generate configuration of the stack). Our VLANs span our entire network (we don't have a situation where VID 999 in area A is a different VLAN than VID 999 in area B). Having more than one VLAN with the same VID in NetBox is a can of worms - you then need to have to duplicate Prefixes if you want 1.2.3.4/24 to be carried on all the incarnations of VLAN VID 999 (a Prefix can only be included on one VLAN), so the problem just cascades from there. Is there something I'm missing about how VLANGroups are intended to work?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The VLANGroup model isn't currently useful to us because you can't have a VLAN be a member of more than one group. We'd like to use VLANGroups to logically group VLANs for sets of equipment (currently we use a custom field in each VirtualChassis to specifiy the list of VLANs that are carried on the stack and the list is use to validate what can be set on Interfaces in the stack and used to generate configuration of the stack). Our VLANs span our entire network (we don't have a situation where VID 999 in area A is a different VLAN than VID 999 in area B). Having more than one VLAN with the same VID in NetBox is a can of worms - you then need to have to duplicate Prefixes if you want 1.2.3.4/24 to be carried on all the incarnations of VLAN VID 999 (a Prefix can only be included on one VLAN), so the problem just cascades from there. Is there something I'm missing about how VLANGroups are intended to work?
Beta Was this translation helpful? Give feedback.
All reactions