Minor request to have Juniper VCP (Virtual Chassis Port) added as an interface type choice under the "Stacking" section.
As far as I'm aware, Juniper utilizes standard Ethernet interfaces for stacking. The Cisco types are included only because they are physical interface definitions.
Not all the switches use standard types.
For instance, EX4200 series switches use a proprietary Twinax cable.
On Tue, Mar 14, 2017, 14:15 Jeremy Stretch, notifications@github.com
wrote:
As far as I'm aware, Juniper utilizes standard Ethernet interfaces for
stacking. The Cisco types are included only because they are physical
interface definitions.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/960#issuecomment-286512463,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfg5sXWEQzzBHHQke5AugUXaYTnbXRQks5rltk6gaJpZM4MbuVE
.
Is it worth considering this being changed to be a table? That way the code wouldn't require updates every time a new speed of Gigabit Ethernet is announced!
See #167 for the reasoning, why this is hard coded and not configurable.
To add to what @jsenecal said, Juniper does have proprietary _physical_ interfaces for many models like Cisco but they do also allow the use of regular interfaces for stacking as well, like @jeremystretch said. It should be noted that when this is the case, the interface in converted so that it no longer looks or acts like a standard interface to the system (it is renamed and renumbered). So they look and act like traditional (proprietary) stacking interfaces.
But in short, yes Juniper does have proprietary VCP interfaces.
I'm fine with adding any of the physical types if we can determine the canonical names.
They are simply called Virtual Chassis Ports or more commonly referred to as VCP's.