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
The issue occurred during HA-Flow reroute action on hardware env(NS switch), passed on virtual lab. HaFlowRerouteSpec: TC Valid HA-flow can be rerouted.
After HA-Flow rerouting validate all involved switches:
The discrepancy occurred on the shared NS switch:
After additional investigation, it was noticed that these excess rules are s42-related. If we use the WB switch instead of the NS switch as a shared endpoint, there is no discrepancy after the ha-flow reroute. initial ha-flow path(switch Triplet: [NS sw1] - NS sw2 - NS sw3): sub-flow1: NS sw1 -> NS sw2; sub-flow2: NS sw1 -> sw3
ha-flow path after reroute: sub-flow1: NS sw1 -> NS sw3 -> NS sw2; sub-flow2: NS sw1 -> sw3 = shared ep is sw3
Excess rules details:
The issue occurred during HA-Flow reroute action on hardware env(NS switch), passed on virtual lab.
HaFlowRerouteSpec
: TCValid HA-flow can be rerouted
.After HA-Flow rerouting validate all involved switches:
The discrepancy occurred on the shared NS switch:
haFlowHistoryReroute.json
The text was updated successfully, but these errors were encountered: