Similar to Gert's question on on delayed eBGP startup, is there a good way to delay IGP default-route generation?
Since our DFZ routers have a 0/0 nailed down to Null0, OSPF begins generating the default right away, irrespective of BGP state (namely before the router is actually prepared to handle default-routed traffic). A delayed startup for OSPF doesn't work, since that same instance would be needed to find iBGP loopbacks. A route-map matching a "default-network" is the only thing that comes to mind, though designating a magic prefix for this seems broken. I don't believe there's a formal BGP state for "done w/ inital UPDATE churn", but presumably this is where both the eBGP-startup and IGP-default originate would ideally trigger. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
