-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable assignment of VLAN during Prefix import #42
Comments
This was intentional. Since a site can have multiple VLANs with the same VID and name, there's no way to specify a unique VLAN in CSV. I suppose we could implement it anyway, and simply return an error if duplicate VLANs are found. |
IMHO, you should not be allowing multiple VLANs that have the exact same identifying information (VLAN name, VLAN ID, site) without adding some other piece of identifying information to the table. Maybe we utilize a 'Default' VLAN database that's used automatically within each site, with the ability to instantiate additional VLAN (or VXLAN) domains in a location if necessary? This would allow network admins to create "PODs" within each site that each contain their own unique set of L2 networks. |
The Prefix Import functionality does not currently accept the VLAN field
The text was updated successfully, but these errors were encountered: