ER7206 Build 20230322 Does not fix static IP issues where a current DHCP Res list exists.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

ER7206 Build 20230322 Does not fix static IP issues where a current DHCP Res list exists.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER7206 Build 20230322 Does not fix static IP issues where a current DHCP Res list exists.
ER7206 Build 20230322 Does not fix static IP issues where a current DHCP Res list exists.
2023-03-29 20:50:19 - last edited 2023-03-29 20:57:12
Model: ER7206 (TL-ER7206)  
Hardware Version: V1
Firmware Version: 1.3.0 B 20230322 Rel 70951

I updated the firware as a result of reading through some threads where people were having issues with static IP's for clients changing, even though the DHCP reservations in services are clearly there.  Even after updating, the current DHCP Res list remains, however none of the static IPs are assigned.  I rebooted all the switches and EAPs including the controller with no luck.  I thought that this firmware update should have corrected this???   Perhaps I missed where its written that you must recreate a new DHCP reservation list?

 

Regards

 

Sean

  0      
  0      
#1
Options
1 Accepted Solution
Re:ER7206 Build 20230322 Does not fix static IP issues where a current DHCP Res list exists. -Solution
2023-03-29 20:56:53 - last edited 2023-03-29 20:57:12
My apologies. When I rebooted my system the switches associated with my network did NOT reboot. When I ensured that the switches were rebooted this indeed corrected the problem. Thread can be closed.
Recommended Solution
  2  
  2  
#2
Options
1 Reply
Re:ER7206 Build 20230322 Does not fix static IP issues where a current DHCP Res list exists. -Solution
2023-03-29 20:56:53 - last edited 2023-03-29 20:57:12
My apologies. When I rebooted my system the switches associated with my network did NOT reboot. When I ensured that the switches were rebooted this indeed corrected the problem. Thread can be closed.
Recommended Solution
  2  
  2  
#2
Options

Information

Helpful: 0

Views: 469

Replies: 1

Related Articles