Re: [j-nsp] Policy-statement to match on metrics less than, greater than, or within a range

2015-08-27 Thread Phil Rosenthal
On Aug 27, 2015, at 7:15 AM, Alexander Arseniev arsen...@btinternet.com wrote: There is a floor for MED and it is 0. What You could do is : term 1 then { metric subtract 1000; next term } term 2 from metric 0; then { local-preference 100; accept } You won't be able to keep the

Re: [j-nsp] Policy-statement to match on metrics less than, greater than, or within a range

2015-08-27 Thread Alexander Arseniev
There is a floor for MED and it is 0. What You could do is : term 1 then { metric subtract 1000; next term } term 2 from metric 0; then { local-preference 100; accept } You won't be able to keep the original MED though :-( HTH Thanks Alex On 27/08/2015 05:40, Mark Tinka wrote: On 27/Aug/15

[j-nsp] Policy-statement to match on metrics less than, greater than, or within a range

2015-08-26 Thread Phil Rosenthal
Hello all, On Cisco, it is possible to write a route policy as such: route-policy test if med le 1000 then set local-preference 100 endif end-policy Is there any way to do the same thing with Juniper? It seems that the “from metric” statement only accepts a static value (comparable

Re: [j-nsp] Policy-statement to match on metrics less than, greater than, or within a range

2015-08-26 Thread Mark Tinka
On 27/Aug/15 01:55, Phil Rosenthal wrote: Hello all, On Cisco, it is possible to write a route policy as such: route-policy test if med le 1000 then set local-preference 100 endif end-policy Is there any way to do the same thing with Juniper? It seems that the “from