The VN that you chose to do L2 handoff for should now have its checkbox checked. LetвЂ™s input this into the GUI:Д¬lick on вЂSaveвЂ™ now and you should go one page back. In my case, the interface that connects to the legacy switch is Gi1/0/12 and the legacy VLAN is 666. Additionally, you need to provide the external VLAN number - this is the legacy VLAN number that is in use in the legacy network for this subnet. This is where some input needs to be given - you need to provide the external link that connects to the legacy network (this is a drop down menu and lists all the interfaces on the box - you simply need to choose the relevant interface). Once you do this, the following page will be displayed: In our case, we are interested in extended an IP pool within the Guest_VN, so thatвЂ™s what we are going to select. As you can see, all VNs that have an IP pool assigned to them will be listed here. For the purposes of this post, we are interested in L2 handoff so thatвЂ™s where our focus will be. In this page, you should see two major options - Layer 3 Handoff and Layer 2 Handoff. Within the вЂњFabricвЂќ tab here, click вЂњConfigureвЂќ: Once you do this, you should see the various details about Border1: In my case, IвЂ™d like to use Border1 for this purpose, so letвЂ™s click on Border1. Under вЂFabric InfrastructureвЂ™, you should see your fabric:ДЄt this point in time, only one border can be used to do L2 handoff. Under вЂProvisionвЂ™, go to the вЂFabricвЂ™ tab. The L2 handoff configuration flow is quite similar to е…ѓ handoff. The biggest question that I always try to answer will also be addressed - HOW does it really work? L2 handoff configuration

This post will walk you through the provisioning of L2 handoff via DNAC and help you understand what kind of configuration is pushed to make it work. For these kind of situations, a feature called L2 handoff was introduced. The requirement is to have this subnet co-exist in the fabric as well as outside the fabric, within a legacy portion of the network.ДЇrom the perspective of our topology, we have the 192.2.21.0/24 subnet that needs to extend between the legacy network and the SD-Access fabric. The premise is this - say you have subnet X that youвЂ™re going to be migrating into SD-Access but it cannot be done in one shot or one window. This is a fairly common scenario that you might run into with customerвЂ™s migrating to SD-Access. WeвЂ™re going to continue working with the following topology for this post, with a legacy network added to the existing infrastructure: Get yourself some coffee because youвЂ™re going to be here for a while! Introduction and topologyДЇair warning - this is going to be a long, long post. Destination Address Address Type VLAN Destination PortД this post, we take a detailed look at the L2 handoff feature in CiscoвЂ™s SD-Access. If you were looking for a device you could ping it, look at the arp table to get the mac then use the mac command to find the port. It is used to record a stations mac address and itвЂ™s corresponding switch port location.'Д®xample: Port 17 has a device plugged in with this mac address.

Here is a quote from 'The CAM table, or content addressable memory table, is present in all Cisco Catalysts for layer 2 switching. I know you don't want to know about the ARP command but this command and the ARP command together you can find devices on your switches. I'm not sure why it's labeled Destination Address.

The MAC table or CAM table only records source addresses. It identifies the mac address that is on that port. The column title in the command is a destination address. It will show multiple MAC addresses on the uplink port that connects to other switches. That's why I showed it two different ways. Some switches/ios versions have a slight variation of the command. Show mac-address table or show mac-address-table will give you the interface (the given name, not the name you assign it) and MAC Addresses.

Cisco mac address 0000.0c9f.