Cisco Nexus 5000 Series NX-OS Software Configuration Guide

About User Accounts

Tip The following words are reserved and cannot be used to configure users: bin, daemon, adm, lp, sync, shutdown, halt, mail, news, uucp, operator, games, gopher, ftp, nobody, nscd, mailnull, rpc, rpcuser, xfs, gdm, mtsuser, ftpuser, man, and sys.

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 TACACS+ 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.

The Nexus 5000 Series switch provides the following default user roles:

• network-admin (superuser)—Complete read and write access to the entire Nexus 5000 Series switch.
• network-operator—Complete read access to the Nexus 5000 Series switch.

Note If you belong to multiple roles, you can execute a combination of all the commands permitted by these roles. Access to a command takes priority over being denied access to a command. For example, suppose a user has RoleA, which denied access to the configuration commands. However, the users also has RoleB, which has access to the configuration commands. In this case, the users has access to the configuration commands.

About Rules

The rule is the basic element of a role. A rule defines what operations the role allows the user to perform. You can apply rules for the following parameters:

• Command—A command or group of commands defined in a regular expression.
• Feature—Commands that apply to a function provided by the Nexus 5000 Series switch.

– Enter the show role feature command to display the feature names available for this parameter.

• Feature group—Default or user-defined group of features.

– Enter the show role feature-group command to display the default feature groups available for this parameter.

These parameters create a hierarchical relationship. The most basic control parameter is the command. The next control parameter is the feature, which represents all commands associated with the feature. The last control parameter is the feature group. The feature group combines related features and allows you to easily manage of the rules.

You can configure up to 256 rules for each role. The user-specified rule number determines the order in which the rules are applied. Rules are applied in descending order. For example, if a role has three rules, rule 3 is applied before rule 2, which is applied before rule 1.

About User Role Policies

You can define user role policies to limit the switch resources that the user can access. You can define user role policies to limit access to interfaces, VLANs and VSANs.

User role policies are constrained by the rules defined for the role. For example, if you define an interface policy to permit access to specific interfaces, the user will not have access to the interfaces unless you configure a command rule for the role to permit the interface command. The Changing User Role Interface Policies contains an example configuration.

If a command rule permits access to specific resources (interfaces, VLANs or VSANs), the user is permitted to access these resources, even if they are not listed in the user role policies associated with that user.

Creating User Roles and Rules

Each user role can have up to 256 rules. You can assign a user role to more that one user account.

The rule number you specify determines the order in which the rules are applied. Rules are applied in descending order. For example, if a role has three rules, rule 3 is applied before rule 2, which is applied before rule 1.

To create user roles and specify rules, perform this task:

The following example shows how to create user roles and specify rules:

switch# configure terminal

switch(config)# role name UserA

switch(config-role)# rule deny command clear users

switch(config-role)# rule deny read-write

switch(config-role)# rule permit read feature router-bgp

switch(config-role)# rule deny read-write L3

switch(config-role)# description This role does not allow users to use clear commands

switch(config-role)# exit

switch(config)# show role

switch(config)# copy running-config startup-config

Creating Feature Groups

To create feature groups, perform this task:

Changing User Role Interface Policies

You can change a user role interface policy to limit the interfaces that the user can access. To change a user role interface policy, perform this task:

You can specify a list of interfaces that the role can access. You can specify it for as many interfaces as needed:

switch(config-role-interface)# permit interface ethernet 2/1

switch(config-role-interface)# permit interface fc 3/1

switch(config-role-interface)# permit interface vfc 30/1

Changing User Role VLAN Policies

You can change a user role VLAN policy to limit the VLANs that the user can access. To change a user role VLAN policy, perform this task:

Changing User Role VSAN Policies

You can change a user role VSAN policy to limit the VSANs that the user can access.

To change a user role VSAN policy to limit the VSANs that the user can access, perform this task: