-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v1.3
-
Component/s: Deprecated - vOLTHA Core
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:VOLTHA 1.3 Sprint 3, VOLTHA 1.3 Sprint 4
The decode of a MIB Upload Request frame fails validation if the command-sequence-number is greater than 255. This is due to decode using rules for the ONU Data ME that is only defined with a mib_data_sync attribute that is a byte.
It is assumed that the Get All Alarms Next response will have a similar issue.
The Scapy definition needs to be extended (if it is possible) to detect the response type or the data checking/constraints for responses needs to be relaxed.
-
-
- This is a good canidate for a unit test case
-
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 8898,3 | VOL-649: Support MIB Upload Next with sequence numbers > 255 Corrected parameter range typo in OntDataFrame documentation | master | voltha | Status: MERGED | +2 | +1 |