The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco Nexus 1000V commands that begin with the letter R.
To configure the dead-time interval for all RADIUS servers used by a device, use the radius-server deadtime command. To revert to the default, use the no form of this command.
radius-server deadtime minutes
no radius-server deadtime minutes
minutes |
Number of minutes for the dead-time interval. The range is from 1 to 1440 minutes. |
0 minutes
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
The dead-time interval is the number of minutes before the device checks a RADIUS server that was previously unresponsive.
Note The default idle timer value is 0 minutes. When the idle time interval is 0 minutes, periodic RADIUS server monitoring is not performed.
This example shows how to configure the global dead-time interval for all RADIUS servers to perform periodic monitoring:
n1000v# config t
n1000v(config)# radius-server deadtime 5
This example shows how to revert to the default for the global dead-time interval for all RADIUS servers and disable periodic server monitoring:
n1000v# config t
n1000v(config)# no radius-server deadtime 5
|
|
---|---|
show radius-server |
Displays RADIUS server information. |
To allow users to send authentication requests to a specific RADIUS server when logging in, use the radius-server directed request command. To revert to the default, use the no form of this command.
radius-server directed-request
no radius-server directed-request
This command has no arguments or keywords.
Disabled
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
You can specify the username@vrfname:hostname during login, where vrfname is the virutal routing and forwarding (VRF) instance to use and hostname is the name of a configured RADIUS server. The username is sent to the RADIUS server for authentication.
This example shows how to allow users to send authentication requests to a specific RADIUS serve when logging in:
n1000v# config t
n1000v(config)# radius-server directed-request
This example shows how to disallow users to send authentication requests to a specific RADIUS server when logging in:
n1000v# config t
n1000v(config)# no radius-server directed-request
|
|
---|---|
show radius-server directed-request |
Displays the directed request RADIUS server configuration. |
To configure RADIUS server parameters, use the radius-server host command. To revert to the default, use the no form of this command.
radius-server host {hostname | ipv4-address | ipv6-address}
[key [0 | 7] shared-secret [pac]] [accounting]
[acct-port port-number] [auth-port port-number] [authentication] [retransmit count]
[test {idle-time time | password password | username name}]
[timeout seconds [retransmit count]]
no radius-server host {hostname | ipv4-address | ipv6-address}
[key [0 | 7] shared-secret [pac]] [accounting]
[acct-port port-number] [auth-port port-number] [authentication] [retransmit count]
[test {idle-time time | password password | username name}]
[timeout seconds [retransmit count]]
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
When the idle time interval is 0 minutes, periodic RADIUS server monitoring is not performed.
This example shows how to configure RADIUS server authentication and accounting parameters:
n1000v# config terminal
n1000v(config)# radius-server host 10.10.2.3 key HostKey
n1000v(config)# radius-server host 10.10.2.3 auth-port 2003
n1000v(config)# radius-server host 10.10.2.3 acct-port 2004
n1000v(config)# radius-server host 10.10.2.3 accounting
n1000v(config)# radius-server host radius2 key 0 abcd
n1000v(config)# radius-server host radius3 key 7 1234
n1000v(config)# radius-server host 10.10.2.3 test idle-time 10
n1000v(config)# radius-server host 10.10.2.3 test username tester
n1000v(config)# radius-server host 10.10.2.3 test password 2B9ka5
|
|
---|---|
show radius-server |
Displays RADIUS server information. |
To configure a RADIUS shared secret key, use the radius-server key command. To remove a configured shared secret, use the no form of this command.
radius-server key [0 | 7] shared-secret
no radius-server key [0 | 7] shared-secret
Clear text
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
You must configure the RADIUS preshared key to authenticate the switch on the RADIUS server. The length of the key is restricted to 63 characters and can include any printable ASCII characters (white spaces are not allowed). You can configure a global key to be used for all RADIUS server configurations on the switch. You can override this global key assignment for an individual host by using the key keyword in the radius-server host command.
This example shows how to provide various scenarios to configure RADIUS authentication:
n1000v# config terminal
n1000v(config)# radius-server key AnyWord
n1000v(config)# radius-server key 0 AnyWord
n1000v(config)# radius-server key 7 public pac
|
|
---|---|
show radius-server |
Displays RADIUS server information. |
To specify the number of times that the device should try a request with a RADIUS server, use the radius-server retransmit command. To revert to the default, use the no form of this command.
radius-server retransmit count
no radius-server retransmit count
count |
Number of times that the device tries to connect to a RADIUS server(s) before reverting to local authentication. The range is from 1 to 5 times. |
1 retransmission
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to configure the number of retransmissions to RADIUS servers:
n1000v# config t
n1000v(config)# radius-server retransmit 3
This example shows how to revert to the default number of retransmissions to RADIUS servers:
n1000v# config t
n1000v(config)# no radius-server retransmit 3
|
|
---|---|
show radius-server |
Displays RADIUS server information. |
To specify the time between retransmissions to the RADIUS servers, use the radius-server timeout command. To revert to the default, use the no form of this command.
radius-server timeout seconds
no radius-server timeout seconds
seconds |
Number of seconds between retransmissions to the RADIUS server. The range is from 1 to 60 seconds. |
5 seconds
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to configure the timeout interval:
n1000v# config t
n1000v(config)# radius-server timeout 30
This example shows how to revert to the default interval:
n1000v# config t
n1000v(config)# no radius-server timeout 30
|
|
---|---|
show radius-server |
Displays RADIUS server information. |
To set the dedicated rate mode for the specified ports, use the rate-mode dedicated command.
rate-mode dedicated
no rate-mode
This command has no arguments or keywords.
Shared rate mode is the default.
Interface configuration (config-if)
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
Use the rate-mode dedicated command to set the dedicated rate mode for the specified ports.
On a 32-port 10-Gigabit Ethernet module, each set of four ports can handle 10 gigabits per second (Gb/s) of bandwidth. You can use the rate-mode parameter to dedicate that bandwidth to the first port in the set of four ports or share the bandwidth across all four ports.
Note When you dedicate the bandwidth to one port, you must first administratively shut down the ports in the group, change the rate mode to dedicated, and then bring the dedicated port administratively up.
Table 1-1 identifies the ports that are grouped together to share each 10 Gb/s of bandwidth and which port in the group can be dedicated to utilize the entire bandwidth.
When you enter the rate-mode dedicated command, the full bandwidth of 10 Gb is dedicated to one port. When you dedicate the bandwidth, all subsequent commands for the port are for dedicated mode.
This example shows how to configure the dedicated rate mode for Ethernet ports 4/17, 4/19, 4/21, and 4/23:
n1000v# config t
n1000v(config)# interface ethernet 4/17, ethernet 4/19, ethernet 4/21, ethernet 4/23
n1000v(config-if)# shutdown
n1000v(config-if)# interface ethernet 4/17
n1000v(config-if)# rate-mode dedicated
n1000v(config-if)# no shutdown
n1000v(config-if)#
|
|
show interface |
Displays interface information, which includes the current rate mode dedicated. |
To configure a flow record, use the record command. To remove the flow record configuration, use the no form of the command.
record {name | netflow ipv4 {original-input | original-output | protocol-port} | netflow-original}
no record {name | netflow ipv4 {original-input | original-output | protocol-port} | netflow-original}
None
Flow monitor configuration (config-flow-monitor)
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
A flow record defines the information that NetFlow gathers, such as packets in the flow and the types of counters gathered per flow. You can define new flow records or use the pre-defined flow record.
This example shows how to configure a flow record to use a the predefined traditional IPv4 input NetFlow record:
n1000v# config t
n1000v(config)# flow monitor testmon
n1000v(config-flow-monitor)# record netflow ipv4 original-input
n1000v(config-flow-monitor)#
This example shows how to remove the predefined traditional IPv4 input NetFlow flow record configuration:
n1000v# config t
n1000v(config)# flow monitor testmon
n1000v(config-flow-monitor)# no record netflow ipv4 original-input
n1000v(config-flow-monitor)#
|
|
---|---|
show flow monitor |
Displays NetFlow monitor configuration information. |
show flow record |
Displays NetFlow record configuration information. |
To reload a module in the device, use the reload module command.
reload module slot [force-dnld]
slot |
Chassis slot number. |
force-dnld |
(Optional) Forces the download of software to the module. |
None
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
Use the show hardware command to display information about the hardware on your device.
This example shows how to reload a module:
n1000v# reload module 2
|
|
---|---|
show version |
Displays information about the software version. |
To connect to remote machines, use the remote command. To disconnect, use the no form of this command.
remote {ip address address | hostname name}
no remote {ip address address | hostname name}
ipaddress |
Specifies an IP address. |
address |
IPv4 address. The format is A.B.C.D. |
hostname |
Specifies the remote host name. |
name |
Host name. The range of valid values is 1 to 128. |
None
SVS connection configuration (config-svs-conn)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to connect to a remote machine:
n1000v#
configure terminal
n1000v(config)#
svs connection svsconn1
n1000v(config-svs-conn)#
remote hostname server1
n1000v(config-svs-conn)#
|
|
---|---|
show svs |
Displays SVS information. |
To resequence a list with sequence numbers, use the resequence command.
resequence {{{ip | mac} access-list} | time-range} name number increment
None
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to resequence the first entry in the MAC ACL named aclOne:
n1000v# configure terminal
n1000v(config)# resequence mac access-list aclOne 1 2
n1000v(config)#
|
|
---|---|
show access-list |
Displays ACLs. |
To remove a directory, use the rmdir command.
rmdir [filesystem:[//module/]]directory
Removes the directory from the current working directory.
Any
network-admin
|
|
---|---|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to remove the my_files directory:
n1000v# rmdir my_files
|
|
---|---|
cd |
Changes the current working directory. |
dir |
Displays the directory contents. |
pwd |
Displays the name of the current working directory. |
To configure a role that will support a specified group of features, use the role feature-group name command. To remove the role, use the no form of this command.
role feature-group name group-name
no role feature-group name group-name
group-name |
Descriptive name for the role. The name is case-sensitive and an alphanumeric string of up to 32 characters in length. |
None
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to create a role called GroupA to support a specified group of features:
n1000v# config t
n1000v(config)# role feature-group name GroupA
n1000v(config-role-featuregrp)#
This example shows how to remove the role called GroupA:
n1000v# config t
n1000v(
config)#
no role feature-group name GroupA
n1000v(config-role-featuregrp)#
To create a user role, use the role name command. To remove the role, use the no form of this command.
role name role-name
no role name role-name
role-name |
Creates a user role of this name. |
None
Global configuration (config)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to create a role named UserA:
n1000v #
config t
n1000v(
config)#
role name UserA
This example shows how to remove the UserA role:
n1000v(
config)#
no role UserA
To create a rule defining criteria for a user role, use the rule command. To remove a rule, use the no form of this command.
rule number {deny | permit} {read | read-write [feature feature-name | feature-group group-name] | command command-name}
no rule number
None
Role configuration (config-role)
network-admin
|
|
4.0(4)SV1(1) |
This command was introduced. |
The rule number specifies the order in which the rule is applied, in descending order. For example, if a role has three rules, rule 3 is applied first, rule 2 is applied next, and rule 1 is applied last. You can configure up to 256 rules for each role.
This example shows how to create a rule that denies access to the clear users command:
n1000v# config t
n1000v(config)# role name UserA
n1000v(config-role)# rule 1 deny command clear users
n1000v(config-role)#
This example shows how to remove the rule 1 configuration:
n1000v# config t
n1000v(config)# role name UserA
n1000v(
config-role)#
no rule 1
|
|
---|---|
username |
Configures information about the user. |
show role |
Displays the user role configuration. |
To run a command script that is saved in a file, use the run-script command.
run-script {bootflash: | volatile:} filename
None
Any
network-admin
network-operator
|
|
4.0(4)SV1(1) |
This command was introduced. |
This example shows how to run a command script that is saved in the Sample file on the Volatile file system.
n1000v(
config)#
run-script volatile:Sample
n1000v(
config)#
|
|
---|---|
cd |
Changes the current working directory. |
copy |
Copies files. |
dir |
Displays the contents of the working directory. |
pwd |
Displays the name of the present working directory (pwd). |