Mapping virtual detached Interfaces #18177
Unanswered
AskskwBv8T2nrm4Qnj
asked this question in
Q&A
Replies: 0 comments
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.
-
This discussion is a follow-up to this "not planned" feature request: #18050
Somewhat related:
https://groups.google.com/g/netbox-discuss/c/b_onSjcdDbE
In Cloud environments like AWS and OpenStack, it is possible for an Interface to be in a detached state. These are virtual Interfaces that are not 'bound' to any Device or Virtual machine, but an IP may be bound to said Interface even while it is in a detached state. I would like to define these detached virtual Interfaces in NetBox, primarily to keep track of WAN IP-addresses: their existence and (lack of) usage. Ideally there would be something such as a Virtual Switch or even a 'Virtual Device', counterpart to physical Devices, to which to bind these virtual Interfaces.
I would appreciate any suggestions as to how to map these Interfaces accurately, without 'abusing' existing NetBox functionality?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions