-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Multi-ASIC]:Update the template to add ipinip entry for Loopback4096 #5235
Conversation
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <arlakshm@microsoft.com>
@@ -2,12 +2,13 @@ | |||
{% set ipv6_addresses = [] %} | |||
{% set ipv4_loopback_addresses = [] %} | |||
{% set ipv6_loopback_addresses = [] %} | |||
{% set loopback_intf_names = ['Loopback0', 'Loopback4096'] %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this interface should be in if multi_asic()
case right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add check to to add Loopback4096 is the device is either Frontend or Backend asic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor suggestion.. we can have it as below in case if we plan to add more loopbacks in future
set loopback_intf_names = ['Loopback0']
if FrontEnd or BackEnd
set loopback_intf_names = loopback_intf_names.append('Loopback4096')
{%- set ipv4_addresses = ipv4_addresses.append(prefix) %} | ||
{%- set ipv4_loopback_addresses = ipv4_loopback_addresses.append(prefix) %} | ||
{%- endif %} | ||
{%- if prefix | ipv6 and name == 'Loopback0' %} | ||
{%- if prefix | ipv6 and name in loopback_intf_names %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like an extra space before name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in latest commit
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <arlakshm@microsoft.com>
restest vsimage please |
2 similar comments
restest vsimage please |
restest vsimage please |
restest vsimage please |
retest vsimage please |
6 similar comments
retest vsimage please |
retest vsimage please |
retest vsimage please |
retest vsimage please |
retest vsimage please |
retest vsimage please |
…#5235) Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <arlakshm@microsoft.com> The following changes are done. - Multi asic platform have 2 Loopback interfaces, Loopback0 and Loopback4096. IPinIP decap entries need to be added for both of them. Update the ipinip.json.j2 template to add decap entries for Loopback4096. - Add corressponding unit test
…sonic-net#5235) Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <arlakshm@microsoft.com> The following changes are done. - Multi asic platform have 2 Loopback interfaces, Loopback0 and Loopback4096. IPinIP decap entries need to be added for both of them. Update the ipinip.json.j2 template to add decap entries for Loopback4096. - Add corressponding unit test
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan arlakshm@microsoft.com
- Why I did it
Multi asic platform have 2 Loopback interfaces, Loopback0 and Loopback4096. IPinIP decap entries need to be added for both of them.
- How I did it
Update the ipinip.json.j2 template to add decap entries for Loopback4096.
Add corressponding unit test
- How to verify it
Verify the ipinip.json is generated properly.
- Which release branch to backport (provide reason below if selected)
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)