Skip to main content

Device, Cable, and Panel Labeling scheme.

V2 of the Device, Cable, and Panel Labeling scheme. It keeps the V1 content and makes the formats consistent. Items marked PROPOSAL are new rules that need your decision. Items marked UNTESTED have not been checked on a real printer or site.

Scope

How to name and label sites, rooms, panels, patch panels, devices, and cables in my installations. Based loosely on ANSI/TIA-606 (see "Relation to TIA-606" below). Device naming (firewalls, switches, cameras, access control) is my own convention, not part of 606.

General rules

RuleDetail
CharactersUppercase letters, digits, - and . only. No spaces, no &, no /. Lowercase is used only for the suffix letter (see below).
- (dash)Separates fields: site, then room or device, then patch panel or role. Example: SASC-IDF.1.01-P6.12
. (dot)Separates numbers inside one field: floor, door or panel number, port. Example: IDF.1.01 = IDF, floor 1, door 01. SW01.49 = switch 01, port 49.
Suffix letterLowercase a, b, ... for a second item at the same spot, or the legs of a split cable. Example: SASC-IDF.1.01b, P6.12a.
PaddingPROPOSAL. Floor: 1 character. Door, panel, device number, port: 2 digits (01). Cable serial numbers: 3 digits (001).
FloorsPROPOSAL. 1 = ground or entry floor, 2, 3 ... above. B = basement (B, then C for a second basement level).
Site prefixRequired on room, panel, and device labels. May be left off cable labels when both ends are in the same site (saves label space).
Same label both endsEvery cable gets the same label at both ends. A cable label must use the exact device and port names on this page.

Site codes

PROPOSAL: 3 or 4 uppercase letters. Fill in the table as sites are added.

CodeSiteNotes
SASC(fill in)
MHFWilson (fill in)
925(fill in)Numeric. Keep, or rename to letters? See Open questions.

Rooms, panels, and doors

Doors and panels are numbered clockwise, starting at the Main Entry. PROPOSAL: on other floors, start at the stair or elevator nearest the Main Entry.

TypeFormatExampleSecond one
Main Point of Entry (MPOE)SITE-MPOE.floor.doorSASC-MPOE.1.06N/A. One MPOE per site.
Intermediate Distribution Frame (IDF)SITE-IDF.floor.doorSASC-IDF.1.01SASC-IDF.1.01b (second IDF behind the same door)
Media cabinet / panelSITE-PNL.floor.numberSASC-PNL.2.01SASC-PNL.2.02
Facility doorSITE-DR.floor.doorSASC-DR.1.01SASC-DR.1.02
Patch panel (inside a room or cabinet)P + number, top to bottomP6P7
Patch panel portP#.portP6.12P6.12a, P6.12b (split cable)
Port, full nameSITE-ROOM-P#.portSASC-IDF.1.01-P6.12

The patch panel face only needs the short form (P6.12), because the room is already known. Use the full name in records and on riser cables.

Notes

MPOE: where the carrier's service enters the building (the demarc). In houses it is often under the stairs or in the basement. In large buildings, riser cables run from the MPOE (or the main equipment room) up to the IDFs on other floors.

IDF: the room or rack on each floor that holds the switches for that floor. It connects back to the MPOE with riser cables.

Device labels

Network and server devices
TypeFormatExampleSecond one
ISP handoff (modem / ONT)SITE-ISP##MHF-ISP01MHF-ISP02. Put the carrier name (e.g. ATT) in the records, not the label.
Firewall / routerSITE-FW##SASC-FW01SASC-FW02 (HA pair: 01 = primary)
Aggregation / distribution switchSITE-AGG##SASC-AGG01SASC-AGG02
Access switchSITE-SW##SASC-SW01SASC-SW02
Wireless access pointSITE-AP##SASC-AP01PROPOSAL (new in V2)
Server / hostSITE-SRV##SASC-SRV01PROPOSAL (new in V2)
NASSITE-NAS##SASC-NAS01PROPOSAL (new in V2)
UPS / PDUSITE-UPS##, SITE-PDU##SASC-UPS01PROPOSAL (new in V2)
Cameras
TypeFormatExampleSecond one
Internal cameraSITE-INT-WhatSASC-INT-CashRegSASC-INT-CashReg02
External cameraSITE-EXT-WhatSASC-EXT-DrivewayNSASC-EXT-DrivewayS

Cameras are named for what they look at. INT and EXT show access level at a glance: tenants and employees can usually see external cameras, but access to internal cameras is tightly controlled. The camera name is the exception to the uppercase rule, so it stays readable.

Access control (physical hardware in panels or on walls)
TypeFormatExampleSecond one
Door access hubSITE-CTL.floor.doorSASC-CTL.1.05SASC-CTL.1.05b
Reader-Flex (no hub)SITE-CTL.floor.doorSASC-CTL.1.01SASC-CTL.1.01b
Badge reader(controller)-RDRSASC-CTL.1.05-RDRSASC-CTL.1.05-RDRb (second reader, e.g. exit side)
Door intercom(controller)-INTSASC-CTL.1.05-INT

The door number in a CTL label is the same as in the door's own label (SASC-DR.1.05 uses SASC-CTL.1.05).

Cable labels

Two-line wrap label, the same at both ends:

  • Line 1 (top) = upstream end: the end closer to the ISP / core.
  • Line 2 (bottom) = downstream end: the end closer to the user or device.
  • Each line = device or port name from this page, plus .port.

The diagram above is from V1 and may still show V1 formats.

