From: m destienne (mdestienne@yahoo.com)
Date: Thu Apr 20 2006 - 16:22:53 GMT-3
i don't think victor is having an issue. he locked
himself from his router but he was smart enough to
issue the reload command before issuing the aaa
commands.
he's providing a real life example of the usefulness
of the reload command.
--- john matijevic <john.matijevic@gmail.com> wrote:
> Hello Victor,
> I am sorry I don't understand your question. So what
> is the issue you are
> having?
>
> Sincerely,
> John
>
>
> On 4/18/06, Victor Cappuccio
> <cvictor@protokolgroup.com> wrote:
> >
> > just happy sharing a moment with friends
> >
> > cha-gw-01(config)#aaa new-model
> > cha-gw-01(config)#aaa authentication login default
> group tacacs+ local
> > cha-gw-01(config)#aaa authorization
> config-commands
> > cha-gw-01(config)#aaa authorization exec default
> group tacacs+ local
> > cha-gw-01(config)#aaa authorization commands 15
> default group tacacs+
> > cha-gw-01(config)#aaa accounting exec default
> start-stop group tacacs+
> > % Authorization failed.
> >
> > cha-gw-01(config)#aaa accounting commands 15
> default start-stop group
> > tacacs+
> > % Authorization failed.
> >
> >
> > cha-gw-01#conf te
> > % Authorization failed.
> >
> > cha-gw-01#show reload
> > Reload scheduled in 6 minutes by console
> >
> >
> > ***
> > *** --- SHUTDOWN in 0:05:00 ---
> > ***
> > Boleita-Sw#show reload
> > Reload scheduled in 2 minutes and 34 seconds by
> console
> >
> >
> > Good Lord, how long are 2 min and 34 sec when you
> incorrecly configure
> > AAA in a production environment, hope no to have
> more fun when when sw
> > reloads it self without notification..
> > ;)
> >
> >
>
This archive was generated by hypermail 2.1.4 : Mon May 01 2006 - 11:41:58 GMT-3