Enter the feature-set fabricpath command to enable FabricPath on each device. You enable FabricPath on each device before you can view or access the commands.FabricPath interfaces carry only FabricPath-encapsulated traffic.
I have no idea if this is a fabricpath bug, also i have no idea what is the purpose of the port 15 and where to find documentation about it and i would like to understand why this mac moves are occuring, i would appreciate any kind of help.FabricPath switching has the following configuration guidelines and limitations: Also this is the only vlan that is in "Non-Conversational-learning" and by coincidence is the only one where mac moves are occuring. How can this be, If vlan 100 is configured has "mode fabric". N7K01-CPDA-CORE1# sh mac address-table learning-mode vlan 100
What is interesting is when i run the command "show mac address-table learning-mode vlan 100" is show as non-conversational. Accordding to Cisco documentation all vlans in mode fabric have only one mac address learning mode which is "conversational learning".Īll the vlans on the Nexus core are configured has "mode fabric". I have been reading the Cisco Nexus 7k Fabricpath document and i found out something interesting which might be only a coincidence, but still interesting. It is important to note that all the other branches that connect through VPCs to not show this behaviour.
I have been looking for fabricpath documentation on flooding but so far i haven't found any (if someone has any please share), also the port 1 correspond to the eth1/22 on nexus CPDA which is the physical port where the remote branch is connected.įrom these logs the only conclusion i have been able to get, is that the mac addresses on these vlan are rebounding form the physical port to this flood lid port on the nexus CPDA and back, and i have not been able to understand really why. N7K02-RECT-CORE2 %L2FM-4-L2FM_MAC_MOVE: Mac 408d.5c39.0e4c in vlan 100 has moved from 15 to 1įrom nexus RECT i have been able to decipher the foreign port of nexus CPDA which apparently looks like it is flood of some kind. On the nexus RECT which has the same kickstart version 6.2.(16), but the last reset shows system version 6.2(10), i can see the logs properly. I am unable to identify the port of origin because most probably there is a bug on this version which is 6.2(16). The nexus CPDA is directly connected to this remote branch and as the switch-id of 100, i can see that there is a mac move from a foreign port to the port where the remote branch is connected to. Since the beginning of times i see mac moves on only one of the vlans that goes through this link, and so far i have been unable to figure out why is this happening, the Vlan in question is VID 100. The link that connects this remote branch as no special configuration, is just a L2 link with the spanning-tree disable. All the remote branches connect to the core network via a VPC, except one remote branch that connects to the core network via a single link, therefore is connected only to one of the core nexus. They are inter-connected with a fabricpath mode port-channel.
#Cisco fabricpath mac address learning series#
I have been troubleshooting a mac move behaviour on my core network, which is made of 2 Nexus 7K with F3 series modules.
0 kommentar(er)
