What's a reliable way to test patch panel connections?

Solution 1:

You are correct to suspect that your $5 network tester is inadequate to the task. It's fine for verifying that your wire map is correct and that the you have connectivity, but it won't detect any of the other problems, like the many varieties of crosstalk.

If you are fine with learning about problems as they occur, you're probably fine with the testing process you described. Another good test would be to push some actual traffic through the wire (iperf on both ends of the wire) and see if any of them run dramatically slower than the rest.

The downside is that when some weird network issue occurs, you'll never be sure if it's your wiring or something farther up the stack.

There are companies that lease test equipment. If you could get your hands on a good Fluke meter for a day, it would go a long way to identifying any of the more esoteric wiring problems.

Solution 2:

How limited is a limited budget?

$0 budget If you have a technical center in town (highschool votec) they might have a highend fluke that could do the work -- call them and see if its something you could use as a teaching exercise for students and borrow gratis.

$100 budget A 'cheap' solution is to swap out your network switches with (used?) managed switches that can monitor packet loss.

A port that has packet loss = bad drop.

You can pickup really cheap 100base switches that are fully managed, and use something like Cacti to log all packet errors per port over time.

$1000 budget If you have a little more money -- consider asking a local wiring company what they would charge to audit your connections. They have the $1000 fluke that can do the work, and should charge ~$120/h for two people to run the tests for ~05 minutes per drop. They might even 'rent' you the tool.

and I'm using a bargain bin $5 manual punch down tool,

Invest in a 'real' tool. They are like $80 aren't they? I think thats what I paid with a 66 block and a 120 block punchdown (are those the right numbers). It litterally changed my outlook on cabling. I would implore you to even buy it yourself if you have to.

There is also the, "if it isn't broken don't mess with it" school of thought. If you aren't having problems its 'close enough' to working. I have seen some REALLY badly installed drops that drop ~10% of the packets yet still work. Stick with your laptop test, copy a 100mb file off another machine, and call it "good enough" for now.

Solution 3:

IMHO, No. I recommend getting a testing tool that does more than making sure each pin is connected correctly. Check out this question for some good answers:

https://serverfault.com/questions/7441/help-me-fight-this-spaghetti-monster-cabling/7449#7449

I just noticed you mentioning something about not using 'network tools', if that's the case (I'm guessing you don't want to spend the cash for 12 clients - though I/most would definitely argue that), then you might want to look at future releases of the NDT server which is claims to include a feature to detect a bad Cat-5 cable.

Solution 4:

Every network guy's first investment should be a decent punchdown tool; you can get a workable unit from your local mega-hardware store, most of them have a low voltage/electronics section these days.

After that, as has been said, load-test, beg or borrow some testing tools and definitely look for a managed switch that fits your budget.

And welcome to the party.

Solution 5:

I've also had a couple of tight-fisted clients who assume that setting up this stuff is quick and free, and it is always difficult to convince them that both time and proper tools are required.

That being said, if you can't afford to buy a very nice Fluke cable tester then I'd recommend hiring, begging or borrowing one for a day or two - it will save you a lot of hair later on...