[j-nsp] BGP Configuration on J6350
Eric Van Tol
eric at atlantech.net
Wed Oct 3 12:43:35 EDT 2007
Yikes - how embarrassing! I am so used to dealing with route
reflection, I forgot about this. We all have our days, I suppose...
-evt
> -----Original Message-----
> From: Stacy W. Smith [mailto:stacy at acm.org]
> Sent: Wednesday, October 03, 2007 12:20 PM
> To: Eric Van Tol
> Cc: Matthew Crocker; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] BGP Configuration on J6350
>
> Sounds like it's working as designed. Remember that a BGP neighbor
> only advertises the routes it's selected as best. In your case it
> sounds like the J6350 has only selected 6141 prefixes that it
> received from ISP3 as the best path, and is therefore only re-
> advertising those 6141 prefixes to the GSR. Presumably the J6350 has
> selected the path via the GSR for the remainder of its prefixes. If
> you want a different behavior you would need to modify which paths
> are being preferred via policy on one or both of your BGP-speaking
> routers.
>
> --Stacy
>
> On 3 Oct 2007, at 10:08 AM, Eric Van Tol wrote:
>
> > Try doing a 'show route advertising-protocol bgp x.x.x.x', where
> > x.x.x.x
> > is the GSR address. It's quite possible that it is already
> sending a
> > full table and the GSR just isn't showing the inactive routes. I
> > can't
> > remember what the default behavior is of Cisco, in terms of showing
> > routes received in 'show ip bgp summary'.
> >
> > If you want to be sure, however, you can do the following:
> >
> > policy-statement internal {
> > term term1 {
> > from protocol bgp;
> > }
> > then nexthop self;
> > }
> > }
> >
> > That will re-advertise all routes learned through BGP to any peer on
> > which you've applied this policy.
> >
> > -evt
> >
> >
> >> -----Original Message-----
> >> From: juniper-nsp-bounces at puck.nether.net
> >> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> >> Matthew Crocker
> >> Sent: Wednesday, October 03, 2007 12:03 PM
> >> To: juniper-nsp at puck.nether.net
> >> Subject: [j-nsp] BGP Configuration on J6350
> >>
> >>
> >> Hello,
> >>
> >> I'm new to JUNOS please bear with me.
> >>
> >> I have the following network setup
> >>
> >> ISP1 (AS7018) connected via OC-3 to GSR
> >> ISP2 (AS1239) connected via GigE to GSR
> >> ISP3 (AS16657) connected via GigE to J6350
> >>
> >> I have a GigE between the J6350 & GSR, My AS7849
> >>
> >> BGP with full tables running to all 3 ISPs
> >>
> >> ISP1 shows 227638 prefixes received (GSR)
> >> ISP2 shows 228612 prefixes received (GSR)
> >> ISP3 shows 227904 prefixes received (GSR)
> >>
> >> The J6350 is seeing 225992 prefixes from the GSR
> >> The GSR is only seeing 6141 prefixes from the J6350
> >>
> >> How do I configure the J6350 to send the full table to its
> IGP peer?
> >>
> >> show bgp summary shows
> >> show bgp summary
> >> Groups: 2 Peers: 2 Down peers: 0
> >> Table Tot Paths Act Paths Suppressed History Damp
> >> State Pending
> >> inet.0 453826 229366 0 0
> >> 0 0
> >> Peer AS InPkt OutPkt OutQ
> Flaps Last Up/
> >> Dwn State|#Active/Received/Damped...
> >> XXXXXXXX 7849 72875 14981 0 6 45:22
> >> 223250/225922/0 0/0/0
> >> XXXXXXXX 16657 41920 113 0 2 53:53
> >> 6116/227904/0 0/0/0
> >>
> >> show configuration protocols bgp
> >> path-selection always-compare-med;
> >> local-as 7849;
> >> group internal-within-AS7849 {
> >> type internal;
> >> local-address <ge-0/0/0.0 IP address>;
> >> export internal;
> >> graceful-restart;
> >> neighbor <GSR IP ADDRESS>;
> >> }
> >> group FiberTech {
> >> type external;
> >> export pl-announce;
> >> peer-as 16657;
> >> neighbor <FIBERTECH IP ADDRESS>;
> >> }
> >>
> >> show policy internal
> >> Policy internal:
> >> Term term1:
> >> then nexthop self
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
More information about the juniper-nsp
mailing list