h proper authentication. You can disable the automatic disconnection after autocommand with the nohangup keyword: R1 (config)#username GAD nohangup autocommand menu root-menu With NX-OS, you create local users with the username command, but you must also assign a role to each user. Before you can do that, and in fact, before you can even configure a Nexus switch, you must determine if you want to enable strong passwords. When you first turn a Nexus switch on, or when you first connect to a newly created VDC, you will be greeted with the following dialog: Daisy# switchto vdc Cozy System Admin Account Setup Do you want to enforce secure password standard (yes/no) [y]: Enforcing secure password standards is a good idea, and it should be done whenever possible. It may even be required if you need to comply with standards such as PCI or SOX. It is sort of a pain because, much like Unix, it will force you to have 169 lowercase, uppercase, numeric, Greek, and Sumerian characters in your passwords. Actually, the password needs to be eight or more characters. OK, SO I made up the part about Greek and Sumerian, too, but it sure feels like ancient languages are a requirement when you look at the strong password rules. According to Cisco's documentation, a strong pass- word has the following characteristics: Is at least eight characters long Does not contain many consecutive characters (such as "abcd") Does not contain many repeating characters (such as "aaabbb") Does not contain dictionary words Does not contain proper names Contains both uppercase and lowercase characters Contains numbers The same documentation goes on to list the following examples of strong passwords: If2CoM18 2004AsdfLkj30 Cb1955S21 If you're like me, you'll spend a ridiculous amount of time coming up with a password that meets the requirements and is in any way memorable. Sometimes I think learning ancient Sumerian would be simpler. Still, if you work in a real environment with real security concerns-and who doesn't?-you'll need to employ strong passwo