Written in react, it's moderately heavy and not entirely mobile optimised.
Written in react, it's moderately heavy and not entirely mobile optimised.
Like you can't model 1 cat5 split into two 100mb terminations, patch panels are kinda of hack, I think you can now but forever you couldn't just swap a termination direction because logically why would you (but their UI gets messy when 44 are done A-B and the 45th B-A)
Anyway that's thoughts as of maybe v2 or 3? Before the new UI when it was all jquery.
Ugh I don't really blame them there, that's really a dirty hack. Sure I've done in a pinch but not for permanent stuff.
I wouldn't call that professional network management. If you really wanna do it, just split the pairs over two patch ports IMO.
I certainly wouldn't do it today, but using two pair for a connection designed for two pair isn't a dirty hack, it's as designed.
Today, using 4 pair for 1G or more and a small switch on the host side to get more ports is probably a better plan.
It was a bit of my OCD being triggered as well. I love neat cabling at work (at home it is chaos funnily enough).
Here is one Discussion/issue that is currently annoying me again.
https://github.com/netbox-community/netbox/discussions/9515 https://github.com/netbox-community/netbox/issues/20005
Netbox is full of these kinds of things. Where people ask for stuff or even create PRs for it and the Maintainer of Netbox shoots it down because reason.
It's cable management and routing to keep things from kinking and breaking while accounting for cable flexing, thermal expansion, and unforseen circumstances like another company lashing their cables to yours for vertical support.
All while maintaining future serviceability
What kind of org shares cabs? Monster!
Your cab's environment should be pretty thermally stable. Your switches are probably venting to the hot isle through their front ports. Thermal expansion of glass and the sleeve is going to be negligible over a metre or so.
Kinking is a possible issue. The minimum radius these days is quite tight. However, if you don't leave enough space inside the doors to allow for the terminations it will go horribly wrong. If you don't allow a gap for cable management between all switches and top and bottom, it might go wrong.
Sorry! In practice manual usage is normally very rare, these are typically auto generated!
There are a lot of connections which look like they should work, but don't - such as patch panel to patch panel. On the other hand, it is possible to connect a single LC connector to two splices at once. There doesn't seem to be any way to unmake a connection. Overriding existing connections sometimes works, but sometimes doesn't. The tube nodes don't have a clear drag-and-drop point towards a cable. By default the tube nodes have a colored edge matching the incoming tube connection, but this edge color doesn't change when you drag a different tube from the cable onto it. The cursor sometimes wrongly shows a "+" to indicate a possible connection, such as trying to drag from one tube exit to another. It is somehow possible to connect two cable tube exits to a single tube node. It is somehow possible to connect a cable tube exit directly to a splice node.
Those probably don't matter all that much if it is almost always auto-generated, but considering the amount of weird behavior it might perhaps be better to disable the edit functionality for now?
My research shifted, and I start making sensors using fibre and similarly sized capillary tube. It all got cleaved, spliced to assemble, cleaved some more, spliced again, then polished to spec. Getting the he process down was a pain, but the results were super satisfying.
zwnow•1mo ago
matt-p•1mo ago
Thank you :)