-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Medium
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.9, VOLTHA v2.10
-
Component/s: openolt-adapter, openolt-agent, openonu-adapter
-
Labels:
-
Story Points:5
-
Epic Link:
-
Sprint:VOLTHA 2.10 - Sprint 2, VOLTHA 2.10 - Sprint 3
When using BAL3.10.2.2 with voltha-2.9 release candidate software and workflow that uses multiple gem ports per TCONT (DT / ATT) and Radisys OLTs the packets arrive on the wrong gem port in the upstream.
From the configuration perspective everything looks fine on the OLTs and the ONUs, so it is not clear how the ONU sends packets on the wrong gem port.
When using voltha-2.9 release candidate software with BAL3.4.9.9 debian package this issue is not found, so it seems to indicate that for some reason the BAL3.10 may be playing a role here.
A separate CSP ticket will be raised on Broadcom to debug further.