CABVIX FIELD GUIDE
Network rack
documentation guide.
A practical method for creating a physical network record that another technician can understand, verify and maintain.
Useful rack documentation explains what is installed, where it sits and how the physical connections run. It should help a technician answer routine questions without relying on memory, an old spreadsheet or the one person who knows the site.
Could an authorised technician who has never visited the site identify the correct cabinet, device, port and downstream location from the record?
1. Establish the location structure
Begin with the physical hierarchy people use when attending the site. Record the client or organisation, site, building or area, room and cabinet. Give every cabinet a stable name and capture its size, position and purpose.
- Client or organisation and site name
- Building, floor, room or communications-area reference
- Rack identifier and rack-unit capacity
- Local access notes that are appropriate for authorised users
- Responsible team or record owner
2. Record installed hardware
Build the cabinet from its real rack-unit positions. Include patch panels, switches, routers, firewalls, servers, fibre trays, shelves, cable managers, power equipment and other devices that affect the physical network.
For each item, capture enough identifying information to distinguish it from neighbouring equipment: manufacturer, model, role, serial or asset number where appropriate, management name, rack-unit position and relevant notes.
3. Document ports and patching
A rack image alone cannot explain the connection path. Record the relationship between patch-panel ports, switch ports, outlets and directly connected hardware. Include lead colour, PoE requirements and locally meaningful tags where these support field work.
- Patch-panel identifier and port
- Connected switch and switch port
- Outlet or endpoint served
- Fibre, inter-rack, carrier and internet-service paths
- Connection status and verified date
4. Map outlets and endpoints
Outlet labels should connect the room or floor-plan location back to the correct cabinet and patch-panel position. Record each socket individually when a wall plate contains multiple ports. Where an endpoint is known, identify the connected device or service.
5. Capture evidence and exceptions
Photographs, test results, marked-up plans and close-out notes provide context, but they should support the structured record rather than replace it. Record missing labels, inconsistent colours, occupied ports, damaged hardware and unverified paths as explicit exceptions.
6. Keep the record current
Documentation becomes unreliable when it is treated as a one-off audit. Update it during moves, additions and changes. Retain a history of repatching, equipment replacement and approved deviations so the current state and significant changes remain understandable.
The person completing the physical change updates the record before the task is closed or handed over.
Minimum useful rack record
- Site, room and cabinet identity are unambiguous.
- Rack size and RU positions match the installed cabinet.
- Installed hardware is named and identifiable.
- Patch panels, switches and relevant ports are recorded.
- Outlets and important endpoints trace back to the rack.
- Uplinks, fibre, inter-rack and carrier paths are represented.
- Unknowns and exceptions are clearly marked.
- The record shows when and by whom it was last verified.