

OTV also introduces the concept of dynamic encapsulation for Layer 2 flows that need to be sent to remote locations. If the destination MAC address information is unknown, then traffic is dropped (not flooded), preventing waste of precious bandwidth across the WAN. As emphasized throughout this document, Layer 2 communications between sites resembles routing more than switching. This is a significant shift from Layer 2 switching that traditionally leverages data plane learning, and it is justified by the need to limit flooding of Layer 2 traffic across the transport infrastructure. OTV introduces the concept of "MAC routing," which means a control plane protocol is used to exchange MAC reachability information between network devices providing LAN extension functionality. OTV Technology Primerīefore discussing OTV in detail, it is worth differentiating this technology from traditional LAN extension solutions such as EoMPLS and VPLS.
#CISCO MAC ADDRESS 0000.0C9F. SOFTWARE#
This document will be periodically updated every time a software release introduces significant new functionality. When necessary, available OTV features will be identified in the current release or mentioned as a future roadmap function. OTV support on Nexus 7000 platforms has been introduced from the NX-OS 5.0(3) software release. All the technology and deployment considerations contained in this paper focus on positioning the Nexus 7000 platforms inside the data center to establish Layer 2 connectivity between remote sites. In addition, OTV provides an overlay that enables Layer 2 connectivity between separate Layer 2 domains while keeping these domains independent and preserving the fault-isolation, resiliency, and load-balancing benefits of an IP-based interconnection.Īs of this writing, the Nexus 7000 is the only Cisco platform supporting OTV. The only requirement from the transport infrastructure is providing IP connectivity between remote data center sites. OTV is an IP-based functionality that has been designed from the ground up to provide Layer 2 extension capabilities over any transport infrastructure: Layer 2 based, Layer 3 based, IP switched, label switched, and so on. This document introduces a Cisco innovative LAN extension technology called Overlay Transport Virtualization (OTV). OTV Technology Introduction and Deployment Considerations

Configuring OTV on a Single Edge Device (Multicast Mode).Layer 2-Layer 3 Boundary at Aggregation.OTV Hardware Support and Licensing Information.Unicast-Only Transport Infrastructure (Adjacency-Server Mode).Multicast Enabled Transport Infrastructure.Destination Address Address Type VLAN Destination PortĠ000.856b. 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.
