About PaulMcG

PaulMcG · ‎09-23-2022

The fact other SSIDs have no issue still leads me to think there's a missing vlan on the port the AP is connected to. Otherwise you can always try rebooting the AP or checking for new firmware.

PaulMcG · ‎09-23-2022

Do you have any other AP with this SSID having the same issue or just the one? Have the server and MR42 changed switchports or just the server? Even if the port facing the server/AP are correctly configured, have you checked links between switches in case a vlan is being pruned?

PaulMcG · ‎09-23-2022

Is the SSID tagged to a vlan?

PaulMcG · ‎09-06-2022

A new SSID tagged to a vlan for their usage could be setup. Assuming the APs are on switchports set to trunk mode. After that it's just a matter of isolating that vlan to keep the traffic seperate from yours.

PaulMcG · ‎08-24-2022

Generally 5 to 10 minutes from bootup a switch should be connected to dashboard. I have had some instances where a switch was powered up for like an hour before having an uplink connected and then I still had no connectivity after 20 minutes. So I usually make sure an uplink is connected before powering up a switch. Although this might not apply to your scenario.

PaulMcG · ‎08-24-2022

Looking through license notifications from some organizations I manage and I find notifcation emails at 90 days, 30 days, 2 days and 1 day. There might be more that got deleted.

PaulMcG · ‎07-11-2022

We started seeing the same error on all our organizations even though the licence page indicated everything is fine.

PaulMcG · ‎06-28-2022

I'm in Canada too but still don't like using kilometers. Your customer's current setup seems like what I've seen at most campgrounds I've encountered. A bunch of what was on sale at Best Buy last week that kinda works but no one is really happy with. You can also look forward to explaining why they have to pay for a year round license when they're closed with 6 feet of snow on the ground half the year. I wouldn't depend too much on a survey of what's currently there as RF power settings are most likely completely out of whack so won't really get you any useful data on what is really needed. As far as frequencies, you're going to want to use 2.4GHz wether it's future proof or not as it will give you the best range. Also, if any MESH repeaters are needed, you want to keep your 5GHz bands free for uplinks and only allow clients to connect to 2.4. If your customer is already on a shoestring budget, not really any point talking about WiFi 6E. Besides, in terms of Meraki at the moment, the only AP that supports it is the MR57 which isn't for outdoor use anyways. I imagine most other vendors 6E APs are also part of their premium lineup.

PaulMcG · ‎06-28-2022

I've worked on both small campground/low budget as well as a large campground/big budget installs using MR74/76. My advice, run. Failing that, make sure customer expectations are well documented to avoid a moving target. End users won't have the same expectations as the campground operator so this will save you some headaches. Asside from Meraki not being a low budget solution, lots of other costs come with a campground install. Poles, underground cable runs for ethernet/fibre or power if you go with MESH, etc. We've quoted many small campgrounds who were willing to foot the bill for the gear but when the extras were explained, they always backed out. I would only use MESH to plug holes that are too difficult to cable rather than as a way to cover a large area. POE extenders are a better option to get more reach. Doing a survey is essential.

PaulMcG · ‎06-14-2022

Organization - Overview, go to the Devices tab, click on the + button at top left and add columns for Uplink IP (Port 1/2). On any MX device you will get IP assigned to WAN 1 and 2.

PaulMcG · ‎05-09-2022

The Release Notes indicate what comes with the firmware update. Bug fixes might be for features and/or devices that might not apply to your specific MX or required features. So an update can be available but not really be of any use to your specific scenario, so you have the option to upgrade if you want or avoid downtime if it's not needed.

PaulMcG · ‎04-29-2022

Additionnal info: that was from version 14.33.1 changelog, but the case I had was from MS390 running 14.32, same as you. So it might be an issue since before 14.33.1.

PaulMcG · ‎04-29-2022

From the Meraki firmware changelog: In rare instances, MS390 management plane will disconnect from dashboard until rebooted Rare instance but I had a data center with two MS390s where one lost dashboard connectivity followed by the other a week later. Both came back after a reboot. Only management plane affected as client didn't even know there as an issue.

PaulMcG · ‎04-12-2022

Been expecting that to be an issue with certain customers. Went through the same situation with the updates to Layer 7 when going from 15.x to 16.x.

PaulMcG · ‎04-08-2022

Good to know. This location is actually moving next week and I was hoping to have LTE up and running for the move. It will give me a chance to try upgrade to 17.6 again to see if I get better results.

PaulMcG · ‎04-08-2022

Have one customer where 7 MX68CW were upgraded to 17.6 and now 3 are having the same "connecting" issue you describe. Trying a rollback on one to see if it fixes the issue.

PaulMcG · ‎03-31-2022

Two public IPs are a minimum with an HA setup but if you want to use the VIP option, a 3rd public IP is also required.

PaulMcG · ‎03-21-2022

Meraki have a best practice guide for WIFI designs with recommendations on AP models depending on ceiling height about halfway down the page. Anything above 8' AP with external antennas are recommended. https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/High_Density_Wi-Fi_Deployments

PaulMcG · ‎03-14-2022

In any warehouse deployment we always go with external antennas, so in your case it would be a MR46E. The location of the APs all in a row aren't helping either. A proper site survey will indicate where they should be, but I don't see the logic of having them placed as you've indicated. Power settings aren't helping either. At a customer with a similar environment to what you describe, we have power settings of 9-14 for 2.4, and 10-17 for 5 and almost all the APs are running on the lower end of the scale.

PaulMcG · ‎03-14-2022

MX+MR is the better option. To add to what @Bruce already menitonned: -You can place the MR wherever it is needed in the office to improve coverage, whereas an MX(W) usually ends up in the wiring closet or worse, enclosed in a metal box with the rest of the networking gear/ISP modem. -An MR gives you the flexibility to run a seperate wirless network and template, should you choose to go that route if you have a large number of sites.

PaulMcG · ‎03-11-2022

I've moved an MX with a static WAN IP to a different organization without the MX losing the IP. That being said, I would assume the static IP will be lost and plan accordingly with someone at the site who can configure the IP on the MX if it's lost.

PaulMcG · ‎03-09-2022

Track by IP is not supported in a combined network. You would need to split up the network if you want to try it.

PaulMcG · ‎03-08-2022

Never heard of a limit, but I've never had to reserve that many either. The biggest DHCP pool an MX can handle is /19, per vlan, so I don't think 600 reservations over 5 vlans would be too many.

PaulMcG · ‎03-08-2022

The VPN subnet has to be enabled on the S2S VPN config page so that VPN clients can go over the S2S VPN.

PaulMcG · ‎03-08-2022

When you say VPN is allowed on both networks, are you talking about Client VPN or Site-to-Site VPN? You have to enable S2S VPN access for the client VPN subnets, same as you do for VLANs.

PaulMcG

Community Record

Badges