Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About fxroche3
fxroche3
Just browsing
Member since Apr 1, 2019
Apr 4 2019
Community Record
7
Posts
0
Kudos
0
Solutions
Badges
Apr 2 2019
5:56 AM
When this happened the first time Meraki Support said it looked like the firmware upgrade was not completing and therefore was attempting to redownload and install every couple of hours. Now I already dealt with Palo Alto and confirmed the firewall was not blocking any communications. So the only other difference between our corporate setup vs home setup is the Meraki is handed DHCP at home and using the cable providers DNS. Here we hard set the IP and use Google DNS, but again these are the same configurations in place today so why is it working now???
... View more
Apr 2 2019
5:52 AM
Just double checking my switch logs and there are link changes. Here is the most recent what I can only assume is a reboot. Dashboard shows offline from 6:42a-6:57a Apr 2 06:44:36.429 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to down Apr 2 06:44:37.428 est: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to down Apr 2 06:44:40.389 est: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up Apr 2 06:44:42.388 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to up Apr 2 06:45:26.984 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to down Apr 2 06:45:27.984 est: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to down Apr 2 06:45:31.067 est: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up Apr 2 06:45:33.066 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to up Apr 2 06:55:57.825 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to down Apr 2 06:55:58.828 est: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to down Apr 2 06:56:01.869 est: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up Apr 2 06:56:03.868 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to up Apr 2 06:56:37.269 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to down Apr 2 06:56:38.268 est: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to down Apr 2 06:56:41.187 est: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up Apr 2 06:56:43.190 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23, changed state to up
... View more
Apr 1 2019
3:16 PM
All versions to the current v13 to beta v14 and 15. Not a firmware problem, happens with all versions. Also it's worth mentioning that we didn't change one piece of any configuration after we brought it back from home.
... View more
Apr 1 2019
3:14 PM
Nope and when we brought it back into the office it stayed connected and hasn't rebooted or gone offline since so something out its trying to do every couple of hours that for some reason is causing this issue.
... View more
Apr 1 2019
3:10 PM
It has a private IP. Its 100% not a MX or network or firewall configuration issue.
... View more
Apr 1 2019
2:33 PM
So the MX sits in its own DMZ and becomes unreachable for approx.10 mins every couple of hours. It's unreachable from inside the LAN and directly from the DMZ switch (interface goes down). On the FW there is also no traffic being logged so it definitely goes offline whether it's a reboot or not there is a link change on the switch interface.
... View more
Apr 1 2019
1:40 PM
Have an issue with MX67s rebooting like clock work every couple of hours, causing 10-12 minutes of downtime. Site 1 - Multiple factory resets, upgrades/downgrades, even did a RMA and still had the same issue. Was told to bring it home and wire it up to my home network. Did that, brought it back to work and it no longer reboots. Not the ideal fix though. Site 2 - Experiencing the same problem as Site 1, but don't have the luxury of bringing this one home since I'm 1000 miles away. Meraki wants to do another RMA, but its going to be a waste of time. I have this plus 3 more remote sites I need to deploy, not to mention before Site 1 I did a deployment without a single problem. In all cases every site is using Palo Alto Firewalls and the rules for the MX are wide open and I validated that the Palo's aren't blocking or treating any of the traffic flows as Threats. In the case of Site 1 we even wired up the MX to our Internet Switch (no FW) and it still continued to reboot. Anyone have any suggestions? Meraki Support is basically a dead end.
... View more
© 2024 Cisco Systems, Inc.
