hi @PhilipDAth,   thanks for your reply on this post! ok... but the local DHCP-Server on the MX is NO option in the project I‘m currently working on! Unfortunatly another reason more (in the meantime they‘re many...) why I’ve to think twice if the MX is really a security component to compete with other vendors on the market! 🤨     ... View more

so it isn‘t necessary to enable CoA for the dynamic vlan assignment to work, correct? if so, why does this option than exist and where/when should or could it be used? ... View more

so the tie-breaker is always the lowest device MAC-Address which determines the Stack-Master and the device-type (e.g. stacking MS225 and MS210) does‘nt matter or influence the election also? ... View more

I`ve just looked at the configuration on the bottom switch again and I`ve to say that I made a mistake in the sketch! the port (towards where RSTP is disabled) is an access port untagged in vlan 1 ... View more

someone any ideas on that? ... View more

Hi, @UCcert thank you for your reply on this topic! But what I don't understand is that RSTP is disabled on the port and the connected device speaks STP ... so I don't understand why it works without problems / loop at all! ... View more

  @Bruce wrote: @whistleblower personally I’d go with plan-1. For a network this size I’d try and keep dynamic routing out of it and if you can achieve your high availability goals using LACP then that’s likely to give you less problems. Dynamic routing has its place - where you expect to add or remove subnets and that would cause a lot of changes to static routes - but I probably  wouldn’t use it here. . OK, but there are no technical advantages or disadvantages, at least I don't have any obvious ones in mind...  🤔     You’ll probably want to allow for a management VLAN too, which is the one the Meraki switches internal management interface will use to connect to the Dashboard. It is highly recommended (basically don’t do it) that the management interface VLAN for a switch doesn’t have a SVI on the switch itself. So your management VLAN will likely terminate on a router or firewall facing the internet, and would be a second VLAN between the head office and data centre - another reason to use plan-1 (unless you have internet access from both locations). that`s a really good and of course important point - thanks for the hint! 😅 Hm, but then I´ve to change the switchports from Access-Ports "untagged" to 802.1q Trunking... allowing the so called "transfer-lan" for Routing and as well the Layer2 Vlan for Management as well as the Native-Vlan1 for RSTP and so on... ... View more

I can´t find the Heat-Map with the Time Lapse anymore? Is this function no longer available in the dashboard? ... View more

... OK guys, I think I`ve got it - I looked also over some official documents for Cisco Enterprise and I think I understood the basics about the Hashing topic now 🙂 - thank you very much!   may I ask you if you can give me your assessment of the planned design as well? A MS350 Pair (physical stacked in the HQ) and a MS425 Pair (Flexible Stack, one of each devices in two different DataCenters interconnected with DarkFiber) should use both physical Lines at the same time (= Load-Balancing) for transfering IP-Traffic between the locations! please have a look at the attached plans, what would you say is the better solution from your side of expirience? Please notice, for Plan-02 I´d like to use OSPF as dynamic Routing Protocol!   Plan-01     Plan-02       ... View more

Hi Bruce,   first - thanks for your response, I appreciate it very much!   @Bruce wrote: The Meraki devices don’t have a Layer 3 LAG, in the same way you can’t make a port a Layer 3 interface. The closest you can get is create an SVI (Layer 3 interface) for a specific VLAN on the switch at each end, and the use a LAG which contains only that VLAN.  maybe you or someone can point out, what would be the difference (advantage/disatvantage) between that suggested solution and a "classic" Layer3 LAG? Probably a better design would be to use no LAG and instead dynamic routing /w the same metric over both links?   The Meraki LAG - which uses LACP - makes use of the IP addresses, MAC and port in its hashing algorithm to determine the member to use, and it not configurable. Please see here, https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Link_Aggregation_and_Load_Balancing. what does that mean exactly - so would e.g. a Server with the IP-Address 192.168.1.1, MAC: aaaa.aaaa.aaaa and Src. Port TCP-3389 always use the same link, without consindering the Destination Side?   ... View more

Hi,   @lomonaco wrote: But how can I specify, for example, that I want the TCP Port 80 and not the UDP Port 80 ? I know that I can include the port number (80,8080,123,53,etc) but I didn't see where I can specify the protocol (TCP/UDP) associated with the Port. any news about this requirment or suggestions whether/how this can be solved?   I`d also like to know if there is a possibility - to match both --> the source- and the destination network maybe with Src./Dst. Port in one rule? e.g. 192.168.1.0/24:80 --> 10.1.1.0/24:8080 ... View more