We had switches with those instead of RJ-4s as well.. and had fan-out
cables.

Without the intermediary patch panel, they are a pain. They might work
OK for the patch trunk though.

-sc

> -----Original Message-----
> From: Ben Scott [mailto:[email protected]]
> Sent: Wednesday, June 20, 2012 1:23 PM
> To: NT System Admin Issues
> Subject: Re: Re-cabling
> 
> On Wed, Jun 20, 2012 at 11:59 AM, Brian Desmond
> <[email protected]> wrote:
> > Rather than pulling cable all the way down in to the racks, you
might
> > want to think about putting a 24 or 48 port panel in the top (back)
of
> > each rack and then running short patch cables from there. Then on
the
> > other end you can cross connect to the switch or whatever.
> 
>   Back in the days of =< 100 meg, you could buy CAT5 cables and patch
> panels with 50-pin "telco" connectors.  So you could then connect 12
ports on a
> patch panel using a single cable.  This saved labor, cable space, and
made
> things neater, as you only had to run one or two trunk cables to each
rack.
> 
>   I don't know if that's still feasible for >= gig.  It uses all four
pairs, so you'd
> only get 6 ports per connector.  The cross-talk requirements are also
much
> stricter, so it may flat-out violate spec.
> 
>   But even if one can't do the single connector method, you can buy
cable
> assembles which bundle a bunch of 4-pair RJ-45 lines into a
> single outer sheath.   That still might make cable management better.
> 
> -- Ben
> 
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
> 
> ---
> To manage subscriptions click here: http://lyris.sunbelt-
> software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to