[j-nsp] OSPF Redistribution

Kashif.Khawaja at broadwing.com Kashif.Khawaja at broadwing.com
Fri May 14 03:18:56 EDT 2004


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   10.2.255.8     10.2.255.8     0x80000072    93  0x2  0xc880  48
  bits 0x3, link count 2
  id 10.2.255.7, data 10.2.255.94, 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
    OSPF AS SCOPE link state database
 Type       ID               Adv Rtr           Seq      Age  Opt  Cksum
Len 
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
Extern   10.0.112.0     10.2.255.8     0x8000000a    98  0x2  0x1e61  36
  mask 255.255.240.0
  Type 2, TOS 0x0, metric 1, fwd addr 0.0.0.0, tag 208.0.0.0

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