As an add on to this..... A thought I had regarding what is currently occuring is that the "other" upstream ISP might not be accepting those new routes. Waiting for a response from them as to what filters they have in place.
Edit add on:
No. It appears the other upstream ISP is accepting those routes.
So, given the diagram I attached, imagine a CPE DSL Customer the other side of Wholesale, comes into HEX-LNS-02, out of ae1 to HEX-CORE-02 and, normally, through xe-1/2/5 to the upstream ISP. But in this DR test I have disabled xe-1/2/5 on HEX-CORE-02. Now, when I complete the following command on THW-CORE-01:
Let's say the two routes should be:
192.168.10.0/30
192.168.100.0/30
set routing-options aggregate route 192.168.10.0/24
set routing-options aggregate route 192.168.100.0/24
run show route advertising-protocol bgp <peer address> ---- I see the following:
* 192.168.10.0/24 Self I
* 192.168.10.0/30 Self I
* 192.168.100.0/24 Self I
* 192.168.100.0/30 Self I
And if I run the following command:
run show route protocol aggregate detail:
192.168.10.0/24 (1 entry, 1 announced)
*Aggregate Preference: 130
Next hop type: Reject, Next hop index: 0
Address: 0x2a2f284
Next-hop reference count: 13
State: <Active Int Ext>
Local AS: 11111
Age: 18:42:58
Validation State: unverified
Task: Aggregate
Announcement bits (3): 0-KRT 2-BGP_RT_Background 7-Resolve tree 4
AS path: I (LocalAgg)
Flags: Depth: 0 Active
AS path list:
AS path: I Refcount: 2
Contributing Routes (1):
192.168.10.0/30 proto BGP
192.168.100.0/24 (1 entry, 1 announced)
*Aggregate Preference: 130
Next hop type: Reject, Next hop index: 0
Address: 0x2a2f284
Next-hop reference count: 13
State: <Active Int Ext>
Local AS: 11111
Age: 17:42:08
Validation State: unverified
Task: Aggregate
Announcement bits (3): 0-KRT 2-BGP_RT_Background 7-Resolve tree 4
AS path: I (LocalAgg)
Flags: Depth: 0 Active
AS path list:
AS path: I Refcount: 1
Contributing Routes (1):
192.168.100.1/32 proto BGP
If I complete a traceroute from the CPE at HEX side, I can get through to the THW-CORE-01 ae0 interface. If I run the following command on THW-CORE-01 ae1 interface:
run monitor traffic interface ae0 no-resolve size 1500 matching "net 192.168.10.1" -----
and ping the xe-1/2/5 interface on THW-CORE-01 I see the packet flow. When I run traceroute from the CPE I get to the ae0 interface and no further and if I try and ping 8.8.8.8 I see no traffic.... so, I think there is an issue with the advertsing or the Policy on THW-CORE-01 rather than HEX-CORE-02.......
Any help here would be great ..... if the above has not completely confused you 🙂
But with the attached network topology it will make sense...