Front port status when rear port has a connection

[Fabian L]

This week I've started using Netbox to document Crossconnects/Patches/Cables. Hopefully I'm using this great tool as intended.

We usually have a a fiber patchpanel per rack which is wired for a multiple of 12 fibers (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 connection).

The patchpanel gets 6 front ports (SC) and I'm using one MTP port as rear port with 6 positions, mapping each front port to a position. The far end of the MTP cable goes to a patchrack with multiple patchpanels. The patchpanel configuration on this end is the same:

Rack A                                            Rack Z

F 1  ---\                                            /---F 1

 .     ----\                                          /---- .

 .     -----\____________________/----- .

 .     -----/rear 1:1               rear 1:1\----- .

 .     ----/     .                              .     \---- .

F 6  ---/      .                              .      \---F 6

              rear 1:6               rear 1:6

(Thanks Todd for the great Ascii art ;))

When an interface from a router or switch is connected to Rack Z  F2,  a trace perfectly shows the connection ending up on Rack A F2.  So far everything is as expected.

Now when looking at the 'Rack A' device, F2 is 'not connected' as there simply hasn't been any connection made in Rack A. However, it would be nice to somehow see when looking at the patchpanel in Rack A that a connection has been made on the far end of the port.

Port F2 is occupied while there is a 1:1 mapping between F2 on the Near end and on the Far end.

Is this as designed/intended or could I make a suggestion (feature request) to add the trace icon/link on a 'Not connected'  front port when the rear is in use on the far end ?

Best regards,

Fabian

[Bert Heylen]

Hi Fabian,

Sorry to bring up a rather old topic, but I have the exact same question.  And in all my searches, your post is the only thing that I can really find :-).

Did you manage to get a propr answer / solution to this?

Thanks!

Op zaterdag 18 mei 2019 20:46:10 UTC+2 schreef Fabian L:

[Brian Candler]

It's as-designed.  "Connected" refers to a complete active end-to-end path: that is, an interface-to-interface connection.  Front ports / rear ports are passive.