Verkada cameras have LLDP, but most of the useful information is hidden in vendor-specific
LLDP values which are not documented on help.verkada.com
. The goal of this article is make documentation for Verkada’s LLDP implementation to aid in the implementation of a comprehensive network monitoring and management solution at the network locations that use Verkada cameras.
Raw LLDP information display for a Verkada camera
<aside> 🧠 You used to not get LLDP frames from non-camera Verkada products, such as Access Control, Alarms, or Sensors because the firmware for these products is completely different and is managed by different teams. It is, however, unclear which products include LLDP as select new access controllers are now providing LLDP data. Verkada still has no official list of which products provide LLDP functionality.
</aside>
Field | Description | Example (source) | Example (converted to ASCII, if applicable) |
---|---|---|---|
Device | Device ID | e4bd3189-8160-4f45-8a07-de20ba17e31e |
|
Port | This is the MAC address of the device | e0:a7:00:aa:bb:cc |
|
UID | Appears to be the MAC address of the device | e0a700aabbcc |
|
System name | Device ID | e4bd3189-8160-4f45-8a07-de20ba17e31e |
|
System description | This always says “Verkada Security Camera,” since only cameras have LLDP | Verkada Security Camera | |
Port ID | This is the MAC address of the device | e0:a7:00:aa:bb:cc |
|
Chassis ID | This is the MAC address of the device | e0:a7:00:aa:bb:cc |
|
Port description | The interface on the camera - since all Verkada cameras have one port it will always say eth0 | eth0 |
|
Management address | The IP address of the camera on your LAN | 10.123.45.67 | |
System capabilities | Always reports the same static value | S-VLAN Component of a VLAN Bridge, Two-port MAC Relay | |
Vendor specific [OUI: 00120f, subtype: 3] | IEEE 802.3 Link Aggregation TLV | 0x0100000000 | |
Vendor specific [OUI: 00120f, subtype: 1] | IEEE 802.3 MAC/PHY Configuration/Status TLV | 0x03EC000010 | |
Vendor specific [OUI: 0012bb, subtype: 1] | TIA TR-41 Committee - Media Endpoint Discovery (LLDP-MED, ANSI/TIA-1057) - LLDP-MED Capabilities TLV | 0x003F01 | “4609”, when converted to decimal |
Vendor specific [OUI: 0012bb, subtype: 6] | Firmware release version - formally called TIA TR-41 Committee - Media Endpoint Discovery (LLDP-MED, ANSI/TIA-1057) "Inventory - Firmware Revision TLV | 0x76323032332E30392E30352E3336393833362D676F726F | v2023.09.05.369836-goro |
Vendor specific [OUI: 0012bb, subtype: 7] | Unknown | 0x556E6B6E6F776E | “Unknown” |
Vendor specific [OUI: 0012bb, subtype: 8] | Serial number | 0x374a45412d424242422d43434343 | 7JEA-BBBB-CCCC |
Vendor specific [OUI: 0012bb, subtype: 9] | OEM | 0x5665726B616461 | Verkada |
Vendor specific [OUI: 0012bb, subtype: 10] | Model | 0x434835322D315442452D4857 | CH52-1TBE-HW |
<aside> 🎯 Remember - these aren’t official documented LLDP values so they can change anytime without notice.
</aside>