How Do You Keep a Camera Inventory? Fields, Labeling and CMDB

A schema of mandatory fields for a camera inventory, a naming and site labeling standard, automatic discovery with ONVIF and switch tables, and accuracy audits.
Technical summary
Technology
ONVIF WS-Discovery, GetDeviceInformation, LLDP, MAC/ARP table, CMDB
Topic
An inventory linking cameras, recorders, switch ports and locations
Level
Beginner–intermediate
Prerequisites
  • A management host with access to the camera VLAN
  • Read permission on switches and the VMS
In this article7 sections

When a camera fails, the technician’s first question is always the same: Where is this camera, which switch port is it connected to, which recorder does it write to? If the answer is in several people’s memories rather than in a table, every intervention starts with a survey, and if that person is on leave, hours are lost. Below we explain which fields an inventory linking cameras, recorders, switch ports and physical locations should contain, a site labeling standard and how to keep the inventory up to date with automatic discovery.

Why the inventory is the basis of maintenance

Almost every process in a camera system relies on the inventory. Gaps in the inventory are usually noticed when a process gets stuck:

  • Fault response: a PoE or cable fault can’t be diagnosed without knowing the port and cabinet the camera is connected to.
  • Firmware management: without knowing which version runs on which model, you can’t say whether a security bulletin affects the organization, and a wave plan can’t be made (camera and NVR firmware update plan).
  • Monitoring and alarms: if the switch–port–camera dependency isn’t defined, a single uplink failure produces dozens of separate alarms (camera health monitoring).
  • Audit and compliance: which camera sees which area, and where and for how long recordings are kept, is also needed for the personal data inventory and VERBİS (the Turkish data controllers’ registry) records (camera systems and VERBİS).
  • Renewal planning: the budget can’t be justified without device age, warranty and support status.

The inventory’s value isn’t in the number of fields but in their accuracy and the relationships between them. A fifty-column table that’s half empty is no use to anyone. The schema below shows mandatory and recommended fields for a camera record. Similar but separate tables are kept for recorders, switches and UPSs; the camera record links to them by ID.

Field Example value Status Source
Camera ID IST1-B2-F1-CAM-014 Necessary Naming standard
Brand / model Manufacturer, model code Necessary ONVIF GetDeviceInformation
Serial number Device serial no. Necessary ONVIF / label
MAC and IP address MAC, 10.20.1.14 Necessary Switch ARP/MAC table
Firmware version Version number Necessary ONVIF / VMS
You are here Building, floor, area, floor plan reference Necessary Site
Switch and port IST1-B2-SW03, Gi1/0/14 Necessary LLDP / MAC table
Patch panel point B2-F1-PP2-14 Necessary Site label
Recorder and channel VMS-REC-02, channel name Necessary VMS
Criticality class A / B Necessary Risk assessment
Purpose and image level Entrance, identification Recommended Project document
Recording mode and retention Continuous, target days Recommended VMS, retention policy
Installation date, warranty, end of support Dates Recommended Purchasing, manufacturer
Reference image Day and night file path Recommended Acceptance test

Passwords are never written in the inventory. Camera and recorder accounts are kept in a password vault; only a reference to the vault entry may appear in the inventory. A sight still common on site is a “user/password” column in a spreadsheet in a shared folder.

Naming and site labeling standard

A good naming standard lets whoever reads the name find the camera on site. Recommended structure: SITE-BUILDING-FLOOR-TYPE-SEQ. For example, IST1-B2-F1-CAM-014 means camera number 14 on the first floor of building B2 at the Istanbul 1 facility. Rules:

  • Use only uppercase letters, digits and hyphens; don’t use non-ASCII characters such as Turkish letters, or spaces (some VMS and switch interfaces corrupt them).
  • A sequence number never changes once given; when a camera is replaced, the ID is kept and the serial number and model are updated.
  • The same name is used in the VMS channel name, the camera device name, the switch port description and the physical label.
  • IDs of removed cameras aren’t reused, so there’s no confusion with archived recordings.

Physical labeling is done at three points: the camera housing or mounting bracket (in a size readable from the ground), both ends of the cable and the patch panel port. Outdoors, use labels resistant to UV and moisture; an ordinary paper label becomes unreadable after one summer. Writing a port description on the switch side is the cheapest step linking the inventory with the site:

! Cisco IOS example: switch port description
interface GigabitEthernet1/0/14
 description IST1-B2-F1-CAM-014 | PP2-14
!
! Verification
show interfaces description | include CAM-

Automatic discovery: ONVIF, VMS, switch tables

A hand-kept inventory starts going stale at the first change. Most technical fields should be collected regularly from automatic sources, and the inventory compared with this data.

Device information via ONVIF

