From: Tony Olzak (aolzak@xxxxxxxxxxxxxxxxxxx)
Date: Fri Dec 01 2000 - 13:04:58 GMT-3
Maybe there is something to the order. Here's the order in which I do mine:
IP address (during the IP addressing phase), spids, Encaps, authentication,
no shut to verify SPIDs, dialer-maps, dialer-group, add network to OSPF, use
a ping to make sure everything works, demand circuit.
I also usually use legacy DDR.
I'm not knocking using that "no peer" command. That was one of the things I
kept in my head for backup. I've just never had a problem getting it to work
without adding the command.
Tony
----- Original Message -----
From: "Shaun Nicholson" <Shaun.Nicholson@kp.org>
To: "aolzak" <aolzak@buckeye-express.com>
Cc: "robertdevito" <robertdevito@hotmail.com>; "jagvans"
<jagvans@yahoo.com>; "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>
Sent: Friday, December 01, 2000 10:06 AM
Subject: Re: OSPF demand circuit
> I have never had a problem with the route flapping most of my issues I
have seen in my lab is as if the interface not being seen by OSPF when I do
a show ip ospf neig no reference for the bri0. I then do sh ip int ospf bri0
and ospf is enabled 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 plus 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 different IP subnet and it worked. Now explain that, I could not and
neither could James.
>
> I have seen this about 6 times out of the 12 or so times I have done this
is the lab it would simply appear as if OSPF is not enabled on the interface
but checking the interface it is.
> I have found that the no peer statement fixes this every single every time
without 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
command and I get it to work every time.
> Well all I can say is well done but some people are doing things
(inputting the correct commands) in a slightly different way and its
screwing up how the demand circuit process in the IOS works so please don't
knock the helpful tips that 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
interface 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" with great success as well. Again I know you should not need it but
why waste an hour on the lab trying to make something work and failing when
typing this command gets you up and running in less than 5 mins I would
however point out your problem to the proctor and tell him this is what you
intend to do to fix the issue.
>
> Thanks
> Shaun
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:57 GMT-3