Interface UP and Down

abdulkarim041 · ‎04-24-2016

Hi

My client has a Cisco 3560 switch. Gi0/2 and Gi0/6 ports have been configured as a trunk and commented with Red-line wireless equipment. Port

Gi0/23 has been configured as a trunk bit connected with core switch.

Issue: Sometime link flapping has been observed as under

Log Buffer (4096 bytes):
40a8.f029.0594 in vlan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:35:22.209 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 549f.3500.07c2 in v
lan 113 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:44:14.280 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f029.0594 in v
lan 105 is flapping between port Gi0/6 and port Gi0/23
Apr 14 2016 15:44:14.380 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 549f.3500.07c2 in v
lan 113 is flapping between port Gi0/6 and port Gi0/23
Apr 14 2016 15:44:14.447 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f027.e170 in v
lan 105 is flapping between port Gi0/6 and port Gi0/23
Apr 14 2016 15:44:14.481 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host f8bc.1256.296a in v
lan 113 is flapping between port Gi0/6 and port Gi0/23
Apr 14 2016 15:44:14.716 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 549f.3500.1806 in v
lan 113 is flapping between port Gi0/6 and port Gi0/23
Apr 14 2016 15:44:14.816 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host a0ec.f9bb.7e7f in v
lan 105 is flapping between port Gi0/6 and port Gi0/23
Apr 14 2016 15:44:14.984 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 0050.568d.5b77 in v
lan 103 is flapping between port Gi0/6 and port Gi0/23
Apr 14 2016 15:44:41.214 GMT: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inco
nsistent peer vlan id 26528 on GigabitEthernet0/6 VLAN103.
Apr 14 2016 15:44:41.214 GMT: %PM-3-INTERNALERROR: Port Manager Internal Softwar
e Error (vlanid >=0 && vlanid < PM_MAX_VLANS: ../switch/pm/pm_vlan.c: 1279: pm_v
lan_get_vlan_data)
-Traceback= 1BB0AC4 1C14E80 1C23D40 11FFB60 120448C 11B2EC8 11B3FA8 1F16C28 1F0D
6A0
Apr 14 2016 15:44:41.222 GMT: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthe
rnet0/6 on VLAN0103. Inconsistent local vlan.
Apr 14 2016 15:44:45.492 GMT: %PM-3-INTERNALERROR: Port Manager Internal Softwar
e Error (vlanid >=0 && vlanid < PM_MAX_VLANS: ../switch/pm/pm_vlan.c: 1279: pm_v
lan_get_vlan_data)
-Traceback= 1BB0AC4 1C14E80 1C23D40 11FFB60 120448C 11B2EC8 11B3FA8 1F16C28 1F0D
6A0
Apr 14 2016 15:44:46.138 GMT: %PM-3-INTERNALERROR: Port Manager Internal Softwar
e Error (vlanid >=0 && vlanid < PM_MAX_VLANS: ../switch/pm/pm_vlan.c: 1279: pm_v
lan_get_vlan_data)
-Traceback= 1BB0AC4 1C14E80 1C23D40 11FFB60 120448C 11B2EC8 11B3FA8 1F16C28 1F0D
6A0
Apr 14 2016 15:45:01.144 GMT: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking Gigab
itEthernet0/6 on VLAN0103. Port consistency restored.
Apr 14 2016 15:46:11.362 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f027.e170 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:11.563 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f029.0594 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:32.005 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f029.0594 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:32.206 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f027.e170 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:35.167 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host a0ec.f9bb.7e7f in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:35.469 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host f8bc.12a2.bb38 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:37.793 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f027.e170 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:38.003 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f029.0594 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:39.454 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host f8bc.12a2.bb38 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:54.007 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f029.0594 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:54.074 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 40a8.f027.e170 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:46:55.458 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host f8bc.12a2.bb38 in v
lan 105 is flapping between port Gi0/2 and port Gi0/23
Apr 14 2016 15:47:55.308 GMT: %SW_MATM-4-MACFLAP_NOTIF: Host 0050.568d.5b77 in v
lan 103 is flapping between port Gi0/2 and port Gi0/23

I want to know what is the possible causes of link flapping in this case?

BR

AbdulKarim

Satwant Singh · ‎04-24-2016

Its a problem with your Spanning tree. Please post the configuration here.

abdulkarim041 · ‎04-25-2016

Thanks Satwant

Below is the running connfigurations of the switch:

sh run
Building configuration...

Current configuration : 8692 bytes
!
! Last configuration change at 07:59:41 GMT Thu Dec 3 2015
! NVRAM config last updated at 07:59:41 GMT Thu Dec 3 2015
!
version 12.2
no service pad

!
hostname
!
boot-start-marker
boot-end-marker
!
enable password
!
username
username
!
--More-- no aaa new-model
clock timezone GMT 3
system mtu routing 1500
!
!
ip domain-name
vtp mode transparent
!
!
spanning-tree mode pvst
spanning-tree portfast bpdufilter default
spanning-tree extend system-id
auto qos srnd4
!
!
!
no errdisable detect cause small-frame
no errdisable detect cause loopback
no errdisable detect cause gbic-invalid
no errdisable detect cause sfp-config-mismatch
no errdisable detect cause pagp-flap
no errdisable detect cause dtp-flap
no errdisable detect cause link-flap
no errdisable detect cause l2ptguard
no errdisable detect cause pppoe-ia-rate-limit
no errdisable detect cause dhcp-rate-limit
no errdisable detect cause arp-inspection
errdisable recovery cause udld
errdisable recovery cause bpduguard
errdisable recovery cause security-violation
errdisable recovery cause channel-misconfig (STP)
errdisable recovery cause pagp-flap
errdisable recovery cause dtp-flap
errdisable recovery cause link-flap
errdisable recovery cause sfp-config-mismatch
errdisable recovery cause gbic-invalid
errdisable recovery cause l2ptguard
errdisable recovery cause psecure-violation
errdisable recovery cause port-mode-failure
errdisable recovery cause dhcp-rate-limit
errdisable recovery cause pppoe-ia-rate-limit
errdisable recovery cause mac-limit
errdisable recovery cause vmps
errdisable recovery cause storm-control
errdisable recovery cause inline-power
errdisable recovery cause arp-inspection
errdisable recovery cause loopback
errdisable recovery cause small-frame
!
vlan internal allocation policy ascending
!
vlan 101
name LEVEL-1-2-NETWORK
!
vlan 103
name LEVEL-3-NETWORK
!
vlan 105
name SWITCH-MGMT
!
vlan 113
name LEVEL-1-2-NETWORK-13
!
vlan 131
!
vlan 213
name LEVEL-1-2-NETWORK-23
!
ip ssh version 2
lldp run
!
!
!
interface FastEthernet0
no ip address
shutdown
!
interface GigabitEthernet0/1
description Connected_To_Radio-Unit-01
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk
!
interface GigabitEthernet0/2
description Connected_To_Radio-Unit-02
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk
!
interface GigabitEthernet0/3
description Connected_To_Radio-Unit-03
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk
!
interface GigabitEthernet0/4
description Connected_To_Radio-Unit-04
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk
!
interface GigabitEthernet0/5
description Connected_To_Radio-Unit-05
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk
!
interface GigabitEthernet0/6
description Connected_To_Radio-Unit-06
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk
!
interface GigabitEthernet0/7
description Connected_To_Radio-Unit-07
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk
!
interface GigabitEthernet0/8
description Connected_To_Radio-Unit-08
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk
!
interface GigabitEthernet0/9
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/10
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/11
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/12
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/13
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/14
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/15
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/16
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/17
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/18
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/19
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/20
switchport access vlan 113
switchport mode access
shutdown
!
interface GigabitEthernet0/21
switchport access vlan 105
switchport mode access
!
interface GigabitEthernet0/22
switchport access vlan 213
switchport mode access
!
interface GigabitEthernet0/23
description Connection-to-PABX
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,131,213
switchport mode trunk
!
interface GigabitEthernet0/24
description Connection-to-FSP
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,131,213
switchport mode trunk
bandwidth 100000
duplex full
!
interface GigabitEthernet1/1
bandwidth 100000
!
interface GigabitEthernet1/2
bandwidth 100000
!
interface GigabitEthernet1/3
description Connection-To-L2_Switch_31-JXU-0126
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,107,113,131,213
switchport mode trunk
bandwidth 100000
!
interface GigabitEthernet1/4
description Connection-To-L2_Switch_31-JXU-0126
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,107,113,131,213
switchport mode trunk
bandwidth 100000
!
interface TenGigabitEthernet1/1
!
interface TenGigabitEthernet1/2
!
interface Vlan1
no ip address
shutdown
!
interface Vlan105
ip address X.X.X.X 255.255.0.0
!
ip classless
!
ip http server
ip http secure-server
!
!
snmp-server community public RO
snmp-server trap-source Vlan105
snmp-server source-interface informs Vlan105
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps config-copy
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps syslog
snmp-server enable traps envmon fan shutdown supply temperature
snmp-server enable traps mac-notification change move threshold
snmp-server host x.x.x.x version 2c public
snmp-server host x.x.x.x version 2c public
!
!
line con 0
line vty 0 4
password
login
transport input all
line vty 5 15
password admin123
login
transport input all
!
ntp clock-period 36026956
ntp source Vlan105
ntp server x.x.x.x
ntp server x.x.x.x prefer
end

Ports G0/23 and G0/24 have been connected with CORE switches. CORE switch connected with port g0/24 is secondary core and with port g0/23 primary root bridge. 

BR

AbdulKarim

pwwiddicombe · ‎04-25-2016

It seems like your wireless equipment (the one in question) is passing frames received back to the 3560 switch, which it shouldn't be doing. Is there only one port connected on each of the radio units?

Anything unusual about the cabling - particularly on port Gi 0/2? (i.e. in a ceiling and somebody's accidentally worked on punchdowns)?

Could that AP be bouncing or have a flaky connection; or be too far from the switch? Is it easy to change its cable?

Carlos Villagran · ‎04-25-2016

Hi!

This is being generated because STP instance is receiving a BPDU with a PVID different that it should be receiving, for example vlan 3 receiving for some software failure a BPDU with a VLAN ID of 5.

If this just happened once this can be because of certain hardware behavior under certain conditions and should be disregarded, however if this condition persist I would suggest an IOS upgrade.

Hope it helps, best regards!

JC

abdulkarim041 · ‎04-25-2016

Hi,

Two ports of g0/2 and g0/6 have been connected with wireless equipment. We are facing the issue from said ports. Other ports are working fine.

BR

AbdulKarim

Carlos Villagran · ‎04-25-2016

Hi!

Is there a way wireless users could be roaming?

Best regards!

JC

abdulkarim041 · ‎04-25-2016

Hi,

Actually we are using the Red-Lines Wireless as medium between Cisco and MOXA switches. You can say Cisco and MOXA have been connected through Read-Lines. MOXA EDS 510 we are using.

Someone is say MOXA EDS 510 has no support of PVST. And at Cisco we are using only PVST on Cisco side.

BR

AbdulKarim

pwwiddicombe · ‎04-26-2016

I'm really not sure about the MOXA side of the network, and what it's effect on the Cisco spanning tree. It looks like their spanning tree is simply LINK based rather than VLAN, and imply that the use of 802.1q links on the moxa side be done "universally" to avoid unintentional blocking and forwarding.

Do you have event logging on the moxa side, and are there "error events" on that side that periodically cause STP events over there? The fact that you have effectively 2 networks with different flavors of spanning tree running with multiple touch points between the networks, isn't a good thing.

Do you have technical support for the MOXA network; and have they recommendations for having failover links to a modern Cisco network? The other option might be to have any links between the networks being L3 rather than L2; but that may involve more devices on the network.

Carlos Villagran · ‎04-26-2016

The issue is definitely because of the MOXAs not having support for PVST. A L3 link could be a workaround but other problems could arise like design problems for example.

Regards!

JC

abdulkarim041 · ‎04-27-2016

Hi,

Issue has been resolved by configuring MSTP

Thanks for all your support

BR

pwwiddicombe · ‎04-25-2016

Is the wireless equipment properly setup as dot1q trunk as well, to match the cisco switch ports? I notice here the native vlan isn't specified.

interface GigabitEthernet0/2
description Connected_To_Radio-Unit-02
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101,103,105,113,213
switchport mode trunk

What you are seeing is frames that are coming back from this port, that should be originating from elsewhere in your network (other ports, or uplink to the core). If the only thing attached to gi0/2 is the wireless access point, it either has a faulty software on it, or has an "unusual" configuration. If you happen to have a hub or other connection, it may have an unintentional connection somewhere between switch and AP. Ports should NOT be sending back traffic they have already seen (unless somehow the AP is getting network traffic via wireless/another AP and re-injecting it on the wired side, but I'd never seen this before).