Introduction to Unified Nexus Dashboard

Hello everyone. Thank you for joining us today for this session on.00:11Unified our introduction to unified Nexus dashboard. So we have two presenters today. We have with us who is a customer success specialist with over five years of experience or rather ten years of experience in the industry. He is a data center networking expert from our.00:16We also have myself, I'm and I'm also customer success specialist. I focus mainly on data center compute and networking technologies with interest on automation and DevOps solutions. So we will be there throughout the session with you today to answer any.00:37You have and we will be the presenters for today's session.00:57So in this session, we will cover the big picture 1st, then we'll move on to the deployment models, the sizing, federation, onboarding, and some key features as well. This is to give you the idea.01:03Of what the architecture looks like and also some practical steps that you can incorporate in your environment and get advantage of Nexus dashboard in your environment as well. Now before we get started, we would like you to join the Slido.01:19I hope you got to see this screenshot even before joining when I mean when you joined and when we did not start the session till 10:00, that time you would have got to see the screen on your PC as well. You can go to slider.com enter the.01:35Code hashtag unified and the passcode is endy or simply you can scan the QR code using your phones and it will take you directly to the slido. So what we will do through the Slido is try to understand your environment in a better way. We will have some questions that will give us more insights about you.01:54Your environment, so that will help us to cater the session, get to this session and also the future sessions that we'll have part of the series.02:14To be more in line and give you the better value out of it. So please feel free to join this session. I will give in five more seconds for you to join if anyone is still remaining to join.02:22Please take 5 s of your time and join this. This will help us cater this session number two way. Okay, so let me load the whole slide 1st.02:38Okay, next is dashboard brings in a new unified approach to data center technologies currently. Let me pointer. So this is a new.02:54View on new options that you get to see next dashboard. What are the few things that are new? 1st, it streamlines the process of provisioning. So it allows you to quickly and easily deploy new services or application across your network across your network.03:09It is also secure, it strengthens your security posture by providing tools to monitor and detect and respond to potential threats helping to save guard your environment. You can also manage a lot of things, so you get a suite of comprehensive management features.03:26Simplifying daily operations making it easier to maintain consistency and reliability across your architecture.03:46And finally, one of the key features analyze, so it has advanced analytics. Nexus dashboard enables you to analyze network performance, uses patterns, turning data into actionable insights for better decision making.03:54This unique solution helps you operate in a more efficient way while also adapting you in the changing demands of business currently with the advent of new technologies coming all the way from all across the architectures you get.04:09To have this new unified nexus dashboard which helps you in with an all around support together. So Cisco is combining switching software, operating models into a unified data center architecture. Nexus dashboard acts as the operational layer.04:25That ties all of these things together. So you have a unified architecture, you have unified operations, you also have unified intelligence, and what are the things that are underneath them? You can see it on your screen. We will also try to cover a bit about all of these in the future slides. So if you have any questions, please feel free.04:45Ask them in the comments as well. Now it's time for the 1st slider question that we have for you. So we 1st want to understand that is nexus dashboard currently deployed in an environment? Are you using it? Are you planning to use it in the future? Are you not aware of the.05:04It is deployed or not. Accordingly, you can send your responses and we get to see around 61 % of people mentioning that they have next dashboard. It's hovering around the 55 % mark currently.05:24And around 35 % of people say that, ok, it's not currently deployed, maybe you're looking at it as a product whether you can deploy it or not, what are the advantages that you will get out of it? So hopefully through today's session and also the future sessions that we have planned in this series, you get a better picture and take that stance that, ok.05:44The next dashboard is actually needed in my, in my environment. And if you're not sure whether it is deployed or not, NO worries, you can get back.06:04Get in touch with the team that is managing the data center networking in your organization and you can have a conversation with them whether it is deployed or not. And whatever you learn through this session today or throughout this series, you can take those learnings and have a discussion. If it is not there in an environment, you can maybe suggest them that, ok, this is something.06:12That we can try out and this is something that can help us in our operations. We.06:32We see that a lot of people are voting in. That is a really nice sign to see, but as many people as you can vote, the better picture will get. Currently, it's at 50 % saying yes they have it, 37 % saying NO and 11 % saying they're not sure.06:38Okay. Now if we talk about the unified operational experience, so next is dashboard four.one brings together a lot of the things that were different or separately there as part of version three.one and three.two which are namely dot.06:58The.07:19The insights, all of those were separate apps that you could install separately on top of the Nexus dashboard. They are now unified as a single tool and you just get different options that are present within the same tool.07:22So the goal here is to give operators a more connected workflow when it comes to managing and monitoring your data center network in architecture. So this is how the picture looks like currently.07:40Okay, one more slider question. Which version of nexus dashboard is currently running in your environment? Is it version four.x? Is it version three.x? Or is it running some version but you are currently not aware?07:58Or it could be some other version, some older version as well if it is running, you can let us know accordingly. Okay, we have a lot of people not very sure of what version they're running on the next dashboard. So if you have access.08:16To your next dashboard you have the credentials to log in into the next dashboard. You can go to the top right and you can find out which version it is running. In case you don't have access again, you can talk to your data center networking team and you can.08:35Have a conversation with them and understand what is running in the environment, how it is benefiting, and you can take back and have a discussion with them as well. So a lot of people I see are running three.X So this again will be a great session and a great series for you to understand the difference between three.X and four.X and.08:49Hopefully upgrade from three.X to four.x. And if you need any support in upgrading from three.X to four.x, you can let us know. We can also have one on one engagements with you to help you better to upgrade from three.X to four.X.09:09Thank you for all the responses. So Nexus dashboard supports multiple fabrics, multiple platforms including Nexus catalyst, MDS, and even iOS XR related scenarios. So anything that is there in your environment, whether it is a land persona, whether it is a.09:29And persona within land also if you have Nexus catalyst, MDS or even ISXR, you can still manage and monitor them through your nexus dashboard, so it supports a wide range of deployment modes and you can manage and monitor regardless of which deployment mode you have.09:48Now next dashboard, the framework underneath the next dashboard is by the microservices that are running within. So next dashboard runs on top of microservices. All the services run into a single or multiple containers.10:09So if I note this, ok. Now one more very important thing here is that these services run on a single or multiple containers in order to ship.10:26We need orchestration tool which is Kubernetes and runs on top of Ubuntu. So Ubuntu is the bottom layer on top of that you have Kubernetes on top of that, you have microservices, but do you really need to care about all of this? Do you need to care about Ubuntu? No. Do you need to care about.10:41Kubernetes? No. Do you need to care about the microservices? No, you just need to care about nexus dashboard. As long as you are well versed with Nexus dashboard, you understand the functionalities and how you can manage and monitor your fabrics better. That's all that you need to know.10:59Underneath what is happening, it is just for your reference, you do not need to understand it in a detailed way. Okay, just a side note here that if required that has access under the hood, if in case some issues.11:14Happen. You can open a tag case and they can look into your nexus dashboard.11:34Under the hood what is happening on the bottom level and you just need to, but you yourself need to just care about installing and upgrading and managing the life cycle of nexus dashboard. That's all. Okay, so as a whole with Nexus dashboard four.one the experience becomes.11:40Even more unified and instead of switching between separate tools, you just get one single product and all the.12:00Things are all the tools that are there within it are in separate tabs. You can just go to each tab and go through the, all the actions that you can perform on the exit dashboard from there itself. You do not need to worry about tools separately.12:08So now that we have a clear understanding and introduction to Nexus dashboard in production, let us go on to the deployment considerations. So what are the different deployment options that you have? So 1st is a physical, so it is on top of a UCS server, it is a server provided from Cisco.12:23So it gives you the maximum performance because it is built.12:44Pod running Nexus dashboard and that's all. Nothing else. Then you also have a virtual option which gives you a lot of flexibility. If you have resources in your environment and you just want to use those resources, you can spin up Nexus dashboard as form of a VM and that will.12:48Done in your environment and give you all the options similar to what you get even on the physical appliance.13:07So you also have an option of virtual, you also have an option of cloud. We now support cloud for agility as well. If you have any public cloud where you want to run your nexus dashboard, that option is also supported. It is a little limited with some features missing.13:15Some small features that are not there, so you can still run cloud which is a new offering, so some of the features are not fully there yet, but if you go with physical or virtual, you'll get access to all the options and for best performance you can go ahead and use the physical. Just one thing to note, you cannot make sense.13:35Match between physical virtual and cloud. Whatever you choose, you have to go ahead with the single.13:55Type of deployment of that particular option. Okay, so this is the next physical node, so you have a lot of options here. I will not go through every option. You can have a look here that what are the different supported versions that there are, so there is.14:01Are these nodes that are supported, underlying hardware of the UCS is also mentioned?14:21And you can see what are the dates and supported options. So this is your physical node which requires a server from Cisco, so we provide the server as an offering and you can just deploy it in your environment.14:26Next we have, the comparison between Nexus dashboard three.two and four.one, what are the differences in terms of the physical Nexus cluster? So you have a single node option. You have three nodes option.14:42You also have up to a six node option, so you can see the comparison between three.two and four.one here. You can compare and see that how much four.one is better when compared to three.two in terms of scalability as well. Okay, now if you go for virtual node.14:59You get to see that these are the requirements that are there for the virtual node. So virtual node are there are two types, one is the app node, which is.15:19And the smaller node that is required for your environment and you also have a data node which is the bigger node which requires a lot more resources in your environment and the resources required are also mentioned here. You can.15:28See this and deploy according to your environment and these were, this will be the requirement for each of the nodes when you're talking about the virtual side of Nexus dashboard. So again, if you compare the versions three.two and four.one, you see that the.15:44There is scalability advancements when we compare three.two to four.one. There are more supported switches that you get on four.one similar to what we saw on the physical node as well.16:04Now if you talk about cloud deployment, it is available through AWS and is focused more on agility and is useful in certain scenarios through some operational limited strengths that will be applied. So.16:18There is the option of cloud deployment, which is a new option, so there are some limitations in terms of features, but apart from that you also have the option of going ahead with the cloud deployment. So it is again, it is also revamped when we talk about four.one. Okay.16:34Now, this is something that is important. So there are three kinds of nodes that are there in your Nexus dashboard cluster. So when you want to deploy a nexus dashboard, you will have to deploy it in a clustered fashion. As we saw, we can have one node, three node or six nodes. One node is only for testing purposes, we do not recommend that.16:52But for any kind of.17:11Deployment where there is production environment involved. So you have the option of three or six nodes. So in, so when we talk about primary, they run the Kubernetes control plane and the service nodes as well. The three primary are always required in a production cluster as I was talking about, and it does support a single.17:13The physical nexus dashboard node or virtual nexus dashboard node, but this is not considered for production, should not be considered. Then you also have secondary nodes. So these are worker nodes that share the load of the service parts used for increasing the supported scale. So if you want to support more number of switches.17:33More number of conversations or more number of flows, you can add secondary nodes which will share the workload from the primary nodes. You also have standby nodes, so these will be the failed safe for you. So in case something happens to your primary or secondary node, these can take their place.17:53And this is only available for physical deployment, so if you have a physical deployment, you can have physical standby nodes as well. Okay, so this talks about the new generation, the M eight appliance that we have.18:09So we have now they made version of servers in UCS, so same the same servers are also used to have as nexus dashboard appliance as well. So you can see the advancements that are there in the current.18:27Version that we have. So if you have a single node you made, you can support up to 50 switches for for three nodes, you can support up to 500 switches. So all these supports are advanced or a little more advanced when you talk about servers.18:46Now, how do you get understanding in a better way for your environment? E.g., if you are looking to deploy Nexus dashboard in your environment, how do you understand that how many switch out, how many Nexus dashboard nodes should I deploy? How many virtual nodes do I need? Each virtual node, how much requirement is there in term.19:04Terms of compute, in terms of memory, in terms of storage, how much requirements are there? For that we have the sizer or the sizing tool for next dashboard. You can go to.19:25And the link that I will paste in the chat section and you can have a look into it as well. I will paste it here.19:36Okay, so it's pasted in the chat section. This tool will help you to understand what is the requirement that is there for your environment. How many nexus dashboard nodes do you need? How much resources do you need for virtual nodes? Everything will be there on this tool.19:54Depending on what are the tools that you want to use. So this will give you an understanding of the scale that is required for your environment. Okay, one more side of questions.20:11What form factor is deployed in your environment? Is it a physical cluster? Is it a virtual cluster? Is it a cloud based deployment or maybe you're not sure you can choose accordingly as well.20:27Okay, we are seeing some votes coming in. We have around 50 % of people saying that they have physical node and some of the people are not sure, which is again fine. You can go back and have a discussion with your team and understand it in a better way. We do have some people who have a.20:45Appliance as well. Good to see that.21:05And we also have a few people who are using cloud deployment as well. You can let us know what is the experience with the cloud deployment. If you're having any challenges that you want to talk about, we will be there to help you with it as well. So we are seeing a lot of people using the physical appliance.21:07And even in the physical appliance, if you have any issues, if you want any help in upgrades or any kind of help, you can let us know in the chat section. We will be more than happy to help you. Okay, thank you for all your responses. We have a clear picture now on how many people are using different.21:27Kinds of deployments. So we'll try to cater the future sessions we have.21:47In terms of that. Okay, now we come to another interesting topic that is Ndy Federation or next to dashboard federation. When a single cluster is not enough, next to dashboard Federation becomes important. It.21:52Allows multiple clusters and fabrics to be managed together. So e.g., if you have.22:12Maybe five or six nexus dashboards managing five or different, five or six different fabrics. So how do you manage all of them together? You can take advantage of nexus dashboard Federation in that case. So we have one managed. So one manage helps you to federate large environments across.22:17Multiple clusters and fabrics. This is usually or essentially very useful when the device scale goes beyond a single cluster's limit. So as we saw in a single cluster, there were support of up to 500 switches.22:38If you have more than 500 switches, what do you do? You can have two different clusters. E.g., here we see one cluster having 400 switches, another cluster having 400 switches and you can take advantage of one managed and use next to manage both the clusters together.22:55In a single pane of glass. Now, there is also multi cluster federation which gives basic visibility across the fabrics distributed in different clusters. So that is also there.23:12So if you have a single cluster with 404 hundred switches, as in the previous example, you can do that. If you have two different clusters with 400 switches in one cluster and 400 and another, you can still get visibility across the fabrics distributed across the clusters that you have.23:28Then you also have federation for co location. Federation is also useful when different services are running in different clusters. It keeps your management and monitoring aligned when the workloads are separated.23:48So even regardless of what workload or what kind of management or monitoring you are running on different clusters, you can still use nexus dashboard Federation for this use case. E.g., if cluster one is just being managed by telemetry, cluster two is there to be managed.24:03For orchestration, you can still have a co location federation between them using Nexus dashboard. Now if you talk about node requirements here, so there are specific node requirements for nexus dashboard between the next.24:21There should be.24:42Round trip time of less than 50 milliseconds and between app and the fabric, there should be a minimum or the round trip time should not exceed 01:50 milliseconds or multi cluster, it should not exceed more than 500 milliseconds. So there are few.24:44The level layer two adjacency as well. So it should be in the same subnet. If you have different subnets, you can have layer three adjacency as well.25:03Which requires BGP support for the upstream routers and thousand 500 bytes of MTU on the ports is supported. And if you are using Nexus for trunk interfaces, you should have it at 1504.25:12So these are few requirements that are there in terms of the nodes when you are going to have federation involved in Nexus dashboard. Okay, now there are some specific failure scenarios that we would like to highlight and briefly touch upon.25:29So what happens when one of the nodes in fails? What happens in that case and how does the recovery looks like? So that is what we want to cover here. This, e.g., is a Nexus dashboard.25:47With three primary nodes, as you can see highlighted with P and one standby. So in healthy state, the cluster runs with the primary and the standby roles in place. This structure ensures that the system can tolerate failures and still continue operating.26:02So you have one standby node and three primary nodes. What happens when one of the primary node fails? When the node fails, the cluster may experience some performance and degradation while the services restart.26:19In larger environment temporary unavail unavailability can occur during recovery. So there could be a slight hiccup of performance and there could be a degradation of performance, but apart from that.26:34It will restart on the standby node and it will run from the standby node. So after this failure happens, what will happen that this failed node will become failed node and this standby node will now become a primary node.26:49Which will be, by promoting the sandby into a primary and this will again become a fully recovered cluster. Now, once the field node is repaired, it then becomes a standby node for future.27:05So when this node gets fixed, it becomes the standby for the future. Next, we'll see what happens if two of the nodes fail. If more than one primary node fails, the cluster becomes non operational. In that case redeployment and backup and restore.27:23Maybe required. So, as many standby nodes as you have that many failures is supported by the next dashboard without any disruption. So if you have one standby node, you can have up to one failure of primary nodes or the standby node, and if the cluster will still work fine if you have.27:39More than that, then it will be disruptive. Then you might have to back up and restore.27:59So how do you do the backup and restore? It's covered here. Backups should be taken daily or regularly at least if possible even more frequently in your environment. You can do it through APIs, it should.28:04Be stored separately from the cluster so that you can avoid the risk of losing it in case something happens to the cluster. So there are two options of backup, there is config only and full. So both options are there.28:21You can go ahead and go with the full backup in a regular fashion and you can just do config on a timely, more frequent basis if required. So that is how you do the backup and restore, and the general recommendation is to do it as frequently as possible.28:36Okay, next we talk about fabric connectivity. This section explains how Nexus dashboard reaches the fabric, it manages and monitors. So there are three main reachability options. One is the direct reachability.28:55Second is the in band routed and 3rd is the out of band routed. The right choice here depends on your operational and resiliency resiliency goals. So there are some port and protocol requirements that are there in here so I will paste.29:14That in the chat section, there will be a link where you can go and visit and see more details about it ok so when we talk about the reachability options in case of direct is not the preferred design, it does not recommend.29:33As you can see here because it creates a feed sharing with the fabric.29:54If the fabric goes down, then the next dashboard may lose access as well. So that's why we do not recommend a direct connection to the next dashboard. What is one of the recommended options is the out of band router reachability. It is recommended as the best practice. It keeps the next dash.29:59Network Connected even through external network domain. So even if you lose access to your fabric, you still have access to your next dashboard.30:19And you can still manage it or monitor it on the next dashboard. So that is the recommended option as one of the recommended options. You can also have a inbound routed reachability, which is also supported, but it is a little more complex to set up and manage. It uses the fabric connectivity.30:29And requires a front panel connection to the external network. So.30:49This leaf switch here, it is connected to the front panel and then it is connecting to the next dashboard here through the external fabric. So this is a little more challenging to be there, but it is again a recommended option if you want, you can still go ahead with this as well.30:54Okay, there, for remote fabrics, there is routed reachability, which is a requirement. So this allows Nexus dashboard to connect across multiple fabrics through external connectivity as well. So if you have two different fabrics on two different locations, you can have router reachability to both of them.31:15With this kind of a option that you have. Next, as we talk about more things about Nexus dashboard, we also talk about the cluster deployment. How do you deploy a nexus dashboard cluster? Whether it is a physical.31:33Node or the virtual deployment. They are very similar to each other, so we'll just cover the physical deployment in the slides now and we will also talk about the virtual deployment in the demo in future. So.31:51Before we deploy, it is important to verify the NTP and the DNS servers and we should ensure that there are NO overlapping network ranges, so the application overlay uses this IP and the service overlay uses this IP. If there is an overlap, we need to mitigate that.32:06And we also need to plan the management data and overlay network directly. So whether it is IPv four only IPv six only dual stack or whether it is using persistent IPs, so we need to manage or have a look at that in a.32:24In advance so that we ensure that the deployment happens smoothly. Now this is the step by step deployment. So, you start with installing and cabling the UCS servers. This is again for a physical nexus dashboard when you configure the management address of one node.32:40Can you continue with the installation?33:00Then you add the additional notes and IPs to the cluster and finally, you launch the cluster bootstrap. Now this is a very high level process. We will see how it actually happens in your environment through a demo that will now be demonstrated by Shivashish. So over to you for the cluster deployment of Nexus dashboard.33:01So thanks thanks for the nice insight and the overview part. And now hi everyone so myself. And so let me just quickly share my screen to show you how this onboarding process takes here.33:22In terms of the cluster deployment, so hope you can able to see my screen, right? Yes, we can. All right, so since also was saying regarding the form factor, as you know, we have a multiple different form factor for the next dashboard. So here I'm just going to onboard a virtual form factor, right? So.33:39So this is my V center where you know from the software download page, you'll be getting the image of the dashboard where you need to onboard for the virtual form factor perspective, right? So now this is the V Center now I'm just going to deploy the OVF, so just.33:59Let me explain you, you have two options, so you can either give the URL repository in this particular 1st URL option or in case you have, you know, downloaded the file locally so you can upload the file as well, right? So now on the next step, we need to provide a couple of information. So these are important.34:19Something, right? So the virtual machine name, what the Nexus dashboard name would be on the environment and what are the sites in case you have a multiple sites in your center you can actually choose that one. So on the next stage.34:39So there are some compute resources required, right? And as explained on the capacity planning tool, you can get to know the details of the compute record or the virtual form factor perspective. So in this stage here, you need to provide that particular sizing part.34:53Once I click next, so it would be asking me whether I want to select app node or the data node, but specifically if you are using the telemetry which earlier used to call as a nexus dashboard insight, so that is a requirement to have a data node.35:11All right, so it is a single node cluster, by the way. Let's click on next. And now we need to select the storage option. Here we'll be selecting the specific storage option, and this is also very important, right? So this is since you'll be running this ND cluster and the 1st time wizard would be always on.35:28The UI, so you need to provide the management information, right? So here.35:48We are selecting two interfaces, that is required for the data and the management and make sure you are selecting the correct one based on your you know the architecture. So once it is done, you'll need to provide a couple of information again. So 1st option is admin password that is required.35:53For the 1st time logging when the UI also will be logging after booting the next dashboard cluster and also the management IP address, the same IP you'll be using in your UI.36:13To open the ND for the 1st time. So we'll be giving this couple of information along with the gateway definitely that is also required. So now it is a summary let me just quickly on, so this is the summary of whatever the configuration we have selected and time to finish and we'll give some time to load.36:24It's it's a recorded video takes some time to load it. So we have 1st forwarded this. So once it would be loading, it would be creating the virtual instance, then we need to power it on from the vCenter. Okay.36:44Right, we'll touch with the name and that the VM has created four one and now we'll go ahead and it on. So once the power on like you can also validate some of the, you know, backend procedure is going to have on the virtual machine perspective before.36:59It started booting, so it will be creating and installing the instance in the backend, and once it is done, you'll be getting this message like next to dashboard switch time initialized successfully. Now it will start to boot and it will also take some time.37:19Again, it will give you the system UI is online. So once the system UI is online message you can get and also it's mentioned the specific logging information, the same IP address is used for the management, alright, so you can just go ahead and launch into into your browser.37:34So let us move to the browser, the same password and that we have given for the admin password perspective, and now as you can see, it's a welcome to next dashboard and the version we are using here with the four.one. Let's log in for the 1st time. And this is the welcome wizard and it will help you to navi.37:54Get few different option to get you familiarized of the options it is providing. And now this is the journey page, so the journey page actually will help you to understand the different options are required from very beginning when you are onboarding your cluster, so you can also get to know the different details and the steps.38:14That is required to take or we'll we'll go one by one.38:341st is the cluster, sorry. Yep. Yeah, 1st is the cluster bringing process. So we'll go to click on go. So that is a part of the initial deployment here. You'll be mentioning the cluster though we are using a single note cluster, but we need to mention the cluster name and then the personas, right? We we know.38:38We have a LAN personas we have a storage management as well, right? For the sand persona, so in case definitely we are going for the LAN, that actually manages your nxos and the AC environment.38:58Right, we'll click on next. There are a few of the information that you need to provide which are very important for the 1st time and make sure you are providing the correct information. So 1st one is the DNS that is always required and this is the NTV information, right? So one important part is that whenever you are putting.39:09Details, make sure you are validating that.39:30All right, so otherwise what happens, I'll just show you, so NTP IP address is.sixty seven and in case I'm providing.sixty nine and I'm going to validate, it won't actually validate, it will show you a failure message, right? So it's not able to reach to the NTP server. So make sure you are providing the correct information so that you.39:33You can actually reach to the NDP server and that is very much essential for the next dashboard configuration. We will change it to 67 now.39:53We'll validate it in case you're using proxy, we're providing the proxy information and make sure you're also validating the proxy information, right? Because the system is going to validate. And in case you record any authentication, you can provide that one. And on the advanced settings, I'm not going to show you in this video but again these are some of.40:01The IP addresses required in the back end and the system is going to use the default IP addresses for that. But if any of the subnet is going to, you know.40:21Overlap with your existing organization subnet, so you can feel free to change, but make sure this is the only one time you are getting that option. So once the deployment part is completed, so you you won't get to change those IP addresses, right? That is because to bringing up the cluster. So anything is overlapping with the.40:32Subnet make sure you're verifying the document and document has all details regarding the subnet information. And once the subnet is not you know overlapping, that is absolutely fine in case it is overlapping, make sure you are clicking this advanced option and go ahead and change that one. We'll click on next.40:52So this is where it will show you the node details and as you can see the cluster connectivity based on our requirement, we'll be selecting whether it is aL2 or the BGP, we'd like to bring it up Since it's a single cluster, it's providing the serial number for that. We can click on edit. So I'll just go to show you what exactly the option. So.41:10In this particular wizard.41:30Would help you to enter the details of the rest of the cluster. So what we did, for the 1st time since we deployed from the C center, we need to bring up one particular node, right? Irrespective of the number of sizing of the cluster, because you are using three node cluster, you are going to get to do before the one 1st.41:321st node and in case you are adding more notes, you can actually do it from here, right? So the same information, the name serial number automatically will be coming up the IP addresses and the gateway information, data network information is required as well.41:53And also the gateway information, right? So I'm not going to do it is video rather I'll cancel it and now on the adding add node option, you can actually add the details of the node management IP addresses and the serial number automatically will be showing up.42:09Right, so you need to click on the add node. Let's go ahead and verify. Now on this stage we need to have some persistent IP. So the persistent IP is very important thing and for one node in a cluster, we need to have a minimum set of three persistent IP. Why it is required because sometime in case the nodes are going to.42:27Failover between your cluster so that all the application and the service should contain the same, should actually retain the same IP addresses for your microservices, right? Which is very essential in case of the clustering deployment. So make sure you are providing the persistent IP and for one node we need to have a mini.42:47Three persistent IP address, right? So here in this wizard we can actually add.43:08The persistent IP addresses for the cluster node. Now, here in the stage the summary will be validating all the information has been entered correctly. We'll click on save. And here we are going to on the cluster bringing up process, so 1st it will go for the bootstrap.43:12And it will go step by step and once some point you will be kicked off from the UI because all the processes are going to install in the back end and you need to re login.43:32Right, so I'll be showing you this in a while. So once you logged out from from it automatically, you need to re login to verify whether the rest of the options are going going on and the, you know, deployment is going on. So you can click on the.43:45A few details and so it will show you what exactly the system is going to install in the backend. So here you can see on the initial mode duplicate IP checks for the notes, so all the different checks and the procedure will be happening in the backend. Okay.44:04So once this is done, this is how got logged in logged out automatically, you need to log in back, you should use your admin credential that you have configured for the 1st time. Now you see the installation activity, the step by step setting up the node for the network, deploying the Kubernetes stacks. All these things are going to happen.44:21Automatically. And once those things are going to complete, it will land you with the page of the Nexus dashboard release where you can see it is activating the all the services and once it is done it will show you the services running. So how much time it takes, it depends on the number of nodes you're able.44:41Is in a cluster for a single load? I can tell about around 40 to 45 min it can take. Alright? And it can be increased based on the number of clusters you are using.45:01With that I think it is quite fine now for you for the last onboarding part and I'd like to hand it over back to Rona. Thank you very much for such a wonderful presentation and demonstration as well.45:12I am sure that the people can have a better understanding on how to deploy their cluster as well, especially when we are looking at a virtual deployment. Again, the physical deployment is also not very different from here. You do not need to give the.45:31Compute resources that you saw in this demonstration, you just need to do the next steps that we saw as after we saw the recenter configurations after that configuration of the nodes giving them the IPs, adding the nodes to the cluster. That's the same thing that you need to do even for the physical node. So hopefully this.45:48Will be helpful for people regardless of what deployment option they choose.46:08And they will be, be able to easily deploy it in the future as well. Okay, now that we have the cluster deployed, what is our next step? That is fabric onboarding. So this is where Nexus dashboard begins interacting with live next.46:13Work fabrics. It could be some new fabric that you want to deploy in your environment. It could also be some fabrics that are already running in your environment and you just want to.46:33Migrate them or not migrate but onboard them onto the next dashboard for better management and visibility. So both the options are supported. So fabric onboarding is the easiest, the easiest method of onboarding is through the out of band management connectivity.46:43The.47:02That you have the management zero. This works both for ACI and NXOS fabrics and supports day zero and day one management regardless of what you're having. So this is how it will look like. You will have your next dashboard here and this will be your fabric.47:03It could be a CI or it could be.47:23Normal Linux OS based fabric, you can onboard it onto your next dashboard. You can also do it through an in band, so for ACI fabrics, onboarding can also be done through in band connectivity in this model. The routed communication and correct contract setup is required, so you will need to have your contract set.47:26Have done on your ACI as well so that proper configurations are there and the fabric can be onboarded properly.47:46So this is under the option that we have. Now for NXOS based fabrics, the onboarding workflow can simply, can simplify interfabric concluding. This supports automation and default VRF extension as well. So both the use cases are supported in this.47:53Kind of onboarding. So you have.48:13Your management zero based connectivity that you can use to onboard. You can also use in band for both ECI and nexus dashboard fabrics. Now, this is just the introduction of how the fabric onboarding looks like, but there are a lot of other steps that are involved. Now to understand.48:17That in a better way, we will have a demonstration now. I will stop sharing my screen and share a recording that I have for the fabric onboarding that I have done in the past.48:35So let me share the video. Now fabric onboarding sometimes takes a lot of time depending on the size of the fabric and the configurations that are there in the fabric. So, that's why we have a recorded demo today.48:54So this is what the demo will look like. So this is what next dashboard looks like. So we will walk you through the onboarding process here. So once you log into your nexus dashboard and you go to the managed tab and under many you go to fabric.49:11You get to see this kind of a screen where you get to.49:32Have visibility of all the fabrics that you have. Now, on the top right, as you saw here, there was the actions tab. Once you go to actions tab, you can go there and click on onboard a fabric or create a fabric. So you can click here to create a land fabric or onboard an existing land fabric.49:34According to your environment.49:55So we'll just create a land fabric for this demonstration. So in this demonstration, we'll actually do two fabrics. One will be an external or internal fabric connectivity, so it will just be the connectivity between the fabrics and one more we will do a VXLAN fabric that we will onboard. So 1st we will see.49:57What are the options here? So you have your classic LAN, you have your VXLAN, you also have your external, and internal fabric connectivity. You can have a routed fabric, you can have IFM, and you can also have a data broker based configuration.50:16Now even for your data center vxlan EVPN, you also have your campus vxlan EVPN. So all these kind of fabrics are supported in the environment. So in our 1st demonstration, we will see how to configure an.50:32Onboard our external internal or external interfabric connectivity. Now EI fabric is something that we have started to support recently for your AI workloads. More specifically, if you are running AI workloads in your environment, you can also have.50:49This kind of a fabric which will support for a better performance for your AI fabrics as well. Now, for this example we'll go with the external inter fabric connectivity. So this.51:06Provides the inter fabric connectivity, including isn's, iepns, and all those kind of fabrics that you are having in your environment. You also have data broker. If you are having 1st monitoring, you can go with the data broker kind of fabric as well.51:24Now we provide basic details of the fabric, the fabric name, the location, the BGP ASN is also something that we'll provide. Now the license tier of the fabric in data center we all have three kind of licenses essential advantage and premier.51:45Essential tier license is bundled with Nexus dashboard or Nexus switches. So if you just have your Nexus switches, you have access to the essential tier. But if you want more advanced features, you can go ahead with as well and if you have access to those, you can select those here as well.52:02Now what are the different features that are supported in the various advantage essential and premier tier is visible on this tab itself. You can look through them. Most of the features that are required for your basic operations are available in essential, but if you want to have advanced features.52:19For monitoring troubleshooting or even advanced analytics advantage and premier tier of licenses will have more in terms of the options that you see here. So once you get to see what are the.52:39Things that you have, you can go next. And then in the configuration mode also you can go to advanced, you can select more options here, the telemetry connection collection do you want it out of band, in band, the telemetry should stream via IPv four or IPv six. So all these configurations you get to see when you go.52:56To the advanced configuration mode.53:16Okay. Now once we are satisfied, we'll click on next. Here is where you get to do a lot more configurations in your fabrics. So you have the advanced settings, so here you can have the fabric monitor mode, you have a lot of different options that you get to see here.53:24So you can enable performance monitoring if you want. And so after you configure all of these, most of the things we have kept as default, but whatever configurations you have done, you get a summary page here where you get to see the configuration.53:46And act accordingly.54:06Okay, we had enabled telemetry, so we'll just turn that off for interconnectivity and that is not required. So once that is done, then you get to see that the fabric is now created. Now, the fabric is created, but the switches are still not onboarded onto the fabric. So the next step will be to add the switches to the fabric.54:09Now how do you do that? You provide the IP addresses of the switches. So we will provide two IP addresses here for the two switches we have. You can have it in a common separated fashion or if you have a range, you can have a-between the upper and the lower limit.54:28Of the range here as you can see or you can have a single IP as well.54:48So in our case, we'll just have two IPs, we provide the credentials as well and we define the max hop and then we start and click on discover switches. So this will start the discovery of switches and you see that.54:54Both the switches that we provided the IT for are now discovered. Now you can select both and add them to the fabric. So this will take a couple of minutes of time for adding them to the fabric. We have fast forward this part.55:09Of the demonstration here a little more yeah now the switches are added once they are added, you can go ahead and close.55:25And now the switches are added. But one thing you see here that switches are added, but they get the default role of leaf. Now any switch you add to a fabric will get a default role of a leaf. If you need to change it, you can do it by selecting the switch and going to the actions tab.55:46So we'll go to action set mode and we'll select them as edge routers. So once we do that, we then need to recalculate the configuration of the switches so that all the configurations that were.56:12In terms of leaf now get evaluated in terms of edge routers as well and then we get to get the base configuration. Now after we get the base configuration, we get to see the configuration as well. So we get a preview of the configurations.56:28Currently there are these two switches and both are in sync. So we do not currently need to do any configuration changes, but when we deploy in future now, we'll see that there are a lot of different configurations that are that need to be pushed that will also push and show you.56:45How it looks like. Okay, now we'll create another fabric. Now this time it will be a VXLAN EVPN fabric for data center, so we'll select that and click on next. We'll again, provide the name of the fabric.57:04We go to the advanced tab, give the BGP ASN. Here we'll select premier because this is a license tier that we want to select and we want to have more advanced advanced features for these switches. And one more option that we now support is the fabric designer. Now fabric designer is the.57:24The Option that provides you the option to design your fabric 1st even before the switches arrive to your environment. Maybe you have ordered the switches and they're not yet in your environment. You can take advantage of fabric designer and set the configuration well in advance and then.57:43Push that configuration onto your switches once they arrive in your fabric as well. So this will help you to save a lot of time in case you're waiting for your switches to arrive and then you can go ahead and just.58:01Track and stack them and push the configurations directly from here. Okay. Now just yeah one more thing, once you push the configuration using fabric designer you cannot go back to the fabric design.58:18What you had in the past, it is a one time thing, just one thing to note in this case. Now telemetry collection, whether you want it in band or out of band, you can select according to your environment. Okay, then the few other options.58:38Of the telemetry VRF, the telemetry source interface, all those can be configured. Now here are few of the advanced settings that we saw in the past as well. For this fabric, we will change a few more options here.58:58So we'll go to advanced, we'll go and see in the PTP. Okay, we'll also enable the layer level layer four to layer seven for PBR, policy based redirect.59:11We will add switches without reload, we can enable that. We will also enable PTP and we can configure the PTP VLAN and all those operations all those options if we are wanting to enable PTP for resources, now these are the various IP ranges that will be used in case.59:27That these IP ranges are being used for something else in your environment, you can go ahead and change it. If not, there's NO need to change it, you can keep it as default. In our case, these are already being used by some other.59:47Operations so we'll change the VLANs here. This is supported but again something that is optional. You do not need to do it. Now you can also change the VRF light deployment.01:00:00You can change the configurations for auto deploy for peer auto deploy for default VRF and auto deploy default VRF for peer as well. Now all these options will depend on your environment. Again, the VLAN range is something that we want to change because the VLAN range provided by default was.01:00:19Being used for some other use case.01:00:39Management, we can give the NDP IPs, you can give the DNS servers, then we click on next and after all the configurations and we are happy with all the configurations, we go ahead and see the summary page. We verify that everything looks fine.01:00:42And then we go again go ahead and submit it ok this will again take a couple of seconds to create the fabric. Again, we'll add the switches to the fabric, we can use the range notation or the.01:01:00Here in this case we are using five different switches that we want to add, so we will give the credentials and whether we want to conserve or preserve the configurations on the switches or not, we can select here if you don't want to preserve and you want to have a clean.01:01:21Configuration on the switches, you can uncheck it. If you want to have the configuration that are already there on the switches, you can preserve those configurations as well Both the options are supported. So again, so you can see that these are the five switches that it discovered.01:01:40So you can select all five and we'll add them. Now again this will take a couple of minutes to get done. We have again fast forwarded this section of the video ok fine with the switches.01:01:57Are added. Once they're added, we can go ahead and close this. Now again as we saw, the same thing is happening. It is defaulting to the leaf roll. So we go ahead and change the spine switches that we see here.01:02:17Into the specific role that we have, we go to border gateway spines. So these will be configured as border gateway again we recalculate and deploy so that all the configurations are refreshed according to the roles that we selected currently.01:02:34Okay, now we get to see the config preview. This we saw in the previous one as well, but here we see that there are a lot of configurations that are to be pushed. So there are, they're all out of sync and they require all of these lines of configuration that needs to be pushed.01:02:59So we can click on each of the configurations and we get to see that what are the configurations that are required to be pushed for the configuration that we selected during setting up the fabric. So all these configurations will be pushed and you get to see all these configurations.01:03:19As pending configuration on that on this tab itself. You get to see the AS number that we configured that is 65001. All the configuration that we have set can be seen here and all of this will directly be pushed onto the switches. Now, then we just push the configuration and it will.01:03:38Again take a couple of minutes to get done. This is again a little fast forwarded. Once the configurations are pushed, now you get to see that the configuration sync status is now success and all of them are in a healthy status and they are working fine according to their configurations that we have set them for.01:03:58Which ok and finally we get to see how the fabrics are looking like in the topology view as well. So this is the fabric that we just onboarded, you get to see the three.01:04:18The leafs and the spines that we have and also the external connectivity that we configured here. So both can be visible over here. You can perform your actions, you can see your monitoring options from here. You can do a lot of other options, but this sums up the entire process of onboarding fabrics. This is the.01:04:38Second fabric that we onboarded.01:04:58And finally, we also get to see the 1st fabric or the external fabric that we have. So yeah, this is the external fabric that we onboarded. You can get to see that our switches here and the vrfs and the connectivity between them. So this is how the entire process of.01:05:00Onboarding fabrics will look like in your environment as well. Hopefully this will give you a brief and good idea of how the process looks like.01:05:20Off onboarding the fabric. Now, with this, I would now like to hand over the ball back to Shivashish to take the session forward. Sure, thanks thanks for the nice insight on the onboarding part and I think it will give some insight about how we can actually onboard.01:05:30So.01:05:50You know, the fabric that you were using already or you have already onboarded. So now so there is a major innovation shift in terms of the fabric onboarding in terms of the other operational features. And as Ronak already mentioned, so it is on the four.X starting from.01:05:51Are we are showing on the four.one part so it's kind of a unified approach.01:06:11And so let's see a couple of features and a couple of, you know, the how the UI also got changed in terms of with the unified approach of the access dashboard. So I'll be talking a few and let me move forward.01:06:15Right, so the 1st shift on the innovation part, how it used to be looked like on the version three.two or below, right? We used to have a different applications, right? We used to have orchestrator, we used to have the fabric controller.01:06:33Even to toggle back to the ND platform, we also need to, you know, use the toggle button, right? But with the new four.one release, so this option is NO more there because we are calling it as a unified Nexus dashboard and all the different applications.01:06:51Then that were available earlier, kind of a Nexus dashboard orchestrator, Nexus dashboard Fabric controller. Those are all combined now.01:07:11So we don't have to toggle down between a different application. So the capabilities remain same. Even we have increased some of the features some of the capability on that. So it's all kind of a unified UI, NO more toggling, NO more navigating with the different services, right? So you can see I'll be also.01:07:21Demonstrating during my walkthrough.01:07:41But now the next option is a multi fabric visibility. So what does it mean is it can actually manage all the different fabrics under the same next dashboard cluster, we can monitor from there. So suppose you have multiple different fabrics and you would like to onboard it, right? So you can.01:07:43Actually do that and you can actually manage those things well.01:08:03And also it would be helping you for the monitoring purpose. Now we have a change in the wizard for the interconnection, how it looks like in case you have a two different ACI with the interfabric connectivity option and that will also will give you from a single pane of glass management and.01:08:07Monitoring perspective.01:08:27As I was talking about the orchestration, why the orchestration is because I can give you a basic understanding in case you are not able and the folks are already probably get an idea about it, right? So it's kind of a management of your multiple ACI sites so you are using a multi site environment where you have two or three.01:08:30Three or more than that different ACI sites and you would like to manage those things, you would like to create a single policy model, right? Creating a schema, creating a template. So all these options do actually manage your multi site multi fabric environment, not multifab actually multi site environment, right? And that we used to do for.01:08:49From the Nexus dashboard orchestrator earlier. So now since the orchestration features is already incorporated within this Nexus dashboard platform, you can actually have your tenant and the schemas, everything together, right? And you can actually do the same things from there, from the all policy point of view.01:09:09Now some major innovation and also in our integration part, but now we have added support for the open shift, right? Along with all your VMM domain integrations we we can support openshift integration. We have integrated.01:09:27For the open stack to actually natively OpenStack is also there that can be supported with the version four.one.01:09:47And this is also one of the very important feature we, you know, got a lot of feedback from our customer where they really wanted to have a custom dashboard, right? And in this area we have improved a lot and we are going to do much more kind of to give you a feel like a knock where you.01:09:55You'll have a single dashboard, you'll have a company name, company logo, everything on that. And in that dashboard you can actually add a different wizard or different options you would like to see from a single pane of glass. So suppose you have a giant screen to monitor like a knock.01:10:15But you can actually create a custom dashboard, maybe add some logos over there, and most importantly, you can, you know, add a different option. How do you like to monitor your fabric from a different UI perspective? You can put everything's together, you can change those things as well.01:10:31And that will also help you in terms of the monitoring for your maybe monitoring team L one or L two team, whoever is monitoring the complete fabric. I'll be also demoing this part. And also this is one of the important things so nobody wants to get an alerts or the anomalies in case during a change window or maybe maintenance.01:10:51This window, right? So suppose you are.01:11:11Doing some maintenance, maybe upgrading some of the portion of your fabric and you know there will be a lot of up and down of the switches where, those end of the day is going to generate a lot of alerts, a lot of anomalies, right? Within that short, maybe a 2 h or three years period of time, and that you would.01:11:14Don't want to receive those things, right? So we have introduced a suspend alert option from the fabric perspective so that during that short of time the fabric won't generate any alert or anomalies, which might be allowing force right during the maintenance window.01:11:34We don't want that, we can actually suspend those alerting and it will stop sending any anomalies related with that. Next, kind of a search right you can search and explore, right? This is also very important irrespective of suppose you have, an endpoint.01:11:50Would like to search, you can actually use that thing and you can use this particular window to get the details of the endpoint, maybe from a specific fabric perspective or even if not, you would like to see whether the endpoints belongs, selecting the all fabric options, all online fabric options, so it will help you to.01:12:10Navigate the specific endpoint out from there using the Mac or the IP addresses?01:12:30Right. Moving forward to the next slide, alright, so this is a part of the connectivity analysis, there is some enhancement has happened, so I'm going to give you a detailed high level overview because we have a session also coming up so we can deep dive on that session, but it is kind of, the connectivity is runs.01:12:34Across the multiple fabric right now where.01:12:54Suppose you have ACI and there are two ACI and you have IPN ISN managing that one, but this is not a managed things, right? It can be unmanaged by you. You can actually see the cloud is there, but if the IPNN ISN is managed, you can actually do that from your end.01:12:57Maybe you can actually manage that one, right? We can also use anogeneous configuration for the you know different fabric like ACI to NXOS or maybe nxos to NXOS communication as well with the help of connectivity analysis to trace down the complete path between two fabric, between two source and destination.01:13:17I'm not going to cover for the traffic analytics, but again, it's the very important features that also we have introduced in case anyone knows about TA the traffic analytics, it requires to you know sort of comparable version with your ACI fabric and that is six.one, but there are.01:13:38A lot of customers who are yet to upgrade, they're facing some challenge maybe due to some compliance or something or they're yet to upgrade their fabric, but still would like to use the traffic analytics which is dashboard. So we have introduced this traffic analytics compatibility mode.01:13:57Where it's kind of a biggest update right and very relevant for that where you can actually see with the health of regular netflow, but definitely with a very limited capability, limited visibility, but I would say a decent level of visibility and can be later on, you know, you can plan for the updates so suppose.01:14:16You did not plan for the AC upgrade on the six.one. You go ahead and start using it and once you'll be going to familiarize on that, so when there will be a turn for you to upgrade your family, you can use the full mode, right? So currently this traffic analytics comfortability features has been introduced with this specific.01:14:35Option.01:14:55With that let me stop sharing and re share my screen with the lab. Just allow me a moment and.01:14:57So what I'll do, I have two different labs because one of the labs having a read only access currently, and so.01:15:16I'm going to re share my screen and I hope my screen is visible, right? To start up with, so this is a overview. All right? So this overview page or you can say the landing page of the next.01:15:27Dashboard. You see there is NO toggle option that used to come on the three.two version, right? And with the when you click on home under the overview, you can actually see various different options right the complete fabrics, anomaly level, the advisories level, how many fabrics we have a list of switches, the energy energy consumption.01:15:47Option, even with the recent activities that has been there, right? And even it will show you a map about how many fabrics has been onboarded over there. Now, if I go ahead and.01:16:07Click on topology, it will also list down the complete topology of the fabric, how many fabrics we have, and you can actually double click in and every item, right? So it will navigate you a particular fabric details. Suppose we we have a NXOS fabric and under that we have two spine.01:16:20Two leave a number of other different integration and also you can actually double down.01:16:40Double click on any items so it will also go deeper to give you the complete visibility of it. Even on the endpoint level you can click and you can see your s details. And even when you single click on the mouse over on that endpoint it will show you the complete details what port, what IP addresses and what switches and what.01:16:46The interface is going to connect, right? Second thing is that if I go to manage, right? So manage is the option where a lot of different options are incorporated over here. And another option is the analyze where we used to see the analysis hub in earlier option, but this analyze.01:17:06A tab or the section is not changed from the earlier version, right? Earlier version also used to see this analytics tab and all different options like anomalies adversary. So let me go to the manage and click on the inventory and this is going to show you a complete inventory of whatever the fabric you select Suppose if I'm selecting the.01:17:24The 1st one leaf, it will go inside that particular specific leaf and it will show you your overview and the complete details of that particular switches. But most importantly when you are landing page on the inventory, it will show you a complete details on the inventory, name of the devices, the fabric name, anomaly.01:17:44How are the anomalies you are learning, IP address, model, the config thing, the role of the specific devices, even the serial number, discovery status and adversaries level, right?01:18:05So what I was discussing during my presentation, I'll go to the home, I'll click on the dashboard. So, this is the kind of a custom dashboard I was showing to you, so let it look, it might take some time. And now we have a dashboard already created, right? And we click it, I don't have a right.01:18:15Right, let me navigate the other one. I'll show you.01:18:36In case you'd like to create a dashboard, go to the dashboard from here you can actually create a new dashboard, but before that let me switch over to the other lab, show you the current dashboard that is currently available. So here, so this is how you have your, you know, categorized or customize your dashboard.01:18:39With the different options. So these options are not fixed. You can change that. You can add some other options as well. You can remove anything. You can select auto refresh or you can keep it like off with this struggle button. You can go to a certain timeline to see like what exactly happened on sort of.01:18:59Maybe five or 6 h back or some minutes back. There are a lot of details with the custom dashboard, so currently we can see there are five fabrics are showing out here. I have only two fabric that is very showing here, the details of the fabric based on the traffic score.01:19:19The devices, and the energy consumption, the interfaces of the fabric and the fabric details as well, right? So even what I was talking about creating a custom dashboard, you can go.01:19:36Under the dashboard, you can click on the action, click on new dashboard. So we have some of the most popular pre built custom dashboard already there, and you can go ahead and like we can see kindly we have five, you can go ahead and click on preview. It will show you the complete UI view of the dashboard. So if you really like.01:19:52Like that you can actually start building based on this pre built template or even you can click create a blank dashboard, right? So let's see, I'm not going to create one just to show you maybe a most popular one I'll be selecting. I'll click on next.01:20:11Now it will ask you the title of the dashboard and then you can just mention some name, the description, the visibility, you can make it for the private, make it kind of a shared dashboard, you can display with the company name with the graphics with full view.01:20:28That is also required in case you are managing knock. Now, if I paste or I'll click on next and it would be automatically selecting some of the template that I've selected showing as most popular and the details and I can click on save.01:20:46So it will be creating the dashboard for me.01:21:06So I'm not going deep on that. So this is how we have recently innovated this particular custom dashboard based on some requirement, based on the customer feedback, obviously. Then the next option I was talking about the orchestration part. So the orchestration part, alright, I got locked out probably.01:21:08Quickly log in allowing me a moment, I think there's some issue with the lab.01:21:28By the time if anyone has any questions, please feel free to put them in the chat section or you can even raise your hand and we can take questions live. Okay.01:21:48Sure sure I'm also back. So let me quickly share again got timed out but yeah anyway what I was doing I was telling about the orchestration part. So orchestration is used to manage multiple different ACI sites if you would like to manage that so how you like to do that click on.01:21:58Manage and you will see this orchestration option. So earlier you used to get a toggle option for that and here this all orchestration part incorporated within this particular manage option. So if I click on orchestration, it's going to show me, alright, so this selection actually record to enable the orchestration part, right? Since I don't have.01:22:18Any way to enable the orchestration, so this is the option it's going to show me.01:22:38But if I will go ahead and go to the manage orchestration, so this lab actually have the orchestration option enabled for some of the fabric and suppose you'd like to enable it, what exactly you need to do, you need to go to the home.01:22:43I'm sorry go go to the manage and go to the fabric and you can select any of the fabric where the orchestration has to be enabled, but in case it is a single site, so there is NO change to create an orchestration because we need to have.01:23:00From multiple side to be orchestrated for that, right? So go on action, click on the edit settings.01:23:20And here we'll be getting this orchestration part, right? But make sure the licensing pair is very much important for this because it actually helps you to unlock the features but someone has you know posted some question, do you require a license for the next dashboard? We don't need to have a specific.01:23:27A license, which is for the next dashboard because it's already end of using the data center networking license that's been the switch licenses. So based on the tier, we have essential advantage and premier, we'll be going to unlock the features, right? So Cisco is not, you know, enforcing, but again it is very important.01:23:47That you are selecting the proper licensing that you are using and based on that is going to unlock the feature. And this is where the orchestration part.01:24:07I was talking about where you need to check this option and also this is the telemetry part which earlier used to come as a you know the nexus dashboard inside, so it's kindly renamed as a telemetry, how we are going to get a telemetry and going to use the different features for that.01:24:15Now, the other option I was talking about the traffic analytics, right? So now you can see this option traffic analytics compatibility mode. It will give you a brief details on that, like it says support condition detection only. So that's been you can get the visibility with the decent.01:24:33Well, but not in the full because of for using it the full version, you actually need to use ACA version six.one, right?01:24:52Alright, another one is multi fabric things that I was talking about. So for that, what we'll do will go to the admin, click on the system settings and you see there is a multi cluster connectivity option. So what this says like in case you have a multiple nexus dashboard.01:25:01Cluster you can actually manage from the single cluster kind of a federated way, right? For that you need to click on the connect cluster and it will help you to select the type. You can select the next but even for the ACA you can select the controller as well. But once you click on the next dashboard you need to click on next.01:25:21And here you need to provide the host name or the IP addresses in case the DNS name is configured and it is reachable you can provide the host name as well, username and password for the authentication so that this cluster can connect to next cluster in that case with a specific username password, and in case it is using.01:25:39Logging domain, you can do it and if you would like to create a multi cluster logging domain, you can actually create a logging domain. So suppose suppose in fabric number two or cluster number two, suppose you don't use any logging domain, but you are creating a logging domain here, but when you.01:25:59Connect with the multi cluster maybe a fabric or the cluster two, the when you'll be using the cluster two directly using the UI, it will show you this particular domain irrespective of it's not being configured. So what does it mean? So I'm creating a multi cluster logging domain from my cluster one and it will help you to visible on the cluster level two.01:26:18As well. So once you make enter all the details, it helps you to connect to a different cluster. Let me see if I have any already unlike that. So we have some cluster already been connected for the multi cluster perspective, and that is specifically.01:26:38I think this is what I'd like to show for the very overview basic overview level and I hope it would be informative for you and also now who have not upgraded their fabric into four.one, I'll highly encourage to upgrade on the four.one perspective and there is some question.01:26:54Now about the recommend release. Yeah, we do see the recommended release is three.two still but since it is a4.eight starting with, we have combined everything with a unified approach, right? So there will be NO other application separately or service separately, so you can go ahead and upgrade with the latest version four.one even four.two in today's data.01:27:14Level with some more feature adding adding.01:27:34With that, I'll hand it over back to Ronak. So before you hand it over, maybe a quick thing, can you also show the inter site connectivity quickly in the admin tab? It's a very small thing, but does help a lot of people. Absolutely. Yeah, that is very essential because there are a lot of things kind of to.01:27:37Get update from the Cisco cloud, right? You need to connect with the inter site and that is a very good thing like.01:27:57You should, everyone should do it. So for that we'll go to the admin and we'll see there is a inter site option. So once we click over there, we'll navigate that particular page. So currently it is not being claimed. So what does it mean? This next dashboard has a device connector, software embedded in.01:28:03To it.01:28:24And it can connect to the internet and then it can connect back to the inter site.com so that our device can be claimed to the inter site. What exactly the benefits are claiming to the inter site is that so next is dashboard always gets the telemetry update, right? Even from the Cisco portal.01:28:24And it also matched those things within the Cisco best practice or suppose you have configured something and that configuration is not a part of the best practice which is already available with cisco.com. It will flag you on that, right? Not only that, some portion of the advisories, some portion of the vulnerabilities.01:28:44Information bug information. So suppose you are running some specific version on your ACI and that version is impacted by some bugs or might impact right now it's not impacted, might impact, so it will going to flag, right? So.01:29:05Otherwise in case you don't have the connection, it's not possible to get the details out from that. So this is very important, you know, to connect back with the inter site.com. So what exactly you need to do, you need to log into the inter site.com. I I'm not going in detail but again inter site.com, once you are logging with with your.01:29:20Username and password, you'll need to claim with using this device ID and claim code. Once you claim within the inter site it will show you all green, and that's when your fabric is connected all your cluster is connected to the inter site.01:29:41Yes, thank you very much. And we also conveniently get a question from I hope I'm pronouncing your name correctly that why do we need to connect to intercite? She already highlighted a lot of benefits regarding P certs, advisories, and all those kind of information that will directly come.01:29:55To your inter site portal as well regarding your Nexus dashboard also. But one more very important thing that we also support when we connect it to inter site is we get connected tag support in which whenever you have or if you open a tech case, all logs that are required in your.01:30:15Stop sharing, share so the connected tag will help you to upload your logs directly onto your inter site or through your inter site account directly to tech, so you do not need to download your log bundles or tech support bundles separately.01:30:38For your tech cases, it will automatically be uploaded to the case directly when you open that case through intercite. So a lot of these features are there when we talk about inter site and it is a simple thing. You do not need additional licenses to claim or onboard your.01:30:58Nexus dashboard onto your inter site so it's just a simple two click process and then you get all these host of benefits when you connect it to inter site. I hope you were able to answer the questions that you had and.01:31:16With that, I will now move on to the end of the presentation. So thank you everyone for being with us today. Hope you found this session useful, but this is just the start and we will have more sessions in this series every week from now on on Thursday.01:31:31Days, we will have one session after the another. So next session will be more focused on the telemetry and orchestration side of dashboard and then we'll have one more session on the lands and persona. And finally, the next session after that week will also be a Q and A session. I hope you have invites for.01:31:51All the three upcoming sessions. If you do not, we will also send some reminders so that you get reminded to register for the sessions and ensure to attend that session.01:32:11In the upcoming weeks. With that again, thank you everyone for joining. If anyone has any other questions, please, you can ask them in the Q and A panel or in the chat section. Else, thank you very much for your time and hope to see you in the next week's session.01:32:21