Meraki

CharlieCrackle · ‎May 19 2021

Just an update for you all. it has taken along time for support to get back to me. Switches boot with an IP address 1.1.1.1 it then changes to the static address or the DHCP address. Support can not tell me why they use 1.1.1.1 (some one else IP address) or how the switch could ever use this address to get to the cloud. If you are upgrading 3 switches at a time then they will all reboot and at the same time there will be 3 devices with 1.1.1.1 causing the MX to error with duplicate IP. If some one from engineering could explain what the rational is it would be great.

CharlieCrackle · ‎Mar 21 2021

Yes issue seen on 120s and 125s and switches on DHCP and default VLAN 1

CharlieCrackle · ‎Mar 20 2021

No all set to DHCP

CharlieCrackle · ‎Mar 18 2021

I just upgraded my office switches to 14.16 and got a duplicate IP 1.1.1.1 alert when doing it. do the switches boot with address of 1.1.1.1 ??? something wierd is going on here. anyone else getting 1.1.1.1 duplicate ip alerts ??

CharlieCrackle · ‎Mar 16 2021

Doing a wire shark capture using the MAC address of the switch you can see it making DHCP requests on native vlan and other vlan and getting responses !

CharlieCrackle · ‎Mar 16 2021

the MX is set to use Cisco umbrella DNS. but the arp ing shows 1.1.1.1 (mac of switch) trying to arp for the address of 8.8.8.8. Had this happen to another single switch site now. this site the switch is still working but not connected to cloud it was interesting as a power cycle did not fix the issue but the users were not effected and switch was still passing traffic 8-12 hours later the switch started talking to cloud its self with the last error being "Disabled Switch Bad DNS" I am wondering if this is a MX DHCP issue as all these issue started when the MXs were upgraded to 15.42 from 14 to fix the "Unable to download configuration error" which was happening more frequently.

CharlieCrackle · ‎Mar 16 2021

no both switches are set to DHCP. it has been 9 hours now and they are still doing this. what is wierd is all the cameras and AP that are connected to the switch are showing as not connected to cloud also but are working ok. and the users on the switch are still working ok. I don't get it at all and at this point support don't either. Some one is going to site to power cycle the switches.

CharlieCrackle · ‎Mar 16 2021

I upgraded a network with 2 x MS120 switches to 12.28 (stable) and then lost the switches and connection to cloud. Just before having to drive 80km to power cycle them the MX started complaining about Duplicate IP 1.1.1.1 and the two mac addresses were the switches. Why does the meraki use a public ip of 1.1.1.1 ? Why do the switches boot with this ip ? (I have them set for DHCP) I did a wireshark capture and both switches are arping 8.8.8.8 and getting no where..... can some one explain what is going on here makes no sence.. wireshark

CharlieCrackle · ‎Oct 2 2020

Just and update for any other that get this issue Meraki RMA unit. after looking that this logs this was the reply from support. "it had an issue where it was not able to keep its configuration properly. Due to that, it also could not keep the firmware that it tried to download from the cloud and properly install. It became a loop where it needed the configuration to fix the issue to keep its firmware. As you could see, it visually reflected that as it kept going from red to rainbow to white and back to red. Usually we would help it get online by pushing that configuration and then applying the fix. It did not hold it well even after that so it is fine that we RMA'd this device. "

CharlieCrackle · ‎Sep 23 2020

Thanks for the info at least I know others are using with out issue. may be is it something in my config. not that my config is anything special other than a lot of DHCP scopes and insight.

CharlieCrackle · ‎Sep 23 2020

I have had a bad day today. I had MX64 with FW15.34 Insight was not working (not uploading data) Case 05530983 I was told that the next firmware update would fix this. MX 15.36 was released I upgraded unit went into an end less reboot loop. Red light…. Then rainbow lights then solid white then flashing white. And then reboots back to red If I disconnect all cables and reboot and ONLY plug in the LAN cable I get the normal Meraki local status page with internet problem (rainbow lights) If I then plug in the internet the light goes solid white and I get the Green tick connected to meraki on local status page The light then goes flashing white.. ( 2-3 min) and then reboots and goes red. I tried to get a diag log from the device when connected to cloud but the unit reboots before it completes. I rebooted the device with no internet and can connect via the LAN but the device still reboots even with no internet and I am unable to get it to download local support data before a reboot. I rang support and they could see it connecting but did not know what was happening and RMA the unit CASE 05593909. Network was down (and MX is the DHCP server) BUT I was prepared I had another MX64. I removed the old MX from the network and and cold swapped and the new unit connected to the cloud (it was running MX15.34) I then got the error "Unable to fetch configuration" contact support {I have been getting this alot lately with various customers, very annoying} Support worked their magic CASE 05594042 and fixed this connection issue. The unit then connected to the cloud loaded config and then started working. This was short lived as this unit then went into the reboot loop after about 10 minutes of working. I went into the console and rolled back the firmware to MX15.34 this did not help still stuck in the reboot loop support could see the device connecting to the cloud and then it started to do a download. they even blocked the download but still it did the download. I factory reset both units and still they connected to the cloud again with the "Unable to fetch configuration" contact support support then fixed this again and again they both went back into the reboot firmware down loop Support tried to force a stable 14 version download but this did not work either just kept rebooting. I have the RMA device coming tomorrow but I am scared this unit is just going to have the same issue (it might not now as the firmware has been downgraded finger crossed) It was a real pain as the network was down most of the day until I configured and OLD Cisco ASA to replace the meraki. Any way this is the reason I usually test firmware on my network before loading on customer network but this got me worried. I have so many customers on meraki now if something like this happened to them I would not be very popular !! Does any one have any idea what is going on here ????

