1

I’m currently notating the tangled mess that is our patch panel/switches/phone panel rack. Here’s an illustration…

Patch Panels:

WIN_20180312_16_31_05_Pro.jpg
WIN_20180312_16_31_05_Pro.jpg800×1200 326 KB

Switches/Phone Panel:

WIN_20180312_16_31_16_Pro.jpg
WIN_20180312_16_31_16_Pro.jpg800×1201 315 KB

Two of the switches are TP-Link TL-SG1048’s, and there’s a Cisco SG200-50P that’s not yet configured, but will be shortly. There’s a patch panel for phones below all of that.

I’ve (stupidly?) given myself the task of mapping and then tidying up this mess (going to get shorter, color coded cables, & try to make a consistant naming scheme for ports and such. I hope so, anyway…)

Now, I’m not the guy who installed and patched all of this, so I’m not totally familiar with the specs on the switches, but I was wondering if, with a mix of dynamic and static IPs, do I really need to patch back to the exact same port on a switch from a patch panel port (I know I need to do so for the phone patch panel)? Or is there a way to ‘freeze’ the list of IP addresses to each device, so that I can make nice tidy cable runs?

And in terms of organizing all of this, I know I’m going to split cable colors into four groups: Internal Network, Guest Network (mostly for wifi access points), Phone & router to switches. Any other advice?

10 Spice ups
2

It depends…if you have VLANs, you’ll either need to go back to the same spot or adjust the VLAN on the port you plug into. I would recommend the latter, it makes for routing cables easier and makes things look nicer.

if you don’t have VLANs, it’s a free-for-all and you can do what you want

3 Spice ups
3

Instead of colors for Network connection, we use colors for data types (black for video, yellow for voice, blue for data, etc.). Just another way of maybe doing it. Are the switches managed or smart switches or are they basic with no VLAN’s or advanced configuration? If not, you might just grab a large switch to temporarily keep things running while tidying up. If the switch isn’t managed, final termination should not matter a bit (and organization may be better having things punched/patches to a more uniform configuration anyways. Phone and video, for sure will need to go back where they came from unless those endpoints get power from their own power supplies. If the have their own PS’s, your good across the board.

1 Spice up
4

The TP-Link TL-SG1048’s are a unmanged switch - (check that’s the model) so they wont care what port is used.

Otherwise all good

1 Spice up
5

The safest assumption is that all switch ports are not the same. They might be, but until you know that, you don’t want to take that chance.

If you’re going to be unplugging cables, take a little time to get to know the switches you’re working with and read up on them.

At the point when you feel comfortable moving cables, move one at a time and then verify it works before going to the next one.

There’s nothing funnier than watching someone who’s removed all the cables and put them back so nothing works. I’d laugh for days. :wink:

5 Spice ups
6

In respect to @justin5198-spiceworks 's comment, something that just occurred to me is that you might want to label and definitely want to document what’s where before you make any changes. :slight_smile:

@rhummel

1 Spice up
7

I know it’s probably too late at this point, but I’ve become a fan of avoiding cable organizers between patch panels.
I now do a 24 port patch on top, a 48 port switch, 48 port patch and so on, ending with a 24 patch. Connect the upper 24 ports of the panels to the bottom 24 of the switch immediately above and the other way around for the bottom 24 (to the upper ports on the switch below). This allows me to use very short patch cords and keeps everything very compact and clean looking. Saves a ton of rack space too.
I do use vertical organizers to connect the switches.

3 Spice ups
8

Also watch out for speed and duplex settings. Sometimes you have a device that requires a port to be forced to something like 100/full. If you plug something else in there you are going to have issues. It’s also possible that ports have been set a different spanning tree priorities for links. I have never seen this down in a small business.

Ports could be in link aggregation. If that’s the case, then those need to go back the way they were or you will introduce a loop if there are redundant links grouped.

9

I now do exactly as tulioarends says. Put patch panel, then switch and use really short cables. So much easier to follow in the future and keeps it looking clean.

Also when mapping out where things are currently, just video it on your phone. Follow the cables whilst talking to the camera.

Then watch it back, it’s far easier

10

Consider changing those switches for something managed, if only to segregate traffic (data, VoIP, guest WiFi, etc).

@Ubiquiti_Inc makes some decent switches at a very attractive price point. We use Unifi POE switches and have no complaints.

11

I hadn’t actually checked OPs model numbers, but those do appear to be unmanaged switches in which case it doesn’t matter what plugs where. There are no custom port settings.

Good catch.

12

First, pull out all cables that are ONLY connected with 1 end.

Second, review most of your runs - follow cables - are they short distances to cover with a long cable? If so, go BUY 1 foot patch cables and start replacing the long ones to short ones into the same ports. Want an example, look at my profile’s Project - https://community.spiceworks.com/people/overdrive/projects/new-cat6-cabling

https://community.spiceworks.com/people/overdrive/projects/new-cat6-cabling

1 Spice up
13

Loving all of the advice you guys have been giving me - very much appreciated! Here’s a detail that I forgot to mention… I’ve been mapping out each cable in an excel spreadsheet (which patch port to which switch or phone port), so I’ll have a list and can just match up if needed.

I would LOVE to move my patch panels, tulioarends, but the punchdowns are an unholy mess in there, and almost none of the cables have any slack for moving them. Maybe when the building gets gutted and remodeled…

The Cisco switch is a smart switch, but isn’t in use yet, so that shouldn’t be an issue. There are a few VLANs, guessing that as long as I know where those switch ports are, I can make that work.

@tulioarends

14

If your switches are unmanaged then there are no VLANs set on them.

15

Yeah, thought there was one, but it turns out that my boss was just testing one (on the smart switch that’s not totally configured yet), and it’s not running anymore.

16

Check to see if the installers left service loops. This is a best practice when running cables, though a lot of contractors don’t do it. I insist on service loops close to both ends of my runs unless most of the run is in conduit, in which case I make do with only one.

Most of the time these are hidden in the plenum space, anchored to the ceiling.

17

Also, on your first rack there is plenty of space for 1U switches, just get rid of the cable organizers. You’ll have to connect all ports on the patch panels to the same switch, which is not as neat looking but works perfectly fine. Use 3"-6" patch cords.

1 Spice up
18

Oooo yeah! Might actually be able to pull that off - had a chat with my boss, and he’s saying that as part of this whole process that we’ll replace the TP-Link’s with new Cisco SG200-50Ps (like the one we have). I’ll see if he would get two 1U switches and a 48 port one instead of two 48 porters.

19

Flamethrower from Amazon

Rebuild as necessary depending on who yells the loudest.

20

In my dreams…

We are in the middle of transitioning from paper charts at our clinic to EMR, and for years I’ve wanted to do the same to the paper charts to force the issue.

Alas, I told people about my dream, so I’m pretty sure I’d be charged with arson if it actually had happened…