From: Kenneth Wygand (KWygand@customonline.com)
Date: Wed Sep 03 2003 - 16:20:01 GMT-3
If you don't have access to the other router, throw a sniffer on the
line and examine the EIGRP update packet. Some network monitoring tools
will even convert the packet into a nice, easy-to-read format with all
the information you are looking for.
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, MCP 2000, CNA 5.1, Network+, A+
Custom Computer Specialists, Inc.
70 Suffolk Court
Hauppauge, NY 11788
(631) 864-6699 x1755
"It's not just about ending up where you want to be, it's about making
the most of the trip there."
-Anonymous
-----Original Message-----
From: Kurt Kruegel [mailto:kurt@cybernex.net]
Sent: Wednesday, September 03, 2003 3:18 PM
To: navaid@rogers.com; ccielab@groupstudy.com
Subject: Re: EIGRP K-value mismatch
check the metric weights command on each router
----- Original Message -----
From: <navaid@rogers.com>
To: <ccielab@groupstudy.com>
Sent: Wednesday, September 03, 2003 2:59 PM
Subject: EIGRP K-value mismatch
> Hi,
> I am having problem esteblishing eigrp neighbor relationship. I know
it is
k-values mismtch. I am wondering how to find what are the values
configured
on other router without looking into config of other router.
>
> R9#debug eigrp packets hello
> 05:21:21: EIGRP: Received HELLO on ATM0.2 nbr 136.10.69.6
> 05:21:21: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0
> 05:21:21: K-value mismatchll
>
> Thanks,
>
> Navaid
>
> 1
>
>
>
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:22 GMT-3