Hi everyone, I've inherited full responsibility for a network I didn't set up. I know that the MX products don't support LAG, this has resulted in a configuration in the environment I've inherited that seems like it might be wrong to me. Relevant to my question, we have two MX250s in an HA arrangement and then two MS425-16 core switches that are in a stack configuration. Basically, my predecessor, upon realizing that the MX doesn't support LAG, decided to make a single all-VLAN trunk link from each of the MX250 units in our HA set up to one of the MS425-16 core switches (MX1 <-> MS1 and MX2 <-> MS2). For redundancy, his solution was to access links from each MX to each switch (MX1 <-> MS1 + MX1 <-> MS2) for each VLAN. This is the current MX VLAN setting. I've blocked out VLAN names so as not to distract. Looking at one of the core switches, I see that the access ports are a mix of forwarding and blocking. This tells me that the configuration is at least sort of working as intended. But I've added new VLANs to the all-VLAN trunk in the past and they don't work until I add an access link as well, which doesn't seem right to me. So, I'm wondering if this practice of combining access and trunk links for redundancy on an MX is recommended or not, because it seems very unconventional to me. How do people usually handle the lack of LAG support on the MX products? I appreciate any guidance with respect to cleaning this if up if necessary. Thanks you.
... View more