Mobotix Storage Full? Enterprise Fix Guide

Address Mobotix Storage Full Issues for Enterprise Users

Storage exhaustion on Mobotix cameras can disrupt critical surveillance workflows. This guide focuses on advanced diagnostics using Mobotix-specific tools like MxManagementCenter and MxThinClient. Root causes often include misconfigured storage tiers, outdated firmware, or insufficient capacity planning. The solution involves verifying storage allocation, enabling automatic overwrite, and leveraging enterprise-grade diagnostics.

Quick Fixes for Mobotix Storage Full

Perform these checks immediately if your Mobotix camera is reporting storage full:

• Check VMS Dashboard Status: In MxManagementCenter, navigate to Device Health → Storage Utilisation. Look for red alerts indicating full capacity.
• Verify PoE Link Light: Ensure the switch port is providing stable power (802.3af/at) and that the camera’s LED indicates a healthy connection.
• Ping the Camera IP: Use ping [camera_ip]`` to confirm network reachability. If the camera responds but shows storage full, the issue is likely local to the device.
• Power Cycle via Switch: Disable the switch port for 30 seconds, then re-enable it to reset the camera’s network stack.
• Check Status LED: A blinking red LED on the camera housing may indicate storage errors. Refer to the Event Log in MxManagementCenter for details.

Deep Troubleshooting for Mobotix Storage Full

1. Verify Storage Tier Configuration in MxManagementCenter

Storage tier limits can cause unexpected fullness if not properly managed. Follow these steps:

• Open MxManagementCenter and select the affected camera.
• Navigate to Storage Configuration → Storage Tier Limits.
• Confirm that the camera is assigned to the correct storage tier (e.g. local SD card, network-attached storage).
• If the tier is full, delete old footage via the Event Log or configure Automatic Overwrite Rules (e.g. retain 7 days of footage, overwrite older content).
• For network-attached storage, ensure the NAS is accessible and the camera has write permissions.

2. Use MxThinClient Diagnostics to Analyse Storage Utilisation

MxThinClient diagnostics provide granular insights into storage health:

• Connect to the camera via SSH or the MxThinClient interface.
• Run the Storage Utilisation Report command: mxdiag storage report.
• Review the output for fragmented files, failed writes, or partition-specific errors (e.g. /var/media full).
• If the report identifies a specific partition issue, reformat it using the Storage Partition Tool in MxManagementCenter.

3. Configure Edge Storage Failover

Edge storage failover ensures continuity if primary storage fails:

• In MxManagementCenter, go to Storage Configuration → Edge Storage Failover.
• Enable the feature and designate a secondary storage location (e.g. local SD card, alternative NAS).
• Test the failover by simulating a primary storage failure (e.g. disconnect the NAS) and confirm the camera switches to the secondary storage automatically.

4. Check Firmware Channel and Rollback if Necessary

Firmware incompatibility can cause storage mismanagement:

• In MxManagementCenter, navigate to Firmware Management → Firmware Channel.
• Ensure the camera is on the stable channel unless testing a beta version.
• If a recent firmware update caused the issue, perform a firmware rollback using the Staged Rollout feature.
• Confirm the rollback by checking the Event Log for firmware-related errors.

5. Validate ONVIF/RTSP Stream Settings

Misconfigured stream profiles may lead to unexpected storage usage:

• In MxManagementCenter, go to Camera Settings → ONVIF/RTSP.
• Verify that the RTSP Stream URL matches the camera’s ONVIF Profile (e.g. rtsp://[camera_ip]:554/cam/realmonitor?channel=1&subtype=0).
• If the VMS platform (e.g. Wisenet WAVE) is misconfigured, re-register the camera and reapply the correct stream profile.
• Check for license limitations in the VMS that might restrict storage allocation.

Advanced Fixes for Persistent Mobotix Storage Issues

If basic troubleshooting fails, consider these steps:

• Factory Reset: For models like the MOBOTIX M73, remove the housing cover and press the reset button for 10 seconds. For the MOBOTIX MOVE SD-340-IR PTZ, access the maintenance port and press the reset button for 15 seconds.
• Packet Capture: Use Wireshark to capture traffic on the camera’s VLAN and check for storage-related errors in the RTSP/ONVIF protocol.
• VMS Database Repair: If the VMS platform (e.g. Wisenet WAVE) is reporting storage full, run a Database Consistency Check in the VMS settings.
• Escalate to Mobotix Support: Provide the Event Log, Storage Utilisation Report, and firmware version. Mobotix support can guide you through advanced diagnostics or initiate an RMA process.

Root Causes of Mobotix Storage Full Issues

Common causes include:

• PoE budget exhaustion on the switch port, leading to unstable power and storage errors.
• DHCP scope exhaustion in the camera’s VLAN, preventing the camera from acquiring an IP address.
• VMS licensing issues that restrict storage allocation or overwrite rules.
• Firmware incompatibility after a staged rollout, causing storage mismanagement.
• UK-specific GDPR retention policy conflicts or Building Regulations Part Q requirements that limit storage duration.

Protecting Your Mobotix Investment for Mobotix Storage

Implement these practices to avoid future issues:

• Schedule firmware updates during off-peak hours using the Staged Rollout feature in MxManagementCenter.
• Monitor VMS health via SNMP traps and configure alerts for storage thresholds.
• Plan PoE budget headroom to accommodate future camera additions.
• Use dedicated camera VLANs with QoS policies to prioritise storage-related 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.