[j-nsp] OSPF Redistribution

harry harry at juniper.net
Fri May 14 11:59:48 EDT 2004


Hmm. The database seems OK. 

See below for some <<<<< call outs.

> -----Original Message-----
> From: Kashif.Khawaja at broadwing.com 
> [mailto:Kashif.Khawaja at broadwing.com] 
> Sent: Friday, May 14, 2004 12:19 AM
> To: harry at juniper.net; juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] OSPF Redistribution
> 
> 
> Restarted routing. Did not help.
> I am sorry I missed pasting it in the last email, I have the 
> RIDs hard-coded. Here is the database output.
> 
> FROM ROUTER B .....
> 
> show ospf database detail instance PRIVATE 
> 
>     OSPF link state database, area 0.0.0.1
>  Type       ID               Adv Rtr           Seq      Age  
> Opt  Cksum
> Len 
> Router  *10.2.255.7     10.2.255.7     0x80000072    97  0x2  
> 0xd476  48
>   bits 0x3, link count 2
>   id 10.2.255.8, data 10.2.255.93, Type PointToPoint (1)
>   TOS count 0, TOS 0 metric 837
>   id 10.2.255.92, data 255.255.255.252, Type Stub (3)
>   TOS count 0, TOS 0 metric 837


<<<< Router LSA from router B, 10.2.255.7 (RID). The LSA reports the RID of
Router A (10.2.255.8), and router A's IP address , 10.2.255.93. Router A
should now know how to reach the router identified as "10.2.255.7" by using
the 10.2.255.92/30 subnet.

>. . .
> Extern  *10.0.96.0      10.2.255.7     0x80000060   132  0x2  
> 0x2812  36
>   mask 255.255.240.0
>   Type 2, TOS 0x0, metric 1, fwd addr 0.0.0.0, tag 208.0.0.0 

. . . 

<<< The external route is advertised by Router B, RID 10.2.255.7. Even
though this RID may not be a route (normally is not when a manual RID is
set), a route to that router owning that RID should be known via router B's
router LSA. IOW, it seems like this should result in externals in the route
table, from what I have seen.

Besides a support case, and/or remove manual RIDs, I would also suggest some
tracing while you restart routing (assumes a test bed) on one of the
routers.


I would start by tracing with:

traceoptions {
    file ospf-trace;
    flag error detail;
    flag lsa-update detail;
}


HTHs.







> Thanks!
> Kashif.
> 
> 
> -----Original Message-----
> From: harry at juniper.net [mailto:harry at juniper.net] 
> Sent: Thursday, May 13, 2004 6:05 PM
> To: Khawaja, Kashif; juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] OSPF Redistribution
> 
> 
> Can I see the output of a show ospf database detail instance 
> instance-name from one of the routers?  Just guessing, but in 
> the past when I have seen externals in the database, but not 
> in the route table, it had to do with the reachability issues 
> for the forwarding address associated with the external 
> route. Nothing jumps out as wrong in the config, and I 
> suspect some type of RID problem.
> 
> Have you tried a restart routing also?
> 
> regards
> 




More information about the juniper-nsp mailing list