From: Miguel.Ciena@xxxxxxxxxxxxxxx
Date: Thu Dec 21 2000 - 23:29:44 GMT-3
here is my sh dialer:
BRI0/0:1 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: ip (s=138.6.105.1, d=224.0.0.5)
Time until disconnect 117 secs
Connected to 4076220483 (r5)
here is my config of that router:
r5
interface BRI0/0
ip address 138.6.105.1 255.255.255.0
no ip directed-broadcast
encapsulation ppp
ip ospf demand-circuit
dialer map ip 138.6.105.2 name r10 broadcast 4076220483
dialer-group 1
isdn switch-type basic-dms100
isdn spid1 4076475738000 6475738
isdn spid2 4076475898100 6475898
no peer neighbor-route
ppp authentication pap
ppp pap sent-username r10 password 7 15060E1F10
r10
interface BRI0/0
ip address 138.6.105.2 255.255.255.0
no ip directed-broadcast
encapsulation ppp
dialer map ip 138.6.105.1 name r5 broadcast
dialer-group 1
isdn switch-type basic-dms100
isdn spid1 40762204830101
isdn spid2 40762204840101
ppp authentication pap
ppp pap sent-username r5 password 7 120D000406
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Padhu (LFG)
Sent: Thursday, December 21, 2000 4:41 PM
To: 'SherefMohamed@cdh.org'; tv
Cc: ccielab@groupstudy.com; mac38456@pegasus.cc.ucf.edu;
nobody@groupstudy.com
Subject: RE: OSPF and ISDN
ok....What the previous message intended to convey was that
"there is something happening to the ospf process which is triggerring
the
lsa and
hence u see the traffic to 224.0.0.5"...
now the question is to identify what is injecting or messing with the
ospf
process
and how you can have that process not affect the isdn....
I the intent is not to filter the 224.0.0.5 address...
-----Original Message-----
From: SherefMohamed@cdh.org [mailto:SherefMohamed@cdh.org]
Sent: Thursday, December 21, 2000 3:28 PM
To: tv
Cc: ccielab@groupstudy.com; mac38456@pegasus.cc.ucf.edu;
nobody@groupstudy.com
Subject: Re: OSPF and ISDN
debug ip packet will not help you, becuase you will always see that
224.0.0.5 is bringing up the line,
If you filtered that address from being intersting traffic then your
ospf
demand circuit will NEVER work !
"tv"
<tvarriale@tel To: "Miguel A. Ciena"
<mac38456@pegasus.cc.ucf.edu>
ocity.com> cc:
<ccielab@groupstudy.com>
Sent by: Subject: Re: OSPF and ISDN
nobody@groupst
udy.com
12/21/2000
03:15 PM
Please respond
to "tv"
Turn on debug ip packet detail and see why the circuit is coming up.
Then,
you can work on filtering what is necessary. I do not have any configs
because I am not near my stash :)
----- Original Message -----
From: "Miguel A. Ciena" <mac38456@pegasus.cc.ucf.edu>
To: <ccielab@groupstudy.com>
Sent: Thursday, December 21, 2000 2:45 PM
Subject: OSPF and ISDN
> I got one practice lab , that required R1 to R2 to use ISDN . In this
=
> ISDN need to be part of OSPF Area 0..Router 2 is running RIP also and
=
> I'm doing 2way redistribution. The question is how can you prevent the
=
> ISDN to kick in everytime is a topoly change...any config example =
> help!!!
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:09 GMT-3