Hi again,

Placing the routes in another table works fine:

# ip r s ta 10 | wc -l
744892

Meanwhile in the default table:

# ip r s | wc -l
3

However it seems the Open vSwitch daemon is again triggered and polls to synchronise the routes.

Still eating it's way through a CPU thread:

top - 08:47:02 up 6 min,  1 user,  load average: 1,11, 0,83, 0,40
Tasks: 123 total,   2 running, 121 sleeping,   0 stopped,   0 zombie
%Cpu(s): 15,5 us, 11,3 sy,  0,0 ni, 73,2 id,  0,0 wa,  0,0 hi,  0,0 si,  0,0 st
KiB Mem : 32929556 total, 31573996 free,  1259204 used,    96356 buff/cache
KiB Swap:        0 total,        0 free,        0 used. 31347300 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                 
  772 root      10 -10 1234200 884504   8440 R 105,0  2,7   6:08.68 ovs-vswitchd                                                           

I believe it's a good thing to fix Open vSwitch (not BIRD) but meanwhile I'll try to figure out another approach, maybe using virtualisation to separate the physical world from the routing process.

If there's any future testing or debugging to do I'm glad to help and make a test lab.

Regards,
Kees

On 07-05-19 07:22, Kees Meijs wrote:
Hopefully I'll be able to configure VRFs today and'll if that helps.