OK

I have done that ....

BUT after restarting I am now seeing ....

ZEBRA: netlink-cmd (NS 0) error: Invalid argument, type=RTM_NEWROUTE(24), seq=1554090, pid=0
repeated lots of times - I am trying a reboot (as that has cleared this before ....). And after a reboot those errors have gone ...

NOW I know this is normally down to the kernel routing table size... BUT I have as yet not found guidance on how to set this correctly for routers.

I'm actually willing to pay for some help getting these running correctly as a one off if anyone would be interested in helping / advising ...
 
I think the setup is close here ... Just trying to determine what I am missing ...

Thanks in advance

Richard
 
Richard Palmer | Director | Merula Limited
Company Registered in England and Wales No. 3243995
5 Avro Court, Huntingdon, Cambridgeshire, PE29 6XS
Phone 01480 222940 | Support 0845 330 0666
Support Email support@merula.net

 
--- Original message ---
Subject: Re: [FROG] Getting Started...
From: Donald Sharp <sharpd@cumulusnetworks.com>
To: Richard J Palmer <richard@merula.net>
Cc: <frog@lists.frrouting.org>
Date: Tuesday, 13/06/2017 2:21 AM

Run ./configure with a --enable-multipath=X Where X is not 1.

donald

On Mon, Jun 12, 2017 at 9:14 PM, Richard J Palmer <richard@merula.net> wrote:
Hi there

I am testing FRR as an alternative to Quagga on what is a very busy core
router - with multiple full table BGP Sessions.

I am currently using this on Slackware 14.2 ... I have things up and running
and some of the quagga bugs seem to have been cleared which is a PLUs BUT I
am seeing oddness - most obviosuly with IPv6.

Running a traceroute from a server behind it is alternating between

traceroute6 l.root-servers.net
traceroute to l.ROOT-SERVERS.NET (2001:500:9f::42) from 2a00:1940:0:1::78,
30 hops max, 24 byte packets
   1 lon1-gw1.merula.net (2a00:1940:0:1::70) 0.647 ms 0.389 ms 0.425 ms
   2 2a00:1940:0:1::67 (2a00:1940:0:1::67) 0.454 ms 0.565 ms 2.283 ms
   3 2001:7f8:17::8480:1 (2001:7f8:17::8480:1) 0.753 ms 0.662 ms 0.728 ms
   4 2a00:1a80:0:1::5:2 (2a00:1a80:0:1::5:2) 7.458 ms 5.662 ms 5.59 ms
   5 l.root-servers.net (2001:500:9f::42) 5.727 ms 5.722 ms 5.726 ms

and

traceroute6 l.root-servers.net
traceroute to l.ROOT-SERVERS.NET (2001:500:9f::42) from 2a00:1940:0:1::78,
30 hops max, 24 byte packets
   1 lon1-gw1.merula.net (2a00:1940:0:1::70) 0.481 ms * 0.682 ms !N
   2 lon1-gw1.merula.net (2a00:1940:0:1::70) 0.614 ms !N 0.54 ms !N 0.529
ms !N

The zebta.log file is filled with lines like:
2017/06/13 02:11:01 ZEBRA: zread_ipv6_add: Prefix 2402:2700:d1::/48 has 2
nexthops, but we can only use the first 1
2017/06/13 02:11:01 ZEBRA: zread_ipv6_add: Prefix 2402:2700:d2::/48 has 2
nexthops, but we can only use the first 1
2017/06/13 02:11:01 ZEBRA: zread_ipv6_add: Prefix 2402:2700:d3::/48 has 2
nexthops, but we can only use the first 1
2017/06/13 02:11:01 ZEBRA: zread_ipv6_add: Prefix 2402:2700:d4::/48 has 2
nexthops, but we can only use the first 1
2017/06/13 02:11:01 ZEBRA: zread_ipv6_add: Prefix 2402:2700:d5::/48 has 2
nexthops, but we can only use the first 1
2017/06/13 02:11:01 ZEBRA: zread_ipv6_add: Prefix 2402:2700:d6::/48 has 2
nexthops, but we can only use the first 1
2017/06/13 02:11:01 ZEBRA: zread_ipv6_add: Prefix 2402:2700:d7::/48 has 2
nexthops, but we can only use the first 1
2017/06/13 02:11:01 ZEBRA: zread_ipv6_add: Prefix 2402:2700:d8::/48 has 2
nexthops, but we can only use the first 1

and so on....

What am I missing here - I am sure it is probbay something really obvious
...

Can you help point me the right way ?

Thanks!

Richard




Richard Palmer | Director | Merula Limited
Company Registered in England and Wales No. 3243995
5 Avro Court, Huntingdon, Cambridgeshire, PE29 6XS
Phone 01480 222940 | Support 0845 330 0666
Support Email support@merula.net


_______________________________________________
frog mailing list
frog@lists.frrouting.org
https://lists.frrouting.org/listinfo/frog