The Site Gateway or camera has a zero config or APIPA IP address. This is an IP address in the 169.254.0.0/16 range.
An IP address in this IP range is used by a network device that is configured for DHCP but communication to the DHCP server has failed. As a result the device is unable to get an IP address lease from the DHCP server.
-
First verify whether the IP address on the device is statically assigned or uses DHCP.
You can verify the IP address assignment method from the Site Gateway settings:
-
Select Devices.
-
Select the more actions menu ( ... ) in the row for the device and select Edit.
-
Verify the assignment method specified in the Standalone Ethernet Port field.
-
-
If there is a DHCP sever on the network, investigate the following potential causes of the device failing to receive an IP address:
-
Network traffic from the Site Camera or Site Gateway is being blocked from getting to the DHCP server.
-
The server has no spare lease in the DHCP scope
-
The DHCP server is incorrectly configured
-
-
If there isn't a DHCP server on the network, set the gateway and camera to a static IP address on the local subnet. For more information, see Configure a Site Gateway to Connect to the Network Using a Static IP Address .
Note
You can also use this as a workaround for a DHCP issue but make sure you do not apply a static IP address that it is not within the DHCP scope or already in use.
Cameras are offline in the gateway because they have renewed their DHCP lease and got a different IP address.
Cameras configured to use DHCP will periodically renew their IP address with the DHCP server. Their new DHCP leased IP address will not always be the same as their old leased IP address. When this happens, the Site Gateway does not always recognize this change and fails to update the camera IP information in the dashboard. This leads to the camera being offline as the gateway is attempting to connect to the camera using the old leased IP address.
-
Run a camera discovery in the gateway.
The results from the camera discovery scan will show the new cameras that the gateway can see on the network. These will be the same cameras but with their newly leased IP addresses.
Note
If the gateway is at full capacity in terms of reaching the maximum number of permitted camera streams, you will not be able to run any additional camera discovery. In this case, please contact sites-support@samsara.com.
-
Update the camera IP addresses in the camera settings in the gateway.
In case of multiple cameras, you might be able to use the camera serial numbers available on the dashboard to determine which IP address belongs to which camera.
-
Save your changes.
If the same IP address is used for multiple cameras, the camera stream in the dashboard cycles between each camera with the same IP address.
Cameras must have a unique IP address unless deployed in the following scenarios:
-
You deploy multiple analog cameras through a network video recorder (NVR) that reports with the same IP address.
-
You deploy a camera with multiple streams—such as a quad camera—where the same IP address is shown for each stream.
-
Confirm whether your Site Cameras are configured with static IP addresses or if they are configured to receive an IP address using DHCP.
When the gateway is set up as a camera server, the gateway acts as a DHCP server to issue IP addresses.
-
For Samsara Site Cameras that receive static IP addresses, contact sites-support@samsara.com to update the IP address to eliminate any duplicates.
For third-party cameras that are issued static IP addresses, log into the web interface for the camera to make any IP address changes. Refer to the instructions provided by the camera manufacturer.
Comments
0 comments
Please sign in to leave a comment.