Bridge LAN extension - Repeater not forwarding ICMP

Martinni
Conversationalist

Bridge LAN extension - Repeater not forwarding ICMP

Hi everyone,

 

after solving issue with wrong VLAN configuration I have another one which I need help.

This is my topology for the bridge connection:

Martinni_1-1696869917807.png

Issue:

1. Trying to ping Interface VLAN 840 from Core to 3560, no response.....

Martinni_0-1696875458052.png

2. Then trying to ping DG 840 from 3560 to core, ping success.

Martinni_3-1696873753488.png

3. After this successful ping I can do the ping in step 1. for about 30 seconds

Martinni_4-1696873858524.png

4. Lose the connectivity from core to 3560 VLAN interface again.....

 

If I SSH to device when its ping-able It will just cut me after those ~30 seconds

 

Any ideas what might be an issue?

Before all steps I make sure:

1. I have IP+MAC in ARP table on Core

2. ALL MAC in mac tables(all match)

3. Repeater has ARP entry of the SVI 840 on 3560

 

Any guidance or help appreciated. 

 

 

10 Replies 10
alemabrahao
Kind of a big deal
Kind of a big deal

Do you have any ALCs configured that could be blocking ICMP?
 
Remember that the mesh is not 100% stable depending on the obstacles and distance between the APs, so I would evaluate the stability of this mesh as well. Analyze packet loss for example.
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

It's also worth taking a look at the Wireless Spectrum tab and seeing what's listed in the list of interfering APs, particularly any APs shown as being one channel up or down (memory says you're on 6, so anything on 5 or 7) would cause a really noticeable hit
 
Also, the minimum allowable bitrate you defined as 802.1b is not so much legacy as it is historical.
 
A channel difference of one and 802.11b combined can create some really unpleasant Wi-Fi situations.
 
It's also worth taking a look at the spectrum view to see if anything in the area is obliterating the 2.4GHz frequencies and this is quite noticeable in the 'waterfall' graph.
 
It's just an exemple ok?
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

Hi, If there would be such ACL it would block the ICMP all the time right? And ICMP works in specific situation. From 3560 all the time. And no I am not aware of such ACL.

Okay, try to think outside the box a little and think about the other possibilities I raised. 😊

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Ryan_Miles
Meraki Employee
Meraki Employee

The SSID tags VLAN 840, but the switch has 840 untagged?

If it was a VLAN payment problem, this wouldn't even work, wouldn't you agree?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
PhilipDAth
Kind of a big deal
Kind of a big deal

Can the MR86s ping the 3560 and the core reliably?

Gateway MR86:

to Core 

Martinni_0-1696880785554.png

to 3560 - no connectivity

 

Repeater MR86:

to Core

Martinni_1-1696881087970.png

to 3560 - no connectivity

 

Both WAPs can reach core but none can reach 3560, after 3560 ping Gateway AP can ping but repeater no.

PhilipDAth
Kind of a big deal
Kind of a big deal

Could you double-check the subnet mask on the 3560 please.

Hi subnet mask matches on core and also on 3560 . /24

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels