Skip to content
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

Config ipv6 bgp Sonic #1800

Open
wegarc opened this issue Sep 4, 2024 · 1 comment
Open

Config ipv6 bgp Sonic #1800

wegarc opened this issue Sep 4, 2024 · 1 comment

Comments

@wegarc
Copy link

wegarc commented Sep 4, 2024

I have bgp problem with ipv6 config for ipv4 is all ok operative 100%.

My bgp config is:

router bgp 266832
 no bgp ebgp-requires-policy
 neighbor 199.100.24.1 remote-as 174
 neighbor 2804:5330:2:6::1 remote-as 174
 !
 address-family ipv4 unicast
  network 45.238.146.0/24
  redistribute kernel
  redistribute connected
  redistribute static
 exit-address-family
 !
 address-family ipv6 unicast
  network 2803:8ca0::/42
 exit-address-family
exit
!
ip prefix-list LOCAL_VLAN_IPV4_PREFIX seq 5 permit 10.11.12.0/24
ip prefix-list LOCAL_VLAN_IPV4_PREFIX seq 10 permit 199.100.24.0/29
ip prefix-list LOCAL_VLAN_IPV4_PREFIX seq 15 permit 45.238.146.0/29
ip prefix-list LOCAL_VLAN_IPV4_PREFIX seq 20 permit 45.238.146.16/29
ip prefix-list LOCAL_VLAN_IPV4_PREFIX seq 25 permit 45.238.146.8/29
ip prefix-list LOCAL_VLAN_IPV4_PREFIX seq 30 permit 45.238.146.24/30
ip prefix-list LOCAL_VLAN_IPV4_PREFIX seq 35 permit 45.238.146.32/28
ip prefix-list LOCAL_VLAN_IPV4_PREFIX seq 40 permit 10.10.16.0/24
!
ip nht resolve-via-default
!
end

Rutas ipv6.
sonic# show ipv6 route
Codes: K - kernel route, C - connected, S - static, R - RIPng,
       O - OSPFv3, I - IS-IS, B - BGP, N - NHRP, T - Table,
       v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

C>* 2804:5330:2:6::/112 is directly connected, Vlan2000, 00:12:19
K>* 2804:5330:2:6::2/128 [0/1024] is directly connected, Vlan2000, 00:12:19
K>* fd00::/80 [0/1024] is directly connected, docker0, 00:12:19
C * fe80::/64 is directly connected, Vlan2222, 00:09:48
C * fe80::/64 is directly connected, Ethernet8, 00:12:19
C * fe80::/64 is directly connected, Ethernet4, 00:12:19
C * fe80::/64 is directly connected, Ethernet0, 00:12:19
C * fe80::/64 is directly connected, Vlan500, 00:12:19
C * fe80::/64 is directly connected, Vlan2223, 00:12:19
C * fe80::/64 is directly connected, Vlan2100, 00:12:19
C * fe80::/64 is directly connected, Vlan210, 00:12:19
C * fe80::/64 is directly connected, Vlan209, 00:12:19
C * fe80::/64 is directly connected, Vlan204, 00:12:19
C * fe80::/64 is directly connected, Vlan202, 00:12:19
C * fe80::/64 is directly connected, Vlan2000, 00:12:19
C>* fe80::/64 is directly connected, Bridge, 00:12:19
sonic#

Anexo bgp summ.
sonic# show bgp summ

IPv4 Unicast Summary (VRF default):
BGP router identifier 199.100.24.2, local AS number 266832 vrf-id 0
BGP table version 16
RIB entries 21, using 3864 bytes of memory
Peers 2, using 1446 KiB of memory

Neighbor         V         AS   MsgRcvd   MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd   PfxSnt Desc
199.100.24.1     4        174        16        23        0    0    0 00:12:40            1       16 N/A
2804:5330:2:6::1 4        174       660      1008        0    0    0    never         Idle        0 N/A

Total number of neighbors 2

Show bgp neighbor.
sonic# show ip bgp neighbors  2804:5330:2:6::1
BGP neighbor is 2804:5330:2:6::1, remote AS 174, local AS 266832, external link
  BGP version 4, remote router ID 38.28.20.11, local router ID 199.100.24.2
  BGP state = Idle
  Last read 00:13:40, Last write 00:00:00
  Hold time is 180, keepalive interval is 60 seconds
  Configured tcp-mss is 0, synced tcp-mss is 0
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                387         13
    Notifications:        768        742
    Updates:                0          0
    Keepalives:             0          0
    Route Refresh:          0          0
    Capability:             0          0
    Total:               1155        755
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  0 accepted prefixes

  Connections established 0; dropped 0
  Last reset 00:13:40,   Notification sent (OPEN Message Error/Unsupported Capability)
  Message received that caused BGP to send a NOTIFICATION:
    FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
    004B0104 00AE00B4 261C140B 2E020601
    04000200 01020280 00020202 00020641
    04000000 AE021405 12000100 01000200
    01000200 02000100 800002
Local host: 2804:5330:2:6::2, Local port: 55964
Foreign host: 2804:5330:2:6::1, Foreign port: 179
Nexthop: 199.100.24.2
Nexthop global: 2804:5330:2:6::2
Nexthop local: fe80::3e2c:99ff:fef2:c10d
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Next start timer due in 1 seconds
Read thread: off  Write thread: off  FD used: -1

Please help me!

@Darwin4053
Copy link

Router1:
router bgp 174
no bgp ebgp-requires-policy
neighbor 172.30.36.164 remote-as 175
neighbor 2001:db8:1::164 remote-as 175
!
address-family ipv4 unicast
network 172.30.36.0/22
neighbor 172.30.36.164 activate
exit-address-family
!
address-family ipv6 unicast
network 2001:db8:1::/64
neighbor 2001:db8:1::164 activate
exit-address-family
exit

Router2:
router bgp 175
no bgp ebgp-requires-policy
neighbor 172.30.36.163 remote-as 174
neighbor 2001:db8:1::163 remote-as 174
!
address-family ipv4 unicast
network 172.30.36.0/22
neighbor 172.30.36.163 activate
exit-address-family
!
address-family ipv6 unicast
network 2001:db8:1::/64
neighbor 2001:db8:1::163 activate
exit-address-family
exit

An IPv6 address is used to establish a BGP session with the topology mentioned above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants