Verify Your Verkada Camera's Network Configuration
If your Verkada camera is stolen but still registered in Verkada Command, your first priority is retrieving cloud footage and securing device health. This guide assumes your camera is enterprise-managed via Verkada Command and covers advanced diagnostics, cloud recovery, and prevention strategies. Root causes often involve PoE budget exhaustion, VLAN misalignment, or firmware incompatibility. The solution includes cloud footage retrieval, device deregistration, and anti-theft mounting recommendations.
Quick Fixes to Try First
Before diving into advanced diagnostics, perform these 30-second checks:
- Check VMS dashboard status: In Verkada Command, navigate to Cameras → [device] and verify if the camera is marked as 'offline' or 'unregistered'.
- Verify PoE link light: Ensure the switch port has a solid green LED, indicating successful PoE negotiation. A blinking or absent light suggests a power issue.
- Ping the camera IP: From the management server, ping the camera’s IP address to confirm basic network connectivity.
- Check status LED: For models like the CD62 Dome Camera, a steady blue light indicates normal operation; a red light may signal a critical error.
- Power cycle via PoE switch: Disable the switch port for 30 seconds, then re-enable it to reset the PoE link.
Verify Network Configuration
Check VLAN Assignment
Ensure the camera’s VLAN matches the switch port configuration. In Verkada Command, go to Cameras → [device] → Network Settings and cross-reference the VLAN ID with your switch’s port configuration. Use the Network Diagnostics tool in Verkada Command to automatically detect mismatches. If the VLAN is incorrect, update the switch port configuration to align with the camera’s assigned VLAN. This is critical in segmented enterprise networks where VLANs are used for security.
Validate PoE Budget
Access the PoE Monitor in Verkada Command under Settings → Network → Power Management. This tool displays real-time power consumption per port and total switch capacity. If a camera is offline due to insufficient power, reconfigure the switch to allocate more power or reduce the number of active devices on the same port. For high-resolution models like the CB62 Bullet Camera, ensure 802.3at (PoE+) compliance.
Check DHCP Lease
Navigate to Settings → Network → DHCP in Verkada Command and verify the camera’s IP address is within the correct subnet. A lease expiration or IP conflict may cause the camera to drop from the network. Renew the lease via the DHCP Renew button if necessary.
Diagnose Verkada Command Connectivity Issues
Use Device Health Dashboard
The Device Health dashboard in Verkada Command provides real-time status for each camera, including network connectivity, firmware updates, and cloud sync status. Look for alerts related to 'Unregistered' status, 'Firmware Pending', or 'Cloud Sync Failure'. If the camera is unregistered, re-provision it via the Add Camera wizard in Verkada Command.
Test RTSP Stream
For models like the CP62 PTZ Camera, test the RTSP stream URL directly using a media player like VLC. The URL format is typically rtsp://[camera_ip]:554/[stream_profile]. Ensure the stream profile is set to 'Main' in Verkada Command under Cameras → [device] → Video Settings. If the stream fails, check for ONVIF/RTSP configuration issues in Settings → Network → Streaming.
Troubleshoot Firmware Management
Check Firmware Channel
In Verkada Command, navigate to Cameras → [device] → Firmware and ensure the camera is set to the Stable channel unless testing new features. If an update is stuck, use the Firmware Rollback feature to revert to a previous version. For enterprise deployments, configure staged rollouts via Settings → Firmware Management to avoid widespread disruptions. Always test updates on a subset of devices before full deployment.
Use Staged Rollouts
In Settings → Firmware Management, enable staged rollouts to gradually deploy firmware updates across your network. This minimises the risk of widespread disruptions. Assign a subset of cameras to the 'Test' group and monitor their performance before rolling out to all devices.
Recover Cloud Footage After Theft
Access Cloud Storage
Log into Verkada Command and navigate to Settings → Storage → Cloud. Ensure cloud storage is enabled and verify the retention period. For stolen cameras, retrieve footage by selecting the camera in the Cameras section and using the Export Footage feature. Export options include time-based ranges and event-triggered recordings.
Report to Police with Serial Number
If the camera is stolen, immediately report the theft to local authorities. Provide the camera’s serial number, which is visible in Verkada Command under Cameras → [device] → Device Info. This serial number is critical for police investigations and insurance claims.
Advanced Troubleshooting
Packet Capture and Protocol Analysis
For persistent connectivity issues, use the Packet Capture feature in Verkada Command under Settings → Diagnostics. This tool captures network traffic between the camera and the management server, helping identify issues like multicast/IGMP snooping or VLAN tagging mismatches. Analyse the capture using Wireshark or similar tools to pinpoint the root cause.
VMS Database Consistency Check
If the camera is unregistered and re-provisioning fails, perform a VMS database consistency check. In Verkada Command, go to Settings → Database → Health Check and run a full scan. This identifies corruption or licensing issues that may prevent camera registration. Repair the database if necessary, ensuring all licences are valid and up to date.
Root Causes of Verkada Camera Issues
PoE Power Budget Exhaustion
Enterprise networks often face PoE budget exhaustion when multiple high-power devices (e.g. CB62 Bullet Camera) share the same switch. The PoE Monitor in Verkada Command helps identify overloaded ports. Reconfigure the switch to allocate more power or reduce the number of active devices on the same port. Ensure 802.3at (PoE+) compliance for 4K models.
VLAN Mismatch
VLAN misalignment is a common cause of connectivity failures in segmented networks. Use the Network Diagnostics tool in Verkada Command to automatically detect mismatches. If the VLAN is incorrect, update the switch port configuration to align with the camera’s assigned VLAN.
Firmware Incompatibility
Staged firmware rollouts may fail if the update is incompatible with the camera’s current configuration. Use the Firmware Rollback feature in Verkada Command to revert to a previous version. Always test updates on a subset of devices before full deployment.
Prevention and Long-Term Care
Enterprise Anti-Theft Mounting
Use Verkada’s anti-theft mounting kits for outdoor models like the CB62 Bullet Camera. These kits include tamper-resistant screws and brackets that make physical removal difficult. For indoor models like the CD62 Dome Camera, install cameras in high-traffic areas with limited access.
Network Best Practices
Implement dedicated camera VLANs and Quality of Service (QoS) policies to prioritise video traffic. Use SNMP monitoring to track PoE usage and network performance. Regularly audit your network for unused devices or unregistered cameras in Verkada Command.
Firmware Update Schedule
Establish a regular firmware update schedule in Verkada Command under Settings → Firmware Management. Enable automatic updates for critical patches and manually deploy feature updates during off-peak hours. Monitor the Device Health dashboard for any pending updates.
Full disclosure: we built scOS to address exactly this — the complexity of managing enterprise camera systems. scOS uses permanently powered cameras connected via ethernet.