resync is one thing....drop is another. In newer code we don't drop but we do resync. ;)
R1_#sh run | section router eigrp router eigrp 1 network 0.0.0.0 auto-summary R1_#config t Enter configuration commands, one per line. End with CNTL/Z. R1_(config)#router ei 1 R1_(config-router)#distribute-list 1 out R1_(config-router)#exit R1_(config)#access-list 1 deny 4.0.0.0 R1_(config)#access-list 1 permit 2.2.2.0 R1_(config)#end R1_# *Apr 22 13:24:16.184: %SYS-5-CONFIG_I: Configured from console by console R1_# *Apr 22 13:24:20.972: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 2.2.2.2 (Ethernet1/0) is resync: route configuration changed R1_# and on the peer: *Apr 22 13:24:20.544: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 2.2.2.1 (Ethernet1/0) is resync: peer graceful-restart Rodney On Tue, Apr 22, 2008 at 07:08:46AM +0200, Ibrahim Abo Zaid wrote: > Hi All > > Yes , this is a normal behaviour to EIGRP to resync topology table between > neighbors after modifying the redistribute-list > > best regards > --Abo Zaid > > On 4/21/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Sadly, it is. > > > > -- > > Regards, > > > > Jason Plank > > CCIE #16560 > > e: [EMAIL PROTECTED] > > > > -------------- Original message ---------------------- > > From: "Jeff Cartier" <[EMAIL PROTECTED]> > > > Ah nevermind. Looks like its normal behaviour... *sigh* > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] on behalf of Jeff Cartier > > > Sent: Mon 4/21/2008 3:59 PM > > > To: [email protected] > > > Subject: [c-nsp] EIGRP - modify distribute-list and EIGRP neighbor drops > > > > > > > > > Greetings! > > > > > > I've coming into an unfamiliar issue where I'm modifying the > > distribution list > > > on a Cisco router running EIGRP...I'm creating a vlan management subnet > > using > > > loopbacks and vlan SVIs; the thing I'm having trouble explaining is when > > I > > > modify the ACL, which is a standard ACL, to permit the subnets that I > > want to > > > redistribute, the EIGRP neighbors drop and then re-connect. > > > > > > Why is this? > > > _______________________________________________ > > > cisco-nsp mailing list [email protected] > > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > > > > _______________________________________________ > > > cisco-nsp mailing list [email protected] > > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > > _______________________________________________ > > cisco-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
