So we just put the first 3.3 in the field and mirrored an existing 2.9 configuration. But OSPF refuses to work. We currently have a 3550 running OSPF and distributing routes to our 2.9MT through a broadcast network (/24). we are not using authentication, and the OSPF areas all match.
When I add a network it dynamically creates an OSPF interface, why? When I add another network with the same area and the same interface a second dynamically created interface shows up. I tried to create a single OSPF interface but the dynamic interfaces still show up for the other networks on the same interface leaving me with the one I setup and the dynamic interface.
So on top of that, the 3.3MT sees my 3550 AND my 2.9MT as a neighbor, but they don’t communicate.
I have dozens of routers running 3.3 and I think it is the most stable ospf implementation I have seen on ROS so far… Must be something in your config.
I upgraded one of our tower locations today from 2.9 to 3.4 and the OSPF session that has been working perfectly (talking to some old Portmasters) for almost 3 years, suddenly stopped working. We were unable to fix the problem and finally just had to create some static routes to get it going again.
I’m not saying OSPF is broken, but the implementation definately changed from 2.9 to 3.x. I have not seen any problems with 3.x MT talking to 2.9 or 3.x.
Yea, the 3.3MT can see the 2.9MT but not my 3550. I’ve done the static route trick as a temp fix but I really dislike static routes in larger network. I’m working on it more today and am thinking that I’ll move the area to the backbone and try that.
EDIT:
I just changed the related area to the backbone, so I’m only working off of the backbone and the 3.3MT still is retarded.
The 2.9MT talked to the 3550 and got the routes, but the 3.3MT set itself up as the DR after the 3550 is already the DR… This could be the problem. Everything is configured right, it just will not work.
I’ll work on it over the weekend and hopefully I won’t need anymore help.