[Xorp-users] OSPF: ASExt-2 entry in database, but not in routing table

[V K]

> What version of xorp are you using?  What OS/kernel
> version?

The Linux OS is 2.6.25-14.fc9.i686 
The xorp version is from xorp.org 1.6 (1/07/2009)
This is probably quite old. I was not aware of xorp.ct

> If not latest xorp.ct, please
> give it a try, and let us know if you still see the
> problem.

I will do this next. I am downloading xorp-1.8.2-CT and will see how that responds.

> The truth is, I'm buried in other work at the moment, so
> I don't have much time to debug this either way. 
> But,
> you might investigate whether you need a policy or not
> for this behaviour.

I followed instructions in the old post here (http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2006-April/001185.html), and it seems to do what it was intended to do. However, what I am trying is something different. I want to take routes from _NON_OSPF_ (and _NON_XORP_) interfaces and redistribute them using the xorp/ospf processes. I don't want to run ospf on those interfaces

Another option could be to have xorp be aware of those interfaces, but not run ospf on them and follow the patch above to see if that works. I will try that on xorp1.6 and see if it is of any help

Thanks
> 
> Thanks,
> Ben
> 
> >
> > show ospf4 neighbor detail
> > Address Interface State ID Pri Dead
> > 10.1.1.254 br1/br1 Full 10.1.1.254 128 37
> > Area 0.0.0.0, opt 0x2, DR 10.1.1.1, BDR 10.1.1.254
> > Up 00:38:55, adjacent 00:38:40
> >
> >
> > Here is what the detail of the As-External-LSA
> database looks like:
> >
> > As-External-LSA:
> > LS age 10 Options 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS
> type 0x5 Link
> > State ID 11.0.1.111 Advertising Router 10.1.1.254 LS
> sequence number
> > 0x80000061 LS checksum 0x439d length 36
> > Network Mask 0xffffffff
> > bit E true
> > Metric 65535 0xffff
> > Forwarding address 10.1.1.254
> > External Route Tag 0
> >
> >
> >
> >     From: V K <vik.kaul at yahoo.com>
> >     Subject: [Xorp-users] OSPF:
> ASExt-2 entry in database, but not in
> >     routing table
> >     To: xorp-users at xorp.org
> >     Date: Tuesday, October 5,
> 2010, 3:46 PM
> >
> >     Sorry. Forgot to put in the
> Subject line. Resending
> >
> >     --- On *Tue, 10/5/10, V K
> /<vik.kaul at yahoo.com>/*
> wrote:
> >
> >
> >         From: V K <vik.kaul at yahoo.com>
> >         Subject:
> [Xorp-users] (no subject)
> >         To: xorp-users at xorp.org
> >         Date: Tuesday,
> October 5, 2010, 3:43 PM
> >
> >         Folks
> >
> >         The xorp
> instance I have receives an AS LSA update message (with
> >         age 1) and
> updates the database (see last entry below for
> >         11.0.2.135). The
> database entry removal also works well.
> >         However, the
> routing table is not updated.
> >
> >         Could it be so
> because the "External<A>::push_routes()" function
> >         does nothing. I
> followed the trail of the push_routes and
> >     
>    external_push_routes routines... but I am
> not sure that is the
> >         reason because
> they seem to be triggered by
> >     
>    policy_backend_0_1_push_routes which seems
> to be dictated by
> >         template.
> >
> >         All I want is a
> way to insert a route in the routing table if it
> >         appears in the
> database as the ASExt-2 entry.
> >
> >         Any help will be
> appreciated
> >
> >
> >
> >         
> >>>>>show ospf4 database
> >         OSPF link state
> database, Area 0.0.0.0
> >         Type ID Adv Rtr
> Seq Age Opt Cksum Len
> >         Router
> *10.2.2.254 10.2.2.254 0x8000000c 1685 0x2 0xad63 36
> >         Router 127.1.0.2
> 127.1.0.2 0x800000cc 1691 0x2 0x47ec 48
> >         Network 10.2.2.2
> 127.1.0.2 0x80000002 1691 0x2 0x56e0 32
> >         Network 10.1.2.2
> 127.1.0.2 0x800000c6 205 0x2 0xda24 32
> >         Router 127.1.0.1
> 127.1.0.1 0x800000e1 1732 0x2 0x5454 60
> >         Router
> 10.1.1.254 10.1.1.254 0x8000000e 1728 0x2 0x9b7c 36
> >         Network 10.1.1.1
> 127.1.0.1 0x80000002 1732 0x2 0x5ae3 32
> >         ASExt-2
> 11.0.2.135 10.1.1.254 0x80000001 7 0x2 0x8ea4 36
> >
> >
> >
> >         -----Inline
> Attachment Follows-----
> >
> >     
>    _______________________________________________
> >         Xorp-users
> mailing list
> >         Xorp-users at xorp.org
> >         http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >
> >
> >
> >     -----Inline Attachment
> Follows-----
> >
> > 
>    _______________________________________________
> >     Xorp-users mailing list
> >     Xorp-users at xorp.org
> </mc/compose?to=Xorp-users at xorp.org>
> >     http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >
> >
> >
> >
> > _______________________________________________
> > Xorp-users mailing list
> > Xorp-users at xorp.org
> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> 
> 
> -- 
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
> 
>