@Clive_A Hello Clive_A, thanks for the answer.

The solution that you give it's useful but dont solve my problem, because the client has about 3 or 4 "back up cameras" and we don't know what camera will fail and the 3 or 4 cameras will be connected in any port, so link a ip to a mac address don't solve my requirement, because i need to recieve the same ip address in the same port that was connected the camera that failed.

What i need it's to assign an IP Address to any camera that connect to an specific switch port.

I think that my last colleagues used single port VLAN to solve that, but i dont know how to link an specific IP from DHCP server from the switch to a specific VLAN

  @GabrielBV 

This may be higher than the switch.

It's safe to assume the clients (the IP cams) use DHCP to get their network details (IP add, GW, mask, etc).

If Link Layer Discovery Protocol (LLDP) can be enabled on the switches, you may be able to get what you are after using DNSmasq as the DHCP server for that subnet.

Using DNSmasq, you should be able to create a config that inspects the DHCP request from any client and determine the switch port to which the client is connected.

Then, DNSmasq should be able to send a specific IP address to the DHCP client plugged into that port.

When a failed camera was replaced, the new camera would get the same IP address as the old one had.

Using a non TP-Link switch, we used this technique to PXE boot Linux hosts and the their hostnames / IP addresses would derived from LLDP to be unique within the rack (based on the port to which they were connected). It did require a little bit of creativity on DNSmasq, but it worked.