Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello, we are looking at deploying the 9105 AXW APs in our environment to improve wired and wireless availability to certain areas of our infrastructure. We had been told long ago when we purchased some 1815W APs that there was a feature request on t...
I just pushed out the 2.1.2.4 upgrade to one of our DNA-Center installs, and after the upgrade I am getting the following post-upgrade task when in a fabric site: The fabric edge nodes do not need to reach each other using /32 in the underlayAnd am p...
In our environment we have a number of sites with local fusion routers, with a border connected to it. We're currently using IP Transit with the local fusion routers providing a default route to our borders for all current VNs. We are looking at addi...
I haven't been able to find any documentation, but is there a way to reliably exclude a switchport from being able to have port assignments configured in host onboarding? I know that having a description of "Fabric Physical Link" is a keyword used by...
In the SD Access Wireless Deployment Guide it shows that Fabric capability is enabled on a per WLAN basis, however when you try to do this in practice (DNA-C 1.2.5) it tells you than only one type of policy can be enabled per Site. Is this planned to...
So it looks like the option only appears if you've designated the device as a stack when adding it to PnP. If you mark it as a stack, you get an option to assign stack details on the "Assign Configuration" page of the claim process. You can set a lic...
Through PnP, yes. During the claim process there is a section to select the image and license level.Through LAN Automation, no. Those claim parameters are locked down and cannot be modified. Your device will need to be on a DNA Advantage license befo...
System version 1.5.255 is DNA-C 2.1.2.5. Edit: I'm not sure who marked this is the solution, but this was more for Balaji.Bandi who said that version of DNA did not exist.
In my testing, DHCPDISCOVERS were not forwarded between FEs. If the DHCP server was located on the same FE as a client, the entire process worked as expected. I did not test disabling DHCP snooping, but given that changes to a fabric network could ch...
It does not, I have tested that multiple times and the current implementation of L2 flooding with a standard SDA deployment does not pass DHCP Offers sourced within the VN between devices. It may function if you disable DHCP snooping the VLAN that ha...
