This is exactly what we did.  We put 3 24 port panels.  One panel to
primary core, one panel to secondary core, and one panel to IP KVM.  Works
well for us.

On Wed, Jun 20, 2012 at 11:59 AM, Brian Desmond <br...@briandesmond.com>wrote:

>  *The labeling I agree is far more important. Get a good label printer
> that’s designed for cable labeling.*
>
> * *
>
> *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. *
>
> * *
>
> *Thanks,*
>
> *Brian Desmond*
>
> *br...@briandesmond.com*
>
> * *
>
> *w – 312.625.1438 | c   – 312.731.3132*
>
> * *
>
> *From:* Steven Peck [mailto:sep...@gmail.com]
> *Sent:* Wednesday, June 20, 2012 10:50 AM
>
> *To:* NT System Admin Issues
> *Subject:* Re: Re-cabling****
>
> ** **
>
> As we have a redundant switched network our network team uses color coding
> religiously.  ****
>
>  ****
>
> Off the top of my head it's something like:****
>
> Blue for primary network, green for the secondary (for the teamed
> networks)  ****
>
> Orange for backup****
>
> Red for rILO****
>
>  ****
>
> They also label all connections, both ends.  They are not so concerned
> with what the system name is, as switch/port it is connected to.  ****
>
>  ****
>
> Steven Peck****
>
> http://www.blkmtn.org****
>
>
>
>  ****
>
> On Wed, Jun 20, 2012 at 7:20 AM, Ben Scott <mailvor...@gmail.com> wrote:**
> **
>
>  On Wed, Jun 20, 2012 at 9:27 AM, Tom Miller <tmil...@hnncsb.org> wrote:
> > What are your preferences?   Cable color by rack, system, type, etc?
> It's
> > just aesthetics but I'm looking for ideas.****
>
>  If you want it to look pretty, use the same color for each
> rack/switch.  Otherwise that's more confusing than helpful.
>
>  Categorizing by VLAN or type of traffic makes some sense.  E.g.,
> yellow is DMZ, blue is main LAN, green is SAN, etc.
>
>  Using a rainbow spread to each rack makes some sense.  Makes it
> easier to tell cables apart when you're hunting for or tracing a
> particular cable.
>
>  There are some standards for cable sheath color coding, but the ones
> I'm aware of are all facility-wide in scope.  Most of your
> in-datacenter cabling would be the same color under such schemes.  So
> I wouldn't call those helpful for this.
>
> -- 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 listmana...@lyris.sunbeltsoftware.com
> 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 listmana...@lyris.sunbeltsoftware.com
> 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 listmana...@lyris.sunbeltsoftware.com
> 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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Reply via email to