Open CLUDev opened 3 years ago
@pavel-shirshov, @arlakshm - Can you please look into this issue. Thanks!
@CLUDev - what's the image being used here, is it based on sonic community 201911 branch? Can you please attach "show tech" file as well?
Hi @CLUDev
Can you please copy 'show run' from both SONiC and other device here?
Thanks
@rlhui @pavel-shirshov Thank you for checking this issue! The previous scenario could not be reproduced, I've updated a reproducible scenario with configurations listed below.
Please find SONiC 201911 "show tech" and "show run all" output here show_run_output.txt sonic_dump_Maple-201911_20201214_063352_show_tech.tar.gz
I. Update IPV6 BGP Config of SONiC & Other device
== Other Device (using Quagga) ==
interface 0/32
no auto-negotiate
no fec
service-policy in RDMA
no shutdown
routing
ipv6 address 1111::1/64
ipv6 enable
exit
router bgp 700
bgp router-id 7.7.1.4
maximum-paths 4
network 192.168.71.1 mask 255.255.255.255
neighbor 1111::2 remote-as 222
address-family vpnv4 unicast
exit
address-family ipv6
network 2014:192:168:71::1/128
neighbor 1111::2 activate
exit
== SONiC 201911 (using FRR) ==
router bgp 222
bgp router-id 2.2.2.2
bgp log-neighbor-changes
no bgp default ipv4-unicast
bgp graceful-restart restart-time 240
bgp graceful-restart
bgp graceful-restart preserve-fw-state
bgp bestpath as-path multipath-relax
neighbor PEER_V4 peer-group
neighbor PEER_V4_INT peer-group
neighbor PEER_V6 peer-group
neighbor PEER_V6_INT peer-group
neighbor 1111::1 remote-as 700
neighbor 1111::1 peer-group PEER_V6
neighbor 1111::1 description Redwood2
neighbor 1111::1 timers 30 90
!
address-family ipv4 unicast
network 2.2.2.2/32
neighbor PEER_V4 soft-reconfiguration inbound
neighbor PEER_V4 route-map FROM_BGP_PEER_V4 in
neighbor PEER_V4 route-map TO_BGP_PEER_V4 out
neighbor PEER_V4_INT soft-reconfiguration inbound
neighbor PEER_V4_INT route-map FROM_BGP_PEER_V4 in
neighbor PEER_V4_INT route-map TO_BGP_PEER_V4 out
maximum-paths 64
exit-address-family
!
address-family ipv6 unicast
network 2020:2222::/64
neighbor PEER_V6 soft-reconfiguration inbound
neighbor PEER_V6 route-map FROM_BGP_PEER_V6 in
neighbor PEER_V6 route-map TO_BGP_PEER_V6 out
neighbor PEER_V6_INT soft-reconfiguration inbound
neighbor PEER_V6_INT route-map FROM_BGP_PEER_V6 in
neighbor PEER_V6_INT route-map TO_BGP_PEER_V6 out
neighbor 1111::1 activate
maximum-paths 64
exit-address-family
II. Check BGP Summary from SONiC 201911 Unable to establish IPv6 BGP with other device
root@Maple-201911:/home/admin# show ipv6 bgp summary
IPv6 Unicast Summary:
BGP router identifier 2.2.2.2, local AS number 222 vrf-id 0
BGP table version 26261
RIB entries 1, using 184 bytes of memory
Peers 1, using 20 KiB of memory
Peer groups 4, using 256 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName
1111::1 4 700 6121 6067 0 0 0 00:00:00 Idle Redwood2
Total number of neighbors 1
root@Maple-201911:/home/admin# show ipv6 bgp summary
IPv6 Unicast Summary:
BGP router identifier 2.2.2.2, local AS number 222 vrf-id 0
BGP table version 26261
RIB entries 1, using 184 bytes of memory
Peers 1, using 20 KiB of memory
Peer groups 4, using 256 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName
1111::1 4 700 6121 6068 0 0 0 00:00:02 Active Redwood2
Total number of neighbors 1
root@Maple-201911:/home/admin# show ipv6 bgp summary
IPv6 Unicast Summary:
BGP router identifier 2.2.2.2, local AS number 222 vrf-id 0
BGP table version 26261
RIB entries 1, using 184 bytes of memory
Peers 1, using 20 KiB of memory
Peer groups 4, using 256 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName
1111::1 4 700 6123 6070 0 0 0 00:00:00 0 Redwood2
Total number of neighbors 1
root@Maple-201911:/home/admin# show ipv6 bgp summary
IPv6 Unicast Summary:
BGP router identifier 2.2.2.2, local AS number 222 vrf-id 0
BGP table version 26287
RIB entries 1, using 184 bytes of memory
Peers 1, using 20 KiB of memory
Peer groups 4, using 256 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName
1111::1 4 700 6127 6073 0 0 0 00:00:01 Idle Redwood2
Total number of neighbors 1
@pavel-shirshov Any comments would be highly appreciated!
Description
Switch is unable to update its BGP routes to peer if its peer does not use FRR to config IPv6 BGP.
Steps to reproduce the issue:
Config IPv6 BGP on DUT_FRR (ex. use 201911 branch)
router bgp 901 bgp router-id 192.168.91.1 neighbor 2222::2 remote-as 222 neighbor 2222::2 timers 30 90 address-family ipv6 unicast network 2014:192:168:91::1/128 neighbor 2222::2 activate
Config IPv6 BGP on DUT_Quagga (ex. use 201807 branch)
router bgp 222 bgp router-id 2.2.2.2 neighbor 2222::1 remote-as 901 neighbor 2222::1 timers 30 90 address-family ipv6 network 2014:1111::2/128 neighbor 2222::1 activate
Describe the results you received: Check BGP Route on Both DUTs I. DUT_FRR can receive DUT_Quagga's BGP route
Describe the results you expected: DUT_FRR should be able to update its BGP routes to peer, and DUT_Quagga should receive UPDATE message, instead of NOTIFICATEION message
Additional information you deem important (e.g. issue happens only occasionally):
ASIC: Broadcom Triden 3
IPv6 eBGP can be connected and update BGP routes with the following setup 1.1 DUT_FRR_1 <-> DUT_FRR_2 1.2 DUT_Quagga_1 <-> DUT_Quagga_2
DUT_Quagga sends "OPEN" message with a "Malformed Packet: BGP" Error
Output of
show version
: