Axis Storage Full? Enterprise Fix Guide for IT
When your Axis camera or NVR reports 'storage full', it often stems from misconfigured storage tiers, firmware incompatibilities, or insufficient network resources. This guide focuses on enterprise-specific tools like AXIS Camera Station and firmware channels to resolve the issue efficiently. By addressing VLAN misconfigurations, verifying PoE budgets, and leveraging advanced diagnostics, IT administrators can restore storage capacity without disrupting operations.
Quick Checks for Axis Storage Full Issues
Before diving into complex diagnostics, perform these 30-second checks:
- Verify VMS Dashboard Status: Confirm the camera is registered in your VMS (e.g. Verkada Command, Avigilon Control Center) and shows no storage alerts.
- Check PoE Link Light: Ensure the switch port’s PoE indicator is green. A Class 0 status indicates misconfigured port settings.
- Ping the Camera IP: Use
pingfrom the switch or VMS server to confirm network connectivity. - Inspect Status LED: A blinking red LED on the camera may indicate storage errors.
- Power Cycle via Switch: Disable the port on the managed switch for 10 seconds, then re-enable to reset the camera’s network stack.
Verify Network Configuration
Check VLAN Assignment
Axis cameras require dedicated VLANs to avoid bandwidth contention. In your switch’s management interface, confirm the camera’s VLAN is isolated from other traffic. If the camera is on a shared VLAN, create a separate VLAN with QoS prioritisation for video streams. In AXIS Camera Station, navigate to Device Health → Network to verify VLAN assignments match the switch configuration.
Validate PoE Budget
PoE budget exhaustion can indirectly cause storage issues if the camera enters a low-power state. Access your switch’s PoE Budget Monitor and confirm the camera’s power class (Class 3 for most Axis models). If the switch reports Class 0, reconfigure the port for 802.3af/at support. For managed switches like Cisco Catalyst or HP ProCurve, use LLDP or CDP to auto-negotiate PoE settings.
Confirm DHCP Lease Limits
Ensure the camera’s VLAN has a sufficient DHCP lease duration (typically 24 hours). If the lease expires, the camera may restart, causing temporary storage disruptions. In your DHCP server, verify the scope includes the camera’s IP range and has no address exhaustion.
Diagnose VMS Integration Issues
Re-Register the Camera
If the camera is unregistered in your VMS, it may not store footage. In AXIS Camera Station, go to Camera Management → Device Discovery and re-register the camera. For VMS platforms like Avigilon Control Center, ensure the camera’s RTSP Stream Profile matches the VMS’s expected resolution and bitrate. If the VMS shows a 'stream not found' error, check the RTSP URL in the camera’s Advanced Settings.
Check VMS Licensing
Storage exhaustion can occur if the VMS lacks sufficient licenses. In your VMS interface, confirm the camera is licensed and has enough storage quota. For Axis NVRs, ensure the Storage Tier Expansion Module is activated and the RAID configuration is optimal (RAID 5 or 6 for redundancy).
Manage Firmware Updates
Use Stable Firmware Channels
Outdated or incompatible firmware can cause storage issues. In AXIS Camera Station, open Firmware Management and ensure the camera is on the Stable Channel. Avoid beta firmware unless explicitly required. If a firmware update failed, use the Firmware Rollback feature to revert to a previous version. For enterprise deployments, enable Staged Rollout to update a subset of devices first.
Verify Firmware Compatibility
Always confirm firmware compatibility with your VMS platform. For example, Axis M5075-G PTZ cameras require firmware v5.x for full compatibility with Avigilon Control Center. If the VMS reports a 'device not compatible' error, check the Firmware Release Notes on Axis’s support portal.
Advanced Diagnostics
Run Storage Health Check
Use the Device Diagnostics tool in AXIS Camera Station to run a Storage Health Check. This identifies corrupted files, failed drives, or misconfigured storage tiers. If the check reports 'storage tier limits exceeded', adjust the Retention Period in Storage Configuration to align with organisational requirements.
Analyse Network Traffic with Packet Capture
For persistent storage issues, use the AXIS Network Diagnostic Tool to capture traffic between the camera and VMS. Look for RTSP stream drops or NFS/CIFS protocol errors. If the VMS is using NFS, ensure the server is configured for read-write access and has sufficient IOPS.
Factory Reset and Enterprise Support
Perform Model-Specific Factory Reset
If basic fixes fail, perform a factory reset. For AXIS M2036-LE: disconnect power, press and hold the control button while reconnecting power. Hold for 15-30 seconds until the status LED flashes amber. For AXIS M5075-G PTZ: press and hold the control button for 15-30 seconds until the LED flashes amber. After reset, re-configure the camera via AXIS Camera Station and re-register it in the VMS.
Escalate to Axis Enterprise Support
If issues persist, escalate to Axis Enterprise Support via their Support Portal. Provide logs from AXIS Camera Station Edge, the Network Health Check report, and any VMS error messages. For critical outages, request SLA-compliant support and ensure your organisation’s RMA process is ready for hardware replacement.
Root Causes and Enterprise Considerations
PoE Power Budget Exhaustion
Enterprise networks often face PoE budget exhaustion when multiple high-power devices (e.g. PTZ cameras) share a switch. Use PoE budget calculators to ensure the switch can support all devices. For example, a Cisco Catalyst 9300 with 802.3at support can power up to 24 Axis M5075-G PTZ cameras.
VMS Database Corruption
Storage exhaustion can occur if the VMS’s database is corrupted. In Avigilon Control Center, run a Database Consistency Checker to repair inconsistencies. For Axis NVRs, use the NVR Database Repair Tool in the Advanced Settings.
UK-Specific Considerations
In the UK, ensure compliance with GDPR retention policies and Building Regulations Part Q for surveillance systems. Storage tiers must align with legal requirements to avoid fines or data breaches.
Prevention and Long-Term Care
Schedule Firmware Updates
Implement a quarterly firmware update schedule using Staged Rollout in AXIS Camera Station. Monitor VMS health metrics via SNMP traps and NetFlow analysis to detect early signs of storage exhaustion.
Plan for PoE Budget Headroom
Allocate 10-15% headroom in your switch’s PoE budget for unexpected device additions. Use QoS policies to prioritise video streams and avoid bandwidth contention.
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
Enterprise camera lifecycles require strategic planning. Wired cameras (e.g. AXIS M2036-LE) typically last 5-8 years, while battery cameras degrade after 300-500 cycles. Replace NVR HDDs every 3-5 years with surveillance-rated drives (WD Purple/Seagate SkyHawk). For UK consumers, the Consumer Rights Act 2015 provides a 6-year right to repair (5 years in Scotland). Always document hardware failures to meet legal requirements.