Looking at the topology sketch here is what I understand:
1)When a remote 803 calls in to say R4 & connects, the R4 will have a host route (let's assume that the 803 comes with static ip address 220.127.116.11) in the routing table (18.104.22.168/32).
OSPF is supposed to distribute this as an routing update to the remaining routers.
2) In R3, show ip route 22.214.171.124 will show it's learnt via R4 as next hop with an admin value 110.....but in fact when R3 needs to send a packet to 126.96.36.199 it will see the static route with lower admin dist & actually make a call OUT.
Try increasing the admin distance on the static route on the R3:
no ip route 255.255.255.248
ip route 255.255.255.248 200 <===add 200 at the end
Now the point arises is that why did the other routers send packet destined for 188.8.131.52 to R3 instead of R4 (since they should have learnt that thru ospf). It will be interesting to see what the "sh ip route" shows on the remaining routers. Surely SGBP should not cause it, not sure if HSRP is causing it.
Please let me know if increasing the admin value fixes it....
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...