I have 3 OSPF areas, with 2.9.11 and routing-test everything works great, but after upgrade to 2.9.16 routers stop redistributing routes between areas
here is config from one router that may redistribute it… Problem persist with both routing and routing-test… router “see” all routes from both areas, but not redistribute. Router is x86 machine. Routers around are RB with 2.9.16 and routing-test. If redistribution router is downgraded to 2.9.11 everything is OK
If blue/green and blue/yellow routers are 2.9.11 and all others are 2.9.17 everything works. In blue area I can see all routes from all networks and in green/yellow area default route is present + routes from this area.
If these two routers are upgraded to 2.9.17 in blue area I see only routes from blue area and in green/yellow area I can see only routes from this area (no default route, no routes from blue area)
I have same problem as Mapik with 2.9.17. My routers are seeing each other , however they don’t redistribute their routes. My topology is:
AS1 <=> switch <=> AS2
… |
… router
Is it a problem that all of them are in one layer2 segment?
I have a rule for setting the distance to 110 in the ospf-in chain
However the state of all the neighbours is continuously changing on all of them - full/2-way/Loading. Is is possible to be a problem of trying to redistribute large number of /32 nets (connected via ppp users)?
I removed the prefix-list-import from all areas. All routers 100.100.0.1-3 had ospf network = 100.100.0.0/24 on the backbone area. I also added to additional areas 10.10.0.1-2 that are run on other interfaces as you suggested.
Again there were no distribution of routes and routers were continuously changing there state.
There are about 500 /32 rouite entries on both 100.100.0.2-3. Also 100.100.0.3 is loaded on 100% now (continuously). Even after stopping ospf on other routers. I can not stop ospf on the loaded router. I am starting to think this is not a configuration problem .
There are pppoe servers on 100.100.0.2-3 and I is not sure on which one of them a client will connect. That’s why a routing protocol is necessary in this situation. I have routed staticly all possible networks.
That is my config. I use one RADIUS server and have different IP-pool settings for all clients with dynamic IPs, however the problem with static routing is with clients that get static IPs. So my routers should understend someway on which access server is connected this client with static address.
It works some way with rip, but sometimes my routers receives wrong information and as result the clients are connecting but there’s no correct routes for them .