cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
770
Views
0
Helpful
0
Replies
Highlighted
Beginner

N1000V mac address learning question

Hi,

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?

Thanks,

-Cindy.

             Module 3                              Module 4    

         ----------------                      ----------------

[VM1]---[Veth4     Eth3/3]---[UplinkSwitch]---[Eth4/3     Veth5]---[VM2]

1. Send broadcast pak from VM1 on Veth4

    - Source mac learned on M3:Veth4 and M4:Eth4/3, as expected

n1k# show mac address-table address 0000.dead.beef

VLAN      MAC Address       Type    Age       Port                      Mod

---------+-----------------+-------+---------+-------------------------+---

100       0000.dead.beef    dynamic 1         Veth4                     3 

100       0000.dead.beef    dynamic 1         Eth4/3                    4 

Total MAC Addresses: 2

2. Send broadcast pak from VM2 on Veth3 using same source mac

    - Source mac now learned on M3:Veth4 and M4:Veth5

    - Would have expected mac to move from M3:Veth4 to M3:Eth3/3 uplink

    - Packet counters show packet ingress on M3:Eth3/3

n1k# show mac address-table address 0000.dead.beef

VLAN      MAC Address       Type    Age       Port                      Mod

---------+-----------------+-------+---------+-------------------------+---

100       0000.dead.beef    dynamic 33        Veth4                     3 

100       0000.dead.beef    dynamic 2         Veth5                     4 

Total MAC Addresses: 2

3. Resend broadcast pak from VM1 on Veth4

    - Source mac remains learned on M3:Veth4 and M4:Veth5

    - Would have expected mac to move from M4:Veth5 back to M4:Eth4/3 uplink

    - Packet counters show packet ingress on M4:Eth4/3

n1k# show mac address-table address 0000.dead.beef

VLAN      MAC Address       Type    Age       Port                      Mod

---------+-----------------+-------+---------+-------------------------+---

100       0000.dead.beef    dynamic 12        Veth4                     3 

100       0000.dead.beef    dynamic 25        Veth5                     4 

Total MAC Addresses: 2

n1k# show running-config

!Command: show running-config

!Time: Fri Apr 12 21:37:02 2013

version 4.2(1)SV2(1.1a)

svs switch edition essential

no feature telnet

username admin password 5 ********  role network-admin

ip domain-lookup

ip host n1k 192.168.9.7

switchname n1k

errdisable recovery cause failed-port-state

vem 3

  host vmware id 4215229f-26f0-d78b-5241-ed62c554e973

vem 4

  host vmware id 4215676a-aefa-d8ea-cf4a-42ea58fda678

snmp-server user admin network-admin auth md5 0xac97948de2d9d07ad5b92e7eb74324ab priv 0xac97948de2d9d07ad5b92e7eb74324ab localizedkey

ntp server 192.168.9.1

vrf context management

  ip domain-name labdomain.local

  ip name-server 192.168.9.1

  ip route 0.0.0.0/0 192.168.9.1

vlan 1,100-101

port-channel load-balance ethernet source-mac

port-profile default max-ports 32

port-profile type ethernet Unused_Or_Quarantine_Uplink

  vmware port-group

  shutdown

  description Port-group created for Nexus1000V internal usage. Do not use.

  state enabled

port-profile type vethernet Unused_Or_Quarantine_Veth

  vmware port-group

  shutdown

  description Port-group created for Nexus1000V internal usage. Do not use.

  state enabled

port-profile type ethernet n1k-uplink

  vmware port-group

  switchport mode access

  switchport access vlan 1

  no shutdown

  system vlan 1

  state enabled

port-profile type vethernet vlan100

  vmware port-group

  switchport access vlan 100

  no shutdown

  state enabled

port-profile type vethernet vlan101

  vmware port-group

  switchport access vlan 101

  no shutdown

  state enabled

port-profile type vethernet L3-control

  capability l3control

  vmware port-group

  switchport mode access

  switchport access vlan 1

  no shutdown

  system vlan 1

  state enabled

port-profile type ethernet vm-uplink

  vmware port-group

  switchport mode trunk

  switchport trunk allowed vlan 100-101

  no shutdown

  state enabled

vdc n1k id 1

  limit-resource vlan minimum 16 maximum 2049

  limit-resource monitor-session minimum 0 maximum 2

  limit-resource vrf minimum 16 maximum 8192

  limit-resource port-channel minimum 0 maximum 768

  limit-resource u4route-mem minimum 1 maximum 1

  limit-resource u6route-mem minimum 1 maximum 1

interface mgmt0

  ip address 192.168.9.7/24

interface Vethernet1

  inherit port-profile L3-control

  description VMware VMkernel, vmk2

  vmware dvport 224 dvswitch uuid "73 a4 13 50 2c b5 71 d0-7c 99 66 00 b3 aa b7 2f"

  vmware vm mac 0050.566E.6997

interface Vethernet2

  inherit port-profile L3-control

  description VMware VMkernel, vmk2

  vmware dvport 225 dvswitch uuid "73 a4 13 50 2c b5 71 d0-7c 99 66 00 b3 aa b7 2f"

  vmware vm mac 0050.566F.5FA5

interface Vethernet4

  inherit port-profile vlan100

  description VM1, Network Adapter 1

  vmware dvport 32 dvswitch uuid "73 a4 13 50 2c b5 71 d0-7c 99 66 00 b3 aa b7 2f"

  vmware vm mac 0050.5693.330A

interface Vethernet5

  inherit port-profile vlan100

  description VM2, Network Adapter 1

  vmware dvport 33 dvswitch uuid "73 a4 13 50 2c b5 71 d0-7c 99 66 00 b3 aa b7 2f"

  vmware vm mac 0050.5693.0B49

interface Ethernet3/3

  inherit port-profile vm-uplink

interface Ethernet3/4

  inherit port-profile n1k-uplink

interface Ethernet4/3

  inherit port-profile vm-uplink

interface Ethernet4/4

  inherit port-profile n1k-uplink

interface control0

  ip address 10.3.1.1/24

line console

boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1a.bin sup-1

boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1a.bin sup-1

boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1a.bin sup-2

boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1a.bin sup-2

svs-domain

  domain id 1

  control vlan 1

  packet vlan 1

  svs mode L3 interface control0

svs connection vc

  protocol vmware-vim

  remote hostname vcenter port 80

  vmware dvs uuid "73 a4 13 50 2c b5 71 d0-7c 99 66 00 b3 aa b7 2f" datacenter-name Datacentre

  max-ports 8192

  connect

vservice global type vsg

  tcp state-checks invalid-ack

  tcp state-checks seq-past-window

  no tcp state-checks window-variation

  no bypass asa-traffic

vnm-policy-agent

  registration-ip 0.0.0.0

  shared-secret **********

  log-level

no logging monitor

no logging module

no logging console


Everyone's tags (3)
CreatePlease to create content
Content for Community-Ad

Cisco COVID-19 Survey