Before & After: A Tale of Data Cabling
Saturday, I tackled a beast.
It wasn’t anything of insane epic porportions, and in reality it only took a couple hours but I felt like sharing.
The picture on the far left is of a clients data rack (after I removed the non-functional and abandonded equipment). Long story short, this is what happens when you don’t have a clear plan, or a single person to make decisions.
There were more problems than the obvious mess:
- Troubleshooting connectivity problems with this tangled mess can make a grown man cry.
- With so much extra cable in such a tangled mess, your chances of Alien Crosstalk goes up, which ultimately means poor network performance.
- The weight of the unsupported cable puts kinks in the cables at the plugs, as well as can damage the connections resulting in poor conductivity (again, ultimately poor network performance).
- Its not apparent (and took me nearly an hour to fully navigate) but the switches on this rack (and there are 5 in use) are daisy chained together, which means that the network had severe bottlenecks, as well, if a device in the middle of the chain were to fail, everything below it would stop working.
The simple solution, get the right sized patch cables for the job. In my case, I was able to layout the equipment in such a way that I could do just about everything with 1′ patch cables. I also re-structured the topography into a star with the switch at the very top of the rack acting as the center of my star. It does unfortunatly mean I still have a single point of failure that could take down the network, but if any one of the other switches fail only devices connected directly to that switch will go down, so I see it as an improvement. Rebuilding the topography also means I don’t have the same bottlenecking problem I had before. Internal traffic now has a maximum of three hops, as opposed to the potentially 6 hops in the prior design.
I’ve asked the client to keep an eye on things, see if the improvements are actually noticable or not. They han’t had any serious problems before so I won’t be supprised if the changes are not readily noticable to the end users. If they do though, it’ll be in the voice quality of their VoIP phone system. At the moment on busy days they get a noticable degredation of the voice quality, and without QoS capable switches there isn’t anything I can do besides hope the drop in packet loss due to the rebuild is enough to subdue the problem until I can get new switches.






I had a great week, and the weekend looks to be just as good. I had Monday off for the holiday, see the post below about that though. Tuesday was back to the daily grind at work, but in the afternoon I got invited to go golfing, to take a couple of our clients out to improve our relationship with them. Why me? Because the clients were IT personel so since Bill and I are the “IT and Infrastrucutre” design team at EDC we were the ones who went. But the best part is WHERE I got to go golfing. We went to
Then Thursday I took the day off and went down to six flags with Matt Lockyer, Chadd, Keith and Meghann. We got a bit of a late start and then took a long time getting into the park. I had a little leatherman squirt on my keychain and they wouldn’t let me in because of it, so I had to go all the way back out the car to leave the pocket knife (which if you’ve ever been to six flags, you know its no short walk). Then, we all bought season passes ($70 for a season pass, $40 for general admission, so if you go twice you’ve paid for it). We didn’t get our passes all taken care of until almost noon. We then procceded to ride Medusa three times, Vertical Velocity, and Boomerang (which I skiped and ate garlic fries). We also watched their whale show and got soaked on the log drop ride.








