Yes run "default-information originate" on you're core/border router's ospf/eigrp process. That should be your IGP def route separate from the EBGP learned default route. Can run this on more than one core/border router to get traffic back to core.
Rich Sent from my iPhone On Apr 21, 2012, at 9:33 AM, Skeeve Stevens <skeeve+cisco...@eintellego.net> wrote: > Hey all, > > Got an odd problem with a Nexus 7010. > > We're taking in a default route from an upstream and we're wanting to > redistribute the default route into EIGRP. > > The route is getting in just fine, but for some reason it isn't > redistributing into EIGRP. We've tried OSFP as well, but no go. > > We're running Image version: 6.0(1) [build 6.0(0.66)] > > The TAC has been looking into it, but they've gone off to with a confused > look on their face. > > If anyone has experienced anything like this and had a resolution, please > let me know. > > > *Skeeve Stevens, CEO* > eintellego Pty Ltd > ske...@eintellego.net ; www.eintellego.net <http://www.eintellego.net.au> > > Phone: 1300 753 383 ; Fax: (+612) 8572 9954 > > Cell +61 (0)414 753 383 ; skype://skeeve > > facebook.com/eintellego > > twitter.com/networkceoau ; www.linkedin.com/in/skeeve > > PO Box 7726, Baulkham Hills, NSW 1755 Australia > > The Experts Who The Experts Call > Juniper - Cisco – Brocade - IBM > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/