You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> [!NOTE]
> This is just @mkeeter's PR #2226, but rebased onto the latest
> `master`, since [it turns out we actually do need this][1]. I had
> wanted to just re-open Matt's original PR but [github would not let
> me do this for some kind of reason I really don't fully understand][2].
> Anyway, heeeeeere's Matt Keeeeeeeterrrr!!!
"Reverso" is a board with the same form factor as a Gimlet which loops
back the two backplane connectors.
In this configuration, packets leaving the VSC7448 destined for SP _i_
instead arrive at the peer Sidecar, appearing to have originated at SP
_i_.
In the unlocked VLAN configuration, this is a problem: packets can
arrive at one tech port and emerge from the other tech port, which
creates a routing loop. When this happens, our CM's network
unceremoniously turns off the offending network port, and we have to
manually get it re-enabled.
This PR adds a `VlanTargets` parameter to unlock-related code:
- `VlanTargets::EverySp` is our existing behavior, where the technician
port can communicate with every cubby
- `VlanTargets::ScrimletOnly` limits technician ports to only
communicate with Scrimlet cubbies, which are guaranteed to be populated
By preventing the technician port from talking to cubbies with Reverso
installed, we can avoid network loops.
The switch zone in the scrimlet can still communicate with every cubby;
indeed, this is how we expect to test connectivity with Reverso
installed.
[1]:
#2226 (comment)
[2]:
#2226 (comment)
Co-authored-by: Matt Keeter <matt@oxide.computer>
0 commit comments