Several times a day - 'Disabled Gateway' for 15-45 seconds

alceryes1
Here to help

Several times a day - 'Disabled Gateway' for 15-45 seconds

(see below) Not sure if I can post links. I am having an issue with my MX67W where I am regularly seeing 'Disabled Gateway' in the historical data. The internet goes down during these occurances (which happen for less than a minute) and just recently the device went offline, into a funk and required a reboot to come back online (this is what Meraki support said probably happened).

Verizon says their light looks clean all the way to the ONT. They are saying it's not an issue on their end. Any idea what/why this is happening? TIA!

 

Edit - The text is Disabled Gateway (bad connectivity). Could this be as simple as a bad network cable?

 

https://imgur.com/a/4DrYxdp

 

 

9 Replies 9
alemabrahao
Kind of a big deal

This can happen for a variety of reasons, such as a DNS issue, an IP configuration issue, or even a hardware issue.

Is the IP configured statically or via DHCP? Are you using an internal or external DNS? And lastly, have you opened a support case?

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.
alceryes1
Here to help

Static IP and Verizon says that it's not them.
I am using OpenDNS. Maybe I'll switch to the ISPs preferred to test. Will also swap out the cable to the ONT - just in case. I opened a support case. Meraki support was leaning towards ISP issue, but not sure.

 

PhilipDAth
Kind of a big deal
Kind of a big deal

This is not a common issue for an MX.  Is the MX running a current stable or better firmware?

 

You could try opening a support case and see if Meraki can see anything going wrong in the backend.

 

You could try replacing the patch cord connecting the MX to Verizon (clutching at straws here).

 

Is there any chance the ONT could have experienced a power failure?

alceryes1
Here to help

Verizon says the ONT has been up for the last 4 days.

I did open a Meraki ticket. Support is leaning towards it being a Verizon issue. Verizon, of course, says it's not them. Firmware is on latest stable. I don't do betas.

I will be replacing the network cable in about an hour.

IvanJukic
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Hi @alceryes1 ,

As @PhilipDAth mentioned. It is not a common alert. That alert is pointing towards the gateway of the MX. Most of the time in my experiance, it is ARP... ARP Poisoning, ARP Caching, Proxy ARP etc..

Have the ISP check from the ONT to the Layer 3 IP Gateway of the MX. After the Layer 1 side; (cabling and such) has beend checked.



Cheers,

Ivan Jukić,
Meraki APJC

If you found this post helpful, please give it kudos. If it solved your problem, click "accept as solution" so that others can benefit from it.
alceryes1
Here to help

Replaced the cable between Meraki and Verizon. Still seeing these Disabled Gateway (bad connectivity) alerts pop up randomly. Waiting to hear back from Meraki support.

 

Verizon says they don't see anything on their end, and that a service call will cost the client money if the tech doesn't find anything. Since we sometimes get 24 hours without the issue appearing, I know the tech will come out, spend 30 mins here, find no issue, and charge the client $140. I'm hesitent to do this, especially since I just got the client to upgrade from a residential router to this commercial-grade router. Any other suggestions are appreciated.

 

Could this be anything on the LAN side causing this?

Also, I am physically plugging the cable in between the Verizon ONT and Meraki. It's one foot away from the Meraki I am opening up the clamshell box, fishing the cable through the little hole, and connecting both ends. There's nothing in between the ONT and Meraki

 

 

alemabrahao
Kind of a big deal

Have you tried updating the firmware? Also try doing a packet capture.

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.
alceryes1
Here to help

Everything is up to date except the wireless (MR) portion, and that's a brand new firmware release.

 

Could this be potentially caused by something on the LAN side?

BrandonD
Meraki Employee
Meraki Employee

Hi @alceryes1,

 

I tend to agree with @alemabrahao that Packet Captures during the reported issues are the best way of determining the cause of the issues, based on the Error I'd be interested in the ARP traffic at the time of the outages. I'd tend to agree I do not believe the MR firmware should be playing a role in the MX connectivity issues. 

 

Another option I often recommend to customers in these scenarios would be to contact Verizon Support and inquire if they'd be willing to join a collaborative call for your case with Meraki Support. In this situation you can call into our main support line as our hold times are typically relatively low, and work collaboratively on the issue to ensure greatest chance at success for a resolution.

 

 

Thanks and hope this helps!

 

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.
Get notified when there are additional replies to this discussion.