Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi,I have been reading this document : https://documentation.meraki.com/Switching/Cloud_Management_with_IOS_XE/Design_and_Configure/Cloud_Managed_EVPN_Fabric_Technical_GuideI'm wondering if it is possible to have a Campus Fabric in Routed Access in a...
Hi ,There is some discrepencies between getOrganizationSwitchDevicesSystemQueuesHistoryBySwitchByInterval and the dashboard. 1- Dashboard doesn't list "Queues" that are not used by the switch. Eg : the switch doesn't run LACP or OSPF it won't be disp...
Executive summaryThis is a maintenance update for the MX 18.1 release family with fixes for PPPoE configuration and MX84 storage durability.Bug fixes - general fixesFixed an issue that could cause the Local Status Page to save invalid PPPoE settings ...
Hi , Anyone here running MX 19.2.9 ? If so can you check the firmware version with the API ? ( getOrganizationDevices )100% of my networks migrated are showing : "firmware": "Not running configured version",
"url": "xxxxx",
"details": [
...
No it is not. It depends if you need redundancy on the WAN side. When the failover will occur if you don't have the MX sharing the same IP , some flows are going to break. If that's not a concern , don't bother getting 3 public IPs.
Can't believe Cisco is even considering fixing this. I have tried many times in the past and even had a chat with the BU without gaining any traction. I'm very happy to read that.
Only took 1 year but it is now fixed in MR 32.2.5 : https://documentation.meraki.com/Wireless/Product_Information/Compatibility_and_Firmware/MR_32.2.5_Release_Notes#mr-84271
It should unless specified in the firmware. https://documentation.meraki.com/Platform_Management/Product_Information/Compatibility_and_Firmware/Security_and_SD-WAN_(MX%2CZ)_Features_DirectoryNote - The MX18.1 firmware release will be the maximum runn...