I would recommend doing a direct linked network between the XMRs. I.e a p2p network. That way you don't have to rely on IGP for the BGP sessions. Doing a p2p link would make the update source-loopback 1 statment obsolete. If you do want to advertise anything in BGP ( which you according to the config currently aren') you would have to add a network statment <a href="http://1.0.0.0/8">1.0.0.0/8</a>. You woul also have to have a exact match of that network statment in your IGP. Eeasiest is normally a static route either to null0 or a pointing to a GW.<br>
<br>Regards Andreas<br><br><div class="gmail_quote">On Thu, Apr 3, 2008 at 10:06 PM, Dan Spataro <<a href="mailto:dspataro@corp.nac.net">dspataro@corp.nac.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
David,<br>
<br>
Try and add this to your XMR config<br>
<div class="Ih2E3d"><br>
router bgp<br>
local-as 64555<br>
neighbor <a href="http://172.16.0.5" target="_blank">172.16.0.5</a> remote-as 64555<br>
neighbor <a href="http://172.16.0.5" target="_blank">172.16.0.5</a> next-hop-self<br>
</div> neighbor <a href="http://172.16.0.5" target="_blank">172.16.0.5</a> update-source loopback 1 ---> add this<br>
<br>
Thanks,<br>
<font color="#888888">Dan<br>
</font><div><div></div><div class="Wj3C7c"><br>
-----Original Message-----<br>
From: <a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>] On Behalf Of David Ball<br>
Sent: Thursday, April 03, 2008 3:43 PM<br>
To: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
Subject: Re: [f-nsp] BGP between XMRs (or from XMR to Juniper)<br>
<br>
<br>
I suppose the BGP config might be helpful:<br>
<br>
router bgp<br>
local-as 64555<br>
neighbor <a href="http://172.16.0.5" target="_blank">172.16.0.5</a> remote-as 64555<br>
neighbor <a href="http://172.16.0.5" target="_blank">172.16.0.5</a> next-hop-self<br>
<br>
address-family ipv4 unicast<br>
exit-address-family<br>
<br>
address-family ipv4 multicast<br>
exit-address-family<br>
<br>
address-family ipv6 unicast<br>
exit-address-family<br>
<br>
address-family vpnv4 unicast<br>
exit-address-family<br>
end of BGP configuration<br>
<br>
<br>
<br>
On 03/04/2008, David Ball <<a href="mailto:davidtball@gmail.com">davidtball@gmail.com</a>> wrote:<br>
> I'm brand new to Foundry devices and thought I was doing well, but<br>
> somehow I'm stumbling at getting something as simple as BGP running<br>
> (iBGP), and I can't afford to tear much more hair out.<br>
> Is much else needed just to establish a session besides:<br>
><br>
> -ip connectivity (PtP and loopback IPs seen on both sides, all<br>
pingable)<br>
> -an IGP (or static routes) to advertise loopback IPs (using OSPF)<br>
> -local-as<br>
> -neighbor statement specifying a neighbor IP and remote-as<br>
><br>
> I know there are dozens of other settings I can (and will) employ,<br>
> but just to get a session up, should it require much more ?<br>
> When trying to establish a session to a Juniper m10 with full<br>
> traceoptions enabled, the m10 indicated:<br>
><br>
> Apr 3 10:30:20.868934 bgp_recv: peer <a href="http://172.16.0.4" target="_blank">172.16.0.4</a> (Internal AS 64555):<br>
> received unexpected EOF<br>
><br>
> where <a href="http://172.16.0.4" target="_blank">172.16.0.4</a> is the XMR. I (apparently) have full logging<br>
> enabled on the XMR, but it's telling me nothing (unless I'm not asking<br>
> it properly). The following shows logging enabled, but I see nothing<br>
> about BGP:<br>
><br>
> Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)<br>
> Buffer logging: level ACDMEINW, 32 messages logged<br>
> level code: A=alert C=critical D=debugging M=emergency E=error<br>
> I=informational N=notification W=warning<br>
><br>
><br>
> Any thoughts or nudges in the right direction would be appreciated.<br>
> Of all the things I plan to configure on the XMRs, I figured BGP would<br>
> be the easiest, but clearly I'm missing something. Thanks in advance.<br>
><br>
> David<br>
><br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</div></div></blockquote></div><br>