Cisco 6509/Sup720/MSFC3 running 12.2(33)SXI4 The only route redistribution we do (at least in our internal core network) is static -> eigrp, so that's why we never have had to modify the default metrics.
Again, the only issue to me is that the syntax allowed me to configure "redistribute static" and silently failed. In the past (with ipv4 eigrp), without specifying the metrics on that line or using default-metric command, IOS would redistribute the metrics with default settings. Either not allowing the command without specifying the full command line or using the default values would be fine, but accepting the command and then not working isn't okay. ---- Matthew Huff | One Manhattanville Rd OTA Management LLC | Purchase, NY 10577 http://www.ox.com | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-460-4139 > -----Original Message----- > From: cisco-nsp-boun...@puck.nether.net > [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Andriy > Bilous > Sent: Thursday, October 21, 2010 7:05 AM > To: Gert Doering > Cc: cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] Redistributing ipv6 static default route into > eigrpfailure > > It does work this way - in 12.4(24)T1 anyway. I'm curious what > hardware/software op's using and why is seed metric required there. > > R1#sh run int fa0/0 > Building configuration... > > Current configuration : 129 bytes > ! > interface FastEthernet0/0 > no ip address > duplex auto > speed auto > ipv6 address 2620:0:2810:104::252/64 > ipv6 eigrp 14607 > end > > R1#sh run | i ipv6 route > ipv6 route ::/0 FastEthernet0/0 2620:0:2810:104::1 > > R1#sh run | s i r e > ipv6 router eigrp 14607 > no shutdown > redistribute static > > R1#sh ipv6 eigrp topology > IPv6-EIGRP Topology Table for AS(14607)/ID(10.0.0.3) > > Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, > r - reply Status, s - sia Status > > P ::/0, 1 successors, FD is 256 > via Rstatic (256/0) > P 2620:0:2810:104::/64, 1 successors, FD is 28160 > via Connected, FastEthernet0/0 > > R1#sh ver | i Ver > Cisco IOS Software, 2801 Software (C2801-ADVIPSERVICESK9-M), Version > 12.4(24)T1, RELEASE SOFTWARE (fc3) > ROM: System Bootstrap, Version 12.4(13r)T, RELEASE SOFTWARE (fc1) > > > On Thu, Oct 21, 2010 at 7:49 AM, Gert Doering <g...@greenie.muc.de> wrote: > > 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 > > g...@greenie.muc.de > > fax: +49-89-35655025 > > g...@net.informatik.tu-muenchen.de > > > > _______________________________________________ > > cisco-nsp mailing list cisco-...@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/
_______________________________________________ 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/
