[R5.0-30]- hold flow for icmp v6 error case with Fat flow port 0 and ignore source
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Fix Committed
|
High
|
Nagendra E S | |||
Trunk |
Fix Committed
|
High
|
Nagendra E S |
Bug Description
hold flow for ipv6 icmp error for udp port unreachable when Fat flow is with port 0 and ignore source.
Index Source:
-------
53332<=>213736 :::0 17 (2)
(Gen: 22, K(nh):19, Action:F, Flags:, QOS:-1, S(nh):19, Stats:0/0, SPort 50944,
TTL 0, Sinfo 0.0.0.0)
213736<=>53332 1::3:0 17 (2)
(Gen: 29, K(nh):19, Action:F, Flags:, QOS:-1, S(nh):27, Stats:1/77, SPort 51706,
TTL 0, Sinfo 10.204.217.102)
221460<=>311332 :::0 17 (2)
(Gen: 15, K(nh):19, Action:F, Flags:, QOS:-1, S(nh):19, Stats:30/2880,
SPort 50257, TTL 0, Sinfo 3.0.0.0)
311332<=>221460 2::2:0 17 (2)
(Gen: 15, K(nh):19, Action:F, Flags:, QOS:-1, S(nh):13, Stats:0/0, SPort 52098,
TTL 0, Sinfo 0.0.0.0)
351120 2::3:0 17 (2)
(Gen: 19, K(nh):19, Action:H, Flags:, QOS:-1, S(nh):0, Stats:2/278, SPort 0,
TTL 0, Sinfo 3.0.0.0)
sender VM: 1::3, destination VM: 2::3(this sends icmp error)
from 1::3, do nslookup to 2::3 on port 53.
Issue is only for ipv6 case with ignore source, with ignore destination this is working fine.
summary: |
- [R5.0-30]- hold flow for icmp v6 error case with port 0 and ignore - source + [R5.0-30]- hold flow for icmp v6 error case with Fat flow port 0 and + ignore source |
For V6, ICMP destination unreachable message the flow key computed by vrouter when fat-flow is configured is incorrect. Because of mismatch of flow keys between vrouter and agent, hold flow is getting created.