[j-nsp] BGP Origin Issue

Discussion:

Borchers, Mark M.

2007-04-19 18:22:01 UTC

We have a downstream BGP site announcing 19 prefixes from a Cisco router.
Eleven of the prefixes were configured with network statements in his BGP
config. The remaining nine were statically null-routed and being
redistributed into BGP. Thus, those nine appeared to us on an M20 as origin
incomplete. None were advertised to other peers.

Just wondering if this is working as designed or if we have a Juniper-Cisco
BGP interoperability issue. We are running Junos 7.6R2.6. I am aware of
the role of origin in BGP path selection, but these examples include routes
that are not being announced via any other path.

Mark Borchers

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.

Ebben Aries

2007-04-19 19:58:38 UTC

Permalink

When you redistribute into BGP, the routes will show as imcomplete. I believe
that is cisco default behavior on redistribution. To circumvent the issue,
you can create a route-map w/ a 'set origin' on outbound announcements.

Post by Borchers, Mark M.
We have a downstream BGP site announcing 19 prefixes from a Cisco router.
Eleven of the prefixes were configured with network statements in his BGP
config. The remaining nine were statically null-routed and being
redistributed into BGP. Thus, those nine appeared to us on an M20 as
origin incomplete. None were advertised to other peers.
Just wondering if this is working as designed or if we have a Juniper-Cisco
BGP interoperability issue. We are running Junos 7.6R2.6. I am aware of
the role of origin in BGP path selection, but these examples include routes
that are not being announced via any other path.
Mark Borchers
NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Borchers, Mark M.

2007-04-19 20:02:04 UTC

Permalink

Thanks, but what really has me scratching my head is whether it is a feature
or a bug that the Juniper does not re-advertise prefixes with
origin-incomplete to other peers?

Post by Ebben Aries
When you redistribute into BGP, the routes will show as
imcomplete. I believe
that is cisco default behavior on redistribution. To
circumvent the issue,
you can create a route-map w/ a 'set origin' on outbound
announcements.

Post by Borchers, Mark M.
We have a downstream BGP site announcing 19 prefixes from a

Cisco router.

Post by Borchers, Mark M.
Eleven of the prefixes were configured with network

statements in his BGP

Post by Borchers, Mark M.
config. The remaining nine were statically null-routed and being
redistributed into BGP. Thus, those nine appeared to us on

an M20 as

Post by Borchers, Mark M.
origin incomplete. None were advertised to other peers.
Just wondering if this is working as designed or if we have

a Juniper-Cisco

Post by Borchers, Mark M.
BGP interoperability issue. We are running Junos 7.6R2.6.

I am aware of

Post by Borchers, Mark M.
the role of origin in BGP path selection, but these

examples include routes

Post by Borchers, Mark M.
that are not being announced via any other path.
Mark Borchers
NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.

Any use, copying

Post by Borchers, Mark M.
or disclosure by any other person is strictly prohibited.

If you have

Post by Borchers, Mark M.
received this transmission in error, please notify the

sender via e-mail.

Post by Borchers, Mark M.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Ebben Aries

2007-04-19 20:05:32 UTC

Permalink

Hmm, I have had many cases of re-advertisement of prefixes w/ "origin
incomplete". As long as it is marked as a valid route, it should be
available for announcement and depending on how your policies are setup. I
to am running 7.6R2.6

Post by Borchers, Mark M.
Thanks, but what really has me scratching my head is whether it is a
feature or a bug that the Juniper does not re-advertise prefixes with
origin-incomplete to other peers?

Post by Borchers, Mark M.
We have a downstream BGP site announcing 19 prefixes from a

Cisco router.

Post by Borchers, Mark M.
Eleven of the prefixes were configured with network

statements in his BGP

Post by Borchers, Mark M.
config. The remaining nine were statically null-routed and being
redistributed into BGP. Thus, those nine appeared to us on

an M20 as

