Wireless automation with Catalyst Center 2.3.7.9

Oh, ok, once again, thank you everybody for joining us today. Welcome to this expert insight series session about wireless automation with Catalyst Center.00:00My name is Gara Pietra. I'm together with Christian Gower. We are both customer success specialists working on adoption of Catalyst Center with background in networking and well Christian in particular heavily in wireless.00:20Just a quick note here in this kind of sessions, we usually provide guidance following Cisco best practices. Of course then it's up to you to review what we're presenting and if you have any question more specific to your environment, feel free to let us know in the surveys.00:37So that we can contact you one on one.00:54Hopefully at this point you are familiar with expert inside series. It's basically the webinars that we do from customer success team, different technologies, different architectures and solutions. In this module in specific we are focusing in wireless both configuration and.00:58Automation today in the next session happening next week assurance capabilities and then also we are going to introduce you a bit to what to expect, how to prepare and what you will see in the next release of Catalyst Center, the three.one.01:17That should be available soon. So if you are interested in these sessions, make sure you have registered to this as well. A bit of housekeeping, you have been muted on entry.01:32If you have any questions during the session, feel free to post it in the Q and A panel. Please, if you don't mind doing that in that place, you will find the Q and A panel considering the bottom right, the three dots, you can click there, you will see the panel, you can send the questions to all the.01:49The panelists so that we have visibility and can track it. If for any reason we don't manage to give you an answer during the session, don't worry, we are going to contact you after the event with the pending answers. And if you have any problem, technical difficulty finding the Q and A panel or audio, whatever, just feel free to put out.02:07The message in the chat as particularly to the host if possible. Okay, let's set up a bit the base of what we are going to see today and from there the agenda. When we talk about wireless with catalyst center, we basically have two really different situations.02:27We have, if we start with the right, what we call the greenfield, a new wireless LAN controller that you need to start from scratch with the configuration, that basically you have the possibility to plan that configuration and do it directly from catalyst center, and we are going to provision that wireless LAN controller.02:46And from there also of course you need to onboard access points. You can have different workflows for operational tasks or configurations to be applied.03:06When we talk about workflows, we refer to plug and play software upgrades, config on access points and well some others, and we will be reviewing some of them today. On the left, we have a totally different situation that it's basically you start working with catalyst center, but you already have your configuration in your wireless line controller.03:17So, for those cases, usually most customers maybe want to start using data center for monitoring and troubleshooting purposes. It's what we call the assurance only use case.03:37Maybe something new. There is a second scenario starting in 2379 that allow us to have some, also capabilities of configuration even in brownfield. It's what we call the per device configuration that we will review in later. And in any of those situations within the brownfield, you.03:51Still have possibility of doing workflows for access point configuration and operational tasks in general.04:10So having this in mind, this is the agenda for today. We are basically start with the concept of what we see as intent in Catalyst Center that it's a concept on how catalyst center works for different features. We are going to tie this with the greenfield scenario, the one in the right, we are then.04:17Going to be covering the details of the brownfield, including this new feature of per device configuration, and we are going to mention capabilities on different workflows. Most of the workflows applies for those situations. There are some differences we are going to be going a bit in the details for some of them.04:37A quick note before we start, you will see that most of the content, the screenshots, recordings, and demos have been done with three.x3.one in particular of catalyst center, but for the features we are mentioning everything much if you are currently running a recommend.04:58In the release 237, everything will match from concepts, procedures where you find the things so it should not be any difficulty for you. It's just to start introducing the new release as I was mentioning respected to have it soon. And one additional comment for you to be aware we are going to be reviewing different concepts.05:16Some of them may also apply to fabric enabled ssids, but we are not going to go to the details of wireless in SDA today.05:36Regarding the presentation that we are going to provide, basically you will see that we have step by step screenshots, demos that we were sharing like to summarize what we have been showing. We always show you where we are locating in terms of menus in Catalyst Center that there are a lot so it can get complicated.05:44Did in the top right corner, you will see that. And then the idea here is to show you a lot of the capabilities. Maybe in some cases you're not going to go to every config of of those features, but just for you to be aware of what you can do for your wireless depending on situation and from there maybe do an analysis and some.06:03Testing in your testing environment so that you can actually adopt it.06:23With this, we can stop with the introductions and go to the topic, basically we are going to start with intent and when we want to deploy a wireless network, we really need to start with the plan and that plan includes AP positioning. So basically from catalyst center.06:28Point of view, this also means having your network hierarchy ready as part of the plan and then a positioning APs on the maps. There is also a design component of different network settings for sure, e.g., ssids and other configurations that at the end get matched to what we call a network profile.06:47Other aspects of design are also, e.g., what image, software image you want to have running in your environment and that's why we need to pick what we call a golden or standard image. At some point everything we have been planning and designing needs to be configured on the wireless line controller and the access point and.07:08And this is what we call the provisioning.07:27And the end goal is also to have visibility of the performance of the wireless network, be able to assure is healthy detect client issues et cetera. So more or less this, this could be the workflow. But why we say intent as this main concept? Well, basically because.07:30Because when we start with the Greenfield in Catalyst Center, maybe we don't need to focus on how to do certain stuff but more on what we can do, what we want to do. Like e.g., configure an SSID with enterprise security.1X leveraging ice.07:49And if you are familiar with the controller, you may know that there are different concepts of profiles and tags that need to be considered, but maybe with this intent, we can abstract a bit from that. Here in the example we are talking about wireless, but this also applies for other devices in Catalyst Center.08:08And at the end, this is the idea, be able to plan, design, have the configuration ready based on this intent of what I want to do and be able to scale, replicate those configurations maybe if I need it with multiple wireless line controller, say an example.08:26So when we talk about intent and in Catalyst Center in general, there is something that is really important and is the site. Catalyst center is really site centric. Like, e.g., if we have been planning settings, network, network settings or services, those need to be assigned or matching sites. Then I briefly mentioned.08:45Some profile. Well, the profile where we have information on ssids, RF parameters, it's also going to be assigned to a site. The devices itself are going to be assigned to sites and from there are going to inherit the properties of what we have defined.09:05Based on those sites. So considering all these for sure, a starting point we need to take into consideration in catalyst center is the network hierarchy. That is basically where we define these sites. You may already be familiar with this, you know, we start with global, we have the possibility of creating areas, different regions. It could be, e.g..09:20So EMEA level country level, and from there start to including the buildings and then the floors.09:40Access points needs to be assigned to floors and ideally placed on maps as I was, as we will see and I was mentioning before. Maybe one thing to highlight from Hurricane Catalyst Center is that buildings need to have a physical address or coordinates. If your the.09:48Browser where you are, as admin are, are accessing Catalyst Center has internet connection, there is a mapbox integration so that you can auto complete the addresses. It's really useful.10:07But this is especially important if you still are in prime and needs to migrate something because this is going to be required. We know that this work of maps especially if you already took the time to place the access point on the maps maybe a bit time consuming. So if you still are in the situation of migrating via.10:19Work that a lot of what you have done can be reused. There are even some tools that could be leveraged to migrate from prime. And also if you, e.g., did some work with Echo how and you have your access points already placed, this can also could be integrated or imported.10:39So let's start from the situation where we do not have these capabilities and we need to do it manually, in catalyst center, in the hierarchy in the map, in the floor map, we are going to be placing access points. In this case, if you notice makes maybe a bit small, but these access points have like a small low.10:58Toggle a P in black well under under the black background. But basically that B means plan. This is the 1st step when we are planning where to put these access points.11:17And, of course this is not yet operational, right? From here we can include additional plan access points, we can see the distance between them. We can edit information if required. And some important highlights to do at this point.11:30Is the names of the access points of your plan access points. Of course there are different naming conventions you could follow, but maybe just something that we recommend not to do is to include models of access points in the names. You can include buildings, maybe if they are in an older area.11:50But the models itself then makes it a bit more complicated at the time of refresh that at some point that happens in in networks and even though we have workflows, you know, that speed up all these processes, if then we need to handle the name portion at the end it's less efficient. We're going to address this, this use case as well. So just for you.12:09Need to be aware of this, we may touch on this later again.12:29So we have the plan access points. Let's keep moving with the design. Here is where we have the settings. E.g., from general network point of view, servers like triple AAA DNS, NTP, credentials so that catalyst center can connect to the device, telemetry that gets.12:33Push automatically to them be able to work on assurance.12:52But of course, if we are talking about wireless, one of the main screens we are going to see here in the design is everything related to wireless configuration, including SSID, profiles of different types. This is an important point. If you have your wireless LAN controller already co.12:58Figure. You are in the brownfield situation for sure you're not going to be using this page. This is everything related to that intent Greenfield provision deployment.13:17So, ssids are created at global level, and then these get innered to the other sites where you could do some maybe change specific to a site. Ssids at global level makes sense, like if we think e.g. corporate SSID, we probably want to have it in all our.13:28Our buildings, but maybe we need to do some tuning per site like e.g. AAA.13:46There are some additional components of the configuration, what we call the feature templates. Maybe if you have seen catalyst center in previous releases, model config resonates with you. It's basically additional configuration advanced safety configuration, as you can see cleaner settings, erroram also related.13:53That we can also include in our configuration and that follows the same model of of intent.14:13So let's see an example of creating an SSID. When we are at a global level, we want to create an SSID, it could be enterprise or guest. Main difference is that the guest includes the possibility of having some captive portal with integration with ICE.14:20So if you don't need that, you don't need to put the guest. If you already have those captive portal in place, e.g., you could go with the enterprise and then do some kind of redirection.14:39When we start this workflow, basically we are going to give a name to the SSID. We are basically enabling it from this 1st screen. There are security settings we can of course choose. We can here include, e.g., the AAA we want.14:50To use based on what we have configuring our settings, and here basically all this configuration is done following best practices from Cisco. Usually, of course you can customize what you need, but our recommendation that we do is to pay attention to the session timeout because.15:09Sometimes it's a bit short the value so in order to do a better experience for the user, maybe we can consider extended to a full day, e.g..15:28For the rest, this is pretty straightforward. You could include some advanced SSID settings right here considering those feature templates. And the next step is saying, ok, we have the SSID, but in order to use this, we need to attach it to a profile, and we are going to include this as part of the configuration.15:39So in this case we don't have any profile yet, created, so we are going to add it.15:59We are going to give it a name. We're going to consider if the SSID is going to be fabric, non fabric, flexconnect or just simply put the VLAN there. And at the end we have the summary. From here we can go to the profile itself, the profile that we just created.16:05Again in the design, 1st we were in the network settings, now we are in the network profiles.16:26And from here we will see the SSID that we just created. We can do some additional configurations. Let's say that I have different ssids, for APs in a specific site, but I don't want in a specific area like it could be a public area to propagate my corporate ssids. There are some filters that can be done.16:31Through tax and are part of the AP zones. Same with RF settings.16:52The profile, of course, needs to be assigned to site because I was, as I was mentioned at the beginning catalyst center is site centric from this point of view. And from here we can include those additional configurations like e.g. the feature templates.17:00Even CLI templates that I haven't mentioned it, let's say that you have something really specific that you need to include in the configuration and it's not something you can add or configure through the UI, you can always leverage a CLI template if that's needed.17:17We have some advanced settings as well. E.g., in this case, it's about the tax. When I was at the beginning I was saying catalyst center tries to abstract you from maybe the way the controller works so that you don't have to pay attention or take care of these details. But let's say that you really want to do that because.17:32E.g., for the profile tags, catalyst center is going to create one per floor and there maybe NO need of that in certain building where you.17:54Really handle the topic and you just want to do it yourself to be more efficient from this point of view. So that's possible, that's not mandatory, but if you handle, if you want to handle the tax because you have the knowledge and you prefer to do it, that's totally possible. It's, it's another option you have there. Only guidance will be let's.18:05Decide if you want to handle this topic or you do it, but try to avoid the, the mix.18:25And well, this will be from design perspective, but we have been showing the workflow on the UI. Of course, this is a 1st level of automation because you are kind of setting your intent and building the configuration on top of that. But if you really want to automate probably at some point you will be.18:33Using APIs to make it like a really automated process. We are highlighting some APIs here for what we have described, like e.g. creating the SSID. This is just for reference. The APIs are there to fully automate these processes. You can check on the APIs on the developer toolkit under the platform.18:53Menu?19:13And you can also give a try to the APIs from this page. So kind to do a recap here, we have been talking about tags, profiles and wireless LAN controller config models. So basically, you know that in the 9800 we have the.19:13Different tags. We have the RF tag, of course, associated with RF properties of the network.19:33We have the site tag where basically we're going to see if this is going to apply to flex or is going to apply to local mode. And we have the policy tag for everything related to SSID and SSID properties. When we think on catalyst center and what we have been explaining so far.19:39How Catalyst Center gets here? In terms of RF, we still have the RF profile. We have the basic RF profile, we could add some AI on top of these with different capabilities like ARRM.20:00But this is a separate story. The network profile that we have been describing so far is going the way, it's going to be the one that is going to take care of these and it's going to, as I was mentioning in the advanced settings is going to deal with everything related to the tax. The moment the.20:14Whereas the controller and the access points gets configured, this is going to take place. So let's briefly see an overview of what we saw. As you may notice here we have some timer for reference. This is our three.one version of catalyst center.20:31A bit of change in the look and feel of the colors to align it more to other platform solutions like Meraki and make it more consistent.20:51From network hierarchy to do a a summary of what we saw in the slides, we have our three plan access points over there different network settings that could apply also in some cases for, for the wired portion, but focusing specifically in wireless, in SSID, we could.20:59Simply do the next, next, next giving a name enabling the SSID and putting the security settings we want for the, for this SSID to work and we are good to go. In this case we are also going to include the AAA, from the eyes.21:19And from there, do the the small tweak that we were mentioning about the session timeout. We could add some feature template on advanced study configuration and here the important point of doing the network profile.21:38Associate this with a network profile that is going to be the one that ties everything together and from the network profile, if you also go a bit to the configuration we are assigning to a site that is something that in the slide we haven't done yet. And here is where we see that we could add.21:55Not only the SSID, the feature template and additional feature templates. Let's say I want to include cleaner parameters here. Finally, we have the tags that basically, well, we give it a name, we need to assign the the sites for.22:12For which we want those tags, and as I was mentioning, this is the recommendation. You do it, you let catalyst center do it, you have the flexibility if you feel comfortable enough to, to do this or you have been dealing with the 9800.22:28So, we have a bit plan and design. The next step would be to put it all these in practice. Christian, if you want to take it. No.22:48Regarding the timer you've seen little comment on that it we did speed up the video in many situations so it shows you the real time. We want to show you that it's possible basically to onboard.23:06Or deploy a wireless network at least in your lab with catalyst center in less than an hour for sure. So I know we are a little bit faster in clicking, we know where to go, but you should be able to do it in an hour, I would say.23:20Now that we have a design, we need the 1st hardware and this is our controller. There are multiple options to get the controller onboarded. I like the plug and play.23:39Method because it reduces the amount of things I have to do directly on the controller. When you boot up the controller, when it's coming fresh from factory or you did a full reset, it starts a PMP agent.23:53This PMP agent looks for two things, either DNS entry PMP server in its local domain or into the DHCP option 43 for plug and play. Wireless people know the option 43 very well because we use it also to point access points to the controller. So it's.24:09Either exclusive or you cannot use it only for one thing in your network.24:28But if you separate into different VLANs, you can do whatever you need to do with the different DHCP settings in option 43. For plug and play option 43 is a string which contains this little code and the IP address.24:33Behind that.24:54Large eye in the middle, so our IP address is 18 01:29 100 for the plug and play server which is catalyst center. And then the next step you can just play the 9800 via catalyst center plug and play. That's how I have a look how that works.24:55Basically, if you go to plug and play on Catalyst Center, which is under provision plug and play, you will see once they have contacted the catalyst center, you will see the controllers popping up.25:15And this example, I directly went with two controllers because I want high availability at the end. Some important fields you can see the status currently it's unclaimed.25:33But the device is ready to be claimed, you can see the IP address and you have all the other information in here. And one thing is the source which is the network. Please, when you go to the lab, be patient. Have a cup of coffee ready or a cup of tea, whatever you drink, but wait until everything here is.25:49Propagated with the right information. If you start the process too early, you might have to end up with something where says NO, I can't continue or we have to do it again. So be patient until you have all the information and then start the process.26:09Select the devices, claim them, sign them to a site, can give them the name, and as I will do HA, the name of 2nd one will anyhow disappear once we paired them.26:28But for the beginning we have to assign them. They both got a DHCP IP address already and then you have to assign a few things. The controller needs a basic configuration, right? And maybe you want also want to assign.26:47An image, so we directly upgrade them to the right version you intend to use. What are the basic information we need? We need the management IP address, so the wireless management IP address.27:02The subnet, the gateway, and we have to select an interface. In my example, I'm using the virtual cloud controller, P 9800 CL software, which means I will have only three interfaces, which is the service port on gig one.27:17The traffic interface or general interface on gig two and the HA interface on internet three. It's virtual and everything, so don't get confused yet that we are not working with ten gig interfaces or something.27:37You do this for both, I gave them both the IP address 10006 and seven and continue from here. We get a summary, we can go through it, have a look at it, go back if you want to fix anything.27:53And then just deploy the configuration. So we claim the device. It starts with onboarding and we can monitor the onboarding process and see what's currently going on. When you click on the device, it will start with the details and switch to history here and you can see what's currently really.28:09Happening on the device. So in my example I'm not doing a software update, so it gets a little bit faster for later for the video. Then you will see the device are provisioned and orange.28:29Please don't be patient until it gets green. If you now want to search for the device in the inventory, it's not there yet. So wait a few seconds until it gets green.28:45These things of being unpatient usually only happens in the lab. In the real deployment, you wait any of your waiting times which should take you a little bit longer and you're not that trigger happy, but in the lab, I often see people being a little bit unpatient.29:00And not waiting until it really happened. And that can be frustrating I know, so have a coffee. Let's have a quick look how long it really takes to onboard two devices. So we.29:16Did need the less than 5 min to create all the settings that was done with Java, and now we're going through the plug and play process. Entering the names, assigning them to the site, typing in the IP addresses.29:32And I know I'm fast in typing, so it's usually double the speed minimum what we're doing here. The other device for HA later, NO template.29:48Just let's preview what we are going to do, then continue from here. Now just waiting and this is something I really like that I don't have to be actively now on the controller configuring things by hand, so everything is done with just this.30:04Small number of basic information. I can just monitor what's going on. I see it's provisioned already. Wait another 30 s and then it took usually turn screen. So wait for that for the 1st sync, and then we continue.30:24So let's go to the inventory, simple filter, and here are the two controllers on boarded. There's 1st provisioning going on, so that's why it says sync stopped. So before you continue with anything, make sure the devices are properly synced and managed.30:43Like, it's happening now. You see the HA is already fully managed and the other one will switch with the next refresh. So now it's time to continue 16 min on the clock meanwhile. And most of the time was waiting meaning.31:03Already. If you can't do the plug and play because of some network restrictions, you don't want to have DHCP running in that network, e.g., you need a basic configuration. A host name, you have to have the admin user and the enabled secret set. You should set SNMP and network.31:21The interface configuration should be ready and you have to have a wireless manage interface up. Catalyst center, by default goes to the wireless manager interface or the controller to manage it. Wireless country code must be set and you should have reloaded the device once before.31:42Onboarding it. If you use a day zero workflow on the controller, it creates, it asks you, hey, you want to create an SSID and you want to have a AAA configuration already, I would suggest to remove it before discovery starts. So go on the GUI of the wireless controller and remove.32:03Of these settings anyhow, it will be pushed later, your design, don't use it for anything productive, I would say. Not when you're using catalyst center. And of course, as we say, we want to automate something.32:22We have APIs also for the plug and play part. Just go into developer toolkit, search for the plug and play, and here pick just three examples to claim the device, to get a device history to add a device into the table. That should allow you.32:40To really onboard the devices with external scripts. I want high availability. I'm not happy with just one single controller, and I'm a big fan of high HAS also.33:00Stable switch over. Just a quick recap, we have an active controller, a standby controller, and they are connected via the redundancy port and synchronizing their database.33:16If one controller fails, if the active controller fails, the standby takes over, we have a depending on the scenario sub second failover, so you're just losing one IP packet and that gets then resent because of the protocol anyway.33:33How to do that. Both controllers are in inventory, they have to be the same type and the same software version. If I select the 1st one, I can go into the actions menu, select provision, and configure WSCHA.33:50It gives me a choice for the secondary. In my case, there's only one available, so it automatically selects the right one. It only allows you to select the same model with the same software.34:08For the cloud controller, we can select the interface, but for a hardware appliance, there's NO need to select it. There's a dedicated support in hardware, so you will not see this select primary and secondary interface.34:22The redundancy management IP address my IP is important, so just enter it. The original IP address, the seven of the controller will disappear once we configure the fully HA. Of course, the controllers will reboot doing this.34:39Here's the warning message, and then it's basically waiting until it's done. The process works in the background, provisions both controllers, reboots them. The secondary controller becomes unreachable for a while.34:57And once the sync is fully completed, you get this little icon here behind the window which tells us this is a pair of controllers. They are changed to each other. And you see the status what's currently the status of the sync which says duplex here, you see the serial numbers of both.35:16Processes.35:36And the RMI IP addresses. What's happening on the controller? Now we have only one IP address reachable, which is the six in my case, which is the active one, the standby one is here. You can see the RMI IP addresses.35:37So this is the redundancy status monitoring page on the controller itself, and you can see what has happened.35:57Yeah, let's have a quick demo here, two, three.36:05Here we go. Both controllers in the inventory, provision, pick the controller, pick the right interfaces, give them.36:25Proper IP addresses, they have to be available as you are a little bit in trouble select now to go ahead and then it's just a little bit of waiting again time for another cup of coffee.36:40Yeah. You can monitor the process under the monitoring section you see what's going on and then.37:00Basically, it takes a few seconds until both have been rebooted. Second one, 1st one becomes unreachable, you see the little icon already appearing in orange not done yet, another simp, which takes a little bit because the secondary also has to reboot completely.37:15Think about how many times of real interaction we had. We had the 5 min for the design. Yes, the access point maps have been there already, but all the other time until now was mostly just waiting, and this is something I really like, why we are doing this.37:37Yeah, it's a great way of getting a coffee. Because things take some time, controllers have to reboot. Access points have to be, have to boot. So it's something like ten to 15 min for controller reboot and 4 min for an access point to boot.37:57What happens if something breaks? This icon turns red, and you can run a H ASSO analyzers. This is the machine reasoning engine in Catalyst Center. Let's do this.38:16It goes through a few checks and conclusion five, let's see what it says. Standby controller is in HA removed state. Yeah, I know.38:32The up here link is down and the RMI link is down. Yep. Please verify the standby controller power source appealing when you give me a network connectivity. What did I do? I just did shut down the virtual appliance of the of the standby controller, so this guy is right and telling me what has happened.38:48This is something for events that happen where Catalyst Center might not have a event itself already. You can create from anything that sends to your syslog. You can create an issue based on that.39:10You have the list under assurance, issues and events, you go into the events, you focus on the wireless controller, and you can see here the syslog events we received. Standby lost, true. Link has changed yep and the dual active has changed.39:30There's a problem. You can select these messages and build a issue based on that. You open the event itself and on the top right you have a button create an issue, which allows you then.39:46To define what you want to do with that. So 1st you create the issue, you enter the syslog details, which is severity facility and nanomic. And then you basically say, what do I want to do with that?40:03How often do I want to see this message until I raise an alarm in a duration of minutes? What is the syslog message itself? You want to enable it, you set a priority and you set notifications. So if there's anything.40:19Happening on your devices where Catalyst Center is not giving you an issue from the global profile, you can enter some user defined settings there as well. So whatever is important for you, coming in as a syslog message or as an MP trap, you can create.40:35An issue based on that. Once the controllers are onboarded, we have to provision them once. Not all configuration is happening during day zero during plug and play, so there's one step of provisioning required.40:54You go to provision inventory, select the device and say provision provision device. The full site assignment will happen, but manage it unless you already have it based on plug and play.41:12You have to set the managed IP access point locations, the interfaces, the model config and the configuration are pushed by this. This is important. In the view of provision inventory, there are multiple.41:27Full focus is available.41:47And this helps you ordering this table here. So if you deal with software, select the software image focus. If you deal with provisioning, select the provisioning, which is here. So select what you are seeing here because when you select provision.41:50It will show you the provisioning status here in the center. Let's provision the device and again a short workflow. This is the active controller for these two locations.42:08As even I love HP HASSO, which allows me to have a stable switch over the access points and a very, very fast switch over for redundancy. There might be still the need for an N plus one redundancy.42:26And this is how you configure it. You define the primary location this controller is managing and you define a secondary location. So this is primary, secondary controller setting for how you do it in Catalyst Center.42:42There is NO 3rd controller concept here. We only are dealing with two because that's most of the time enough to cover the use cases. Rating the interfaces, my client interface.43:00On VLAN two, the cleanup configuration and the advanced SSID configuration is added here and one little comment on CLI templates.43:14CLI templates are part of the network profile. If you have your 9800 in a data center location, I see it very often that there's anti artificial location for data center stuff in catalyst center, which is ok. But then you might forget to assign.43:29The wireless profile to this location because it's a generic or artificial location you are using and your data center, you're not taking care of it as a as a full site. You just put it use it there to put your devices, and then you forget to add a wireless profile to this site.43:48In that case, CLI templates will not apply to the controller. So you have to have your controller in a site where the network profile which has the CLI templates is in. Summary, click next.44:07And then you provision your device, wait a little bit until it's done. And again, you can monitor it under activities at the task, you can see what's really going on here and currently happening, what has failed if something has failed.44:24Provisioning, currently configuring with the right focus here and then going back and everything is green and happy and successfully done. You can see what has happened again.44:42And then what do we see on the 9800? So switching again from the GUI of catalyst center into the GUI of the controller. Now we see triple A things have been configured policy profiles have been configured and wlans have been configured.44:57What we are not seeing yet are site tags. Also for this part of provisioning the controller, we have the APIs available.45:15What's missing to build a wireless network, I would say access points. And again, plug and play is your friend or can be your friend. But.45:361st, there's only one option 43, which you can have in a network. So either you're using the option 43 as a option to point your access points to the controller, then they join the controller and will show up in catalyst center.45:52Or you use the plug and play process, but then you have to change your option 43 in that segment to use the plug and play parameters more or less the same process, but.46:13Let's do something different. With the controller, we booted up the controller and the controller contacted catalyst center automatically. Now with access points, the amount of devices usually is much higher, so it's two controllers you bring in so easy to type.46:31But thinking about hundreds of access points or at least 50 or ten when you're building a, a new floor and designing new access points to it, that becomes a little bit lot of typing. So I prefer working with tables.46:50And there are some method which we call bulk adding, and there you have a CSV file which has the syntax what you see here, which allows you, as you see, you enter the serial number, you have your name of the access points so everything is there.47:09Automatically onboard the devices once they come online. So imagine a box of access points, you barcode scan the serial number so you don't have to type them, you get their names, you assign them to the site, and then you have your Excel sheet.47:27You change your access sheet into into a CSV file and upload it here to Catalyst Center. One little thing, once uploaded, you have to select the devices and import the devices, please select add and claim because then everything else is happening automatically. If you just click add, you still have to.47:43Claim them.48:03Keep in mind the access points are not online yet. They are still in the box. So I'm adding the list. I have pre populated the device names here. This is the claim process now, and there's a site assignment already also coming from the CSV so you don't have to do anything here. Just click next.48:05You are asking for the RF profile because this is still a per access point setting. Once done, review the configuration and you see the access points being listed in the plug and play table.48:26You see the device is claimed, the state is planned, but it has never contacted Catalyst Center yet. One small difference, the source now is user because a user or the API call added.48:46The devices to the table. When we did the plug and play for the controllers, it was network, so the network device itself contacted the catalyst center and showed up in the plug and play table.49:01So now I'm saying giving the box to the installer guys with the access points and I lay back again, maybe another coffee, and once they come online, you can see and still monitor the process. So you see them here, they come online, they have been plugged in powered on.49:19And they contact catalyst center, you see the IP address.49:39And then the workflow is executed automatically. Again, just wait until it's finished. Monitor the status again, so everything more or less the same. The access points are also for a short time in the provisioned orange state, so not done. So wait until.49:43Everything gets green.50:03Switch over to your inventory and you see the access points are done in there. You can see what has happened, what has been configured, have a look at the access points. So switching directly to the GUI here on the controller. We see the name.50:05You see the location, you see the access point mode, we see.50:25The policy side and RF text and some other best practice settings have been done. Now the access point is operational back and back to the center, let's look at the map.50:30We can see the both access points AP one and AP two are online now. You see the signal is there, so we are good and green. As always plug and play for access points uses the same.50:46API calls as we are used to, for the controller, so these are the same calls as different devices. Short demo, I think we are on something like, yeah, not fully half an hour done.51:01It takes a while to get the table maybe, so not really counting that time here, Importing the devices. Select them and please click add and claim question. Yeah, I did that.51:18Going through the quick claim process. So there's NO difference in this process of adding two or ten or 50 access points. It just will show up in the plug and play table, and that's why I like this process. If I'm using the cap web.51:34The access points is joining the controller and they have to enter all these information with a different method. So in the back you see the console of one access point will be booting up. You see the discovery timer DHCP discovery is kicking in.51:50Then you see the addresses being populated, NO three six in my network, behind you see the access points have contacted last contact center already, so they are talking to each other.52:09Onboarding process going on, look at the history, day zero conflict generated, everything done after a while, executing the workflow, waiting a little bit, and after a few minutes, this thing comes online.52:26Slowing down, changing the view, let's have a look at the access points itself and checking what has happening on the controller. Automatically.52:48It has been provisioned, but this is something happening in the background automatically. Once access points are coming online, there gets happens a provisioning on the controller. So I would say bringing on two access points in your lab.52:58It's really done in less than 40 min in our example. Maybe you need to believe it longer, but you should be able to do it in less than an hour for your 1st job. I think. Yes, thank you Christian. Let's skip.53:14Going, let's continue with this. So basically we have been the we have been reviewing the greenfield scenario. Now we're going to move with the brownfield scenario, so.53:36We have the two different the two different situations. Some from Brownfield's perspective, basically we already have the controller that you probably were already configuring before having catalyst center or before onboarding into Catalyst Center Center.53:47Just to give you some examples, we have here controller in production with access points ssids. We can see some tag here. We have all the different options of configurations available, and this is just.54:05A quick comment, not so much to focus on the feature itself, but to focus on one difference that I would be highlighting in in some minutes. So here, e.g., we have the possibility of assigning tags to access points based on some regular based on the name. This is something that has not.54:23Been implemented this way in what we have been seeing so far, but remember this and we will.54:43Come up to this point in some minutes. So there were different questions on Brownfield in in the Q and A and this section is more aligned to those questions. Basically, the 1st thing if we have already a configured wireless line controller, we need to add it onboard it into Catalyst Center.54:50And in order to do this, we could add it, we could use the discovery workflow that is part of the tools, basically, with a range of IP addresses, e.g., but also a single one could work as in this example.55:10And what we need to provide are credentials, basically, once again SSH, with privilege 15, SNMP read or SNMPB three and netconf with port 08:30.55:24The idea well of course center to be able to connect to this and you can include as part of the workflow the assigned to site. This could also be done later, but it can directly be done here. This is not provisioning. It's just assigned to site.55:39We can keep going, have the summary here, and once this is done, we are going to see the results if there was any problem with any of the credentials we provided. As you can see for this use case HTTPS is, is not mandatory, it's not required.55:57So once we have this, of course we can also launch the this process from the APIs. But well, we have the controller in the inventory for sure having assigning to site, having the access points into sites, we're going to have telemetry assurance information. But what about the confi.56:14That is what we have been discussing so far.56:34So regarding the brownfield scenario, you may remember this learn device configuration workflow, if you were one of those customers that was looking to say, ok, I onboard my wireless LAN controller. It has already has some configuration, I want catalyst center to learn this configuration and then keep doing change.56:37Just from catalyst center. This was a workflow that was developed some time ago. It was tested, it was in beta for some time to be tested. But as you can see from the slide, this is going to be deprecated. So it is deprecating 237. So it's NO longer the way to go. Basically, just to say in a summary.56:57The configuration that was done from the wireless line controller need to be much how catalyst center thinks the configuration and that was not flexible enough for how a wireless LAN controller could be configured, it was becoming complex, and also you really need to have a deep understanding on all the intent.57:17A configuration, how it works in catalyst center to then be able to use this. So.57:37This was a stop, that's why, it didn't continue with enhancements, but that doesn't mean that we do not longer have a solution for this. Instead, a new workflow was developed to try to overcome the difficulties that were seen, and this is what we call the per device configuration for.57:45For Brownfield that was introducing 237. Basically from the inventory you can access the device details for any device and in specific for wireless, you will see that there is this option of enabled per device configuration. This basically what it does is.58:05Telling you that if you enable this mode, we're going to learn the configuration through a resync. And from this moment you will not be able to provision the wireless LAN controller, but this makes sense because if you already have your brownfield, you probably will not need to provision the wireless LAN controller anyway. It's just to set up.58:25The expectation. So what this is going to do is to learn your configuration, grab it. And from there you will see that a lot of different menus are going to appear here in the configuration.58:43That are not available until you actually perform this action of enabling with your configurations that you can initially just have for visibility, but also you could of course do further actions edit, add new configurations.58:56So this is a new feature, this kinds of response to some of the questions that were done by some customers during the session. This doesn't have an impact, and there is something new in in three.one it was introduced about the possibility of cloning.59:14E.g., in this case a profile from another controller to this one. This of course tries to reuse some of the work you may already have done in, in another controller to prevent having to do it from scratch again. As of today be aware that this.59:33Configuration is per device, that's why we emphasize this in in the title.59:53Those configurations are not going to be keep in sync, but it's the 1st step. We are presenting what we have available as of today. There is more work from the product to keep improving in this kind of scalability approach.59:58Okay, so another really common question is, what happens if I need to do a change from the controller itself? In this case, this is not a limitation. I mean of course if you have enabled the configuration from here, probably you want to do it from here, but.01:00:13If you need to do some configuration that it's also available in Catalyst Center from the controller itself, you can do it. The recommendation would be to also do a resync in Catalyst Center after that to grab the latest configuration and avoid any conflict. But it's much more flexible.01:00:33In terms of, what we used we what we have with the other way of operation. Remember that a small comment that I did on some configurations that were from the controller but maybe were not implemented that way in Catalyst Center about being able to ***.01:00:50Leveraging regex. This was just an example to show you. We have a lot of parameters here. It's almost all the configuration of the controller. You will see these new screens, and basically it's the same experience that or really similar experience to what you have in the controller to make it easier for you to actually.01:01:12Use this to adopt it to learn it. So, you can give it a try as we mentioned starting in 237 and some capabilities maybe not there yet because are part of three.one but the workflow itself it's it's already in 237.01:01:30Okay, so what about the access points? Regarding the wireless line controller, it has already joined access points the moment where we onboard it into Catalyst Center is also going to bring with her, with it, the access.01:01:47Access points that are part. So basically the next step is to assign the access point to sites. As you can see, this is a pending task we have to do. We encourage you to do this because from assurance perspective, from statistics per site, this is valuable.01:02:07So basically we need to run the workflow of assigning to site from inventory. Again, this is not provisioning, it's just assigning to site. And from there we can then go to the maps in our network hierarchy and we will see that these new access point.01:02:25Points in this case we see them directly here as unposition and operational, we can click and drag them to to the map.01:02:45And from there, of course we are also going to be able to edit position information, e.g., and have them the operational heat map. We could also leverage plug and play for this situation of.01:02:54Access points in brownfield. So Christian, Christian I think you're mute. Thank you.01:03:12Brownfield plug and play. The situation we do have a fully configured controller in production. We have the controller already discovered by catalyst center and we want to bulk at new access points.01:03:29After adding the controller, we can go and say, ok, this is a per device configuration, this is a way we can continue configuring the controller from catalyst center. For pluck and play of access points.01:03:50In brownfield, we need some special information. To get them pushed to the access point, we have to create a CLI template. So we go to design CLI templates.01:04:05This is not really a proper CLI with iOS XE commands, that's the way how it works. So just follow my guidance here. It is an onboarding configuration, so it has to go into the project with the onboarding configuration. Anything you want to use for.01:04:22The zero plug and play has to be in that project.01:04:41So don't delete the project, don't modify it, just use it and drop all the templates you want to use for onboarding there. It's a regular template, deployment type doesn't matter in that case. Ginger or velocity also doesn't matter in that case.01:04:45But software type is important and please NO questions on that. The device family is wireless controller. Follow this guide, follow the settings, don't ask questions for this one. For that one you might. Parameters.01:05:01I used Ginger as the language, that's why my double woven brackets are the variables here and are highlighted. If I'm using that catalyst center then will go during the process and ask me what I want to fill in these places. It looks a little bit like.01:05:19Like a Json, even the text is not fully correct, but it looks like a jason. And you might remember that a little bit from the old plug and play on prime. There was also a way to have this file which then gets pushed to the.01:05:38Control to the access point. What you can have is the controller name, 1st and secondary, the policy tag site and RF text. So you can even go group plug and play and assign the tags to the access point. If that's the preferred method, use it.01:05:56The Required is definitely the primary controller IP address. That's all we need. And you don't have to use a variable, you can directly enter your 10006 in my case here into that field. But what if I have.1X on my switch ports?01:06:13Yep. These parameters are also available. You can add sort bundle there and everything in here in a base 64 encoding, e.g.. So everything is there what you need. I did put in the comments here into the text.01:06:33Of the template, don't do this, you have to remove the white text here. That's why I had this little note here from in line nine to 14, but that was the easiest to get it on screen.01:06:51Next to jason, please. We are still working with the CSV file, but now we are not assigning the site. So do not configure a site. You can have the name and we I don't like fixed IP addresses and access points anyhow, that's why I didn't put any IP addresses.01:07:06Import the file, add and claims the same as before, but do not assign a site. Just continue without doing that. Even it says recommended, we are in brownfield. We don't want to do that. But we need to assign the configuration, which is the temp.01:07:27That we just created. We selected from the dropdown, we can see what I've in there. In my case, I directly had the IP address and the name entered in the text. You can still see the text which is going to be pushed.01:07:47Ready to power on the access points. So every all the information are there in Catalyst Center power on the access points and just let them go. Wait for them onboarding processes running and after a few minutes they are provisioned in green.01:08:07I like assignment either doing it through the template, so site text policy texts and all that assignment through the template or do it via regex questions on the controller directly.01:08:24Inventories here, Map is here, the two access points are coming online and start servicing on their radios. We do have enough things we can do with the access points.01:08:43In the workflows. So Brownfield is there is important and there are a lot of functions we can use. So if somebody says, I only can use assurance, that's not really correct. There's way more you can do besides assurance and lot of automation.01:09:01You just learned to onboard a controller for poor device configuration. So you can still use configuration from catalyst center just different. You can't use the internet, ok? But you decided to manually configure your controller. You can continue doing that and now you have two options doing it.01:09:20On catalyst center or the controller directly just keep them in sync. You can use plug and play to onboard new access points. And we have workflows available. I really like the access point refresh.01:09:39I like the replaced device, which is an RMA case, but this is not for brownfield, to be honest. I like configuring my access points, maybe I have to rename, change some settings or radio parameters.01:09:57And I have the AI enhanced RRM. We are not covering replace device and AI enhanced RM, but we are having a look at the access point refresh and the configuring access points.01:10:13The refresh. What are we doing? We are replacing old access points in my example here in the in the slides is 91 thirties and changing them with whatever 9170 you have in place and you want to replace them.01:10:30The prerequisites, the controller and the old APs are managed by Catalyst Center, and the old APs are assigned to a site. In my situation, I want to replace the access point without pre assigning the serial numbers.01:10:46I want to label them while they're getting installed and keep the access point name. I know some people like to have the access point type somehow in the access point name. I'm not a big fan of that. You saw my names are only AP 1234.01:11:06And of course you might want to encode the building, maybe the floor and the name, then you have something like B one for building one floor zero, and then-and the access point number. That's the easiest way because you don't have to invent new names for new access point types and you can keep it all.01:11:23For me, an access point is just a position or marker.01:11:44On the map. What type behind it is, doesn't matter. Important, the AP has to join the same controller as the old access point. And I want to run CDP on the access point port.01:11:48Which makes it easier and nicer. We have two access points. We want to replace them. 91 twenties in my example and I add them, I go to the workflows.01:12:08Select the right workflow for the access point refresh, and then give it, give the workflow a name refresh 91 twenties. I take the assurance per device configuration use case. Again, here's the, what you need. New access points should join the same.01:12:28Wireless controller where the old IP was provisioned associated. This can be done with the DHCP cap web option. So we are not using plug and play here. We're using the DHCP cap web option so the new access point joins the controller automatically.01:12:48No need to configure anything on the new access point. The box with the ten access points is still closed. I select the group of access points I want to refresh.01:13:08They must not need to not be provisioned for that flow, and I would like to auto detect the access points based on the switch port. And as you see here, I see the CDP neighbor.01:13:26In my case, it's an ISR router with a few PoE ports, but I can see the CDP neighbors, and these CDP neighbors, and I saw a question in the Q and A on that, it doesn't have to be a Cisco switch, it just has to talk to CDP.01:13:43The information is via a show command on the controller. So you can, we have the information and I think they are also visible in the device three 60 even if the switch is not.01:14:00Cisco are not managed by Catalyst Center. What's happening? Still the boxes are closed, I'm starting the workflow here. Configuration will be copied from old AP to new APs, which includes the access point name.01:14:18I get my summary which gives me the new device name. I could potentially edit them if I want different names there, but I want to keep them. Now I'm giving the box to the installer.01:14:37And tell them, just replace access points. They ask which for which I say, take the old one from the ceiling, look at the label, put a new label with the same name on the new access point, plug it in. We can now exit the workflow, even nothing has happened yet.01:14:55We cannot click next until all access points in the list have been refreshed, but you can exit the workflow, NO danger. It will continue running in the background. Here you see it, it's still there.01:15:14It's in progress, and now I'm sending the installer to the site. Quick demo, 123. Old access points managed. Let's have a look at the map, five and 6901 twenties.01:15:31Starting the workflow, access point refresh, I know what's been in there, 91 twenties, assurance use case, I should join, so my current DHCP option.01:15:52As cap web and pointing the access points directly to the controller. I saw the CDP network neighbors here, I start the workflow. I just selected the access points I want to replace. Nothing more has happened.01:16:08I didn't enter any additional information.01:16:28I'm Plugging the APs, new access point booting up, you can see here, it will join viab, the controller, and I see why booting up, it's getting the the text already.01:16:33Process the default tag. I see a mix of access points for a short time in the inventory. After a while the old access points disappear, the new access points are there and replaced.01:16:51From the point I clicked to start the workflow, the administrator had nothing to do anymore, so NO work to do. This is extremely nice especially on remote sites, e.g., you sent the installers there, you had the job in the back.01:17:08Background running and there's nothing you need to do.01:17:28From an admin side. The network comes up automatically and it really replaces your old access points with the new ones. The downtime per access point is something like 10 min and if you need a software update, yeah, ok, it can be 15 depending on.01:17:32On the, on the link you have to your controller, but the installer doesn't have to call the admin and say, hey, I have installed two new access points. Can you please configure them now? I have one customer who is actively or was actively using that to refresh their access points.01:17:48And they didn't run CDP in their network and just because the workflow was so comfortable, they enabled CDP. They were using LLDP, ok? But we are unfortunately not supporting LLDP for that workflow. We need CDP. They used it that way, enabled it just.01:18:08That workflow and that shows me a lot that this is really a cool thing. What if, the new APs are pre labeled? Maybe you need your new new names because your methodology is containing the names.01:18:29Maybe you are mapping your serial number to the locations. So you define which access points goes there. So the IT department is pre labeling the access points. So installer has to take the access point of the box, looks hey this is access .5, looks at the ceiling and rep.01:18:49Places access .5 with that. We can do that. Still the AP has to join the same controller and the old and new serial number from this APs need to be mapped now. So we have to tell catalyst center what needs to be mapped.01:19:09The access point never, the new access points never touched the network yet. We only know the serial number. So we take the access point out of the box, scan the serial number of the new AP, and then.01:19:29We assign the name to it. So we turn off this auto detect and we import a file again because that's what I like. So you can download a CSV which has the information which is already known and then you add the information. So in my case.01:19:43I'm going from access .5 9120 to a new access .5 and new with this new serial number. You don't have to get the system the new type because this is already there the information here, you only need the new serial number.01:19:59It's a pretty easy file again, but mandatory to have the new serial number. What happens during the workflow when you connect the devices?01:20:17One step back. Once done, you click next, the workflow starts in the background, the installer takes the new access points, installs them, and everything happens automatically again. The 1st time the access point touches the network is the point of time when the installer takes them and plugs them in.01:20:33No need for any pre configuration, NO need for staging. Okay, I want to monitor what's going on. What are the activities? Go back to the audit log. I showed them the audit log a few times to you. What do I see?01:20:53I see the old IP with this serial number was deleted, a request sent to delete this AP, so all this is happening in the background so I can really see what's going on and what's happening and monitor it carefully and see if something fails, why it failed.01:21:09The audit log is really, really helpful. What haven't we talked about yet? Again, also available for brownfield, stuff for image management. Oh, up to you.01:21:29And you're muted. Now that's my time to be muted. Thank you. So another workflow is about software upgrades. Again, this is not something new specifically useful in wireless especially when we have new access points being supported introducing new releases. You can check.01:21:54Software version in multiple parts of catalyst center including inventory advice details, and in this case we see the seventeen.fifteen.01:22:14If we have already market targets or golden image or standard image, we will see a compliance error here alerting that we still need to upgrade this device to follow our intent or to follow what we are standardizing.01:22:24And this was a feature that has been for some time in in catalyst center in 237 just to put some screenshots here. You may remember, you need to go to the sign image repository and mark the image there as golden. Then from the inventory you will realize what are devices that require.01:22:41Higher software upgrade especially if you are putting the focus view of software, have some readiness check on basic things we need to verify to make the upgrade successful, like e.g., available flash or being able to transfer the image through HTTPS, e.g.01:23:00Or, the other alternative we have. But well, at the end you needed to go through these different options and menus, mostly design and inventory to then launch the upgrade and also check the monitoring, check the status.01:23:21As we are getting a bit closer to 33.one this year, we also plan to show you a bit of the change in the workflow, NO changes in concepts from this. All the capabilities remain the same as 237, but we have another organization of the information.01:23:39Basically, we have an overview with different insights about devices missing standard image or golden image information on advisories. We can find this menu on the provision software image management to deal with everything.01:24:00Relates to software directly from here.01:24:19So basically, we can go to the images to go to the specific situation of a family. Remember we have filters in these features like per site per device family. We can get the information on the images.01:24:23Based on our synchronization with Cisco.com or we can import images manually if we need it. When we see this way, we basically are being told that we do not have defined yet a standard image.01:24:41We may have download something, but here we are missing some stuff, and this is bringing this is being brought by the synchronization with cisco.com. So basically we have different options. We can mark it as standard. We could also apply additional filters for.01:24:57Additional tagging, and the capability of differentiate versions maybe in a device family and site.01:25:15And once we mark an image, we are going to have some compliance results in this case, as we are matching the target image, of course, we are not able to do another upgrade, we are ok, but if we pick another version.01:25:25Like the 1718, then the situation is going to change. We still have the information on the image, the verification that can be done against the known good values to avoid any corruption on the image. And from here, we will see that the checks are in progress.01:25:40That we have the same readiness report that we used to know but also the possibility of launching the update process. So remember, we have two steps in this process. Distribution and activation are two separate activities where you can also perform pre and post checks.01:25:59Depending on how you configure and you can add your own if you want. You can decide the order.01:26:19How you want to execute that update if you have multiple devices, devices in parallel devices, one after the other insequential. You can enable ISSU if the device is eligible, if you have e.g. SSO and if you have, you are going through the right versions, the results.01:26:27So a matrix that is checked to do that, and of course the idea is to minimize the downtime.01:26:47You have here the scheduling of the different activities and also remember that you could delete other inactive images after activation. So, probably this is known workflow, but just to give you the new look and feel, then you can do the monitoring from.01:26:54Here once again with all the different steps for distribution, highlighting especially that the AP pre download process is part of the distribution for wireless, of course, and then the login on the activation.01:27:14You have the results of the checks as well if you have configured any of those when you were doing the activities, the configuration of the distribution and active and activation.01:27:33Okay, once again, you can launch this through APIs. We have also a really quick demo. This is mostly to show you the process that we just show on the slides. It's going to be really fast is to give you an idea of doing this in a real.01:27:48The device here we have our golden image already marked as you can see.01:28:08We are basically ready to go and, review the report and launch the workflow. With this, let's.01:28:12Go through these, we have this single device. We have enabled ISSU remember that for eligible devices, this is the moment where you enable this and.01:28:29This is a lab we are going to run it right now, but of course you have a schedule your activities. Then we're going to start monitoring the activity. This is a super speed up by the video because of course it's going to take some time, but just for you how to see how every step.01:28:44It's completed?01:29:04In that instance, we already have the bean distributed. Now we are starting to distribute the image to the different access points as part of this distribution process. And then, at some point we are going to see that as part of the activation, we are going to have the.01:29:07H AP upgrade reboots. But well, have the standby controller, the other one, and now we are going to see.01:29:27The result of this SSIU, especially here from this initial release to the target, and this is basically completed.01:29:46Let me go through the last workflow we have. We are just on minutes behind that. We have the configure access points that it's also another workflow really useful. Also in brownfield situations, basically you could do rename of access points. It's useful when you have to move access.01:30:01Points maybe to secondary worseline control in terms of high availability settings. You can also turn on or off led and do a lot of configurations in terms of radio. Maybe one interesting thing here that.01:30:21May get a notice is that based on the selections you do, you can create a template and save it in case you want to reuse it then for additional access points, not need to repeat the process. So basically you pick what are the access points that you want to do the activity based on the workflow confirm.01:30:36In this case we are going to change the name pattern, you can see this is the original name. This is the new name we're going to put. We could also have CSV file. We could follow a specific pattern we define, and with this.01:30:57We're going to see some moment later that we have the new names in the inventory, the same, e.g., if you want to do some operation activity or disable the led in this case. So as a conclusion, we have been showing a lot of different functionalities that depending on your situation you could leverage.01:31:10Remember we have two scenarios, the Greenfield and the brownfield. Some of them, most of them are common or there are ways of implementing for both cases. But e.g. wireless line controller PMP, of course, it only makes sense for the greenfield. As in the other case you already have a configuration. Discovery applies.01:31:30Is for both configuration. There are options for both, even though.01:31:49There are different options as we have been sharing 1st part and second part of the presentation. Then you can configure HA in any case. Same with plug and play of access point, different methodologies but available for both scenarios. Swim also applicable, refresh access point just.01:31:54Highlighting that in the case of brownfield, the new access point also needs to be onboarded a part of the controller. RMA replace device we didn't mention it today, but this only applies for Greenfield for the provision controller, and then you have the configure access points.01:32:14What's next, basically to start monitoring the network, but this is something that we are going to review in our next session next week. So as a key takeaway, as we have been mentioned, there are a lot of capabilities, not only assurance for brownfield, both for Greenfield and brownfield.01:32:34Ability of doing configuration and automation to avoid doing repetitive tasks and simplify as much as possible.01:32:54You have been asking questions, feel free to keep posting questions in the Q and A We are going to share some resources so that you can also access later the recording of the session. But please, before you leave, the moment you close the session, you will receive a survey in your bra.01:33:01Closer that will pop up. We really appreciate your feedback. If you could let us know what you think about the session, what are the topics where you think we should go deeper and maybe prepare another session in the future as part of these regular webinars we do. And if you want to be contact one on one for reviewing something more.01:33:21Specific of your environment, you also have the opportunity to do it there. So with this, thank you very much for staying this additional 5 min and for joining us today, we hope you found it valuable and.01:33:41Well, we are ready to close the session. I hope you all have a really nice day. Thank you very much Christian and the team for, presenting today. Thank you.01:33:55