From: Javier Tomé (fjtm@tid.es)
Date: Wed Oct 26 2005 - 11:50:39 GMT-3
Remember the experience for the exam... ;-)
rionaldi wrote:
> Strange, the same configuration, but i restart the router.. work just
> fine.. troubleshooting for 3 hrs, resolve just 1 boot.
>
>
> ----- Original Message ----- From: "rionaldi" <rionaldi@cbn.net.id>
> To: "Chris Lewis" <chrlewiscsco@yahoo.com>; <ccielab@groupstudy.com>
> Sent: Wednesday, October 26, 2005 9:45 PM
> Subject: Re: Dialer Watch with ISIS
>
>
>> the debug dialer is as attached below on my email.. again and again..
>>
>> Rack2R5#debug dialer
>> Dial on demand events debugging is on
>> Rack2R5#
>> *Mar 1 05:51:10.302: BR0/0:2 DDR: idle timeout
>> *Mar 1 05:51:10.302: DDR: Dialer Watch: watch-group = 1
>> *Mar 1 05:51:10.302: DDR: network 150.2.4.0/255.255.255.0 UP,
>> *Mar 1 05:51:10.302: DDR: primary DOWN
>> Rack2R5#
>> *Mar 1 05:51:15.302: BR0/0:2 DDR: idle timeout
>> *Mar 1 05:51:15.302: DDR: Dialer Watch: watch-group = 1
>> *Mar 1 05:51:15.302: DDR: network 150.2.4.0/255.255.255.0 UP,
>> *Mar 1 05:51:15.302: DDR: primary DOWN
>> Rack2R5#
>> *Mar 1 05:51:20.302: BR0/0:2 DDR: idle timeout
>> *Mar 1 05:51:20.302: DDR: Dialer Watch: watch-group = 1
>> *Mar 1 05:51:20.302: DDR: network 150.2.4.0/255.255.255.0 UP,
>> *Mar 1 05:51:20.302: DDR: primary DOWN
>>
>>
>> As my understanding this issue means that the dialer treated the
>> 150.2.4.0/24 up but still received from the BRI not from the S0/0
>> that why the primary still down.
>> Alhtough the ISIS adj happen already with router
>>
>>
>> ----- Original Message ----- From: "Chris Lewis"
>> <chrlewiscsco@yahoo.com>
>> To: "Prio Utomo" <rionaldi@gmail.com>; <ccielab@groupstudy.com>
>> Sent: Wednesday, October 26, 2005 7:26 PM
>> Subject: Re: Dialer Watch with ISIS
>>
>>
>>> What is the output of the debug dialer?
>>>
>>> Prio Utomo <rionaldi@gmail.com> wrote:I configure ISIS between 2
>>> routers connected with Serial and ISDN to simulate
>>> Dial on Demand using Dialer Watch.
>>>
>>>
>>> When I put the serial off, the dialer watch triggered and call the
>>> opposite
>>> router, but when I turn on the serial again. The dialer watch won't
>>> go down,
>>> when i debug the result as below
>>>
>>> *Mar 1 04:27:16.878: BR0/0:1 DDR: idle timeout
>>> *Mar 1 04:27:16.878: DDR: Dialer Watch: watch-group = 1
>>> *Mar 1 04:27:16.878: DDR: network 150.2.4.0/255.255.255.0 UP,
>>> *Mar 1 04:27:16.878: DDR: primary DOWN
>>>
>>>
>>> I understand that the router still receving 150.2.4.0/255.255.255.0
>>> from the
>>> BRI. I increase the metric of isis in BRI but still the isdn does
>>> not off.
>>>
>>> Any suggestion why this condition happen, how to resolve?
>>>
>>> Thx,
>>> rionaldi
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>>
>>> ---------------------------------
>>> Yahoo! FareChase - Search multiple travel sites in one click.
>>>
>>> ---------------------------------
>>> Yahoo! FareChase - Search multiple travel sites in one click.
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:54 GMT-3