|-----Original Message----- |From: owner-usr-tc@lists.xmission.com |[mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Jeff Mcadams |Sent: Tuesday, November 16, 1999 12:12 PM |To: usr-tc@lists.xmission.com |Subject: Re: (usr-tc) Continuing OSPF problems | | |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 HARC is not sending anything wrong in this case. It is doing something wrong based on information it receives from the DR. The card should not be changing its netmask for any reason. But it obviosly is doing this when it receives a less specific route from the DR. |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. :/ Actually its not a Cisco thing. Its called Internal Distance in the RFC. This information is used for tie breaking when equal cost routes are present and the admin does have a preference. -M * - 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.