This is different from TIA-606, where the near end is printed first so the order flips at each end. Here the order is always upstream first, so the label reads the same everywhere.

CableLine 1 (upstream)Line 2 (downstream)Notes
ISP to firewallISP01FW01.WAN1Second WAN: ISP02 / FW01.WAN2
Firewall to aggregation switchFW01.03AGG01.01HA: FW02.03 / AGG02.01
Aggregation to access switchAGG01.10SW01.49Bond / LAG: label each member normally (e.g. AGG02.12 / SW01.49 and AGG02.13 / SW01.50). Record the LAG in the docs.
Switch to patch panel (patch cord in rack)SW01.12P6.12
Patch panel to wall outlet (horizontal)IDF.1.01-P6.12Outlet faceplate shows the same IDSplit cable: P6.12a, P6.12b
Riser / backbone (between MPOE, IDFs, panels)MPOE.1.06-P1.01IDF.2.01-P1.01Add the site prefix if the cable leaves the site.
CameraIDF.1.01-P3.05 or SW01.05INT-CashRegThe bottom line is the camera name.
Access hub to badge readerCTL.1.05CTL.1.05-RDRIntercom: CTL.1.05 / CTL.1.05-INT
Switch to access hub / Reader-FlexSW01.20CTL.1.05

UNTESTED: I have not checked how many characters fit per line on the 1.5" x 1.0" wrap label (M7-31-427). MPOE.1.06-P1.01 is 15 characters. Print a test label before committing to the riser format.

Service type (from V1)

V1 used a service prefix on patch cables: NET-001, TEL-001, COM-001. In V2 the panel port ID replaces the serial number. PROPOSAL: show the service with cable color (see Relation to TIA-606) or with a third line on the label. See Open questions.

Hardware and labels

Printer: Brady M710

Label typeSizeBrady part numberPer rollPrice (V1, date unknown)Ribbon
Basic sticker1.0" x 1.0"M7-19-423250$43.50(fill in)
Metallic label1.0" x 2.0"M7-20-435100$40.00(fill in)
Cable wrap (self-laminating)1.5" x 1.0"M7-31-427250$68.00R4300 ($73.00)

Brady M710

Templates

Site template (editable): NetworkIdentification.docx

Site template preview

Patch bay label templates:
PatchBaySize_12portLevitonKeystone.docx
PatchBaySize_12portSurfacemount.docx
PatchBaySize_24portKeystone.docx
PatchBaySize_24port.docx
PatchBaySize_48port.docx

These templates were made for V1 formats and may need updating.

Relation to TIA-606

ANSI/TIA-606 is the US cabling administration standard. ISO/IEC 14763-2 is the international equivalent. This scheme borrows its ideas (unique IDs, both ends labeled, records kept) but uses its own formats.

This schemeTIA-606 term
MPOEEntrance facility (demarc). Often in the same room as the equipment room / main cross-connect (MDF).
IDFTelecommunications room (TR)
Riser cableBackbone cable
Patch panel to outletHorizontal link
Multi-site with site codesClass 3 (campus) / Class 4 (multi-site)
606 color codes (from memory, not checked against the current revision)
ColorUse
OrangeDemarc / carrier
GreenNetwork connections (customer side of demarc)
PurpleCommon equipment (servers, PBX)
WhiteFirst-level backbone
GraySecond-level backbone
BlueHorizontal (to the outlet)
BrownBetween buildings
YellowMiscellaneous (security, alarms)
RedKey telephone systems
606-B cable example (kept from V1)

Near end AG09-35:01/AJ06-35:01, far end AJ06-35:01/AG09-35:01. AG09 = rack at grid AG09, -35 = patch panel 35 rack units from the bottom, :01 = port 1, / = separates near end from far end. Newer revisions (606-C, 606-D) exist. I have not checked what changed.

Changes from V1

ItemV1V2
MPOESASC-MPO.1.6SASC-MPOE.1.06
IDF second unitIDF-1-1aSASC-IDF.1.01b
DoorsSASC-01-DR01SASC-DR.1.01
Firewall on cablesFW-Primary-WAN1FW01.WAN1 (same name as the device label)
Aggregation switchAGG-## and AGGR-##AGG##, with its own device row
Site 925 devices925-FW01Same format, but see Open questions about the code
Wilson-MHF patch portMHF-IDF2.1-P1.1MHF-IDF.2.01-P1.01 (same rule as every site)
Access hub suffix1.1A / 1.05a mixedAlways lowercase: 1.05b
Intercom / reader-IntCom, -Reader-INT, -RDR
CamerasINTERNAL-CashRegSASC-INT-CashReg
Camera cableSASC-CAM-1.05Port ID / camera name
Wire label orderTwo conflicting wordingsLine 1 = upstream, line 2 = downstream
Bond cables-BONDa / -BONDbLabel each member normally. LAG in the records.
NewGeneral rules, site code table, AP / SRV / NAS / UPS / PDU, patch panel naming, 606 mapping

Open questions

  • Fill in the site code table. Should 925 stay numeric, or get a letter code?
  • Agree with the separator, padding, and floor proposals?
  • Line 1 = upstream: is this the order you actually use in the field?
  • Service type: drop NET/TEL/COM, use cable color, or add a third label line? What did COM mean?
  • Are MPOE and MDF always the same room in your sites, or do you need an MDF room type?
  • Do you want rack positions (rack units, as in 606) in the labels, or is P# top to bottom enough?
  • Print a test wrap label to check line length (see UNTESTED note).
  • Ribbon part numbers for the basic and metallic labels.
  • V1 of this page, saved as a copy ending in "_old" (link to be added)