Siscco

I have not done that in my Real LAB.

This seems to be correct.

Sorry to hear that Brother.

Hey Man , Yeah do it only for IoT VN , and it does not need any additional Policy. Worked fine in my Lab exam .

check for prefix suppression , try clear ospf in DC. Check if you're fully converged in VPNV4 - SP1

DNAC takes some time to bootup. Better do not do that.

Try Adding eBGP Multihop <2> , Happened with me while practicing. However never happened in real exam.

I was having some General Slowness While accessing DNAC GUI , made difficult to me to manure through it. Also faced some issues while deploying to one of the Switches . fixed somehow after some few re-sync retries. Keep an eye on SW400 while deploying AAA configs. Rest all was good.

DNAC GUI was on a slower Side. took some time to gain the phase.

I would recommend you to start practicing session 1 to finish in less than 1:30 Hours. Section 2 may take longer than we expect. That is what happened with me on my last attempt.

Found this useful thread. DNA Center - Provision - What It Does To Your Devices | zartmann.dk

Thanks champ

I see. it looks like " aaa authentication login default local " is already preconfigured on all SDA switches. which might be the reason DNAC does not push the same to console? as it might intelligently automates the task ?

Yeah , Initially I thought the same. I do not see an option to Specifically select , VTY or CON in DNAC while we do 2.1 . Any thoughts on that ?

Guys , I still wonder how'd we get locked out from devices if we do 2.1 ? we are dealing with VTY login , still we got OOB isn't it ?