All
Small
Medium and large
Upgrading right now 🙂
It's been running stably for me on an MX75 for 28 minutes...
And it also seems fine for me on MX85.
Nice!
@cmr wrote:What's new
- Added API support for configuring Multicast Forwarding
- Added API support for configuring Split DNS
Is there any documentation about these two features?
I was also wondering about Split DNS ... but perhaps its for Anyconnect ? - Or do you mean the API support and not the feature as documentation ?
/Thomas
Both, I think I was hoping that we'd get some DNS proxy / conditional forwarder support on the MX platform but that might be asking too much.
Security and SD-WAN (MX,Z) Features Directory - Cisco Meraki Documentation
API for Local/Split DNS Service* | Gives administrators the power to control which DNS requests are answered by which servers. |
Sounds like it may be just that! Lacking any other documentation at this time. They have also updated that entry to be 'API for..', it used to just say 'Local/Split DNS Service' so sounds like it will only be configurable in the API and not the GUI??
Very interesting - Lets see what happens.
I'm thinking API first and then they'll build the dashboard interface for it later
I dont understand that at all ...
I'm guessing the traffic classification engine changed and while it updates, it might not work. Therefore people could visit sites that are blocked or similar, but just for the few minutes the upgrade takes.
I was wondering the same thing.
So ... "during" the upgrade the MX can misclassify traffic ??? .. until the upgrade is done at it reboots ?
Is that what it is saying ?
Same... because when the MX is upgrading , well it's upgrading , nothing is working and the device has to reboot to perform the upgrade.
Orrrr let's say you schedule a device upgrade in 2 weeks. The software is downloaded on the MX and untill the upgrade window , the classification is broken ? 🤔
Normally the MX continues to work from the time you schedule the upgrade, through the download and install and only stops for the reboot. I think it's the install part where it will pass traffic but might misclassify it.
I think it's as @cmr described - Once you kick off the upgrade, there's a few steps involved (simplified below):
- 1. Downloading
- 2. Updating packages/services etc.
- 3. Reboot of device
I assume the time of misclassifying traffic is specifically between steps 2 and 3 which is probably like a 5-10 minute window.
Running 19.1.5 since 24 hours ago on MX95 without any issue
Upgrading MX75 now...
I upgraded a few to test with, any without dual WAN connections immediately quit passing traffic. WAN2 showed 100% loss, even though there was never a WAN2 connected. I converted LAN to WAN and then WAN to LAN and everything started functioning properly and the WAN2 loss went away and the networks started functioning properly.
Yes, all MX67.
Only effected devices with something plugged into Port 2 from what I can tell. I've found this to be true on 9 devices so far.
Possibly only devices with static addresses assigned to WAN1. I've got some devices that are DHCP on WAN1 and they weren't affected.
If anyone is upgrading from MX 18.107 or MX 18.211 AND has a signifiant network usage ( device utilization over 15-20% before the upgrade ) I would be curious to see the device utilization AFTER the upgrade. Please share your results.