Command Connectors can be configured with a static IP to ensure that they maintain consistent network communication without relying on dynamic IP allocation protocols, such as the Dynamic Host Configuration Protocol (DHCP).
Command Connectors support private IP addresses, as defined in RFC 1918. This means only private IP ranges specified in the RFC, such as 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, are compatible with the static IP configuration.
Before you begin
To configure a static IP address on a Command Connector, it must initially connect to Command and update to the latest firmware using DHCP. Once the update process is complete, you can configure a static IP.
Configuration
Only Site Admins can enable or modify static IP configurations.
In Verkada Command, go to All Products > Cameras
.Select a Command Connector to configure.
On the right, click the Settings
. Under General > Command Connector IP, click the dropdown and select Manual.
On Manual IP Settings, enter the static IP addressing information.
Click Save.
Recovery mechanisms
In case of any configuration mistakes or network changes, Command Connectors have a recovery mechanism. The Command Connector performs the following checks at regular intervals to ensure connectivity. In case any of these tests fail, it falls back to the DHCP operation.
Recovery Mechanism | How to Perform this Task |
On the subnet, verify there is no duplicate IP conflict | Send Address Resolution Protocol (ARP) requests for the configured Command Connector IP. If the Command Connector receives an ARP request, it considers the reply a duplicate IP conflict. |
Verify there is a default gateway | Send ARP requests for the configured gateway IP. If no reply is received by the Command Connector, the gateway is considered unreachable. |
DNS resolution is operational for Verkada domains | Perform Domain Name Server (DNS) lookups for Verkada domains. In case the Command Connector doesn't receive a response from any of the domains, this test fails. |
SSL/TLS sessions can be established with the required endpoints | Send HyperText Transfer Protocol Secure (HTTPS) requests to the Verkada endpoints required for Command Connector operation. In case the Command Connector is unable to perform a Transport Layer Security (TLS) handshake with any of the endpoints, or in case there is any error while performing this handshake, this makes the test fail. |
Endpoints for DNS tests
The following list of endpoints is used for DNS tests in US organizations, for other regions their equivalent endpoint will be used. For a full list of endpoints, see Video Security Network Settings.
api.control.verkada.com - TCP/443
vprovision.command.verkada.com - TCP/443
For TLS tests, only the first endpoint is used. In case the Command Connector is unable to establish a TLS connection with the api.control.verkada.com endpoint, it falls back to the DHCP operation.
Troubleshooting
If the Command Connector encounters any issues during these checks, it attempts to fall back to its default DHCP operation and perform the connectivity tests listed above.
If the DHCP connection fails, the Command Connector retries using the static IP configuration.
If the Command Connector fails to connect again while using its static IP configuration, it alternates between static IP and DHCP operations in exponential backoff increments, ranging from 20 seconds up to 1 hour.
If the Command Connector successfully connects to Verkada Command using DHCP, it continues to operate on DHCP until it is rebooted via Command or by power cycling the Command Connector.
Need more help? Contact Verkada Support.