AP9619 ip address not connecting via DHCP

[trouble]

We recently bought an UPS from APC with a AP9619 network card, i am trying to dhcp to it. My configuration works when there is an DHCPACK response and i get results when i ping it. But a couple of seconds later when i get a BOOTREQUEST request, i am no longer able to ping the ups.

According to 'APC netorwk management guide', "If a DHCP server responds with an invalid offer (for example, the offer does not contain the APC Cookie), then the Management Card will accept the lease from that server on the last request of the sequence and then immediately release that lease."
This makes me think that my cookie is invalid, however accoring to 'APC installation and quickstart document' the correct sequence is 01 04 31 41 50 43.
So what is causing me to gain connection then loose it 2 seconds later?
Thank you

Lease
lease 172.16.240.100 {
starts 5 2024/05/10 13:47:31;
ends 5 2024/05/10 13:47:46;
tstp 5 2024/05/10 13:47:46;
cltt 5 2024/05/10 13:47:31;
binding state free;
hardware ethernet {mac address};
uid "\000\000\300\267{Bo\000\000\000\001\000\300\267{Bo";
}
server-duid "\000\001\000\001-\320\322\000\000&U\334\207\370";

lease 172.16.240.100 {
starts 5 2024/05/10 14:03:00;
ends 5 2024/05/10 14:13:00;
cltt 5 2024/05/10 14:03:00;
binding state active;
next binding state free;
rewind binding state free;
hardware ethernet {mac address};
uid "\000\000\300\267{Bo\000\000\000\001\000\300\267{Bo";
set vendor-class-identifier = "APC";
set vendor-string = "APC";
}
lease 172.16.240.100 {
starts 5 2024/05/10 14:03:00;
ends 5 2024/05/10 14:03:15;
tstp 5 2024/05/10 14:03:15;
cltt 5 2024/05/10 14:03:00;
binding state free;
hardware ethernet {mac address};
uid "\000\000\300\267{Bo\000\000\000\001\000\300\267{Bo";
}

Dhcp.conf
class "APCUPS" {
match if substring (option vendor-class-identifier, 0, 3) = "APC";
}

# The following line populates the lease file with the Vendor Class identifier that the client sends.
set vendor-string = option vendor-class-identifier;

subnet 172.16.240.0 netmask 255.255.255.0 {
pool {
range 172.16.240.100 172.16.240.150;
filename "grubaa64.efi";
next-server 172.16.240.1;
option routers 172.16.240.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 195.171.11.66, 81.145.132.3;
option vendor-encapsulated-options "01 04 31 41 50 43";
allow members of "APCUPS";
ping-check TRUE;
}
}

Ping requests
/etc/dhcp$ ping 172.16.240.100
PING 172.16.240.100 (172.16.240.100) 56(84) bytes of data.
64 bytes from 172.16.240.100: icmp_seq=7 ttl=255 time=2059 ms
64 bytes from 172.16.240.100: icmp_seq=8 ttl=255 time=1038 ms
64 bytes from 172.16.240.100: icmp_seq=9 ttl=255 time=17.1 ms
64 bytes from 172.16.240.100: icmp_seq=10 ttl=255 time=6.74 ms
64 bytes from 172.16.240.100: icmp_seq=11 ttl=255 time=5.82 ms
64 bytes from 172.16.240.100: icmp_seq=12 ttl=255 time=4.28 ms
64 bytes from 172.16.240.100: icmp_seq=13 ttl=255 time=3.79 ms
From 172.16.240.1 icmp_seq=1 Destination Host Unreachable
From 172.16.240.1 icmp_seq=2 Destination Host Unreachable
From 172.16.240.1 icmp_seq=3 Destination Host Unreachable

