Meraki

cmr

Thanks @alemabrahao using MAB and then selecting Access Manager and picking MAC address might do what I want. Time to experiment!

cmr

I was looking into using adaptive policy and it seems that objects can only be matched on CIDR. I was wanting to use it in lieu of Smartports not being supported on any of the Catalyst based switches. This would require matching on MAC or something else that does not seem to be supported. Is there a way of putting IoT devices of a known type into a specific VLAN other than Smartports? Or is there a plan to roll Smartports out to the C9x00 switches?

cmr

I agree with @RWelch and regarding 6GHz, I have found it to work reliably for Windows and Apple computers, but not to much for Android phones. Depending on the distribution of your clients across your SSIDs you might want to enable 6GHz on some and not others. Bear in mind that 6GHz requires WPA3 and I have found WPA3 only to be okay for the computers mentioned above. Do not even think of using WPA3-Transition mode, in my experience it doesn't work at all reliably!

cmr

There was a bug relating to ports 25-48, mainly on the MS220s and MS320s from memory, but might well affect other models.

cmr

As there are two page generations for switches, I have been trying to use the new one, but it doesn't populate any power information for my MS220-8p switches... So I use the old one most of the time, today when I switched over to an MS220-8p with has an MR55 plugged into it, it showed 16.7W consumed in the section on the left (but changed before I could screenshot it...). Initially I thought, how is it consuming more than budgeted, but then I checked the datasheet and the MR55 can consume up to 22W of power, so where does the error lie??? On another MS220-8p I have, there is a CW9163E and MV73X connected and both of those budget 30W, so it isn't like the switch doesn't know how to supply over 16W...

cmr

I WANT IT Please 😊

cmr

FS.com do make up cables that mimic different vendors at each end, but of course they are not OEM cables... This is the cable https://www.fs.com/de-en/products/49577.html

cmr

@PhilipDAth what about stack replace member, or will that not allow an MS350-48FP to replace an MS350-48P?

cmr

0,1 and 2 are the SNMP interface IDs, the LAN ports on an MX75 also started at 0 last time I looked, so 4 is 0, 5 is 1 etc. This why the MX LAN interface page was pulled after less than a week, due to the interface numbering not being consistent. That was a few years ago and it still hasn't come back, so I think the change may be more involved than we think. I'd love it to be fixed and the LAN interface page to return 🤞🙏

cmr

I'm guessing that the NIC is trying to use an MCS table entry that is beyond the MR56, do you have an MR57 or CW916/7x AP that you could try and see what bitrate it connects at?

cmr

Are you using IKEv2 and is only one SA establishing? If so try IKEv1, but as you have dynamic peers you may already be using IKEv1...

cmr

I would have thought you could do this, but it isn't something I have tried.

cmr

The computers are making you buy more computers, it's there way of taking over 😉

cmr

Cellular gateway firmware versions MG 4.1.1 changelog Executive summary This is an update to the new MG 4.1 feature release. It mainly includes HTTPS support for the device local status page. Additionally, we have improved connectivity through the addition of a new provider and more built-in APNs to AutoAPN and improved band support for MG52 appliance’s “day 0” connectivity through eSIM. What's new Added HTTPS support for the device local status page. Added support for the Transatel provider. Updated the list of built-in APNs for the Mint provider to include “wholesale”. Updated the list of built-in APNs for the Bell provider to include “mnet.bell.ca.ioe”. MG52s will now be able to establish “day 0” connectivity across a wider range of bands and providers using the built-in eSIM. Other Updated the default login credentials for the device local status page. The new login is a username is "admin" and the password is the device's serial number in upper case, with dashes included. If a custom login credentials have already been configured on the Meraki Dashboard, those will continue to be used.

cmr

Cellular gateway firmware versions MG 4.1.1 changelog Executive summary This is an update to the new MG 4.1 feature release. It mainly includes HTTPS support for the device local status page. Additionally, we have improved connectivity through the addition of a new provider and more built-in APNs to AutoAPN and improved band support for MG52 appliance’s “day 0” connectivity through eSIM. What's new Added HTTPS support for the device local status page. Added support for the Transatel provider. Updated the list of built-in APNs for the Mint provider to include “wholesale”. Updated the list of built-in APNs for the Bell provider to include “mnet.bell.ca.ioe”. MG52s will now be able to establish “day 0” connectivity across a wider range of bands and providers using the built-in eSIM. Other Updated the default login credentials for the device local status page. The new login is a username is "admin" and the password is the device's serial number in upper case, with dashes included. If a custom login credentials have already been configured on the Meraki Dashboard, those will continue to be used.

cmr

@PhilipDAth I think it's rolling out still, I have a customer on shard 856 where it isn't forced yet...

cmr

I have stuck with 17.1.4 on sites with older switches, some as I had no choice (MS220-8p), but it does look like it is geared to the newer switches.

cmr

I think this tells a story: That is for an MX75. Interesting that the MX68W for @RWelch also shows a drop...

cmr

This one is a good start: https://community.meraki.com/t5/Cisco-Meraki-Network-Engineer/ct-p/CMNE-F

cmr

@Commenterry are you the only admin? As an aside, if you are I would highly recommend setting up another, even if it is just another email address for you... If you are, then you will need to contact support to get the MFA reset. If you aren't then the other admin can reset your MFA for you.

cmr

It will time out in that case, I have had it happen a number of times. I agree it should use the same route as the management traffic.

cmr

What model switches are they and what firmware version are you running?

cmr

Also noticed this about 10 minutes after the upgrade: Intrusion detection rules update: snort_rules_version: 20250612-1532 Interesting that it needs to apply a version from almost a month ago...

cmr

Applied and on the reboot it just stayed orange... Pulled the power and it rebooted okay. One to not trigger remotely for the moment!

cmr

There is another around device utilisation as well, I have scheduled the upgrade on my MX75 and we will see!

About cmr

cmr

Community Record

Badges