Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- About JonP
JonP
Getting noticed
Member since Mar 8, 2022
2 weeks ago
Community Record
36
Posts
17
Kudos
0
Solutions
Badges
3 weeks ago
Hi there, The TLDR version is: We didn't. It remains a problem. The slightly longer explanation is as follows: It turned out that it wasn't just WAN interface drops - the whole appliance was rebooting. The problem seemed to self-resolve once support got involved. For months we'd had these random drops, but support blamed the ISP. It wasn't until we put a switch between the MX and our ISP demarc/router and could prove the MX interface was dropping that support really took any notice. Once that was proved conclusively they started looking into it some more, and the conclusion they came to was that we were overloading the appliance with too many WAN users at once. We were forced to upgrade to an appliance which could handle more users, which we are very unimpressed about. We regularly have between 250-300 active devices at once and support's view was that the 75 was not designed to handle over 200. They wouldn't look into the matter further. I won't throw any individual agent under the bus, but here's what they said: Performance from the last day on this device is still receiving a few performance spikes up to 100 percent CPU Usage, However at about average this device seems to be under about 75 percent on average, however this again could be because this device is over spec'd above the documentation of 200 clients. Due to the recent panics of this device we will continue to monitor moving forward on this device to see if any further reboots occur. Please let me know if you have any further questions. We had an unexpected reboot again on 6th Jan and this is what support said this time: Thanks for calling Cisco Meraki Technical Support today. I investigated your WAN outage and consequent loss of LAN connectivity at around 11 am this morning. I examined back-end logs and can confirm that this was due to the MX unexpectedly rebooting. I am glad to hear that the recovery time for the network was under a minute. I have collected initial data regarding this and will be collecting further data with a view to raising an internal case to investigate the issue further. I will keep the case open and keep you informed of progress. Please let me know in the case comments if you experience this issue again. Thank you for being a valued Meraki customer. I've chased them today for an update - Support are notoriously bad at getting back to you. What they said on the phone was that they could see "an event which caused the device to reboot" but wouldn't be drawn on what that "event" was. So we await the installation of our new MX105 in an HA pair to hopefully solve this problem once and for all. And Meraki - if you're reading this, your support sucks. Do better.
... View more
05-23-2022
05:10 AM
Hello Community, Hope you're all doing well. Over the last few days our RH in the comms room has been creeping up to around 70%. We know this thanks to our MT10 we've placed in there. My question is - is this ok? At what point do I need to worry about RH? We've set thresholds but they're a little arbitrary at the moment!
... View more
04-14-2022
12:42 PM
1 Kudo
I will mention it to support again and have them check the CPU logs! Thanks!
... View more
04-14-2022
12:38 PM
1 Kudo
That's interesting as that was similar to my theory. I wondered if it was CPU usage. We have some port forwards enabled on 8001 and 8002 for CCTV access. We had/have a case open with support who have now replaced the MX and we put the new one in this week.
... View more
04-13-2022
01:43 AM
Have you set a trunk port for that VLAN so that it can escape the core? We have a VLAN which only exists on our core switches, and thus isn't tagged anywhere. Those devices in that VLAN can't get out of the switch to the gateway or beyond.
... View more
04-13-2022
01:40 AM
If you have a singe /23 subnet then as @PhilipDAth says, VLAN trunks wont make a jot of difference. You could split them into VLANs on separate subnets, and that would then mean you would, by necessity have to have some trunk ports in your switches, otherwise your VLANs won't be able to escape the switch.
... View more
04-12-2022
08:41 AM
1 Kudo
We have a similar setup. An MS Core, with two legs going to each of our access layer. The core has LACP links across the switches so in the event that one switch fails, the other can keep chugging. Can you describe your LACP setup switch by switch?
... View more
04-11-2022
07:40 AM
2 Kudos
Came here to say this! We had a mixed setup whilst we were waiting for our new MR's to come in. Air Marshal went wild until we figured out what it was and turned it off!
... View more
04-08-2022
05:43 AM
2 Kudos
Hi, It's connected to an HPE Aruba 2530, and I don't think EEE is enabled? HP-2530-48G(config)# sh savepower led LED Save Power Information Configuration Status : Disabled HP-2530-48G(config)# sh savepower port-low-pwr Port Save Power Information Configuration Status : Disabled HP-2530-48G(config)# sh energy-efficient-ethernet Port | EEE Config Current Status txWake(us) ----- + ---------- -------------- ---------- 1 | Disabled Inactive - 2 | Disabled Inactive -
... View more
04-08-2022
02:54 AM
Hello community, We've been having problems for a few months now, where randomly our primary internet connection will failover to the backup. After much investigation, troubleshooting, network redesign and even a replacement of the MX the problem persists. Prior to Wednesday, the internet would failover to WAN2 at random intervals, for a period of 1-2 seconds, and then switch back. This would have the effect of dropping every VoIP call in progress each time it fails over, and back again. The realtime utilisation graph in the Meraki dashboard is pretty much useless as by the time we get into it, the event has already gone off the left edge of the graph, and we only see current traffic, however on a couple of occasions we've seen high utilisation of the link immediately before a failover. We logged cases with both Meraki and our ISP. Our ISP's router logs show that their LAN interface which connects to our firewall drops, but their WAN (internet) link remains up and available. To find out if the router or the MX was faulty, we installed a switch between them so we can log which port drops. We saw the MX's WAN1 port would go off during the outage. Meraki took this information, and replaced our MX. The replacement was installed on Wednesday, but the problem has continued - mostly during the night: 2 hours Thursday - midnight to 2am (both circuits) 4 seconds Thursday - 09:46:03-09:46:07 (primary) We have managed to get PRTG up and running to monitor the interfaces, and interestingly this is showing zero downtime on either interface for the same periods. Could this be a false positive? Could the cloud dashboard be recording loss of connectivity when in actual fact it is fine? These "new" outages on the replacement MX have so far only happened overnight - so I am hoping that this is just the cloud being stupid. Anyone have any thoughts?
... View more
04-08-2022
02:30 AM
1 Kudo
Apologies, it's a 2530, and I don't think EEE is enabled? HP-2530-48G(config)# sh savepower led LED Save Power Information Configuration Status : Disabled HP-2530-48G(config)# sh savepower port-low-pwr Port Save Power Information Configuration Status : Disabled HP-2530-48G(config)# sh energy-efficient-ethernet Port | EEE Config Current Status txWake(us) ----- + ---------- -------------- ---------- 1 | Disabled Inactive - 2 | Disabled Inactive -
... View more
04-06-2022
09:12 AM
We have the same problem, only slightly reversed. We saw the MX drop WAN1 at random - only for a second or two and then come back up. We were directly connected to the ISP router and they were saying it is the MX dropping, whilst Meraki were suggesting it is the ISP router. We installed an HPE Aruba 2920 in between to log the port changes and we can see that the MX is indeed dropping the WAN1 interface, whilst the ISP router stays up. We logged these findings with Meraki and they are replacing the MX as they believe it is a faulty port.
... View more
04-06-2022
08:59 AM
That has worked a treat! Thanks very much indeed, that is exactly what I needed to see! Next question - is there a similar template for the MS range?
... View more
04-06-2022
08:06 AM
I downloaded the MIB and copied it to C:\Program Files (x86)\PRTG Network Monitor\MIB - is that all I need to do, or is there some more magical process to get PRTG to see it?
... View more
04-06-2022
08:04 AM
I have v2C and V3 enabled and have tried with both. How did you get yours set up?
... View more
04-06-2022
06:45 AM
Hello all, For weeks I have been trying to set up my PRTG instance to monitor our MX bandwidth (or in fact, any sensor!) and failing miserably. I've enabled SNMP in Organization>Settings, enabled SNMP Traps in Alerts, and opened the port in the firewall but whatever I do I cannot get the PRTG instance to register that the devices exist expect for the default ping sensor. I've tried following the instructions in the Meraki KB article on the subject, (https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/SNMP_Overview_and_Configuration) but PRTG still cannot communicate with any of my devices. I am really confused where Meraki says "by default Meraki devices cannot be polled via SNMP from outside the local IP network" but yet earlier in the documentation it says that the hostname for all SNMP requests should be "snmp.meraki.com" so I can't see how those two statements can match up? Either way, using the MIB file downloaded from the portal and uploaded into the PRTG system, or using the built-in MIB's doesn't work and I just get errors. I've even tried to test the devices from a PC within the network by using Paessler SNMP Tester. This is what I get each time: 06/04/2022 14:41:01 (4 ms) : Device: snmp.meraki.com 06/04/2022 14:41:01 (7 ms) : SNMP v3 06/04/2022 14:41:01 (9 ms) : Walk -v2c -t 10 -c meraki 10.0.0.252:161 06/04/2022 14:41:01 (168 ms) : Error: -2007 Does anyone in the community successfully monitor their Meraki install using PRTG or similar?
... View more
04-01-2022
03:49 AM
2 Kudos
Of course! I'm dumb. When I connected the switch it was sending out BPDU's like crazy, and because we had BPDU guard enabled, the Meraki port transitioned to a disabled state. Because it is a switch and not a client device it would always send BPDU's. Thank you @ww and @alemabrahao for the info.
... View more
04-01-2022
03:32 AM
Yes, BDPU guard was enabled on the Meraki trunk port, but I had to switch it off to get the CBS switch to work.
... View more
04-01-2022
03:29 AM
They are not Catalyst switches. These are CBS-250's and 350's. BDPU guard is not enabled on those switches.
... View more
04-01-2022
03:25 AM
We've recently done this due to a flapping port on either the MX or the ISP router. We used an HPE Aruba switch with no config. Works well!
... View more
04-01-2022
03:13 AM
The core stack is priority 0: The Cisco IOS devices have RSTP enabled, and the uplink is a trunk port: POD-SW1#sh span Spanning tree enabled mode: RSTP Default port cost method: long Loopback guard: Disabled Root ID Priority: 0 Address: a8:46:9d:d9:1e:11 Cost: 50000 Port: gi1 Hello Time: 2 sec Max Age: 20 sec Forward Delay: 15 sec Bridge ID Priority: 32768 Address: 2c:1a:05:26:39:e8 Hello Time: 2 sec Max Age: 20 sec Forward Delay: 15 sec Number of topology changes: 2 last change occurred: 165:24:43 ago Times: hold: 1, topology change: 35, notification: 2 hello: 2, max age: 20, forward delay: 15 Interfaces Name State Prio.Nbr Cost Sts Role PortFast Type --------- -------- --------- -------- ------ ---- -------- ----------------- gi1 enabled 128.1 20000 Frw Root No P2P (RSTP) gi2 enabled 128.2 2000000 Dsbl Dsbl No - gi3 enabled 128.3 20000 Frw Desg Yes P2P (RSTP) gi4 enabled 128.4 20000 Frw Desg Yes P2P (RSTP) gi5 enabled 128.5 20000 Frw Desg Yes P2P (RSTP) gi6 enabled 128.6 20000 Frw Desg Yes P2P (RSTP) gi7 enabled 128.7 200000 Frw Desg Yes P2P (RSTP) gi8 enabled 128.8 20000 Frw Desg Yes P2P (RSTP) Po1 enabled 128.1000 20000 Dsbl Dsbl No - Po2 enabled 128.1001 20000 Dsbl Dsbl No - Po3 enabled 128.1002 20000 Dsbl Dsbl No - Po4 enabled 128.1003 20000 Dsbl Dsbl No - _____________________________________________________________________ POD-SW1#sh run int ge1 interface GigabitEthernet1 switchport mode trunk
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 5 | 3234 | |
| 2 | 730 | |
| 2 | 1522 | |
| 2 | 1528 | |
| 1 | 1354 |
