The answer to the original question is that it is a bug: CSCdw67111 (OSPFv2:default-info-originate has incorrect metric type for NSSA).
It isn't fixed until 12.2(10), which isn't out yet. ""Hunt Lee"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Steve, > > I think on p540 of Jeff Doyle, the reason that it has N1 metric type is > because the RIP routes are redistributed into OSPF with "metric type 1". > > Lee > > > ""Steven A. Ridder"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > According to the example in Doyle's Vol 1. book, using the command "no > > redis" instead of default-metric creates the N1 stuff. It's on page 540, > > footnote 27. > > > > -- > > > > RFC 1149 Compliant. > > Get in my head: > > http://sar.dynu.com > > > > > > ""Chee Kin"" wrote in message > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > Hi, > > > > > > Has anyone tried this command? > > > > > > area 1 nssa default-information-originate metric-type 1 > > > > > > This is the effect on one of the routers in the NSSA. > > > > > > O*N2 0.0.0.0/0 [110/1] via 192.168.2.66, 00:27:33, TokenRing0 > > > > > > I was expecting to see O*N1. Is the above output correct? > > > > > > Thanks. > > > > > > > > > cheekin Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39719&t=38881 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
