Smartswitch DPU Redirection in NDFC VXLAN/EVPN

Welcome to the smart switch DPU regression with Nexus dashboard. In our agenda, we will see a VXLAN topology and the DPU radiation steps.00:06So this is our topology. We have a properly functioning VXLAN public and we want to redirect traffic from VLAN 2300 zero one to VLAN 2300 specifically to the CPU in order to perform policy enforcement.00:21In order to networks to the DPU, we will follow these steps. 1st, we will enable DPU redirection at the BRF and network level in the Nexus dashboard GUI. Second, we will configure the policies for the desired traffic filtering.00:42Once we have configured the traffic redirection in the nexus dashboard and the hypershield policies, we will run this command on the smart switch to confirm the proper DPU redirection. For instance, we will see MPU policies being deployed, DPU interface counters, and hypershield policies.01:03As we can see here, we have our smart switch that currently it is connected as you can see it in the connectivity status. Also, if you go to integration, we can see the proper integration. In this topology.01:26We have two networks that are currently running for VXLAN that we want to redirect to the DPU. If we take a look at your host, as you can see here, we can have connectivity with the other side.01:44On the small switch, as of now we can see the current service system configuration. So the 1st step is to go over the vrfs and enable the DPU validation.02:02We choose the switch, we go edit, and here we enable secure BRF. Click on save, that's deployed.02:26Once it's completed deployment, we can take a look at the configuration of this. So now we can see here that the BRF it is included within the service system. Now we also want to proceed to do the same thing for the networks.02:52Your networks, which is the two networks that we want to use, which is my switch.03:13Next are here we also enable secure network, click on next, save and deploy. This deploy.03:33We go back to the smart switch and as you can also see, the VRF and also the are included. At this point, traffic is going to be blocked because we don't have any policies configured yet.04:00So if you go to go back to a coin, you can see the traffic is being blocked. So let's do that in the hypershill.04:18Here we're going to configure an object, give it a name, we're going to specify the subnet and we're gonna choose the BRF.04:38That we currently have on next to dashboard, click on deploy, and we will do the same thing for the destination hosts.04:59And the same thing, we're gonna choose the BRF, the next step is to configure a policy that going to make reference to those objects.05:22Name please give a name. Here you have the options to choose allow or block. In your case, for testing purposes.05:47Want to permit everything. So we have the source and destination. You can see here that you can specify the protocol and include any port if needed.06:00Let's click on deploy, and now we can go back to the CLI and test the validation and we can see.06:18We have connectivity again, back to the CLI, we can see the configuration for the DPU policies. We can see here the dpus and also the port channel.06:38You can also see the existing flows that are are being sent to the repeat. Here we can see your source and destination this command is going to show you the hypershipper.07:04Policies that we previously configured in the GUI, so that's the indication that he has been properly programmed in the in the smart switch. We can also see the counters.07:24For the DPU, as you can see here in your scenario, that DPU number three is the the one that is sending the traffic. You can see here the context increasing.07:43Answer question.08:00