cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

264
Views
0
Helpful
4
Replies
Highlighted
Participant

BGP aggregate-address summary-only route injection

Hello,question about BGP IGP tag:

On Cisco when i'm doing [aggregate-address summary-only] command the summary route is created by BGP is with IGP tag. Even when no of suppressed routes has an IGP flag. 

 

But the RFC says:

ORIGIN attribute: If at least one route among routes that are
aggregated has ORIGIN with the value INCOMPLETE, then the
aggregated route must have the ORIGIN attribute with the value
INCOMPLETE. Otherwise, if at least one route among routes that are
aggregated has ORIGIN with the value EGP, then the aggregated
route must have the origin attribute with the value EGP. In all
other case the value of the ORIGIN attribute of the aggregated
route is INTERNAL.``

 Looking into that i think that Cisco IOS-XE behaves not compliant to RFC because no of the suppressed routes are with IGP tag. Here is my BGP route table with aggregate address command:

aggregate-address 10.254.33.0 255.255.255.0 summary-only

 

 s>   10.254.33.0/31   0.0.0.0                  0         32768 ?
 *>   10.254.33.0/24   0.0.0.0                            32768 i
 s>   10.254.33.2/31   0.0.0.0                  0         32768 ?
 s>   10.254.33.4/32   0.0.0.0                  0         32768 ?
 s>   10.254.33.5/32   10.254.33.2            201         32768 ?
 s>   10.254.33.6/31   10.254.33.2            200         32768 ?
 s>   10.254.33.8/31   10.254.33.0            200         32768 ?
 s>   10.254.33.10/31  10.254.33.0            200         32768 ?
 s>   10.254.33.12/31  10.254.33.2            200         32768 ?
 s>   10.254.33.14/32  10.254.33.2            210         32768 ?
 s>   10.254.33.15/32  10.254.33.2            210         32768 ?
 s>   10.254.33.16/31  10.254.33.0            200         32768 ?
 s>   10.254.33.18/31  10.254.33.2            200         32768 ?

Could you say why Cisco creates summary route with IGP tag as the RFC does not say so ?

Everyone's tags (1)
4 REPLIES 4
Highlighted
VIP Mentor

Re: BGP aggregate-address summary-only route injection

Hello,

 

it doesn't work in pre-XE (15.6) either...

 

*> 1.1.1.0/24 0.0.0.0 32768 i
s> 1.1.1.4/30 0.0.0.0 0 32768 i
s> 1.1.1.8/30 0.0.0.0 0 32768 i
s> 1.1.1.12/30 0.0.0.0 0 32768 i
s> 1.1.1.16/30 0.0.0.0 0 32768 i
s> 1.1.1.28/30 0.0.0.0 0 32768 ?

Highlighted
Participant

Re: BGP aggregate-address summary-only route injection

Thanks, from your output seems like it's the same behavior. Would be nice to know from Cisco if it's intended BGP behavior 

Highlighted
Hall of Fame Master

Re: BGP aggregate-address summary-only route injection

Hello @from88  , @Georg Pauwen 

 

>> Could you say why Cisco creates summary route with IGP tag as the RFC does not say so ?

 

To make easier the life in multi vendor environments in big service provider networks, because for Example I know for sure that Juniper networks do this, IOS XR do this, I suppose ALU and Nokia do this

 

if you have a mix of IOS XE and IOS XR PE nodes it is handy too.

 

 

Hope to help

Giuseppe

 

Highlighted
Participant

Re: BGP aggregate-address summary-only route injection

Thanks, sad but FRR (soon too be new Linux Routing stack) works by RFC. When u have multiple routes received from FRR box and CISCO box - these routes become different (by IGP tag) and ECMP doesnt work, so i need to use some workarounds like set igp in route-maps.