Post by Borchers, Mark M.
origin incomplete. None were advertised to other peers.
Just wondering if this is working as designed or if we have

a Juniper-Cisco

Post by Borchers, Mark M.
BGP interoperability issue. We are running Junos 7.6R2.6.

I am aware of

Post by Borchers, Mark M.
the role of origin in BGP path selection, but these

examples include routes

Any use, copying

Post by Borchers, Mark M.
or disclosure by any other person is strictly prohibited.

If you have

Post by Borchers, Mark M.
received this transmission in error, please notify the

sender via e-mail.

Post by Borchers, Mark M.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

--
Ebben Aries
Lead Network Engineer
United Communications, Inc.
389 SW Scalehouse Ct. Suite 100
Bend, OR ?97702
Office: 541.322.1407
Fax: 541.322.1417
earies at uci.net

Phil Bedard

2007-04-19 20:13:29 UTC

Permalink

Are there any other attribute differences between the routes? What does
a show route detail or show route extensive give you? The origin
should
not affect re-advertisement of the route.

Phil

Post by Borchers, Mark M.
Thanks, but what really has me scratching my head is whether it is a feature
or a bug that the Juniper does not re-advertise prefixes with
origin-incomplete to other peers?

Post by Borchers, Mark M.
We have a downstream BGP site announcing 19 prefixes from a

Cisco router.

Post by Borchers, Mark M.
Eleven of the prefixes were configured with network

statements in his BGP

Post by Borchers, Mark M.
config. The remaining nine were statically null-routed and being
redistributed into BGP. Thus, those nine appeared to us on

an M20 as

Post by Borchers, Mark M.
origin incomplete. None were advertised to other peers.
Just wondering if this is working as designed or if we have

a Juniper-Cisco

Post by Borchers, Mark M.
BGP interoperability issue. We are running Junos 7.6R2.6.

I am aware of

Post by Borchers, Mark M.
the role of origin in BGP path selection, but these

examples include routes

Any use, copying

Post by Borchers, Mark M.
or disclosure by any other person is strictly prohibited.

If you have

Post by Borchers, Mark M.
received this transmission in error, please notify the

sender via e-mail.

Post by Borchers, Mark M.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-
mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Phil Bedard
philxor at gmail.com

Ebben Aries

2007-04-19 20:02:15 UTC

Permalink

As a follow up, here is a cisco doc explaining the fact.

http://www.cisco.com/warp/public/459/bgp-toc.html

Static Routes and Redistribution

You can always use static routes to originate a network or a subnet. The only
difference is that BGP considers these routes to have an origin that is
incomplete, or unknown. You can accomplish the same result that the example
in the Redistribution section accomplished with this:

--
Ebben

--
Ebben Aries
Lead Network Engineer
United Communications, Inc.
389 SW Scalehouse Ct. Suite 100
Bend, OR ?97702
Office: 541.322.1407
Fax: 541.322.1417
earies at uci.net

Warren Kumari

2007-04-19 20:17:53 UTC

Permalink

Nope, this is working as designed -- the name "incomplete" is a
little unintuitive...

Post by Borchers, Mark M.
We are running Junos 7.6R2.6. I am aware of
the role of origin in BGP path selection, but these examples
include routes
that are not being announced via any other path.

I am a little confused - are you saying that the ones that were
configured with the network statement are working correctly and that
the ones that arrive from the redistribution are not? Or that none or
working?

I would suggest checking that you are really getting all the routes:
show route receive-protocol bgp <neighbor> detail
show route protocol bgp <one of each of the route types> all detail

and look at the State: and Inactive reasons:

W

Post by Borchers, Mark M.
Mark Borchers
NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-
mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

--
"Does Emacs have the Buddha nature? Why not? It has bloody well
everything else?"

Chuck Anderson

2007-04-19 20:20:51 UTC

Permalink

Post by Warren Kumari
show route receive-protocol bgp <neighbor> detail
show route protocol bgp <one of each of the route types> all detail

Also, see if you have any hidden routes:

show route hidden detail

Angel Bardarov

2007-04-19 20:19:39 UTC

Permalink

Post by Borchers, Mark M.
Thus, those nine appeared to us on an M20 as origin
incomplete. None were advertised to other peers.

In that case the problematic routes are present in the routing table of
your M20. Do you have export policies to you iBGP peers? Can you post
the output from "show route advertising-protocol bgp ..."

Angel

Borchers, Mark M.

2007-04-19 20:40:12 UTC

Permalink

Thanks to all responders. To summarize request for further info:

1. We do *not* have any origin attributes contained in any inbound or
outbound policy statements. We are filtering inbound from downstreams only
by prefix. Outbound policy is a mix of as-path and prefix terms. In this
case, first match would be on an as-path term.

2. We are receiving all advertisements from the downstream site, both
origin-incomplete and origin-internal.

3. All routes are being advertised and received in IBGP ok.

4. After doing "show routes adv bgp" it does appear that we are announcing
all prefixes including origin-incomplete. It's possible they are being
rejected by our peers, although I'm pretty confident that most should be
accepting them.

Based on the fact that nobody has said "Yo dummy, JunOS never re-advertises
prefixes with origin incomplete", I'm going to do more detailed checking on
the looking glasses.

-----Original Message-----
From: Angel Bardarov [mailto:angel.bardarov at btc-net.bg]
Sent: Thursday, April 19, 2007 3:20 PM
To: Borchers, Mark M.
Cc: 'juniper-nsp at puck.nether.net'
Subject: Re: [j-nsp] BGP Origin Issue

Post by Borchers, Mark M.
Thus, those nine appeared to us on an M20 as origin
incomplete. None were advertised to other peers.

In that case the problematic routes are present in the
routing table of
your M20. Do you have export policies to you iBGP peers? Can you post
the output from "show route advertising-protocol bgp ..."
Angel

Phil Bedard

2007-04-19 20:49:41 UTC

Permalink

As an aside, you can use network statements with the static routes in
place, if
you control that box.
Perhaps using a test prefix you can test the behaviour and figure out
if the origin
attribute plays a part, which it shouldn't.

Phil

Post by Borchers, Mark M.
1. We do *not* have any origin attributes contained in any inbound or
outbound policy statements. We are filtering inbound from
downstreams only
by prefix. Outbound policy is a mix of as-path and prefix terms.
In this
case, first match would be on an as-path term.
2. We are receiving all advertisements from the downstream site, both
origin-incomplete and origin-internal.
3. All routes are being advertised and received in IBGP ok.
4. After doing "show routes adv bgp" it does appear that we are announcing
all prefixes including origin-incomplete. It's possible they are being
rejected by our peers, although I'm pretty confident that most
should be
accepting them.
Based on the fact that nobody has said "Yo dummy, JunOS never re-
advertises
prefixes with origin incomplete", I'm going to do more detailed checking on
the looking glasses.

Post by Borchers, Mark M.
Thus, those nine appeared to us on an M20 as origin
incomplete. None were advertised to other peers.

In that case the problematic routes are present in the
routing table of
your M20. Do you have export policies to you iBGP peers? Can you post
the output from "show route advertising-protocol bgp ..."
Angel

Phil Bedard
philxor at gmail.com

Borchers, Mark M.

2007-04-19 21:02:45 UTC

Permalink

I'll apologize for posting a red herring to the list. Looking further I
believe that by diabolical coincidence, the origin-incomplete routes were
also carrying prepends that prevented them from showing up as active routes
anywhere. The ones that were visible on the Internet were in some cases not
prepended and in other cases more-specifics that weren't being announced
elsewhere. I jumped on the origin attribute too eagerly.

Mark

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

Jeff Tantsura

2007-04-20 09:41:25 UTC

Permalink

Hi,

