Mailing List Archive

redial working for ppp auth failures too
I'm trying to enable an interval between failed auth attempts, which has to be
configured on the client modem.

I tried the "dialer redial" command:

int dialer 1
dialer redial interval 60 attempts 3 re-enable 300

but the problem is that this redial interval isn't working for ppp auth
failures, because it doesn't count them.

Di2 - dialer type = DIALER PROFILE
Idle timer (300 secs), Fast idle timer (30 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
xxxxxxxxxx 96 0 00:00:10 successful Default


So is there a way to delay the redial after a ppp auth failure?


--
Tassos

_______________________________________________
cisco-nas mailing list
cisco-nas@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nas
Re: redial working for ppp auth failures too [ In reply to ]
The below URL may solve your problem

http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide09186a008044206d.html

Best Regards,
Mounir Mohamed

On 3/30/06, Tassos Chatzithomaoglou <achatz@forthnet.gr> wrote:
>
> I'm trying to enable an interval between failed auth attempts, which has
> to be
> configured on the client modem.
>
> I tried the "dialer redial" command:
>
> int dialer 1
> dialer redial interval 60 attempts 3 re-enable 300
>
> but the problem is that this redial interval isn't working for ppp auth
> failures, because it doesn't count them.
>
> Di2 - dialer type = DIALER PROFILE
> Idle timer (300 secs), Fast idle timer (30 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
> xxxxxxxxxx 96 0 00:00:10 successful
> Default
>
>
> So is there a way to delay the redial after a ppp auth failure?
>
>
> --
> Tassos
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas
>



--
Best Reagrds,
Mounir Mohamed
Re: redial working for ppp auth failures too [ In reply to ]
I think the relevant command for Tassos' situation is "dialer
wait-for-line-protocol". Note the Usage Guidelines:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cr/hdia_r/dia_d2h.htm#wp1092154


Usage Guidelines

This command is supported only with encapsulation PPP.

By default the Cisco IOS software considers a dial-out attempt
successful if a connection is established to the physical layer (Layer 1
of the Open System Interconnection reference model). The *dialer
wait-for-line-protocol* command can be used to configure a router to
wait a specific amount of time for a line protocol to come up once a
physical layer connection has been established. If the call is dropped
before the timer has elapsed, the call will be considered a failure.
Redial will be triggered if the redial options have been configured with
the *dialer redial* interface configuration command. The dialer failure
statistics for the physical interface will be updated, which may
influence the selection of a physical dialer for the next dial attempt.
The physical dialer selection algorithm may be customized using the
*dialer rotor *interface configuration* *command.


Cheers,

Aaron

------------------------------------------------------------------------


> The below URL may solve your problem
>
> http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide09186a008044206d.html
> <http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide09186a008044206d.html>
>
> Best Regards,
> Mounir Mohamed
>
> On 3/30/06, *Tassos Chatzithomaoglou* <achatz@forthnet.gr
> <mailto:achatz@forthnet.gr>> wrote:
>
> I'm trying to enable an interval between failed auth attempts,
> which has to be
> configured on the client modem.
>
> I tried the "dialer redial" command:
>
> int dialer 1
> dialer redial interval 60 attempts 3 re-enable 300
>
> but the problem is that this redial interval isn't working for ppp
> auth
> failures, because it doesn't count them.
>
> Di2 - dialer type = DIALER PROFILE
> Idle timer (300 secs), Fast idle timer (30 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
> xxxxxxxxxx 96 0 00:00:10
> successful Default
>
>
> So is there a way to delay the redial after a ppp auth failure?
>
>
> --
> Tassos
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net <mailto:cisco-nas@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-nas
>
>
>
>
> --
> Best Reagrds,
> Mounir Mohamed
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas
>
Re: redial working for ppp auth failures too [ In reply to ]
Quite strangely this does not seem to work on dialers attached to atm/adsl interfaces :(
When used on dialers attached to isdn bri interfaces, it does the job nicely ;)

Tassos

Aaron Leonard wrote on 30/3/2006 8:10 ìì:
> I think the relevant command for Tassos' situation is "dialer
> wait-for-line-protocol". Note the Usage Guidelines:
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cr/hdia_r/dia_d2h.htm#wp1092154
>
>
> Usage Guidelines
>
> This command is supported only with encapsulation PPP.
>
> By default the Cisco IOS software considers a dial-out attempt
> successful if a connection is established to the physical layer (Layer 1
> of the Open System Interconnection reference model). The *dialer
> wait-for-line-protocol* command can be used to configure a router to
> wait a specific amount of time for a line protocol to come up once a
> physical layer connection has been established. If the call is dropped
> before the timer has elapsed, the call will be considered a failure.
> Redial will be triggered if the redial options have been configured with
> the *dialer redial* interface configuration command. The dialer failure
> statistics for the physical interface will be updated, which may
> influence the selection of a physical dialer for the next dial attempt.
> The physical dialer selection algorithm may be customized using the
> *dialer rotor *interface configuration* *command.
>
>
> Cheers,
>
> Aaron
>
> ------------------------------------------------------------------------
>
>
>> The below URL may solve your problem
>>
>> http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide09186a008044206d.html
>> <http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide09186a008044206d.html>
>>
>> Best Regards,
>> Mounir Mohamed
>>
>> On 3/30/06, *Tassos Chatzithomaoglou* <achatz@forthnet.gr
>> <mailto:achatz@forthnet.gr>> wrote:
>>
>> I'm trying to enable an interval between failed auth attempts,
>> which has to be
>> configured on the client modem.
>>
>> I tried the "dialer redial" command:
>>
>> int dialer 1
>> dialer redial interval 60 attempts 3 re-enable 300
>>
>> but the problem is that this redial interval isn't working for ppp
>> auth
>> failures, because it doesn't count them.
>>
>> Di2 - dialer type = DIALER PROFILE
>> Idle timer (300 secs), Fast idle timer (30 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
>> xxxxxxxxxx 96 0 00:00:10
>> successful Default
>>
>>
>> So is there a way to delay the redial after a ppp auth failure?
>>
>>
>> --
>> Tassos
>>
>> _______________________________________________
>> cisco-nas mailing list
>> cisco-nas@puck.nether.net <mailto:cisco-nas@puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-nas
>>
>>
>>
>>
>> --
>> Best Reagrds,
>> Mounir Mohamed
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> cisco-nas mailing list
>> cisco-nas@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nas
>>
>
_______________________________________________
cisco-nas mailing list
cisco-nas@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nas