A switch can run in a ceiling void for ten years without a single person looking at it. That is the core tracking problem with networking equipment: it is installed in order to be forgotten. Switches, routers, access points and firewalls disappear into comms cabinets, risers and roof spaces on day one, and from that moment the asset register is the only evidence the organisation owns them at all.
What you will learn
- Why network gear falls off the books
- What to record per device
- Labelling gear in cabinets and on ceilings
- Custody: who touched the cabinet last
- Spares, RMAs and the storeroom shelf
- Tools that make this easier
- FAQ
Why network gear falls off the books
Network hardware leaves the record in ways laptops never do:
- It arrives inside projects. A fit-out or an upgrade buys switches on a project budget, a contractor installs them, the project closes - and nothing was ever entered in the register.
- It dies without a funeral. A decommissioned switch stays racked and powered because unplugging it feels risky. The result is a zombie asset: drawing power and a support contract, serving nothing.
- RMAs swap serials silently. A failed unit goes back to the vendor, an identical replacement arrives, and the register still lists the serial number that left in the post.
- Monitoring creates false confidence. Monitoring shows what answers on the network right now. It cannot see the spare access points in a box, the unit out for repair, what anything cost, or when support expires. Monitoring is a view of traffic; it is not an inventory.
What to record per device
| Field | Why it matters |
|---|---|
| Asset ID | A number on a label, independent of hostnames and IP addresses that get reused |
| Device type, make, model | A “switch” can be 8 ports or 48 - the model determines spares, licences and what can replace it |
| Serial number + MAC | Serial for warranty and RMA; MAC ties the physical box to what monitoring sees |
| Location, down to the cabinet | ”Building A, riser 2, cabinet 3” finds a device; “head office” does not |
| Status | In service, spare, out for RMA, retired - the difference between spare stock and guesswork |
| Purchase date + price | Drives refresh budgets and depreciation |
| Warranty / support end | Decides whether a dead switch is a claim or an invoice |
| Custodian | The named person or team who answers for the cabinet |
| Attached documents | Invoices, support contracts, install photos |
Labelling gear in cabinets and on ceilings
- Label the front face, readable in the rack. A label that requires unplugging cables to read will never be read.
- Label access points before they go up. Once an AP is mounted, its label is out of reach. Record the exact mounting location (“Floor 2, corridor outside room 2.14”) and photograph the install while the ladder is still out.
- Give cabinets their own IDs. “Cabinet 3” only works if cabinet 3 says so on the door. Labelled cabinets turn location fields from folklore into fact.
- Choose heat-tolerant stock. Comms cabinets run warm year-round; paper labels curl and drop. Polyester or laminated labels stay put.
Custody: who touched the cabinet last
A comms cabinet is handled by more people than any laptop: in-house IT, electricians, the MSP, the fibre provider’s engineer, whoever had the key that day. Every install, swap and removal should land on the asset’s record as an event - who, what, when - so there is a chain of custody instead of a mystery. Name an asset custodian for each site or cabinet. The custodian does not have to perform every change; they have to know about every change, and they are who the register names when a device’s history needs a human.
Tip: put the register update inside the change procedure itself. The same checklist line that says “test the failover” should say “update the asset record”. A register maintained from memory always loses to a cabinet that gets visited twice a year.
Spares, RMAs and the storeroom shelf
Spare stock is where a network inventory pays its way. A dead switch at a remote site is a same-day fix only if you know a compatible spare exists and which shelf it sits on - otherwise it is a procurement exercise with users offline. Track spares with their own status, not as a vague pile. When a unit fails, mark it out for RMA with the date and the vendor reference, and book the replacement in as a new asset with its own serial and label. Swaps that are not recorded as swaps slowly turn the register into fiction - the same discipline that keeps a server inventory trustworthy.
Tools that make this easier
A network inventory spreadsheet is usually born during an audit and dies quietly afterwards. It captures one heroic walkthrough of every cabinet, then ages: nobody stands in a plant room updating a sheet, and a spreadsheet has no way to record the swaps, RMAs and moves that happen between audits. Twelve months on, it describes the network as it was, with no record of how it changed. Working through an IT asset inventory checklist fixes the first pass; the maintenance problem remains.
AMPthilly is built for the maintenance problem. Every device gets a profile with serial, model, location, custodian, warranty end and attached invoices and support contracts; custom fields hold gear-specific details like MAC addresses; and a printable QR label on the front face opens the record in a phone browser at the cabinet - check the status, log a swap, or report a fault without leaving the riser. Every change lands in a filterable audit history. The free plan (3 users, 25 assets) covers a small office’s switches and access points end to end, with no card required.
FAQ
How do I keep track of networking equipment? One register, every device, serial and model recorded, location down to the cabinet, a label on each front face, and installs, swaps and removals logged as events with a named custodian per site.
What should a network equipment inventory include? Asset ID, type and model, serial and MAC, cabinet-level location, status, purchase date and price, warranty or support end, custodian, and attached invoices and contracts.
Does network monitoring replace an asset inventory? No. Monitoring sees what is online now; it knows nothing about spares, RMAs, costs, suppliers, support dates or retired gear. They answer different questions.
Where do you put asset labels on switches and access points? Front face for rack gear, readable without unplugging anything. Label APs before mounting, record their exact ceiling position with a photo, and give cabinets their own IDs.
How do I track network equipment across multiple sites? A consistent site-building-room-cabinet hierarchy, labelled cabinets, a custodian per site, and register updates baked into the change procedure. QR labels let anyone on site identify a unit with a phone.
The takeaway
Networking equipment is bought to be invisible, so the register has to do the work the eye cannot. Record every device down to the cabinet, label gear before it disappears into ceilings, treat swaps and RMAs as events, and give every site a custodian. The day a switch dies - and that day always comes - the difference between an outage and an anecdote is whether the register knows where the spare is.