Stephane,

> As u said, ^(200)+$ will match my ASPATHs but not only ...

I am afraid that was not what I said :)

> However, when I configure it, this expression doesn't match ASPATH
prepended
> like "200 200 200" (but 200 is present !). The not prepended ASPATH (200
> only) is matched. I don't understand this behavior.
>

As I said, ^(200)+$ would match 200 ONLY, we only have 2 bytes for the
as-number, 200200 will not show up in a router.

When you give IOS "200  200 200", it sees the spaces between the numbers,
^(200)+$ tells it to match some 200s without anything else in between them,
space is something.
Since you have ^ and $, it can not have anything before and after these 200s
either.
After reading the first 200, it expects the next thing is either 2 or end of
line, but it sees the space following the first 200 in "200  200 200",
that's a no-no.

Kent
>
> ""Kent Yu""  a icrit dans le message de news:
> [EMAIL PROTECTED]
> > Stephane,
> >
> > ^(200)+$  matches  200 or 200200 etc.. Of course, in case of as-path, it
> > will only find 200.
> >
> > You want to use _ to match the space between the as-nums, so IOS will
try
> to
> > match the whole as-path.
> >
> > HTH
> > Kent
> > ""Stephane Litkowski""  wrote in message
> > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > Hi all,
> > >
> > > I'm trying to find a regexp to match AS PATH including AS200 only, but
> > AS200
> > > can be contained more than one time (AS PATH prepending).
> > > Example :
> > > 200 -> Match
> > > 200 200 -> Match
> > > 200 200 200 -> Match
> > > 200 200 200 300 -> Don't Match
> > >
> > > I tried to use this regexp : ^(200)+$ but it doesn't work, why ?
> > > However, the regexps : ^(200_)+$ seems to work.
> > >
> > > Can someone explain me why the first regexp doesn't work ?
> > >
> > > thanks.
> > >
> > > Stephane




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=53978&t=53956
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to