[j-nsp] BGP Origin Issue

[Ebben Aries]

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

On Thursday 19 April 2007 11:22 am, Borchers, Mark M. wrote:
> 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

-- 
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