Unable to assign VLAN to prefix, if the prefix is assigned to a site

[jmmey]

Problem description

If a prefix has a site assignment, it is unable to be assigned a VLAN. The only work around I found is to remove the site assignment from the prefix. At that point the UI will allow me to assign a VLAN to the prefix.

Has anyone else experience this issue in version 2.11.10? This is happening on two different installations of netbox. I'm not sure if it is something I do not understand from the docs or a bug.

Steps to Recreate

1. Create a VLAN with an ID, Name, and Status set to "Active".
2. Create a site.
3. Create an IPv4 prefix, and assign it to the site created in step 2, save.
4. Edit the IPv4 prefix from step 3, under section Site/VLAN Assignment, select the drop down for VLAN. The drop down states "No results found".

5. Still in the IPv4 prefix edit screen under section Site/VLAN Assignment, remove the site by either selecting "None" or click the x.
6. Click on the drop down for VLAN, and now the list is populated with a list of VLANs available for assignment.

[candlerb]

Have you tried:

• assigning the VLAN to a site?
• assigning the VLAN to a VLANGroup, and assigning the VLANGroup to a site?

[jmmey]

Here are the results from those two suggestions.

Assigning the VLAN to a site

• VLAN assigned to the same site as the prefix works, but the VLAN can no longer be assigned to a VLAN group.

URL for image: https://netbox-url/ipam/vlans/1/edit/

Assigning the VLAN to a VLANGroup, and assigning the VLANGroup to a site

• This works if the site is removed from the prefix.

URL for image: https://netbox-url/ipam/prefixes/4/edit/

• If prefix is assigned back to a site, VLAN's are not listed even though prefix is assigned to the VLAN group.

URL for image: https://netbox-url/ipam/prefixes/4/edit/

My intent

Below is a diagram mapping my intent. It is possible my ignorance of Netbox at this point is the problem. My goal is to have [VLAN-Group]<-->[VLAN-ID]<-->[Prefix]<-->[Site] relationship.

[sdktr]

In this example, is your L2 domain stretched between te two sites or site unique?

If the latter: netbox intent is to explicitly model the unique L2 broadcast domain (VLAN) and not tbr blueprint of it that replicates over sites. So you'd have to create two (site specific) VLANgroups with a copy of the vlans in each of them.

I like your way of thinking though, where the network model is administrated once and applied to multiple implementations, in this case by using the prefix as glue.

[jmmey]

The L2 domain is not stretched between sites. These locations are separated by an SD-WAN overlay with multiple types of transport (MPLS, Internet, LTE). They are small retail branch offices with an identical L1/L2 architecture.

The VLAN ID's used at the sites are always the same (10, 20, 30), but represent a different L3 subnet that fall under an assigned site IPv4 aggregate. Since these locations always share identical VLAN ID's, I attempted to leverage a common VLAN group. If in the future we need to provision say VLAN 40 at all sites, my hope was to add it to the single VLAN group.

My thought was less data entry and less prone to human error. I will use a VLAN group per site with a copy of the VLAN in each as you suggest.

I really appreciate the help!