From: Popgeorgiev Nikolay (nikolay.popgeorgiev@siemens.com)
Date: Wed Feb 08 2006 - 04:38:38 GMT-3
Chris,
Actually we are talking about N2 routes no inter or intra area routes. The case is simple and I don;t think there is something else. I think there is a special rule for my case but I cannot find it.
If you have time and will try it.
best,
Nick
_____
From: Chris Lewis [mailto:chrlewiscsco@gmail.com]
Sent: Tuesday, February 07, 2006 4:11 PM
To: Popgeorgiev Nikolay
Cc: ccielab@groupstudy.com
Subject: Re: ospf again
The state of forward address only relates to external routes, not inter area routes. For an external LSA to be inserted in to the routing table, the forward address needs to be 0.0.0.0 <http://0.0.0.0> or known via an inter or intra area route. As this is NSSA, the discussion of external routes is moot anyway.
It reads like you have some other configuration problems.
Try a look at http://www.cisco.com/warp/public/104/trouble_main.html <http://www.cisco.com/warp/public/104/trouble_main.html>
Chris
On 2/7/06, Popgeorgiev Nikolay <nikolay.popgeorgiev@siemens.com <mailto:nikolay.popgeorgiev@siemens.com> > wrote:
Hello people,
I asked a question about a problem with ospf and nssa but maybe I didn't explain it the best way so nobody respond.
It is a question why no matter that a LSA is in the database of ospf it sometimes is not installed in the routiing table. I have a case where a router(B) in nssa is receiving a lsa about a network(loopback address)in area 0 but is not installing it in the routing table. The question is why.
After some investigation I came to the conclusion that the reason for this is that the Forward address: of the lsa is directly connected to my router B.
When I shut the interface of B to this Forwarding Address the LSA is installed in the routing table.
So is there some rule saying something about how the receiving router is reaching the Forwarding address of the lsa ?
thanks
Nick
This archive was generated by hypermail 2.1.4 : Wed Mar 01 2006 - 11:28:17 GMT-3