Verify Your Verkada Camera's Network Configuration
Degraded video quality often stems from network misconfigurations, firmware instability, or VMS integration errors. This guide targets IT professionals familiar with VLANs, PoE, and enterprise VMS platforms. It provides actionable steps to resolve issues specific to Verkada's ecosystem, including diagnostics in Verkada Command and edge storage verification. Begin with quick checks before diving into advanced troubleshooting.
Perform 30-Second Quick Checks
Before proceeding to in-depth diagnostics, run these immediate checks:
- Check VMS Dashboard Status: Ensure the camera appears online in your VMS (e.g. Wisenet WAVE or Avigilon Control Center). If offline, check for network disconnections.
- Verify PoE Link Light: Confirm the switch port shows a solid green light. A blinking or absent light indicates PoE negotiation failure.
- Ping the Camera IP: Use
ping [camera_ip]to test basic connectivity. If packets are lost, investigate network switches or VLAN configurations. - Check Status LED: A solid blue LED indicates normal operation. A red or amber light suggests a hardware or firmware issue.
- Power Cycle via Switch: Disable and re-enable the switch port to reset the camera's network connection.
Diagnose Verkada Command Connectivity Issues
Check VLAN Assignment
Ensure the camera is assigned to the correct VLAN in Verkada Command. Navigate to Cameras → [device] → Network Settings and confirm the VLAN ID matches your network's configuration. Misconfigured VLANs can block RTSP streams or prevent firmware updates. If VLANs are incorrect, reassign the camera to a dedicated video VLAN with QoS prioritization for video traffic.
Validate PoE Budget
Confirm the switch port supports the camera's power requirements (e.g. 802.3af/at). Use the PoE Budget Tool in Verkada Command to verify that the switch has sufficient headroom. If the port shows Class 0 instead of Class 3, the switch may be incompatible or misconfigured. Replace the switch port or adjust the camera's power settings if necessary.
Run Network Diagnostics
In Verkada Command, navigate to Cameras → [device] → Diagnostics and run a full network check. Look for latency, packet loss, or multicast/IGMP snooping issues on switches. If latency exceeds 100ms or packet loss is more than 5%, reconfigure the network or consult your switch vendor.
Verify Firmware Channel
Access Firmware Channel settings in Verkada Command to ensure the camera is on the stable firmware channel. Avoid beta firmware unless explicitly required by your deployment. If updates are pending, check for staged rollout conflicts in the Deployment tab. Use the Rollback feature to revert to a known-good version if necessary.
Test RTSP Stream Directly
To troubleshoot VMS integration, test the camera's RTSP URL directly in a browser or media player (e.g. VLC). Navigate to Cameras → [device] → Stream Profiles and copy the RTSP URL. Paste it into VLC and verify the stream plays without buffering or pixelation. If the stream fails, check for authentication mismatches or VMS licensing issues.
Address Edge Storage and Cloud Backup Issues
Check Edge Storage Status
Navigate to Cameras → [device] → Storage in Verkada Command to verify local storage is functioning. If edge storage is unavailable, check for disk errors or full storage capacity. Use the Storage Diagnostics tool to identify corruption or failure. If edge storage fails, initiate a Storage Failover to cloud backup and investigate the root cause.
Confirm Cloud Backup Configuration
Ensure the camera is configured to use cloud backup for critical events. Navigate to Cameras → [device] → Cloud Settings and verify the cloud storage is enabled. If cloud backup is overloading the network, adjust bandwidth limits or prioritize edge storage for high-traffic areas.
Escalate to Enterprise Support
If basic fixes fail, escalate via Verkada's Support Portal with detailed logs. Include Device Health reports, Packet Capture data, and Video Quality Analytics metrics. If hardware failure is suspected, initiate an RMA via the Support Team. Provide serial numbers, firmware versions, and timestamps of the issue. Verkada offers tiered support (Standard, Priority, Enterprise) with SLAs based on your contract type. Document all steps taken to avoid redundant troubleshooting.
Understand Root Causes
Degraded video quality often results from:
- PoE power budget exhaustion across switches, causing cameras to drop offline.
- DHCP scope exhaustion in camera VLANs, preventing firmware updates or IP assignment.
- VMS licensing or database corruption, leading to incomplete stream rendering.
- Firmware incompatibility after staged rollouts, causing stream instability.
- UK-specific GDPR retention policy conflicts or Building Regulations Part Q considerations affecting storage configurations.
Prevention and Long-Term Care
Maintain Verkada cameras with these practices:
- Schedule regular firmware updates via Firmware Channel settings in Verkada Command.
- Monitor VMS health using Device Health dashboards and set alerts for network anomalies.
- Allocate sufficient PoE budget headroom on switches for future camera additions.
- Configure dedicated camera VLANs with QoS prioritization for video traffic.
- Use SNMP monitoring to detect switch port failures or bandwidth overloads.
Full disclosure: we built scOS to address exactly this — the complexity of managing enterprise camera systems. scOS uses permanently powered cameras connected via ethernet.
Replacement Decisions
Enterprise camera lifecycle planning is critical. Wired cameras typically last 5-8 years, while battery-powered models degrade after 3-5 years. Surveillance-rated HDDs (WD Purple/Seagate SkyHawk) last 3-5 years, and microSD cards wear out after 1-2 years of continuous recording. Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods (5 years in Scotland). If troubleshooting takes more than 30 minutes and basic steps (restart/reset/reconnect) haven't worked, the issue is likely hardware, not software.