OSPF Demand-C Resolved/Take Note!

From: kpalmer (kip.palmer@verizon.net)
Date: Fri Sep 20 2002 - 02:38:52 GMT-3


I'm very RELIEVED!!! (Like you care)

My OSPF Demand circuit DILEMMA IS OVER!

In previous posts, I threatened suicide and/or throwing in the towel
over OSPF Demand-C "over Aux-to-Aux", failure to be quite.

I'm not talking about a redistributed route keeping it up. I'm talking
about
*Change in LSA 0.0.0.0*...?, in the following topology:

     A0 A0
     r1----------r2
      \ /
       \ -|--|- /
          DDR
A10 Stub <or> A0 V-Link

 *IT DOESN'T GET ANY MORE BASIC*

I just lab'd it on a ISDN Sim and the circuit is quiet like a baby. It
actually works. So, the problemo is somewhere in my Async config and
I really don't care to resolve it. Reasoning, not tested on, and not a
real
world resolution.

SO FOR THOSE CURRENTLY WITH A ROPE AROUND YOUR NECK, GET DOWN!!

I'll include my, Interface Async config's for anyone who care's to
resolve the aux-to-aux, PPP debacle. E.I., *Change in LSA 0.0.0.0*

Late,

KPALMER....
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

hostname r6 === CALLED Router

chat-script dummy " "

username r1_net password (^*(^U^*&(*

interface Async1
bandwidth 64
ip address 170.100.16.6 255.255.255.240
encapsulation ppp
async default routing
async dynamic routing
async mode dedicated
ip ospf cost 9999
ip ospf demand-circuit
no peer neighbor-route
dialer in-band
dialer idle-timeout 60
dialer map ip 170.100.16.1 name r1_net broadcast
dialer-group 1
ppp authen chap

router ospf 6
router-id 170.100.9.9
network 170.100.16.0 0.0.0.15 area 10
area 10 stub no-summary

dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit

line aux 0
exec-timeout 0 0
script dialer dummy
modem Dialin
transport input all
flowcontrol hardware



This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:57 GMT-3