Seems fine Tacack theoretically. If we can lab it out, then it should be clear.
With regards Kings On Fri, Sep 24, 2010 at 1:03 PM, Vybhav Ramachandran <[email protected]>wrote: > Hello Kings, > > Thanks for the response. So this is somewhat similar to the dot1x max-req > and max-reauth-period commands? > > Ok, i'm going to use an example. > > Suppose i've configured the : > > - *radius-server deadtime 1* > - *radius-server dead-criteria time 30 tries 3* > > My understanding is that, first the NAS sends the radius access-request to > the radius server and waits for the response. According the dead-criteria, > it waits for 30 seconds and if it receives no response, it tries again and > increments the tries counter to 1. It tries for 2 more times ( 30 X 2 = 60 > seconds ) and it then marks the radius-server as "DOWN". > > Now, after the radius-server is marked as down, no further access-request > messages are sent to the radius-server for the duration of time configured > using the "radius-server deadtime 1" command , i.e 1 minute. So after one > minute, the whole process starts all over again? > > The caveat to this whole thing is that , unless we configure the > radius-server deadtime command, even though the radius server fails to > respond after 3 attempts, it will still be shown as up and the NAS will keep > trying to contact the radius-server. > > Please correct me if i've erred somewhere. > > Cheers, > TacACK >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
