Hi Majba, There is a typical ACI behaviour with dhcp relay I am aware about which occurs in case you try to reach DHCP server via another VRF within ACI (Inter VRF). 1. The discover request is sourced from the ip address of the out-going interface IP which in your case would be ip address of the interface from default vrf and not your BD SVI. So please check if you are applying the right filter in wireshark. I would suggest to filter via MAC address of your host. 2. In such cases DHCP option 82 sub-option 5 comes into the picture and which contains the subnet information from which you actually need the IP address from the DHCP server. 3. In case you are running DHCP server on MS then Microsoft Server 2016 is the minimum version which supports DHCP option 82 sub-option 5 (I assume TAC might have already verified). 4. Now if you have MS2016 server running DHCP services then there is typical requirement to have a n IP scope defined on the server for the subnet in ACI (L3 out interface subnet) which is the exit point of the VRF otherwise you may see a NACK.   Parallely, you can also verify at your end following the instructions shared in below Technote: https://community.cisco.com/t5/data-center-documents/technote-on-dhcp-relay-in-aci/ta-p/3161830   Let me know if you need more clarity on any of the points above. Regards, Jayesh   ***Rate all posts that are helpful. Mark it as a solution if that solves your problem, it may help other users who have the same query.*** ... View more

Thanks for the details Steve. There is one configuration setting for LLDP policy I am aware about, but can't see those options there, Please follow below GUI path: Fabric > Fabric Polices > Global > Click on LLDP Policy Default You will see optional TLV selector attributes there,   ... View more

Hi Steve, Have you tried enabling LLDP on interface policy group corresponding to your leaf ports connecting to your servers? Is it not working? Regards, Jayesh ... View more