Skip to content

[multi-asic] fix network command for internal ipv6 loopback #7878

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

Merged
merged 1 commit into from
Jun 24, 2021

Conversation

arlakshm
Copy link
Contributor

Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan [email protected]

Why I did it

In the multi asic platforms all the ASIC are advertising the same IPv6 /64 network from Loopback4096.
Therefore, the IPv6 loopback address of backend asic is not learnt on the frontend asic.
Change this to advertise the Loopback4096 address as /128

How I did it

Change the bgpd.conf.main.conf.j2 template file.

How to verify it

Verify the route to Loopback4096 address of backend asic is programmed on the Frontend linecard

  • Loopback4096 ipv6 address on backend asics
admin@sonic:~$ show ipv6 int -d all -n asic4 | grep -i loopback4096
Loopback4096               2603:10e2:400::4/128                       up/up         N/A             N/A
                           fe80::fc68:56ff:fe3a:7f37%Loopback4096/64                N/A             N/A
admin@sonic:~$ show ipv6 int -d all -n asic5 | grep -i loopback4096
Loopback4096               2603:10e2:400::5/128                       up/up         N/A             N/A
                           fe80::705c:bbff:fec5:1c36%Loopback4096/64                N/A             N/A
admin@sonic:~$

Verify the route is programmed in the hardware for these addresses

admin@sonic:~$ bcmcmd -n 0 "l3 ip6route show" | grep 2603:10e2:0400:0000:0000:0000:0000
27    0        2603:10e2:0400:0000:0000:0000:0000:0000/128  00:00:00:00:00:00 100003    0     0     0    1 n
65565 0        2603:10e2:0400:0000:0000:0000:0000:0002/128  00:00:00:00:00:00 200258    0     0     0    0 n      (ECMP)
30    0        2603:10e2:0400:0000:0000:0000:0000:0003/128  00:00:00:00:00:00 200258    0     0     0    0 n      (ECMP)
65566 0        2603:10e2:0400:0000:0000:0000:0000:0005/128  00:00:00:00:00:00 100008    0     0     0    0 n
31    0        2603:10e2:0400:0000:0000:0000:0000:0001/128  00:00:00:00:00:00 200258    0     0     0    0 n      (ECMP)
65567 0        2603:10e2:0400:0000:0000:0000:0000:0004/128  00:00:00:00:00:00 100009    0     0     0    0 n

Which release branch to backport (provide reason below if selected)

  • 201811
  • [x ] 201911
  • [ x] 202006
  • [x ] 202012

Description for the changelog

A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <[email protected]>
@abdosi
Copy link
Contributor

abdosi commented Jun 15, 2021

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@arlakshm
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@arlakshm
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@arlakshm
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@arlakshm
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@arlakshm arlakshm merged commit ef67ba5 into sonic-net:master Jun 24, 2021
@arlakshm arlakshm deleted the masic_ipv6_lpbk_fix branch June 24, 2021 19:02
carl-nokia pushed a commit to carl-nokia/sonic-buildimage that referenced this pull request Aug 7, 2021
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <[email protected]>
In the multi asic platforms all the ASIC are advertising the same IPv6 /64 network from Loopback4096.
Therefore, the IPv6 loopback address of backend asic is not learnt on the frontend asic.
Change the bgpd.conf.main.conf.j2 template file to advertise the Loopback4096 ipv6 address as /128
qiluo-msft pushed a commit that referenced this pull request Feb 9, 2022
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <[email protected]>
In the multi asic platforms all the ASIC are advertising the same IPv6 /64 network from Loopback4096.
Therefore, the IPv6 loopback address of backend asic is not learnt on the frontend asic.
Change the bgpd.conf.main.conf.j2 template file to advertise the Loopback4096 ipv6 address as /128
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants