rtr-feed2 is on our side. What I'm attempting to do is to pref rtr-feed1 over 
rtr-feed2 (hence the 200 metric).

I'm also seeing the metric of 0 on the "show ip bgp neighbor 10.151.0.82 
advertised-routes".



----
Matthew Huff       | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
http://www.ox.com  | Phone: 914-460-4039
aim: matthewbhuff  | Fax:   914-460-4139


-----Original Message-----
From: Peter Rathlev [mailto:[email protected]] 
Sent: Thursday, April 30, 2009 12:49 PM
To: Matthew Huff
Cc: [email protected]
Subject: Re: [c-nsp] BGP Med and outbound metric

On Thu, 2009-04-30 at 09:31 -0400, Matthew Huff wrote:
...
> neighbor 10.151.0.82 route-map setMED-LOW out
> neighbor 10.151.0.82 filter-list 10 out
> 
> route-map setMED-LOW permit 10
>  match ip address routemap_ecn
>  set metric 200
> 
> ip access-list standard routemap_ecn
>  permit 129.77.44.0
> 
> I've done the "clear ip bgp * soft" and have verified that the other
> side has seen the change (previously I had a block all access list on
> the distribute out so I know that the change has taken effect).
> 
> rtr-feed2#show ip bgp 129.77.44.0

Is the "rtr-feed2" your side or their side?

...
> Both outputs show a metric of 0. Any ideas?

You can only see the results of an outbound route-map on the other side.
The metric you see on your side is the one you box knows about.

Are you sure they would accept the MED setting? It's quite normal to
clear this inbound to enforce some standard policy.

Regards,
Peter


_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to