From: Hobbs (deadheadblues@gmail.com)
Date: Sun Nov 02 2008 - 21:44:24 ARST
What is the mask of each interface?
On Sun, Nov 2, 2008 at 4:43 PM, Hobbs <deadheadblues@gmail.com> wrote:
> When does it happen? After you change a parameter? I think I have seen the
> issue that Bob talked about with the goodbye message causing a K-value
> mismatch....It looks like you are getting the K-value mismatch, then your
> adjacency is forming. This means your adjacency was brought down for some
> reason - maybe you configured a summary or secondary address...
>
> Example: I had an initial config with a mistake (on purpose). One router on
> a LAN with /24 and the other with /20 mask. After I configured the /20 for a
> /24, EIGRP sent a goodbye and the other router complained about a K-value
> mismatch. The adjacency then came up fine.
>
> I wonder if its a code issue...I am always running 12.4...
>
> On Sun, Nov 2, 2008 at 4:22 PM, Piotr <usaccie@gmail.com> wrote:
>
>> On the routers I left the MTU at default,m 1500. On the switches
>> (3550/3560)
>> I set the system MTU to 1500 (system MTU 1500 or system MTU routing 1500.
>> Where allowed on the interface I set ip mtu 1500).
>>
>> Debugs don't show me anything. I was looking to shut the messages off with
>> a
>> command similar to ip ospf mtu-ignore but I don't see one under the
>> interface.
>>
>> I can try and set the metric for all devices in the AS and see what
>> happens.
>>
>>
>> On Sun, Nov 2, 2008 at 3:02 PM, Bob Sinclair <bob@bobsinclair.net> wrote:
>>
>> > Piotr,
>> >
>> > Check that the MTUs match on both devices. I notice one is a switch.
>> > Though the specs do not require equal MTU (like OSPF does) Cisco
>> routers
>> > have been known to drop EIGRP packets over MTU mismatch issues.
>> > The K-value mismatch error can be caused when the near side router does
>> not
>> > support the "goodbye" message, added around 12.2(3), but the far side
>> does.
>> >
>> > HTH,
>> >
>> > Bob Sinclair CCIE 10427 CCSI 30427
>> > www.netmasterclass.net
>> >
>> > Piotr wrote:
>> >
>> >> Switch:
>> >>
>> >> 05:04:04: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
>> >> 183.1.105.5(FastEthernet0/18) is up: new adjacency
>> >> --More--
>> >> 05:05:23: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
>> >> 183.1.105.5(FastEthernet0/18) is down: K-value mismatch
>> >> --More--
>> >> 05:05:26: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
>> >> 183.1.105.5(FastEthernet0/18) is up: new adjacency
>> >>
>> >> router eigrp 100
>> >> network 183.1.105.10 0.0.0.0
>> >> network 183.1.107.10 0.0.0.0
>> >> no auto-summary
>> >> eigrp router-id 150.1.10.10
>> >>
>> >> interface FastEthernet0/18
>> >> no switchport
>> >> ip address 183.1.105.10 255.255.255.0
>> >>
>> >>
>> >> Routing Protocol is "eigrp 100"
>> >> Outgoing update filter list for all interfaces is not set
>> >> Incoming update filter list for all interfaces is not set
>> >> Default networks flagged in outgoing updates
>> >> Default networks accepted from incoming updates
>> >> EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
>> >> EIGRP maximum hopcount 100
>> >> EIGRP maximum metric variance 1
>> >> Redistributing: eigrp 100
>> >> EIGRP NSF-aware route hold timer is 240s
>> >> Automatic network summarization is not in effect
>> >> Maximum path: 4
>> >> Routing for Networks:
>> >> 183.1.105.10/32
>> >> 183.1.107.10/32
>> >> Routing Information Sources:
>> >> Gateway Distance Last Update
>> >> 183.1.107.7 90 00:07:43
>> >> Distance: internal 90 external 170
>> >>
>> >>
>> >>
>> >>
>> >> router:
>> >> *Nov 2 13:55:54.926: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
>> >> 183.1.105.10 (FastEthernet0/0) is down: retry limit exceeded
>> >> RSRack1R5(config-router)#
>> >> *Nov 2 13:55:57.322: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
>> >> 183.1.105.10 (FastEthernet0/0) is up: new adjacency
>> >> RSRack1R5(config-router)#
>> >> *Nov 2 13:57:16.834: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
>> >> 183.1.105.10 (FastEthernet0/0) is down: retry limit exceeded
>> >> RSRack1R5(config-router)#
>> >> *Nov 2 13:57:20.290: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
>> >> 183.1.105.10 (FastEthernet0/0) is up: new adjacency
>> >>
>> >>
>> >> router eigrp 100
>> >> network 183.1.105.5 0.0.0.0
>> >> no auto-summary
>> >> eigrp router-id 150.1.5.5
>> >>
>> >>
>> >> interface FastEthernet0/0
>> >> ip address 183.1.105.5 255.255.255.0
>> >> duplex auto
>> >> speed auto
>> >>
>> >>
>> >> Routing Protocol is "eigrp 100"
>> >> Outgoing update filter list for all interfaces is not set
>> >> Incoming update filter list for all interfaces is not set
>> >> Default networks flagged in outgoing updates
>> >> Default networks accepted from incoming updates
>> >> EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
>> >> EIGRP maximum hopcount 100
>> >> EIGRP maximum metric variance 1
>> >> Redistributing: eigrp 100
>> >> EIGRP NSF-aware route hold timer is 240s
>> >> Automatic network summarization is not in effect
>> >> Maximum path: 4
>> >> Routing for Networks:
>> >> 183.1.105.5/32
>> >> Routing Information Sources:
>> >> Gateway Distance Last Update
>> >> 183.1.105.10 90 00:09:49
>> >> Distance: internal 90 external 170
>> >>
>> >>
>> >> Blogs and organic groups at http://www.ccie.net
>> >>
>> >> _______________________________________________________________________
>> >> Subscription information may be found at:
>> >> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:28 ARST