[c-nsp] Redistributing ipv6 static default route into eigrpfailure

[Gert Doering]

Hi,

On Thu, Oct 21, 2010 at 07:36:48AM +0200, Oliver Boehmer (oboehmer) wrote:
> > My bad. You are right. It has been too long since I last checked ;-)
> 
> same here, fell into the same trap.. guess with static being the only 
> exception (is this documented anywhere?), adding  "default-metric" 
> to eigrp has been in my dna, not questioning the exceptions :)

Well, I'm not sure whether it's documented anywhere, but this is soooooo
useful :-)  - and this is what we really missed when we changed from
customer-routes-in-EIGRP to customer-routes-in-BGP.

Our typical usage case is "two routers, HSRP, trying to get (mostly)
symmetric traffic" - so we put "bandwidth 1g" on the master router, 
"bandwith 100k" on the backup router, and EIGRP will do the right thing.

With BGP, extra route maps and stuff are needed to designate certain
statics-to-interfaces as "this is backup".

(I find it surprising that it doesn't work that way for EIGRP-for-IPv6...)

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20101021/4b2e5373/attachment.bin>