Configuring Endpoint Locator in NDFC

Hello. My name is Tomas Klenschnik. I'm a Cisco data center network subject matter expert with the Cisco technical education team. In this video, you will configure endpoint locator feature in Nexus dashboard fabric controller. You will begin with importing and deploying an existing VXLAN EVPN fabric into Nexus dashboard fabric controller. Then you will configure endpoint locator feature, and you will finish with verifying Endpoint Locator dashboard. Let's look at an example where you have implemented a testing VXLAN EVPN fabric called Fabric one with three leaf and one spine switch in your environment. There is an ESX host with two virtual machines, server two and server three, connected to leaf two and leaf three switches. Your first task is to create and import an existing fabric one fabric in Nexus dashboard fabric controller. You will add switches to fabric one in Nexus dashboard fabric controller and preserve their configuration. Now you would like to enable the endpoint locator feature in Nexus dashboard fabric controller which helps you locate the endpoints connected to leaf switches. This would be very useful when you must troubleshoot or locate one from hundreds of endpoints inside your data center. You will enable and configure endpoint locator feature. In the end, you will verify and explore the list of active endpoints in the endpoint locator dashboard in Nexus dashboard fabric controller. First, open and log in to Cisco Nexus dashboard fabric controller. Begin with import and deployment of an existing fabric. Navigate to LAN and click on fabrics. Click on actions and choose create fabric. Give your fabric a name. In this example, use fabric one and click choose fabric. Since your network is a VXLAN EVPN environment, choose data center VXLAN EVPN template and click select. In the general parameters tab, in the BGP autonomous system number field, enter sixty five thousand two. In the advanced tab, notice that site ID field is set to sixty five thousand two. In the resources tab, change the first quote of all underlay IP address fields from ten to twenty. Scroll down and change the first quad of the VRFLite subnet IP range field from ten to twenty. Click save. You can now see a new fabric called fabric one in the list of LAN fabrics with VXLAN fabric technology and switch fabric type. Double click fabric one fabric. Navigate to switches tab, click on actions, and choose add switches. In the seat IP field, enter the management IP of one of the leaf switches that is one nine eight dot one eight dot four dot two zero one for this example. Enter the username and password for the admin user. You want to import an existing fabric, so make sure the Preserve Config checkbox is checked. Then click Discover Switches. In the Warning window, click Confirm. In the Discovery Results pane, check the Select All checkbox and then click Add Switches. Wait for a couple of seconds until the status shows Switch added. Click Close. You now see switches listed in the Switches tab. Discovery status is okay. Select Spine two switch, click Actions, and choose Set role. This is a Spine switch, so select role Spine and click Select. In the Fabric Overview window, click Actions. Click Recalculate and Deploy. After a few seconds, you can see switches are out of sync and they have a number of lines in pending configuration. Click deploy all. Wait for a couple of seconds for status to go from started to success on all switches. Click close. Notice the config status is success. Close the fabric overview display, click topology, and then double click fabric one fabric. You can observe the fabric one topology, two networks, and one VRF were imported and deployed in the fabric. Now configure the leaf two ethernet one three interface, which is connected to the Nexus dashboard fabric controller data interface in this example. In the menu, click LUN and fabrics, and then double click fabric one fabric to open the fabric details. In the window, click the interfaces tab and then in the filter field choose device name equals leaf dash two and interface equals ethernet one slash three. In the fabric overview window, check the box next to leaf two and then click actions and choose edit. In the policy list, select EPL routed to configure a layer three interface for endpoint locator feature. In the interface IP field, enter one nine eight dot one eight dot four dot one in this example. In the IP netmask length field, enter twenty four in this example. In the free form config field, enter iprouter ospf underlay area zero point zero point zero point zero to enable OSPF on the interface for this example. Click save, then click deploy, and then click deploy config. Click X to close the edit interface window. In the fabric overview window, click actions, then more, and choose configure endpoint locator. In the endpoint locator dialog, check configure my fabric. In the spine slash route reflector one drop down, select spine two in this example. For collect additional information, select yes and then click save config. Wait for Nexus Dashboard Fabric Controller to enable the endpoint locator feature. The endpoint locator feature relies on BGP peering established between Nexus Dashboard Fabric Controller and the route reflector. After you establish the BGP session, Nexus dashboard fabric controller receives BGP updates from the route reflector with endpoints information. Open a PuTTY session to Spine two. On Spine two, enter show BGP l two VPN EVPN summary to verify a new BGP session with the Nexus dashboard fabric controller IP address. In this example, one nine eight point one eight point four point one nine nine for the endpoint locator feature. Go back to Nexus dashboard fabric controller user interface. Press X to close the fabric overview window. In the menu, click dashboard and then in the dashboard window, click endpoint locator. The endpoint activity screen is populated by the recently configured endpoint locator. The endpoints are server two and server three, which are located on leaf two and leaf three switches. Scroll down to the list of active endpoints table, then click one zero point one zero point one zero point one one, which is the IP address of server two, and then click endpoint live. This shows that the endpoint IP ten dot ten dot ten dot eleven is on leaf two and hasn't moved recently. Endpoint locator provides near real time tracking of every endpoint. Events such as an endpoint coming up, an endpoint going down, or an endpoint move are now visible with a few simple clicks. This concludes the Cisco technical education video on configuring endpoint locator feature in Cisco Nexus dashboard fabric controller. Thank you for watching.