Actually there's a situation where you could get hit by differences in
"origin" setup.
By default Cisco, when aggregates, marks origin as IGP while Juniper does
incomplete. If you have got more than 1 BGP sessions with a same peer and
they aggregate on the peering routers where 1 is Cisco and another is
juniper... guess what :)
That's why resetting of origin to IGP on your borders is a good idea.

Just my .02 cent
Jeff

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
bounces at puck.nether.net] On Behalf Of Borchers, Mark M.
Sent: donderdag 19 april 2007 23:03
To: 'juniper-nsp at puck.nether.net'
Subject: Re: [j-nsp] BGP Origin Issue
I'll apologize for posting a red herring to the list. Looking further I
believe that by diabolical coincidence, the origin-incomplete routes were
also carrying prepends that prevented them from showing up as active routes
anywhere. The ones that were visible on the Internet were in some cases not
prepended and in other cases more-specifics that weren't being announced
elsewhere. I jumped on the origin attribute too eagerly.
Mark

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Jeff Tantsura

2007-04-20 09:43:21 UTC

Permalink

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Phil Bedard

2007-04-20 13:16:27 UTC

Permalink

Yeah the Cisco is a little strange in those regards, the only time it
will not
use IGP for the origin code in an aggregate-address is if you are
using as-set
and one of the contributing routes is incomplete...

I second the policy of resetting the origin to IGP to take that out
of the possible path selection. Using a route-map on the
redistribute, you
can set that policy on import into the BGP table...

Phil

Post by Jeff Tantsura
Hi,
Actually there's a situation where you could get hit by differences in
"origin" setup.
By default Cisco, when aggregates, marks origin as IGP while
Juniper does
incomplete. If you have got more than 1 BGP sessions with a same peer and
they aggregate on the peering routers where 1 is Cisco and another is
juniper... guess what :)
That's why resetting of origin to IGP on your borders is a good idea.
Just my .02 cent
Jeff

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
bounces at puck.nether.net] On Behalf Of Borchers, Mark M.
Sent: donderdag 19 april 2007 23:03
To: 'juniper-nsp at puck.nether.net'
Subject: Re: [j-nsp] BGP Origin Issue
I'll apologize for posting a red herring to the list. Looking further I
believe that by diabolical coincidence, the origin-incomplete
routes were
also carrying prepends that prevented them from showing up as active routes
anywhere. The ones that were visible on the Internet were in some
cases
not
prepended and in other cases more-specifics that weren't being announced
elsewhere. I jumped on the origin attribute too eagerly.
Mark

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Phil Bedard
philxor at gmail.com

Jeff Tantsura

2007-04-20 14:27:07 UTC

Permalink

Hi,

My bad, described behaviour was true back in 2001.
In nowadays both cisco and juniper set by default origin for aggregated
routes to IGP.

Jeff

P.S. Sorry for all the mails, bloody outlook :)

-----Original Message-----
From: Phil Bedard [mailto:philxor at gmail.com]
Sent: vrijdag 20 april 2007 15:16
To: jeff.tantsura at sscplus.nl
Cc: 'Borchers, Mark M.'; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP Origin Issue
Yeah the Cisco is a little strange in those regards, the only time it
will not
use IGP for the origin code in an aggregate-address is if you are
using as-set
and one of the contributing routes is incomplete...
I second the policy of resetting the origin to IGP to take that out
of the possible path selection. Using a route-map on the
redistribute, you
can set that policy on import into the BGP table...
Phil

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
bounces at puck.nether.net] On Behalf Of Borchers, Mark M.
Sent: donderdag 19 april 2007 23:03
To: 'juniper-nsp at puck.nether.net'
Subject: Re: [j-nsp] BGP Origin Issue
I'll apologize for posting a red herring to the list. Looking further I
believe that by diabolical coincidence, the origin-incomplete routes were
also carrying prepends that prevented them from showing up as active routes
anywhere. The ones that were visible on the Internet were in some
cases
not
prepended and in other cases more-specifics that weren't being announced
elsewhere. I jumped on the origin attribute too eagerly.
Mark

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Phil Bedard
philxor at gmail.com

