Features, bugs, etc for the OpenNetAdmin web interface
Tasklist

FS#32 - Patch Panel Documentation (TIA/EIA 606A)

Attached to Project: OpenNetAdmin Web Interface
Opened by Ben Story (bstory) - Friday, 14 November 2008, 14:56 GMT-6
Last edited by Matt Pascoe (matt) - Wednesday, 19 November 2008, 22:16 GMT-6
Task Type Feature Request
Category Backend / Core
Status Assigned
Assigned To Matt Pascoe (matt)
Operating System All
Severity Low
Priority Low
Reported Version 08.08.16
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

In larger environments especially, it is useful to keep track of the patch panel field in terms of what server/device is plugged into what port on what panel in relation to the TIA/EIA 606-A structured cabling standard. I think that this kind of documentation fits in well with the overall framework that ONA is creating.

To take the current IP address hierarchy as a model I would suggest that patch panels be subcontainers of a rack container and then a port exists within a patch panel. Then there would be linkage between an interface on a server/device and the port.

Unfortunately I don't have the PHP skills to code the GUI portion, but with help on that I could probably contribute to the underlying functions and procedures.
This task depends upon

Comment by Matt Pascoe (matt) - Wednesday, 19 November 2008, 22:15 GMT-6
I would agree that having a method of tracking the port, whether it is a patch panel or switch port or both that a device is plugged into would be great. I have had various thoughts and ideas around this whole issue. I expect whatever it is to be a "plugin" to the ONA framework as not everyone would use it.

I believe there are several ways this could be handled. Choosing one that fits the majority would be the next step.

For now however it would be low on my priority list.

Loading...