Limit IP address selection to site/vlan when assigning to interface #19822
Unanswered
hydrobauer
asked this question in
Help Wanted!
Replies: 2 comments
-
It's not quite what you're asking, but as a side suggestion, using VRFs is a fantastic way to split up your IPAM in this scenario. |
Beta Was this translation helpful? Give feedback.
0 replies
-
We already use VRFs, but it's not an appropriate way to separate (internal) tenants because IP address conflicts are only checked within the same VRF. In our case they use the same VRFs and we need the check ;-) Any other suggestions or ideas? |
Beta Was this translation helpful? Give feedback.
0 replies
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.
-
Hello,
we plan to use netbox as IPAM system for our internal customers.
The customers are separated by tenants or other filterable criteria.
Each tenant should be able to manage its own devices and assign preconfigured VLANs and IPs.
IP Prefixes have a tenant, a site scope and a VLAN set, VLANs a tenant and a site.
If a customer creates a new device for a specific site, it should be easy as possible to assign VLAN and IP address to it's interfaces.
Is there a way to limit the suggested interface IPs to IP addresses of the site which is configured on the device?
It would be also nice to limit interface VLAN assignment to VLANs of the specific site.
Example:
Device D is created on site A. Netbox already contains IP Prefixes and VLANs for site A, there is also a Prefix->VLAN mapping.
Customer should only see VLANs and IPs which belong to site A. (Currently he will see all entries for his tenant)
Beta Was this translation helpful? Give feedback.
All reactions