[FROG] Migration scripts for FRR from Quagga

Wed Jun 12 18:39:21 UTC 2024

So my best guess was frr did not like some of the simplicity of this config.  So I pulled a config from another router I have and things seem better.  The logs have the following 3 errors in them googling is not helping me answer:

2024/06/12 18:19:25 BGP: [TXY0T-CYY6F][EC 100663299] Can't get remote address and port: Transport endpoint is not connected
2024/06/12 18:19:25 BGP: [P90Z5-FP0GJ][EC 33554461] 100.125.6.19: nexthop_set failed, local: 100.125.6.7:35287 remote: (null)p update_if: (None) resetting connection - intf (Unknown)
2024/06/12 18:19:26 BGP: [M8SSC-Q34TS] EBGP inbound/outbound policy not properly setup, please configure in order for your peering to work correctly

The last error seems odd, I have it set and have read through the documentation, but am not seeing what I need that it expects.  And that being said, bgp is indeed now up, and receiving routes from the peer, so in spite of these errors things are working.  But I don't know if these are ok to ignore or not, and the last one bugs me as something that is likely problematic but I'm not sure what it may affect.  here is how my config looks now.  Any suggestions are welcome.

log syslog informational
no ipv6 forwarding

! We need a route to the peer in the other AZ
! otherwise "redistribute connected" confuses the route table
! with route flaps seen itself over iBGP
! .1 through .5 we always lose and their router is always .1
! this is an artifact and /dev/null

! ip route 100.125.6.147/32 100.125.6.1

! Configure interfaces
interface lo
service integrated-vtysh-config
!
hostname mailspoool-ap-southeast-1a-test
password a
enable password a

!
!bgp mulitple-instance
!

router bgp #########
  bgp router-id 100.125.6.7
  timers bgp 10 30
  bgp log-neighbor-changes

! VPC peer in AP-Southeast-1a
  neighbor 100.125.6.19 remote-as ###########
  neighbor 100.125.6.19 description Router in AP-Southeast-1a
  neighbor 100.125.6.19 update-source 100.125.6.7
!  neighbor 100.125.6.19 route-map rm-default-accept-all out
  neighbor 100.125.6.19 route-map rm-default-accept-all in
  neighbor 100.125.6.19 send-community all
  neighbor 100.125.6.19 weight 100
  neighbor 100.125.6.19 next-hop-self

route-map rm-default-accept-all permit 10
  match ip address all

!
access-list all permit any
!

log file /var/log/frr/bgpd
!

Doug Tucker
Sr. Director of Networking and Linux Operations

o: 817.975.5832
e: doug.tucker at navigaglobal.com

Newscycle Solutions is now Naviga. Learn more.

CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibite

________________________________
From: Donald Sharp <donaldsharp72 at gmail.com>
Sent: Thursday, May 23, 2024 2:29 PM
To: Doug Tucker <doug.tucker at navigaglobal.com>
Cc: frog at lists.frrouting.org <frog at lists.frrouting.org>
Subject: Re: [FROG] Migration scripts for FRR from Quagga

add a no form of the command?

`no bgp ebgp-requires-policy`

On Thu, May 23, 2024 at 3:36 PM Doug Tucker <doug.tucker at navigaglobal.com<mailto:doug.tucker at navigaglobal.com>> wrote:
I saw and read that.  It states essentially  it is on by default, and says you have to restart when disabling, but I can't find any syntax to how to turn it off.

Doug Tucker
Sr. Director of Networking and Linux Operations

o: 817.975.5832
e: doug.tucker at navigaglobal.com<mailto:doug.tucker at navigaglobal.com>

Newscycle Solutions is now Naviga. Learn more.

CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibite

________________________________
From: Donald Sharp <donaldsharp72 at gmail.com<mailto:donaldsharp72 at gmail.com>>
Sent: Thursday, May 23, 2024 1:32 PM
To: Doug Tucker <doug.tucker at navigaglobal.com<mailto:doug.tucker at navigaglobal.com>>
Cc: frog at lists.frrouting.org<mailto:frog at lists.frrouting.org> <frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>>
Subject: Re: [FROG] Migration scripts for FRR from Quagga

https://docs.frrouting.org/en/latest/bgp.html#require-policy-on-ebgp

On Wed, May 22, 2024 at 7:33 PM Doug Tucker <doug.tucker at navigaglobal.com<mailto:doug.tucker at navigaglobal.com>> wrote:
Thanks Donald, and sorry for the late response.  I am just getting back to this.  I found this in the documentation:

Configuration for the daemon should be saved in the FRR integrated configuration file located in /etc/frr/frr.conf, see Integrated Config File<https://docs.frrouting.org/en/latest/basic.html#config-file> for more information on system configuration.
Prior versions of FRR supported reading and writing per-daemon config files; however, with the introduction of the centralized management daemon mgmtd this could no longer be supported.
The interesting thing is it did seem to read my zebra.conf, but completely skipped the bgpd.conf.  So I tried copying the contents of the bgpd.conf into frr.conf and the daemon starts, and doing a show run it looks pretty identical to quagga system side by side with a few caveates (hostname for instance shows up twice with 2 different values).  But, I'm not getting the advertised routes from remote.  The logs are showing me this.  So it sees them, but something is missing that wasn't needed in quagga.
2024/05/22 23:04:45 BGP: [RZMGQ-A03CG] 169.254.244.13(Unknown) rcvd UPDATE about 10.0.0.0/8<http://10.0.0.0/8> IPv4 unicast -- DENIED due to: inbound policy missing
2024/05/22 23:04:45 BGP: [RZMGQ-A03CG] 169.254.244.13(Unknown) rcvd UPDATE about 192.168.0.0/16<http://192.168.0.0/16> IPv4 unicast -- DENIED due to: inbound policy missing

2024/05/22 23:04:45 BGP: [RZMGQ-A03CG] 169.254.244.13(Unknown) rcvd UPDATE about 172.16.0.0/12<http://172.16.0.0/12> IPv4 unicast -- DENIED due to: inbound policy missing

I've been reading for a while now but not finding an resolution.

Doug Tucker

________________________________
From: Donald Sharp <donaldsharp72 at gmail.com<mailto:donaldsharp72 at gmail.com>>
Sent: Wednesday, April 17, 2024 2:35 PM
To: Doug Tucker <doug.tucker at navigaglobal.com<mailto:doug.tucker at navigaglobal.com>>
Cc: frog at lists.frrouting.org<mailto:frog at lists.frrouting.org> <frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>>
Subject: Re: [FROG] Migration scripts for FRR from Quagga

You don't often get email from donaldsharp72 at gmail.com<mailto:donaldsharp72 at gmail.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

Naviga WARNING: External email. Please verify sender before opening attachments or clicking on links.

In general you should just be able to use the Quagga configs directly in FRR(There are a couple caveats of course ).  I am not aware of any conversion/migration scripts though.  Have you tried just loading the config and seeing what happens? Then comparing a show run to the saved config?

donald

On Wed, Apr 17, 2024 at 4:29 PM Doug Tucker via frog <frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>> wrote:

---------- Forwarded message ----------
From: Doug Tucker <doug.tucker at navigaglobal.com<mailto:doug.tucker at navigaglobal.com>>
To: "frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>" <frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>>
Cc:
Bcc:
Date: Wed, 17 Apr 2024 19:23:33 +0000
Subject: Migration scripts for FRR from Quagga
I am needing to undertake migrating from all of my quagga instances to frr.  I have read through the general documentation but before I started from scratch I thought I would see if there were some migration/conversion scripts available for existing quagga installations.  Thank you for your assistance.

Doug Tucker

---------- Forwarded message ----------
From: Doug Tucker via frog <frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>>
To: "frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>" <frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>>
Cc:
Bcc:
Date: Wed, 17 Apr 2024 19:23:33 +0000
Subject: [FROG] Migration scripts for FRR from Quagga
_______________________________________________
frog mailing list
frog at lists.frrouting.org<mailto:frog at lists.frrouting.org>
https://lists.frrouting.org/listinfo/frog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20240612/360faecb/attachment-0001.htm>