[R5.0-30]- hold flow for icmp v6 error case with Fat flow port 0 and ignore source

Bug #1766559 reported by alok kumar
6
This bug affects 1 person
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:Port/Destination:Port Proto(V)
-----------------------------------------------------------------------------------
    53332<=>213736 :::0 17 (2)
                         1::3:0
(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)
                         :::0
(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)
                         2::2:0
(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)
                         :::0
(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)
                         :::0
(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.

Tags: vrouter
alok kumar (kalok)
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
Revision history for this message
Ashok Singh (ashoksr) wrote :

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.

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/44836
Submitter: Nagendra E S (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R5.0

Review in progress for https://review.opencontrail.org/44994
Submitter: Nagendra E S (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/44836
Submitter: Nagendra E S (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R5.0

Review in progress for https://review.opencontrail.org/44994
Submitter: Nagendra E S (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/44994
Committed: http://github.com/Juniper/contrail-vrouter/commit/ff467f01e9b626e67063ed006f7ceb099be35e83
Submitter: Zuul v3 CI (<email address hidden>)
Branch: R5.0

commit ff467f01e9b626e67063ed006f7ceb099be35e83
Author: Nagendra E S <email address hidden>
Date: Mon Jul 23 09:14:55 2018 +0530

Fix for flow creation for IPv6

When VN configured with fat flow and icmp6 error is
generated, flows are not created on the destination VN.

Change-Id: I203d80cfdc2625f463c19359a40a9f166d47ba20
Partial-Bug: #1766559

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/44836
Committed: http://github.com/Juniper/contrail-vrouter/commit/b88acfc6bf93e5dba3b165ae09e891a3521ba0d2
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit b88acfc6bf93e5dba3b165ae09e891a3521ba0d2
Author: Nagendra E S <email address hidden>
Date: Mon Jul 23 09:14:55 2018 +0530

Fix for flow creation for IPv6

When VN configured with fat flow and icmp6 error is
generated, flows are not created on the destination VN.

Change-Id: I203d80cfdc2625f463c19359a40a9f166d47ba20
Partial-Bug: #1766559

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.