ME-3800-X : Problèm Flappin @mac on vpls

Unanswered Question
Oct 13th, 2011

Hello,

I have a network based on ME-3800-X

I use MPLS/Vpls technologie and too VRF/MPLS

The VPLS works but at times, there has @mac flapping between tunnel EoMPLS of VPLS.

For exemple :

Oct 13 05:52:46: %SW_MATM-4-MACFLAP_NOTIF: Host 0016.177b.17e1 in vlan 3990 is flapping between port VP6 and port VP7

Oct 13 05:52:59: %SW_MATM-4-MACFLAP_NOTIF: Host 0016.177b.17e1 in vlan 3990 is flapping between port VP9 and port VP5

Oct 13 06:02:56: %SW_MATM-4-MACFLAP_NOTIF: Host 0016.177b.17e1 in vlan 3990 is flapping between port VP5 and port VP8

Oct 13 06:03:58: %SW_MATM-4-MACFLAP_NOTIF: Host 0016.177b.17e1 in vlan 3990 is flapping between port VP9 and port VP6

Oct 13 06:04:49: %SW_MATM-4-MACFLAP_NOTIF: Host 001c.c436.6410 in vlan 3990 is flapping between port VP7 and port VP5

Oct 13 06:08:27: %SW_MATM-4-MACFLAP_NOTIF: Host 0016.1780.68df in vlan 3990 is flapping between port VP5 and port VP8

Oct 13 06:11:14: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.0b62.4990 in vlan 3990 is flapping between port VP7 and port VP5

Oct 13 06:26:28: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.0b62.4990 in vlan 3990 is flapping between port VP7 and port VP5

Oct 13 06:43:38: %SW_MATM-4-MACFLAP_NOTIF: Host 0016.1726.0459 in vlan 3990 is flapping between port VP1 and port VP5

Oct 13 07:07:44: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.0b62.4990 in vlan 3990 is flapping between port VP7 and port VP5

Oct 13 07:07:46: %SW_MATM-4-MACFLAP_NOTIF: Host 001e.0b62.4990 in vlan 3990 is flapping between port VP5 and port VP9

Oct 13 08:48:58: %SW_MATM-4-MACFLAP_NOTIF: Host 0016.1780.6c03 in vlan 3990 is flapping between port VP7 and port VP1

Oct 13 08:50:07: %SW_MATM-4-MACFLAP_NOTIF: Host 0090.ec08.0f66 in vlan 3990 is flapping between port VP7 and port VP1

Oct 13 09:23:52: %SW_MATM-4-MACFLAP_NOTIF: Host 001d.920c.0bd2 in vlan 3990 is flapping between port VP7 and port VP1

Spit-horizon is OK on VPLS.

I think a bug

An other question :

How to see who is the end for VP xx ??

ME-3800-X , Version 15.1(2)EY

Configuration for VPLS, ( E-BGP

!

l2 vfi L2_NM_L2 autodiscovery

vpn id 3990

!

interface GigabitEthernet0/1

description Inerco L3 - DSI

switchport trunk allowed vlan none

switchport mode trunk

service instance 3990 ethernet

  encapsulation dot1q 225,256,726,728,733-737,741,743,755,1000

  bridge-domain 3990

!

interface Vlan3990

description VPLS_VOIP_SIA

no ip address

xconnect vfi L2_NM_L2

end

******

Regards,

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Anand Ram Thu, 10/13/2011 - 08:20

Hello Auvinet,

You could check you VFI status and the neighbors it connects through using the command

1) show mpls l2 vc - if you know the vpn id, you should see all the neighbors for that VFI

2) show vfi "VFI name"

As for the MAC flaps, there seems to be some STP issue happening in the L2 VLAN somewhere. I would suggest checking your sites for STP loop

Regards,

Anand

a.auvinet Fri, 10/14/2011 - 02:06

hi Anand,

No information for VP

There 's no loop in the network, No spanning tree.

I am sure.

sw_pn_cun101_tb#show mpls l2 vc

Local intf     Local circuit              Dest address    VC ID      Status

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

VFI L2_NM_L2   VFI                        172.30.0.2      3990       DOWN

VFI L2_NM_mgmt  \

               VFI                        172.30.0.2      3999       DOWN

VFI L2_NM_L2   VFI                        172.30.0.3      3990       UP

VFI VPLS_TAN   VFI                        172.30.0.3      3998       DOWN

VFI L2_NM_mgmt  \

               VFI                        172.30.0.3      3999       UP

VFI L2_NM_L2   VFI                        172.30.0.4      3990       DOWN

VFI L2_NM_mgmt  \

               VFI                        172.30.0.4      3999       DOWN

