
S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
1-2
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 1 Configuring User Accounts and RBAC
Information About User Accounts and RBAC
Note
User passwords are not displayed in the configuration files.
Caution
The Nexus 5000 Series switch does not support all numeric usernames, whether created with
or RADIUS, or created locally. Local users with all numeric names cannot be created. If an all numeric
user name exists on an AAA server and is entered during login, the user is not logged in. Usernames
must begin with an alphanumeric character and can contain only these special characters: ( + = . _ \ -).
The # and ! symbols are not supported. If the username contains characters that are not allowed, the
specified user is unable to log in.
Characteristics of Strong Passwords
A strong password has the following characteristics:
•
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 following are examples of strong passwords:
•
If2CoM18
•
2004AsdfLkj30
•
Cb1955S21
Note
Clear text passwords can contain alphanumeric characters only. Special characters, such as the dollar
sign ($) or the percent sign (%), are not allowed.
Tip
If a password is trivial (such as a short, easy-to-decipher password), the Nexus 5000 Series switch will
reject your password configuration. Be sure to configure a strong password as shown in the sample
configuration. Passwords are case sensitive.
About User Roles
User roles contain rules that define the operations allowed for the user who is assigned the role. Each
user role can contain multiple rules and each user can have multiple roles. For example, if role1 allows
access only to configuration operations, and role2 allows access only to debug operations, then users
who belong to both role1 and role2 can access configuration and debug operations. You can also limit
access to specific VSANs, VLANs and interfaces.