Meraki

PhilipDAth · ‎Sep 11 2018

The PoE injector is interesting. If you plug the AP directly into the PoE injector via a patch lead does the issue still happen (perhaps there is a cabling issue)? If you plug the AP directly into a PoE injector, and disable LDP and CDP does the issue still happen? Using PoE injectors on a port that supports power negotiation via LLDP can produce unpredictable results.

PhilipDAth · ‎Sep 11 2018

The MX67C does use external antenna. Refer to this picture: https://meraki.cisco.com/products/appliances/mx67c#technology Meraki only offer the one type of antenna (that ships with it). You would need to source your own antennas seperately. That note RF signal drops off pretty quickly, so you want the RF cable leads to be as short as possible, or you'll need to compensate by using lower loss cable (and the lower the loss the more the cable costs).

PhilipDAth · ‎Sep 11 2018

The root certificate is documented in the link you provided. No one else is concerned the deployed root certificates match the documentation. I think you are the only person concerned.

PhilipDAth · ‎Sep 11 2018

Have you got both CDP and LLDP enabled on the switches? If so, and one of them is not advertising the correct information then you will experience intermittent failures. If both are enabled on the switch then try disabling one. I think you should also try and standardise on using one firmware version on your switches. You are getting inconsistent results and and a mix of firmware versions.

PhilipDAth · ‎Sep 10 2018

Another thought, MR24.5 added the ability to negotiate power using CDP as well as LLDP. If your switch can do CDP and LLDP - trying disabling one of them, and using just one at a time. Perhaps the switch lacks the ability to negotiate power properly using both protocols.

PhilipDAth · ‎Sep 10 2018

The new "E" access points also use this firmware, even if the dashboard reports 25.x.

PhilipDAth · ‎Sep 10 2018

I've had issues with the MR42E but not the MR42. The MR42 has been rock solid. Also note that while an MR42 will work on 802.3af it will retard its performance to work within that power budget. You need 8023.at for it to run at maximum performance. Have you seen if there are any firmware updates for the switches? Does anything appear in the switch log? Is there any chance you have exceeded the switch POE budget, hence preventing the AP from getting enough power to boot properly? For a switch that is having this issue with the AP - what does it report its PoE co assumption to be and what budget does it report it has available?

PhilipDAth · ‎Sep 9 2018

Mr FedEx seems to have been a bit slower getting to my office. Maybe he's getting tired of doing deliveries.

PhilipDAth · ‎Sep 7 2018

Lets consider MPLS a little bit further. For the "customer" view it virtually looks like a full mesh. Physically however it is quite different. Your have the CE router on the customer premise, which then connects to a providers PE router, and then to the providers code. When site A talks to site B it goes CE->PE->Core->PE->CE. The important bit to note is that it traverses the providers core. It isn't actually physically a full mesh. The traffic does not magically physically jump from one branch CE to another branch CE (there is no actual physical mesh). The provider core is essentially the same as your Meraki Hub. Just like the service providers core network - you need to make sure your Hub environment has plenty of bandwidth and redundancy and processing capacity to ensure that their are no issues. I have run a 300 site Meraki network off a pair of MX's as a hub and it runs great. If your deployment is spread over over a large geographic area (such as multiple countries) you could also consider using multiple hubs - a pair for each area. That way traffic within from site to another in the same geographic area will not leave that geographic area.

PhilipDAth · ‎Sep 6 2018

I've changed my mind. Use the Bulk network creation tool. https://documentation.meraki.com/zGeneral_Administration/Templates_and_Config_Sync/Using_the_Bulk_Network_Creation_Tool

PhilipDAth · ‎Sep 6 2018

I think you'll need to use a script to do this. You'll need VLANs enabled, and you'll want to use this API: https://dashboard.meraki.com/api_docs#update-a-vlan @HodyCrouch will be able to give better advice.

PhilipDAth · ‎Sep 6 2018

Your 2.4Ghz spectrum on some of those access points seems very busy and could easily be causing you issues. I would also try giving the AP a power cycle, just in case it has gotten into a suck state. But my guess is this is not a hardware issue. It is an issue with clients not under your control.

PhilipDAth · ‎Sep 6 2018

If none of those devices show up then they may be flooding on another WiFi network that is not yours. I would also take a look at Air Marshall and Wireless Health. It sounds like you might not have enough RF spectrum in the area. If you have 2.4Ghz enabled I would try disabling it. 5Ghz has a lot more spectrum available. You could putting in an extra AP in the area to reduce the impact.

PhilipDAth · ‎Sep 6 2018

You aren't using any third party repeaters are you? What are these devices listed as causing a packet flood? 8A:15:04:FA:B4:82 F8:E4:FB:E2:BA:1D 72:C2:46:14:BF:37

PhilipDAth · ‎Sep 5 2018

Just in case everyone didn't spot this - half of the MOTM's come from New Zealand. We are a Meraki powerhouse!

PhilipDAth · ‎Sep 5 2018

You can't do the claim as soon as you get the email. You need to wait a good 4 hours or so.

PhilipDAth · ‎Sep 4 2018

Phew. What an effort that was. 🙂

PhilipDAth · ‎Sep 3 2018

I haven't mentioned it to anyone. I wasn't sure if anyone else was also experiencing the issue.

PhilipDAth · ‎Sep 2 2018

For me, having just the agent installed works - it is only when I deploy the Meraki management profile to the Windows 10 device that it seems to kill the Azure AD membership (eventually, not straight away).

PhilipDAth · ‎Sep 1 2018

Have you configured an IP address restriction in the APC interface? I would be tempted to factory reset the APC management card and set it up again from scratch using the new IP addressing. And yes, a firmware update wouldn't hurt.

PhilipDAth · ‎Aug 31 2018

I haven't experienced that issue; but I have had another issue. I have had two machines I am playing with, both AzureAD joined, and enrolled with a Meraki profile. If I leave the machines unused, and not logged in, for say two weeks, the primary Office 365 account that was used to log into the machine disappears - and the original user can no longer log in again. So now I'm wondering about you saying you can not log in anymore - because the password no longer works. Could it be perhaps not the password - but my case - where the whole account is now gone from the machine? In my test machines, to get it working again, I had to repeat the AzureAD join process. ps. I enabled the local Administrator account so I still have a way to login and see what is going on.

PhilipDAth · ‎Aug 31 2018

@MacuserJim is correct - the new built in LTE modem serves exactly the same role as what an existing USB plug in cellular modem did - it only functions as a backup. Having said that, if you have nothing plugged into WAN1/2 then it will become permanently active.

PhilipDAth · ‎Aug 29 2018

It is probably easiest to deploy a proxy server in each location (like squid). Then create a WPAD auto-proxy configuration script (which web browsers use) and tell it which sites are to go via which proxy. You'll want a VPN linking the two sites so users at either site can use either proxy server.

PhilipDAth · ‎Aug 29 2018

Both antennas are used at the same time, and the signals are combined using MIMO.

PhilipDAth · ‎Aug 28 2018

A big shout out to the Meraki employee's who have also contributed but that largely go unrecognised. Also a thumbs up to @CarolineS and the team at FedEx.

About PhilipDAth

PhilipDAth

Philip D'Ath

Community Record

Badges