[c-nsp] Match on MED in BGP inbound route-map

Oliver Boehmer (oboehmer) oboehmer at cisco.com
Wed Apr 27 02:18:07 EDT 2005


You can't currently match on BGP MED inbound, and we should print an
error message when you try this with a policy-list as well. Currently,
"match metric" can only be used on outbound BGP route-maps..

	oli
 

Ravi Vaidyanathan <> wrote on Tuesday, April 26, 2005 6:45 PM:

> Aaron,
> 
> Thanks for your response. I did try match metric first, here's what
> it told me:
> 
> #(config-route-map)#match metric 10
> % "IN-COMM" used as BGP inbound route-map, metric match not supported
> 
> Appears it only supports an IGRP metric in this context. At least at
> the IOS version I am running (12.2xTx).
> 
> thanks,
> Ravi
> 
>> -----Original Message-----
>> From: Aaron Weintraub [mailto:aaronw at distracted.org]
>> Sent: Tuesday, April 26, 2005 12:35 PM
>> To: Ravi Vaidyanathan
>> Subject: Re: [c-nsp] Match on MED in BGP inbound route-map
>> 
>> 
>> On Tue, Apr 26, 2005 at 12:25:54PM -0400, Ravi Vaidyanathan wrote:
>>> 
>>> I am setting up a configuration where I would like to match on the
>>> incoming MED values from my peer AS. I am using ip policy-list
>>> configuration to match on the MED values (sanitized configuration
>>> snapshot below), but am having trouble getting the communities set
>>> based on the incoming MED (it appears to ignore the incoming MED
>>> and simply execute the set condition in the first route-map entry).
>> 
>> You want 'match metric', not match policy-list.. that's a completely
>> different matching system and not applicable for what you're trying
>> to do. 
>> 
>> aw
>> 
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list