Meraki

MRCUR · ‎Dec 9 2024

" MX: MX Warm Spare - High-Availability Pair Change: Updated requirement: "Ensure that both MX's have their own uplink IP address for dashboard connectivity as mentioned here. If a virtual IP is being used, an additional IP address is needed, and all three IP's must be in the same subnet." This should be "MXs" and "IPs" without the apostrophes.

MRCUR · ‎Nov 18 2024

Found the issue: IOS-XE mode switches do not include the Message-Authenticator attribute even though in CS mode they do (MS switches also include it).

MRCUR · ‎Nov 12 2024

Has anyone tried RADIUS with a C9300 that's been migrated to native IOS-XE? The switches keep logging "sessmgrd: Cannot open UDP socket for service Radius server" and we don't see any traffic to the configured RADIUS servers but we do see it in the aaa config.

MRCUR · ‎Oct 15 2024

@WirelesslyWired Yes that's correct.

MRCUR · ‎Oct 15 2024

Thankfully I haven't had the issues like @PhilipDAth with a migrated MS390, but I do have a C9200L that seems to be happy never kicking off the migration. Definitely not enough info through CLI or Dashboard to tell what's going on or what's not going on.

MRCUR · ‎Oct 14 2024

I think this should say "last fetched" once on IOS-XE.

MRCUR · ‎Oct 14 2024

The tools (including CLI) work for me on a migrated MS390. It seems like your migration might not be done yet or something else is going on.

MRCUR · ‎Oct 3 2024

There are dozens of us!

MRCUR · ‎Sep 21 2024

Glad to see these being posted again. No updates for August?

MRCUR · ‎Mar 16 2024

Did you get a resolution for this issue? I'm seeing it on an MX95 and the issue has persisted even after a downgrade back to 18.107 firmware.

MRCUR · ‎Feb 23 2024

Palo Alto to Meraki MX? That's quite the downgrade in feature set.

MRCUR · ‎Sep 1 2020

This might be my favorite episode. Let's do it again sometime @merakisimon! 😉

MRCUR · ‎Apr 26 2019

@Chriz_J I'm not sure what you mean by "emergency" management IP. If you set an IP through Dashboard or the local UI for a switch, that is the IP the switch will use for its Dashboard (Internet) connection. There isn't a concept of a "backup" or "emergency" IP on Meraki devices (they will automatically revert to a previous IP however if you incorrectly configure the management IP).

MRCUR · ‎Oct 27 2018

Ask for some pizza while you're at it.

MRCUR · ‎Oct 17 2018

@nikiwaibel While I understand what you're going for, badgering Support about this isn't going to change anything right now. Make sure your sales team knows you want IPv6 support in the MX line so they can add your account ($$$) to the feature request.

MRCUR · ‎Oct 12 2018

Unfortunately @MacuserJim is correct. The timeout is a global org setting so the users will need to keep the session active. If you have video walls set up, you could use the new auto rotate walls option to have the page auto refresh and move between walls. This should keep the session alive although I have not tested it since the feature just launched (hopefully it's available for everyone!).

MRCUR · ‎Oct 12 2018

This isn't supported today for certs or credentials on the MV. You could use MAC based auth as a workaround.

MRCUR · ‎Oct 11 2018

If your core Cisco switch has a default route pointing at the ASA's "inside" (LAN) IP, then you can replicate that on the MX using the "use a single LAN" option. You would create a "Local LAN" that matches the ASA's inside IP and then create static routes for all of your internal subnets and put the Cisco switch IP as the next hop.

MRCUR · ‎Oct 4 2018

This should work fine. I have my Z3 behind a Ubiquiti USG and previously had it behind an MX64.

MRCUR · ‎Oct 2 2018

@jdsilva wrote: Try swapping the fibres around. To clarify what @jdsilva is saying - you have two fiber strands, flip them (on the fiber patch panel likely) so they're opposite what they are now. It's likely that you have TX going to TX and RX going to RX right now instead of TX to RX.

MRCUR · ‎Oct 2 2018

@PhilipDAth wrote: vMX is not free. You need to buy a licence from Cisco Meraki to use it (like all other Cisco Meraki kit). You also need to pay Microsoft Azure for the virtual machine charges and data traffic. Philip is right. The only thing "free" about the vMX is the VM image itself.

MRCUR · ‎Sep 26 2018

I would recommend removing the config and moving to a supported setup. I've created a VLAN for the L3 MS devices on the upstream switch they connect to which provides the switches with Internet access. I then make this a tagged VLAN on the MS uplink port and set the VLAN as the management VLAN for the device in Dashboard.

MRCUR · ‎Sep 26 2018

My understanding on this after speaking to multiple engineers is that the setup you are using is not supported. I originally wanted to setup my L3 MS switches this way and was advised not to because of this.

MRCUR · ‎Sep 21 2018

Apple defines what the restriction payloads can do, not Meraki. You should submit this feedback to Apple directly.

MRCUR · ‎Sep 21 2018

I don't think so. The delay date is set based off of "release date" which is 9/17/18.

About MRCUR

MRCUR

Community Record

Badges