Verify Your Verkada Camera's Power and Network Configuration
If your Verkada camera is not powering up via PoE, the issue likely stems from a misconfigured network, insufficient power budget, or firmware incompatibility. Begin by confirming the camera is correctly registered in Verkada Command and that the switch port is delivering power. Enterprise deployments must ensure PoE standards (802.3af/at) are met, VLAN assignments are accurate, and the camera firmware is up to date.
Simple Verkada Checks Before Deep Troubleshooting
Before diving into advanced diagnostics, perform these 30-second checks:
- Check VMS Dashboard Status: In Verkada Command, navigate to Cameras → [device] → Status. Look for Power Negotiation Failed or No Power alerts.
- Verify PoE Link Light: Ensure the switch port shows a solid green light (not blinking or off) for PoE delivery.
- Ping the Camera IP: Open a terminal and run
ping [camera_ip]. A response indicates the camera is online but may not be receiving power. - Check Status LED: A solid red light on the camera indicates a power failure. A blinking green light suggests PoE negotiation is in progress.
- Power Cycle the Switch Port: Disable the port in the switch's management interface for 30 seconds, then re-enable it to force PoE renegotiation.
Diagnose Verkada Command Connectivity Issues
Check VLAN Assignment
Ensure the camera is assigned to a dedicated VLAN that allows Multicast/IGMP Snooping and has sufficient bandwidth. In Verkada Command, go to Network → VLAN Configuration and confirm the camera's VLAN matches the switch port's settings. For UK deployments with Virgin Media Hub 5x, ensure Modem Mode is enabled to avoid double NAT.
Validate PoE Budget
Access the PoE Budget section in Verkada Command → Network → Switch Status. Confirm that the switch port allocated to the camera has at least 15.4W (802.3at) available. If the budget is exceeded, reconfigure the switch or use a higher-wattage model. For CD62/CP62 cameras, ensure the switch supports 802.3at and is not in Power Saving Mode.
Check Firmware Channel
In Verkada Command, navigate to System → Firmware. Ensure the camera is on the Stable channel unless instructed otherwise. Staged rollouts can cause power failures if Firmware Rollback is not enabled. For CM62 models, check if Analytics Modules are consuming excessive power and disable them if necessary.
Verify ONVIF/RTSP Settings
Use the RTSP Stream Test Tool in Verkada Command → Cameras → [device] → Diagnostics. Enter the RTSP URL manually and confirm the stream is accessible. If the stream fails, check the camera's ONVIF Profile in the VMS platform and ensure it matches the camera's capabilities. For CB62 models, confirm 4K Resolution is enabled and the Bandwidth Monitor shows upload speeds above 5Mbps.
Use Device Health Dashboard
In Verkada Command, access the Device Health dashboard for the camera. Look for Power Negotiation Status and Cloud Connectivity indicators. If the camera shows Class 0 on the switch port, the port may be misconfigured. Ensure the switch port is set to Auto or 802.3at. For UK deployments with concrete block walls, consider using Wi-Fi 6 repeaters to avoid signal degradation.
Advanced Verkada Poe Not Troubleshooting
Perform Packet Capture
If basic steps fail, use the Packet Capture Tool in Verkada Command → Diagnostics. Filter for PoE Negotiation and RTSP Handshake packets to identify where the power delivery or video stream is failing. Look for LLDP or CPLD protocol errors that indicate switch port misconfiguration.
Re-register the Camera
For CD62/CB62 models, if the camera is not powering up and shows Offline in Verkada Command, the administrator must deregister the camera from the platform. Navigate to Cameras → [device] → Actions → Deregister. Wait 10 minutes, then re-provision the camera using a new serial number. Ensure the camera's MAC Address is not duplicated in the VMS database.
Check VMS Database Consistency
If the camera is registered but not powering up, run a Database Repair Tool in Verkada Command → System → Maintenance. This resolves inconsistencies in the VMS database that can prevent power negotiation. For large deployments, use the Bulk Camera Re-registration tool to refresh all devices simultaneously.
Escalate to Enterprise Support
If the camera remains unpowered, contact Verkada's enterprise support via help.verkada.com. Provide the Device Health dashboard, Packet Capture logs, and VLAN Configuration details. For UK customers, ensure the support ticket includes Building Regulations Part Q compliance checks if the camera is in a new-build property.
Root Causes of Verkada PoE Failures
PoE Budget Exhaustion
Enterprise switches often allocate power budgets across multiple devices. If the switch port shows Power Budget Exceeded, reconfigure VLANs or use a higher-wattage switch. For deployments with 10+ cameras, ensure the switch supports 802.3bt (PoE++).
VLAN Misconfiguration
Incorrect VLAN assignments can prevent PoE negotiation. In Verkada Command, confirm the camera's VLAN matches the switch port's configuration. For UK deployments with Virgin Media, ensure Modem Mode is enabled to avoid double NAT.
Firmware Incompatibility
Staged firmware rollouts can cause power failures if Rollback is not enabled. Ensure all cameras are on the Stable firmware channel. For CM62 models, disable Analytics Modules if the camera is not powering up.
UK-Specific Network Issues
UK ISPs often use single SSIDs for both 2.4GHz and 5GHz bands. For Verkada cameras requiring persistent internet, temporarily disable 5GHz mode during setup. In properties with 9-inch solid brick walls, use Wi-Fi 6 repeaters to avoid signal degradation.
Protecting Your Verkada Investment
Plan for PoE Budget Headroom
When deploying Verkada cameras, allocate 20% more power than the total required. For example, 10 cameras at 15.4W each require a 200W switch. Use the PoE Budget Calculator in Verkada Command → Network → Switch Status.
Implement Dedicated VLANs
Create a dedicated VLAN for Verkada cameras with QoS policies prioritizing video streams. Ensure the VLAN allows Multicast/IGMP Snooping and has sufficient bandwidth (minimum 5Mbps per camera).
Schedule Firmware Updates
Use the Firmware Channel in Verkada Command to schedule updates during off-peak hours. Enable Rollback for critical updates and test new firmware on a small subset of cameras before full deployment.
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.