Vivotek Missed Recordings: Enterprise Troubleshooting Guide
You're encountering gaps in video recordings from Vivotek cameras, but the system appears otherwise functional. This guide focuses on enterprise-specific diagnostics, including VAST Security Station tools, Smart VCA configuration, and firmware channel management. Root causes often involve network misconfigurations, VMS integration, or firmware incompatibility. Follow this structured approach to resolve the issue efficiently.
Quick Checks for Vivotek Missed Recordings
Before diving into advanced diagnostics, perform these rapid checks:
- Verify VMS Dashboard Status: Open VAST Security Station, navigate to Cameras → [device] → Status. Look for red indicators under Recording Health or Stream Connectivity.
- Check PoE Link Light: Inspect the switch port for the camera. A solid green light confirms successful PoE negotiation (Class 3). If it's amber or off, check the switch's PoE budget and cable integrity.
- Ping the Camera IP: From the NVR or management server, use
ping [camera_ip]to confirm basic network reachability. A 100% packet loss suggests a network or hardware issue. - Inspect Status LED: For models like the FD9391-EHTV, a blinking blue LED indicates normal operation. A red LED may signal a firmware update or configuration error.
- Power Cycle the Camera: For IB9391-EHT, disable the switch port, wait 10 seconds, then re-enable. This can resolve transient connectivity or configuration glitches.
Your Network Configuration Checks
Verify VLAN Assignment
Ensure the camera is assigned to the correct VLAN in VAST Security Station → Network Settings → VLAN Configuration. Incorrect VLAN assignments prevent the camera from communicating with the NVR or management server. Confirm the switch port is configured for the same VLAN and that Port Security or Storm Control features are not blocking traffic.
Validate PoE Budget
Access the switch's PoE Budget Tool (typically via the management interface). Confirm the camera's power consumption (e.g. FD9391-EHTV requires 15.4W) and ensure the switch port is not exceeding its Class 3 limit. If multiple cameras share a PoE budget, temporarily disable non-critical devices to free capacity.
Check DHCP Lease and Configuration
In VAST Security Station → Network → DHCP Status, confirm the camera has a valid lease and that the Default Gateway and DNS Server match the network's settings. A misconfigured gateway can prevent the camera from reaching the NVR or updating firmware.
Test Multicast/IGMP Snooping
If the camera uses multicast streams (e.g. for ONVIF or RTSP), disable IGMP Snooping on the switch. This feature can inadvertently block multicast traffic, leading to missed recordings. Navigate to Switch Port Settings → Multicast and set the mode to Disabled or Per-Port.
Resolve VMS Integration Failures
Confirm VMS Connection Settings
In the NVR (e.g. ND9541P), go to Camera Configuration → [device] → Connection Settings. Ensure the RTSP Stream URL matches the camera's configuration under Configuration → Streaming. For example, a typical URL is rtsp://[camera_ip]:554/cam/realtime. If the NVR uses ONVIF, confirm the Profile (e.g. Profile S) is supported by both the camera and NVR.
Re-Register the Camera in VAST
If the camera is unresponsive in the VMS, navigate to VAST Security Station → Cameras → [device] → Actions → Re-Register. This process refreshes the camera's connection and re-syncs configuration settings. Ensure the camera is powered on and connected to the network during re-registration.
Check VMS Licensing and Database Health
Access the NVR's System → License Status to confirm valid subscriptions for recording features. If the license is expired or incorrect, the NVR may stop recording. Use the VMS Database Repair Tool under Advanced Tools → Database Health to fix corruption that might prevent the NVR from storing footage.
Manage Firmware and Analytics Configuration
Ensure Firmware is Up to Date
In VAST Security Station → Device Management → Firmware Updates, select the Stable channel unless instructed otherwise. If updates are pending, ensure the camera has sufficient PoE budget and network connectivity. For staged rollouts, check Firmware Rollout Status to confirm all devices are updated. If a rollback is needed, use the Firmware History feature to revert to a previous version while preserving configuration settings.
Configure Smart VCA Rules
Open the camera's web interface and navigate to Configuration → VCA. Ensure Intrusion Detection, Loitering, and Line Crossing rules are enabled. Misconfigured rules may cause the camera to ignore motion events, leading to missed recordings. Adjust sensitivity thresholds based on the environment (e.g. higher sensitivity for low-light scenarios with SNV technology).
Verify Fisheye Dewarping Settings
For FE9391-EV models, access Configuration → Fisheye Settings and confirm the Mounting Type (ceiling, wall, floor) is correct. Incorrect mounting type settings can cause dewarping algorithms to misinterpret the video feed, leading to missed motion events. Test the dewarped view in real-time to ensure it aligns with the physical installation.
Your Enterprise Support and Diagnostics
Initiate Packet Capture
Use VAST Network Diagnostics → Packet Capture to analyze traffic between the camera and NVR. Filter for the camera's IP address and inspect for TCP resets, UDP packet loss, or latency spikes. If the NVR is not receiving streams, check the ONVIF Profile in the camera's web interface (Configuration → ONVIF) and ensure it matches the NVR's supported profiles.
Repair VMS Database Corruption
If the NVR is unresponsive, access the VMS Database Repair Tool under Advanced Tools → Database Health. This tool scans for inconsistencies in the recording database and attempts to repair them. If the repair fails, consider backing up the database and reinstalling the NVR software after resolving network or firmware issues.
Escalate to Enterprise Support
If all steps fail, contact Vivotek support via https://vivotek.zendesk.com. Provide the VAST System Health Check report, packet capture logs, and firmware channel status. For enterprise customers, escalate to the Vivotek Enterprise Support Tier and reference the RMA Process if hardware replacement is required.
Root Causes of Vivotek Missed Recordings
Common enterprise causes include:
- PoE Power Exhaustion: Multiple cameras on a single switch port may exceed the PoE budget, causing intermittent power failures.
- DHCP Scope Exhaustion: If the camera VLAN has no available IP addresses, the camera may fail to connect to the network.
- VMS Licensing Issues: Expired or incorrect licenses may prevent the NVR from storing footage.
- Firmware Incompatibility: Staged firmware rollouts may leave some cameras on outdated versions that fail to communicate with the NVR.
- UK-Specific Considerations: Double Glazing or Foil Insulation may block RTSP streams if the camera relies on WiFi. Ensure wired connections are used in such environments.
Vivotek Preventive Maintenance Guide
Schedule Regular Firmware Updates
Use VAST Security Station → Firmware Updates to schedule monthly checks. Ensure all cameras are on the Stable channel and that staged rollouts are tested in a controlled environment before deployment.
Monitor Network Health with SNMP
Enable SNMP Monitoring on the switch to track PoE usage, VLAN traffic, and port status. Set thresholds for latency, jitter, and packet loss to receive alerts before issues escalate.
Plan for PoE Budget Headroom
Allocate 20% extra PoE budget across switches to accommodate unexpected camera additions or firmware updates that increase power consumption.
Implement Dedicated Camera VLANs
Create a separate VLAN for cameras to isolate traffic from other network segments. Apply QoS Policies to prioritize video streams and prevent bandwidth-hogging applications from interfering with recordings.
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.