Hi all.Had been searching everywhere for a solution for this issue. While the conditions discussed here are not 100% similar to mine, I am convinced that the issue is the same.1) My environment runs a Cisco 3850 stacks access switches with two vlans,...
@Dan Hoag we did eventually get it fixed and we ran the commands on all the switches and we have not experienced any DHCP issues ever since. I just copied from a production switch right now.ip device tracking probe auto-source fallback 0.0.0.1 255.25...
This is one of the most insightful explanation on the Vlan vs Bridge domain topics with diagrams as an added bonus.Thank you for your contribution RedNectar.
After weeks of struggling with this issue.I ended up generating a new Root CA and DNAc could join successfully. At some point I blamed a bug. Running ISE 3.1 and DNA Version 2.2.3.6.I could have broken the certchains on ISE when doing an upgrade and ...
Hi @Georg Pauwen I would admit there is a huge number of ip-helpers will need to remove them, they don't have overlapping scopes,,The scope you saw is a Temp scope put in place few days ago to temporarily hand over addresses and that is what is keepi...
I have tested by removing the Temp scope I had, and managed to bounce a Windows 10 machine and a Cisco AP, both got addresses from the Microsoft DHCP and are both reachable on the network as shown on the attached image.I modified the tracking command...
