Jump to content

Recommended Posts

Posted

Имеем абонентское кольцо.

 

Приходит на два ASR 9010.

 

Коммутаторы доступа D-link 3526.

 

 

Поднято управление (vlan 10):

 

interface GigabitEthernet0/5/0/17.10 l2transport
description MANAGEMENT RING-906
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric

l2vpn
bridge group RING_MGMT
bridge-domain RING_906
  interface GigabitEthernet0/5/0/17.10
   storm-control multicast pps 1
   storm-control broadcast pps 500
  !
  neighbor xx.xxx.xxx.111 pw-id 15906
  !
  routed interface BVI20906

interface BVI20906
vrf MGMT
ipv4 address 10.128.35.3 255.255.255.0

router vrrp
interface BVI20906
 address-family ipv4
  vrrp 35
   priority 150
   address 10.128.35.1

 

 

 

 

Поднят igmp multicast в двух вланах (30 и 31)

 

interface GigabitEthernet0/5/0/17.30 l2transport
encapsulation dot1q 30
rewrite ingress tag pop 1 symmetric
mtu 1518
ipv4 access-group IPTV ingress
ipv4 access-group IPTV egress
!
interface GigabitEthernet0/5/0/17.31 l2transport
encapsulation dot1q 31
rewrite ingress tag pop 1 symmetric
mtu 1518
ipv4 access-group IPTV_MEGATV_IN ingress
ipv4 access-group IPTV_MEGATV egress
!
l2vpn
bridge group multi
 bridge-domain multi
  igmp snooping profile customer
  interface GigabitEthernet0/5/0/17.30
   split-horizon group

l2vpn
bridge group multi
bridge-domain MEGATV
  igmp snooping profile customer_megafon
  interface GigabitEthernet0/5/0/17.31
   split-horizon group

 

 

Поднята схема vlan per switch, с терминирование на BRAS`e (pppoe). (vlan 101- 150)

 

interface GigabitEthernet0/5/0/17.906101 l2transport
encapsulation dot1q 101
rewrite ingress tag pop 1 symmetric
ethernet-services access-group IPOE_IN ingress
ethernet-services access-group IPOE egress
!

..................

interface GigabitEthernet0/5/0/17.906150 l2transport
encapsulation dot1q 150
rewrite ingress tag pop 1 symmetric
ethernet-services access-group IPOE_IN ingress
ethernet-services access-group IPOE egress
!

l2vpn
bridge group IPOE
 bridge-domain S-7
  interface GigabitEthernet0/3/0/1.20007
   storm-control multicast pps 1
   storm-control broadcast pps 100
  !

  interface GigabitEthernet0/5/0/17.906101
   storm-control multicast pps 1
   storm-control broadcast pps 500
   split-horizon group

.....................

  interface GigabitEthernet0/5/0/17.906150
   storm-control multicast pps 1
   storm-control broadcast pps 500
   split-horizon group
!
  neighbor xx.xxx.xxx.103 pw-id 40007
  !
  neighbor xx.xxx.xxx.104 pw-id 40007
  !
  neighbor xx.xxx.xxx.111 pw-id 40007
  !
  routed interface BVI40007

 

 

 

 

 

Дальше идет само STP.

 

interface GigabitEthernet0/5/0/17.999 l2transport
description MSTP CTRL RING-906
encapsulation dot1q 999
!

spanning-tree mstag STP_RING_906
interface GigabitEthernet0/5/0/17.999
 name STP_RING_906
 revision 5
 bridge-id 0000.0000.0906
 instance 0
  root-id 0000.0000.0906
  root-priority 4096
 !

 

Настройки на другом ASRe идентичные этим (только порты разные и все впринципе).

 

 

 

Настройка коммутатора доступа:

 

config stp version mstp
config stp maxage 6 maxhops 20 forwarddelay 4 txholdcount 3 fbpdu enable
config stp priority 32768 instance_id 0
config stp mst_config_id name STP_RING_906 revision_level 5
enable stp
config stp ports 1-23 externalCost auto hellotime 2 edge true p2p auto state disable
config stp ports 1-24 fbpdu disable
config stp ports 1-24 restricted_role true
config stp ports 1-24 restricted_tcn true
config stp mst_ports 1-26 instance_id 0 internalCost auto priority 128
config stp ports 24 externalCost auto hellotime 2 edge true p2p auto state enable
config stp ports 25-26 externalCost auto hellotime 2 edge false p2p auto state enable
config stp ports 25-26 fbpdu enable
config stp ports 25-26 restricted_role false
config stp ports 25-26 restricted_tcn false

 

 

 

И так сам вопрос. После заведения интерфейсов для STP, его конфигурирование на коммутаторах и ASR`e, оно сходится. Петли нет, абоненты работают. Все отлично.

Но есть одно НО, на ASR`e !!!единоразово!!! появляется сообщение:

 

Oct 25 22:04:49 xx.xxx.xxx.xxx 59048: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.931 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906102 and msti: 0 
Oct 25 22:04:49 xx.xxx.xxx.xxx 59048: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.931 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906102 and msti: 0 
Oct 25 22:04:49 xx.xxx.xxx.xxx 59049: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.932 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906103 and msti: 0 
Oct 25 22:04:49 xx.xxx.xxx.xxx 59049: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.932 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906103 and msti: 0 
Oct 25 22:04:49 xx.xxx.xxx.xxx 59050: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.932 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906104 and msti: 0 
Oct 25 22:04:49 xx.xxx.xxx.xxx 59050: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.932 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906104 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59051: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.934 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906105 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59051: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.934 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906105 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59052: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.935 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906106 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59052: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.935 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906106 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59053: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.936 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906107 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59053: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.936 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906107 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59054: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.937 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906108 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59054: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.937 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906108 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59055: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.938 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906109 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59055: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.938 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906109 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59056: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.939 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906110 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59056: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.939 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906110 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59057: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.940 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906111 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59057: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.940 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906111 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59058: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.941 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906112 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59058: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.941 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906112 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59059: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.942 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906113 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59059: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.942 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906113 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59060: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.943 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906114 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59060: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.943 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906114 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59061: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.943 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906115 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59061: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.943 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906115 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59062: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.944 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906127 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59062: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.944 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906127 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59063: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.944 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906128 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59063: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.944 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906128 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59064: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.945 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906129 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59064: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.945 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906129 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59065: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.945 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906130 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59065: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.945 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906130 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59066: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.946 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906131 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59066: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.946 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906131 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59067: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.946 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906132 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59067: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.946 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906132 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59068: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.947 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906133 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59068: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.947 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906133 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59069: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.948 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906134 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59069: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.948 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906134 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59070: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.948 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906135 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59070: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.948 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906135 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59071: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.949 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906136 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59071: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.949 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906136 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59072: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.950 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906137 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59072: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.950 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906137 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59073: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.950 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906138 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59073: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.950 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906138 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59074: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.951 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906139 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59074: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.951 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906139 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59075: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.952 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906140 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59075: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.952 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906140 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59076: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.952 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906116 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59076: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.952 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906116 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59077: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.953 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906117 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59077: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.953 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906117 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59078: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.953 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906118 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59078: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.953 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906118 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59079: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.954 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906119 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59079: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.954 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906119 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59080: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.955 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906120 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59080: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.955 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906120 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59081: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.956 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906121 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59081: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.956 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906121 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59082: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.957 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906122 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59082: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.957 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906122 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59083: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.958 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906123 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59083: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.958 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906123 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59084: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.959 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906124 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59084: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.959 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906124 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59085: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.959 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906125 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59085: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.959 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-8 (BD ID: 7) for interface GigabitEthernet0_5_0_17.906125 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59086: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.961 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906141 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59086: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.961 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906141 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59087: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.962 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906142 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59087: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.962 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906142 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59088: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.962 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906143 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59088: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.962 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906143 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59089: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.963 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906144 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59089: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.963 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906144 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59090: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.964 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906145 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59090: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.964 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906145 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59091: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.965 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906146 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59091: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.965 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906146 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59092: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.966 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906147 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59092: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.966 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906147 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59093: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.967 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906148 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59093: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.967 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906148 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59094: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.968 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906149 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59094: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.968 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906149 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59095: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.969 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906150 and msti: 0 
Oct 25 22:04:50 xx.xxx.xxx.xxx 59095: ASR9K.VES RP/0/RSP0/CPU0:Oct 25 22:04:49.969 : l2vpn_mgr[1124]: %L2-L2VPN-4-BD_MST_LOOP : Potential MST forwarding loop in Bridge Domain S-7 (BD ID: 6) for interface GigabitEthernet0_5_0_17.906150 and msti: 

 

Эти сообщения чисто информативные? Либо это самом деле что то опасное. Как тогда это лечить?

 

Заранее спасибо за ответ.

 

з.ы. спойлер не нашел чей-то...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...
На сайте используются файлы cookie и сервисы аналитики для корректной работы форума и улучшения качества обслуживания. Продолжая использовать сайт, вы соглашаетесь с использованием файлов cookie и с Политикой конфиденциальности.