ONVIF-compliant cameras can be found on the network with WS-Discovery; discovery messages are sent over UDP port 3702 to the multicast address 239.255.255.250. Since multicast isn’t routed between VLANs, run discovery from a host inside the camera VLAN. A discovery tool run from the management VLAN finds zero devices, and the team thinks ONVIF doesn’t work. From the devices found, manufacturer, model, firmware version and serial number are read with GetDeviceInformation. A simple example with the onvif-zeep library in Python:

from onvif import ONVIFCamera

cameras = ["10.20.1.14", "10.20.1.15"]
for ip in cameras:
    try:
        cam = ONVIFCamera(ip, 80, "inventory", "Password")
        info = cam.devicemgmt.GetDeviceInformation()
        print(ip, info.Manufacturer, info.Model, info.FirmwareVersion, info.SerialNumber, sep=";")
    except Exception as err:
        print(ip, "ERROR", err, sep=";")

For this script, create a separate read-only “inventory” account on the camera; inventory isn’t pulled with the admin account. On some models, the ONVIF service port may be something other than 80. The specifications are published on ONVIF’s official site.

VMS and switch tables

The VMS knows which camera is connected to which recording server and the channel names; most enterprise VMS products provide this via CSV export or API. On the switch side, the MAC address table, ARP table and LLDP neighbors give the camera–port relationship:

! Which MAC is on which port in the camera VLAN (example VLAN 20)
show mac address-table vlan 20
! Neighbor information for cameras that support LLDP
show lldp neighbors detail
! Per-port PoE status and power drawn
show power inline

The address in the MAC table is mapped to an IP using the ARP table (usually on the L3 switch or firewall that is the camera VLAN’s gateway). If more than one MAC appears on a port, there’s an intermediate switch or unmanaged device there. Investigate it separately. A small unmanaged switch added in the ceiling later is a point of failure that doesn’t show in the inventory.

The CMDB and floor plan relationship

In small systems, a well-structured table may be enough. With multiple sites, hundreds of cameras and more than one team, the organization’s CMDB or asset management system should be preferred, and relationships modeled explicitly:

  • Camera → switch port → switch → cabinet → UPS: power and network dependency; alarm suppression rules in the monitoring system are derived from this.
  • Camera → recording server → storage: shows which cameras go unrecorded when a recording server fails.
  • Camera → area → floor plan: each camera’s position and field of view are marked on the floor plan; the mark on the plan must match the ID in the inventory.
  • Camera → responsible unit: who holds video access permission and change approval?

Floor plans are also versioned as part of the inventory. If the plan isn’t updated when a camera is added, moved or removed, coverage analysis and incident review are done on a wrong assumption. An old plan is a wrong plan. For central management of the inventory in multi-site setups, see the scope of multi-site central camera management. For consistency with the port map and IPAM on the network side, the network documentation and IPAM article is complementary.

Auditing inventory accuracy

An inventory whose accuracy isn’t measured can’t be trusted. Accuracy is checked in two directions:

  1. From record to site: records chosen at random from the inventory are verified on site: is the camera at the stated location, is the label correct, is it connected to the stated port?
  2. From site to record: cameras chosen at random on site are checked for a correct record in the inventory. This direction catches unrecorded “shadow” devices.

For each record checked, errors are counted per field and the result reported as an accuracy rate. Incorrect records in critical fields (location, port, recorder) are fixed immediately; recurring error types point to a process problem. For example, if port errors come up often, field teams aren’t reporting cable moves to the inventory; an “inventory updated” step is added to the change form.

Checklist:

  • Does every change record (addition, move, replacement, removal) close with an inventory update?
  • Is an automatic comparison report produced at least weekly, and are the differences reviewed?
  • Do switch port descriptions and VMS channel names match the inventory ID?
  • Are removed devices marked “decommissioned” and kept with their history?
  • Do floor plans reflect the latest changes?

An up-to-date inventory is also the starting point of a camera system technical audit. For independent verification of the inventory and identifying gaps, see the scope of the camera systems technical audit, and for tying regular updates to the maintenance process, the periodic maintenance and support service.

Frequently asked questions

What fields must a camera inventory include?

The mandatory fields are camera ID, brand and model, serial number, MAC and IP address, firmware version, physical location, the switch and port it’s connected to, the patch panel point, the recorder and channel, and the criticality class.

Can camera passwords be kept in the inventory?

No. Passwords are stored in a password vault with restricted access and an audit trail. Only a reference to the relevant vault entry may appear in the inventory.

Why should ONVIF discovery be done from within the camera VLAN?

ONVIF WS-Discovery works with messages sent over UDP 3702 to the multicast address 239.255.255.250. This multicast traffic usually isn’t routed between VLANs; the discovery tool must run in the same VLAN as the cameras.

How is inventory accuracy measured?

Records chosen at random from the inventory are verified on site, and cameras chosen at random on site are verified in the inventory. Errors are counted per field to report an accuracy rate, and recurring error types are turned into process improvements.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles