Meraki

clopez · ‎Jul 24 2025

Edit: Sorry I just realized you mentioned the dedicated mgmt port. I was more talking about the switches internal IP, the one it uses for management traffic, not the status page port. (though that would be nice to access internally in an easier fashion) Thanks for the further info. What I am seeing is two IPs though. Using your example IPs. My switches SVI is at 10.0.0.2 In the dashboard shows 10.0.0.210 as its private IP I tried to change the management VLAN to see what would happen and despite the switch changing IPs properly (I could ping the new IP), and seeing the new IP reach out to DNS and Meraki IPs via our firewall upstream, it went offline and reverted 2 hours later. I guess this is the quirk? since its not the primary SVI it wont work. I can work around this, I will likely end up placing a secondary monitor/probe on the same subnet so that it can reach the management interface and map the network more accurately.

clopez · ‎Jul 23 2025

We have a C9300L that is doing L3 routing, unfortunately its not setup the way we'd like ti to be, its using a particular internal VLAN as its transit vlan as well. i.e. 172.16.100.2 is the VLAN IP and GW for endpoints but its management IP is 172.16.100.10 On another vlan we have a network probe that can communicate with 172.16.100.0/24 but it cannot specifically with 172.16.100.10 (the C9300 management IP) Initially the management IPs GW was pointed directly at the upstream firewall, and I thought return traffic was going there and dropped but even after changing the GW to its own VLAN IP (172.16.100.2) it is not communicating. Is this just an issue with that transit vlan being shared or is this a quirk of the Meraki Managed C3900s? I do notice that there is no ARP entry on the core for that IP.

clopez · ‎Jul 7 2023

So we're having hit or miss experience recently. If I am understanding this correctly Windows 10(22H2) / 11 are now defaulting to TLS 1.2 (or maybe even 1.3) and this is causing authentication issues when communicating/trying to auth with the old RADIUS server. It seems I can just add the reg key to force the server to use TLS 1.2 but the MRs themselves dont support TLS 1.2. Does that affect clients as well or does that only affect the RADIUS Testing the MR does (theres a checkbox for this) Am I safe to enable TLS 1.2 on the server side to resolve Windows client issues or do I have to force Windows Client to use 1.0 (via a GPO or MDM) or replace MRs?

Meraki

Community

About clopez

clopez

Community Record

Badges

Re: Meraki C9300 Management interface not communicating with endpoints on o...

Meraki C9300 Management interface not communicating with endpoints on other...

Microsoft NPS, TLS 1.2, older MRs. Trying to clear up some confusion.