[prev in list] [next in list] [prev in thread] [next in thread]
List: quagga-users
Subject: [quagga-users 12307] Re: Torus network and Quagga
From: yogesh <geekyogi () gmail ! com>
Date: 2011-05-20 1:45:05
Message-ID: BANLkTim5GeBWdszOzpYn8i_CzQX87vYjug () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/related)]
[Attachment #4 (multipart/alternative)]
Hi Adrian,
I guess you're talking about the summarizing the routes, yes that will be a
problem.
I had suggested this because the only network he had mentioned was
135.24.223.0/24.
/27 could be also be an option as it gives us 8 subnets, but since it's a
point to point network,
we could use /30 and save a few subnets for later use.
@Venkat, You have to do the subnetting in a way that suits you're existing
network.
Thanks
Kind Regards
--
Yogesh
http://twitter.com/geekyogi
http://geexhq.com
On Thu, May 19, 2011 at 11:48 PM, Adrian Terranova <aterranova@gmail.com>wr=
ote:
> Totally aside - couldn't you lose any (2) ports and still have full
> connectivity?
>
> Also - make the networks carrying the routing information discrete /30's
> (and not overlapping a divided /24) that's going to cause you more
> headache's than it's worth. (That's a 2nd for the recommendation from Yog=
i.)
>
> Routing tables really expect to be able to hit the full l3 via the l2
> interface when you set the network / netmask - having it split-up and
> segmented is asking for trouble.
>
> --Adrian
>
>
> On Thu, May 19, 2011 at 12:14 PM, yogesh <geekyogi@gmail.com> wrote:
>
>> Hi Venkata
>>
>> I'd suggest you to use /30 subnet for P-P network connection along with
>> RIPv2.
>> Screenshot attached for reference.
>>
>> Let me know if there is any issue related to subnetting.
>>
>> Regards
>> --
>> Yogesh
>> http://twitter.com/geekyogi
>> http://geexhq.com
>>
>>
>> On Mon, May 16, 2011 at 4:00 PM, Duvvuru, Venkata Kumar <
>> VenkataKumar.Duvvuru@netapp.com> wrote:
>>
>>> Hi,
>>>
>>> I=92m trying to setup a torus network between 4 nodes and install Quagg=
a
>>> for routing between them.
>>>
>>> Each node has three Ethernet ports and they are connected such that the=
y
>>> will be an alternate path if one Ethernet port fails.
>>>
>>> Below diagram explains the setup.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Let=92s assume that NODE1 addresses are
>>>
>>> Eth0 =96 135.24.223.100
>>>
>>> Eth1 =96 135.24.223.101
>>>
>>> Eth2 =96 135.24.223.102
>>>
>>>
>>>
>>> NODE2 addresses are
>>>
>>> Eth0 =96 135.24.223.103
>>>
>>> Eth1 =96 135.24.223.104
>>>
>>> Eth2 =96 135.24.223.105
>>>
>>>
>>>
>>> NODE3 addresses are
>>>
>>> Eth0 =96 135.24.223.106
>>>
>>> Eth1 =96 135.24.223.107
>>>
>>> Eth2 =96 135.24.223.108
>>>
>>>
>>>
>>> NODE4 addresses are
>>>
>>> Eth0 =96 135.24.223.109
>>>
>>> Eth1 =96 135.24.223.110
>>>
>>> Eth2 =96 135.24.223.111
>>>
>>>
>>>
>>> My configuration file for zebra looks like this on all the nodes.
>>>
>>> interface lan0
>>>
>>> * ip address 135.24.223.xxx/24*
>>>
>>> *interface lan1*
>>>
>>> * ip address 135.24.223.xxx/24*
>>>
>>> *interface lan2*
>>>
>>> * ip address 135.24.223.xxx/24*
>>>
>>> * *
>>>
>>> *ip route 135.24.223.0 255.255.255.0 eth0*
>>>
>>> *ip route 135.24.223.0 255.255.255.0 eth1*
>>>
>>> *ip route 135.24.223.0 255.255.255.0 eth2*
>>>
>>> * *
>>>
>>> rip configuration file looks like this
>>>
>>> *interface lan0*
>>>
>>> *!*
>>>
>>> *interface lan1*
>>>
>>> *!*
>>>
>>> *interface lan2*
>>>
>>> *router rip*
>>>
>>> * network 135.24.223.0/24*
>>>
>>>
>>>
>>> With the above configuration, the current situation is that
>>>
>>> I=92m able to reach
>>>
>>> *NODE1 to NODE3 and vice-versa*
>>>
>>> *NODE2 to NODE4 and vice-versa*
>>>
>>> but what is not working is
>>>
>>> *NODE1 to NODE2 and vice-versa*
>>>
>>> *NODE3 to NODE2 and vice-versa*
>>>
>>> *NODE1 to NODE4 and vice-versa*
>>>
>>> *NODE3 to NODE4 and vice-versa*
>>>
>>>
>>>
>>> Is there something wrong in the configuration file??
>>>
>>> Does Quagga support torus network?
>>>
>>>
>>>
>>> Any help on this is appreciated.
>>>
>>>
>>>
>>> /Venkat
>>>
>>> _______________________________________________
>>> Quagga-users mailing list
>>> Quagga-users@lists.quagga.net
>>> http://lists.quagga.net/mailman/listinfo/quagga-users
>>>
>>>
>>
>>
>> _______________________________________________
>> Quagga-users mailing list
>> Quagga-users@lists.quagga.net
>> http://lists.quagga.net/mailman/listinfo/quagga-users
>>
>>
>
[Attachment #7 (text/html)]
Hi Adrian,<div><br></div><div>I guess you're talking about the summarizing the \
routes, yes that will be a problem.</div><div>I had suggested this because the only \
network he had mentioned was <a \
href="http://135.24.223.0/24">135.24.223.0/24</a>.</div>
<div>/27 could be also be an option as it gives us 8 subnets, but since it's a \
point to point network,</div><div>we could use /30 and save a few subnets for later \
use.</div><div><br></div><div>@Venkat, You have to do the subnetting in a way that \
suits you're existing network.</div>
<div><br></div><div>Thanks</div><div>Kind Regards<br clear="all">--<br>Yogesh<div><a \
href="http://twitter.com/geekyogi">http://twitter.com/geekyogi</a></div><div><a \
href="http://geexhq.com">http://geexhq.com</a><br> <br><br><div \
class="gmail_quote">On Thu, May 19, 2011 at 11:48 PM, Adrian Terranova <span \
dir="ltr"><<a href="mailto:aterranova@gmail.com">aterranova@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">
Totally aside - couldn't you lose any (2) ports and still have full \
connectivity?<br><br> Also - make the networks carrying the routing information \
discrete /30's (and not overlapping a divided /24) that's going to cause you \
more headache's than it's worth. (That's a 2nd for the recommendation \
from Yogi.)<br>
<br>Routing tables really expect to be able to hit the full l3 via the l2 interface \
when you set the network / netmask - having it split-up and segmented is asking for \
trouble.<br><font color="#888888"><br>--Adrian</font><div>
<div></div><div class="h5"><br><br><div class="gmail_quote">
On Thu, May 19, 2011 at 12:14 PM, yogesh <span dir="ltr"><<a \
href="mailto:geekyogi@gmail.com" target="_blank">geekyogi@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><div>Hi Venkata</div><div><br></div><div>I'd \
suggest you to use /30 subnet for P-P network connection along with \
RIPv2.</div><div>Screenshot attached for reference.</div><div><br>
</div><div>Let me know if there is any issue related to \
subnetting.</div><div><br></div><div>Regards</div><div>--</div><div>Yogesh</div><div><a \
href="http://twitter.com/geekyogi" \
target="_blank">http://twitter.com/geekyogi</a></div>
<div><a href="http://geexhq.com" \
target="_blank">http://geexhq.com</a></div></div><div \
class="gmail_quote"><div><br></div><div><br></div><div>On Mon, May 16, 2011 at 4:00 \
PM, Duvvuru, Venkata Kumar <span dir="ltr"><<a \
href="mailto:VenkataKumar.Duvvuru@netapp.com" \
target="_blank">VenkataKumar.Duvvuru@netapp.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div><div></div><div> <div link="blue" vlink="purple" \
lang="EN-US"><div><p class="MsoNormal">Hi,</p><p class="MsoNormal">Im trying to \
setup a torus network between 4 nodes and install Quagga for routing between \
them.</p><p class="MsoNormal">
Each node has three Ethernet ports and they are connected such that they will be an \
alternate path if one Ethernet port fails.</p> <p class="MsoNormal">Below diagram \
explains the setup.</p><p class="MsoNormal"> </p><p \
class="MsoNormal"><span></span></p><table align="left" cellpadding="0" \
cellspacing="0"><tbody><tr><td height="14" width="3"></td></tr>
<tr><td></td><td><img src="cid:image001.png@01CC13E2.6F99D170" height="393" \
width="503"></td></tr></tbody></table> <p></p><p class="MsoNormal"> </p><p \
class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal">
</p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p \
class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p \
class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal">
</p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p \
class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p \
class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal">
</p><p class="MsoNormal"> </p><br clear="ALL"><p class="MsoNormal">Lets assume that \
NODE1 addresses are</p><p class="MsoNormal">Eth0 <a \
href="tel:%E2%80%93%20135.24.223.100" value="+13524223100" target="_blank"> \
135.24.223.100</a></p>
<p class="MsoNormal">Eth<a href="tel:1%20%E2%80%93%20135.24.223.101" \
value="+13524223101" target="_blank">1 135.24.223.101</a></p><p class="MsoNormal">
Eth2 <a href="tel:%E2%80%93%20135.24.223.102" value="+13524223102" target="_blank"> \
135.24.223.102</a></p><p class="MsoNormal"> </p><p class="MsoNormal">NODE2 addresses \
are</p><p class="MsoNormal">Eth0 <a href="tel:%E2%80%93%20135.24.223.103" \
value="+13524223103" target="_blank"> 135.24.223.103</a></p>
<p class="MsoNormal">Eth<a href="tel:1%20%E2%80%93%20135.24.223.104" \
value="+13524223104" target="_blank">1 135.24.223.104</a></p><p \
class="MsoNormal">Eth2 <a href="tel:%E2%80%93%20135.24.223.105" value="+13524223105" \
target="_blank"> 135.24.223.105</a></p>
<p class="MsoNormal"> </p><p class="MsoNormal">NODE3 addresses are</p><p \
class="MsoNormal">Eth0 <a href="tel:%E2%80%93%20135.24.223.106" value="+13524223106" \
target="_blank"> 135.24.223.106</a></p><p class="MsoNormal">Eth<a \
href="tel:1%20%E2%80%93%20135.24.223.107" value="+13524223107" target="_blank">1 \
135.24.223.107</a></p>
<p class="MsoNormal">Eth2 <a href="tel:%E2%80%93%20135.24.223.108" \
value="+13524223108" target="_blank"> 135.24.223.108</a></p><p class="MsoNormal">
</p><p class="MsoNormal">NODE4 addresses are</p><p class="MsoNormal">Eth0 <a \
href="tel:%E2%80%93%20135.24.223.109" value="+13524223109" target="_blank"> \
135.24.223.109</a></p><p class="MsoNormal">Eth<a \
href="tel:1%20%E2%80%93%20135.24.223.110" value="+13524223110" target="_blank">1 \
135.24.223.110</a></p>
<p class="MsoNormal">Eth2 <a href="tel:%E2%80%93%20135.24.223.111" \
value="+13524223111" target="_blank"> 135.24.223.111</a></p><p class="MsoNormal"> \
</p><p class="MsoNormal">
My configuration file for zebra looks like this on all the nodes.</p><p \
class="MsoNormal">interface lan0</p><p class="MsoNormal"><b> ip address \
135.24.223.xxx/24</b></p><p class="MsoNormal"><b>interface lan1</b></p><p \
class="MsoNormal">
<b> ip address 135.24.223.xxx/24</b></p><p class="MsoNormal"><b>interface \
lan2</b></p><p class="MsoNormal"><b> ip address 135.24.223.xxx/24</b></p><p \
class="MsoNormal"><b> </b></p><p class="MsoNormal"><b>ip route 135.24.223.0 \
255.255.255.0 eth0</b></p>
<p class="MsoNormal"><b>ip route 135.24.223.0 255.255.255.0 eth1</b></p><p \
class="MsoNormal"><b>ip route 135.24.223.0 255.255.255.0 eth2</b></p><p \
class="MsoNormal"><b> </b></p><p class="MsoNormal">rip configuration file looks like \
this</p>
<p class="MsoNormal"><b>interface lan0</b></p><p class="MsoNormal"><b>!</b></p><p \
class="MsoNormal"><b>interface lan1</b></p><p class="MsoNormal"><b>!</b></p><p \
class="MsoNormal"><b>interface lan2</b></p><p class="MsoNormal">
<b>router rip</b></p><p class="MsoNormal"><b> network <a \
href="http://135.24.223.0/24" target="_blank">135.24.223.0/24</a></b></p><p \
class="MsoNormal"> </p><p class="MsoNormal">With the above configuration, the current \
situation is that</p>
<p class="MsoNormal">Im able to reach </p><p class="MsoNormal"><b>NODE1 to NODE3 and \
vice-versa</b></p><p class="MsoNormal"><b>NODE2 to NODE4 and vice-versa</b></p><p \
class="MsoNormal">but what is not working is</p><p class="MsoNormal">
<b>NODE1 to NODE2 and vice-versa</b></p><p class="MsoNormal"><b>NODE3 to NODE2 and \
vice-versa</b></p><p class="MsoNormal"><b>NODE1 to NODE4 and vice-versa</b></p><p \
class="MsoNormal"><b>NODE3 to NODE4 and vice-versa</b></p>
<p class="MsoNormal"> </p><p class="MsoNormal">Is there something wrong in the \
configuration file??</p><p class="MsoNormal">Does Quagga support torus network?</p><p \
class="MsoNormal"> </p><p class="MsoNormal">Any help on this is appreciated.</p>
<p class="MsoNormal"> </p><p \
class="MsoNormal">/Venkat</p></div></div><br></div></div><div>_______________________________________________<br>
Quagga-users mailing list<br>
<a href="mailto:Quagga-users@lists.quagga.net" \
target="_blank">Quagga-users@lists.quagga.net</a><br> <a \
href="http://lists.quagga.net/mailman/listinfo/quagga-users" \
target="_blank">http://lists.quagga.net/mailman/listinfo/quagga-users</a><br> \
<br></div></blockquote></div><br> </div><br>
<br>_______________________________________________<br>
Quagga-users mailing list<br>
<a href="mailto:Quagga-users@lists.quagga.net" \
target="_blank">Quagga-users@lists.quagga.net</a><br> <a \
href="http://lists.quagga.net/mailman/listinfo/quagga-users" \
target="_blank">http://lists.quagga.net/mailman/listinfo/quagga-users</a><br> \
<br></blockquote></div><br> </div></div></blockquote></div><br></div></div>
--00151747363ea5fe8904a3ab1bab--
["image001.png" (image/png)]
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic