Catalyst Center 3.1 – upgrade process to leverage the latest features

Okay, hello, good morning, good afternoon. Thank you for joining yet another.00:10Cisco Catalyst Center expert inside Series webinar. Today we will talk about Cisco Catalyst Center three.one, the upgrade process for us to leverage the latest features. My name is Alex Girdes. I'm a customer success specialist and I will present today so.00:17Session.00:37Quick reminder as we do in our webinars, what you will see is best practices, is recommended practices, it's guidance but it's not something that you should do in your networks unless.00:40You take the decision, the decision, the business decision, the strategic decision is yours. If you need further guidance for anything that you will hear today, feel free to contact us. We will reach out and we will see your needs in a one on one session.00:58Choose.01:18Today's session is the 3rd in April's schedule. We had two on wireless automation and assurance. You can find the recordings in our community page and you see the link. Now.01:20We have a minor technical we have a minor technical issue with the community page and we will have the recordings in probably a couple of weeks. If.01:39If you want the recordings earlier, you can again request them.01:59In the post webinar survey and we will we will send you the links. Sorry for my pace. I see that there are a lot of questions and messages in the chat.02:04My comment on that is, if you have any questions, please post them in Q and A window and since I'm alone today, I will try to I will try to answer them at the end. Don't use the chat unless there is a technical issue.02:25I saw a message that someone cannot hear me.02:44What I appreciate is if someone can tell us if I can be heard. I think from my end things are good if ok you can you can hear me. Thank you. So you are muted questions in Q and A I'll try to answer them all.02:48Well at the end, if not, I will revert with emails, answers and stuff after the.03:08Session. Our agenda for today bit on catalyst center scaling and form factors, we will see the highlights for versions three.XI would say, and then how to migrate step by step by step process. It's not.03:15The same as we have in the other versions but we will see how to do it step by step. If you can find Q and A, please use the three dots bottom right corner. I think you can find.03:34The panel there.03:54And then of course you can post your questions. If not right now it's impossible to do it so you can, you can use the chat for for this session. So let's start with form factor scaling and strategy from now on. We still have.03:57Single appliances, medium, large and extra large depending on your needs. We do have the high availability clusters and if we go with three extra large appliances, then we have three times the scale, so we can cover all.04:17Almost every need for every network and every organization. We also have the virtual appliances in AWS. We have the virtual appliance on prem VM.04:37With three.one version, we will have the appliance in Azure and we are also planning to have the KVM version in the near future.04:49Now, all these appliances can be seen in catalyst center, a global manager. This is a new product. You can, if you have many appliances virtual or physical, you can connect them to.05:06CCGM and you can have a single pane of glass. You can see all the data in CCGM. You cannot change things from CCGM, you have to go to the specific catalyst center appli appliance, but still you have a monitoring.05:25Single pane of glass. We can see Catalyst Center global Manager in another session.05:45If you do have questions on that, again, feel free to ask for a one on one session and we will contact you to to have it. These are numbers the system scale, I won't go through the numbers but you see that we can cover all types of.05:52Networks, the appliances that we the physical appliances that we now have are the DN three, the 3rd generation.06:12DN three HW APL is the medium one, the DAS L is the large and the DAS XL is the extra large. What happens to DN one and DN two? DN one is now end of life. So if you do have a DN one appliance, we strongly recommend that.06:22You find a way to replace it, to take it to DM three or a virtual appliance. DM two is end of sales.06:42It is supported until 28. But, again, if, I think it's better to plan the replacement to be safe and make sure that you have the most capable appliance for your network.06:52As we have the end of life and the life cycle for hardware, we also have it for software. So for software, the life starts with the recommended release when some.07:14When the release is, published we have it as a recommended release. Now typically we have twelve months until we stop the software maintenance and another twelve months until we have the last day of.07:28These, these periods can be extended and this is the case with the release 237X but as you see, we have the milestones, the end of software maintenance and the last day of support. Now, for the current releases.07:49We had the 2377 in 17 December 2024, and that was when it became a recommended release. In 5 June in 25 we had the 22379 as the recommended release and now the.08:08The RR is the 23710. However, all these releases are expected to be end of software maintenance by calendar, by end of calendar 26.08:28Calendar year 26 and the last date of support is expected to be in June 2027. So, we see that although of course the versions we.08:42Keep on working. The support will not be there. If something happens, you maybe in trouble, so this is an indication that we should upgrade to a newer version. Now what you see here is a phone number.08:56Naming scheme 2377910, this represents major.09:16Minor, minor minor and parts numbers for the new release we have, we soon have a global availability. We have a different scheme sorted if you like, a simpler. We have three numbers, so you would expect.09:24315323 or something like that. The 1st number will be the major release, which means significant market value something really important that has to do with the whole platform. 2nd number is a minor release and usually it.09:45Regarding new features, some new features and this the 3rd one is and.10:05In that case we have usually bug fixes errors and stuff like that. Now, before we move on quick discussion on strategy, so far we used to have catalysts and catalysts.10:15Center managing catalyst switches with catalyst licenses.10:35That's on the left. On the right we had Meraki and we had the Meraki dashboards where we could manage Meraki hardware with the Meraki licenses. Now, the strategy is to unify those platforms and to have Cisco hardware.10:39One hardware for both.10:59Approaches. Cisco license, one license unified license again for both approaches and a unified management, but this does not mean that we will have or we will not have catalyst center or Meraki. We will have both solutions, cloud.11:02Is Meraki dashboard on prem is catalyst center and we can have a hybrid approach where we can use both.11:22Now the difference in the one management is the in the fact that we can see Catalyst Center in Meraki and we can see Meraki in Catalyst Center. So we can integrate both systems, either way.11:30And we can have a single view in either of the platforms. The new thing it's in beta from November is that we can connect and integrate catalyst center in the Meraki dashboard and in that dashboard we can see the organization that we have in Catalyst Center and.11:47We can get information and we can have monitoring on that. Of course, if we want to make changes, we have to go to catalyst center, but still it's a single pane of glass for monitoring and troubleshooting.12:07What's also new and we have it in Meraki dashboard and is coming in catalyst center. We have it in beta in 23711 and we have we expect it in versions of three.X is the A.12:22AI assistant. Now, AI assistant, helps us understand network health instantly. We just ask the assistant in.12:42Natural language and we get responses, we get suggestions or we get reports, all sorts of things. We won't spend time on today, but we have a couple of sessions on AI in June.12:54You will get the emails and the invitations soon and in those sessions we will analyze amongst other things, AI assistance Cisco workflows and so on. So regarding catalyst center, AI assistant will help us in.13:10The client troubleshooting in infrastructures troubleshooting, network automation and and so on. But again, we will see those in the sessions in the upcoming sessions in June.13:30Now, why should we migrate to Cisco Catalyst Center except from the fact that the 237 releases are becoming end of software maintenance end of the year. We do have some really nice new things and regarding.13:42Think the platform itself we have a new operating system and this reduces in half the upgrade process. Also, we have a single backup storage. We don't need to have two places for one for automation, one for assurance, and also we.14:02We can have the cron cross version backup restore so we can back up in three.15 and we can restore in three to three or something like that. So this is an evolution for the platform. This will help us a lot on the up.14:22Great process from now on.14:42We have the site based, the site based role based access control. We are waiting for this for many years, I'd say. Now we have it and we will see how it works in in a bit. We also have rule based compliance, so.14:46We'll see that in a bit. Again, compliance certification for regulated environments. These are improvements in security and compliance areas.15:05User experience is enhanced by means of having a consistent look and feel across Meraki dashboard and Catalyst Center. The the new catalyst center view and the menu looks like the new Meraki dashboard view.15:15So they're very very similar and.15:35Things move, towards towards that. We also have reduced touchpoints and you will see how in the discovery example in a bit. And as I mentioned, we have AI and with this we get comprehensive visibility.15:39And troubleshooting.15:59And, we also have operational simplicity and sustainability. The most important aspect here is the energy management dashboard. We were asked for this and we now we will provide it in a version of three.X.16:01So a bit more on on those things regarding the backup and restore, as I mentioned in previous releases in two.X releases, you should back up something but you couldn't restore it in a new.16:20Version, you had to restore it in the same version and the purpose of that was to remax the appliance if something went wrong and use the same version as before the upgrade try. Now in three.x, we can actually.16:40Only back up in one version and we can restore in a newer one so three.523317 or something similar, ok? This makes the backup easier.16:59And we will see also the change in the operating system when we start the step by step migration. Now, a lot of features in the actual catalyst center application we have a site based we have.17:17The onboarding workflows you see the list here and the list is not even complete. We will go through the ones, the highlighted ones, the ones marked with but as I said, there are even more so.17:37There are lots of reasons to move to catalyst center three.X site based role based access control so far we had three roles in Catalyst Center, we had the admin role, the observer role and oops, sorry.17:53And, we couldn't, we couldn't provide access to specific sites, to specific users. So if I had three sites across the globe or across the country, an observer would see all the sites that maybe they.18:13Couldn't write, they couldn't modify something but they could see all sites. With the new feature, we now define.18:33Custom roles and access groups and this gives us the granularity and this gives us the capability to choose which sites can be seen by which groups of people.18:42Okay, so the site is an area building the floor, whatever we have in a center hierarchy. We have custom roles and access groups and the combination of those provides them access control to the different sites and the whole organization.18:57Enhancements in NetOps in specifically in onboarding device workflow. So far we had different places. We had the inventory where we could add a device or we could provide the CSV file. We had the discovery.19:20Tool and we could there discover devices.19:38Using different protocols. Now we have the workflow and everything is consolidated there. So, as you see, we have the method in the dropdown menu and we do everything from the onboarding device workflow. We can choose a discovery or a single.19:42Device or a CSV, NO need to go to search and go to different places. This is supported from 313 and onwards.20:02You will hear different numbers on catalyst center and I guess the question is, ok, but we haven't seen any of those numbers and that is true. We have the catalyst center in early free trial, so some of you may have catalyst center three.X.20:14Eh, but.20:33Here we present the the features and we just give you the version from which the features are supported. So if in the next month we have a version 315 available or 317 or three do.20:34Three.two.three, then you understand that all these features will be there and you will be able to use them.20:55We have a new software image management dashboard. The previous one was, a bit complex if you like. Now we have the tabs as you see and we have another view, we have the images, we have the devices that need.21:05Need to be upgraded and we also have the updates, the the status of the updates. So everything is in one page. You don't need to go from the repository back to inventory and see what happens with devices and so on. Everything is in one.21:24Section the software image management section.21:44We have the rule based compliance, so, what happens with this is that we can check configurations that have not been pushed through the process the provision process. So, so far we had the compliance.21:49The template compliance or the provisioning, and if we could, if we would push a configuration to the devices, we would then have a check on configuration compliance. But in many cases, we don't want to push.22:08We just want to onboard switches or controllers or devices in any case and we want to monitor them. With the rule based compliance, we can create rules and these rules can be applied and can be used to identify.22:25Configuration.22:45Violations in different switches, in different devices without the need of going through templates and provisioning and so on. Okay, so this adds to the compliance area and aspect in catalyst center.22:48Yeah. We also have a new approach regarding the grouping of devices. In the past we had the hierarchy, the, the areas, the buildings, the floors, and we should assign the the devices to.23:07Different buildings or different floors and based on that they would get a basic configuration, let's say NTP servers or DNS servers and if we wanted we could push templates and so on. Now with the campus network automation and the new feature, the, the one that you.23:25Can finding networks, we can create device groups.23:44And we can have in those device groups, we can have devices from different sites. And we can apply configuration to those devices. So an example would be, I have 9200 switches dedicated for cameras and.23:50I want to have a specific configuration for those switches and those switches are across my organization, so 4561020 different sites. I can create the device group and I can push.24:10This configuration to those devices regardless of what they got from the network profiles that they belong. Now, this is in beta but you will see it in version 313 onwards.24:28If there are features that are in beta and you don't see in your organization, feel free to contact us and we can arrange for the enablement of beta versions.24:47And this is how we create the network. We provide the name, we then choose the sites, the device groups and so on. And of course there are many steps but we are just highlighting the new features here. Now regarding AI OPs, we have the.25:01The energy management dashboard. We had a a PoE dashboard, but now we talk about energy and we have the energy consumption statistics by device type, by sites and so on. So it's an enhancement and it.25:21For probably it's more meaningful than having PoE switches and PoE devices and statistics on those devices. The integration with thousand eyes is simpler we had.25:42A couple of points that we had to visit in catalyst center in order to integrate and install agents and then create tests now with the new workflow. This is simplified and everything is done through a workflow and we start from scratch and we end up.26:02With a thousand eyes integrated with catalyst center agents installed and tests done. And so much easier integration with thousand eyes.26:22We get more information from ICE regarding authentication failures. So in previous versions we had the client three 60 view and we were getting errors, we were getting authentication failures, but we had to go to ICE to see what.26:39The problem was in the new version we now have the top ice failure reasons in catalyst center and we can see from ICE what has happened so we don't need to go back we we don't need to go to ice to investigate.26:57And as I said, there are a lot more features. Those are the most popular if you like but in any case we definitely suggest to have a look at three dots.27:18Whatever version will come soon and plan your migration as we will see it in the next slides. So, what steps are required? If we have a new deployment.27:32I saw that question when the version is going GA and I don't have an answer but what we expect is to see it in May.27:51So, take it as a personal view we expect to see it in May. It has been postponed for a few times. Hopefully this time it's not gonna be and we will see something in in May June frame timeframe.28:08So we have two streams here if there is a new deployments, you don't have to do something. You just you have the scale design the form factors as before and you start with three.X If you have an existing catalyst center deployment and you.28:28Want to upgrade.28:47Then, you have to make sure that your catalyst, your existing catalyst center is at 2377 or later. If it's in an earlier version, then you have to take it to 2377 or later because it's the version that we start.28:48Work with the.29:08Upgrade workflow, ok? Here I need to point out that DN one appliances are not supported with three.one. It has nothing to do with the end of life of the devices.29:10Three.one cannot be installed in DN one appliances. It's only DN two and DN three. Now, the upgrade is different and we have this call for this because.29:29We don't simply update catalyst center application and applications. So, you probably know that when we go to software management in catalyst center, we have the catalyst center application, the, the system application if you like and underneath we have the.29:44Applications installed and.30:04We have a new release published and we click the different buttons and we upgrade through catalyst center. When we move to three.X, we are actually updating the operating system that sits underneath catalyst center as well as Catalyst Center. So we have three.30:06Phases if you like three steps. We have a fresh installation of the operating system.30:26And on top we have the catalyst center. We have the conversion of the backup of the old version, so it's got it can be read in three.x. And we have the restoration of course of the backup in catalyst center. Now.30:32I want to quickly go to catalyst center and show you what I mean. So this is let's see what version it is just to make sure 23710. So if I go to software management, it's a system.30:52Software management, I see here the next release and I see here the applications that are available. I have installed other applications, I haven't done with I haven't done this one. I can do it. If I click download, I will then have the option to install.31:13And the process is done through catalyst center. In the new version we have something different, ok? And this is why we have this call today.31:30Why we change operating system because the one that we used in the past would do eighteen.04 is end of standard support and reaches end of pro support so we decided to move to the to a newer version and that version.31:45Is 20 two.oh four.32:05And this has this gives us a lot of flexibility in different aspects, but the fact is that this is the reason that we have the different process. We have a new operating system. On top of that it will sit the catalyst center application. We need.32:08To wipe out everything and start from scratch.32:28We have different scenarios. You see four here, but actually there are 16 or 17, if I'm not wrong in the documentation that we have published. The four that you see here, the 1st one we have.32:35A1a cluster either three node cluster or a single node device and we want to upgrade it. So this is this is what we call in place upgrade. We also have another scenario where we have two clusters.32:51An old one and a new one and we want to move from the old to the new one.33:12Oh, we can go from a medium appliance to a virtual machine or a virtual machine to a virtual machine, so there are different scenarios. We will focus on scenario number one today, so it's the in place upgrade.33:16For 315 or three.X if you like the models that are supported are all the DN two and DN three appliances, DN one is not supported. We also, support the.33:37The Versions that you see on the right hand side and this is as of today 29 April.33:55Maybe tomorrow we have another version that is supported, but as we speak, these are the supported hardware and models and software versions for the upgrade. Now.34:03What if I really, really, really want to install three.X on my DN one appliance? Well, the answer is, it is not supported, ok? You may try, I don't know what's gonna happen. We haven't tried it in the lab. You may succeed, but you may find issues with.34:20The resources.34:41So Cisco does not support the version three.X on a DN one appliance. You can use the appliance for something else for a VMware environment or something else but not for three.X.34:42Catalyst center. Now, before we see this the prerequisites and the process, it's it's good to have sorted out. So we need to have a specific version for a.35:00Actually, we need to have firmware version four.one or newer so it is.35:21Compatible with the process and you you go to, to swims interface and you go to settings system health and there you see the firmware version that is.35:30Yeah, that is installed. Now if you see a version lower than a4.one which is supported or if you want to upgrade, there is a YouTube channel and there are videos there, I will post the.35:45Links at the end and you can see the process on how to upgrade in in that video. 2nd thing is you need to verify in the settings you need to verify that is enabled. So you go to communication services and you make sure that.36:02Let this is clicked.36:22Probably it's there but you need to make sure that it is and the last thing, the 3rd thing for Simsi regarding Simsi is the naming. So although we usually don't change those names, you need to confirm that the the names for the virtual drives.36:24Are system fusion and NDP for DN two appliances or analytics for DN three appliances. If for whatever reason these do not match, you need to change and make sure that they have they they follow this naming convention.36:44Once we are good with SIMC remember we talk about the in place upgrade, so we talk about a single node or a three node cluster, a node that we have, right? So once we are ok with SIMC, we then need to configure.37:06The backup, and restore settings but we need to configure the backup basically. For 3237.37:25Seven or later we have two settings. We have to take care the remote host configuration and the NFS configuration. These are for the sorry for the automation and assurance backups. So in.37:35The older versions we had two places to store the backups.37:55In the newer version, as I mentioned earlier, we will have one place. But, for the migration process, we set up if we haven't already we set up the the two places and we also create the backup so we can perform.37:59The backup. This is the data that we will use in the new version. Again, we have a video in YouTube and I will post the link on how to backup and restore how to configure and then how to create the backup.38:19Okay, in place upgrade, these are the steps and as you see, we have the upgrade wizard that will do the job for us. So we will need to download, install and run the upgrade wizard.38:37And then we need to get some details. We need to do the conversion. The cata catalyst center will stay down while re imaging or restoring data and this is approximately three, three and a half hours, and at the end we have the post installations checks.38:57But let's see all those in in detail. Now to understand when there is up or down, we will have those two icons on the top right corner, so it will they will indicate the status of the appliance.39:17Oh, the download of the upgrade wizard. So we go to the same place as the software management in 237 but in order to upgrade to three.one, we will see the.39:37Release upgrade wizard 1.4 or whatever version is available at the time.39:56It's not clearly it's not as the the the image that we will use. It's the apply the application that we we will use for the process. We do it through catalyst center, but it's actually the application that we will use to upgrade.40:04And we download the the wizard.40:24And, it will follow the similar steps so it will install the wizard in catalyst center. And at the, at some point we will get the message your system is up to date. Usually this message indicates that the upgrade.40:29Has completed now.40:48This means that the upgrade wizard has been installed, ok? As you notice the appliance status is still green. So, how do I start the catalyst, the upgrade wizard? I either go to system catalyst center three.X upgrade and this.40:51This is something that you see in system section once you.41:11Download and install the wizard or you can log out and log back in and go to system you will see it there. You get this message, get started and you have.41:17The steps, ten steps and details for each step as you move towards the completion of the process. Now, you see, you see here cluster cluster details and other references, cluster migration precheck.41:33Cluster is either one node or three.41:53So don't get confused. It's not only about a three node configuration. A single node is also a cluster for the upgrade wizard. The 1st one is the details cluster details. You see here backup details, remote server info NFS.41:55If all if all of these are green, we can continue. If something is not, then we need to go back and make sure that we correct the the issue. Second step server authentication, it has to do with catalyst centers, so we provide the username and the passwor.42:15This username needs to be a super admin because it needs the privileges for all the process. So admin and whatever the password. The 1st step we need to provide information about SIMC.42:35And this information is the IP address of the SIMC plus username and password. Why is this needed? Because it has to do with the boot process while reimagining. So we do need to configure if we haven't done already SIMC.42:51And we need to provide the credentials and the information in step three. We click next and here we select the backup that we will use in the new version. As you see, we have selected a backup.43:08We can refresh to get more information if we don't see what we expect to see. We can use the latest backup or we can use older backups, but they have to be within the five day.43:28Period. So this is mandatory and another important thing to remember is that we can migrate only automation data. You see the checkbox here. So we leave as soon as that aside.43:44Why should we do that? Because it's a faster migration. However, regarding assurance, if we do that we start from scratch.44:04Okay, so, if, if we do it for I don't know for a lab environment or for a pilot environment, it's fair enough to go with automation only but if it's our production network, then we do need the assurance data.44:13So, we advise to go with the full backup.44:33Next step to choose the release, the catalyst center release. Here we see 313I don't know what's gonna be available when you try the upgrade, but you choose the release that you want. This is the release that it will be downloaded, but not yet.44:42Okay, so here we just choose which release to use.45:00Step six is about notifications. As I mentioned earlier, we need three, three and a half hours for the whole process to complete. So if you want, you can keep the graphical user interface and you can see the bar going right, but you can also set up notification.45:05Person you can receive emails on the progress of the migration process. Then we have the summary. This is typical for catalyst center. We have all the steps summarized in this in this page.45:25And this is where we need to check if everything is, correct. If correct, then we click next and we proceed. If some things are missing, we can refresh and we can.45:41Confirm that they come in in the picture. If they are incorrect, then we need to go back and fix them before we proceed with their imaging. We can do that in quotes many times, so it's not that we have reached the point that we cannot go back, so.45:57We can reach this point and go back in order to make sure that everything is correct and as we need it.46:17Now, step eight, we get closer to the remagic, we now have the prechecks and these are done by the upgrade wizard. All green means we go ahead. We may have some warnings and we can ignore them if.46:26We feel that we are ok with the the warnings, the comments. We may need to do something later.46:44But usually warnings are not hard stops for the process. What is hard to be is a critical error, so if you see red if you see an error, you cannot proceed, you have to go back and fix the error. And you can run the.46:55You check as many times as you need.47:14To make sure that everything is green or you have acceptable warnings. Once we are done, we click ignore and proceed or just proceed. Another confirmation you get the selected backup, you get the selected three.47:17Release.47:37If you click proceed, we then have the preparation where the backup migration is done, so we convert the backup from version two through to two.three.seven something to three.something. We download the.47:39Release that we have selected and we build the custom ISO and we are ready to reboot. If you noticed so far the appliance status is green. So far we haven't lost the appliance. The appliance is up and running. Now.47:58We pass all the texts, we get one last notification and we click ignore and proceed to go with the remats. This is the point of noticep. If I click this button, then the appliance will go down and the reimage is.48:17Do we start?48:36The appliance going down doesn't mean that we lose the network or we need we lose the operations or whatever, ok? The network will keep on working as before the devices will be ok. We just don't have management capabilities monitoring capabilities.48:38And so on. So we don't have catalyst center.48:58The processor starts you see different images here, different, different messages here, the reimagining is done, it takes three, three and a half hours to to complete. And then at some point we get the prompt.49:02To log in we see a new login screen. The appliance status is up and.49:22If everything went well then we have the new version installed. As you see here, we have the, the steps, the different steps, and they are all green. Congratulations upgrade is complete. This is the new screen, the new login.49:31Screen part of the simplified and a unified look and feel, so it looks like the Meraki dashboard login for those of you who are experienced in Meraki. We get the platform refresh completed.49:51Post checks.50:11And, once we have done everything and everything is green, we need to set up the schedules, the backup schedules for the new appliance. This doesn't have to do with the restoration.50:12Of the.50:32Data that we backed up. This has been done. So at this point, the new catalyst center, the three.X catalyst center version has automation and assurance data and is operational, but it does not have the schedules that we had for our backups. So we need to.50:33Create the schedules.50:53Again in the new version of of catalyst center. And with that we basically reached the end of the upgrade process for scenario one, the in place upgrade.50:56As I mentioned we have plenty of scenarios and you can find them in the documentation in catalyst centers site. I will again post the links in in a bit.51:15In here you can find different scenarios and you can see some of them on the left hand side. And, one last comment, actually a couple best practices are.51:34Let's say for upgrades, when you have an upgrade you are strongly advised to use.51:53The release notes of the specific version that you want to install you are strongly advised to use the compatibility matrix to see whether whether the devices are supported or they need a specific image to be supported.51:59We have the cvds and cvds Cisco validated designs and profiles.52:19That you can use and they can help you understand the design and the the different profiles based on verticals and stuff. You're strongly advised to open a proactive tag case in case something.52:27You can you can have support from from. And of course as I mentioned at the beginning if you have any questions, if you want to see something in more detail, if you have other topics, you can always contact.52:47Customer success specialists and we can go through what you need in order to make sure that everything goes well with catalyst center migration but also catalyst center itself.53:07Oh, so this is the completion of the presentation. Let me go through a couple more slides and then I'll go through the questions. So if you want to find information about.53:23The Webinars for.53:42Q3 or Q4, you can go to CS.co EMEA-EIS-Q3 how this this includes all webinars for, for all technologies as you see on the right hand side. If you're interested in.53:45A catalyst center only, then this is our page CS.CO EMEA does EIS dot That's I said at the beginning that some the the latest recordings are not yet there. We have a minor technical issue we we are trying to sort it out.54:05And, we expect to have them in a couple of weeks, including today's session. If you if it's urgent for you if you want to have the recordings before that.54:25Send us a note in the survey or an email and we will forward the direct links to you. I will paste the links inside in a bit. I just need to stop sharing so I need to finish with the slide.54:41Slides allow me please a couple of minutes. If you want to contact to contact us any@Cisco.com is the email you can send an email with your request and.55:01One of our, one of us will will contact you. Last but not at least we have the post webinar survey and once this session is finished you will get this page in.55:13Browser. Please spend a couple of minutes to share your feedback. It's important to us and it's also an opportunity for you to ask for whatever you want in the last section, the additional feedback.55:33Question number five. So, let me now stop sharing and take questions and see what we can do but 1st let me paste the links.55:50From the different places that I mentioned in chat here you go. So.56:09Okay, recording, as I mentioned, it will be in the community page, and if you want, we can send the direct link to you if you requested how many switches can be managed in one site?56:29Maximum with the new server generation. I saw the slide I can quickly go back and.56:49Say it again, so.56:59Okay, so, not sure if you are still with me yeah ok.57:15We are here. Okay, so, so.57:35Okay. And here it is the scaling for for new appliances, ok? So I guess you mentioned.57:47Devices five 5000 devices for the medium appliance 8000 for the large and 25000 for the extra large. We don't have any information for DN four for for now DN three is.58:06Alive and kicking. Okay, let's see what other questions we have. We don't have any date as I mentioned for our three.one or three.X, but hopefully we will see it in.58:27May June timeframe. Catalyst center says catalyst says catalyst center says current release 23710 is the latest one.58:45You don't see three.one because it's not GA yet. You don't see 23711. Maybe this is something that we have to look at together the fact that it's a DM two appliance doesn't matter.59:01So it's not that it's a stopper for 23711 and one supporting virtual on Nutanix, we don't have such information three.one.59:19Another hypervisors we don't have that information.59:38The recommended release dates where can we find the recommended release dates in order to estimate the end of support? The end of support is given in the end of life document and I think it's the 1st.59:44Link I posted in chat so you can find that information there. It's not their release, so it's not that 2379 will have a different release different date from 23710.01:00:03So the end of support information is actually there. Is it possible to upgrade from DN two to three.one on local virtualized platform? Probably VMware. The scenarios are in again one of the links and.01:00:19I think there is that scenario in there so you can check.01:00:39I haven't found the recording of the last session said I mentioned that we have a minor issue and it will be sorted. You will have them soon. The link will not be automatically posted.01:00:47But as I said, if you want the direct link, please send me a message, our organizational security policy does not allow NFS based backups as I understand NFS is required for version three.01:01:06And there is NO option to use SIXTYP. Are there any plans to introduce this is something that I don't know, but I haven't also heard.01:01:26Who have plans to introduce SFTP backup capability in upcoming releases. I can have a look and if I find something I can send you a message but I haven't seen something like that.01:01:36And will catalyst center in the great 3rd party stuff in sync with Meraki dashboard? So, I3 3500 switches and stuff. So what happens is the the integration between Meraki.01:01:53In Catalyst Center in Meraki dashboard is done by means of bringing catalyst center as an organization. So whatever is in Catalyst Center, you can see it as in.01:02:13Excuse me, in Meraki dashboard as an organization. If you have in industrial switches in catalyst center, you will see them there. The other way around is working the same. So if you integrate Meraki and.01:02:28Catalyst center and you see them in catalyst center. You bring Meraki organizations as a site in catalyst center and again whatever is in Meraki dashboard you see it in catalyst center. In either case, you just monitor, you cannot.01:02:47Modify something from.01:03:07The dashboard if it's managed by catalyst center and vice versa. What if I don't see an upgrade option but you have, what if I don't see an upgrade option on a DNAC appliance DN two, but now I have 23711. If you.01:03:09F23 7-eleven then it's fine, right? It's great. And actually you shouldn't see something because it's the latest to my knowledge. Is there a breakdown on new features in the I can use if I'm running my.01:03:30Controller we have a different session on that. The new features on three.1I can provide more information by email and you can see information there. What happens if we are not backing up the assurance is this still optional?01:03:48If you refer to migration, if you don't back up back up the assurance, you won't get the assurance. If you refer to that as a strategy.01:04:09Then, you lose assurance data if something happens, you lose assurance data. Good day hopefully we will cover this in the end but the version yeah ok we covered that. Why is there only one IP for SIMC one.01:04:22You have a cluster. Ok, this is because.01:04:41We saw an example where the cluster it was actually a single node. When you have a three node cluster you would have to provide information for all.01:04:47Firmware version is four, I guess about you're talking about Is there a reason why don't get an upgrade option? I.01:05:08Cannot answer that if I don't see it so maybe we have a caller you can open the case if you want to upgrade the will help you. The process for a three node cluster is the same. The upgrade was a.01:05:17That will ask details of all three notes and you can see the scenario in the documentation I've shared. The recording we sorted out.01:05:37It seems that there are bugs regarding NFSA on both version two and three. Are there any plus I'm not aware of specific bugs, if you have specific asks, please contact me.01:05:49There is a question on disaster recovery environment in a three plus three plus one disaster recovery environment are the settings restored or do we need to reconfigure disaster recovery from scratch? I'm afraid I don't have that information. I don't know whether it is in.01:06:09In the documentation but I will I will ask and I'll provide that information offline.01:06:28Can I use release 434.three for update? C 220M5 yes you can. And it is adjusted by Cisco, so what I mentioned was you need four.one or later four.three is actually recommend.01:06:42And that's all, yes, you can.01:07:02Recording, we are migrating our physically into Azure, can we use the same license or do we need to purchase a different license? If you refer to DN DNA licenses for.01:07:06Devices and stuff, then, you don't need the license. Catalyst center does not have a license so you're ok if you refer to something else that has to do with Azure of course, I don't know, but regarding device licenses or.01:07:23Access points or switches licenses. These are ok. How to check if a three node cluster setup is clusters enabled within the cluster ipsec? I can send some information on that later. How long does it take to upgrade the three nodes and also DR? How long.01:07:41How does it take to upgrade the three node cluster?01:08:01And also, they are again I don't have that information because we haven't done that in the lab, but I believe it's in the documentation and you can see the fact that you have three nodes and you do that.01:08:04Oh, in parallel I guess it's 33 and a half hours but there are other considerations especially because you have the please refer to the documentation.01:08:25The site hierarchy limits to 10000 if it's increased in three.one, again, sorry but I don't have that information. I will have to search and come back to you. Campus network automation could this be used to sync wireless.01:08:43Configuration of two Azure wireless 9800. Canvas network automation as we saw it is about device groups what you can do for the controllers and the wireless configuration. You can have a look at.01:09:02The previous sessions everything is explained there. Regarding Azure, I think we covered that as well, so I can send you the links to check that in in detail.01:09:22And we have ok we have to install DN three appliance in a new installation. What do you recommend? Use 23710 or wait for three.X so.01:09:38That is a good question, but it has to do with the urgency and it's a big discussion if if it's something that you have to do it now, then of course you go with 23710 and you upgrade.01:10:00If, you can wait for a couple of months, but again, this is not something that I could put my hands on fire, you can, you can wait. Support for hyper V I have NO information on that.01:10:22And, slides we cannot share but we can share the recording. And with that, I think I covered all questions. I'll go through the questions again afterwards if I miss something, I will.01:10:39Will contact you.01:10:59And provide the the answers offline. And with that I think we can close the session. I hope it was.01:11:01Interesting and informative.01:11:21I again ask you to please spare a minute or two to fill in the survey, next quarter we have the AI sessions next in June, the next sessions are in June and you will get invitations for those.01:11:24Sessions. Thank you for joining. Thank you for your time.01:11:43And I wish you a very nice rest of the day.01:11:48