VFI L2_NM_L2   VFI                        172.30.0.5      3990       UP

VFI L2_NM_mgmt  \

               VFI                        172.30.0.5      3999       UP

VFI L2_NM_L2   VFI                        172.30.0.6      3990       UP

VFI L2_NM_mgmt  \

               VFI                        172.30.0.6      3999       UP

VFI L2_NM_L2   VFI                        172.30.0.7      3990       UP

VFI L2_NM_mgmt  \

               VFI                        172.30.0.7      3999       UP

Vl959          Eth VLAN 959               172.30.0.8      959        UP

VFI L2_NM_L2   VFI                        172.30.0.8      3990       UP

VFI VPLS_TAN   VFI                        172.30.0.8      3998       DOWN

VFI L2_NM_mgmt  \

               VFI                        172.30.0.8      3999       UP

VFI L2_NM_L2   VFI                        172.30.0.9      3990       DOWN

VFI VPLS_TAN   VFI                        172.30.0.9      3998       DOWN

VFI L2_NM_mgmt  \

               VFI                        172.30.0.9      3999       UP

VFI L2_NM_L2   VFI                        172.30.0.10     3990       DOWN

VFI L2_NM_mgmt  \

               VFI                        172.30.0.10     3999       UP

VFI L2_NM_L2   VFI                        172.30.0.11     3990       UP

VFI L2_NM_mgmt  \

               VFI                        172.30.0.11     3999       UP

                                          172.30.0.12     3998       DOWN

sw_pn_cun101_tb#sh vfi name L2_NM_L2

Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: L2_NM_L2, state: up, type: multipoint

  VPN ID: 3990, VPLS-ID: 65000:3990

  RD: 65000:3990, RT: 65000:3990

  Local attachment circuits:

    Vlan3990

  Neighbors connected via pseudowires:

  Peer Address     VC ID        Discovered Router ID    S

  172.30.0.3       3990         172.30.0.3              Y

  172.30.0.2       3990         172.30.0.2              Y

  172.30.0.9       3990         172.30.0.9              Y

  172.30.0.10      3990         172.30.0.10             Y

  172.30.0.11      3990         172.30.0.11             Y

  172.30.0.7       3990         172.30.0.7              Y

  172.30.0.6       3990         172.30.0.6              Y

  172.30.0.5       3990         172.30.0.5              Y

  172.30.0.8       3990         172.30.0.8              Y

  172.30.0.4       3990         172.30.0.4              Y

yashfaqu Fri, 10/14/2011 - 02:24

Most probably your are hitting CSCts07998, Wait for the fix

Anand Ram Fri, 10/14/2011 - 03:10

That is very interesting. A very close match.

Auvinet,

Do you what triggered these logs? Any commands executed on any of the PEs in the VP?

Regards,

Anand

Ricardo Suarez Gamez Fri, 10/14/2011 - 08:57

Hi guys:

I have the same problem but no access to CSCts07998 details.

Could anybody please include here those details (description, severity, workaround, etc)?

Regards

Ricardo

TIGMA AIT Mon, 02/02/2015 - 02:25

Hi,

 

4715575: .Feb  2 5:09:29.406: %SW_MATM-4-MACFLAP_NOTIF: Host 4c1f.cc1b.742 in vlan 1232 is flapping between port VP7 and port VP1

 

ME3800#sho vfi nam 3GH

Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: 3GH, state: up, type: multipoint
  VPN ID: 1232
  Local attachment circuits:
    Vlan1232  
  Neighbors connected via pseudowires:
  Peer Address     VC ID        S
  10.0.200.26      331916232   Y
  10.0.200.93      331913232   N
  10.0.200.46      331916232   Y
  10.0.200.29      331919232   Y
  10.0.200.11      331911232   Y
  10.0.200.10      331910232   Y
  10.0.200.208     331911232   Y

 

How should I do next?

a.auvinet Mon, 02/02/2015 - 03:10

Hi,

 

I don't know....

I think macflapp occurs when a type of  multicast packets go across the MPLS VPLS.

It's a Bug.

I have also same problem.

 

 

 

 

 

 

Actions

Login or Register to take actions

This Discussion

Posted October 13, 2011 at 2:05 AM
Updated October 13, 2011 at 2:06 AM
Stats:
Replies:7 Overall Rating:
Views:1388 Votes:0
Shares:0
Tags: No tags.
 

Discussions Leaderboard

Rank Username Points
1
mheusinger
918
2
swaroop.potdar
902
3
Giuseppe Larosa
752
4
mohammedmahmoud
263
5
pkhatri
257
Rank Username Points
Mohamed Sobair
5
CSABA GARAI
5
Jon Marshall
5
jcozzupoli
3