As path for Junos

Marco Paesani marco at paesani.it
Sat Mar 8 06:06:50 UTC 2014


Hi,
thanks for all info but with my 11.4R7.5 I cannot implement the check.
Regards,
Marco




2014-03-07 20:47 GMT+01:00 Pedro Cavaca <pmsac.nanog at gmail.com>:

>
>
>
> On 7 March 2014 19:44, Pedro Cavaca <pmsac.nanog at gmail.com> wrote:
>
>>
>>
>>
>> On 7 March 2014 19:26, Michael Loftis <mloftis at wgops.com> wrote:
>>
>>>
>>> http://www.juniper.net/techpubs/en_US/junos13.3/topics/usage-guidelines/policy-configuring-as-path-regular-expressions-to-use-as-routing-policy-match-conditions.html
>>>
>>> There's no backref support in the regex subset that juniper has chosen
>>> to implement, see
>>> http://juniper.cluepon.net/index.php/ER_Detect_AS-PATH_prepends
>>>
>>> - and I don't think Juniper has gone anywhere with that engineering
>>> request.
>>>
>>
>> Why wouldn't ".{3}" work, for this case?
>>
>>
>
> Or, to better align with the given Cisco example: ".* .{3} .*"
>
>
>>
>>> On Fri, Mar 7, 2014 at 3:31 AM, Marco Paesani <marco at paesani.it> wrote:
>>> > Hi Everyone,
>>> > I need a help to transform this Cisco IOS command:
>>> >
>>> > ip as-path access-list 50 permit _([0-9]+)_\1_\1_
>>> >
>>> > in Juniper JUNOS policy-options.
>>> > Best regards,
>>> > Marco
>>> > M. +39 348 6019349
>>>
>>>
>>>
>>> --
>>>
>>> "Genius might be described as a supreme capacity for getting its
>>> possessors
>>> into trouble of all kinds."
>>> -- Samuel Butler
>>>
>>>
>>
>


More information about the NANOG mailing list