cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Poor Connectivity to Meraki Cloud

Highlighted
Here to help

Poor Connectivity to Meraki Cloud

Hi guys!

 

I've got one switch in my network that is repeatedly having trouble communicating with Meraki Cloud.  I had things working last night for about 6 hours, but then the trouble started again.  Traffic is passing OK, and I can see the Layer 2 switch behind this (troublesome) layer 3 switch. The layer 3 switch is constantly amber.

 

The switch is on the far-end of a Transit Network (leased layer 2 line from ISP).  When I take a packet capture from the near-end switch port of the transit network I get the following:

 

17:24:04.649233 IP 10.100.200.229.58811 > 52.84.235.30.80: Flags [S], seq 247871360, win 29200, options [mss 1460,sackOK,TS val 6177911 ecr 0,nop,wscale 7], length 0
17:24:04.667300 IP 52.84.235.30.80 > 10.100.200.229.58811: Flags [S.], seq 2507373319, ack 247871361, win 28960, options [mss 1460,sackOK,TS val 2705000754 ecr 6177811,nop,wscale 8], length 0
17:24:04.670938 IP 52.84.235.30.80 > 10.100.200.229.58811: Flags [S.], seq 2507373319, ack 247871361, win 28960, options [mss 1460,sackOK,TS val 2705000754 ecr 6177811,nop,wscale 8], length 0
17:24:05.443512 IP 10.100.200.229 > 8.8.8.8: ICMP echo request, id 11207, seq 61547, length 64
17:24:05.462298 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.463253 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.463434 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.463626 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.463802 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.464321 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.464502 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.465287 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.465475 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.465904 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.466200 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.466552 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.466727 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.467444 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.467627 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.467920 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.468108 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.468657 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.468835 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.469376 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.469553 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.470083 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.470272 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.470832 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.471160 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.471555 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.471742 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.472384 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.472567 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.473044 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.473234 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.473841 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.474117 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.474620 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.474803 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.475308 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.475498 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.476162 IP 8.8.8.8 > 10.100.200.229: ICMP echo reply, id 11207, seq 61547, length 64
17:24:05.674419 IP 52.84.235.30.80 > 10.100.200.229.58811: Flags [S.], seq 2507373319, ack 247871361, win 28960, options [mss 1460,sackOK,TS val 2705000854 ecr 6177811,nop,wscale 8], length 0
17:24:05.675155 IP 52.84.235.30.80 > 10.100.200.229.58811: Flags [S.], seq 2507373319, ack 247871361, win 28960, options [mss 1460,sackOK,TS val 2705000854 ecr 6177811,nop,wscale 8], length 0

 

It looks like the ICMP request is sent, but the reply repeats.  Last night when I left (thinking everything was working) I was getting a 1:1 ratio of request/reply.

 

Any hints?

6 REPLIES 6
Highlighted
Kind of a big deal

Re: Poor Connectivity to Meraki Cloud

I'd contact the service provider.  You might have a faulty circuit.

Highlighted
Kind of a big deal

Re: Poor Connectivity to Meraki Cloud

Looks like a loop maybe, is everything else on that connection behvaing as expected?

Meraki CMNO, Ruckus WISE, Sonicwall CSSA, Allied Telesis CASE & CAI
Highlighted
Here to help

Re: Poor Connectivity to Meraki Cloud

Yes, everything else is behaving as expected.  I have a layer 2 switch 'behind' my layer 3 and it is communicating with dashboard fine.  All end-user devices are behaving fine.

 

I opened a support case and so far the engineers are stumped as well.

Highlighted
Kind of a big deal

Re: Poor Connectivity to Meraki Cloud

Perhaps try changing the layer 2 switch management IP address in case their is an IP address conflict or something.

Highlighted
Here to help

Re: Poor Connectivity to Meraki Cloud

I gave that a try. No luck. The address of the layer 2 switch changed OK, but everything else is still the same.
Highlighted
Meraki Employee

Re: Poor Connectivity to Meraki Cloud

Hi,

 

Make sure that default gateway of switch's management IP is not defined as SVI of management VLAN on itself.

 

Cheers,

Gaurav

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.