TOI Author :: Yaonan Liang

Normally BGP allocates local labels and installs LFIB entries for all received IPv4/IPv6 Labeled Unicast (LU) routes in anticipation of readvertising them with nexthop-self. However, some deployments don’t require nexthop-self with LU routes, so LFIB hardware resources are needlessly allocated, which can present an issue in large scale LU deployments. 

This feature limits the maximum number of routes that BGP can advertise to a peer. When the maximum

BGP update wait for convergence feature prevents BGP from programming routes into hardware and advertising routes

The BGP Replace AS Path feature provides the capability to customize the AS PATH attribute for prefixes that are