AFDX SNMP Get-Next Fix
The project page will track all necessary activity associated with implementing the AFDX SNMP Get-Next fix. PCR 5252.
Description
SNMP GET-NEXT requests that are traversing the MIB tree in the area of AFDXRedundancy.VLPortIndex will return an incorrect 'next' port value when the 'next' port requires more than 2 bytes in the ASN notation.
Specific test case: A400M ISU configuration: SNMP GET-NEXT request for "enterprises.11348.1.1.3.2.1.1.1.15068" incorrectly returns "enterprises.11348.1.1.3.2.1.1.1.8466"
The correct 'next' port should be 24850 which would require 3 bytes in ASN. If you convert 24850 to ASN and forget to add the 3rd byte you will end up with port 8466, so this seems to indicate that there is a problem converting the larger port numbers to ASN.
News
- 2009-01-26: Tom Taranowski updated SAS about this limitation.
- 2009-02-25: ADIRU requests quote for this fix.
Searchable Mail List
- AFDX Users Mail List: Click to subscribe or change your subscription options
- Search the AFDX Users Mail List: Click to search the list for specific messages/topics
Tasks
Initial Budget:
YTD:
Current ETC:
Current EAC:
| Milestones | Due Date | Estimated Delivery | Delivered | Percentage Complete |
|---|---|---|---|---|
| Certification Candidate: Version 4.5.0 | 100% | |||
| Verification Complete | 27-MAR-2007 | 26-APR-2007 | 26-APR-2007 | 100% |
| Analysis Complete | Never* | Never* | 8% |
*This analysis was not deemed necessary to meet any DO-178B objectives. Therefore, it was not/will not be performed.
Note: Unless noted otherwise, all estimates below are in terms of effort hours.
Infrastructure Update
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|
Certification Candidate
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 2.1 Requirement Rework | None | 4 | 4 | 0 | 4 | ||
| 2.2 Code development | 2.1 | None | 4 | 4 | 0 | 4 | |
| 2.3 Ad-hoc Test development | 2.1 | None | 16 | 16 | 0 | 16 | |
| 2.4 Certification Candidate - Release | 2.3 | None | 8 | 8 | 0 | 8 | |
| Totals | 32 | 32 | 0 | 32 | |||
Verification
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 3.1 Energize Review Status Files | 2.4 | None | 8 | 8 | 0 | 8 | |
| 3.2 Requirements review | 2.1, 3.1 | None | 8 | 8 | 0 | 8 | |
| 3.3 Test Case Development | 2.1 | None | 16 | 16 | 0 | 16 | |
| 3.4 Test Procedure Development | 2.1, 2.3 | None | 24 | 24 | 0 | 24 | |
| 3.6 Code review | 3.2 | None | 8 | 8 | 0 | 8 | |
| 3.7 Test Case Review | 3.2, 3.3 | None | 8 | 8 | 0 | 8 | |
| 3.8 Test Procedure Review | 3.4, 3.7 | None | 16 | 16 | 0 | 16 | |
| 3.9 Software life cycle audit | 3.8 | None | 16 | 16 | 0 | 16 | |
| 3.10 Requirements coverage analysis | 3.6, 3.7 | None | 8 | 8 | 0 | 8 | |
| 3.11 Conformity inspection - SQA build Witness | 3.8, 3.10 | l | None | 8 | 8 | 0 | 8 |
| 3.12 SCAT/ABC qualification | 3.8 | None | 8 | 8 | 0 | 8 | |
| 3.13 Integration review | 3.11, 3.12 | None | 8 | 8 | 0 | 8 | |
| 3.14 Run for score, including SQA witnessing, and test results review | 3.13 | None | 8 | 8 | 0 | 8 | |
| 3.15 Structural coverage analysis | 3.14 | None | 8 | 8 | 0 | 8 | |
| 3.16 Verification audit | 3.15 | None | 16 | 16 | 0 | 16 | |
| 3.17 Certification documents: SAS, SLCECI, SCI | 3.15 | None | 40 | 40 | 0 | 40 | |
| 3.18 Population of certification archive (PCA) | 3.17 | None | 8 | 8 | 0 | 8 | |
| 3.19 Software conformity audit | 3.18 | None | 8 | 8 | 0 | 8 | |
| Totals | 224 | 224 | 0 | 224 | |||
Analysis
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 4.1 Analyze Implementation (per the above) | 2.2 | Larson | 80 | 80 | 8 | 72 | |
| 4.2 Document Discoveries | 4.1 | Larson | 16 | 16 | 0 | 16 | |
| Totals | 96 | 96 | 8 | 88 | |||
Risks
None currently.
