Once the static routes have been added to the MX, DHCP scopes will need to be configured for each VLAN.

Those routes can be configured as follows:

The firewall needs be configured with static routes (under Configure > Addressing & VLANs), so any inbound traffic destined for the voice or data VLANs will go through the routing interface of the switch.

Now that the distribution switch is performing inter-VLAN routing for the network, we will need to perform some additional configuration steps on the firewall to allow full network connectivity:

Once this has been done, we can remove the legacy router from the network, as all routing functionality has been delegated to the distribution switch. The LAN port on the firewall and the uplink port on the distribution switch also need to have similar settings, likely a trunk port, though configuration may vary as there is only one VLAN between the two devices. Please see the Related KBs section for more details on how to configure switch ports. The access switch will also need to be configured appropriately to place client traffic in the voice and data VLANs. The uplink port on the access switch should be configured identically, otherwise VLAN mismatches will result.

Under Configure > Switch ports select the port that will be connected to the access switch, and update the following settings: To allow for the downstream access switch and connected clients to take advantage of the routed interfaces, the switch port going to the access switch will need to be configured as a trunk to allow for both VLANs to traverse it.

Default gateway command vpcs in gns3