Netbox cable splitting functionality requires input and output to match #12372
-
I've spent several hours trying to figure out how to model a typical next gen PON network using all the new cable features that came out. I've played with positions, multi-interface cables, etc. I can't seem to get it. I am stuck on how to show a cable trace where an interface splits into two of the paths. Below is the closest I have gotten. I need the one front port to map to two rear ports. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
It seems netbox will only do the multi output if the multi-input exists. |
Beta Was this translation helpful? Give feedback.
-
There are quite a few limitations with fibre modelling in Netbox, and being unable to model PON splitters is one of them. The multi-position stuff (i.e. 1 rear port with N positions <-> N front ports) is for modelling a multi-strand trunk cable, like an MPO, used to join two patch panels together - not for PON splitting. A single "N-strand" (implied) rear cable breaks out into N front ports. Netbox is able to trace such a cable from the Nth front port on one patch panel, through the trunk cable, to the Nth front port on the other patch panel - the rear port "position" is implicitly the strand offset within the trunk cable. The cable is still just a single cable, and doesn't actually contain explicitly modelled "strands". Netbox also doesn't model SFPs, and it doesn't model separate transmit/receive fibre strands. So every "interface" can only accept a single "cable". However, you can have a cable which connects to an interface at one end, and two ODF ports at the other end. It's still considered a single "connection". Similarly, if you have a QFP port at one end of a cable, and four distinct SFP+ ports at the other end, you can't treat these as separate connection paths (even if the QFP port is configurable as 4 separate interfaces). I'm afraid this info doesn't help you. The best you can do for now, I believe, is to model all the passive ports as "interfaces" - as if they were switches - but you won't be able to trace cables through them, you'll have to trace in hops. |
Beta Was this translation helpful? Give feedback.
There are quite a few limitations with fibre modelling in Netbox, and being unable to model PON splitters is one of them.
The multi-position stuff (i.e. 1 rear port with N positions <-> N front ports) is for modelling a multi-strand trunk cable, like an MPO, used to join two patch panels together - not for PON splitting. A single "N-strand" (implied) rear cable breaks out into N front ports. Netbox is able to trace such a cable from the Nth front port on one patch panel, through the trunk cable, to the Nth front port on the other patch panel - the rear port "position" is implicitly the strand offset within the trunk cable. The cable is still just a single cable, and doesn't actually conta…