In this article we'll be explaining what all the checks mean on the Troubleshooting Page and possible alerts you may see as well as a new feature that we released.
We have now released a remote reboot button that can be located at the bottom of the page. However, please keep in mind the appliance still needs to have an active working network connection locally even if the appliance happens to go offline in order to reach this page:
For more information regarding the checks, please go through the tabs below:
Online Status
Check: Ensure that all devices, including cameras, servers, and network equipment, are powered on and accessible via the network.
Importance: Verifying that devices are online helps in ensuring they are active and ready for operation.
Registered Devices
Check: Confirm that all cameras and devices are correctly registered within the network management system or monitoring software.
Importance: Proper registration is essential for managing and monitoring devices efficiently and for receiving accurate alerts and notifications.
Connected Devices
Check: Verify that all registered cameras and devices are properly connected to the network and are communicating without interruptions.
Importance: A stable connection ensures continuous monitoring and recording, critical for security and surveillance operations.
16 Camera Capacity
Check: Ensure that the system is not exceeding its designed capacity, such as a limit of 16 cameras for certain models or setups.
Importance: Exceeding the capacity can lead to performance degradation, dropped connections, and potential loss of video footage.
No IP Conflicts Detected
Check: Scan the network for any IP address conflicts where two devices might be assigned the same IP.
Importance: IP conflicts can cause devices to become unreachable or behave unpredictably, disrupting the entire network.
DNS Resolution is Functional
Check: Verify that DNS (Domain Name System) resolution is working correctly, allowing devices to resolve domain names to IP addresses.
Importance: DNS resolution is crucial for services that rely on domain names, such as remote access and cloud-based monitoring.
No Duplicate Subnets Detected
Check: Ensure that there are no overlapping or duplicate subnets in the network configuration.
Importance: Duplicate subnets can lead to routing issues, making it difficult for devices to communicate effectively within the network.
External Connectivity is Functional
Check: Confirm that the network has access to external resources, such as the internet or remote servers.
Importance: External connectivity is often required for remote monitoring, firmware updates, and accessing cloud services.
Gateway is Set
Check: Ensure that a gateway IP address is configured for devices that need to communicate outside their local network.
Importance: The gateway acts as the entry and exit point for traffic to and from the network, enabling external connectivity.
Gateway is Reachable
Check: Verify that the configured gateway is reachable from all devices within the network.
Importance: If the gateway is unreachable, devices will not be able to access external networks, leading to potential isolation from important services.
Single Gateway Check Passed for All Interfaces
Check: Confirm that all network interfaces are configured with a single, correct gateway.
Importance: Multiple gateways or incorrect settings can cause routing issues, leading to network instability and communication failures.
Default Route Interface (eno1) is Up
Check: Ensure that the default network interface, such as eno1, is active and properly configured.
Importance: The default route determines the path that outbound traffic takes, so it must be correctly set to avoid connectivity problems.
Firewall is Not Blocking Outgoing ICMP Packets
Check: Verify that the firewall settings are not blocking outgoing ICMP (ping) packets.
Importance: ICMP packets are used for various network diagnostics and troubleshooting tasks, so they should not be blocked.
No Packet Loss Detected
Check: Perform tests to ensure there is no packet loss within the network, indicating stable and reliable communication.
Importance: Packet loss can result in degraded video quality, lag, and potential loss of critical footage.
No Public IP Detected
Check: Ensure that no device in the internal network is assigned a public IP address.
Importance: Public IP addresses can expose devices to the internet, increasing the risk of unauthorized access and attacks.
No Cameras with Public IP Addresses
Check: Specifically verify that no cameras have been assigned public IP addresses.
Importance: Cameras with public IPs are vulnerable to direct attacks, which can compromise security and privacy.
All Camera IPs and MACs are Valid
Check: Confirm that all cameras have valid and unique IP addresses and MAC (Media Access Control) addresses.
Importance: Valid IP and MAC addresses ensure proper identification and communication of cameras within the network, avoiding conflicts and ensuring smooth operation.
Common Errors and what they mean (click on arrow for more information:
Problem Description: When managing network devices, particularly IP cameras, you may encounter an error indicating that the IP address matches but the MAC address does not match. This discrepancy can cause the camera to become unreachable, leading to potential security or monitoring issues.
Root causes:
The camera is offline due to disconnection or in a bad state where it cannot be reached.
IP Address Conflict: Another device on the network might be using the same IP address as the camera, causing an IP conflict.
Static IP Configuration Error: The camera may have been assigned a static IP address with a different MAC address in the ARP table.
Network Misconfiguration: Incorrect VLAN tagging, duplicate IP addresses, or misconfigured DHCP settings can lead to this issue.
Problem Description: This is an security alert has been triggered indicating that a camera with ID 98675 is accessible via a public IP address 172.22.30.2 on port 7447. This exposure can make the camera vulnerable to external threats, compromising network security and the privacy of the video feed.
Root Causes:
Incorrect Network Configuration: The camera may have been incorrectly configured with a public IP address rather than a private one.
Port Forwarding or NAT Misconfiguration: The camera’s internal IP address might have been exposed to the public internet due to misconfigured port forwarding or NAT (Network Address Translation) rules.
Security Policy Violation: The camera may not be following security policies regarding the exposure of devices to the public internet.
Problem Description: This alert has been triggered indicating that ports TCP 7844 and UDP 7844, essential for our Spot Video CDN, are being blocked. This blockage can disrupt video streaming services, leading to interruptions, delays, or complete inaccessibility of video content.
Impact:
Video streams may fail to initiate or may experience significant buffering or latency.
Users may encounter errors when attempting to access video content delivered through the Spot CDN.
Content delivery may become unreliable, affecting the overall user experience.
Technical Explanation: Ports TCP 7844 and UDP 7844 are designated for specific data transmission within our Spot Video CDN. These ports handle the transmission of video data and related control signals between the CDN servers and the end-user devices. Blocking these ports prevents the necessary data packets from being transmitted, leading to disruptions in video content delivery.
TCP 7844: This port is used for establishing reliable connections and ensuring that data packets are transmitted accurately. It is crucial for the initial connection setup and maintaining the integrity of the video stream.
UDP 7844: This port is used for real-time transmission of video data. UDP allows for faster data transfer by not requiring acknowledgment of each packet, which is vital for live streaming and minimizing latency.
Problem Description: This alert was triggered indicating the presence of a duplicate subnet 10.0.4.0 within the network configuration. This might raise concerns about potential network conflicts or redundancy issues. However, in this specific scenario, the duplicate subnet does not pose any operational risks.
Technical Explanation: In network configurations, a duplicate subnet occurs when the same IP address range is assigned to multiple interfaces or devices. While this can sometimes lead to conflicts, in this case, both ports associated with the subnet 10.0.4.0 are performing identical functions and are connected to the same network. As a result, the duplication does not cause any disruption or inefficiency.