ret password, you change your level to privileged EXEC mode, which is level 15. If you'd like a user to be able to access privi- leged-level commands without entering the enable password, you can assign a higher privilege level to that user. In other words, configuring a user with a privilege level of 15 removes the need for that user to use the enable password to execute privileged commands: R1(config)#username GAD privilege 15 When you enter separate commands for the same user (either on the same or separate command lines), as I've just done with the secret and privilege commands, the parser will combine the commands into a single configuration entry: username GAD privilege 15 secret 5 $1$uyU6$6iZp6GLI1WGE1hxGDfQxc/ When this user logs into the router, she'll be greeted with the privileged # prompt instead of the normal exec prompt: User Access Verification Username: GAD Password: GAD-R1# Another interesting feature of the username command is the ability to assign a command to run automatically when the user authenticates. Here, I've configured the show ip interface brief command to run upon authentication: R1(config)#username GAD autocommand show ip interface brief When this user logs in, she'll be shown the output from this command and then promptly disconnected: User Access Verification Username: GAD Password: Interface IP-Address OK? Method Status Protocol FastEtherneto/o 10.100.100.1 YES NVRAM up FastEtherneto/1 unassigned YES NVRAM administratively down down Serial0/0/0:0 unassigned YES unset down This may not seem like a useful feature until you consider the possibility that a first- line engineer may need to execute only one command. Why give him access to anything else? Another possibility with the autocommand feature is to call a predefined menu of com- mands (configuring menus is outside the scope of this book): (config)#username GAD autocommand menu root-menu Chapter 26: Authentication in Cisco Devices If you specify a command or menu that does not exist, the user will not be able to log in even wit