I have a simple lab environment running VMware vSphere 5.1.0 with two ESXi hosts, a Nexus 1000V 4.2(1)SV2(1.1a), and 2 VMs running Centos5. All of this is running as a vApp within vCloud.
I have a question about mac address learning on the N1000V switch, specifically when a single mac address migrates from a Vethernet port on one module to another, all within the same vlan (see diagram below).
Initially, I send a broadcast packet from a VM attached to Veth4 on Module 3. As expected, the mac address is learned on Veth4 on Module 3, as well as the the uplink port on the other module.
If I then send the same broadcast packet (same source mac) from the VM attached to Veth5 on the other module (Module 4), the mac gets moved from the uplink port to Veth5 on Module 4. However, the mac does not get moved from Veth4 to the uplink port on the original module (Module 3).
So, at this point, the mac address shows up on two different Veth ports in the mac address table (one on each module).
If I send the original packet again from Veth4 on Module 3, the mac address on Module 4 is not moved back from Veth5 to the uplink port.
Is there a reason why a learned mac address would migrate from an uplink port to a Vethernet port, but not the other way around?
Original Blog published @ https://blogs.cisco.com/datacenter/spinning-up-an-nvme-over-fibre-channel-strategy
Every so often there comes a time when we witness a major shift in the networking industry that fundamentally changes the landscap...
Let me start by telling you that there is already a very nice document in the Cisco Community Forums which describes the procedure to upgrade the APIC CIMC. In case you came across this document before looking into the mentioned one, here is...