Meraki

Iansays1

Still struggling with this. Cloning the existing network seems to work ok, but after adding the new MX105 & 3 unconfigured switches to the new, cloned, network, the 3 new switches go dormant or offline. I'm assuming this happens because the config on the MX105 has changed and the IPs it was assigning the switches are no longer in the right DHCP scope the MX105 inherited from the clone. The newly cloned MX105 also won't give out IPs in the cloned scope to the switches or even a laptop plugged directly into a LAN port on the MX105. Not sure what's going on here. Also weird: removing the MX105 from a network and trying to do a factory reset doesn't work. It retains the static IPs one would assign in the local config page. And I can only get to the local config page by hard coding my laptop NIC to 192.168.0.x

Iansays1

Thank you. Will review that today.

Iansays1

>as not everything is going to be patched in the same! You are exactly correct. I had visions in my head about preserving some of the port specific settings we've made over the last several years (ports that started dying and had to be set to 100 non-duplex, for example), but all my new ports should work properly without any of that. Thanks for reminding me of that!

Iansays1

I'm able to clone the MX100 and prep the MX105 with all the config, firewall rules, etc.. Not sure of the approach to take with the 3 new MS350s (old are also MS350). And/or how to integrate the newly stacked switch into the new combined network the cloned 105 is currently the only member of. And while I'm asking, I have 3 APs (MR33) that were (incorrectly, I think) added as a seperate 'wireless' network in the same physical location as the old MX100 network, and ideally, I'd like to migrate them into the combined new network. We are moving offices and the replaced equipment (MX100 and 3 stacked MS350s) is going to be delicensed and mothballed for disaster recovery options. And I'm trying to stage as much of the new equipment as I can, running in parallel, aside from the MR33s. Thank for any thoughts, advice, well wishes. Ian

Iansays1 · ‎Mar 6 2024

This just happened on our MX 100, and lasted about 15 minutes, blocking or dropping almost all DNS traffic to 8.8.8.8 and 1.1.1.1, which, of course, brought most internet and email connectivity to a standstill. Looking back through the last few weeks logs, this has been happening sporadicially for the past 30 days, but nothing like the volume of traffic flagged this morning. Source IP: <redacted>, Source Port: 51406, Destination IP: 8.8.8.8 « hide Destination Port 53 Protocol UDP Block Type DNS NBAR ID 67 Classification eDonkey Layer 7 firewall rule Deny MX 18.107.2

Meraki

Community

About Iansays1

Iansays1

Community Record

Badges

Re: Replacing MX 100 + Stacked Switches with MX 105 + 3 NEW stacked switche...

Re: Replacing MX 100 + Stacked Switches with MX 105 + 3 NEW stacked switche...

Re: Replacing MX 100 + Stacked Switches with MX 105 + 3 NEW stacked switche...

Replacing MX 100 + Stacked Switches with MX 105 + 3 NEW stacked switches

Re: Email and DNS Traffic Blocked as eDonkey Traffic

Re: Replacing MX 100 + Stacked Switches with MX 105 + 3 NEW stacked switche...