From: Prakash H Somani (pdsccie@xxxxxxxxxxxxxx)
Date: Tue Jul 09 2002 - 07:21:10 GMT-3
Hi,
Have you gone through following link ?
http://www.cisco.com/warp/public/104/dcprob.html
regards....Prakash
On Tue, 09 Jul 2002 Danny.Wang@alderwoods.com wrote :
>Hi Logan and Carlos,
>
>After i changed cost on the both dialer interfaces, i still got
>the same
>thing, just wondering anything else you changed, what
>value you ever used. Logan, what ISDN simulator you used?
>
>Thanks for your input anyway.
>
>r1#00:26:16: %DIALER-6-UNBIND: Interface BR0/0:1 unbound from
>profile Di1
>00:29:34: BR0/0 DDR: rotor dialout [priority]
>00:29:34: BR0/0 DDR: Dialing cause ip (s=172.19.1.6,
>d=224.0.0.5)
>00:29:34: BR0/0 DDR: Attempting to dial 8358662
>00:29:35: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
>up
>00:29:35: %DIALER-6-BIND: Interface BR0/0:1 bound to profile
>Di1
>00:29:36: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to
>8358662
>00:29:36: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected
> from 8358662
>, c
>ll lasted 1 seconds
>00:29:36: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
>down
>00:29:36: BR0/0 DDR: has total 0 call(s), dial_out 0, dial_in 0
>00:29:36: BR0/0:1 DDR: disconnecting call
>00:29:36: %DIALER-6-UNBIND: Interface BR0/0:1 unbound from
>profile Di1
>
>00:30:14: BR0/0 DDR: rotor dialout [priority]
>00:30:14: BR0/0 DDR: Dialing cause ip (s=172.19.1.6,
>d=224.0.0.5)
>00:30:14: BR0/0 DDR: Attempting to dial 8358662
>00:30:15: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
>up
>00:30:15: %DIALER-6-BIND: Interface BR0/0:1 bound to profile
>Di1
>00:30:16: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to
>8358662
>00:30:16: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected
> from 8358662
>, ca
>ll lasted 1 seconds
>00:30:16: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
>down
>00:30:16: BR0/0 DDR: has total 0 call(s), dial_out 0, dial_in 0
>00:30:16: BR0/0:1 DDR: disconnecting call
>00:30:16: %DIALER-6-UNBIND: Interface BR0/0:1 unbound from
>profile Di1
>
>
>r1#sh dialer
>
>BRI0/0 - dialer type = ISDN
>
>Dial String Successes Failures Last DNIS Last
>status
>0 incoming call(s) have been screened.
>0 incoming call(s) rejected for callback.
>
>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 idle
>
>BRI0/0:2 - dialer type = ISDN
>Idle timer (120 secs), Fast idle timer (20 secs)
>Wait for carrier (30 secs), Re-enable (15 secs)
>Dialer state is idle
>
>Di1 - dialer type = DIALER PROFILE
>Idle timer (120 secs), Fast idle timer (20 secs)
>Wait for carrier (30 secs), Re-enable (15 secs)
>Dialer state is idle
>Number of active calls = 0
>
>Dial String Successes Failures Last DNIS Last
>status
>8358662 49 0 00:00:09
>successful
>Default
>
>
>
>
>
> "Logan, Harold"
> <loganh@mccfl.edu To: "Carlos
>G Mendioroz" <tron@huapi.ba.ar>,
> >
><Danny.Wang@alderwoods.com>
> Sent by: cc:
><ccielab@groupstudy.com>
> nobody@groupstudy Subject: RE:
>ISDN and OSPF
> .com
>
>
> 07/08/2002 02:24
> PM
> Please respond to
> "Logan, Harold"
>
>
>
>
>
>
>I went ahead and set this up using Danny's configs, and setting
>the cost on
>the dialer interfaces fixed the problem. Before I did that, I got
>the same
>thing: the line was coming up from LSA's, but they weren't type
>1's. I'm
>guessing that when the line is brought back down, that represents
>a change
>in the ospf cost, therefore the line needs to be brought back up?
>Danny, if
>you still have this set up, try doing 'debug ip ospf
>lsa-generation',
>observe what happens for a few minutes, then do an 'isdn
>disconnect int
>bri0/0 all'. You should see things fairly quiet until the bri
>line gets
>brought down, then it comes right back up as more lsa's are
>generated.
>Likewise, if you force the line down with isdn disconnect, it
>gets brought
>right back up along with a handful of lsa's.
>
>Does anyone else have any input on why this happens, or know of a
>way to
>fix the problem other then ip ospf cost?
>
>Thanks,
>Hal
>
> > -----Original Message-----
> > From: Carlos G Mendioroz [mailto:tron@huapi.ba.ar]
> > Sent: Monday, July 08, 2002 4:01 PM
> > To: Danny.Wang@alderwoods.com
> > Cc: ccielab@groupstudy.com
> > Subject: Re: ISDN and OSPF
> >
> >
> > Danny,
> > Short answer: fix the ospf cost of your ddr interfaces (via ip
>ospf
> > cost).
> >
> > If you take a closer look, you should see that hellows are
> > supressed for
> > the
> > DDR interfaces. The link is being set because of an LSU
>triggered by a
> > change in
> > cost of the link.
> >
> > HTH
>
> >
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:23 GMT-3