Classic Alarms Network Settings
Learn about the required network settings for Verkada Classic Alarms
This article is a guide for classic Alarms. Refer to this article if you have new Alarms. See New Alarms vs Classic Alarms if you are unsure which version of Alarms you have.
This article outlines the required network settings that your Verkada Classic Alarms devices need to communicate with Verkada Command. For more information on the required network settings for other Verkada product lines see Required Network Settings.
Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command.
IP address
Alarms devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Alarms devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.
If you require your Alarms device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label).
Domain Name System
Alarms devices use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Alarms device where the DNS server is on the network and the Alarms device communicates using UDP port 53.
DNS over HTTPS (DoH) is currently not supported.
Power
Some Alarms devices are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to them, or a PoE injector needs to be utilized. For specifics on power requirements, see the Alarms device’s datasheet.
Firewall settings
Alarms devices require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the devices to communicate with the general required endpoints.
These are the general domains to allow, applicable for all organization-regions:
If you prefer a more granular allowlist, you can add IP addresses, full FQDNs, and wildcard domains to your firewall rules based on the region where your devices are located.
Your region is selected when you create an organization in Command.
Region: United States
Region: Europe
All regions
BC51s in all regions require these endpoints:
BK21s in all regions require these endpoints:
BZ11s in all regions require these endpoints:
Last updated
Was this helpful?