Log
2024-05-10T11:14:18.175768+01:00 {random server} dhcpd[314803]: BOOTREQUEST from {mac address} via enp1s0f0: BOOTP from dynamic client and no dynamic leases
2024-05-10T11:14:51.025081+01:00 {random server} dhcpd[314803]: BOOTREQUEST from {mac address} via enp1s0f0: BOOTP from dynamic client and no dynamic leases
2024-05-10T11:15:01.790599+01:00 {random server} CRON[315761]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2024-05-10T11:15:23.975756+01:00 {random server} dhcpd[314803]: BOOTREQUEST from {mac address} via enp1s0f0: BOOTP from dynamic client and no dynamic leases
2024-05-10T11:15:56.076768+01:00 {random server} dhcpd[314803]: BOOTREQUEST from {mac address} via enp1s0f0: BOOTP from dynamic client and no dynamic leases
2024-05-10T11:16:28.526150+01:00 {random server} dhcpd[314803]: BOOTREQUEST from {mac address} via enp1s0f0: BOOTP from dynamic client and no dynamic leases

2024-05-10T11:17:05.502276+01:00 {random server} dhcpd[314803]: DHCPDISCOVER from {mac address} via enp1s0f0
2024-05-10T11:17:06.503923+01:00 {random server} dhcpd[314803]: DHCPOFFER on 172.16.240.100 to {mac address} via enp1s0f0
2024-05-10T11:18:09.729322+01:00 {random server} dhcpd[314803]: DHCPREQUEST for 172.16.240.100 (172.16.240.1) from {mac address} via enp1s0f0
2024-05-10T11:18:09.774501+01:00 {random server} dhcpd[314803]: DHCPACK on 172.16.240.100 to {mac address} via enp1s0f0

2024-05-10T11:18:24.568811+01:00 {random server} dhcpd[314803]: BOOTREQUEST from {mac address} via enp1s0f0: BOOTP from dynamic client and no dynamic leases
2024-05-10T11:18:56.977955+01:00 {random server} dhcpd[314803]: BOOTREQUEST from {mac address} via enp1s0f0: BOOTP from dynamic client and no dynamic leases
2024-05-10T11:19:06.721821+01:00 {random server} systemd[1]: Started session-7642.scope - Session 7642 of User Tinkerbell.
2024-05-10T11:19:29.077664+01:00 {random server} dhcpd[314803]: BOOTREQUEST from {mac address} via enp1s0f0: BOOTP from dynamic client and no dynamic leases

[Teken]

I’m not really sure what you’re asking or trying to do. But, login to the NMC Webpage go to the following:

Configuration -> Network -> TCP/IP -> IPv4 -> Uncheck vendor specific cookies.

If this resolves your problem mark this as solved. If not please restate your question.

[trouble]

Thank you for the suggestion. Unfortunately, I'm working solely through the Linux terminal, so GUI-based solutions aren't an option for me.
I apologize for the confusion earlier. I'm relatively new to this. I have a specific issue with my new Smart-UPS Network Management Card (AP9619). When I assign it an IP address via DHCP, it initially acknowledges and accepts the IP address. However, shortly after, it drops the assigned IP address. I've successfully assigned IP addresses to other devices using DHCP before, so I'm unsure why this issue is occurring specifically with the UPS NIC. What could be causing this behavior?

[Teken]

A Static IP address can be assigned to the NMC by using SSH / Telnet / Serial. Go into the Configuration -> Network -> TCP/IP -> IPv4 and disable DHCP and enter the network attributes for your LAN.

Another way I believe you’re trying to do is reserve a IP Address based on the NMC MAC Address. This can be easily done with the router, firewall.

The last method is to go to the UPS and enter the network attributes via the LCD. 
As an aside I’m unsure why you would not use the web interface to make these changes?!? All Linux OS offer some kind of web browser and using this interface would assist you in the fastest deployment of the new hardware.

[trouble · Accepted solution]

Hello thank you for your responses i fixed my error by removing the quotation marks from the cookie, and all other un-nessesary lines. This then allowed my ups to be assiged a temporary ip address, using that ip address i could access the apc's website and change the ip address manually.
For anyone else who gets stuck on option 43 cookie this is what my dhcpd.conf looks like.
Thank you all for your help.

subnet 172.16.240.0 netmask 255.255.255.0 {
pool {
range 172.16.240.100 172.16.240.150;
filename "grubaa64.efi";
next-server 172.16.240.1;
option routers 172.16.240.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 195.171.11.66, 81.145.132.3;
option vendor-encapsulated-options 01:04:31:41:50:43;
}
}