Summary
A shard's translation program attaches to a single named uplink. On a node with more than one fabric uplink, traffic arriving on any other uplink reaches no translation program and is forwarded untranslated rather than dropped or counted. The uSID decap hook on the same node already takes a list of interfaces; the shard takes one name.
Multi-homing a shard node therefore means pinning its traffic to the primary uplink with routing policy and accepting that the shard role degrades on failover instead of surviving it. The containerlab lab does exactly that for its one dual-homed compute node.
Outcome
A shard node with more than one fabric uplink translates on all of them, and losing an uplink does not silently stop translation.
Related to #458.
Summary
A shard's translation program attaches to a single named uplink. On a node with more than one fabric uplink, traffic arriving on any other uplink reaches no translation program and is forwarded untranslated rather than dropped or counted. The uSID decap hook on the same node already takes a list of interfaces; the shard takes one name.
Multi-homing a shard node therefore means pinning its traffic to the primary uplink with routing policy and accepting that the shard role degrades on failover instead of surviving it. The containerlab lab does exactly that for its one dual-homed compute node.
Outcome
A shard node with more than one fabric uplink translates on all of them, and losing an uplink does not silently stop translation.
Related to #458.