APM-DHCP Access Policy Example and Detailed Instructions
Prepared with Mark Quevedo, F5 Principal Software Engineer May, 2020
Sectional Navigation links Important Version Notes || Installation Guide || What Is Going On Here? || Parameters You ...
Updated Sep 08, 2023
Version 9.0Chase_Abbott
Employee
Joined September 17, 2008
Chase_Abbott
Employee
Joined September 17, 2008
Mark-Quevedo-F5
Ret. Employee
Joined December 10, 2021
Gopichand_Yaragani
Employee
Joined February 01, 2023
M_Quevedo
Apr 30, 2020Nimbostratus
If you wish, you can test another config trick. Perhaps your DHCP servers only demand Option 61 client-ID because they do not like the 32-bit "serial line" client-hardware-address that APM-DHCP uses by default (sort of like RBTJNR's problem). You could run a test with variable session.dhcp.hwcode set to "MAC" with no Machine Info Item, and not placing the sessionID-constructed-MAC from session.dhcp.client_ID. With that configuration, the DHCP requests will not contain Option 61 but they will have the sessionID-derived MAC in the client-hardware-address field. That may be more pleasing to your DHCP servers.