Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Quagga: Bugs
[Bug 455] New: AS-external-LSA does not get updated immediately.
 

Index | Next | Previous | View Flat


bugzilla-daemon at allevil

Jun 2, 2008, 8:24 AM


Views: 2941
Permalink
[Bug 455] New: AS-external-LSA does not get updated immediately.

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.

http://bugzilla.quagga.net/show_bug.cgi?id=455

Summary: AS-external-LSA does not get updated immediately.
Product: Quagga
Version: CVS
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: Medium
Component: ospfd
AssignedTo: maintainers [at] quagga
ReportedBy: jkrabbendam [at] aimvalley


I have the following situation:
GW --10/8-- ASBR ---- R
The GW ip address is 10.0.0.1. R stands for the rest of the OSPF network.
GW is outside the OSPF domain.

On the ASBR issue the following commands:
linux> route add default gw 10.0.0.1 #add a default route to the gateway.
ospfd> default-information originate originate metric 123 metric-type 2 #let
OSPF advertise the default route.
ospfd> network 10.0.0.0/8 area 0.0.0.0 #enable this network for OSPF.
(additional commands are needed to have OSPF enabled between ASBR and R, but
they are not relevant for the problem).

Two ASBR LSAs are relevant to this case: A router-LSA for 10.0.0.0/8 and an
AS-external-LSA with Forward Address set to 10.0.0.1.

So far so good. The problem occurs when the following command is given on ASBR:
ospfd> no network 10.0.0.0/8 area 0.0.0.0 #disable this network for OSPF.

The ASBR should do two things now:
1) Cancel the advertisement of the 10.0.0.0/8 network (flush the router LSA).
2) Update the Forward Address in the AS-external-LSA: 10.0.0.1 -> 0.0.0.0.

It does the first but it does the second only when the AS-external-LSA age
reaches 1800 seconds (can be some earlier or later as well). This means that the
gateway is not reachable from R for quite some time.

The same faulty behaviour occurs when going from 'no network 10.0.0.0/8 area
0.0.0.0' to 'network 10.0.0.0/8 area 0.0.0.0' but in that case, reachability is
not at stake.

A work around is to re-issue the default-information command.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs [at] lists
http://lists.quagga.net/mailman/listinfo/quagga-bugs

Subject User Time
[Bug 455] New: AS-external-LSA does not get updated immediately. bugzilla-daemon at allevil Jun 2, 2008, 8:24 AM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.