[OVSDB-319] Mcast entries not added correctly Created: 14/Mar/16  Updated: 30/Oct/17  Resolved: 31/Mar/16

Status: Resolved
Project: ovsdb
Component/s: Southbound.hw_vtep
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Vishal Thapar Assignee: Vishal Thapar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Duplicate
is duplicated by OVSDB-320 remote mcast mac table entry update i... Resolved
is duplicated by OVSDB-321 remote mcast mac entry add operation ... Resolved
External issue ID: 5514

 Description   

There are two issues with mcast entries:
1. While updating we match on destination mac, this should be changed to uuid.
2. For unknown-dst entries in different network segments, mac will be same but VNI [Logical switch] will be different.

Solution is to use logical-switch-ref also as a key and use uuid to match mac entry when doing an update.

 Comments   
Comment by Vishal Thapar [ 31/Mar/16 ]

Gerrit: https://git.opendaylight.org/gerrit/36201

Generated at Wed Feb 07 20:36:05 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.