CharlieCrackle · ‎Aug 17 2020

Update.. it has taken a while bit this issue has been fixed in MX 15.34

CharlieCrackle · ‎May 23 2020

I have to agree with you, being in the Cisco IT industry for the past 30+ years Cisco TAC has certainly degraded in the last 24 months. In the good old days Cisco TAC was the GOLD standard for support. Nothing was too much trouble it was all about getting your issue fixed ASAP. These days Cisco is a machine I call it the "Cisco System" if your issue falls out of what the system supports you are in big trouble and you can waist hours and hours of unchangeable time making your issue fit the system. Cisco has lost the human/common sense element due to digitization of everything. The joke line "The computer says NO" is becoming more prevalent.

CharlieCrackle · ‎May 23 2020

The issue is it may be effecting other people and they do not even realize it. Anyone who has a WLAN controller on the network that is proxying the DHCP will be effected. It is just luck that most devices it seems when the DHCP renew fails (after 3 seconds) then go back to the broadcast for a new ip address technique. Most people would never know the renewal failed and the time that took as the device continues to work fine while this failure happens in the back ground.

CharlieCrackle · ‎May 23 2020

I have tested up to 15.29 and the stable release of 14.x I do not know other devices are effected as I do not have access to any others in this config. if the devices share code they may be.

CharlieCrackle · ‎May 23 2020

I have tested up to 15.29 and issue still exists.

CharlieCrackle · ‎May 22 2020

I reported this bug on 10 Feb 2020 Case 04855962 it took a lot of wasted and un-chargable time to get this through the Meraki Support firewall with support insisting the MX64 was just following the RFC. Eventually after 7 hours of my own lab work they agreed with me and sent to development. Meraki even closed the case and re-open a new one 04955618 which no one can explain to me (was this the keep the KPI's looking good ? Months and months later still getting nowhere and I am sure there are other having this issue to and do not even know it due to the client fall back doing a new broadcast after getting no renewal response from MX64 I have written up a very detailed explanation on my blog for others to understand. https://blog.cie.net.au/2020/05/dhcp-relay-issue-meraki-mx64.html If other could please open cases if you suffer from this issue so meraki can get this fixed. I did expect meraki to fix such a fundamental issue with DHCP quickly and other models may be effected to. I have ONLY tested the MX64.

CharlieCrackle · ‎Apr 1 2020

An update for all After support looked at the local debug file they discovered it was connecting to a different server "For some unknown reason" they logged on to that different server and rebooted it from there and now it is working... 🙂

CharlieCrackle · ‎Mar 31 2020

I am running out of solution for customers now. Telstra is Australia is using IPV6 on their mobile network with a IP6 to IP4 GW which does not support l2tp VPN Up till now I have been disabling IPV6 on the client to get around this I now have IOS devices with the same issue and you can NOT disable IPV6 on IOS. so VPN on IOS does not work any more. Need IPV6 support or anyconnect VPN client support.. URGENTLY as now supplying non meraki gear to fix these issues.

CharlieCrackle · ‎Mar 27 2020

It says connected.... little bit that connected today Interesting how the bit before the the green is NOT red any more.. I logged case and they are looking at it.

CharlieCrackle · ‎Mar 26 2020

Because of COVID-19 there is a LOCK DOWN at the data centre so I can not get rebooted. But today the device came on line for 15 minutes. and then stopped.. How would this be possible ? The device is still working and the SDWAN is working (how are the SDWAN updates working ?)

CharlieCrackle · ‎Mar 25 2020

Thanks I have added a wish for a reboot button the local config page.

CharlieCrackle · ‎Mar 24 2020

Meraki support are saying they can not connect. Why would this happen and only to a couple of devices ?? how can meraki not allow this to happen again during a dashboard upgrade ? Charles

CharlieCrackle · ‎Mar 24 2020

The device has full internet access It has just lost the Meraki cloud connection tunnel connection between device and meraki cloud. When I connect the the local web interface it says it is connected to the meraki cloud when I go to the dashboard it says device has not connected for 5 days the SDWAN is working so it mush be registering the VPN ip addresses ok I do not want to reboot and find it does not work at $100 per 15 min. how log will the device keep working with no cloud connection is there a license issue eventually ?

CharlieCrackle · ‎Mar 24 2020

With the updates to the Meraki cloud dash board last week. I have had a couple of MX loose connection to the cloud. the MX is still working and all the SDWAN is still working. The Meraki dashboard says lost connection to the device. Logged a support case and was told I just need to reboot the MX and all will be ok as issue with keys to cloud connection. This is fine for one and a reboot fixed this. The other one is at a data-centre and it will cost me $100 to get remote hands to go to rack and pull the power and plug back in. Why should customer have to pay $100 because of a meraki dashboard upgrade ?? Is there some other way to reboot the device. I got the data-center to SHUT and NO SHUT the port that connects to the internet in case the resetting of the network port would fix it. It did not and the device is still working but has no connection to cloud. I have local access to the meraki web page (config page) can not see any reboot option here.. Does meraki have a back door ssh to reset the device ?? is there some way to reboot this device remotely with no cloud access ?

About CharlieCrackle

CharlieCrackle

Charles Clare

Community Record

Badges