Thus spake Mike Andrews
The real problem is that the ARC is letting less specific routes override more specific routes, and thus confusing itself about its own netmask. That's apparently why communication fails with the new DR:
Hrmm...ok...so its sending the wrong netmask...the netmask in the routing table in the Hello packets.... So...that means that someone isn't paying attention to the Hello packets in the normal course of operation. Theoretically, sending a Hello packet with the wrong netmask (as the Arc is doing) should destroy the adjacency, should it not? OK...a check of the RFC shows that I'm not quite right here. A mismatch on the Netmask should cause the Hello packet to be dropped, which, after RouterDeadInterval time of no Hello packets, the router should be declared down and the adjacency destroyed. It seems that the Cisco is not doing the checks that it should here either though in that its not killing the adjacency. Just out of curiosity, what does a list ip networks, or show ip network <blah> show for the netmask on that network after picking up the new OSPF routes?
Yeah, fra1 is the border (3620). The null0 tiedown routes have a "250" distance metric on the end (used to be 10 til last night), and those routes are getting injected into OSPF. The ARC still uses them whether the metric is 10 or 250... it seems to ignore the metric.
I believe administrative distance is a Cisco proprietary thing and is not transmitted via OSPF. The Arc's don't seem to have nearly the control over route redistribution and such that the Cisco's do. :/
The only way I was able to make things sane was to stop the tiedowns from getting injected into OSPF at all. I haven't yet figured out how to stop just those routes from getting injected without shutting down redistribution of ALL static routes. (Fortunately there aren't many other static routes, so for now, this is what I've done.) I had tried various combinations of distribute-list on the Cisco, as well as receivepolicy on the ARC, and didn't have much luck. I'm sure there's a better way to do it though. :)
Hrmm...Cisco's web site seems to be broken at the moment, but I think you'll need to put a route-map on the "redistribute static" clause in router ospf for this to work. Not sure exactly what distribute-list does... -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.