Remove the controller, upgrade to DNAC 1.3 and then readd the controller is an standard approach, if you have upgraded already, check if rogue AP detection is enabled on the controller, thats when this issue is triggered with controller going in unmo...
Multiple Scenarios and end result can be achieved following multiple approaches:* Legacy approach is to create a new VLAN for every new set of devices.* Creating a new vlan doesn’t change anything till the time that VLAN forwards to same VRF. If full...
Technically yes, desirably no, you can achieve it but you would still need vbond, vsmart and vmanage for orchestration and policies to achieve the end objective. Value add will be missed since the true value of the Solution is connecting different si...
I faced a similar issue back in the days once, but worked for me second time I tried, just readded the vSmart on vManage, I am running Platform Version: 19.1.0 for vManage in my Lab and works like a charm for me. Upgrade may be? Thanks
