วีดีโอ

Hi, dCloud is accessible to all Cisco partners. You have multiple demos, both instant and scripted labs you can schedule and configure. Search for SD-Access or Catalyst Center (DNA Center) in dCloud catalog.

In this series, I used the Dedicated Guest VN. It uses the same B/CP as the other VNs. By ticking the box for Guest VN, Catalyst Center recognizes it. When you want to add a Guest SSID or a captive portal, Catalyst Center will know it is for guests and give you the subnet from the Guest VN pool when enabling it. So, it makes it easier.

Hi, this was supported in the past, but it has been discontinued. Embedded WLC on a C9k switch is only supported on an SD-Access deployment at present. See guide: www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-744299.html

@@pabmart Thanks for sharing this Doc. But this doc talks about Embedded WLC in Catalyst 9000 = Some Catalyst 9K have built-in WLC right? But that is not what I am talking about: I just want to use DNA Center to manage the deployment and provisioning of my WLC and WAPs. I don't want to use the WLC to provision my WAPs, but rather integrate my WLC into DNA and use DNA to provision my WAPs. Of course my environment doesn't have SD-Access, and i am already using DNA to provision my IOS-XE switches (non SD-access environment), just trying add my physical C9800 in this environment but manage my WAPs from DNA and not from the WLC....hope I am not confusing you by being too repetitive. In Sum, I want to do what this video is doing but in a non-SD-Access environment

@@mariejosv Apologies if I misunderstood. Yes, you can do that and it's a typical use-case. Once you add your WLC to the inventory via a discovery, Catalyst Center will discover the APs attached to said WLC. You can then manage the WLC from there and the best of all, get all the assurance capabilities in Catalyst Center. Hope that helps.

@@pabmart Thanks a lot. I feel confident now moving in that direction. Last question: What are the Assurance features that DNA has over the WAPs or over the WLC itself that the WLC cannot provide? what are the real added values using the DNA vs relying on the WLC?

Catalyst Center discovers the AP via the WLC and shows up directly in inventory.

I recorded these videos ~2Ys ago, I can't remember exactly. But after looking through it again, it seems that Catalyst Center for some reason left that port behind and I did a manual assignment to then force the normal port configuration which should have been the same as 1/0/38. Maybe not the answer you were expecting, but hope that helps.

Glad it helped. Not much thought went into it. Essentially earlier versions of Catalyst Center hard coded those VLANs while automating the L3 handoff starting at 3001. In this version of the lab CC allows the user to manually enter the VLAN ID. As all my templates and notes were already done with 3001-300x from previous labs, I just continued using those.

@@pabmart Got it. Thank You very much.

Hi, yes I've tried that and works fine. I just prefer the option 43 as it's quick and easy. For DNS you have to include the domain in your DHCP offer. The device will then look for PNPSERVER.domain.com, you can see more in the user guide: www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/2-3-7/user_guide/b_cisco_dna_center_ug_2_3_7/m_onboard-and-provision-devices-with-plug-and-play.html#id_90879

For this lab, most of the equipment was physical. The only VM I think was the C9800 WLC and the Linux machine.

Thank you for your quick answer ! Do you know if there is any way of having a DNA center + ISE evaluation license for practice purposes ? @@pabmart

@@niichinonii559 If you get your hands onto an ISE image, it will give you 90days evaluation license. For Catalyst Center you'll need either the physical appliance, or get the ISO to put on ESXi or AWS. No license required.

APs attach to the WLC. Catalyst Center (formerly DNAC) discovers the WLC. CC then learns the APs via the WLC and adds to inventory.

Sounds is clear on my side. Please check your headset or audio output. Thanks.

ok thanks @@pabmart

Hi, glad to hear. The template is adapted to my lab environment, there is nothing exceptional in it. Some of the things I've put: username/pass/secret (so DNAC can use that once provisioned), enable ip routing, hostname, ssh v2, some vlans, enable netconf, loopbacks and L3/L2/Trunk physical interfaces, a static route, line console, line vty. That's pretty much it. It's just the very basic setup to allow DNAC to reach, and take over it via GUI.

Glad it was helpful!

@@pabmart I haven't tried it yet but I hope I will get this scenario soon. I have L3 SVI for vlan 10 on my router and expect switch to get connected with it using a routed interface (no vlan on switch, just like a P2P configuration). Will this dhcp part work with this scenario ?

@@vaibhavbhosle6511 You will need VLAN 1 subinterface on the upstream router and provide the DHCP on that vlan. PNP Agent works on VLAN 1 by default. You can remove VLAN 1 once PNP has finished and your device has been fully provisioned with desired config.

@@pabmart Can this PnP method be used for deploying Fabric edge switches as well ? What about smart licensing will there be any issue if choose deploying using PnP instead of LAN Automation

Thnx@@pabmart

At the Fusion device.

@@pabmart when you do a Pnp service restart in pnp agents, it will automatically do the discovery to the fusion device? Also, don’t you have to configure the interface where the discover message goes to in DNAC?

@@estebangomez1823 Hi, no config needed in the device to be discovered. Just let it boot into out of the box state, where it runs a PNP agent. The agent will try to get an IP address and Default GW along with Option 43 via DHCP from any interface in UP status. Ideally, that will be the interface connecting upstream (to the Fusion in this case). It will use that configuration to reach out to DNAC. You have to make sure reachability is there between PNP device and DNAC (now known as Catalyst Center). Hope it helps.

No probs!

Thanks for watching!

I don't have any on brownfield unfortunately. This was a from-scratch lab I did about a year ago.

Rock on! Glad it helped.

Glad it's helpful and yes please, if you have any questions let me know.

Hi, Yes /31 is allowed in that field. Hope that helps.

@@pabmart yep, thanks

Hi, each fabric site will require a WLC. For branch sites, you could deploy Physical, Virtual or Embedded on a C9300.

Looks fine to me on 720 & 1080 quality. Have you tried that?

Hi, no IGP between them in this lab. I'm using static routes, and then BGP for the L3 handoff. Hope that helps.

Hi David, maybe try adjusting the video quality feature here in TH-cam. When I play it at 480p it is fair and with 720p/1080p image is clear.

Hi, Yes you can have a shared WLC to manage Fabric and non-Fabric APs. Fabric is enabled per SSID not per controller. Please refer to CiscoLive session in the on-demand catalog: Fabric Fundamentals - Integrating wireless into SD-Access (Fabric Enabled Wireless) - BRKEWN-2308, for more information on this.

@@pabmart Thanks Pablo. I’ll have a look at that. It’s something customers with existing standard deployments ask as a way to keep their existing setup and migrate to SDA wireless in a staged manner on the same controllers.

Can also leave existing controllers in place, deploy new controllers in parallel, then start migrating APs on an area by area basis... So, you could have floor 1 in the new controller fabric enabled and the rest of the floors on the older controller non-fabric. Just a thought.

When you create an SSID in Network Design, attach it to a Network Profile and assign to the site(s), it will show up in the summary of the provision workflow. It then gets provisioned to the WLC. Hope that helps.

Hi Ali, There are a couple of great CiscoLive on-demand sessions that go over the migration to SD-Access. Take a look at BRKCRS-2812 Barcelona 2019 and TCRCRS-2500 Barcelona 2019. They are old sessions but content is still valid. Hope that helps.