[racktables-users] Re: Cable sharing (port doubler)

  • From: Jörg Schneider <software@xxxxxxxxxxx>
  • To: racktables-users@xxxxxxxxxxxxx
  • Date: Thu, 28 Mar 2013 16:14:01 +0100

Thank you Steve,

I thought about this too, but I dislike the idea of having hundreds of useless 
objects in out RackTables database...
Wether it would be  a clean solution, nobody wants to link multiple ports... ;-)

Joerg

Am 28.03.2013 um 15:57 schrieb theodore e van iderstine 
<tvaniderstine@xxxxxxxx>:

> You could build a 'splitter' object that has three ports: 1 out and 2 in, and 
> attach it to the panel port and then connect the devices (phone, pc, etc) to 
> the splitter object.
> 
> I did this very thing in Informix 20 years ago... so how i managed 
> it....we'll, i don't remember how I validated the connections.
> 
> On Thursday, March 28, 2013 02:23:06 PM Steven Brown wrote:
>> I suggest a naming convention with patch panels which include double the
>> number of actual ports.
>> 
>> Port / Pair
>> 
>> Port 1/1
>> Port 1/2
>> Port 2/1
>> Port 2/2
>> etc
>> 
>> 
>> Steven Brown
>> Midrange Server Team
>> IT&S
>> 
>> 2025 Victoria Avenue
>> Regina, SK  S4P 0S1
>> Phone: (306) 566-2579
>> Email: sbrown@xxxxxxxxxxxxx
>> 
>> ________________________________________
>> From: racktables-users-bounce@xxxxxxxxxxxxx
>> [racktables-users-bounce@xxxxxxxxxxxxx] on behalf of Jörg Schneider
>> [software@xxxxxxxxxxx] Sent: March 28, 2013 07:10
>> To: racktables-users@xxxxxxxxxxxxx
>> Subject: [racktables-users] Cable sharing (port doubler)
>> 
>> Has anyone suggestions how to picture panels with cable sharing?
>> We have a lot of POTS in our datacenter which are shared in order to save
>> resources... (only one pair of four used if not shared)
>> 
>> Best regards
>> 
>> Joerg Schneider
>> This email including attachments is confidential and proprietary. If you are
>> not the intended recipient, any redistribution or copying of this message
>> is prohibited. If you have received this email in error, please notify us
>> by return email, and delete this email.
> 
> 


Other related posts: