Verify Your Avigilon Camera's Recording Configuration
If your Avigilon cameras are failing to record, the issue likely stems from misconfigured storage settings, network policies, or firmware incompatibilities. Begin by validating the camera's integration with Avigilon Control Center and confirming storage destinations. Enterprise environments often encounter conflicts between VLAN assignments, QoS prioritisation, or mismatched firmware channels. Address these systematically to avoid prolonged downtime.
Quick Checks for Avigilon Recording Failures
Perform these 30-second checks before diving into advanced troubleshooting:
- Check VMS dashboard status: Open Avigilon Control Center and confirm the camera appears as online in the device list. A disconnected state may indicate a network or VMS integration issue.
- Verify PoE link light: Ensure the switch port's PoE indicator shows Class 3 or higher (for H6A models) or Class 4 (for H6A PTZ models). A Class 0 status suggests negotiation failure.
- Ping the camera IP: Use
ping <camera_ip>from the VMS server to confirm basic network connectivity. A dropped response may point to VLAN misconfiguration or firewall rules blocking traffic. - Check status LED: A solid amber light on the camera body indicates normal operation. A blinking amber light may signal a firmware update in progress or a configuration error.
- Power cycle via switch port: Disable and re-enable the switch port to force a network reinitialisation. This can resolve transient connectivity issues.
Diagnose VLAN and Network Configuration Issues
Check VLAN Assignment
Incorrect VLAN settings are a common root cause for Avigilon cameras failing to record. In Avigilon Control Center, navigate to Network → Camera Configuration and verify the camera's assigned VLAN matches the switch port's VLAN. Mismatched VLANs prevent the camera from communicating with the VMS server or storage appliance. Use Network Diagnostics in the management platform to test connectivity between the camera and the NVR. If a VLAN mismatch is confirmed, reconfigure the camera's VLAN via Device Settings → Network and ensure QoS policies prioritise video traffic on the camera VLAN.
Validate PoE Budget and Switch Configuration
Avigilon cameras require specific PoE power levels: H6A models use 802.3af/at (Class 3), while H6A PTZ models require 802.3bt (Class 4). Use the switch's PoE management interface to confirm the port is allocating sufficient power. If the switch port shows Class 0, ensure the camera's PoE settings match the switch's capabilities. For enterprise environments, allocate dedicated VLANs for cameras and apply QoS policies to prioritise video traffic.
Check DHCP Lease and IP Assignment
Avigilon cameras may fail to record if their IP address is outside the VMS server's subnet. In Avigilon Control Center, access Camera → Properties → Network and confirm the camera's IP is within the same subnet as the VMS server. If the camera is using a static IP, ensure it is not conflicting with another device on the network. Use DHCP Lease Check in the management platform to verify the camera's IP assignment and lease duration.
Resolve VMS Integration and Storage Issues
Confirm Storage Pool Assignment
Avigilon cameras may fail to record if they are assigned to an incorrect or full storage pool. In Avigilon Control Center, navigate to Camera → Properties → Recording Settings and verify the camera's storage destination matches the NVR or storage appliance's configuration. Use Storage Health Check in the management platform to identify failed drives or full capacity. If edge storage is enabled, confirm Edge Storage Failover is activated in Camera → Advanced Settings to prevent recording interruptions.
Validate VMS Licensing and Analytics Configuration
Avigilon's Unusual Motion Detection (UMD) requires a 2-3 week learning period to establish a baseline for normal scene activity. If UMD is disabled or the camera is in the learning phase, motion detection may not trigger recordings. Enable UMD in Camera → Properties → Analytics and avoid major scene changes during the learning period. For real-time processing, ensure Appearance Search is licensed and the AI appliance is online in Camera → Advanced Settings.
Troubleshoot Firmware and Update Management
Check Firmware Channel and Rollout Status
Avigilon cameras may fail to record if they are on an incompatible firmware channel or if an update is pending. Access Firmware Management in Avigilon Control Center and confirm the camera is on the Stable channel unless testing beta features. For staged rollouts, check Rollout Status in the management platform to ensure all cameras have received the latest firmware. If an update fails, use Firmware Recovery Mode by pressing the factory reset button for 30 seconds while the camera is connected to the network. Reapply the update via the management platform.
Verify RTSP Stream Health and ONVIF Profile
Use Network Diagnostics in Avigilon Control Center to test RTSP stream health. Check ONVIF Profile compatibility in Camera → Properties → Streaming and ensure the camera is using Profile S for maximum resolution. If RTSP fails, manually test the stream URL in a browser: rtsp://<camera_ip>:554/Streaming/Channels/101. Confirm Authentication Mode in the camera's network settings matches the VMS configuration.
Advanced Diagnostics and Enterprise Support
Perform Packet Capture and Protocol Analysis
If basic troubleshooting fails, use Packet Capture in Avigilon Control Center to analyse network traffic between the camera and VMS server. Look for dropped packets, authentication failures, or misconfigured ports. If the issue persists, escalate to enterprise support with logs from Device Health, Storage Health Check, and Network Diagnostics.
Escalate to Avigilon Enterprise Support
If the camera continues to fail recording after exhausting all troubleshooting steps, contact Avigilon's enterprise support team. Provide them with the Device Health report, Firmware Rollout Status, and Storage Health Check results. Include details about the camera model (e.g. H6A PTZ, H4 Pro 7K) and any recent network changes. Enterprise support can guide you through RMA processes or firmware rollback procedures.
Root Causes of Avigilon Recording Failures
Enterprise environments often face Avigilon recording failures due to PoE budget exhaustion, VLAN misconfigurations, or incompatible firmware channels. For example, a 24-port switch may fail to power multiple H6A PTZ cameras if the PoE budget is not allocated correctly. Similarly, a mismatch between the camera's ONVIF profile and the VMS server's expectations can cause RTSP stream failures. Ensure all cameras are on the Stable firmware channel and that QoS policies prioritise video traffic on the camera VLAN.
Prevention and Long-Term Maintenance
Schedule Firmware Updates and VMS Health Checks
To prevent Avigilon recording failures, schedule firmware updates during off-peak hours and monitor VMS health via Device Health in Avigilon Control Center. Use Storage Health Check regularly to identify failed drives or full capacity before they impact recording. Allocate dedicated VLANs for cameras and apply QoS policies to prioritise video traffic.
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.
Replacement Decisions for Avigilon Cameras
Avigilon wired cameras typically last 5-8 years, while battery-powered models degrade after 3-5 years. Surveillance-rated HDDs in NVR systems last 3-5 years, and microSD cards in cameras 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. If troubleshooting exceeds 30 minutes and basic fixes fail, consider hardware replacement.