Verify Your Verkada Camera's Network Configuration
If your Verkada camera's live view is not working, begin by confirming that the device is correctly integrated into your network. The issue could stem from VLAN misconfiguration, PoE power budget exhaustion, or incompatible firmware channels. Verkada's hybrid storage model relies on both local and cloud storage, so ensure that neither is full. Use Verkada Command's Network Diagnostics tool to verify switch port status, VLAN tagging, and PoE power allocation. This step is critical for enterprise deployments where multiple VLANs and subnets are common.
Quick Fixes for Verkada Live View Issues
Before diving into advanced diagnostics, perform these 30-second checks:
Check VMS Dashboard Status
Log into your VMS platform (e.g. Wisenet WAVE VMS or Avigilon Control Center) and confirm the camera is listed as online. If it's marked offline, check the Device Health tab in Verkada Command for any warnings.
Verify PoE Link Light
Ensure the switch port connected to the camera shows a solid green PoE link light. A blinking or absent light may indicate a power negotiation failure. For Verkada's CD62 Dome Camera, verify that the PoE switch supports 802.3at (Class 3) to avoid under-powering the device.
Ping the Camera IP
Open a command prompt and ping the camera's IP address. If it fails, the device may be unreachable due to network segmentation or firewall rules. Use Verkada Command's Network Diagnostics → DHCP Lease Check to confirm the camera has obtained a valid IP address.
Power Cycle via Switch Port
Disable and re-enable the switch port connected to the camera. This action forces a new PoE negotiation and can resolve transient connectivity issues. For CB62 Bullet Cameras, this step is particularly useful if the camera was recently added to the network.
Check Status LED
Observe the camera's front panel LED. A solid green light indicates normal operation, while a blinking red light may signal a firmware update or storage error. Use Verkada Command's Device Health → Storage Status to investigate further.
Diagnose Verkada Command Connectivity Issues
Check VLAN Assignment
In Verkada Command, navigate to Cameras → [device] → Network Settings. Ensure the camera's VLAN ID matches the switch port configuration. If the switch port is set to Access mode, it must be configured for the same VLAN as the camera. For Trunk mode ports, confirm that the camera's VLAN is allowed through the port. Use SNMP polling to cross-check switch port status and VLAN tagging compliance.
Validate PoE Budget
Access Network Diagnostics → PoE Budget in Verkada Command. Ensure the switch port's allocated power is sufficient for the camera's requirements. For Verkada's CP62 PTZ Camera, which consumes higher power, verify that the PoE switch supports 802.3at (Class 3) and that no other devices are over-subscribing the port's power budget.
Check Firmware Channel
Navigate to Cameras → [device] → Diagnostics → Firmware Update Status. If updates are pending, ensure the camera is registered to the correct firmware channel (stable or beta). Use staged rollout to deploy updates across subnets without disrupting live streams. If updates fail, check PoE power budget and switch port utilization via the Network Diagnostics tool. Reboot the camera after successful updates to apply changes.
Verify ONVIF/RTSP Settings
In Verkada Command → Cameras → [device] → Video Settings, confirm RTSP stream profiles match the VMS platform's requirements. Test the RTSP URL directly using a media player like VLC: rtsp://[camera_ip]:550/[stream_profile]. If the stream fails, check ONVIF profile compliance in Network Diagnostics → ONVIF Test. Ensure multicast/IGMP snooping is disabled on the switch if using multicast streams.
Check Cloud Connectivity
For cloud-managed cameras, ensure cloud connectivity is active in Network Diagnostics → Cloud Connection. If the camera is registered to a cloud-managed organisation, check that the cloud storage subscription is active and that the camera's GPS coordinates are correctly configured in Verkada Command.
Advanced Troubleshooting for Verkada Live View Failures
Perform Packet Capture
If basic steps fail, use a network analyser (e.g. Wireshark) to capture packets on the switch port connected to the camera. Look for RTSP handshake failures, ONVIF profile mismatches, or DHCP exhaustion. For Verkada's D80 Fisheye Camera, ensure that the VMS platform is configured to accept H.265 streams if the camera is set to this profile.
Repair VMS Database
If the camera is registered in the VMS but not appearing in live view, check the VMS database for inconsistencies. For Avigilon Control Center, use the Database Consistency Checker tool. For Wisenet WAVE VMS, run a Camera Re-registration process to refresh the device's metadata.
Escalate to Enterprise Support
If the issue persists, contact Verkada's enterprise support team. Provide them with the Device Health report, Network Diagnostics logs, and Firmware Update Status from Verkada Command. Include details about the VMS platform and switch configuration to expedite resolution. For large deployments, request a packet capture analysis and firmware rollback if a recent update caused the issue.
Root Causes of Verkada Live View Failures
Enterprise deployments often encounter PoE power budget exhaustion, VLAN misconfiguration, or VMS licensing conflicts. For Verkada's multisensor cameras, ensure that all sensor streams are correctly configured in the VMS. In the UK, Building Regulations Part Q may require additional network resilience, such as dedicated VLANs for surveillance traffic. GDPR retention policies can also impact live view performance if local storage is not configured to retain footage for the required period.
Prevention and Long-Term Care for Verkada Cameras
Schedule Firmware Updates
Use Verkada Command's Firmware Management tool to schedule updates during off-peak hours. For large deployments, implement staged rollouts to avoid disrupting live streams. Ensure that all cameras are registered to the correct firmware channel (stable or beta) based on your organisation's risk tolerance.
Monitor Network Health
Implement QoS policies on your network switches to prioritise RTSP and ONVIF traffic. Use SNMP monitoring to track switch port utilisation and PoE power allocation. For Verkada's cloud-managed cameras, ensure that cloud connectivity is active and that the GPS coordinates are correctly configured in Verkada Command.
Plan for PoE Budget Headroom
In enterprise environments, allocate 10-15% headroom for PoE power budget planning. This accounts for edge storage failover and cloud connectivity spikes. For Verkada's CP62 PTZ Camera, ensure that the PoE switch supports 802.3at (Class 3) to avoid under-powering the device.
Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.