. When duplex patches come around, we just delete the second interface and rename the port x/y. Not an elegant solution, but it works. This certainly falls under the 'Quality of

approach for duplex links is to connect the interface to just the odd-numbered port on the fibre infrastructure, and implicitly the even-numbered port is used as well. You could use

with 8 duplex LC ports. > I've modelled this having the "line" port being the rear port with 8 > positions and then having 8 front ports, each with a wavelength.

(6 duplex connections). For simplex connections I'm > occupying a duplex connection because for now I'm not looking to double the > work (creating 2 cables per duplex

like a duplex LC-SC (or similar), I'll just use a single port on the patch panel named with both position numbers - ie, a port named 1-2 for a cable taking position 1 and position 2 on

speed, Duplex, > Autoneg, FEC, and so on. > > My initial thought was this would be easy to solve with a custom field, > however it does not exist. Then I noticed a strong resistance

Hi, > I've just hit this very issue now with installing our new Core Network. > > So far we are modeling the interfaces as they are on the

a Rear port is connected to many front ports? > > A patch panel which has 6 duplex LC connectors on the front, and a 12-fibre MPO port at the rear to connect to another patch panel.

speaking of duplex connections). If the rear port isn't connected my view wont work properly, and it will display only the front trace (trace starting from front port) Il giorno

fibres are duplex then you can just consider a fibre pair as a single connection. > - API for interoperability with existing tools in-house > > Netbox exposes a fairly traditional

as six duplex LC connectors. > > In the limit: you can make a device type for a patch panel that has a > single rear port (called eg "backplane") linked to 24 front ports

speed/duplex/autoneg for the link This sort of attribute is only applicable to a subset of interface types; it wouldn't make sense to add as a field on the Interface model. And typically

On Wednesday, 6 February 2019 15:16:59 UTC, Brian Candler wrote: > > > 2. interfaces also represent logical interfaces: for example, an IP

is attaching duplex vs simplex cables to network device interfaces, simplex seems OK because there is a 1:1 mapping between interface and LC patch panel port. Duplex however seems

panel as duplex all the way: that is, have ports called "1-2", "3-4", "5-6" etc, where each represents a pair of LSH ports. But this won't work

removed SC duplex/simplex designations >> - #2570 - Add >> bulk disconnect view for front/rear pass-through ports >> - #2571 - >> Enforce deletion of attached

a start, but there seems to be no way to create a relationship between a network interface eg ge-0/0/0 on a Juniper switch and say it's installed FiberStore 1310 SM Duplex optic.