From: Church, Chuck (cchurch@wamnetgov.com)
Date: Fri Feb 06 2004 - 00:11:27 GMT-3
P.S. Check out:
http://boerland.com/dotu/
for some of these commands. Be careful though, some are hidden for a reason...
Chuck Church
CCIE #8776, MCNE, MCSE
Wam!Net Government Services
13665 Dulles Technology Dr. Ste 250
Herndon, VA 20171
Office: 703-480-2569
Cell: 703-819-3495
cchurch@wamnetgov.com
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=index&search=cchurch%40wamnetgov.com
> -----Original Message-----
> From: Packet Man [mailto:ccie2b@hotmail.com]
> Sent: Thursday, February 05, 2004 3:34 PM
> To: Church, Chuck; turgon2004@hotmail.com
> Cc: ccielab@groupstudy.com
> Subject: RE: Eigrp
>
>
> Hey Chuck,
>
> Thanks for letting me know about that undocumented show
> command. How do
> find stuff like that?
>
> I ran that show command, but quite honestly, I didn't really
> understand how
> to interpret the output. What does "parent" mean? And, more
> generally how
> can I use the output to help troubleshoot a neighbor flapping problem?
>
> Thanks again
>
>
> >From: "Church, Chuck" <cchurch@wamnetgov.com>
> >To: "Packet Man" <ccie2b@hotmail.com>,<turgon2004@hotmail.com>
> >CC: <ccielab@groupstudy.com>
> >Subject: RE: Eigrp
> >Date: Thu, 5 Feb 2004 14:15:23 -0600
> >
> >Debugging EIGRP packets or hellos with service timestamps
> debug datetime
> >will show you the frequency they're coming in at. I'm not
> sure if EIGRP
> >requires exact parameters like OSPF does for neighbors to form
> >relationships. Nothing here at work to try it on. 'sh ip
> eigrp timers'
> >(hidden) will give you an idea of your sending frequency. I
> think it
> >behaves more like RIP, where as long as the dead time isn't
> exceeded, the
> >neighbor stays a neighbor (no, I'm not saying that RIP has
> neighbors either
> >:) I'm just doing this from memory, so someone please
> correct me if I'm
> >wrong...
> >
> >Chuck Church
> >CCIE #8776, MCNE, MCSE
> >Wam!Net Government Services
> >13665 Dulles Technology Dr. Ste 250
> >Herndon, VA 20171
> >Office: 703-480-2569
> >Cell: 703-819-3495
> >cchurch@wamnetgov.com
> >PGP key:
> >http://pgp.mit.edu:11371/pks/lookup?op=index&search=cchurch%4
> 0wamnetgov.com
> >
> > > -----Original Message-----
> > > From: Packet Man [mailto:ccie2b@hotmail.com]
> > > Sent: Thursday, February 05, 2004 2:22 PM
> > > To: Church, Chuck; turgon2004@hotmail.com
> > > Cc: ccielab@groupstudy.com
> > > Subject: RE: Eigrp
> > >
> > >
> > > Hi Chuck,
> > >
> > > Thanks for getting back to me on this.
> > >
> > > Actually, this is a practice lab problem. The issue here is
> > > to figure out
> > > how the remote router was (mis) configured by finding and
> using the
> > > appropriate debugs - and then configuring the local router as
> > > to match. So,
> > > it's "known" that there's no cable, interface, hardware issue
> > > here, although
> > > in the real world those sort of things would be among the
> > > first to check.
> > >
> > > The idea is to be able to overcome this type of potential
> > > "nasty" in the
> > > actual lab where you don't access to the backbone router -
> > > only your router
> > > which is connected to the backbone router. I'm doing
> this with every
> > > routing protocol as an exercise to get stronger with using
> > > and interpreting
> > > debugs.
> > >
> > > With other protocols, it seems easier to find mis-matched
> > > parameters, but
> > > I'm having a heck of time doing so with Eigrp. The output
> > > from their debugs
> > > is unintellible for the most part and appears to be very
> > > poorly documented.
> > >
> > >
> > >
> > >
> > > >From: "Church, Chuck" <cchurch@wamnetgov.com>
> > > >To: "Packet Man" <ccie2b@hotmail.com>,<turgon2004@hotmail.com>
> > > >CC: <ccielab@groupstudy.com>
> > > >Subject: RE: Eigrp
> > > >Date: Thu, 5 Feb 2004 12:47:18 -0600
> > > >
> > > >Is this a new installation, or has it been in place for a
> > > while? If it's
> > > >flapping and been in place for a while, I'd say it's more
> > > likely packet
> > > >loss due to something, rather than mis-configuration. A
> > > failing circuit
> > > >will usually cause hellos to be lost and up/down neighbor
> > > messages to be
> > > >logged. Check your DSUs for errors, assuming it's serial
> > > ints. And check
> > > >the serial ints for errors, queue drops, etc. A pegged CPU
> > > on the router
> > > >can also cause neighbors to drop.
> > > >
> > > >Chuck Church
> > > >CCIE #8776, MCNE, MCSE
> > > >Wam!Net Government Services
> > > >13665 Dulles Technology Dr. Ste 250
> > > >Herndon, VA 20171
> > > >Office: 703-480-2569
> > > >Cell: 703-819-3495
> > > >cchurch@wamnetgov.com
> > > >PGP key:
> > > >http://pgp.mit.edu:11371/pks/lookup?op=index&search=cchurch%4
> > > 0wamnetgov.com
> > > >
> > > > > -----Original Message-----
> > > > > From: Packet Man [mailto:ccie2b@hotmail.com]
> > > > > Sent: Thursday, February 05, 2004 1:40 PM
> > > > > To: turgon2004@hotmail.com
> > > > > Cc: ccielab@groupstudy.com
> > > > > Subject: RE: Eigrp
> > > > >
> > > > >
> > > > > Thanks for getting back to me.
> > > > >
> > > > > As it happens, I tried both of those debugs but the output
> > > > > was, for the most
> > > > > part, undecipherable and I couldn't tell from that output if
> > > > > there was a
> > > > > mis-match.
> > > > >
> > > > > Do you know what specifically I should look for in the output
> > > > > from those
> > > > > debugs to see if there's a Hello or Hold interval mismatch?
> > > > >
> > > > > Thanks iv advanced
> > > > >
> > > > >
> > > > > >From: "Gary Duncanson" <turgon2004@hotmail.com>
> > > > > >To: ccie2b@hotmail.com
> > > > > >CC: ccielab@groupstudy.com
> > > > > >Subject: RE: Eigrp
> > > > > >Date: Thu, 05 Feb 2004 18:34:49 +0000
> > > > > >
> > > > > >debug eigrp neighbor
> > > > > >debug eigrp packet
> > > > > >
> > > > > >
> > > > > >>From: "Packet Man" <ccie2b@hotmail.com>
> > > > > >>Reply-To: "Packet Man" <ccie2b@hotmail.com>
> > > > > >>To: ccielab@groupstudy.com
> > > > > >>Subject: Eigrp
> > > > > >>Date: Thu, 05 Feb 2004 12:50:24 -0500
> > > > > >>
> > > > > >>Hi all,
> > > > > >>
> > > > > >>I'm trying to debug a flapping Eigrp neighbor. I can
> > > > > access my local
> > > > > >>router's config but I can't access the remote router.
> > > > > >>
> > > > > >>I'm trying to figure out which debug to use to see if
> > > > > there's a mismatched
> > > > > >>hello or holdtime interval, but can't seem to find the
> > > > > right debug to use.
> > > > > >>
> > > > > >>Anybody have any ideas?
> > > > > >>
> > > > > >>Thanks in advanced.
> > > > > >>
> > > > >
> > >
> >>_________________________________________________________________
> > > > > >>Check out the coupons and bargains on MSN Offers!
> > > > >
>>http://shopping.msn.com/softcontent/softcontent.aspx?scmId=1418
> > > > >>
> > > > >>____________________________________________________________
> > > > ___________
> > > > >>Please help support GroupStudy by purchasing your study
> > > > materials from:
> > > > >>http://shop.groupstudy.com
> > > > >>
> > > > >>Subscription information may be found at:
> > > > >>http://www.groupstudy.com/list/CCIELab.html
> > > > >
> > > >
> > > > _________________________________________________________________
> > > > Let the new MSN Premium Internet Software make the most of
> > > > your high-speed
> > > > experience.
>http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1
> > >
> > > ______________________________________________________________
> > > _________
> > > Please help support GroupStudy by purchasing your study
> > > materials from:
> > > http://shop.groupstudy.com
> > >
> > > Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
> > >
>
>_________________________________________________________________
>Learn how to choose, serve, and enjoy wine at Wine @ MSN.
>http://wine.msn.com/
>
This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:47 GMT-3