Transcript
Oh. Thank you everybody for joining. Now, my name is Patrick and today we will be focusing.00:00On delivering this expert inside series session with focus on next solution. All right, flow of the session. Okay, let me do yeah flow of the session. We will at the beginning actually I forgot to add one point we will discuss Cisco IQ before we jump to the, to the main.00:18Topic of today which is focusing on what is next to fabric next fabric, how does it work? Where does it help you? Right and so 1st half of the session I will be doing the slides and focusing on the presentation and then second half, we will have a demonstration.00:38Going through. But before we jump to that apologize for my voice, we want to see, if you are already onboarded on Cisco IQ because for those who, maybe most of you already know, I'm not sure, but for those who doesn't know.00:55We have this product called platform called Cisco IQ, which is basically a digital intelligence platform, which gives you the actionable and data driven insights to help you and maybe your customers depends on how are you running your infrastructure.01:15To optimize, optimize their IT infrastructure and accelerate the technology adoption. It is using the advanced analytics and telemetry data, thanks to which it identifies the the risks and some performance opportunities across your environment and use these insights, which it gains to enable the teams to show.01:33Shift from reactive troubleshooting.01:53To proactive management and basically predict what might happen to to act quickly and drive the operational efficiency. Now you might be coming from the two options or you already have the existing CX cloud account. So in that case, you'll be able to migrate your.01:55Put that data automatically to the Cisco IQ and steps are.02:15Simple you just navigate to Cisco IQ, you enter your Cisco Cisco cco ID, you name the account and select the CX cloud account from which you want to migrate the data from. Then you click the create create account migrate data.02:22And it will be automatically done, and once it's done, you log in and then you will be able to to see the Cisco IQ launchpad or the, the welcome page. Second option, if you are not the cisco CX cloud user yet, you will do the same thing. You navigate the Cisco IQ now so I.02:38You log in and you create the Cisco IQ account, you give it a name, you put the company name.03:00And use you create a primary storage region and, and just create the account, right? And after that there is this self guided account configuration in which you connect your Cisco cloud products, add services.03:06Right? So I didn't mention that if this is not your 1st time joining us, we will have some questions going through. On the right side of the presentations, you have the Slido panel, the appli in the application panel, you will see Slido. There will be some questions popping up through.03:25The through the session as we go. 1st one you should be already running is have you already tested hyper fabric solutions, right? Do you have.03:42Have you been in touch with? Have did you already tried the demo or had some, some experience with it? So we are interesting to see what is the experience of from your side, right? What are you bringing towards us, right? So there will be more questions. Also, if you have any question, Slido has a Q and A panel.03:51Upload it there so our panelists and me we can we can answer you. And with that, let's get to the topic so what is Nexus hyper fabric?04:07Nexus hyper fabric is cloud management data center switching fabric, right? The working names actually was fabric anywhere, which pretty much described the the purpose of of the hyper fabric. The whole point is to have one place.04:27Where you can as you see design order deploy validate, monitor or even upgrade your data center infrastructure from single single dashboard in a kind of automated plug and play plug and play way, right? You can simplify the IT operations.04:44And define, sorry, my thread is not best today and define, you can define define steps or the processes to ensure that that before you do deployment, your IT department, your DevOps team, your apps teams are all all being.05:02Aligned. All right. What you can also do, you cannot onboard data centers of any shape and size and accelerate the deployments thanks to cloud control services that manage them, which I'm sure really for you is good because it leads to rapid time to value.05:23In your deployments, in your projects and and the utilization of the, of the fabric. And that's the goal. So today inside we will show you how is this all done and what can you achieve and kind of gain when you're using the next to hyper fabric solution.05:41Little bit about components. So everything, as I said, everything is managed from cloud controller, which is this highly scalable multi tenant cloud service that is operated by us compared to the alternative approach to using on prem management tools. We provide all of the operations.05:58It's updates so your customers don't really need to worry about this, that aspect of operations.06:18Then we have a fabric, which is made by the cloud management managed switches. Now here the main focus was high performance performance fabrics especially which are relevant to the AI traffic, which I will talk about on the next slide.06:25You can see here the support of 800 gb internet connectivity, mesh and defense topologies and grade addition especially for for deployment and validation is this onsite web portal where you basically have your.06:42Tablet or phone, and based on design that has been prepared between before, you get the real time validation while you are actually connecting the cables in a data center, but about that, we will also talk a little bit later.06:58So where can you benefit what are the use cases, right? From using the nexus hyper fabric, that's what you see here. You have one point of control and point of policy as well and with zero touch touch provisioning, you can deploy the the edge data centers. You can scale up your existing data set.07:15Center and manage large data center with multiple sites.07:35And I said already exactly hyper fabric is being positioned as a premium holistic AI cluster solution. So it's specifically engineered for the AI workloads. You can manage as you see full stack AI infrastructure with a turnkey full stack air infrastructure.07:38Which is fully compliant with NVDR enterprise reference architecture or you can also scale to to cloud reference architecture there as well. Our second option is to bring your own AI where you.07:56You can onboard your, your preferred compute the GPUs, your ASI software and and your storage to the cloud managed network of the hyper fabric solution. And that brings us, yeah I told you there are more questions to the question number two.08:11On the slido. In what scenario do you plan to use your fabric solution, right? Is it a traditional or a workload or you actually have the fabric which already using AI workload and and you want to, you might be interesting to use the hyper fabric for that solution.08:28Okay, just quickly to to tell you about the supported hardware that you can use as of now, we have three Nexus hyper fabric 6006 K switches based on silicon.08:45One architecture.09:05Which are supported with this 64 AD at the bottom you see the spine air leave for high bandwidth and low latency for AI traffic. And lately we also added the Nexus nine K So few of the Nexus nine K switches are now supported with more and more switches coming up, right?09:06So as we go.09:26And, I mean probably you already know that Nexus nine K can be used for ACI or fabric for private cloud management or you can use it with hyper fabric license to be managed by the cloud controller or there is also automation option for infrastructure with open open APIs, right? So.09:28Next to 93 case especially these types are are pretty.09:48Pretty flexible devices. And now how do you use Nexus I gave you some hints already, but if we go a little bit into it, so we divided the workflow to three kind of steps for installation on, on differentiation differentiation of.09:52For how is the hyper fabric going to help you right in your in your operation? So starting with the day zero.10:12Where you can provision the design or the blueprint, which you then use the insta inside of organization for collaboration. You know, you can specify the capacity, the the cabling, the power supplies etc. And you can even show it and discuss with your customers for modifications and once you have the alliance design, you can.10:18Create the bill of materials and that's your day zero preparation, right? It's the design phase. Now day one is when you focus on deployment, you actually have configuration ready in hand for your all the hardware infrastructure and installations and thanks to that.10:38You can use the auto provisioning of the fabric, so it gets super efficient on deployments, right? You have also immediate verification to see if the things are exactly working based on the design that that you prepared. And in design, so the after deployment.10:57You're gonna gain a fabric which operates anonymously with the real time telemetry and automation and you have the cloud controller which takes care of the complex tasks, so you can actually focus on on innovating your fabric, you know, managing your customers.11:12Etc. So to go a little bit deeper on day zero, that's where you, as I say, create the blueprint and you you you define how you want your fabric to looks like, right? We have kind of optimized it for little spine topology, but you can go with the two.11:3046 which is in the mess topology so you are not limited. You don't need to stick to any, any design. You can scale up or scale down based on based on your based on your needs, right? And based on that design that you choose, you get a full list of the cable plant with all the redundancy.11:50With the railed optimal design and you can pre provision the the logical overlay network even without having the the hardware yet. And a few months ago, this is a good part, we added the ability to right away get your bill of material and put it straight away to CCW so to see the pricing and.12:09You know, to see if they if you want to continue with order to get the business done. And now, so you send it, you order it and you are in the deployment phase, like you have your blue blueprint that I talked about. So then now thanks to onsite web application.12:29You have a quick guidance or where to connect the cabling, right? And you have this real time validation. So you are on site, you are connecting and you see if the SFP that you connected is working well or if it's faulty, if it had some issues et cetera, because you already have the design. So this is very good feature. You just go and you know it's much easier.12:48Of controlling everything through the, through the, through the old way, through the CLI maybe. Now you can see everything right away, so it, it, makes the deployment much easier.13:08And afterwards, once you deploy everything, you get the monitoring and troubleshooting because we actually know how these connections are supposed to work from the design blueprint, right? So, what we do is we use assertions, so if something is configured as a fabric connection, we know how that should operate.13:19Right, and if it deviates from what is expected, well, we will tell you we will get a notification, right?13:39We try to gather as much as much intelligence when something's appear not to be in the normal behavi behavior. E.g., if there is there is a host which connects and disconnect, right? That's when you generate an assertion because it's something you might want to know about. So you get the alert.13:45You get the in the alerting the dashboard you in your email S3 buckets so you can also use it with your apps and we are also working on using the web hooks based on the, some particular events, but this is coming soon, this is not yet being deployed.14:05Right, and yeah, so that was enough talking. Let's share the floor with with so you can go through the demo and so how does it look like? Thank you so much Patrick, for the great presentation.14:22Let me start by sharing my screen. I hope everyone can see it. Okay, so this is the welcoming page whenever you start or or you get started to the.14:38To the hyper fabric. You will need to log in using your cisco ID. If you don't have one, you will need to create your Cisco ID through the different prompts that you will get inside the hyper fabric, and then you will be able to access it. One of the main important things is that.14:55That you can create different organizations within your hyper fabric. With those organizations, you can split out the different fabrics, split out the accessibility for specific users.15:15So that you can get accessibility to the different fabrics, ok? Now before we start, we will start by speaking about having the switch itself, even though that switch is not still yet claimed.15:30We I want to show you how or what will be the procedure for us to claim that device towards our hyper fabric. So if you are able to see my screen and it's clear, I will start. So the 1st thing is that we console.15:49To our switch. The login will be TTG admin, ok? And the password will be H fabric 2025. These are the default username and password for the console accessibility for the 1st time that you will get access to it in order to claim it through hyper fabric.16:05Okay. So as you can see, we provide the username and then the password, and then we will pop up with the 1st part of the configuration that will be required. So here you will see the different options. We have the change of the configuration and then the list of the configuration on the right side. If there's any issue you.16:25You can check number two option which is diagnostics. You can reboot the switch, power off the switch or factory reset it, and lastly you can log out.16:45So let's go ahead with change the configuration and here you will see of course the serial number and the switch name. Now, once you get to the switch configuration, you will see that by default it enables DSCP. So if you have this connection established and you have already DSCP enabled.16:55It and the management will get the IP address through the DSCP Dora steps. Now in our scenario, we don't have DHCP, so we need to disable the DSCP and provide the IP addresses statically as well as the gateway.17:15Now let's go ahead with applying this and then provide the gateway and then the next will be if required to have IP versus six as well. Then you need to change this to yes. If not, then you can keep it up as NO and you you wouldn't.17:34Need to to provide any configuration. Then we provide the DNS server and the proxy service or server so that we can reach out the cloud and the internet to towards the hyper fabric cloud.17:55Then now we provide our proxy server. Let me just speed it up a little. Yeah, and then we can apply and start our discovery process.18:17These are the initial discovery process just we are confirming our connection between our hyper fabric switch towards a hyper fabric cloud. As you can see, now the current status is that, the connection is disconnected from the hyper fabric cloud. We are still also not able to reach our proxy as you can.18:32See, so let's give it some time until it fixes this reachability issue. It will take few minutes to to retry and then ultimately getting the access to what the hyper fabric cloud.18:52Oh, and now you can see now we our connection status has changed. Now we are connected to the hyper fabric cloud and then the switch will provide us with the claim code.19:06Because it's not claimed, we will use this code in order to establish the connection between our hyper cloud hyper fabric, sorry, account towards our switch.19:26This is under the inventory, if you go to claim, the new pop up claim device, you will be able to provide the code and the device will be claimed. There are a couple of things that I would like to show before we, we jump in.19:40So let's go to the inventory. As you can see, here I have my two switches already claimed. If I'm claiming a new device, I can claim it using the claim code or claim discovered already discovered devices, ok?19:54Now you wouldn't need to have the hyper fabric connectivity established with all of the switch nodes that you have. You can actually establish the connection with one of the nodes, and then the rest of the nodes within the fabric will use this as the exit node. So you can.20:10Utilize only a single node to, to establish that cloud connectivity.20:30Okay, so we have our two devices already claimed. They are added to our account. The next step for us is to start creating the fabric. So we go to fabrics, a new fabric, and here we will have three main options.20:35The 1st one is to import fabrics so in case if you have a fabric that's exported from another hyper fabric account, and you would like to import it directly here, you can do it using this method or you can do it which is the new fabric in designer, meaning that you can.20:51Manually assign the, switch groups, the number of switches in each switch group. So in this scenario, we have one switch tier inside that one switch group. We can add another group. E.g., I can say this is spine.21:09Group, and this is leaf group, and then I can provide the e.g. spine, I will need two spines and leaf and I will need.21:26Two leaves, ok? Yes. Okay, and then you can provide these details and here you will see the switch groups connectivity itself. So this is the designer method, so you manually enter all of these set of details.21:41The different tiers, different groups, all of that will be done manually.22:02The, this, the 3rd option that we have is that we can create the fabric directly directly from templates. Now in that scenario, we have two main templates that we you can use either switch fabrics or through the AI cluster.22:08Now let's go with the switch fabrics. Here you can create it either using the spine leaf topology, and if you choose the spine leaf topology, you will see all the results that you have. So you will have five templates that you can use. If you have a specific.22:23Model that you want to use, you can filter out and you will see that now we have four results instead of five. And if you choose another model, it will have two. So if you have a specific hardware in mind, you can choose the hardware or put the hardware at the switch model and it will give you the option to.22:41To which topologies are supported to be used.23:01Now the other option is mesh, and this one has only a single template, which has two leaves in it and it uses the, 6160 L4D switch model. Just sorry give me a second.23:06Let me try yeah so I think it might be better this way with the light in the room so ok.23:25Okay, now 2nd template mode that you can use is the AI cluster one and this you can filter it out on the number of GPUs as well as the GPU model that you want to use. So if you select.23:43E.g., the 1st GPU, we want 96, then it will give you which, AI cluster template you can use in order to, to build or achieve this or have this number of GPUs available for you. Okay, so let's go ahead.24:00With the mesh and select this template for our usage, ok? So now we can see we have our leaf mesh network. The group is, it, it has leaves and they are naming it as 60 l-one and we will have two.24:17Switches. Now inside this, you can see the switch interconnectivity. You can directly establish this interconnectivity from this template creation or you can leave it for later on after the fabric is created. So let's save the fabric.24:36And continue to topology, ok? Now by creating the fabric, it doesn't mean that now you cannot do any changes on it. If needed to increase the amount of switches, you can always go back and edit the fabric, and this time you can change the quantity to four six the number that you would like.24:57Now let's start by doing a couple of things that are really important as the name of the fabric will be created automatically. So let's create this and name it up as fabric one. Then if we go to the, our device inventory, this is our two switches.25:18Now all of that is within the template. We haven't still mapped our two switches to the fabric itself, ok?25:38So let's go to each of those switches and rename them. So we will name this as leaf one and under inventory, let's name the other as leaf two.25:46Okay. Now, also on the right side, you can provide description, so this is, e.g., development fabric, the address is.26:08Lisbon, e.g., I'm just putting any details here and then you can provide the location if you want to speak specifically about the, in which rack this, in which DC and which rack this specific switches are, are being associated, ok?26:24Okay, now since we have changed the fabric name and the host name, let's review our configuration and push the 1st set of configuration. So you will see here, this is exactly what we have did. We created the fabric.26:43Then updated the fabric name to fabric one, then changed the name of the leaves and they played around a little bit with fabric one, ok? Which is the description and the address name. Now, if you want to see this from a JSON perspective, you will see, you can see these details.27:01All the differences between the names and everything from adjacent point of view on how it will be actually committed. Now let's comment and push though changing fabric name and post names.27:20Let's push the configuration. Now we have pushed our configuration. Let's go ahead to the insights to see that now every push or change of configuration that we will do can be seen now.27:37So under our event viewer. This can be checked through like only the last hour or you can customize it to a specific period or within last month or last week.27:56Now you will see here the 1st one was for us to initially create the fabric, the fabric creation, and 2nd one was the changing the fabric name and the hostname. This is the comment that I just added. So now every change that you apply to the fabric, you can comment it out so that you will be able to return back to the interview.28:05You want to understand what was the exact steps that you used or if there is an issue happened after a specific change of configuration, you can always revert and see what type of config was done during that time.28:25Now that we saw the initial config and the setup of the fabric, let's now do the bill of materials check. So if you go to bill of material, the 1st thing that you will get is the bomb calculation. This is where you will have the three options to use. You either print it.28:40Get out and go speak with the Cisco partner or directly with your Cisco account team. You can.29:00Exported into a CSV file and if you want sorry you can share it through an email. And lastly, you can request an estimate ID which will automate the request and provide you with a bomb calculation immediately or automated without the need for.29:06For any intervention, this estimate will be shared directly with you as well as with your Cisco partners so that they will see exactly what was requested.29:26Now if you have this already done, you can review your estimate IDs under the estimate ID request. This is where you will see all the rest of estimate IDs that you have. So you can request estimates to different type of fabrics if you want to understand how much it will cost for each of them.29:38Lastly, we have the assembly list. This will use the fabric that you have and show you a switch by switch or node by node. What will be each of the material that you have in bill of material, how they will be associated to. So you can see for leaf one, this is the, the switch itself. We have two power supplies that.29:56Will be needed and we will have six, ok? Now, if we start adding sfps, cables, et cetera et cetera, you will start seeing mapping of these devices to your bill of material as well as adding them to each of the assembly list for their specific notes. You can see that exactly for the leaf two.30:16So it will go through to each of the devices that you have available in your fabric.30:36Okay, so now we went through a couple of the tabs that we have. Now let's go ahead and check a little bit or understand a little bit about the different port configuration that we can apply.30:43So here under ports, you can filter out your devices to different to to the different either you can do it from inside the switch or you can do it inside the fabric itself to see the list of ports for both leaf one and leaf two in this scenario.31:00Okay. Now if we try to change the port, type for one of the devices that we have, yeah. This is something that I I forget to mention is that as you can see here in the top right, it's showing me as switch to edit mode.31:18So by using the hyper fabric, there are two main modes that you can see. It's either the edit mode or the running mode. Whenever you are in the.31:38Running mode, it means that you wouldn't have any, right, privileges. You will only be able to see or view or read access towards the hyper fabric. If you if you transition towards the edit mode or edit view, then you.31:49You will be able to do the changes to your configuration. As you can see previously, whenever I selected the port, I didn't have the options to do any configuration, and this was because I was using the running mode, not the edit mode.32:08Okay, so as an example, I will just select one of the ports and let's select port rules. So you can see here we have mainly four ports, rules. There is the fabric one which indicates that this interface is being used as an interconnection between the different devices I have.32:25Then we have the host.32:44Mode. This is where we are indicating that this interface will be connected to downstream servers. Then we have the routed mode. This is where we use the layer three interfaces to establish routing connectivity. And lastly unused, this is where we map this interface that it will not be.32:47Used and this will be the default status by the way, that you would see on all of the.33:06Interfaces that haven't been configured. Now we will go back to this part of the configuration. I just wanted to review the different port types that we have. Now let's start by doing some cabling, so now we want to run the cabling between our fabrics.33:13Directly. Okay, for the inter fabric connectivity.33:32So let's run cabling. This will automatically do the cabling for us. If you want to edit the cabling, you can select go to the group connection under the switch group. You select the connection type.33:35And then what type of, cabling strategy that you want to use. Since they are two switches, we don't have much cabling strategy, they will be directly connected to each other. We can also try to change what will be the SFP that will be used as well as the maximum.33:52For speed. In my scenario, we will be using the QDDB 400 CU 3 m and this I put it on the wrong side under the search.34:12And we will be using this as our SFP, so you can see now it has changed and let's select, and now let's preview the cabling. Now we can see that 31 and 32 from each side will be connected to each other.34:29Oops I closed it by mistake and let's save and run the cabling. Now if you go back to our cabling, you can see now it has changed to use the specific SFP that I provided and it will be connected between 31 and 32 on each of the site.34:47That we have. Okay, so now that we have created our direct connectivity between the fabrics, let's start creating some of our configuration that will be needed. So the 1st one is that we can create our, sorry, we can create our VRF.35:07Which is under our route, our route tables. You can add a route table here. This is the VRF, which VNI will be used. This can be automatically created or if you want to manually do it, you can do it manually. Let's name this as VRF one and.35:35If I need to add any notes, I can do it directly from here. Before I do that, let me just review the configuration, the one that we did, we're changing the SFP comment, and then we can see this is interfabric.35:51Configuration.36:25Okay, let's go back to our VRF creation. Again, I was changed to edit mode, add routing VRF one and you create our VRF. Now let's start with creating our vnis after that. We will need to have the VRF available so that we can match.36:29Up our vnis to the VRF.36:49And let's create each of the ones that we have. So this is for VM, VRF one, network one. This will use VRF one and the IP version four addresses will be 172160 one/twenty four.36:53If you require any route tag addition or if you want to do to add IP version six, you can do those directly from here. So this is our 1st logical network created. Let's create another 01:00 P.M..37:12VRF one, network two, under VRF one and the subnet will be 17216 11/twenty four. Now that I have created my logical vni's or networks or VNI.37:27Let's.37:47Now or the next step for us is to associate those logical vnis with the specific VLANs that will be matching to our interfaces. Remember previously I told you that whenever we want to, create or associate the VLANs or use this connection to servers, we need to change this to host ports. You will see.37:48See that if you try to do the VLAN membership.38:08And we choose the 1st one, e.g., we select both switches and we can select both interfaces. You can see that it will show you that these interfaces are not host ports, so you require to change those to host ports in order for us to.38:11Associate VLANs directly to it. So let's go to port configuration.38:31Of course, you can always specify the amount of interfaces that you want to select. This way it will make your life easier. We select all of our ports, 112112 on both sides and edit port roles. We change it to host and save.38:36By the way, on the top, you can see there are now ten pending changes, so every time we do any change on the config, you will see it on the top. It will start increasing. Okay, so now let's go to VLAN membership.38:58Add VLAN membership for the 1st VRF for both leaves, interface one one and one two, and the VLAN will be one oh one.39:14And let's do the other. One leaves, one one oh two, and the network will be one oh two. So now we have added both of our networks to and mapped those VLANs towards our VNI and added.39:33Give them directly to the interfaces that we have created as a postponest. So now we are done with part of the configuration. Let me go ahead and review configuration. You will see here the review of the config exactly what you have just done.39:53And we can see VNI and layer two config creation and let's push it. Now remember all of that can be seen under our event viewers, so you will see everything that we I just did for every comment comment.40:11Bit of configuration change, I can now see it under the event viewer here.40:30Now let's go ahead and start doing some layer three configuration. Now for the layer three configuration, we will need to create some routed ports. So let's go to port configuration again. We will do it on the interfaces number.40:3764. Now, if you have more interfaces, you can end it out by 64. If that's not, not the case, you can leave it open without the issue. And let's edit the 1st one which is on leaf one.40:52Of course I need to change it to edit mode, edit port roles, this will be routed. We can do it for both. Routed and safe. Now that both interfaces are now changed to routed, let's start putting some of the con.41:08Configuration on each of those interfaces. For that we go under actions for each of the interface.41:28We have, if you want to change the speed of the interface, you can do it from here. For us, we will enable VLAN tagging. We will add a sub interface, it will use VLAN tag Ten.41:35Sorry, under VRF one and the IP address will be 190-21-6082 hundred.6/thirty the admin status up and if I want to provide any description.41:51Okay, let's save it. Now you can see here there is number one next to our interface. If you check it, if you open it, you will see the sub interface configuration that we just did. Let's do it for the other interface from other from the other switch.42:07Similarly enable VLAN tagging, add some interface, also VLAN ten, and we will use the IP 192168 210.42:27I don't remember if I did it on the other side. Let me check it now. This is under VRF one and save. So let's see here, then/thirty VRF 16/thirty. So now I have my routed interfaces created, my sub interface.42:44Created. The next step is that I want to use use those routed interfaces for BGP configuration. So that can be done directly from the.43:04Leaf switches and you can see sorry we can do it from the fabric BGP, and this is where we can do some peering either from routed interface or host interface. Now in hyper fabric, you will see in the.43:17Configuration guides. There are two sets of routing that can be done, either northbound, which is peering from the routed interface or you can do it southbound, which is routing from the host ports directly.43:36Okay, give me a second, sorry. Okay, so now you can view your BGP.43:51Configuration from here if it was done, let's go and start creating our configuration. So we will do it under our VRF that we have created and we will create BGP peers for it. So I went to our VRF, BGP peers, and then add the BGP peer. Now we will do it.44:11But as I explained, either from a routed interface or from a host interface, let's do it from routed interface and let me get the names as well as the.44:31Okay, so just to make it easy, I will just copy the name, the address will be 192168.44:44205 and we will use the routed interface six. This will be EBGP and the peer here as will be six five.45:00201. And I don't want to add any import or export policy. Let me just confirm the that this is the configuration.45:19I made a mistake, this is 200 and switch one exactly from this interface to be a single hop. Exactly.45:37All right.46:05For some reason I'm not able to add it. Let me just edit this here for our local AS number save and try again maybe because I forget to do it, search one.46:07Two hundred.five. We will use the.six. This is our routed interface. It will be EBGP single hop and 65201200I mean.46:27And now we can add yes ok what does it say? Oh, I made the mistake, sorry. So this is one.46:48Save add BGP from route it, five EBGP 5200, and we can.47:01This as it is. Yeah, so now we added our 1st peer. So now 2nd peer is to be added from 2nd sub interface. Similarly, it will have the same, but just a different name.47:18The IP will be the same but.nine and now you can see we we are showing a different interface now which is on leaf two. EBGP 65200.47:34Now in the single home and let's add it. Okay, so now we have added both of the interfaces as you can see on most of BGP peers, each one of them from each of the interfaces that we have. So now we can, after we have done this.47:52We can go back to the fabric, review the config and comment that configuration. So you can see now this is the updated for the interfaces. We changed them to routed interfaces, then we created the sub interfaces and then under the V.48:11RF, we created our two BGP neighbors from each of the switches.48:31So I will put here layer three and BGP configuration and let's push the configuration. So now I have created all of the configuration that will be needed for my fabric but.48:36Still I haven't associated any of the devices that I have. So still we are only creating a test environment without applying any switches. You can also review the bill of material.48:56As you can see now, it's, it has added the sfps that I have associated with the fabric. Previously it didn't have it under the assembly. Also, it will show you what optics you have and where it will need to be added.49:10And if you want the step by step guide as Patrick explained in the slides, you can go through the on site and then you will have a step by step guide, and you can assign yourself as you are the one who's working for that specific task, and then you can.49:29See all of the tasks, so the 1st one, check put the server in the rack, check that the fans are present, be a power supplies, check that it's in the designated area or put it in the designated area, connected the management port to the management network, et cetera et cetera. Now once you are done with both of them, it will ask you.49:49You to climb and bind those two towards the leaf switches and then it will help you out with connecting the leaf to leaf interfaces, so it will show you what type or which interface you will need to use.50:09And then you do it for 2nd leaf, et cetera. So you will see it will help you out whenever you get to the data center to give you a list of tasks of what exactly needs to be done. Okay, so now that we are done and we have our fabric ready, the next step for us is to start binding our fabrics.50:24So binding our fabrics is the way for us to actually start associating the switches that we have discovered, that we have claimed with the leaf switches that we have. So let's go for the 1st leave, we change.50:44From running to edit mode and then we bind it. Now, once you select the bind, it will give you the option for the devices that you have claimed and you can select the device that you want. Now, the only thing that I need to make sure is that I choose a proper one.50:59So.51:19Now you will have to, the two option, you can either utilize the configuration that was already done on the switch, on the device itself. So you in that option you use configuration from the device or you can utilize the configuration that you have in your blueprints in the, in this scenario, we don't have any. So it will actually.51:20To wipe.51:40Everything that we have, which will mean that we will lose access to the to the switch. So in our scenario, we will utilize the configuration from the device and find it immediately. And now you will see it was removed from the discovered switches and now it's showing as directly on the, on the leaves.51:41Let's go and do exactly the same for 2nd one. Select that one and we will utilize configuration from the device and bind it. Now you can see we don't have any more discovered devices to, to bind.52:01Now all of our switches have been bound successfully under now if we go to the device inventory, now the host name is showing the host name the serial number for the switches. And now we can review the configuration and.52:19Apply this configuration towards the switches. So let's do that.52:39Let's review our configuration, which is the addition. As you can see, these are the configuration for the management interface, and here finding leave switches.52:43Now you will see the color has changed for each of the leaves that we have. We are now going to the day two part of the, of the demo, which is how you can see the configuration status. So if we go to the BGP, we will see our BGP peers.53:04Now that have been created, the status is still not showing, but it should show us if everything all of the configuration is proper. If you want to go to each of the devices that you have.53:21And you can see the assertion. So what are the issues? So port link is unexpectedly up for 1314. External BGP is not setting up. So you can see all of the issues that you have, in the configuration that was created.53:36Okay? With that, I'm finished with my demo for today. Let me pass the ball to my colleague Patrick to guide us through the finalization of this session. Thank you Saif. Great demo, great demo.53:53Let me bring the slides again. Alright, thank you for answering. I I bring up one question while the demo was running actually to see what preferable design template would you option would you, would you go with?54:11And now, actually can you run the last, last question, yeah? We did deliver I'm not sure if you've been on on the other sessions that we did did deliver in these last two months. 1st one was focusing on Cisco live protect next to day two visibility and production. Then we had two sessions on micro.54:27For Segmentation.54:47On for ACI with common policy which was done last week. And this is our last session for this set of set of expert inside series. So guys if you want to see the recordings of the previous ones, I did share the link in the chat window so you can find it there. I also shared the link to the Cisco IQ and and hyper.54:48Fabric. So not in a slider but in the chat of the of the Webex on the top, you will see all trainings, so take it with you as you go. And one small ask before you go, so what we always do is, is ask you kind of feedback from your side if you need any support.55:08What do you need support for? What other topics you would like to cover us on the next? Something that you are interested, you are struggling with, let us know. There is a there is a post survey that is being shared now in the, in the Slido. If you need one on one support or or help with Cisco, just let us know fill it up so then we can.55:27Prepare more more tailored and customized session for you and and for your needs, ok? Thank you so much for attending and that's all from our side. That's everything we'll be doing. You can stay on, we will leave the session up so you can still take time to to answer the questions that we have for you.55:47And that's all. Thank you so much.56:07
About this Video
Author : Cisco Customer Success
Uploaded : June 11, 2026
Explore Cisco Nexus Hyper Fabric and Cisco IQ in a focused, end-to-end walkthrough. The recording shows how a cloud controller unifies day zero design, day one deployment, and day two operations for data center fabrics. It covers template-driven spine-leaf or mesh builds, AI-ready capabilities, zero-touch provisioning, and an onsite web app for cabling validation with real-time checks. It walks through inventory claim by code, optional single-node cloud connectivity, Bill of Materials with CCW estimate requests, then switch binding, configuration push, and change tracking with the event viewer and actionable assertions.
Internal error
No related resources available.