You need aaa author exec command. The exec command makes the custom attribute for "cli-view-name=view_name" work.
Best Regards. ______________________ Adil On Jul 6, 2012, at 6:08 PM, Radim Jurica wrote: > Adil, > you got user EXEC ">" without any aaa authorization command [level] ?? > > R. > > 2012/7/6 Adil Pasha <[email protected]> > Yup, it is related to the IOS version. In real lab it worked and I got the # > sign right away but in my home lab I get ">". > > > Best Regards. > ______________________ > Adil > > On Jul 6, 2012, at 5:12 PM, waleed ' wrote: > >> for me it is working fine I moved to # privilige mode , I think it is >> related to version >> Regards >> >> From: [email protected] >> Date: Fri, 6 Jul 2012 23:08:11 +0200 >> To: [email protected] >> Subject: [OSL | CCIE_Security] Yusuf - Role-based access control >> >> Hello, >> anybody working now on Yusuf's Configurations Practice Labs, question 5.2 >> Role-based access control? >> >> In Lab debrief, when testing the CLI view solution he connect directly into >> priv EXEC (#) but I think it should be in user EXEC (>) >> >> When I configure CLI View using parser feature it should be always in user >> EXEC, is it right? >> >> Thanx in advance, >> >> Radim >> >> _______________________________________________ For more information >> regarding industry leading CCIE Lab training, please visit www.ipexpert.com >> Are you a CCNP or CCIE and looking for a job? Check out >> www.PlatinumPlacement.com >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> >> Are you a CCNP or CCIE and looking for a job? Check out >> www.PlatinumPlacement.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
