Has anyone ever experienced an External Type 2 OSPF route to be preferred over an Inter Area route?
Here is our situation. We have two MPLS providers AT&T and Global Crossing. We are peering with AT&T through BGP and with Global Crossing through OSPF. On the AT&T router I am advertising a summary route 10.12.0.0/16 through the aggregate command. I am also sending this route via and area range command on an OSPF ABR to Global Crossing.
When I turn up a new site with both MPLS providers, I am receiving the summary route via BGP and OSPF into two separate routers. I have a core switch that is running OSPF as well. When I redistribute the BGP routes into OSPF, my core switch prefers the E2 route via the AT&T BGP router versus preferring the OSPF Inter Area route via Global Crossing. I would like to prefer all traffic to flow through the Global Crossing routers.
I think this may be an issue with the route being preferred over AT&T because the originating router of this route is closer to the destination (since Global Crossing does redistribute between MBGP and OSPF). See RFC 2328 section 16.4
In this case the 10.8/16 external LSA is the only one present, so it is selected. This is expected, standard compliant and nothing to wonder about.
Why are you presenting an output now with no LSA3 for 10.8/16 ?? Where did they go?
Could it be you are troubleshooting changing topologies? Then the picture will be inconsistent and conclusions very difficult, if not misleading.
General advice: First clean up your summary routes. make sure aggregation does not advertise the same aggregate from different locations with different subnets.
Second, make sure the topology and route presented are the same.