Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
while integrating opensync 6.2 with BCM 5.04.04p3 it was observed that the extender devices could not associate with the onboard AP.
Further analysis revealed that the SDK was set to the default value for BSS (bssmax = 8). Since opensync was trying to bring up interfaces ranging from wlx.1 to wlx.7 by default, there was some conflict that caused the failure in the leaf association.
The following fix addresses the issue if the SDK comes with default values, the leaf will still be able to associate with the GW and bring up the APs. The VIFs wlx.1 to wlx.6 will be brought up in this case.
This can help with the normal operation of the leaf device. However, it will be better to request the ODM for this requirement (bssmax at least 10) in intake form / TRD when they approach for Integration/Certification with the plume team.