Hi JFD, Thanks for the response, but it doesn't answer the question. Is there something about redistributing from RIP into OSPF where it is *necessary* for one to provide a metric on the redistribute command? I agree from a BCP perspective it is wise to explicitly list the metric, but want to understand if there is some low-level protocol issue where it's not possible for the IOS to provide and use a default metric when one is not provided via the redist command.
This is both a theory of protocols / routing and a practical question. In a real live network, we had an issue where a router was configured with a redist of RIP routes into OSPF. The RIP routes where not being redistributed by OSPF. (I don't know if the routes never got advertised or if they where being advertised and then the advertisements stopped at some point in time.) Cisco was called in to look at the problem and reported the problem was because the redist was missing the "metric XYZ" command. I don't buy that the "metric XYZ" is in fact necessary. In the testing I've done, the redist works without the metric and in fact supplies a default metric when a metric is not provided. This would seem to indicate the metric value is in fact not needed in order for the redist to work correctly. I expect this was a bug in the IOS we were running and the response that the "metric XYZ" was required was provided as a work around to the bug, but cast as necessary for the protocols to work properly. But trying to unwrap this onion a bit more... Thanks Jean-Francois Delrieu wrote: > > Bergenpeak, > > You should always use default metrics before redistributing or specify a > metric when reditributing specific routes. > This is valid for any protocol redistribution in a lab or in prod. > You will avoid a lot of problems. > > JFD Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=55455&t=55364 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
