Discussion on:

10 things you shouldn't do when running network cable

#8 That means using a cable testing device, such as a LANcat, or other device to certify the connection. Not using an LED tester to show the wires are right and then plugging in a computer and checking if it shows a 1Gb connection.
Also the real testers will generate a log which the installer can give you to show everything was done.

#3 and #9: In order for network cable runs to be certified, they must also be terminated with a jack at each end, not just left with an RJ45 end to plug into the switch/computer.

"If you have to go near electrical power lines, cross them in parallel instead."
not sure "parallel" was the intention

I think "perpendicular" was intended, no?

Absolutely. I'm the author... I certainly meant perpendicular.

I'm not sure but I think often there are chutes running parallel with hallways where the power is run, and of course it is easy to run along a drop ceiling that way. If you are trying to cross perpendicular wouldn't you have to do some weird things? Ie. run the wires across every wall, if you are running data chutes than you'd have to make a gap in the chute where it crosses power etc. Fortunately I don't have to do network monkey work but for those that do ... ease the pain

Cross at an angle, then keep a few inches or more between high and low voltage.

It seems to me though that since most interior power cables are in conduit that emi wouldn't be that much of a problem. I've seem hundreds of feet of telephone lines run alongside power conduit with no interference problem. (remember, that's UTP analog and highly susceptible to emi.)

Line that reads: If you have to go near electrical power lines, cross them in parallel instead.

Should be perpendicular, not parallel.

If cabling in a building with more than one story, then cabling rated for air ducts (plenum cabling) should be used for the lower level even if the cabling is not routed through air ducts. If a PVC jacket on a cable were to burn on a first floor, then the toxic chemicals could rise up to the second floor level and above.

Note: The space between the buildings structural ceiling and a suspended ceiling is usually considered a plenum air space (This applies to raised floors in computer rooms as well). Caveat: Some ceilings create a tight seal with no air flow, so are not subject to these restrictions.

Additionally, some new theories suggest that abandoned cables in plenum air spaces may create a hazard in the event of a fire since the air flow through the spaces supplies oxygen which will fan the flames and create a much hotter and stronger fire.

PVC cables also serve to allow the rapid transport of the flame from a central location to an entire building, often in under a minute.

A key factor in plenum cabling isn't just the minimal toxicity of the fumes, it's the fact that the jacket is self-extinguishing.

Another common error is to over-cinch cable ties on bundled cables, specially on racks. Use a good tension tool that provides repeatable results. Over-tension can throttle bandwidth significantly

I know spreadsheets are popular for documenting patch panels but, does anyone know of more advanced software for documenting your patch panels, switches, etc?

Way back in my old days in IT, I worked for a company that used both Thin-net and older Thick-net cabling. This cable was awful to run and maintain. I, and probably many other people, welcomed the change over to UTP when that became the standard much later on.

When I started my job there, they had me run cabling for their demo room. I was a tech, but this was my job too because I was the new guy. There were network problems all over the building. As I worked my way through the mess, it turned out to be self-inflicted by my tech teammates. They had insisted on running the thin-net cable over the florescent light fixtures, which were causing all kinds of poor performance due to electrical interference. I explained to them what the problem was, but they insisted I knew nothing because I was the new guy on the team.

Then there were the vampire taps and the Thick-net cable. This nasty stuff has its own issues such as bending radius and tapping too deep into the coaxial cable. The standards are set to ensure proper data handling and good performance. Well again these guys insisted on shoving this cable into tight spaces, which bent the cable too tight. There were also other cases where the taps were obviously too deep into the cables, which had to be replaced. When I mentioned this too, I was told to shut up and do the job.

I didn't last much longer with them after that, and left for a much more respectful company. The org closed a few months later when they were purchased by another company and everything was transferred to Delaware.

Mark both ends and then write down someplace where (room/floor) the drops are. Five years from now someone else may be looking at the panel wondering where 231 is, because it isn't in room 2-31.

Absolutely spot on! Always map and document it in detail, and put copies in several places with a name beginning with an "A" or zero so it can be found easily at the top of the relevant folder.

In addition, I also write the specific floor/room number on the top edge of the door on a bit of masking tape (it's the one safe place guaranteed not to get disturbed.) May be overkill, but the doc will then always match up should there be any later room renumbering.

Always wait for the FINAL furniture layout, usually you will get 4-5 blue prints before they make their mind. dont forget the Printer, WiFi, Projector, Fax Machine, and the kitchen if you have IPT, forthe drawings and documentation, keep a copy in the cabinet, one with the network admin and one for the facilitymanagemnt team.

One thing I run across a lot in bad UTP installs is punch downs with way too much of the cabling untwisted at the end. They are intended to be punched down snugly, you shouldn't have 1 or 2 or 6 inches of untwisted wiring - it violates the integrity of the cable completely. Also, ditto on the testing and marking of the cables. It's great to follow a standard (if you don't, get one) but if you don't have one at least mark it unique and the same at both ends.

On #1 - if you're doing new construction (and you have any say in the matter whatsoever) - use conduit! Having done more ThinNet to Cat3 and Cat3 to Cat5, and even a Cat3 to Fiber (yes, prematurely) than I would like to admit, trust me, the cost of the conduit will pay for itself many times over.

Run *4* instead. Somebody will certainly want a VoIP phone, network printer, and spare laptop connection there in short order.

Seriously, cable is cheap in comparison with labor. Even if you just label it and leave it unterminated, I've never regretted running too many cables.

I was called in to find out why a new building with new cabling was simply not working over any part of the network. The cabling had been done by the local telecomm team. Beautiful conduits, very neat wall plate connections BUT when I took a look behind the patch panel I find ..more very neat work. Each cable had been straightened and lined up with its partner along a board and pinned in place. Then nice right-angled turns into each port. Pretty but all the cables were untwisted for at least 24 inches! I had to move the rack to get enough cable to re-terminate the panel properly.
I can just imagine the 'phone tech guy with the guys having a beer after work... "the cable they gave me to work with was terrible, all twisted to hell! "

NT

Very good article, and indeed must plafinicar good wiring and think ahead, not only the basic needs of the present, as these increase significantly. eg " Data Cabling" is something that increases every day by new technologies and the use of more data.

Pulling cable is a two person task. If you pull cable without someone feeding it you will wind up with kinks in the cable effectively destroying the entire run.