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

BGP for 6PE with FRR version 7.3 #6341

Closed
KaushikNiral opened this issue May 5, 2020 · 5 comments
Closed

BGP for 6PE with FRR version 7.3 #6341

KaushikNiral opened this issue May 5, 2020 · 5 comments
Labels
bgp triage Needs further investigation

Comments

@KaushikNiral
Copy link
Member

KaushikNiral commented May 5, 2020

FRR version 7.3
commit Id: c0038fc

**Issue with FRR 7.3 BGP for 6PE setup **

We have been trying to use FRR as BGP for 6PE. The BGP sessions were up and also received 6PE routes from PE routers (Cisco router), however the FRR didn't show these received routes as valid and best path. Please find the screenshot attached below ( The routers with entry 1111::1/128 and 2222::/64)

bgp_ipv6_unicast_table

It also displays the learned route as inaccessible, screenshot is attached for it below.

bgp_ipv6_unicast_table_ip

Could anyone please advise how to make it work?
Thanks a lot in advance.

The configuration which we used in FRR as PE router given below.
Current configuration:

!
frr version 7.3
frr defaults traditional
hostname vyatta
log syslog
service integrated-vtysh-config
!
router bgp 234
 no bgp default ipv4-unicast
 neighbor 2.2.2.2 remote-as 234
 neighbor 2.2.2.2 update-source 4.4.4.4
 neighbor 3333::5 remote-as 5
 !
 address-family ipv4 unicast
  neighbor 2.2.2.2 activate
 exit-address-family
 !
 address-family ipv6 unicast
  neighbor 3333::5 activate
 exit-address-family
 !
 address-family ipv6 labeled-unicast
  neighbor 2.2.2.2 activate
 exit-address-family
!
router ospf
 timers throttle spf 500 500 50000
 timers throttle lsa all 0
 network 4.4.4.4/32 area 0.0.0.0
 network 172.16.169.0/24 area 0.0.0.0
!
mpls ldp
 router-id 4.4.4.4
 !
 address-family ipv4
  discovery transport-address 4.4.4.4
  label local allocate host-routes
  session holdtime 30
  !
  interface dp0p192p1
  !
 exit-address-family
 !
!
line vty
!
end

To Reproduce
Please use the configuration above.

Expected behavior
The received routes from other PE router should not show as inaccessible and it should also be installed in rib table "show ipv6 route" .

Versions

  • OS Kernel: Linux ubuntu 4.18.0-15-generic
  • FRR Version [7.3]
@KaushikNiral KaushikNiral added the triage Needs further investigation label May 5, 2020
@qlyoung qlyoung added the bgp label May 5, 2020
@ton31337
Copy link
Member

ton31337 commented May 9, 2020

Could you show show ipv6 nht output? And debug bgp updates output would be useful as well. Even more, if you have a pcap, that would be cool as well.

@KaushikNiral
Copy link
Member Author

KaushikNiral commented May 10, 2020

Hi,
Please find our setup information.
6PE-FRR-Diag

The output of show ipv6 nht from FRR router (PE2)
show_ipv6_nht

The log contains bgp updates of both in and out
bgp_update.log

The packet capture is also attached below.
In the packet capture you can see the BGP update which is shared from FRR router should have nexthop as IPv4 mapped IPv6 address like ::ffff:404:404 but the update is shared with nexthop IP as 3333::5

pkt_capture_towards_P_router.pcap.zip

Thanks,
Kaushik

@ton31337
Copy link
Member

I'll check this.

@KaushikNiral
Copy link
Member Author

This issue is resolved in BGP and ZEBRA.

The output of the BGP table and RIB table is attached below.

6pe_bgp_table
6PE_show_rib_table
6pe_bgp_table_detail

The BGP update issue is also resolved for 6PE .
The packet capture is attached below.

6PE_bgp_update_packet.pcapng.zip

Thanks,

KaushikNiral added a commit to Niral-Networks/frr-1 that referenced this issue May 25, 2020
BUG No. FRRouting#6341 and FRRouting#6382
lib   : Added a macro to validate the IPv4 Mapped IPv6 address.
bgp   : Modifications done for bgp receive and while sending updates
	for IPv4 Mapped IPv6 address.
zebra : Modifications done for installing IPv4 Mapped IPv6 address as nexthop
	in RIB. Minor correction done in fpm while sending the routes for
	nexthop as IPv4 Mapped IPv6 address.
KaushikNiral added a commit to Niral-Networks/frr-1 that referenced this issue May 25, 2020
BUG No. FRRouting#6341 and FRRouting#6382
lib : Added a macro to validate the IPv4 Mapped IPv6 address.
bgp : Modifications done for bgp receive and while sending updates
for IPv4 Mapped IPv6 address.
zebra : Modifications done for installing IPv4 Mapped IPv6 address as nexthop
in RIB. Minor correction done in fpm while sending the routes for
nexthop as IPv4 Mapped IPv6 address.

Signed-off-by: Kaushik <kaushik@niralnetworks.com>
KaushikNiral added a commit to Niral-Networks/frr-1 that referenced this issue May 25, 2020
BUG No. FRRouting#6341 and FRRouting#6382
lib : Added a macro to validate the IPv4 Mapped IPv6 address.
bgp : Modifications done for bgp receive and while sending updates
for IPv4 Mapped IPv6 address.
zebra : Modifications done for installing IPv4 Mapped IPv6 address as nexthop
in RIB. Minor correction done in fpm while sending the routes for
nexthop as IPv4 Mapped IPv6 address.

Signed-off-by: Kaushik <kaushik@niralnetworks.com>
@KaushikNiral
Copy link
Member Author

Closing this issue. It is fixed by PR #6821

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

No branches or pull requests

3 participants