2960xr + Meraki MR18 port flapping - Page 2

the-lebowski · ‎11-07-2018

I have a remote office and I have seen this problem constantly but I can't pin down why. We have a single AP connected to an 2960xr running 15.0(2)EX5 in a remote office in a country without the best wiring practices. However this problem seems to be specific to whatever port is connected to the AP which has already been replaced. The only thing I notice is that is auto negotiating to 100Mbps but not sure that would cause the port to constantly flap. Its an MR18 which is 10/100/1000 and when I hard code the port the AP doesn't come up so I just assume their is a dumb switch on the other end.

2960-3rdworld#show int gi1/0/47
GigabitEthernet1/0/47 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 8890.8dda.6eaf (bia 8890.8dda.6eaf)
Description: ###access to ap-meraki18###
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
3317664 packets input, 704875181 bytes, 0 no buffer
Received 322826 broadcasts (197335 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 197335 multicast, 0 pause input
0 input packets with dribble condition detected
6176535 packets output, 2229684212 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
104351 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out


2960-3rdworld#sho controllers e gi1/0/47

Transmit GigabitEthernet1/0/47 Receive
2229683065 Bytes 704874416 Bytes
3877481 Unicast frames 2994835 Unicast frames
2291990 Multicast frames 197333 Multicast frames
7050 Broadcast frames 125491 Broadcast frames
0 Too old frames 672434342 Unicast bytes
0 Deferred frames 22440476 Multicast bytes
0 MTU exceeded frames 9999598 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 683532 Minimum size frames
0 8 collision frames 1174545 65 to 127 byte frames
0 9 collision frames 967691 128 to 255 byte frames
0 10 collision frames 213871 256 to 511 byte frames
0 11 collision frames 80934 512 to 1023 byte frames
0 12 collision frames 197086 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 0 Symbol error frames
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
2253782 64 byte frames 0 Valid frames, too small
1342884 127 byte frames
1088508 255 byte frames 0 Too old frames
275386 511 byte frames 0 Valid oversize frames
129972 1023 byte frames 0 System FCS error frames
1085989 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames


Nov 7 12:41:31.876 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov 7 12:41:48.630 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
Nov 7 12:41:49.633 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov 7 12:44:56.249 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
Nov 7 12:44:57.249 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov 7 12:45:14.244 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
Nov 7 12:45:15.243 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov 7 16:02:53.214 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
Nov 7 16:02:54.217 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov 7 16:03:11.012 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
Nov 7 16:03:12.012 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov 7 16:12:48.670 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
Nov 7 16:12:49.687 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov 7 16:13:06.430 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
Nov 7 16:13:07.430 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov 7 16:14:59.395 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
Nov 7 16:15:00.395 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov 7 16:15:17.312 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
Nov 7 16:15:18.316 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov 7 16:54:57.380 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down

paul driver · ‎11-08-2018

Hello

@the-lebowski wrote:

Nah just access port on the cisco side and nothing on the Meraki side (no vlan tagging). I just removed the spanning-tree portfast command but not sure that would cause what I have been seeing?

If you have no vlan tagging why is the ap in vlan 10?, is this your native vlan? - I would expect the switch port attaching the meraki AP would be a trunk.

Can you explain a little how this network is setup or maybe provide a little topology

Lastly - what have you done regards cabling /port relocation /LLDP etc...

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

the-lebowski · ‎11-08-2018

When I said no VLAN tagging I meant other than what VLAN that AP and the SSID are on. Like I posted before its an access port in VLAN 10, AP has an IP on VLAN 10 and the clients get IPs on VLAN 10. I already pasted a copy of the port connected to this AP showing 'switchport access vlan 10'...pretty basic if you ask me.

This 2960 is doing layer3, handful of SVIs and 10.19.10.1 (VLAN 10) is one of them.

I disabled CDP and enabled LLDP made 0 difference. No cable changes because like I said I got little to no help from the local office over there. At this point I can only do things remotely.

I also noticed the port isn't really going down because it never grants POE again, it just flaps but not like when I shut it down manually and it actually grants power:

Nov  8 18:29:18.289 GST: %ILPOWER-7-DETECT: Interface Gi1/0/47: Power Device detected: IEEE PD
Nov  8 18:29:19.474 GST: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/47: Power granted

Whereas I just see this constantly in the logs:

ov  8 14:11:49.987 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov  8 14:28:44.583 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
Nov  8 14:28:45.586 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov  8 14:29:02.423 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
Nov  8 14:29:03.423 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov  8 14:55:27.225 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
Nov  8 14:55:28.228 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov  8 14:55:45.104 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
Nov  8 14:55:46.104 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov  8 15:04:07.014 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
Nov  8 15:04:08.013 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov  8 15:04:24.728 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up
Nov  8 15:04:25.728 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to up
Nov  8 18:08:53.695 GST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/47, changed state to down
Nov  8 18:08:54.695 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to down
Nov  8 18:09:11.455 GST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/47, changed state to up

the-lebowski · ‎11-08-2018

I think I may have found the problem, seemed someone using Ruckus APs had the same issue. Bug in the version of code I am running: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCus35889/?referring_site=bugquickviewclick

2960-3rdworld(config)#int gi1/0/47
2960-3rdworld(config-if)#no power
2960-3rdworld(config-if)#no power eff
2960-3rdworld(config-if)#no power efficient-ethernet