[chassis][multi-asic]: Add support for vendor LC ip range for macvlan ip#22008
Merged
yxieca merged 6 commits intosonic-net:masterfrom Mar 25, 2025
Merged
[chassis][multi-asic]: Add support for vendor LC ip range for macvlan ip#22008yxieca merged 6 commits intosonic-net:masterfrom
yxieca merged 6 commits intosonic-net:masterfrom
Conversation
Contributor
Author
|
Hi @abdosi , for your viz. Thanks |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
abdosi
previously approved these changes
Mar 12, 2025
judyjoseph
reviewed
Mar 12, 2025
Contributor
|
@anamehra can we please check failure? |
Contributor
|
@abdosi , can we please file ado? thanks. |
Contributor
Author
|
@yejianquan , for your viz. |
Contributor
Author
Contributor
|
There's a known issue and has been discussed in Elastictest group chat. |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
10 tasks
Contributor
Author
|
PR for 202405 sonic-buildimage-msft |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
Cherry-pick PR to 202411: #22125 |
patrickmacarthur
pushed a commit
to patrickmacarthur/sonic-buildimage
that referenced
this pull request
Aug 6, 2025
… ip (sonic-net#22008) Signed-off-by: Anand Mehra anamehra@cisco.com
patrickmacarthur
pushed a commit
to patrickmacarthur/sonic-buildimage
that referenced
this pull request
Aug 6, 2025
[chassis][multi-asic]: Add support for vendor LC ip range for macvlan ip (sonic-net#22008) Signed-off-by: Anand Mehra anamehra@cisco.com Why I did it As per current design, macvlan IP start with an offset of 10 from miplane Ip subnet base ip on a namespace. In some platforms this may cause conflict if the LC midplane ip for any slot falls in that range. The IP conflict cause midplane traffic loss. In Cisco Chassis, macvlan IP may conflict with LC midplane IP range. This conflict causes midplane traffic loss for conflicting ip and affects any LC namespace transaction with Supervisor. To prevent any conflict, Venddor may provide an offset to be used to generate macvlan IP address to prevent any conflict with midplane IP address. Work item tracking Microsoft ADO (31798758): How I did it Added an ip_offset value which Vendor may provide based on their midplane ip range to generate safe IP address for macvlan in namespace. The lc_ip_offset offset needs to be set in /usr/share/sonic/device//chassisdb.conf file for the LC where an offset is required. cat chassisdb.conf chassis_db_address=127.0.0.3 midplane_subnet=127.0.0.0/16 lc_ip_offset=100 How to verify it After boot, check eth1 IP address in namespaces. The IP addresses should not conflict with any expected LC eth1-midplane IP or any other IP in the system. co-authorized by: jianquanye@microsoft.com
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: Anand Mehra anamehra@cisco.com
Why I did it
As per current design, macvlan IP start with an offset of 10 from miplane Ip subnet base ip on a namespace.
In some platforms this may cause conflict if the LC midplane ip for any slot falls in that range. The IP conflict cause midplane traffic loss.
In Cisco Chassis, macvlan IP may conflict with LC midplane IP range. This conflict causes midplane traffic loss for conflicting ip and affects any LC namespace transaction with Supervisor.
To prevent any conflict, Venddor may provide an offset to be used to generate macvlan IP address to prevent any conflict with midplane IP address.
Work item tracking
How I did it
Added an ip_offset value which Vendor may provide based on their midplane ip range to generate safe IP address for macvlan in namespace.
The lc_ip_offset offset needs to be set in /usr/share/sonic/device//chassisdb.conf file for the LC where an offset is required.
How to verify it
After boot, check eth1 IP address in namespaces. The IP addresses should not conflict with any expected LC eth1-midplane IP or any other IP in the system.
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)