Jeff Tantsura

2007-04-20 14:28:36 UTC

Permalink

Hi,

My bad, described behaviour was true back in 2001.
In nowadays both cisco and juniper set by default origin for aggregated
routes to IGP.

Jeff

P.S. Sorry for all the mails, bloody outlook :)

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
bounces at puck.nether.net] On Behalf Of Borchers, Mark M.
Sent: donderdag 19 april 2007 23:03
To: 'juniper-nsp at puck.nether.net'
Subject: Re: [j-nsp] BGP Origin Issue
I'll apologize for posting a red herring to the list. Looking further I
believe that by diabolical coincidence, the origin-incomplete routes were
also carrying prepends that prevented them from showing up as active routes
anywhere. The ones that were visible on the Internet were in some
cases
not
prepended and in other cases more-specifics that weren't being announced
elsewhere. I jumped on the origin attribute too eagerly.
Mark

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Phil Bedard
philxor at gmail.com

Jeff Tantsura

2007-04-20 14:42:23 UTC

Permalink

Hi,

My bad, described behaviour was true back in 2001.
In nowadays both cisco and juniper set by default origin for aggregated
routes to IGP.

Jeff

P.S. Sorry for all the mails, bloody outlook :)

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
bounces at puck.nether.net] On Behalf Of Borchers, Mark M.
Sent: donderdag 19 april 2007 23:03
To: 'juniper-nsp at puck.nether.net'
Subject: Re: [j-nsp] BGP Origin Issue
I'll apologize for posting a red herring to the list. Looking further I
believe that by diabolical coincidence, the origin-incomplete routes were
also carrying prepends that prevented them from showing up as active routes
anywhere. The ones that were visible on the Internet were in some
cases
not
prepended and in other cases more-specifics that weren't being announced
elsewhere. I jumped on the origin attribute too eagerly.
Mark

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Phil Bedard
philxor at gmail.com

Jeff Tantsura

2007-04-20 09:45:36 UTC

Permalink

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Jeff Tantsura

2007-04-20 09:47:52 UTC

Permalink

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Jeff Tantsura

2007-04-20 09:53:06 UTC

Permalink

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Jeff Tantsura

2007-04-20 09:49:48 UTC

Permalink

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Jeff Tantsura

2007-04-20 09:51:24 UTC

Permalink

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises
prefixes with origin incomplete", I'm going to do more
detailed checking on
the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Ihsan Junaidi Ibrahim

2007-04-21 07:17:03 UTC

Permalink

Jeff,

On 7.6, the aggregated routes are still marked as origin. I have a couple of
and many older 7.0 boxes doing that. I still have to manually mark the
routes as IGP-originated in the aggregate defaults stanza.

/ihsan

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Jeff Tantsura
Sent: Friday, April 20, 2007 10:27 PM
To: 'Phil Bedard'
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP Origin Issue

Hi,

My bad, described behaviour was true back in 2001.
In nowadays both cisco and juniper set by default origin for aggregated
routes to IGP.

Jeff

P.S. Sorry for all the mails, bloody outlook :)

-----Original Message-----
From: Phil Bedard [mailto:philxor at gmail.com]
Sent: vrijdag 20 april 2007 15:16
To: jeff.tantsura at sscplus.nl
Cc: 'Borchers, Mark M.'; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP Origin Issue
Yeah the Cisco is a little strange in those regards, the only time it
will not use IGP for the origin code in an aggregate-address is if you
are using as-set and one of the contributing routes is incomplete...
I second the policy of resetting the origin to IGP to take that out
of the possible path selection. Using a route-map on the
redistribute, you
can set that policy on import into the BGP table...
Phil

