Going virtual & beyond: virtual Nexus Dashboard (vND) deployment and Cloud Nexus Dashboard in action

Hello everyone, Welcome to 2nd webinar of this expert insight series that we are running.00:11So this is mainly ongoing virtual and beyond. What do we mean by that? We are going to talk about virtual nexus dashboard and the cloud Nexus dashboard, and we will see how you can get started with either of them. In this, as we are going virtual, there is NO requirement for a physical appliance.00:18And you can start your infrastructure what you have already. You do not need any additional hardware from Cisco to get started with your journey here. So today we have myself Ronak, and we also have Shyam, we are both customer success specialists who have joined us for this webinar.00:36Throughout the session as we already discussed, if you have any questions, please feel free to put them in the chat, you can ask them by raising your hand as well and we can bring those questions up. Now before you started this webinar, when we were in the.00:54Page where the webinar had not yet started, you would have seen a Slido page open up for you as well. In case you are not able to join it then, this is your turn to join it once again. You can scan the QR code using your phone.01:10You can enter the code 810 and the passcode in the and you will move directly into the slido. Apart from this, we will also be running it on the right side of our screen. I will open it up.01:26Right ok so you will have both options, either you can join from your devices by scanning the QR code and then putting the passcode of ND or you can go to slider.com enter 810, and use the passport of Ndy.01:42Or we will also be opening it up in the Webex chat or Webex panel itself on the right side, where we will ask you some questions to understand better about your environment and what are your priorities, what are some things that you are looking for in this session. So before.02:00Moving forward, we will have the 1st question of slido. Okay, that will come maybe after this slide. Okay, let's talk about the agenda for today's call. The 1st will be the introduction on why do you want a virtual environment or a cloud nexus dashboard and what are the two infrastructure.02:17Is what.02:37Differentiates between what are the differences between each other and when do you choose one versus another? Second section will be more on deploying virtual dashboard itself, what are the form factors that you can explore? What are the node profiles, the sizing, the network design, bootstrap process, everything will be covered in 2nd section. 3rd section.02:38Will be more on the cloud side of Nexus dashboard where we will talk about AWS hosted nexus dashboard, the hybrid connectivity, the scope and the.02:58Onboarding of fabric also. And finally, we will be closing the session where you will have an idea on which is the right form factor for you, what are the takeaways for you? And in case if you have any more questions from today's session, please feel free to bring them up in the last part as well.03:07So the 1st section will be more of the introduction side where we will talk about the two different things that we are going to discuss, the customer manage which is the virtual nexus dashboard and the AWS hosted, which is the cloud.03:25Nexus dashboard and where does each of these models fit in? Now, if we talk about the entire introduction, so in case if you do not want to start with a physical appliance where you have a server that Cisco provides for running Nexus dashboard, you can do it.03:40But without that also you do not need a hardware from Cisco to run Nexus dashboard.04:00You can use your own compute, which could either be through VMware ESXi it could be through it could also be through Nutanix, which is something that we are supporting from now on from the version four.two onwards. We are now supporting Nexus or Nutanix based deployment on.04:05So for your virtual nexus dashboard.04:25Then once you have your environment set up, you can onboard your ACI based fabrics or NXOS based fabrics for the centralized visibility and management of your fabrics from Nexus dashboard. And you do not always need to have your own compute if in case you want to do it through cloud, that also is supported.04:27It runs on the same operating model, but it just runs on AWS with a hybrid path that connects back to your on premise or on your on premises devices. Now one thing to note here is that you do not need to buy any additional licenses here.04:46The feature set that is supported will depend on the tier of license that you have. If it is, e.g., if you have essential tier license, if you have advantage license or premier tier license, the features that are supported in each of the tiers will be different. So you do not need an additional license, you just need to have data center networking license from Cisco.05:03That you already have for ACI on NXOS that will support the Nexus dashboard also, but the features will depend on the tier of license that you have. Okay, this brings us to the 1st question of our session today. Now, this is more to understand what.05:22What is going on in your environment currently? Are you running next to the dashboard in a physical appliance? Are you running in a virtual appliance?05:42Are you running in the setup where you have a physical appliance but also a virtual or you do not have a Nexus dashboard currently, which, in which case you are at the evaluation stage or you could also be running the older version of MSO NDFC separately?05:49I see a lot of people choose that they have physical Nexus dashboard here. Some of them are still are also on virtual Nexus dashboard. Few more people are still evaluating which next to dashboard to choose and few are on the older side of things on the MSO.06:07Nexus dashboard fabric controller. And there are a few people who also have both physical and virtual devices. That's good to see and good to see that so many people are voting in. We will give few more minutes of time or few more seconds of time for people to vote in. So this will help us understand what is going on in your environment and.06:25How we can cater our sessions today and also in future based on what environment you have and what are your challenges? What are your priorities based on that? This is just the 1st question. We will have few more questions coming in as we go along in the slides as well, but good to see that we are getting responses.06:44And a lot of people are already having the next dashboard, so that is good to see and few of them are already running the virtual nexus dashboard but again hopefully you will learn something new that you might not be aware in the past from today's session.07:04Thank you for all your votes. We will now move forward to the session. Okay, we will put this down. Okay, now we talk about the two info.07:18One of them is the customer managed that is something that you will be managing on yourself, the hardware side of things at least.07:39And the other will be AWS managed. So in the customer managed part, we have the virtual nexus dashboard. Now, as we were talking about, it is supported on ESXi L KVM or Nutanix. You provide your compute storage and networking here. So the infrastructure that you provide for running Nexus dashboard is.07:47It's from your side.08:07This is best fit for environments where you already have virtualization. E.g., if you're already having ESXi hosts and you want to run Nexus dashboard without any additional hardware, you can run it. If you already have Nutanix clusters, you want to run Nexus dashboard on top of it, that will make a lot of sense and it will help you a lot.08:09On not getting additional hardware just to the next dashboard and you can take advantage of your hardware that is already there in your environment.08:29There is full control of data locality and life cycle because it is completely on premises and you're running it completely in your environment, you have full control on the data and the life cycle also. But there are also cases where customers look.08:36Into the AWS site. They might not have virtualization environment currently running in that environment and they also don't want to go ahead with a physical device from Cisco. In that case, we also support AWS based deployment. In this case, you will be having three automated node deployment, which will be across three availability zones.08:51Once.09:11There is this hybrid VPC plus on prem VXLAN edge for the persistent IPs that will be required to run this Nexus dashboard. So this is one of the requirement and you will own the AWS networking and the hybrid connectivity because it will be connecting to the cloud with your on premises devices, the switches.09:12That are running on your environment, so there will be a hybrid connectivity and you will be owning the networking side that will happen between your devices and AWS. So these are the two platforms that we have in today's discussion, and we will be delving more deep into this in the future as well as we go along in today's session.09:31Okay, now we will talk about the 4th major section after today's discussion. That is how do you deploy virtual nexus dashboard? What are the options that you have? How do you ensure that the prerequisites are met? How do you ensure that what are the requirements for each of the deployment profiles?09:54To design the network and of course we will have a live demonstration.10:13Which will cover on how do you deploy the nexus dashboard as well. But before that, we have one more questions that is on Slido where we want to understand which platform are you already hosting your Nexus dashboard or you want to host your Nexus dashboard? It could be ESXi, it could be red Hat KVM.10:18Could be.10:38Nutanix HV, it could be AWS, it could also be physical appliance that you have today. Or it could also be that you are looking for this answer in today's session. You can do not decided yet for that case, where you will be able to understand what do you use and what will work the best.10:39Test for your environment.10:59Okay, Majority of the people are mentioning VMware ESXi. A few of them already have physical appliance as of today. If you have not decided hopefully after today's session, you will be at a better state to decide which one to use and you can choose that accordingly.11:01Few people are also having Nutanix and KVM that is also good to see that there is a mix of people in today's call, and we will hope to cater to all of you in today's call as well. I don't see anyone choose AWS.11:21Okay, in case you are looking forward to AWS you can choose that as well. But mostly I see either you are having physical appliance or you're looking for any or ESXi based deployment, ok?11:35So I think we are good to move forward now this is an important part where you get to choose which platform do you want to use.11:53If you use the VMware ESXi, you will need to download the Cisco OVA, which you can find on software.cisco.com, either of them, whichever you want to run, whether it is ESXi, whether you want to run it on KVM from or you want to run it on Nutanix clusters, you can download all of these from software.12:13Dot cisco.com.12:33In case you're running on ESXi, you'll need to download the OVA file. In case you're running it on the KVM, you will need to download the.Q code W two and in case you're running it on AHV from Nutanix, you need to download the AHV image. But if, if in case you want to run it on AWS, you can.12:35Find this from the marketplace provided and you can start using that for your AWS deployment. The bottom line will be that there's the same software, the same user interface is there. Only the difference will be in terms of sizing the network and the storage. So we'll come to that. What will be the sizing that you need to take care?12:55Of in each of them and what how will it differ also? Now, when we talk about this, there are two different node profiles that we see in Nexus dashboard. There is the app node and the data node.13:14Now the app node will have a little lower requirement in terms of resources when you are deploying it on your environment and the data node will have more. So we see some of the basic differences here. Now this is not the exhaustive list. The exhaustive list will be present to you in the capacity planning.13:30The Portal off nexus dashboard, we will be sharing the link for it in the chat so that you can go into it and choose which kind of deployment you are looking at and for that deployment how many notes are you looking at and you can find more details about each of them and what will be the requirements for each. But if we just compare the basics here, so in.13:50In case we are talking about vcpus, there are 16 or 32 vcpu requirements.14:10Then there is also CPU reservation where to run an app node, you need to have a minimum of 17600 mhz reservation of CPU and for data node it's 35200 mhz. This is a requirement where you need to have this much reserved so that the next dashboard can run properly. Similarly for.14:15We have 64 gigs here and 01:28 gigs there and they are both reserved as well. For the data disk, in case of an app node it will be 500 GB or the data node it will be three GB of SSD. Now this is the difference here where this could be a hard time hard disk all.14:35SSD, but in case of a data node it has to be a three TB of SSD share. For the system list it will be 50 GB for either of them. And for the typical use this is for secondary nodes or the smaller scale, and data node is usually used for.14:56Higher scale or unified deployments. Now one more thing here that is the data node SSD floor has to have 903K random reads IOPS and 301K random light IOPs for 4th.15:14Okay, so these are few requirements that are highlighted here, but always it is good to confirm with the Cisco capacity planning tool for the next dashboard, we will be putting the link in the chat so that you can go through that as well. Now.15:29That was the node profiles. Now there are different kinds of nodes also. So there are primary nodes which will actually be running the Nexus dashboard and the features that it has. So there are options of one or three.15:44Now one node is only recommended for lab environments for production environment, always go ahead with three nodes at least. So three is the production norm and it is the only resilient option in case you are running one node and something happens to that node, that could.16:01Cause issues where you will not be able to access next dashboard if in case that has a failure. Now there are secondary notes as well which adds scale if in case your fabric is big or you're maintaining multiple fabrics or you have a lot of flows that you need to monitor.16:17You can add more scale by adding up to three more secondary nodes. So there are primary nodes which does the actual processing and the actual running of dashboard and there are also secondary notes which will add scale, and that will help you in scaling the Nexus dashboard up.16:34Similarly, you have standby nodes. Now standby nodes are nothing but for faster replacement of your primary node in case a primary node fails, you do not want to wait for the node to get RMA and you then get a node separately and then it takes a few days of time and it reaches to your environment and then you.16:53To boot it up and replace the primary node that failed. You can have up to two standby nodes which will ensure that your operations go on without any issue and automatically as soon as the primary node fails, the standby can take its place and do its job.17:13There is also one thing that you need to note here that is resizing. So in case you choose to deploy a single node cluster at the start, you cannot extend it to three nodes. You will need to build a new cluster of three nodes. So in case you think that I will start with one node at start and then.17:30Extend that to a three node cluster in the future that will not be supported.17:50And that is something that you need to take care of. So anything that you are planning to do, at least plan for two years in future that what will be your scale in two years time and build your cluster accordingly, build your primary notes, at least three of them. You can add more secondary notes in case you feel that you need to have more.17:54Scale, you can also definitely have standby nodes so that in case something happens in terms of failure where you need to.18:14I Ensure that the primary notes gets replaced as fast as possible. You can have up to two standby nodes as well and resizing is something that is not possible. You cannot extend a one single node cluster into a three node cluster. Resizing will require you to back it up, rebuild the cluster and then restore the backup.18:23Okay. Now we come to the network designs and so in case of the bootstrap process, you need to decide it once and then it will be permanent. So do take care in processing the bootstrap process.18:48While you need to have, you need to ensure that the management and data networks are in separate subnets. You cannot have the same subnet for the management side of traffic and the data side of traffic. One more thing is you can either go with the IPv four setup on an IPv six setup or you can do a.19:04Will tag as well.19:24If you want to change it, then again, you will need to redeploy the clusters so do take into consideration what you want to go ahead with and do that and because if you want to change anything that will require a redeployment. The data network MTU should at least be 1500 bytes, that is something that you need to take care of.19:27And there will be a requirement of three persistent.19:46IPs for one node cluster and at least five or three or more. So this is the person IP requirement at the bootstrap stage. Apart from that, there are also some external services requirement. Of course, you need to have a DNS and MTP that should be reachable from every node on the Nexus dashboard cluster.19:49Then there is a requirement for delay as well. The NTP delay can be up to 100 milliseconds. There could be an offset of plus -25 milliseconds that is ok, but it should be under a hundred milliseconds. The node to node round trip should be under 50 milliseconds and the node to switch round trip.20:10Should be under 01:50 milliseconds.20:30Now, these are the requirements that you need to take care of. One thing to note here is in case you are going with the dual stack setup, in that case the IP will double. So if you are going with the dual stack, for one node it will be six IPs and for three or more, it will be at least five IPs.20:33Okay, now one more question on Slido, I will open it up on Webex as well.20:52So what is holding you back from deploying a virtual dashboard or cloud nexus dashboard? Now this question is mainly for people who have not deployed it yet. If in case you have already deployed, then you can skip this question. But in case there are.21:10Some concerns that you have before deploying it, do let us know so that we can try to cover that in a more detailed fashion during the demonstration and the future part of today's session. Okay, I see few people, they don't have any particular reason just have not started.21:26But we would like to know from more people what is the concern that you have, ok? Some people do have storage and this is the performance requirement. Some are not sure about the sizing and resourcing reservations, ok?21:44Some do have concerns on approvals and budget, ok? Now the sizing and the resource reservation or the storage and the SSD performance requirements, you can get information about it on the capacity planning tool. Do give a read through the tool and understand you can understand what are the requirements.22:00Now internal approval or budget because you do not need to.22:20Acquire a separate hardware to run Nexus dashboard in a virtual form factor that will definitely save you a lot of cost where you do not need to procure a new hardware and you can run it internally on your hardware that is already present. So it should be a little easier than getting approval for physical nexus dashboard, but I do understand.22:24There are cases where it could be a little challenging also.22:44But ok good to see few people already mentioning that they do not have any concern that but they have just not started yet. Hopefully after today's call, you will be a little more sure to get started with this journey and take advantage of something that is already available to you. So it does not require additional licenses. You can just get started with.22:48Using it. So just take advantage of whatever is there for you with the current licensing itself. You do not need to procure something else additionally, ok? I believe the few other people already might be having physical nexus dashboard or virtual nexus dashboard. So that's why we got a little lesser response.23:07But ok, we will now move on to the next part.23:27Now this is again very important, the pre deployment readiness checklist. You need to 1st of course size it. Please use the Cisco capacity planning tool to select the node profile and the node count. Accordingly, do ensure that you reserve that much resources before you start deploying the next dashboard.23:32Again, once you calculate what size you will be requiring, you need to physically reserve the CPU memory and also validate this is the IOPS on the data store, ok? Then address it. You need to have separate subnets for management and data and you also need to have a persistent IP pool.23:50So that it will depend on the requirement or how many notes you have, but you need to have reservation of the persistent IPs as well. Resolve it, ensure that the DNS and NTP are reachable and they are within the documented latency budgets.24:10Now all this information in detail you will also find in the deployment guide that link also we will be putting in the chat. You will have more information in a more exhaustive and detailed fashion in that guide also. Then of course, confirm that you have.24:26Reached all the requirements and then you can proceed with the deployment.24:42Okay, now we will move ahead with the.25:02Next part, which is the actual process. So this is something that we are talking about more in terms of the ESXi side of things where we will be showing you the demo also on the ESXi itself, where you will.25:08Select the profile, you will check the hypervisor version, you will ensure that the CPU and memory reservations and the storage performance is there. Then you will deploy either the OVA or QCO W two nodes and map the management and data networks. You will also go through the bootstrap process where you will.25:26You have a cluster wizard where you will configure the DNS, you will configure the NTP, the node details, the data and network and the persistent IPs. Everything that we deserved and ensure that is working fine will be used in the bootstrap process.25:46Once the bootstrap process gets going and gets done, you will ensure that the fabric health is in a healthy state and all the services are at a ready state. Once that is done, then you can proceed and start using the next dashboard, you can onboard your fabrics, you can enable capabilities that you have validated.25:59So we will be seeing more in details about it in the demo, that is the next part of today's segment where we will be seeing a live demo on how do you deploy the template? How do you do all the configuration, how do you bootstrap, and finally what it looks like once it is all done. For that I will hand over.26:20Put the stage to Sham to take the session forward.26:40Okay, thank you Ronak and let me go ahead and share my screen as well. Perfect. So I do, you know, as you all know that the deployment of any services might take some time and.26:47And it's NO difference in Nexus dashboard, which will eventually take some of our time because a lot of the storage, the CPU memory needs to get allocated the bootstrapping procedure takes a lot of time. So with that reasons, we have recorded a video, but I also would like to quickly show.27:07Do some steps as much as possible on a live demo, and then eventually we will roll the video as well where things can be speeded up for you to look at the the overall procedure in a seamless and a compact time as well.27:27With that said, you know, we are talking about Nexus dashboard in virtual and cloud form factor. Having said that, the 1st question you might have is where do I download this image, right? Now, as you all will be aware of, Cisco software download.27:42Or if you just type in in your browser software.cisco.com, you will eventually lead to this page. Now, all you need to do is, you need to type the product which is Nexus dashboard and you can click on that particular icon and you can see we have multiple versions listed.28:02And four.three is the one that is the latest and something that would be eventually be the stable release. So I'm sure most of most of you have worked with Cisco products and whenever you see this icon is what.28:22Suggests the stability of the software or the product itself. Now, four.three.one is also scheduled to get this icon, meaning it's extent extensively tested and very stable as well. So, what I would recommend all of you.28:39Irrespective of the version you are, do plan with in your environment or with your customers of how to upgrade to four.three.one. Alright, so with that said, four.three.one, when I click on this you see three options, right? So the 1st one is the ISO image mostly for the physical upload.28:56We also have the VMware or a Broadcom image which is formatted in the OVA and we also have the Linux format for deployment in the Linux environment. Now what we do for VMware is we download this image and the demo is gonna focus on on the.29:16That environment, but it's gonna be very similar to the other virtualization platforms as well. Now when you download this.29:35You know it's gonna be around twelve GB and the it's gonna be a single file as you can see here, and it'll be around twelve GB as I already mentioned. Now in this demo what we gonna do is we will try to deploy this and see the steps and eventually we will roll the video wherever we feel it's taking a.29:43A lot of time, right? Now, what I'm gonna do is I'm gonna click on deploy OVF template.30:03And I'm gonna lead or point to the file that is already downloaded from the Cisco software site. Now, once you provided the link, you would click on next and you are asked to provide the name. Now here is where you can provide a name that is.30:09It's very understandable for, for the entire VMware or the virtualization team as well as for you as well. Since this is the demo, I'm gonna name with some timestamp, I'm gonna click on next.30:29I'm gonna choose this particular host and that'll be something similar to your environment as well. You will pick a host, which can host the, the CPU memory and the storage requirement. I believe Ronak already shared that on the slides so we we need to ensure that we have.30:43For the app node and the data node whichever you're planning to deploy, that respective allocations are already provided. And do also know that the CPU memory as well as storage, there will be reservations so your host should also be able to.31:00Handle the reservations as well. So once you have, you know, in this environment it's a lab, so we do have a warning in terms of certificate, but in your environment, these should not be there must be taken care. And then eventually you're gonna click on next. So here is where.31:20The two options to deploy the virtual appliance shows up. One is the data node and then the app node. So I'm sure Ronak already talked about the differences between these. You know, where in terms of scale, in terms of feature sets, a lot of our customers have.31:38And we what we do recommend is the data node, but it does come.31:58With the higher requirements in terms of the CPU, the RAM or the memory as well as the disk size as well, right? As you can see, we are also giving you've already shared this links in the chat window, but you could also see this URL pasted right here on the in the.32:02This particular page. An app is where you would choose for a certain feature sets such as probably the orchestration piece which is helping you manage multiple ACI fabrics or multi sites of Nexus switches. So that some of the use cases, it might fit you if you have a resource.32:22Constraint, but for all the feature sets for higher scale, I highly recommend a three node data app, right? For this example, I'm gonna choose app and click on next.32:42And eventually what it's gonna do is it's gonna look at the storage and then we can eventually go ahead and choose the right disc. Now what I'm gonna do is I'm gonna click on the data store that is that has some free space. If your environment has this check mark, do I mean if it doesn't.32:54Have a checkmark do click on the check mark because we do not want a storage DRS for the virtual machine, but as you all know that we would want this virtual machines to not to move around hosts so do ensure that beat storage DRS or the the other high availability set.33:14Things are optimized for nexus dashboard and these are all captured in the, in the guide as well which we are which we have already shared.33:34What we do recommend is to do a thick provision lazy zero, as you know, this is the one that's gonna provide the highest performance in terms of the VMware storage provisioning concepts. So I'm gonna keep it to lazy zero. I'm gonna disable the storage DRS. For those of you who don't know what a storage DRS is, based on the capacity, the.33:41We as you all know, a virtual machine is a bunch of files and the files can eventually move to a different data store based on certain criteria. So we don't want that to happen. We want the host.34:01Hosting the Nexus dashboard to be static. Once I've selected these options, the next option is the networking part. Now you might have already attended most of our EIS or expert inside series sessions. Now for Nexus dashboard.34:12We have two different networks. So the one network is called a management network and the other network, which is pointed here as fabric is your data network. So management network is how you access the Nexus dashboard UI, and that is how you would eventually talk to let's say a service like inter site to get metadata update.34:28And you could also.34:48You know, the DNS and NTP, all of these sync is going to happen through management port. Now data NO data port or the fabric network is how we talk to the switches, be it out of band or in band. This is the way we talk to the switches, we collect information such as telemetry, the software.34:50Informations and all of that from the switches, be it ACI or Nexus switches or be it catalyst switches which we can manage with Nexus dashboard. All of that comes through the data fabric or the data network. So it's highly recommended and mandatory to have two different network. You do not wanna run same network because.35:10Is the utilization is gonna be very different, right? As you can understand, a management network is gonna carry way less throughput. It's mainly for management, but the data is gonna carry a lot more traffic and you don't want that to be in the same network in terms of the network design as well. In this case, I'm gonna.35:30Now quickly choose a different one just for the example, and I'm gonna click on next. And all right now what you see is we need to provide the password for the, the default.35:50User, the default user is admin, and from a CLI standpoint, it's a user called rescue user. Most of you might be already aware of it. Now, what you can do is you can provide a password and please remember this password because you're gonna use that later to bootstrap as well.36:08Now once you've done that, we, we provide the IP address for the management, right? Because we will, this is one part of the.36:27The deployment, 2nd part, the bootstrapping happens through the UI, where we configure the remaining informations. Now what we gonna do is we are going to give a different, an IP address for the management port, which should work, and eventually we will use this IP to carry forward our the next part of the.36:36Installations right of the deployment. I'm gonna give the subject mask in terms of the prefix and I'm also giving the, the gateway IP. So once I've given this, you know, as you can see, there's also a green logo indicating all of them looks good in terms of the fields and click on next.36:58Here is where we can review the information of the deployment. Once you have do not have anything to change, go ahead and click on finish.37:17So here is where it's gonna take a while, where because we are deploying a twelve GB OVA file to the VMware environment and there's a network in between this particular jump box and the vCenter and the deployment itself takes a certain time. Here is where we have a backup where we have.37:26The video recording. What we have done is we have covered all of these sections. I'm gonna click on play here. As you can see, it's gonna take a while. We have also set up the, the demo and eventually you can see that it's gonna go over a certain percentage and eventually it's gonna go to a hundred percent.37:46Right? Now once it's completed, what we do recommend is to go to the, the virtual machine that is deployed. In this case what I did deploy was yesterday with the timestamp of yesterday's date. We want to check that if the VMware sync option is according to our best practice.38:06Now this is captured in the deployment guide which we can go, but what we want to do is the sync time periodically should be unchecked.38:26Now in this case, it looks good, so we will proceed and go ahead and and then what we also gonna do is you know before the, you know, before we power on, we just look at all the settings and we ensure the the sync periodic setting is disabled and we can click on power on.38:33Now this is where once you powered on, you go to the, the VM console, you will start to see certain things run up, right? Now here is where we want some of the processor bootstrap to complete, and the, the console.38:53It's gonna very clearly show you that we, when the bootstrap is complete, you can proceed to the URL, which is the management IP we gave in the previous step, right? So I'm gonna quickly speed up a bit where we will show you what are all the information that is happening in the back end that you can see on the VM console.39:09So and you can also see that.39:29We're waiting for the system to boot and there's a percentage that is provided. Now I'm gonna speed up that, and once you see a hundred percent, it's gonna give you a dialogue saying that waiting for the UI to be online. Now, once the UI is online, we should get the IP address that we, we provided in the previous.39:32Step in the VMware section.39:52And that is what we're gonna use it to proceed with our bootstrap process. So this is the CLI part. If you would like to log in, it's gonna be a rescue user and the password that you set, but we would like to jump to the browser so that we could go ahead and finish our deployment process.39:55So let me go ahead, speed up the process a bit. You can see that I'm giving the same IP address and all it's asking is the password, right? It didn't ask you to ask you for the username. So go ahead and provide the username that we provided in the, the page when we were deploying the nexus dashboard.40:14Now this is the 1st one where we agreed and meet in terms of showing you where things are and then giving you a quick tour of the respective solution which is Nexus dashboard. And now once that is done, we will go to 2nd part. So as you can see, I'm gonna go back and pause here.40:32Let's quickly, ok. So as you can see, we have our steps, right? We have 123, and four steps. So we have done the 1st step in terms of giving a tour of the nexus dashboard. 2nd is cluster bring up, and then we will also have a system status, and then we will eventually onboard the fabrics. When we say fabric, it can be ACI.40:53It can be NXOS fabric, it could be catalyst switches that you would like to manage. All of that can be done as well.41:14I'm gonna click on play, where I'm gonna, because we already done this meet and greet I'm gonna quickly go to the step two and we will bring up the cluster. Now what we gonna do is just to talk about the process in terms of how you do it in the production. Right now we have deployed a single virtual node.41:21For a production system, you will do this two other times, meaning in total three times, you will deploy three virtual machines, be it Nutanix or Linux platform or in this case the broad Broadcom VMware platform. So you do this three times. You would give three different IPs in terms of management, and then now.41:41So what we do is we are going to the 1st node and then try to set it up so that it bootstraps. Now, with that said, we also provide the cluster name, what would this cluster be called as, where it's gonna have at least minimum of three nodes in production. And if you choose a cloud instance, which is on AWS, it's gonna be.42:01The Minimum three, there's NO option of a single node.42:21Now the any software requires a prerequisite such as DNS and NTP so that we are accurate in terms of time and we are accurate in the sense of resolving the full fully qualified domain name as well. So what I'm gonna do is I'm gonna provide the IP.42:24And eventually I'm gonna give the network, or the NTP address as well. And we also have internal subnets. As you can see there are two subnets which again is well documented in our documentations, which is app network and service network. Now app network is where we carry certain functionalities as you, as you all know.42:44So the Nexus dashboard is built on microservices and containers. There will be a Kubernetes cluster running a lot of managing the containers and all of them needs to talk to each other. A lot of the features are a container that's running.43:04And hence to facilitate the east west communication between the ports, between the containers, these networks are used and you know we can ensure it's it's gonna stay internal, but it, it could also go between the Nexus dashboard. So based on your network, you could ensure that it's not something available.43:18Or it's well isolated. Now once you do that, I'm gonna quickly go and correct my DNS in this case. Let me go.43:38Back. All right. So here's where I'm gonna click on, you know, what, what it does show is the proxy ability as well. So proxy is where we are able to reach our secure service called Cisco Intersight. For those of you managing compute systems of Cisco, you already know what inter site does. It helps you manage be day zero or day one.43:47On our day two activities all from a single pane. It could be a software as a service or it can be an appliance, but.44:07In terms of networking team, I'm not sure if all of you know, but when you integrate Nexus dashboard to intercite, we get a lot of features in terms of, the metadata update of Nexus dashboard, meaning post post meetos error, there could be a lot of vulnerabilities that can hit your systems. Now, how.44:14The next is dashboard be aware of all these events.44:34In near real time, right? Now that's where if you connect to inter site, we give you the package in terms of, hey, this piece of is affecting your five switches and also part of the features of Nexus dashboard, we have something called live protect where we could eventually help you mitigate that and harden and secure your kernel as well, right? So all of that happens.44:37Smoothly and also continuously because of inter site integration. So for that, you could also go directly management network and talk to inter site or if you need proxy, you can set up the proxy as well. In this lab environment, I'm gonna skip the proxy. I'm gonna click on next. Once that is done.44:58Now here is where we have two options of Nexus dashboard, that can be deployed. Either it can be L two adjacent or it can be L three adjacent, meaning you can have Nexus dashboard nodes in different subnets and different different L three constructs or you can have that in a single subnet in.45:16A single layer to domain. So if that is the case, then you can choose layer two.45:36Or you need to choose BGP that is going to advertise the routes between the nodes so that the communication between the app services or the app network, service network, and all the correlation between the nodes can happen. Now I'm gonna keep it simple for this demo, and we're gonna I'm gonna choose layer two. And here is where I need.45:40To provide more configurations for the, the, for the respective node that I've deployed.46:00So what will be the name for this node is what I'm giving here, and then I need the mandatory data network as well, right? Here is where i'm choosing a different subnet that is different from the management and I'm gonna choose here. Now, I, for the simplicity of this demo and also because of my lab resource.46:06I am going to deploy a single app node, but when you have three other nodes, then what you gonna do is you will go ahead and click on the add node that you see here that's gonna ask you the management IP, and it's gonna get all the data.46:26And eventually, all of the bootstrapping happens from a single place, right? You deploy the Nexus dashboard instance three times, you power on this the nodes and then eventually come to the one IP. And from there all the other nodes can be added and bootstrapped as a single process, right? So that's the idea.46:44I'm gonna click on validate and it is telling you this warning sign. Let me go back to the warning sign I'm gonna roll the video again. I want to quickly show you what is the warning sign as well.47:05So you can see that we we highly recommend installing the Nexus nodes in terms of the three nodes and are you, do you want to proceed a single node deployment? As and I already reiterated, the single node deployment is purely for testing and lab environment. We would always recommend a three node appliance.47:23For the high availability and other reasons. Once, we read this banner, I'm gonna go ahead with this demo environment for the with a signal load appliance. And 2nd part is now we need to go ahead and create something called as persistent IPs.47:43Now if you if you already work with nexus dashboard, it's the same concept in physical ND as well. Also, by the way, the the process that we're discussing here in terms of the UI based bootstrap is very similar in the physical Nexus dashboard as well, right? Because it's just the differences there are three physical nodes.48:02You give the IP and you come here and we've just done that in the virtual form factor. Now, what are persistent IPs? Some of our services within Nexus dashboard requires an IP allocated to it, meaning you can imagine in a way that you have a, a container system and there are parts, certain parts running.48:20Respective service and that needs to come out of the container network and able to reach you.48:40So that you could eventually communicate and that's gonna communicate to other services and whatnot. Example is nexus dashboard insights. Or the telemetry function is also one of the container that requires a persistent IP, right? So here is where we call out ok for which functions, how many persistent IPs are required? And these things are made.48:47In the, the guide which we can, which we have already shared it with you. So I'm gonna go ahead and add the persistent IPs, and also another question you might have is which subnet or which network.49:07Will these persistent IPs go into, right? If you look at our guide based on how you're deploying it, you could have in the management segment or you could have in the data segment. Now what I'm gonna do is I'm gonna go ahead and provide the data subnet in this case and I'm gonna give a range, right? Because the way I.49:21See of my services that I'm envisaging to bring it up, it's gonna act or it's gonna function in the data network.49:41So once I created that list, I'm gonna quickly review it and I'm gonna go ahead and click on save. Now what that's gonna do is it's going to do these seven step process and eventually it's gonna give us a way to view the entire.49:48Process and then eventually it's gonna bring up the system where the next step would be to add your.50:08Fabrics which could be ACI catalyst. It could be NXOS and eventually start managing those as well, right? So this takes it does take some time in terms of the whole bootstrapping process. So I'm gonna quickly go ahead and speed up.50:13Where as you can see the Kubernetes stack is getting deployed. We should see all success and there are certain processes that is eventually that is running. And once that is done, the next step is eventually it's activating the services as well. So the bootstrapping is complete. If it's the three node cluster, then it's gonna happen to all the nodes and.50:30It's gonna be a parallel in nature and and all three nodes eventually will come together and then through a single IP, right? Though each of the nodes can have a dedicated IP, you can always access any of the IPs and all of them, all the data are shared across.50:50So this is again gonna take a few minutes and I'm gonna speed up. You can see the activate services around 50 % now and once it is done, you will see the hundred percent activation and now we are in the login page, right? So here is where we can get started with the topics that we've covered.51:05In the previous year session of how do you create fabrics? How do you enable features? How can you integrate with Intersight so that your Nexus dashboard metadata stays updated, right? Now.51:25What you can do optionally as well is to go to the CLI and eventually do a command such as ACS health as well, right? I'm gonna quickly bring up.51:37The CLI as well because I'm sure a lot of you must have interacted with the CLI for certain troubleshooting aspects, but when you look at this, when you type ACS health, here is where you can see that all the components are healthy and we are good to go to the next step as well, right?51:54Now, this is broadly covering the, the whole process of how do we bring up the Nexus dashboard in a virtual form factor. Now, as you can imagine, the process is going to stay.52:13Very similar, the way we showed in the Broadcom environment, but how can you know, these steps and how can you be rest assured to run this more seamlessly, right? So the one stop shop is if you go to any of your search engine and type Cisco nexus dashboard deployment and upgrade.52:27Guide. You can choose the respective version that you're choosing. And I, as I already mentioned, it is highly recommended to go to four.three.one. We will have this gold star or it's gonna be a long lived release very soon. And you also know that.52:47In few a few months back, there was a AI model called Mitos that was released and those AI models is very good at exploring vulnerabilities in hardware or software, right? Anything that is that is digital, it it has ability to look at what are the vulnerabilities.53:03Now four.three.one version is.53:23Post Metas hardened version, meaning anything that we had before four.three.one is not Mitos level looked at for a vulnerability scan, but four.three.one is the version that we released after and hence whatever an LLM model like Methos can identify.53:26In a software, we have already rectified it, right? 431 is the version. So highly recommend.53:46You know, using this particular version. Now, as I was coming back to how do, how do I know the step by step process? Now what I just did is for VMware ESX. Now, if I, if I look into this particular segment.53:52When you look into the steps that is provided, you can also see there is step by step guide with the screenshot provided and also what are the best practices as well. So this will give you a framework in terms of reference to go ahead and do it in your environment. Now what we did cover in the demo.54:08Was the ESX part or the Broadcom part, but if you would like to do this on a Linux KVM, what is the step, right? We give you every step or we give you the commands and here is where you could have this as a reference, and I'm pretty sure since all of us on the forum are, have done this for many of our customers and we are tech.54:26Equal to a lot of sense, it's gonna be very easy for you to follow this guide.54:46Now I also saw in comments that some of you have Nutanix. We started supporting Nutanix platform very recently to deploy Nexus dashboard, and how do you do that on Nutanix platform is also covered in this detailed guide, right? Now those are something I wanted to cover before we jump into the next segment.54:50Of our presentation that is focused on the, the AWS part.55:10What I do also wanna emphasize is the, the Nexus dashboard pre pre pre install checklist, right? Sometimes, as a deployment or a implementation engineer, it is good to have a checklist, right? Now we give that from the website. You can just, it's the same website.55:16I went in the earlier, just that before you go to deploying in VMware ESX, you can click on pre installation checklist and this gives you all the IPs and all the different aspects that you would like to be prepared before you go on site or before you have a session to deploy the Nexus dashboard, right? So this is pretty exhaustive in terms of helping you give a template in terms of.55:36Of, the IP schema required, how many IPs do you require or what is the BGP ASN required if you are looking at an L three adjacencies? So all of that is something that is taken care of in this particular checklist. Now I would also like to go to another link, just give me a second.55:56Right. So most of you might have a lot of questions in terms of, what, you know, what do I support in a virtual Nexus dashboard and where can I deploy a three node and then what will be the scale that I support, right? Now, what I would like to show you is this particular guide, which is.56:18Updated.56:38Very frequently based on our changes and this is called as Nexus dashboard verified scalability guide. Now, if you scroll down, we will also have the information in terms of what is required to deploy the Nexus dashboard, but more importantly the scale, right? Because you need to.56:40Choose the right appliance or the right form factor for your customer or for your IT team, right? Now, you can see that of course the physical Nexus dashboard is gonna provide a lot more scale in terms of the, be it the flow telemetry, be it traffic analytics and other aspects. But if you are looking at what can virtual Nexus dashboard provide.57:00We also give you the scale as well, right? Upfront in terms of what is a single node can provide and what is a three node that can provide and also we could have a six node virtual deployment, meaning three data node would act as three primary node and three app nodes can act as worker node, meaning it is something that can offload.57:19Some of the CPU memory and storage cycles and do certain jobs so that you could get the benefit of the higher scale, right? Because as you can see, a six node cluster can handle much more switches and much more flows than what a three node or a single node can do. So.57:39You know, these are all the questions that you would answer in terms of, hey, would I invest in a physical node or would I look at, how am I gonna do this in the in the virtual standpoint, and then eventually map your environment, reverse track it to what is required, and then you go ahead and deploy it so that there is NO gap in terms of the.57:56Scale the feature set and the other aspects as well, right? Because I would highly recommend you to look into this particular guide as well because certain things that we we don't support in a a cloud form factor maybe, right? In AWS, we do not support flow telemetry, e.g., right? In a virtual ND similarly, we might not support a lot of scale.58:16So you would like, you would like to come here and then eventually there's another link that Ronak shared, which is in terms of the, the dynamic scaling guide and eventually come to a conclusion in terms of what you would like to deploy and then go forward, right? So that is the overall guidance.58:36All right, so this is the demo that we covered and I'm gonna go to the the slide part. I'm sure there are questions coming through. I can I can see there are a lot of activity happening I'm sure Ronika is addressing it, but if not, we will also take up some of the questions on the chat later on.58:55Alright, now let's look at the next segment. Personally, I know a lot of customers in the cloud wave, they did standardize on the public clouds. I used to work in a lot of organizations. This is my 16th year in the IT. I work with multiple customers and partners.59:13On multiple form factor. I've looked at open, OpenStack, I've looked at Red Hat I've looked at a lot of cloud environments as well. Now, there are some certain customers where because of enterprise agreement with a vendor like Microsoft or Amazon.59:33It it's a lot of sense for them to be in the cloud and they have direct connectivity from their, what, what people call as offshore departments to the cloud directly, right? There's a direct network that is available for them to talk to the cloud, right? There are various ways we access cloud. A lot of people when we.59:52Look at public cloud is where we go to a portal, we get some instances and we can deploy something and it's gonna eventually have an IP address that is public in nature and you can start using it. That's one way. And the other way is a lot of my customers in the past where we have helped them migrate to cloud, is where we had a dark fiber.01:00:12A lot of you will know this dark fiber or we had a IPsec connectivity to our IT department and the public cloud and the traffic flows and it feels almost internal like as if they've set up a data center, right?01:00:32So some of these customers, they were asking Nexus dashboard team in terms of if we can have at least one cloud, which is prominent cloud where a lot of our customers are standardized and if we can have, you know, some, this deployed in the cloud, whereas the switch is being in the data center, right?01:00:45That is where we announced our some time ago in terms of AWS hosted Nexus dashboard. Now, what we do provide is you cannot have a single node here. You need to have a three node, a three data node deployed in AWS, and this is an instance or you can you will already have it in the market.01:01:06So you don't have to download anything unlike what we saw in the virtual ND. As you know that in the cloud we have marketplace and Cisco has published Nexus dashboard.01:01:26Application that we will go ahead and deploy and automatically part of the deployment, it is going to get deployed in three different azs or three different availability zones. And, it's gonna have also six different subnets because as you know that it's in three different availability zones, the IP schema will be different.01:01:35And we have data network and management network and hence we have six network and you we we want that to have six different subnets and and eventually the the routable IP or the elastic IP will be three because three management IPs and three node and the these are the three elastic IPs, right? In terms of.01:01:55Do the infra requirements look like?01:02:15Now how do I connect this to my switches, right? Because the switches are in data center with the with the customers or partners and cloud AWS cloud is somewhere in the region. But how do I connect it? So there are two options provided. One is the direct connection, what all of you know as dark fiber. So we can have a physic.01:02:17Dark fiber that connects the customer's environment and the AWS cloud. Most of our customers have it, at least in the past what I've worked worked on, which is expensive, but they've already set it up because they're most of the workloads are in the cloud anyways, right? Because they need to have.01:02:38There's also hybrid connectivity where the database services resides in the private cloud, whereas the web part which has to scale more efficiently resides in the public part. So a lot of connectivity is required between the data center traffic and the hosted services that is in the cloud.01:02:54Such as Amazon Web Services. So direct connection or direct dark fiber or something is one option and also we can have routers in between that can provide the dedicated IPsec tunnel which can securely connect the data center and the cloud.01:03:14Now, very important thing is if you, if your customers do not have do not have a direct connect, then you need to have switches that can terminate and truncate vxlan as well, right? Because we need to, you need to ensure the IPsec is gonna travelse where we leave the VTAP travelse and then eventually enter a vtep. So the v vxlan.01:03:30Understanding is something required as well. And what we do recommend is catalyst 8000 or Nexus 9000 as these devices that can facilitate these things, right? And these are some of the requirements in terms of the cloud cloud deployment. Now let's look at the.01:03:50The resources in terms of what is, what will be deployed in the AWS cloud. The max configuration we can have is three primary and one standby. We only support this configuration for AWS cloud. And what we do support in terms of feature sets are definitely a controller. For those of you who are trying to understand what a controller means.01:04:07When we say controller feature.01:04:27If you already work with Nexus dashboard, it's very similar to DCNM or NDFC, meaning we give you a template to deploy NXOS fabrics or catalyst fabrics or you can also manage the ACI fabric. Now, 2nd part is the orchestration piece. Orchestration is where we are.01:04:29Orchestrate multi site. If you have multiple fabrics, site one side two, site three, but you need to ensure things are stretched and things needs to be managed more effectively in a single pane of glass Orchestration is the is the respective service that will help you manage multi domain or multi fabric.01:04:49Architectures, and we do support telemetry which is also what we call what we used to call as insights Nexus dashboard insights, which is evolved to be called as telemetry, meaning we will look at your data flow, we will look at your packets and we give you insights in terms of how you can optimize your environment, right? Now for.01:05:07Cloud environment as you can see, we can deploy only land so some of you might already know that the Nexus dashboard can also manage SAN fabrics, meaning we can manage your MDS switches. We can help you optimize zones of zone sets and help you migrate from brocade to MDS if required. We have.01:05:27Templates for that. And you also know that Nexus switches are also positioned in the media industry to convert the voice into data traffic and eventually wherever you have large conferences, wherever you look at music being produced, Nexus switches are used there as well.01:05:47It's called IPFM, IP fabric for media. So those things are not supported on cloud, instance, only land part is supported for ACI and NXOS. And in terms of traffic analytics, there are two ways to do it. One is the in band and out of band I'm sure you might have seen this in our sessions.01:06:06So in terms of cloud, we only support traffic analytics out of band, meaning we support four tuple, source IP, destination IP, source port, and the protocol, right? We don't give you the destination port. So that's the availability that you will get from all of this and the scale, what you have verified is hundred switches per cluster, right? So these are.01:06:26All the nitty gritties of your cloud instance managing your switches or in your data center.01:06:46No, there are some of the best practices are captured as well in terms of, of course, we will have an automated playbook that can help you deploy this in three different availability zones all already mentioned the subnet requirement, the VXLAN capable routers or edge devices required, so I'm gonna skip that but.01:06:53Once you have deployed the virtual appliance or the cloud appliance, the.01:07:13Process or the workflow it's gonna look very similar, right? It's gonna look at how do I add the fabric? How do I choose that respective role, and also what are the capabilities that we enable and also confirm the flow of telemetry from the switches into your AWS hosted.01:07:20You know, nexus dashboard, right? Now, I, I would also like to go to one of the guides and show you a few other informations as well, right? I'm gonna quickly bring this to presentation slide.01:07:37Now I wanna quickly focus on the two network topology that I talked about, which is well documented as well. So here is where we have the IPsec tunnel and this you could assume it to be the dark fiber part where on premises data center having your, having your.01:07:53Switches, which is eventually running some form of VXLAN, right? Because we do support the three tier architecture as well with the spanning tree and the VLANs, but we would also have the devices running VXLAN and we would have this network connectivity that is connected to.01:08:13To the public cloud where you have a transit gateway and we have a VPC within the AWS cloud that's going to be facilitating communication between the three nodes that is deployed in three different available zones as well, right? So this is the, this is the way the architecture looks like. Now I'm gonna also show you the other part.01:08:32Where you do not have a direct fiber or a dark fiber, but you have routers. That's where we were suggesting to have the 8000 or nine thousands routers that can help you forward the traffic and run the IPsec more effectively where we will eventually.01:08:53Talk to the so this sorry this is the direct connect option and the 1st one that I showed is the one without the direct connect over the IPsec VPN tunnel, right? So these are the two options and then the, the backend terminologies and the architecture is gonna look very similar, right? You have a transit gateway in the public cloud. We have the.01:09:10Three VP we have three vpcs in three different regions and all of that is communicated through the transit gateway and then your devices on the left is gonna talk to either on the IPsec tunnel or directly using the dark fiber in this case, right? Or where it's gonna be just a VXLAN extension from your.01:09:30Our network to the cloud network.01:09:50Now just like our VND process, if you go to the segment of, how do I host this on the Amazon Web Services, there, there is a detailed guide in terms of what what we support, what is the process and how can we go ahead and do it as well, right? So there's a.01:09:53Section that is talking about how do you prepare the Amazon Web Service for Nexus dashboard. Here we talk about the private IP and the public IP are also called as the eips, and eventually what are the subnets required and what is the prefix that we recommend, and eventually we go to a step by step process, right? This here is where.01:10:13From helping you click the link and which exact port or tab you need to go to is all captured here. Again, very detailed, very comprehensive, and it gives you all the information in terms of how can you set it up and go ahead and successfully deploy your cloud Nexus dashboard for your AWS.01:10:33Customers who have standardized their data center and the all the other aspects on the cloud, right?01:10:53Now with that said, so these links will be provided to you. I'm gonna come back to the presentation, and I'm gonna quickly go go over a few other slides before we conclude as well. Now what we did look at is in terms of the deployment part, in the day two part, as you all know.01:10:59Although clouds provide many lines of availability, you need to look at how do you back up the Nexus dashboard, which we provide within the appliance, and in terms of the patching aspects, how do we do that? Because it's a cloud managed one, in terms of the patch processes well defined in the guides as well. Now, how do we do that as something that.01:11:19We will, that we need to plan how do we look at the overall cluster health? Because you know cloud is multi tenant in the sense, have you reserved it?01:11:39Have you have a common platform so all of those requirements need to be looked at as well. And, and as we already as we already discussed, you know, resize is something we don't something recommend it's always we need to redeploy. So always ensure that you plan ahead, look at your fabrics, plan your networking and.01:11:53Then eventually deployed and be successful, right?01:12:12So with that said, what we are do getting into is the option we provide. If you need the highest scale, if you need a dedicated performance, then we have always our physical node. But lot of our customers have NXOS fabrics deployed, have ACA fabrics deployed, but they do not have.01:12:16Have a tool that can eventually help them.01:12:36Take them to the next level of operations, right? Now, buying a physical hardware might take time in the sense of planning a hardware cycle or what is the next procurement cycle and then bringing in that, right? Now, in the meantime, how about we take the power of cloud form factor or virtual.01:12:40Form factor, and then eventually get your customers or your your partners look into the certain feature sets that we can provide immediately, right? Why why to wait for a procurement cycle when you can do it today so that eventually you can back up and restore eventually probably to a virtual or I mean, to a private appliance too, right?01:13:00So that's the idea where you could eventually get started and eventually not wait for a longer cycle because a lot of feature sets of nexus dashboard is extremely powerful in terms of the endpoint visibility, be it how do you keep your environment compliant and how can post meters attacks don't act.01:13:20Occur to your switches more frequently, right? So Nexus dashboard gives you the ability to be updated and also enforce and protect your switches as well. And eventually you can later upgrade it or later reboot it if required, right? So there are a lot of features that you can get.01:13:40Today and hopefully after the session there is nothing stopping you to go ahead and embrace the virtual or a cloud form factor as well. Now with that said, the, you know, the question is, where will the cluster run? I think I need to open this.01:13:56Yeah is not loading for some reason. Okay, got it because I'm I've opened this on the, on the web browser. I'm gonna quickly open this on the desktop. Just give me a second. Please.01:14:15Yeah, the although the poll is live on the panel of Webex, we already have twelve responses on Webex itself, but it's always good to have it shown on the display as well. Okay, I'm gonna go to the slider slide again and this is the QR code, the code to join in as well as the.01:14:36Passcode. We already see some of the responses, so we'll give it a few more seconds and then eventually wait and see where we are all at We see positive responses, explore.01:14:56Some of us are looking at within a 30 day span. We are thinking about deploying the VND lab cluster and testing some some of the features. As I said, a lot of feature sets are within the virtual Nexus dashboard as well, except the scale part and few other caveats.01:15:15As I said, the hardware procurement takes time, but then until then, we don't have to because I see a lot of our customers who are using Nexus fabrics, right? Hundreds of switches, but they all manage it box by box. How come.01:15:34You know, in the age of AI, at least we need to get them onto a controller where they unify the configuration as well as the monitoring part and eventually get some of the features in terms of flow visibility and point visibility, how can we use natural language to query into your endpoints, so there are a lot of features with Nexus dashboard we get it. And.01:15:50I think that'll be a great way to get our customers and partners a taste the sense of how a controller or a day top machine like a Nexus dashboard can help them in their operations and be more effective, right?01:16:10Oh, so we see 24 responses and let me see, we have about 81 participants, so I'm gonna give few more seconds for all of you.01:16:25You'll go ahead and join the Slido. If you do have issues joining the slido, do paste it in the chat. We can help you with that as well. So I'm gonna say I'm gonna give it 30 more seconds so that I don't take away a lot of time from all the others as well for who who are already promptly.01:16:40Participate in the poll. I'm gonna give probably another 50 more seconds for you to provide answers. I do see 28, but how about we wait for 30 and then we go to the next slide, right? So whoever it is, if you want this slide to move, it's in your.01:17:01And go ahead and provide your votes and we can go to the next segment.01:17:20There are 29. We just need that one person for us to take the slide to next and bring it home in terms of closure. Alright, but that's 30. Thank you team for participating in the Slido. Alright, so this is our, this is what we did in terms of what we covered today and we.01:17:26I've already shared a lot of useful resources. You can see the links in terms of recordings, in terms of resource guides, in terms of the verified scale guide. Everything is being you know shared in terms of in the chat section. So we highly recommend all of you to explore the virtual.01:17:45Nexus dashboard or the cloud instance if it makes sense to your customer, so that we do not stop our customers from experiencing enhanced operations and more optimized way of handling the data center networks, right? So that is the intent of the session where if you didn't know we could do this, we are glad to let you know that that is.01:18:05Easy eventually it's gonna help your customers and your teams to manage your net Nexus or be it ACS switches more effectively. And as always, if you do have any questions, you know where to reach out, you have the email address to reach. If you need a dedicated focused way to walk.01:18:25Through how can this happen, and share probably few other best practices that can help you or your customers or your environment benefit.01:18:45I think this is closure, but I'll also let Ronak chime in and see if you have any questions that are not addressed and also bring this to a closure Ronak. Thank you. Yes, thank you very much. Yeah, all good from my side as well. Just one question that I will be replying with the recording of the previous.01:18:53Section I'll just put that link in the chat. But just one more thing to highlight is just as we end this session, you will be redirected to a survey page.01:19:13Right, you will have a few questions about today's session. How did you feel about it? Something that you will be looking forward to in future as well. You can recommend a few sessions to us through the feedback as well. So do fill in the feedback. It will take one or 2 min only to fill in.01:19:22That will definitely mean a lot to us and help us improve this in the future as well. Just that I want to highlight and I'll just put the recording link in the chat as well. But yeah, we still have few more minutes time.01:19:37If anyone has any more questions, please feel free to put them in the chat. I feel we have covered almost all the questions that were asked. If in case something is remaining, you can bring them up now as well.01:19:53But if there are NO questions, thank you all for joining. We will be looking to meet you in our next session that will happen next week. That will be more focused on a dedicated Q and A session. In case you try out any of them, you try out the cloud nexus dashboard, you try out the virtual nexus dashboard and then you face any issues.01:20:12After that you can bring up those queries, those concerns that you faced in the next week's segment. So we will highly recommend you to join that as well. Do join us, bring up your questions that will be completely dedicated to a recap of the series and also the Q and A part of the series.01:20:31We will have entire 1 h to cover that. So if you have any questions, you can put them in the chat, else do join us back for our next session on next week.01:20:50Okay, I see some good reactions. Thank you all for the reactions, definitely means a lot.01:21:09Thank you so much for joining. Thank you Selva. Thank you.01:21:20Thank you Ward, thank you so much thank you thank you thank you for joining all.01:21:42Sure John, you can check the recordings and come back next week with any questions you have, ok? I believe there are NO more questions, so we will conclude the session. But again, if you have any questions that you want to bring up before next week's session, I will also paste our.01:22:11Mailer that we have. You can put in your questions, your concerns in the mailer also, and that will help us to give you a more dedicated response.01:22:31If in case you need any particular help. Okay, thank you everyone for joining. We will see you in our next session next week.01:22:41