Re: RR & metrics not being propergated to ebgp peer from RR

In this case "we're not originating so explicitly state to neighbour right?"

thank you ever so much Brian sorry this may have been a basic question :/

On 1 March 2013 00:01, Brian McGahan <bmcgahan_at_ine.com> wrote:

> Apply the route-map out to the neighbor, from the CE to the PE.****
>
> ** **
>
> Brian McGahan, CCIE #8593 (R&S/SP/Security), CCDE #2013::13****
>
> bmcgahan_at_INE.com****
>
> ** **
>
> Internetwork Expert, Inc.****
>
> http://www.INE.com <http://www.ine.com/>****
>
> ** **
>
> *From:* Tony Singh [mailto:mothafungla_at_gmail.com]
> *Sent:* Thursday, February 28, 2013 5:47 PM
>
> *To:* Brian McGahan
> *Cc:* Brian Dennis; Cisco certification
> *Subject:* Re: RR & metrics not being propergated to ebgp peer from RR
> client****
>
> ** **
>
> ** **
>
> Hi Brian****
>
> ** **
>
> In initial post show ip bgp on PE it didn't match^^****
>
> ** **
>
> here are a few prefixes where after resetting the peering it sends an
> update to the ebgp peer****
>
> ** **
>
> if I read it correctly it sends an update on the two prefixes with MED of
> 200****
>
> ** **
>
> *Feb 28 23:31:00.578: BGP(0): 192.168.58.226 send UPDATE (prepend,
> chgflags: 0x820) 1.1.1.0/26, next 192.168.58.225, metric 200, extended
> community ****
>
> *Feb 28 23:31:00.578: BGP(0): 192.168.58.226 send UPDATE (prepend,
> chgflags: 0x820) 2.2.2.0/26, next 192.168.58.225, metric 200, extended
> community ****
>
> ** **
>
> ** **
>
> network 1.1.1.0 mask 255.255.255.192 route-map Not-Prefer****
>
> network 2.2.2.0 mask 255.255.255.192 route-map Not-Prefer****
>
> ** **
>
> route-map Not-Prefer permit 10****
>
> set metric 200****
>
> set local-preference 100****
>
> route-map Prefer permit 10****
>
> set metric 100****
>
> set local-preference 200****
>
> ** **
>
> ** **
>
> on PE****
>
> ** **
>
> *Feb 28 23:46:53.850: BGP(0): 192.168.58.225 rcvd 1.1.1.0/26****
>
> *Feb 28 23:46:53.850: BGP(0): 192.168.58.225 rcvd 2.2.2.0/26****
>
> ** **
>
> ** **
>
> sh ip bgp on PE is same as first post****
>
> ** **
>
> ** **
>
> ** **
>
> Tony****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On 28 February 2013 23:10, Brian McGahan <bmcgahan_at_ine.com> wrote:****
>
> Setting the MED manually should work. What does your config setting the
> MED look like on the CE? show ip bgp may not show you the value that you
> are setting outbound, you may need to look at the debug ip bgp update to
> see the attribute actually being set, or if you can get the show ip bgp
> output from the PE side youll be able to tell if the attribute is there.*
> ***
>
> ****
>
> Brian McGahan, CCIE #8593 (R&S/SP/Security), CCDE #2013::13****
>
> bmcgahan_at_INE.com****
>
> ****
>
> Internetwork Expert, Inc.****
>
> http://www.INE.com <http://www.ine.com/>****
>
> ****
>
> *From:* Tony Singh [mailto:mothafungla_at_gmail.com]
> *Sent:* Thursday, February 28, 2013 4:24 PM
> *To:* Brian McGahan
> *Cc:* Brian Dennis; Cisco certification****
>
>
> *Subject:* Re: RR & metrics not being propergated to ebgp peer from RR
> client****
>
> ****
>
> ****
>
> Hi Brian****
>
> ****
>
> Thanks but I have already tried this i.e same metrics/route-maps from
> CE doesn't work man!****
>
> ****
>
> Can't originate the prefixes on CE as I need them to come from behind the
> CE no IGP being used & don't really want to use one if I can get away with
> it..****
>
> ****
>
> ****
>
> ****
>
> BR****
>
> ****
>
> Tony****
>
> ****
>
> ****
>
> On 28 February 2013 22:15, Brian McGahan <bmcgahan_at_ine.com> wrote:****
>
> Originate the prefixes on the CE so that the IGP metric will be copied to
> MED. If that's not an option then you'll have to manually set the MED
> outbound on the CE towards the PE if you want to get it to propagate.
>
> HTH,
>
>
> Brian McGahan, CCIE #8593 (R&S/SP/Security), CCDE #2013::13
> bmcgahan_at_INE.com
>
> Internetwork Expert, Inc.
> http://www.INE.com****
>
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Tony Singh
> Sent: Thursday, February 28, 2013 2:36 PM
> To: Brian Dennis
> Cc: Cisco certification
> Subject: Re: RR & metrics not being propergated to ebgp peer from RR client
>
> Ok thanks for setting me straight Brain, what would be the best way to
> achieve the desired goal in that case or is it not possible
>
>
> On 28 February 2013 20:25, Brian Dennis <bdennis_at_ine.com> wrote:
>
> > MED is a non-transitive attribute which means in your case if the CE
> > learns a path via iBGP you can't pass the MED for that path to an eBGP
> > peer. If the CE originated the path into BGP itself then it would be
> > passed to its eBGP peer (PE).
> >
> > --
> > Brian Dennis, CCIEx5 #2210 (R&S/ISP-Dial/Security/SP/Voice)
> > bdennis_at_ine.com
> >
> > INE, Inc.
> > http://www.INE.com
> >
> >
> >
> >
> > On 2/28/13 3:05 PM, "Tony Singh" <mothafungla_at_gmail.com> wrote:
> >
> > >Hi Experts
> > >
> > >I may be missing some fundamental here but say the following
> > >
> > >SW>CE>PE
> > >
> > >SW is RR but also announcing several subnets into bgp process which
> > >reference preferred metrics
> > >
> > >these metric are advertised out to CE, CE see's these and advertises
> > >these metrics out to PE but PE does not see these metrics in bgp
> rib....?
> > >
> > >anything im doing wrong....
> > >
> > >
> > >
> > >CE#$ ipv4 unicast neighbors x.x.x.x advertised-routes BGP table
> > >version is 20, local router ID is x.x.x.x Status codes: s suppressed,
> > >d damped, h history, * valid, > best, i - internal,
> > > r RIB-failure, S Stale
> > >Origin codes: i - IGP, e - EGP, ? - incomplete
> > >
> > > Network Next Hop Metric LocPrf Weight Path
> > >*>ix.x.x.x x.x.x.x 200 100 0 i
> > >*>ix.x.x.x x.x.x.x 200 100 0 i
> > >*>ix.x.x.x
> > > x.x.x.x 200 100 0 i
> > >*>ix.x.x.x x.x.x.x 100 200 0 i
> > >*>ix.x.x.x
> > > x.x.x.x 100 200 0 i
> > >*> x.x.x.x
> > > 0.0.0.0 100 200 32768 i
> > >*> x.x.x.x
> > > 0.0.0.0 100 200 32768 i
> > >*> x.x.x.x
> > > 0.0.0.0 100 200 32768 i
> > >*>ix.x.x.x
> > > x.x.x.x 100 200 0 i
> > >
> > >Total number of prefixes 9
> > >
> > >
> > >
> > >PE#show ip bgp
> > >BGP table version is 28, local router ID is x.x.x.x Status codes: s
> > >suppressed, d damped, h history, * valid, > best, i - internal,
> > > r RIB-failure, S Stale
> > >Origin codes: i - IGP, e - EGP, ? - incomplete
> > >
> > > Network Next Hop Metric LocPrf Weight Path
> > >* x.x.x.x x.x.x.x 0 xxxxx i
> > >*> x.x.x.x 0 xxxxx i
> > >* x.x.x.x x.x.x.x 0 xxxxx i
> > >*> x.x.x.x 0 xxxxx i
> > >* x.x.x.x
> > > x.x.x.x 0 xxxxx i
> > >*> x.x.x.x 0 xxxxx i
> > >* x.x.x.x x.x.x.x 0 xxxxx i
> > >*> x.x.x.x 0 xxxxx i
> > >* x.x.x.x
> > > x.x.x.x 100 0 xxxxx i
> > >* x.x.x.x 0 xxxxx i
> > >*> 0.0.0.0 0 xxxxx i
> > >* x.x.x.x
> > > x.x.x.x 0 xxxxx i
> > >* x.x.x.x 100 0 xxxxx i
> > >*> 0.0.0.0 0 xxxxx i
> > >
> > >
> > >Blogs and organic groups at http://www.ccie.net
> > >
> > >_____________________________________________________________________**
> **
>
> > >__ Subscription information may be found at:****
>
> > >http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
> ****
>
> ****
>
> ** **

Blogs and organic groups at http://www.ccie.net
Received on Fri Mar 01 2013 - 00:29:43 ART