Looking for input and best practice. How I was trained, I was always told when you can avoid Trunks to firewall/router, avoid trunks to firewall/router.
Example.
Network Equipment
1MX, 1 MS, and 1 AP.
4 Vlans, (2- Production VLAN, 15- VoIP VLAN, 90-Other VLAN, 100-being a place holder for spare subnet as I shrunk one subnet)
I have 3 lines coming from Switch to MX.
1 Trunk for Management traffic and VLAN 2, one access port for VlAN 15, and one access port for 90.
I was wondering if this is best practice or if I should trunk them all together. Idea behind this is each VLAN has full port speed back to firewall/router so in theory there could be more performance then if all networks are sharing one port. Open to suggestions. Many of our sites have <15 people so its not a concern at the moment really, but still something I always wondered about.
I'm not aware of any reason not to trunk, other than, as you stated, throughput.
Most networks I've built in the past would have an L3 aggregation switch terminating the user/server subnets, and then route on to a FW or router as required, but in smaller networks as you're mentioning I would have no problem just trunking that up to an L3 device. A lot of what I'm doing in my current role is using that design.
>Is there any benefit to going with a single trunk?
Less cabling. Less ports used. Less configuration. Easier to understand when try to work out a fault.