You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/etc/frr/bgpd.conf will have a router bgp line, which is not valid
supporting "DEVICE_METADATA" - "bgp_asn" with a value "None"
The case appears if /etc/sonic/minigraph.xml miss
/etc/frr/bgpd.conf will have a router bgp None line, which is not valid
supporting "DEVICE_METADATA" - "bgp_asn" with a int value
The normal L3 switch config
So right now, we need to fix sonic-device_metadata.yang to support above behaviors. In future, ideally we need to improve the first 2 cases, let /etc/frr/bgpd.conf handles them gracefully.
…sing. (#12588)
bgpd.main.conf.j2: bugfix-9739
* Update bgpd.main.conf.j2 to gracefully handle the bgp configuration cases for when 'bgp_asn' is set to 'None', 'Null', or missing.
How I did it
Include a conditional statement to avoid configuring bgp in FRR when 'bgp_asn' is missing or set to 'None' or 'Null'
How to verify it
Configure 'bgp_asn' as 'None', 'Null' or have it missing from configurations and verify that /etc/frr/bgpd.conf does not have invalid bgp configurations like 'router bgp None'
Description for the changelog
Update bgpd.main.conf.j2 to gracefully handle the bgp configuration cases for when 'bgp_asn' is set to 'None', 'Null', or missing for bugfix 9739.
Signed-off-by: [email protected]
My understanding of currently SONiC behaviors:
router bgp
line, which is not validrouter bgp None
line, which is not validSo right now, we need to fix sonic-device_metadata.yang to support above behaviors. In future, ideally we need to improve the first 2 cases, let /etc/frr/bgpd.conf handles them gracefully.
Originally posted by @qiluo-msft in #9640 (comment)
The text was updated successfully, but these errors were encountered: