flows marked for Hold when a route moves from non-ecmp to ecmp
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.21.x |
Fix Committed
|
Undecided
|
Naveen N | |||
R3.1 |
Invalid
|
Undecided
|
Naveen N | |||
Trunk |
Invalid
|
Undecided
|
Naveen N |
Bug Description
R2.21.2 build 41 Ubuntu 14.04 Juno
This is with vrouter having changes to do ecmp nh update.
Below 99780 and 215800 were active tcp flows
Route to 10.204.217.158 at this moment was a non-ecmp flow.
A change was done in the physical network so that it becomes a ECMP route.
A few older flows were marked for Hold as shown in the second flow -l output.
Index Source:Port Destination:Port Proto(V)
-------
34684<=>99176 192.168.192.1:60955 169.254.0.3:22 6 (0->1)
(K(nh):5, Action:N(SD), S(nh):5, Statistics:
99176<=>34684 10.204.221.179:22 169.254.
(K(nh):14, Action:N(SD), S(nh):14, Statistics:
99780 10.204.
(K(nh):14, Action:F, S(nh):14, Statistics:
176396 10.204.
(K(nh):14, Action:F, S(nh):14, Statistics:
215800 10.204.217.158:80 10.204.
(K(nh):14, Action:F, S(nh):22, Statistics:
356004 10.204.
(K(nh):14, Action:F, S(nh):14, Statistics:
370228 10.204.217.158:80 10.204.
(K(nh):14, Action:F, S(nh):22, Statistics:
495972 10.204.217.158:80 10.204.
(K(nh):14, Action:F, S(nh):22, Statistics:
----------------
34684<=>99176 192.168.192.1:60955 169.254.0.3:22 6 (0->1)
(K(nh):5, Action:N(SD), S(nh):5, Statistics:
99176<=>34684 10.204.221.179:22 169.254.
(K(nh):14, Action:N(SD), S(nh):14, Statistics:
99780<=>215800 10.204.
(K(nh):14, Action:F, E:1, S(nh):14, Statistics:
176396 10.204.
(K(nh):14, Action:F, S(nh):14, Statistics:
215800<=>99780 10.204.217.158:80 10.204.
(K(nh):14, Action:F, S(nh):23, Statistics:
356004 10.204.
(K(nh):14, Action:F, S(nh):14, Statistics:
370228 10.204.217.158:80 10.204.
(K(nh):14, Action:H, S(nh):23, Statistics:
495972 10.204.217.158:80 10.204.
(K(nh):14, Action:H, S(nh):23, Statistics:
Changed in juniperopenstack: | |
milestone: | none → r3.1.0.0-fcs |
Fixed committed with bug 1573265