[f-nsp] BGP between XMRs (or from XMR to Juniper)

David Ball davidtball at gmail.com
Fri Apr 4 11:07:35 EDT 2008


  Thanks Andreas.  Some of the details not included in my original
post were that the XMRs will hopefully (if testing goes well) become a
part of an existing MPLS network (currently all Juniper T-series)
consisting of LDP and a full mesh of RSVP-TE LSPs.  With such a
topology it seemed as though loopback peering (LSPs are also built
btwn loopbacks) would be easiest.
  Thanks again.  And if anyone has run into stumbling blocks using
Juniper & Foundry together in an MPLS deployment, I wouldn't mind
hearing your tales.

David


On 04/04/2008, Andreas Larsen <andreas at larsen.pl> wrote:
> 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 1.0.0.0/8. 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.
>
> Regards Andreas
>
>
> On Thu, Apr 3, 2008 at 10:06 PM, Dan Spataro <dspataro at corp.nac.net> wrote:
> > David,
> >
> > Try and add this to your XMR config
> >
> >
> > router bgp
> >  local-as 64555
> >  neighbor 172.16.0.5 remote-as 64555
> >  neighbor 172.16.0.5 next-hop-self
> >  neighbor 172.16.0.5 update-source loopback 1 ---> add this
> >
> > Thanks,
> > Dan
> >
> >
> >
> >
> > -----Original Message-----
> > From: foundry-nsp-bounces at puck.nether.net
> > [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of
> David Ball
> > Sent: Thursday, April 03, 2008 3:43 PM
> > To: foundry-nsp at puck.nether.net
> > Subject: Re: [f-nsp] BGP between XMRs (or from XMR to Juniper)
> >
> >
> >  I suppose the BGP config might be helpful:
> >
> > router bgp
> >  local-as 64555
> >  neighbor 172.16.0.5 remote-as 64555
> >  neighbor 172.16.0.5 next-hop-self
> >
> >  address-family ipv4 unicast
> >  exit-address-family
> >
> >  address-family ipv4 multicast
> >  exit-address-family
> >
> >  address-family ipv6 unicast
> >  exit-address-family
> >
> >  address-family vpnv4 unicast
> >  exit-address-family
> > end of BGP configuration
> >
> >
> >
> > On 03/04/2008, David Ball <davidtball at gmail.com> wrote:
> > >  I'm brand new to Foundry devices and thought I was doing well, but
> > > somehow I'm stumbling at getting something as simple as BGP running
> > > (iBGP), and I can't afford to tear much more hair out.
> > >  Is much else needed just to establish a session besides:
> > >
> > > -ip connectivity (PtP and loopback IPs seen on both sides, all
> > pingable)
> > > -an IGP (or static routes) to advertise loopback IPs (using OSPF)
> > > -local-as
> > > -neighbor statement specifying a neighbor IP and remote-as
> > >
> > >  I know there are dozens of other settings I can (and will) employ,
> > > but just to get a session up, should it require much more ?
> > >  When trying to establish a session to a Juniper m10 with full
> > > traceoptions enabled, the m10 indicated:
> > >
> > > Apr  3 10:30:20.868934 bgp_recv: peer 172.16.0.4 (Internal AS 64555):
> > > received unexpected EOF
> > >
> > >  where 172.16.0.4 is the XMR.  I (apparently) have full logging
> > > enabled on the XMR, but it's telling me nothing (unless I'm not asking
> > > it properly).  The following shows logging enabled, but I see nothing
> > > about BGP:
> > >
> > > Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
> > >    Buffer logging: level ACDMEINW, 32 messages logged
> > >    level code: A=alert C=critical D=debugging M=emergency E=error
> > >                I=informational N=notification W=warning
> > >
> > >
> > > Any thoughts or nudges in the right direction would be appreciated.
> > > Of all the things I plan to configure on the XMRs, I figured BGP would
> > > be the easiest, but clearly I'm missing something.  Thanks in advance.
> > >
> > > David
> > >
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
> >
>
>



More information about the foundry-nsp mailing list