<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Sorry,<br>
<br>
There is a mistake bellow. Please read the following "Either
setting it up in R1..." as "Either setting it up in R2..." <br>
<br>
Best~<br>
<div class="moz-signature">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<style>
<!--
.txt1{
font-family:Verdana;
color:#103e81;
font-size:12px;
}
.txt2{
font-family:Verdana;
color:#00ace5;
font-size:12px;
}
a:link{
color:00ace5;
text-decoration:none;
}
a:visited{
color:00ace5;
text-decoration:none;
}
-->
</style>
<div class="txt1">
---<br>
<strong>Dean Belev</strong><br>
Product Manager<br>
<br>
Neterra Ltd.<br>
Telephone: +359 2 975 16 16<br>
Fax: +359 2 975 34 36<br>
Mobile: +359 886 663 123<br>
</div>
<a href="http://www.neterra.net" class="txt2">www.neterra.net</a>
</div>
On 17.8.2012 г. 14:10 ч., Dean Belev wrote:<br>
</div>
<blockquote cite="mid:502E26AF.1010202@neterra.net" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Stefan,<br>
<br>
Thank you. Now it works.<br>
<br>
Ondrej,<br>
<br>
Either setting it up in R1 (neighbor 6.6.6.6 next-hop-self) or
in RS (if net ~ 3.3.3.0/24 then bgp_next_hop = 6.6.6.100) I see
that in the RS's routing table the route takes the appropriate
NEXT-HOP (BGP.next.hop: 6.6.6.100). But when I check it on
Router1 - the route points to 6.6.6.6.<br>
<br>
Best~<br>
<br>
<div class="moz-signature">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<style>
<!--
.txt1{
font-family:Verdana;
color:#103e81;
font-size:12px;
}
.txt2{
font-family:Verdana;
color:#00ace5;
font-size:12px;
}
a:link{
color:00ace5;
text-decoration:none;
}
a:visited{
color:00ace5;
text-decoration:none;
}
-->
</style>
<div class="txt1"> ---<br>
<strong>Dean Belev</strong><br>
Product Manager<br>
<br>
Neterra Ltd.<br>
Telephone: +359 2 975 16 16<br>
Fax: +359 2 975 34 36<br>
Mobile: +359 886 663 123<br>
</div>
<a moz-do-not-send="true" href="http://www.neterra.net"
class="txt2">www.neterra.net</a> </div>
On 17.8.2012 г. 13:45 ч., Ondrej Zajicek wrote:<br>
</div>
<blockquote cite="mid:20120817104553.GM7311@localhost" type="cite">
<pre wrap="">On Fri, Aug 17, 2012 at 08:38:42AM +0300, Dean Belev (Neterra NMT) wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Hi all,
I was performing a home lab and decided to test a new scenario including
iBGP between a router and RS.
That's a brief scheme of the lab:
###
5.5.5.1 5.5.5.2 6.6.6.100/24
6.6.6.6/24
6.6.6.101/24
Router3 (as3)---eBGP---> Router2 (as2)---iBGP/not a rs_client---> RS
(as2)---eBGP / rs_client--- > Router1 (as1)
3.3.3.0/24 2.2.2.0/24
1.1.1.0/24
###
Since, as route 3.3.3.0/24 is seen in RS directly attached ( first asn is
as3) with next-hop 6.6.6.100 (I've set the next-hop manually into the RS's
config in bgp_in) I expect that Router1 should see it in the same way -
with hext-hop 6.6.6.100.
</pre>
</blockquote>
<pre wrap="">The question is whether you set manually real next-hop or bgp_next_hop
attribute. For BGP route propagation, bgp_next_hop attribute is more
important. You should check route attributes by 'show route 3.3.3.0/24
all' on RS and R1.
</pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>