Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Given a lot of the users on here have vast experience, what is the best way to label individual cables for equipment mounted in a rack?

I was thinking something like:

Port Number of Switch | U-Number | Server Interface Number (such as Rc1-InterfaceID) on btoh ends of the cable but wanted to see what more experienced folks were using.

share|improve this question

closed as not constructive by SvW, Ward, Shane Madden, Brent Pabst, mdpc Nov 5 '12 at 17:46

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

    
There is no single best way, it just depends on too many factors. Think about what you want documented and what makes sense in your environment and then establish this scheme. –  SvW Sep 19 '12 at 14:28
add comment

2 Answers 2

up vote 3 down vote accepted

It ultimately depends on why you want the labels.

For me the most important thing is so that when something needs plugging back in, you don't have to trace the cables with your fingers - impossible in some circumstances. Your scheme would facilitate that, although you probably want to include:

  • Device/Patch ID (could be a server, switch, other network device or just a patch panel)
  • Interface ID (specifically which port the cable should be plugged into)

Include details of both ends of the cable at both ends, since sometimes you want to know where the far end of the cable goes!

I would say it is useful to use the physical labelling on the devices themselves, and then keep documentation of how that maps through in the specific system (e.g. NIC on a server may be labelled A, but in the OS it is eth0). Where you have multiple interface cards with multiple ports, you should agree and document a naming convention.

If you use VLANs you might want to include VLAN ID, or you might want to use different colour cables for different things.

I would avoid any tags that snag, and definitely anything that falls off easily.

share|improve this answer
    
So what kind of documentation do you use to match your physical labeling? Pictures of the back of the servers/switches/routers with some sort of color coding for each port to say which cables are going where? Not sure the best way to create a matching document –  What'sTheStoryWishBone Sep 20 '12 at 12:14
add comment

As SvenW points out there is no single best way.

The big thing I've found to be advantageous is to not label cables using server name, port number, etc. These items become inherently inaccurate over time. It takes a long tome to physically relabel cables. It is much faster to update a document. As a result my preference is to label the cable on both ends with a unique identifier (two letters and two digits is my favorite, but anything works really) and call it good. The other information (port assignments, servers, etc) are maintained in separate document, spreadsheet, etc.

I'm also a fan of color coding cables if / where applicable. If for example you have ESXi servers which are cabled into two network switches for redundancy as well as into an iSCSI SAN I'd color code Network 1 green, 2 blue SAN 1 white, 2 grey.

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.