we found that BGP aggregate sometimes wont be advertised after interface flapping.
We used OSPF on SSTP (point to point) and sometimes it flaps, but after the flaps bgp aggregate with include IGP checked, wont advertising itself anymore, even bgp aggregate shows routes being aggregated. Restarting router works, disabling enabling aggregate sometimes work, but most of the time wont.
Before flaps (fresh restarted) :
> routing bgp advertisements print
PEER PREFIX NEXTHOP AS-PATH ORIGIN LOCAL-PREF
peer4… 103.24.76.0/24 218.100.36.116 incomplete
routing bgp aggregate print detail status
Flags: X - disabled, A - active
0 A instance=bgp5-IIX prefix=103.24.76.0/24 summary-only=yes
inherit-attributes=yes include-igp=yes attribute-filter=“”
suppress-filter=“” advertise-filter=advertise-out
routes-used=*40149987,*401736B9,*401736E5,*40173701,*4017372D,*40173749,
*40173765,*40173781,*4017379D,*401737E5,*40173801
After flaps :
> routing bgp advertisements print peer4-Nice
PEER PREFIX NEXTHOP AS-PATH ORIGIN LOCAL-PREF
routing bgp aggregate print detail status
Flags: X - disabled, A - active
0 A instance=bgp5-IIX prefix=103.24.76.0/24 summary-only=yes
inherit-attributes=yes include-igp=yes attribute-filter=“”
suppress-filter=“” advertise-filter=advertise-out
routes-used=*40149987,*401736B9,*401736E5,*40173701,*4017372D,*40173749,
*40173765,*40173781,*4017379D,*401737E5,*40173801
ticket sent Ticket#2016100422001545