The Command Connector enables organizations to integrate legacy non-Verkada camera feeds into the Verkada ecosystem. This article outlines various troubleshooting steps that will help narrow down issues that might come up when setting up the connector with non-Verkada devices.
The following diagram outlines a typical setup where the Command Connector bridges non-Verkada camera devices into the Command platform to manage footage and supported features from a centralized platform.
The Command Connector has 2 RJ-45 Ethernet Interfaces. Only connect one of the interfaces to your network. Connecting both interfaces could lead to switching loops.
Command Connector troubleshooting
Verify the Command Connector is connected to an AC power source and the organization's network via an Ethernet cable. Ethernet connectivity is currently limited to one port. Ensure that only one Ethernet cable is connected to the available interfaces.
What happens if a Command Connector is offline?
What happens if a Command Connector is offline?
If a Command Connector is offline, it could have issues reaching the Verkada cloud.
Validate the power source: Disconnect the Ethernet cable and physically power cycle the device to see if it will connect. If not, try connecting the Command Connector to a known working power source.
Validate the IP address: Verify the Command Connector has a local IP address from your Dynamic Host Configuration Protocol (DHCP) server. You can create an IP reservation with the device's Media Access Control (MAC) addresses. MAC addresses are listed on the top of each Command Connector and on the Devices page.
Validate that the Command Connector is reachable: Try to ping the Command Connector’s IP address, replies are expected.
If the Command Connector is on a network behind a firewall, certain endpoints need to be allowed to stream non-Verkada cameras. See Command Connector Network Settings for more information.
What happens if a storage drive fails?
What happens if a storage drive fails?
Reach out to Verkada support for assistance if a hard drive experiences a failure.
How do I verify communication between the Command Connector and non-Verkada cameras?
How do I verify communication between the Command Connector and non-Verkada cameras?
Verify that the Command Connector and the non-Verkada camera are connected on the same LAN. Then you can connect a computer to the same VLAN or port the Command Connector will use. Ping the camera's IP address to test communication. Replies from the camera are expected.
Non-Verkada camera troubleshooting
Verify the Command Connector is online and fully operational before adding non-Verkada cameras.
Why can't I add my non-Verkada camera to the Command Connector?
Why can't I add my non-Verkada camera to the Command Connector?
Check the hardware compatibility list to verify that your non-Verkada camera is compatible with the Command Connector. You can make a request for hardware compatibility at the bottom of the page if your camera is not on the list.
The user profile adding the cameras must be an Org Admin and a Site Admin for the site the Command Connector is in.
If a camera is not found via network discovery, try uploading the camera to the Command Connector via CSV import and ensure that both the Command Connector and the non-Verkada cameras can communicate on the same LAN.
If you observe any credential errors, ensure that the username of the non-Verkada camera is an administrator.
Why is my Non-Verkada camera not connecting to the Command Connector?
Why is my Non-Verkada camera not connecting to the Command Connector?
Verify the camera has been activated by following the vendor-specific instructions to activate the camera and assign credentials. Most vendors have a default IP address that the activating device (laptop/desktop) must be on to activate and assign an IP address to the camera.
After activating the device, validate that the camera stream is accessible locally by logging into the camera via its IP address.
Open a new browser window, and navigate to the camera via IP address by typing http://<camera_ip>.
Enter the credentials that were set up during camera activation or any known administrator credentials.
Ensure that the camera is on ONVIF Profile S and uses H.264 for video encoding.
After logging into the camera, ensure that the camera is configured with a static IP or a DHCP reservation.
If the camera IP changes at any point, the Command Connector won't be able to reach the camera. This will cause streaming and recording from the camera to stop.
The Verkada Command Connector is not an ONVIF conformant device. Any references to ONVIF in this article pertain solely to non-Verkada ONVIF conformant cameras.
Need more help? Contact Verkada Support.