Virtual Switch Interfaces #198

Closed
opened 2025-12-29 16:19:15 +01:00 by adam · 2 comments
Owner

Originally created by @rdujardin on GitHub (Jul 12, 2016).

It would be interesting to create a VSI object for trunk interfaces. It's useful in the IXP use case.

The VSI would have a foreign key on a vlan, and its own vlan-id (to take into account the mapping between customer vlan id and internal vpls id), and it would have a foreign key on the interface (physical) it belongs to, and a foreign key on a IP (several VSIs on the same physical interface can have different IPs).

Interface should have a new boolean field indicating if it's tagged or not (access mode or trunk mode).

Before implementing this we'd need to take into account how we would handle ethereal channels, because in the case of a new object describing these, VSI should point at such an object and not at a physical interface directly...

Originally created by @rdujardin on GitHub (Jul 12, 2016). It would be interesting to create a VSI object for trunk interfaces. It's useful in the IXP use case. The VSI would have a foreign key on a vlan, and its own vlan-id (to take into account the mapping between customer vlan id and internal vpls id), and it would have a foreign key on the interface (physical) it belongs to, and a foreign key on a IP (several VSIs on the same physical interface can have different IPs). Interface should have a new boolean field indicating if it's tagged or not (access mode or trunk mode). Before implementing this we'd need to take into account how we would handle ethereal channels, because in the case of a new object describing these, VSI should point at such an object and not at a physical interface directly...
adam closed this issue 2025-12-29 16:19:15 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 20, 2016):

I'm not clear on the concept being conveyed, but it seems a bit too complex to take on in the near term.

@jeremystretch commented on GitHub (Jul 20, 2016): I'm not clear on the concept being conveyed, but it seems a bit too complex to take on in the near term.
Author
Owner

@jeremystretch commented on GitHub (Jul 22, 2016):

In an effort to clean up the issues backlog, I'm closing all issues labelled as "discussion." If there is interest in continuing this topic, please start a thread on the NetBox subreddit. Thanks!

@jeremystretch commented on GitHub (Jul 22, 2016): In an effort to clean up the issues backlog, I'm closing all issues labelled as "discussion." If there is interest in continuing this topic, please start a thread on the [NetBox subreddit](https://www.reddit.com/r/netbox). Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#198