No subject


Fri Jul 4 19:44:43 IST 2008


few routes via BGP without setting any weights. On the Solaris 10 system
that's learning routes,  we expect to see one route in the Solaris 10 Kernel
Routing Table at any given point. We are seeing two routes instead. Does
anyone know what the issue is?

# netstat -nr

Routing Table: IPv4
  Destination          Gateway          Flags  Ref  Use  Interface
-------------------- -------------------- ----- ----- ------ ---------
10.10.10.0        10.10.10.0      UG        1      0
10.10.10.0        10.10.20.0      UG        1      0


Ideally, there should be only one route to 10.10.10.0 in the kernel routing
table and if Router A dies, Router B should show up. We've compiled Quagga
with the default options. We did not configure any multipathing while
compiling (took defaults). Is this a known bug?

Any help would be appreciated.


Thanks
Peter

------=_Part_2427_29132458.1219892444410
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr"><div style="font-family: verdana,helvetica,sans-serif; font-size: 10pt;"><div>Hi Quagga Users,<br><br>Does any one know why Quagga inserts duplicates routes into the OS Kernel <span style="border-bottom: 1px dashed rgb(0, 102, 204); cursor: pointer;" class="yshortcuts" id="lw_1219892300_0">routing table</span>? This is seen with 0.98.6 and <a href="http://0.99.6.">0.99.6.</a><br>
<br>From Router A (<span style="border-bottom: 1px dashed rgb(0, 102, 204); cursor: pointer;" class="yshortcuts" id="lw_1219892300_1">10.10.10</span>.10)
and Router B (<a href="http://10.10.10.20">10.10.10.20</a>), we are injecting a few routes via BGP
without setting any weights. On the Solaris 10 system that&#39;s learning
routes,&nbsp; we expect to see one route in the Solaris 10 Kernel Routing
Table at any given point. We are seeing two routes instead. Does anyone
know what the issue is?<br><br><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"># netstat -nr</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Routing Table:
 IPv4</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">&nbsp; Destination&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  Gateway&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  Flags&nbsp; Ref&nbsp;  Use&nbsp;  Interface</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">-------------------- -------------------- ----- ----- ------ ---------</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="border-bottom: 1px dashed rgb(0, 102, 204); background: transparent none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; cursor: pointer; font-family: Courier New,courier,monaco,monospace,sans-serif;" class="yshortcuts" id="lw_1219882527_19"></span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><a href="http://10.10.10.0">10.10.10.0</a>&nbsp; &nbsp; &nbsp; &nbsp; <a href="http://10.10.10.0">10.10.10.0</a>&nbsp; &nbsp; &nbsp;  UG&nbsp; &nbsp; &nbsp; &nbsp; 1&nbsp; &nbsp; &nbsp; 0</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><a href="http://10.10.10.0">10.10.10.0</a>&nbsp; &nbsp; &nbsp; &nbsp; <span style="border-bottom: 1px dashed rgb(0, 102, 204); cursor: pointer;" class="yshortcuts" id="lw_1219892300_2">10.10.20</span>.0&nbsp; &nbsp; &nbsp;  UG&nbsp; &nbsp; &nbsp; &nbsp; 1&nbsp; &nbsp; &nbsp; 0</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br><br>Ideally,
there should be only one route to <a href="http://10.10.10.0">10.10.10.0</a> in the kernel routing
table and if Router A dies, Router B should show up. We&#39;ve compiled
Quagga with the default options. We did not configure any multipathing
while compiling (took defaults). Is this a known bug?<br><br>Any help would be appreciated.<br><br><br>Thanks<br>Peter<br></div></div></div>

------=_Part_2427_29132458.1219892444410--


More information about the Quagga-users mailing list