Hi @GIdenJoe Thanks for your reply, this is exactly the type of info I was after. It makes sense to me and I think the 16 VLAN limitation won't be an issue. - I create the MS management VLAN that goes L2 through the core stack so the gateway is the MX. This way you can have the core switches and the access switches is one management VLAN. Understood - Then I create the /30 transit VLAN between MX and core stack. This is done both on the MX addressing and vlans page and the switch routing and dhcp page. Understood - Then I create the static routes on the MX pointing to the core stack IP each individually because you need those individual subnets to create a DHCP scope for in the MX. This is the piece of info I was missing, I see that for every static route you add (just like any VLAN you add) on the MX, you then have an appropriate DHCP scope added and configurable in the DHCP page. - Then I create the dhcp scopes on the MX DHCP page. Understood - Then I create the individual VLAN interfaces with DHCP relay pointing to the MX /30 subnet IP address. Understood Thanks very much. Jason
... View more
