[racktables-users] Re: Multiple connections on a port for patchpanels
- From: Aubin Galinotti <noxin.racktables@xxxxxxxxxx>
- To: racktables-users@xxxxxxxxxxxxx
- Date: Tue, 24 Feb 2009 02:13:42 +0100
Hello Denis,
Yes you got right me right, thanks.
Do you think it would be possible in a future version to have a front
and a back connection on a port ?
In a patch panel, it could be used to explicitely follow the physical
connection chain.
In a router/host/switch, it could be used to map the physical port with
the OS interface.
Denis Yeldandi a écrit :
Hello Aubin,
Not sure that I understood you correctly, but... If you mean that you
want to document in racktables the fact that a patchpanel has 2 types
of ports: front ports -- RJ45 (8P8C is more correct word) and back
ports -- 110 block punchblock
(http://en.wikipedia.org/wiki/110_block), then no, there is no special
way to do that.
Instead of that you can:
create a new port type called "110 block"
48 ports for a 24-port panel: 24 RJ45 and 24 110 block, called front1
... front24 and back1 ... back24
connect back ports of the 2 patchpanels you have (as far as I
understood, you have 2 patchpanels, right)
connect corresponding front ports to your devices (again, as far as I
understood your topology)
There would be no explicit connection between front and back ports of
a panel, you just have to assume that port frontN corresponds to port
backN.
If I didn't get you right, can you please explain it more? :)
Thanks!
Denis.
Aubin Galinotti wrote:
Hello,
I'am new to racktables, discovered it last week.
So far it looks great.
I have just a question, is there a way to have 2 connections on a
port in the case of a patch panel ?
For instance I have :
- a router in a rack
- a cable from this router to a plug in a patchpanel in a meet-me room
- a cable from this plug another plug of the patch panel
- a cable from the second plug to another router in another rack
I don't see how to do this in racktable, unless I create two ports
for each port in the patch panel (but then I can't "follow" the
cables from the interface)
(I looked on the bugtracker but didn't find a request on this, sorry
if it's allready asked for and I didn't see it)
--
Regards
Aubin Galinotti
Other related posts: