Z3C (Disabled gateway bad connectivity)

SOLVED
NorwegianFrog
Here to help

Z3C (Disabled gateway bad connectivity)

NorwegianFrog_0-1632730700639.png

My company has recently set up over 150 units of Z3C's across the country, and in some destinations we get these messages 'Disabled gateway bad connectivity'. Now in the example above, it's a bit weird since the signal strength is good(3 out of 5 lines), and the speed in general is like 50down and 15up, so it's not in a bad location. 

 

So the question is, why is this happening in some locations, and others not? Is there a fix to this? The firmware of the Z3C's are MX16.8. 

1 ACCEPTED SOLUTION

Accepted Solutions
UCcert
Kind of a big deal

Re: Z3C (Disabled gateway bad connectivity)

hi @NorwegianFrog 

 

https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failo...

 

"The MX then begins performing the internet test. If either the ICMP or the HTTP test is successful, the internet test is marked as good for 300 seconds on that uplink. During this time, the MX continues running the internet test every 150 seconds. Each successful internet test (meaning either a successful ICMP test or a successful HTTP test) results in the internet being marked as good for another 300 seconds. If any test within the internet group fails, the MX decreases the testing interval to 20 seconds. If the tests continue to fail for a time period exceeding 300 seconds from the last successful test, the internet will be marked as failed on the uplink. Otherwise, any successful ICMP or HTTP test will mark the internet test as good for another 300 seconds. Once marked as good, the test is run every 150 seconds."

Darren O'Connor | uccert.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.

View solution in original post

5 REPLIES 5
UCcert
Kind of a big deal

Re: Z3C (Disabled gateway bad connectivity)

hi @NorwegianFrog 

 

This is explained within other posts:

 

https://community.meraki.com/t5/Security-SD-WAN/Meraki-showing-Bad-Gateway-no-internet-connectivity/...

 

 

https://community.meraki.com/t5/Security-SD-WAN/Teleworker-Z3-14-53-Bad-Gateway-Event-Log/m-p/94088#...

 

Darren O'Connor | uccert.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
ww
Kind of a big deal
Kind of a big deal

Re: Z3C (Disabled gateway bad connectivity)

Any logging in the event log on that times? For example change of lte channel?

 

You could try run latest 16.12

or 15.44 if you dont want beta

NorwegianFrog
Here to help

Re: Z3C (Disabled gateway bad connectivity)

I would assume it has something to do with the ISP then. 

 

I've noticed on some other locations where the Z3C will lose connectivity, but will pick it up after 1-5 minutes. Do you know how it works when they do lose connectivity? Is there a time limit on how long they're trying to reconnect?

 

 

NorwegianFrog
Here to help

Re: Z3C (Disabled gateway bad connectivity)

Well I get a lot of different ones, not sure which one are relevant.

Here are a few:

Route connection change - This is when I think it lost connectivity, around that time.

VPN registry connectivity change - During no connectivity

Primary uplink status change - When I think it got back. 

 

UCcert
Kind of a big deal

Re: Z3C (Disabled gateway bad connectivity)

hi @NorwegianFrog 

 

https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failo...

 

"The MX then begins performing the internet test. If either the ICMP or the HTTP test is successful, the internet test is marked as good for 300 seconds on that uplink. During this time, the MX continues running the internet test every 150 seconds. Each successful internet test (meaning either a successful ICMP test or a successful HTTP test) results in the internet being marked as good for another 300 seconds. If any test within the internet group fails, the MX decreases the testing interval to 20 seconds. If the tests continue to fail for a time period exceeding 300 seconds from the last successful test, the internet will be marked as failed on the uplink. Otherwise, any successful ICMP or HTTP test will mark the internet test as good for another 300 seconds. Once marked as good, the test is run every 150 seconds."

Darren O'Connor | uccert.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.

View solution in original post

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.