[quagga-users 14508] Re: Zebra RTM_NEWROUTE

Arnaud,

    I looked at the code in  zebra/rt_netlink.c:netlink_parse_info() 
where we parse netlink packets.
  The error log you see takes place at line 372 in the same file.

   In summary, you are receiving and error packet from the kernel  in 
response to a previous RTM_NEWROUTE msg.
   To see what is going on you need to enable zebra-kernel debugging by 
adding the following to zebra.conf:

    debug zebra kernel

right after where you specify the log file would do. Using the sequence 
number you can then match the error msg
sequence number with that of the offending RTM_NEWROUTE msg.  Please 
post back the result and then we
can continue from there.

Regards,
Jafar


On 11/6/2016 2:17 PM, Arnaud Launay wrote:
> Hello,
>
> Le Sat, Nov 05, 2016 at 11:50:56PM -0500, Jafar Al-Gharaibeh a écrit:
>>> Since shutdowning one router (on three) to add more SFP ports, we
>>> see like 200 lines like this:
>>> 2016/11/05 10:50:37 ZEBRA: netlink-cmd (vrf 0) error: Invalid argument, type=RTM_NEWROUTE(24), seq=564170, pid=0
>>> 2016/11/05 10:50:37 ZEBRA: netlink-cmd (vrf 0) error: Invalid argument, type=RTM_NEWROUTE(24), seq=564171, pid=0
>>> 2016/11/05 10:50:37 ZEBRA: netlink-cmd (vrf 0) error: Invalid argument, type=RTM_NEWROUTE(24), seq=564172, pid=0
>>> 2016/11/05 10:50:37 ZEBRA: netlink-cmd (vrf 0) error: Invalid argument, type=RTM_NEWROUTE(24), seq=564173, pid=0
>>> 2016/11/05 10:50:37 ZEBRA: netlink-cmd (vrf 0) error: Invalid argument, type=RTM_NEWROUTE(24), seq=564174, pid=0
>>>
>>>
>>> At boot, and then a few dozen more each day, not necessarily
>>> grouped. Does anyone has an idea on where to look at ? We found
>>> very few references on google, mostly on very old releases, but
>>> we use a recent one...
>>>
>>> Linux 4.4.26
>>> quagga-1.0.20160315-r4.ebuild on Gentoo (it includes the RA,
>>> ospfd dangling and bgpd logging patches)
>>>
>>> Strangely enough, this issue doesn't appear on the other routers.
>>> Should we try the very last quagga ?
>>    What are the other routers? Gentoo as well? same Quagga version?
> Yes. Same Gentoo, same quagga, same kernel config, same sysctl.
>
>>     Without testing to see what exactly is going wrong I can
>>     only speculate. Could it be that the Gentoo box doesn't have
>>     support for network namespaces? and that is causing issues
>>     with Quagga trying to send vrf fields in RTM msgs? What do
>>     yo see if you do "ip netns list" on the router where you see
>>     this issue? is the output any different on other routers?
> It's the same on all three, output on the first one:
>
> qua1 ~ # ip netns list
> qua1 ~ #
>
> I don't think they support network NS. It can be added, though.
> Would it help ? And why until now was that never needed ?
>
> 	Arnaud.
>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users-UOy77sIEA+cAd7ICUelF/[email protected]
> https://lists.quagga.net/mailman/listinfo/quagga-users

_______________________________________________
Quagga-users mailing list
Quagga-users-UOy77sIEA+cAd7ICUelF/[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-users