Good morning y’all. Thank you in advance for any knowledge base on this subject. I’ll try to keep it brief.    Preface:  these are all new deployments, with new out-of-the-box devices.     I have a circuit on single port, offering a /29 LAN block to feed the WAN1 port for a pair MX84’s.  Some locations have a catalyst 3650 and some have MS250’s for switching.    On both switching platforms forms I would run a single copper from router to switch Port 52 on trunk: native VLAN671.  I would run copper from switch ports 47-48 to WAN1 on each MX via Access: VLAN671.  My production VLANS and VLAN 671 terminate on the MX’sin warm-spare mode.  I now runcopper up from MX ports LAN3 to switch ports 45-46 via Trunk: Native VLAN 1, allowed: 300,310,320 (production only - 671 is pruned). See attachment for visual representation.   Using the catalyst for switching this works efficiently and effectively. Exactly as intended.    Using the MS 250 for switching this does not exactly. I have some packet loss I can’t run down… I have a Shortell void switch that seems to be unable to keep a connection… If I ping using specific packet counts I can hit everything in the legacy network at 1373, but no higher than.  Switch MTU is default... I can hit all the way up to 1500 and above from the catalyst architecture. I suspect I have an issue somewhere.     I know the MS switching likes to use defined uplinks, the MS is currently showing uplink on switch ports 45–46, I should think it should be showing on 52 as that is the genuine Uplink to the router.   I did use 45 for initial switch to router cloud connectivity... perhaps I need a factory reset using 52 has the initial athlete, then build out my aggregation?    If somebody has some insight I don’t. This is my first time using MS switching platform. Feel free to ask questions for additional information.            ... View more