Can we have multiple default-information originate commands?

I don't see why you should not be able to have multiple default- information originate commands. Its effectively the same as having a BGP internet connection at both datacenters and redistributing a default route into each DC. If there is a third site that has a connection to each DC, it will select the best path via your IGP (in this case OSPF), or you can manually set the preference for each site. The only thing to be concerned with is the traffic coming back in. You want to avoid asynch routing, especially if you have firewalls or any other stateful appliances that will deny traffic that is out of state.

This requires that you think carefully about what you want to occur with respect to default routing.

You should look at the metric associated with the current default route (defautl for deafult-info orig is a metric of 1 I believe. The MPLS network will probably be "invisible" to OSPF so you need to check a few remote site and see what the metric is on the current default route. For the west cost dat cneter you may then want to configure the default-originate with a higher-metric ( less preferred). This also means that should your east cost data center router fail, Internet traffic will flow via the wet cost data center which you might or might not want.

Do your homework ...

Yes, I plan on having both for redudancy. The question is how to make any particular site prefer one over the other.

They will via your IGP no matter what. Meaning if you have unequal links or paths, it will prefer the better one. Presuming you have equal cost paths to both, you will need to modify your metrics or do a route map. Several options for doing that.

! Select east or west default route using route tags - for illustration purposes only !!!

! East coast data center router(s)

! do not use always parameter in case this data center's Internet link is down

! If using BGP with ISP then could request ISP to also advertise default to us

default-info orig metric 1 metric-type < > route-map SET_DEFAULT_ROUTE_TAG

! set route tag to allow each site to select east or west coast default route

route-map SET_DEFAULT_ROUTE_TAG permit 10 set tag 10

!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++

! West coast data center router(s)

! do not use always parameter in case this data center's Internet link is down

default-info orig metric 1 metric-type route-map SET_DEFAULT_ROUTE_TAG

! set route tag to allow each site to select east or west coast default route

route-map SET_DEFAULT_ROUTE_TAG permit 10 set tag 20

!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++

! site router - prefer East default route

route-map CHECK_DEFAULT_ROUTE_TAG permit 10 match tag 10 ! east coast set metric 5

route-map CHECK_DEFAULT_ROUTE_TAG permit 20 match tag 20 ! west coast set metric 10

router ospf distribute-list route-map CHECK_DEFAULT_ROUTE_TAG in exit

!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++

! site router - prefer West default route

route-map CHECK_DEFAULT_ROUTE_TAG permit 10 match tag 10 ! east coast set metric 10

route-map CHECK_DEFAULT_ROUTE_TAG permit 20 match tag 20 ! west coast set metric 5

router ospf distribute-list route-map CHECK_DEFAULT_ROUTE_TAG in exit

!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++

see Cisco doc "OSPF Inbound Filtering Using Route Maps with a Distribute List"

Thanks Merv. I'll look into this.

Taqs are perfect. That's what I wanted.

Thanks!

- Bob

I think the ospf distribute list with route-map was introduced in

12.2, so check that you remote site(s) are at that level beforehand