Post by Jeff Tantsura
Hi,
Actually there's a situation where you could get hit by differences
in "origin" setup.
By default Cisco, when aggregates, marks origin as IGP while Juniper
does incomplete. If you have got more than 1 BGP sessions with a
same peer and they aggregate on the peering routers where 1 is Cisco
and another is juniper... guess what :) That's why resetting of
origin to IGP on your borders is a good idea.
Just my .02 cent
Jeff

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
bounces at puck.nether.net] On Behalf Of Borchers, Mark M.
Sent: donderdag 19 april 2007 23:03
To: 'juniper-nsp at puck.nether.net'
Subject: Re: [j-nsp] BGP Origin Issue
I'll apologize for posting a red herring to the list. Looking
further I believe that by diabolical coincidence, the
origin-incomplete routes were also carrying prepends that prevented
them from showing up as active routes anywhere. The ones that were
visible on the Internet were in some cases not prepended and in
other cases more-specifics that weren't being announced elsewhere.
I jumped on the origin attribute too eagerly.
Mark

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises prefixes with origin incomplete", I'm going to do
more detailed checking on the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use,
copying or disclosure by any other person is strictly prohibited.
If you have received this transmission in error, please notify the
sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Phil Bedard
philxor at gmail.com

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Ihsan Junaidi Ibrahim

2007-04-21 07:24:18 UTC

Permalink

Rephrase that, On 7.6, the aggregated routes are still marked as having
incomplete origin.

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Ihsan Junaidi
Ibrahim
Sent: Saturday, April 21, 2007 3:17 PM
To: jeff.tantsura at sscplus.nl; 'Phil Bedard'
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP Origin Issue

Jeff,

On 7.6, the aggregated routes are still marked as origin. I have a couple of
and many older 7.0 boxes doing that. I still have to manually mark the
routes as IGP-originated in the aggregate defaults stanza.

/ihsan

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Jeff Tantsura
Sent: Friday, April 20, 2007 10:27 PM
To: 'Phil Bedard'
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP Origin Issue

Hi,

My bad, described behaviour was true back in 2001.
In nowadays both cisco and juniper set by default origin for aggregated
routes to IGP.

Jeff

P.S. Sorry for all the mails, bloody outlook :)

-----Original Message-----
From: Phil Bedard [mailto:philxor at gmail.com]
Sent: vrijdag 20 april 2007 15:16
To: jeff.tantsura at sscplus.nl
Cc: 'Borchers, Mark M.'; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP Origin Issue
Yeah the Cisco is a little strange in those regards, the only time it
will not use IGP for the origin code in an aggregate-address is if you
are using as-set and one of the contributing routes is incomplete...
I second the policy of resetting the origin to IGP to take that out
of the possible path selection. Using a route-map on the
redistribute, you
can set that policy on import into the BGP table...
Phil

Post by Jeff Tantsura
Hi,
Actually there's a situation where you could get hit by differences
in "origin" setup.
By default Cisco, when aggregates, marks origin as IGP while Juniper
does incomplete. If you have got more than 1 BGP sessions with a
same peer and they aggregate on the peering routers where 1 is Cisco
and another is juniper... guess what :) That's why resetting of
origin to IGP on your borders is a good idea.
Just my .02 cent
Jeff

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
bounces at puck.nether.net] On Behalf Of Borchers, Mark M.
Sent: donderdag 19 april 2007 23:03
To: 'juniper-nsp at puck.nether.net'
Subject: Re: [j-nsp] BGP Origin Issue
I'll apologize for posting a red herring to the list. Looking
further I believe that by diabolical coincidence, the
origin-incomplete routes were also carrying prepends that prevented
them from showing up as active routes anywhere. The ones that were
visible on the Internet were in some cases not prepended and in
other cases more-specifics that weren't being announced elsewhere.
I jumped on the origin attribute too eagerly.
Mark

-----Original Message-----
Based on the fact that nobody has said "Yo dummy, JunOS never
re-advertises prefixes with origin incomplete", I'm going to do
more detailed checking on the looking glasses.

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use,
copying or disclosure by any other person is strictly prohibited.
If you have received this transmission in error, please notify the
sender via e-mail.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Phil Bedard
philxor at gmail.com

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp