Fortinet white logo
Fortinet white logo

Administration Guide

Connecting cameras to a DHCP server and FortiRecorder

Connecting cameras to a DHCP server and FortiRecorder

You can use this scenario if you already have an existing network with a DHCP server where you will install your FortiRecorder, cameras, and access control system (ACS). Often the PoE switch is connected to an existing router, and an existing DHCP server gives IP addresses to devices on the subnet.

The cameras get network settings from your DHCP server, but FortiRecorder does not. Like any server, FortiRecorder uses a static IP address so that its GUI or CLI can always be reached at the same network address.

Caution

For best performance and security:

  • Isolate cameras and ACS devices from the building's LAN, on a network separate from the building's LAN. Only FortiRecorder should be able to control the cameras. Don't connect other devices — especially untrusted computers — to the surveillance network.

    If the PoE switch is connected to an existing router or firewall such as FortiGate — especially if it connects to the Internet — use policies and VPNs that only allow authorized access.

  • Dedicate a port on FortiRecorder for camera connections only. Network bandwidth should be consistently available to cameras. (For example, cameras may use port2, while remote storage (NAS) is on port3, etc.)

local deployment with DHCP server

  1. Use Ethernet cables to connect your DHCP server (and router, if any) to your power-over-Ethernet (PoE) switch.

    Your DHCP server must have a range of IP addresses (pool) that is larger than all of the devices that you will connect.

  2. Use Ethernet network cables to connect the cameras to the switch.

    Caution

    If you connected the cameras too soon, before a DHCP server was available, then they are using a default IP address. The default address will not work with your network. To fix this, unplug the cameras and then plug them in again. This reboots the cameras and requests a correct IP address from the DHCP server.

  3. On your DHCP server, create a reservation for each camera so that it always gets the same IP address.

    Tooltip

    Fortinet strongly recommends to either:

    • configure your cameras with a static IP address (see Address), or
    • configure your DHCP server with lease reservations and then update the camera's Address with its current IP address

    Without reservations, the IP address provided by the DHCP server might appear to work initially, but later, when the DHCP lease expires, the DHCP server might change the IP address of the camera. DHCP servers do not notify FortiRecorder about the camera's new dynamic IP address. FortiRecorder tries to detect IP address changes with mDNS probes, but some networks do not allow this. During this time, FortiRecorder will try to control the camera at its old IP address. This does not work. Connections with that camera will be broken and all video from that camera could be lost during that interruption.

  4. Use Ethernet network cables to directly connect port1 of FortiRecorder to your computer.

    Do not put your switch between them yet. FortiRecorder network settings are not configured yet.

  5. Temporarily change your computer's IP address to be 192.168.1.98 with subnet 255.255.255.0. (If your computer has a static IP address, write it down so that you can restore the settings later.) Steps vary by whether you use Apple macOS, Linux, or Microsoft Windows.

    Alternatively, you can use a different IP address, but it must be on the same subnet as the default IP address of FortiRecorder port1: 192.168.1.0/24.

  6. On your computer, open a web browser and go to:

    https://192.168.1.99

    Log in with the name admin and no password.

  7. Change the password. For details, see Setting the "admin" account password.

  8. Configure port1:

    1. Go to System > Network > Interface.

    2. Select port1. Click Edit.

    3. Enable Discover cameras on this port.

    4. In IP/Netmask, enter the IP address and netmask that FortiRecorder will have on your network.

      Caution

      Do not use one of the range of IP addresses that the DHCP server assigns to cameras, computers, etc. (This can cause IP address conflict error messages.)

    5. Click OK.

  9. Change your computer's IP address and subnet back to its original settings.

  10. Unplug the Ethernet cable between your computer and FortiRecorder port1, and then plug them both into the switch.

  11. In your web browser, go to the new IP address of FortiRecorder. Log in.

  12. Discover and configure the cameras:

    1. Go to Camera > Configuration > Camera.

    2. Click Discover.

      After several seconds, a list of cameras appears.Newly discovered cameras are highlighted in yellow, and their Status column displays Not Configured.

    3. Double-click each camera to adjust its settings. For details, see Configuring cameras.

      Repeat this step for all cameras.

  13. To verify that FortiRecorder is able to receive video from the camera, go to Monitor > Video > Video. You should be able to see the camera's live video feed.

Connecting cameras to a DHCP server and FortiRecorder

Connecting cameras to a DHCP server and FortiRecorder

You can use this scenario if you already have an existing network with a DHCP server where you will install your FortiRecorder, cameras, and access control system (ACS). Often the PoE switch is connected to an existing router, and an existing DHCP server gives IP addresses to devices on the subnet.

The cameras get network settings from your DHCP server, but FortiRecorder does not. Like any server, FortiRecorder uses a static IP address so that its GUI or CLI can always be reached at the same network address.

Caution

For best performance and security:

  • Isolate cameras and ACS devices from the building's LAN, on a network separate from the building's LAN. Only FortiRecorder should be able to control the cameras. Don't connect other devices — especially untrusted computers — to the surveillance network.

    If the PoE switch is connected to an existing router or firewall such as FortiGate — especially if it connects to the Internet — use policies and VPNs that only allow authorized access.

  • Dedicate a port on FortiRecorder for camera connections only. Network bandwidth should be consistently available to cameras. (For example, cameras may use port2, while remote storage (NAS) is on port3, etc.)

local deployment with DHCP server

  1. Use Ethernet cables to connect your DHCP server (and router, if any) to your power-over-Ethernet (PoE) switch.

    Your DHCP server must have a range of IP addresses (pool) that is larger than all of the devices that you will connect.

  2. Use Ethernet network cables to connect the cameras to the switch.

    Caution

    If you connected the cameras too soon, before a DHCP server was available, then they are using a default IP address. The default address will not work with your network. To fix this, unplug the cameras and then plug them in again. This reboots the cameras and requests a correct IP address from the DHCP server.

  3. On your DHCP server, create a reservation for each camera so that it always gets the same IP address.

    Tooltip

    Fortinet strongly recommends to either:

    • configure your cameras with a static IP address (see Address), or
    • configure your DHCP server with lease reservations and then update the camera's Address with its current IP address

    Without reservations, the IP address provided by the DHCP server might appear to work initially, but later, when the DHCP lease expires, the DHCP server might change the IP address of the camera. DHCP servers do not notify FortiRecorder about the camera's new dynamic IP address. FortiRecorder tries to detect IP address changes with mDNS probes, but some networks do not allow this. During this time, FortiRecorder will try to control the camera at its old IP address. This does not work. Connections with that camera will be broken and all video from that camera could be lost during that interruption.

  4. Use Ethernet network cables to directly connect port1 of FortiRecorder to your computer.

    Do not put your switch between them yet. FortiRecorder network settings are not configured yet.

  5. Temporarily change your computer's IP address to be 192.168.1.98 with subnet 255.255.255.0. (If your computer has a static IP address, write it down so that you can restore the settings later.) Steps vary by whether you use Apple macOS, Linux, or Microsoft Windows.

    Alternatively, you can use a different IP address, but it must be on the same subnet as the default IP address of FortiRecorder port1: 192.168.1.0/24.

  6. On your computer, open a web browser and go to:

    https://192.168.1.99

    Log in with the name admin and no password.

  7. Change the password. For details, see Setting the "admin" account password.

  8. Configure port1:

    1. Go to System > Network > Interface.

    2. Select port1. Click Edit.

    3. Enable Discover cameras on this port.

    4. In IP/Netmask, enter the IP address and netmask that FortiRecorder will have on your network.

      Caution

      Do not use one of the range of IP addresses that the DHCP server assigns to cameras, computers, etc. (This can cause IP address conflict error messages.)

    5. Click OK.

  9. Change your computer's IP address and subnet back to its original settings.

  10. Unplug the Ethernet cable between your computer and FortiRecorder port1, and then plug them both into the switch.

  11. In your web browser, go to the new IP address of FortiRecorder. Log in.

  12. Discover and configure the cameras:

    1. Go to Camera > Configuration > Camera.

    2. Click Discover.

      After several seconds, a list of cameras appears.Newly discovered cameras are highlighted in yellow, and their Status column displays Not Configured.

    3. Double-click each camera to adjust its settings. For details, see Configuring cameras.

      Repeat this step for all cameras.

  13. To verify that FortiRecorder is able to receive video from the camera, go to Monitor > Video > Video. You should be able to see the camera's live video feed.