Mailing List Archive

>
> >
> > I'm having troubles coming up with a regexp to show me just directly
> > connected peers. The best I've come up with is :
> >
> > sh ip bgp regexp ^(5555)+
> >
> > which covers directly connected peers that prepend their path to me.
> > However, is there a regexp that'll show me all, without having to have
one
> > for each peer?
>
> sh ip bgp ^(5555)+_[0-9]*$
>

I was looking for a regex that would replace the need to mention every
directly attached AS, not directly attached and their downstreams.

For instance, I have peers AS5555 and AS4444 and AS3333. Instead of three
seperate regexp's, can I do it all in one?

try this:

sh ip bgp regexp ^[0-9]+$


i think that is what you are looking for


On Mon, 12 Aug 2002, matthew zeier wrote:

> Date: Mon, 12 Aug 2002 14:48:14 -0700
> From: matthew zeier <mrz@intelenet.net>
> To: cisco-nsp@puck.nether.net
> Subject: [nsp] BGP regex - directly connected routes ?
>
>
> I'm having troubles coming up with a regexp to show me just directly
> connected peers. The best I've come up with is :
>
> sh ip bgp regexp ^(5555)+
>
> which covers directly connected peers that prepend their path to me.
> However, is there a regexp that'll show me all, without having to have one
> for each peer?
>
> Thanks.
>
>
> --
> matthew zeier | "In mathematics you don't understand
> InteleNet Communications, Inc. | things. You just get used to them."
> (949) 784-7904 | - John von Newmann
>
>
> _______________________________________________
> cisco-nsp mailing list real_name)s@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

-sean
Spoon!

though I guess that doesn't cover prepended routes...
oh well.



>
> try this:
>
> sh ip bgp regexp ^[0-9]+$
>
>
> i think that is what you are looking for
>
>
> On Mon, 12 Aug 2002, matthew zeier wrote:
>
> > Date: Mon, 12 Aug 2002 14:48:14 -0700
> > From: matthew zeier <mrz@intelenet.net>
> > To: cisco-nsp@puck.nether.net
> > Subject: [nsp] BGP regex - directly connected routes ?
> >
> >
> > I'm having troubles coming up with a regexp to show me just directly
> > connected peers. The best I've come up with is :
> >
> > sh ip bgp regexp ^(5555)+
> >
> > which covers directly connected peers that prepend their path to me.
> > However, is there a regexp that'll show me all, without having to have one
> > for each peer?
> >
> > Thanks.
> >
> >
> > --
> > matthew zeier | "In mathematics you don't understand
> > InteleNet Communications, Inc. | things. You just get used to them."
> > (949) 784-7904 | - John von Newmann
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list real_name)s@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>
> -sean
> Spoon!
>
>

-sean
Spoon!

----- Original Message -----
From: "matthew zeier" <mrz@intelenet.net>
To: <cisco-nsp@puck.nether.net>
Sent: Monday, August 12, 2002 4:48 PM
Subject: [nsp] BGP regex - directly connected routes ?


>
> I'm having troubles coming up with a regexp to show me just directly
> connected peers. The best I've come up with is :
>
> sh ip bgp regexp ^(5555)+
>
> which covers directly connected peers that prepend their path to me.
> However, is there a regexp that'll show me all, without having to have one
> for each peer?

sh ip bgp ^(5555)+_[0-9]*$

> Thanks.
>
>
> --
> matthew zeier | "In mathematics you don't
understand
> InteleNet Communications, Inc. | things. You just get used to
them."
> (949) 784-7904 | - John von Newmann
>
>
> _______________________________________________
> cisco-nsp mailing list real_name)s@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

>
> ----- Original Message -----
> From: "matthew zeier" <mrz@intelenet.net>
> To: <cisco-nsp@puck.nether.net>
> Sent: Monday, August 12, 2002 4:48 PM
> Subject: [nsp] BGP regex - directly connected routes ?
>
>
> >
> > I'm having troubles coming up with a regexp to show me just directly
> > connected peers. The best I've come up with is :
> >
> > sh ip bgp regexp ^(5555)+
> >
> > which covers directly connected peers that prepend their path to me.
> > However, is there a regexp that'll show me all, without having to have
one
> > for each peer?
>
> sh ip bgp ^(5555)+_[0-9]*$

Sorry, I forgot the 'regexp'

Obviously that would be, show ip bgp regexp ^(5555)+_[0-9]*$

>
> > Thanks.
> >
> >
> > --
> > matthew zeier | "In mathematics you don't
> understand
> > InteleNet Communications, Inc. | things. You just get used to
> them."
> > (949) 784-7904 | - John von Newmann
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list real_name)s@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>

I don't think the cisco regexp supports match recall so you can't
construct a regexp that says "repeat what matched." However..


> I was looking for a regex that would replace the need to mention every
> directly attached AS, not directly attached and their downstreams.
>
> For instance, I have peers AS5555 and AS4444 and AS3333. Instead of three
> seperate regexp's, can I do it all in one?

Is it that you don't want to enumerate the AS's, or that you don't want
multiple regexps... 'cuz there's a difference. I think (tho somebody
may know better) the best you can do is list paths with ONLY your
neighbor AS's in them, but you'd have to enumerate the ones you want.
That would be OK if you can assume you wouldn't be seeing one of your
neighbor AS's in a path from another one of your neighbors, but that
may not be the case.

Anyway something like:

show ip bgp regexp ^(5555_|4444_|3333_)+$

would, I think, show you paths with only those ASs in them. As I say,
if you don't expect to see one neighbor's AS in a path learned from
another, that would probably be sufficient.

mm