Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

BGP decision process - Local origination


I'm trying to figure out the preference of locally generated routes. In BGP Design and Implementation by Randy Zhang pg25 says:

"Here is the complete order with decreasing preference: default-originate (configured per neighbor) default-information originate (configured per address family), network, redistribute, aggregate-address."

I understand how a router injected by network is more preferred over redistribute command, but have a hard time understanding the preference of other injection methods. Can somebody give me an example or clarify?

Thank you in advance.


Everyone's tags (2)
Hall of Fame Super Silver

Re: BGP decision process - Local origination

Hello Tom,

this is somewhat similar to what happens with origin code.

the network command provides routes with an origin code of i internal

redistributed routes provide an origin  code of ?.

Aggregate-address origine code depends from configuration and from codes of component routes.

Going back to your question:

Both redistributing and using aggregate-address creates locally originated routes but with some loss of details.

for aggregate-address the original AS path of each single component route is lost so it is information that lacks some information in comparison to original data structures.

This may explain also the hierarchy in locally generated routes.

To be noted that first two neigh default-originate and default-information originate comes into play only when it is the case of deciding what default route to pick up to send to a neighbor:

first command neigh .. default-originate wins for being more specific then second

default-information originate should win over using network  (that is a possible way to generate a BGP default route if a default route exists in the local node IP routing table).

Hope to help