Explore the guide library · Maintenance and recovery
Record exact revisions, device roles and support links without putting credentials into the inventory.

A useful home-network inventory does more than list “router” and “extender.” Exact model and hardware information can determine which firmware is appropriate, which replacement is compatible and where a fault should be investigated.
Record stable identity information
For each device, note the manufacturer, model, hardware revision and a private descriptive label. Record the installed firmware and official support page. TP-Link’s extender maintenance guidance illustrates why revision information matters when selecting an update.
Describe its role
State whether the device routes traffic, provides Wi-Fi, switches Ethernet, bridges buildings or supplies PoE. Include the physical location and upstream connection. A product capable of several modes should be documented according to how it is actually configured.
Keep secrets out
Store passwords, recovery codes and configuration backups in appropriate protected locations. The inventory can point to the relevant private record without containing the secret itself. Avoid sharing unredacted device labels or public contact details in a support copy.
Track the lifecycle
- Purchase or installation date when known.
- Last supported firmware update.
- Current support or end-of-life status.
- Any planned replacement requirement.
Manufacturer lifecycle terminology varies, so save the source and check date rather than recording a vague assumption that equipment is “too old.”
Connect devices to the cable map
Use the same outlet and patch-panel identifiers as the cabling record. Keep the device identity separate from the port so moving equipment does not erase the fixed-link history.
Review the inventory after a hardware or configuration change. A short accurate record is more useful than a detailed document that no longer matches the installation.
During the next outage, the inventory should let another authorized person identify the affected device, find its current documentation and understand what depends on it. That practical handover test is a good measure of whether the record contains the information the network actually needs.
Sources and editorial notes
Sources checked 8–9 October 2026. Independent guidance and original illustrations; product comparisons use published specifications rather than hands-on benchmarks. Check the exact model, revision and regional documentation before changing settings.
- TP-Link: extender management and revision-specific firmware
- ASUS: end-of-life networking products
- Fluke Networks: linking cable labels to test records