We have two data centers. At each location, at the outside edge, is a firewall. Just inside of the firewall is a distribution router (ABR). Just inside of the distribution routers are the Core routers, which have Gig links to each other. Those gigs are the primary flow between the DCs.
Previously, the default-route was simply a static on each Distribution router pointing to their respective firewall. Obviously, this isn't very dynamic since that will stay in the table even if the firewall's outside interface goes down.
Last weekend, I removed the static default-routes. I then made the link between each firewall and their connected distribution router an OSPF NSSA area. I then had the firewall inject a default route by this command: "area 10.17.10.48 nssa default-information-originate metric-type 1".
When this was completed at each location, I saw a full adjacency form. I then saw a default route in the table of each distribution router, learned from their connected outbound firewalls.
Strangely, when I went on the core routers at either data center, I did "sho ip route 0.0.0.0" and got a response of "subnet not in table"
Since this was a full internet outage, I didn't have much time to troubleshoot. I added a "default-information originate" to each distribution router, assuming that if the distribution saw a default-route in its table, that it would propagate it. This still did not fix it.
The firewall learned every core route from distribution, and distribution learned the default from the firewall. I just can't figure why either default wouldn't propagate into area 0.
Our core is kept very simple - there are no filters there. Frankly, I've baffled. I finally had to put the statics back on to get the late-night people back out to the internet.
Any insight here would be appreciated. I have all weekend to look at this.
Thanks in advance for any help!