From: M Lab (mlabccie@gmail.com)
Date: Tue Mar 17 2009 - 23:15:16 ART
Thanks for the replies.
I did try the debug ip packet dump with an ACL referencing 224.0.0.10,
(handy trick I hope I never forget) but after some time watching the output,
I started to feel like a cat trying to cover <bleep> on a marble floor.
Thank you for helping me not feel like I'm just a dufus! I will bury this
one and move along with the studies.
On Tue, Mar 17, 2009 at 7:21 PM, Scott Morris <
smorris@internetworkexpert.com> wrote:
> The short answer is no. Even through wireshark. :)
>
> But if you are interested enough to grab packet information, instead of
> using the "sh buffers" command you have below, I'd look at "debug ip packet
> (ACL) dump" instead.
>
> That's a hidden command for a reason, by the way!
>
> Scott
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Dale
> Shaw
> Sent: Tuesday, March 17, 2009 9:10 PM
> To: M Lab
> Cc: Groupstudy
> Subject: Re: Kind of silly EIGRP question
>
> Hi,
>
> On Wed, Mar 18, 2009 at 11:36 AM, M Lab <mlabccie@gmail.com> wrote:
> > I've been looking through documentation and notes, but I'm just not
> seeing
> > a way that this can be determined through log messages or debugs. This
> has
> > to be something that many have encountered, so I figure I'm just
> overlooking
> > this somehow. I've put this in my lab and debugged just about everything
> I
> > can think of, but I'm just not seeing it.
>
> Hmmm, I just had a quick look too, and you're right, there doesn't
> seem to be a debug or log option to say "hey! our K-values are set to
> this, but their K-values are set to that!" like there is with OSPF
> hello parameter mismatches.
>
> So, other than using a packet sniffer (that understands EIGRP), I
> don't know of a way to dig deep enough into the hellos to figure out
> what we'd need to set locally in order to match the other side.
> Obviously a packet sniffer is not available in the real lab.
>
> If you were Macguyver, you might be able to use "sh buffers
> input-interface fa0/0 packet" just at the right time to catch an EIGRP
> hello packet. But only if you're Macguyver.
>
> Given we don't have access to the BB routers in the real lab, I reckon
> it is extremely unlikely that you'd encounter a problem like this
> between a candidate router and a BB router. Between two candidate
> routers? maybe.
>
> Having said all that, I'd be happy to be shown a way to expose the
> K-values being offered up from a "would-be" EIGRP neighbour.
>
> cheers,
> Dale
>
>
> 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 Apr 06 2009 - 06:44:05 ART