Overview
Describes how BGP aggregates link-bandwidth values of DMZ eBGP multipaths when advertising routes to iBGP peers, enabling accurate internal bandwidth representation for improved routing decisions.
BGP DMZ aggregate bandwidth is a feature that aggregates the link-bandwidth values of DMZ eBGP multipaths when advertising routes to iBGP peers, and enables accurate internal bandwidth representation for better routing decisions.
BGP DMZ aggregate bandwidth operation
BGP aggregates bandwidth without an explicit command if these conditions are met:
-
The network has multipaths and all multipaths have link-bandwidth values.
-
You set the next-hop attribute to next-hop-self . The next-hop attribute for all routes advertised to the specified neighbor is the address of the local router.
-
You do not configure an outbound policy that might change the DMZ link-bandwidth value.
DMZ link bandwidth aggregation rules
DMZ link bandwidth aggregation follows these rules:
-
If BGP does not know the DMZ link-bandwidth value (dmz-link-bandwidth ) for any one of the multipaths (eBGP or iBGP), BGP does not download the DMZ link-bandwidth value for all multipaths, including the best path, to the routing information base (RIB).
-
BGP does not consider the DMZ link-bandwidth value of iBGP multipath during aggregation.
-
BGP can advertise the route with an aggregate value as a best path or an add-path.
-
Add-path does not qualify for DMZ link bandwidth aggregation as the next hop is preserved. BGP does not support configuring next-hop-self for add-path.
-
For VPNv4 and VPNv6 address family identifiers (AFIs), if you configure the DMZ link-bandwidth value using an outbound route-policy, specify the route table or use the additive keyword. Otherwise, the system does not import routes on the receiving end of the peer.