From: Shaun Nicholson (Shaun.Nicholson@xxxxxx)
Date: Fri Dec 01 2000 - 12:06:17 GMT-3
I have never had a problem with the route flapping most of my issues I have see
n in my lab is as if the interface not being seen by OSPF when I do a show ip o
spf neig no reference for the bri0. I then do sh ip int ospf bri0 and ospf is e
nabled for the interface but it still does not work. Still no problems with the
route flapping as it will not come up. Reboot of the routers still no success.
I add the no peer neig and it works.
This also happened to me on the ARS class and 10 of the people in the class plu
s the instructor could not understand it. I even compared my configs to working
configs and all was fine. Many reboots and a change of the ios still no joy.
Finally the instructor James Parks blew away the OSPF on the bri changed to a d
ifferent IP subnet and it worked. Now explain that, I could not and neither cou
ld James.
I have seen this about 6 times out of the 12 or so times I have done this is th
e lab it would simply appear as if OSPF is not enabled on the interface but che
cking the interface it is.
I have found that the no peer statement fixes this every single every time with
out having to blow away the ip and start again on that interface with reboots (
takes in the region of an hour).
OK so what's my point?
I understand what other people are saying about you should not need this comman
d and I get it to work every time.
Well all I can say is well done but some people are doing things (inputting th
e correct commands) in a slightly different way and its screwing up how the dem
and circuit process in the IOS works so please don't knock the helpful tips tha
t make things work we all know it should not be necessary but unfortunately it
is (no one questions rebooting a router to get Appletalk to work).
It may be more helpful if we covered what order we put commands on the interfac
e as the issue may be that PPP ENCAP may need to be on the first and the second
last command should be the demand circuit.
I would also add many other people with the same issue have used this "fix" wit
h great success as well. Again I know you should not need it but why waste an h
our on the lab trying to make something work and failing when typing this comma
nd gets you up and running in less than 5 mins I would however point out your p
roblem to the proctor and tell him this is what you intend to do to fix the iss
ue.
Thanks
Shaun
aolzak@buckeye-express.com on 11/30/2000 08:40:00 PM
To: Shaun Nicholson, robertdevito@hotmail.com@Internet, jagvans@yahoo.com@I
nternet
cc: hnrane@yahoo.com@Internet, Simon.Baxter@au.logical.com@Internet, michae
l.yurchenko@verizon.com@Internet, obuba@yahoo.com@Internet, ccielab@groupstudy.
com@Internet
Subject: Re: OSPF demand circuit
By default, PPP creates a /32 route to your "peer", also known as the router
on the other end of the call. Typing the "no peer" command disables this
behavior.
I've never had a problem with demand circuit. I do not use this command and
I only put "ospf demand-circuit" on one side, the calling side. Although, it
shouldn't matter on which side the command is placed.
Most people think demand circuit is their problem when you've really got
routing loops causing your link to flap. Do a show dialer to determine the
reason for the call, then debug the lsa generation to figure out which lsa's
are causing the problem.
It works if configured correctly.
Tony
----- Original Message -----
From: "Robert DeVito" <robertdevito@hotmail.com>
To: <Shaun.Nicholson@KP.ORG>; <jagvans@yahoo.com>
Cc: <hnrane@yahoo.com>; <Simon.Baxter@au.logical.com>;
<michael.yurchenko@verizon.com>; <obuba@yahoo.com>; <ccielab@groupstudy.com>
Sent: Thursday, November 30, 2000 8:41 PM
Subject: RE: OSPF demand circuit
>
> Please refresh my memory, what does the "no peer" command do?
>
> Thank you,
> Robert
>
> ----Original Message Follows----
> From: Shaun Nicholson <Shaun.Nicholson@KP.ORG>
> Reply-To: Shaun Nicholson <Shaun.Nicholson@KP.ORG>
> To: jagvans <jagvans@yahoo.com>
> CC: hnrane <hnrane@yahoo.com>, "Simon.Baxter"
<Simon.Baxter@au.logical.com>,
> "michael.yurchenko" <michael.yurchenko@verizon.com>, obuba
> <obuba@yahoo.com>, ccielab <ccielab@groupstudy.com>
> Subject: RE: OSPF demand circuit
> Date: 30 Nov 2000 09:22:54 -0800
>
> Yes but more importantly it makes the ip ospf demand circuit (which is
very
> very buggy) work everytime without needing to mess about and in a timed
lab
> environment that's very important.
>
> Shaun
>
>
>
>
> jagvans@yahoo.com on 11/30/2000 12:17:00 PM
> To: Shaun Nicholson, hnrane@yahoo.com@Internet
> cc: Simon.Baxter@au.logical.com@Internet,
> michael.yurchenko@verizon.com@Internet, obuba@yahoo.com@Internet,
> ccielab@groupstudy.com@Internet
> Subject: RE: OSPF demand circuit
>
> Word of caution with the "no peer" command ... it can keep an interface
> quiet, but it can also make chap authentication and callin / callback act
> a little flaky.
>
>
> --- Shaun Nicholson <Shaun.Nicholson@KP.ORG> wrote:
> > Use the no peer neighbor-route on the demand circuit and it will work
> > with only one side enabled as a OSPF demand circuit.
> >
> > Shaun
> >
> >
> >
> >
> > hnrane@yahoo.com on 11/30/2000 07:13:00 AM
> > To: Simon.Baxter@au.logical.com@Internet,
> > michael.yurchenko@verizon.com@Internet, obuba@yahoo.com@Internet,
> > ccielab@groupstudy.com@Internet
> > cc: (bcc: Shaun Nicholson/MD/KAIPERM)
> > Subject: RE: OSPF demand circuit
> >
> > Simon,
> >
> > I tried putting the demand circuit command on only
> > one side of the ISDN router....it ain't worked! Then I
> > configured demand circuit on both ISDN router and it
> > works great.
> >
> > I also found that this command is not their in IOS
> > version 11.1 and earlier....what a knowledge!!!
> >
> > Harish
> >
> > --- Simon Baxter <Simon.Baxter@au.logical.com> wrote:
> > > You only need to put demand circuit on one end, the
> > > circuit will establish
> > > and negotiate the link as a demand circuit. (ie set
> > > DNA on both sides)
> > >
> > >
> > > Simon
> > >
> > > -----Original Message-----
> > > From: haresh rane [mailto:hnrane@yahoo.com]
> > > Sent: Thursday, November 30, 2000 1:30 AM
> > > To: Yurchenko, Michael; 'Nnanna Obuba';
> > > ccielab@groupstudy.com
> > > Subject: RE: OSPF demand circuit
> > >
> > >
> > > Michael,
> > >
> > > I worked on that lab yesterday. You need to put 'IP
> > > ospf demand-circuit' command on bri interfaces of
> > > both
> > > the routers.....I remember they were R2 and R3...
> > > It works perfectly fine.
> > >
> > > The Ios version I am using is 11.2.9 ent.
> > >
> > > Harish
> > >
> > > --- "Yurchenko, Michael"
> > > <michael.yurchenko@verizon.com> wrote:
> > > > This is an ospf-only lab. Unfortunately I did not
> > > > save the configs. I was
> > > > running it on 2500s w/12.0(8) ios
> > > >
> > > > -----Original Message-----
> > > > From: Nnanna Obuba [mailto:obuba@yahoo.com]
> > > > Sent: Monday, November 27, 2000 9:26 AM
> > > > To: Yurchenko, Michael; ccielab@groupstudy.com
> > > > Subject: Re: OSPF demand circuit
> > > >
> > > >
> > > >
> > > >
> > > > Is there redistribution from RIP or IGRP into
> > > ospf?
> > > > If so, make sure you are not sending 'native ospf'
> > > > networks back into the ospf process. Use the sh ip
> > > > ospf database command , and make sure that no
> > > > 'native
> > > > ospf' routes show up as type 5, and if it does
> > > > filter
> > > > it out in your redistribution.
> > > >
> > > > Hope this helps
> > > >
> > > > Nnanna
> > > >
> > > > --- "Yurchenko, Michael"
> > > > <michael.yurchenko@verizon.com> wrote:
> > > > > Hello!
> > > > >
> > > > > This weekend I was working on the fatkid.com's
> > > > OSPF
> > > > > lab and I was not able
> > > > > to get the ospf demand-circuit to work. If i set
> > > > up
> > > > > the IP ospf network
> > > > > nonbroadcast on the isdn, and then configure
> > > > > neighbors, the hellos don't get
> > > > > suppressed for some reason. If I do not specify
> > > > the
> > > > > network type, then
> > > > > hellos do get suppressed but the ckt gets
> > > brought
> > > > up
> > > > > by multicast to
> > > > > 224.0.0.5. While I could exclude this address
> > > from
> > > > > the interesting traffic,
> > > > > such exclusion is not in the fatkid's solution.
> > > > >
> > > > > Would any of you fine ladies and gentlemen have
> > > > any
> > > > > input on this?
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Michael Yurchenko
> > > > > michael.yurchenko@verizon.com
> > > > > verizon Network Integration
> > > > >
> > > > >
> > > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:57 GMT-3