-
Cisco SN 5400 Series Storage Router Command Reference, Release 3.4
-
About This Guide
-
Chapter 1 - CLI Overview
-
Chapter 2 - A Commands
-
Chapter 3 - C Commands
-
Chapter 4 - D Commands
-
Chapter 5 - E Commands
-
Chapter 6 - F Commands
-
Chapter 7 - H Commands
-
Chapter 8 - I Commands
-
Chapter 9 - L Commands
-
Chapter 10 - M Commands
-
Chapter 11 - N Commands
-
Chapter 12 - P Commands
-
Chapter 13 - R Commands
-
Chapter 14 - S Commands
-
Chapter 15 - Show Commands
-
Chapter 16 - T Commands
-
Chapter 17 - U Commands
-
Chapter 18 - V Commands
-
Chapter 19 - Z Commands
-
Table Of Contents
R Commands
This chapter covers the following commands:
radius-server deadtime
To improve RADIUS response time when some servers might be unavailable, use the radius-server deadtime command to cause the storage router to skip the unavailable servers immediately. To set the dead time to 0, effectively preventing the storage router from skipping any RADIUS server, use the no form of this command.
radius-server deadtime minutes
no radius-server deadtime
Syntax Description
minutes
The length of time, in minutes, for which a RADIUS server is skipped over by the storage router when requesting AAA authentication services, up to a maximum of 1440 minutes (24 hours).
Defaults
The dead time is set to zero (0) by default.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command to cause the storage router to mark as "dead" any RADIUS servers that fail to respond to authentication requests, thus avoiding the wait for the authentication request to time out before trying the next configured server. A RADIUS server marked as dead is skipped by additional requests for the specified number of minutes, unless all RADIUS servers are marked as dead. If all RADIUS servers are marked as dead, the deadtime setting is ignored.
This is a global command that applies to all configured RADIUS servers. To override the global dead time setting for a specific group of RADIUS server, use the aaa group server radius deadtime command.
Examples
The following example specifies a dead time of five minutes for all RADIUS servers that fail to respond to AAA authentication requests:
[SN5428-2A]# radius-server deadtime 5The following example effectively sets a dead time of zero minutes for all RADIUS servers. The storage router will wait for any AAA authentication request to a RADIUS server to time out before retransmitting or retrying the next configured server.
[SN5428-2A]# no radius-server deadtimeRelated Commands
Specify the length of time the storage router can skip a RADIUS server in the named group that is marked as unavailable.
Display AAA configuration information.
radius-server host
To specify a RADIUS server to be used for AAA authentication services, use the radius-server host command. To delete the specified RADIUS server, use the no form of this command.
radius-server host ip-address [auth-port port-number] [timeout seconds] [retransmit retries] [key key-string]
no radius-server host ip-address [auth-port port-number]
Syntax Description
Defaults
No RADIUS server is specified.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
AAA authentication services are used to provide the following authentication types:
•
iSCSI authentication—provides authentication of IP hosts requiring access to storage via SCSI routing instances
•
•
You can use multiple radius-server host commands to specify multiple RADIUS servers. AAA authentication searches for servers in the order in which you specify them.
Use the aaa group server radius server command to add a RADIUS server to a server group. If you delete a RADIUS server, delete the server from the RADIUS server using the no aaa group server radius server command.
If no host-specific timeout, retransmit, or key values are specified, the global values apply to each RADIUS server.
A retransmit value of zero (0) disables RADIUS request retransmission.
If you use spaces in the key, enclose the key in quotation marks.
Note
Examples
The following example identifies the server with IP address 10.5.0.53 as the RADIUS server and uses the default port for authentication:
[SN5428-2A]# radius-server host 10.5.0.53The following example identifies port 1612 as the destination port for authentication requests on the RADIUS server 10.6.0.61:
[SN5428-2A]# radius-server host 10.6.0.61 auth-port 1612The following example identifies the server with IP address 10.5.0.53 as the RADIUS server, uses ports 1612 as the authorization port, sets the timeout value to 6, sets the retransmit value to 5, and sets "rad123" as the encryption key, matching the key on the RADIUS server:
[SN5428-2A]# radius-server host 10.5.0.53 auth-port 1612 timeout 6 retransmit 5 key rad123Related Commands
radius-server key
To set the authentication and encryption key to be used for all RADIUS communications between the storage router and the RADIUS daemon, use the radius-server key command. To disable the key, use the no form of this command.
radius-server key key-string
no radius-server key
Syntax Description
key-string
The authentication and encryption key string to be used for all RADIUS communications, in clear text. If spaces are used in the key, enclose the key in quotation marks.
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use the radius-server key command to set the global authentication and encryption key to be used by the storage router for communications with RADIUS servers. The key entered as part of the command must match the key used on the RADIUS daemon. If the key includes spaces, enclose the key in quotation marks.
To override the global key for a specific RADIUS server, use the radius-server host command with the key keyword.
Examples
The following example sets the global authentication and encryption key to my key string:
[SN5428-2A]# radius-server key "my key string"Related Commands
radius-server retransmit
To specify the number of times the storage router resends the RADIUS request to each server in the list of configured RADIUS servers after a timeout occurs, use the radius-server retransmit command. To disable retransmission, use the no form of this command.
radius-server retransmit retries
no radius-server retransmit
Syntax Description
retries
The number of times the request can be resent to each server in the list. Enter a value in the range of 0 to 100. A value of zero (0) disables RADIUS request retransmission. The default is 3.
Defaults
The number of possible resends defaults to three.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
If multiple RADIUS servers are configured for AAA authentication, the storage router attempts to reach each server in the list before incrementing the retransmit count. To disable RADIUS request retransmission, set the retransmit count to zero.
To override the global retransmit count for a specific RADIUS server, use the radius-server host command with the retransmit keyword.
Examples
The following example sets the retransmit count to six, meaning the request can be resent up to six times for every RADIUS server:
[SN5428-2A]# radius-server retransmit 6The following example disables RADIUS request retransmission by setting the retransmit count to zero:
[SN5428-2A]# radius-server retransmit 0Related Commands
radius-server timeout
To set the global interval that the storage router waits for a RADIUS server to reply, use the radius-server timeout command. To restore the default, use the no form of this command.
radius-server timeout seconds
no radius-server timeout
Syntax Description
seconds
The global timeout value in seconds. Enter a value in the range of 1 to 1000. The default is 5.
Defaults
The timeout value defaults to five seconds.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command to set the number of seconds the storage router waits for a RADIUS server to reply before timing out.
To override the global timeout value for a specific RADIUS server, use the radius-server host command with the timeout keyword.
Examples
The following example sets the global timeout value to 10. You may want to increase the timeout value if you have network problems or if the RADIUS servers are slow to response, which causes consistent timeouts when a lower timeout value is used.
[SN5428-2A]# radius-server timeout 10Related Commands
read script
To read and execute the CLI commands in a command file, use the read script command.
read script command-file [force [parameters]]
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
2.5.1
The parameters argument was added.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use the show bootconfig and show runningconfig commands with the to keyword to create basic files containing many of the CLI commands that were issued to create the storage router's bootable or currently running configuration. These files can be modified and used as command files to automate common tasks.
You can also manually create a command file. If you have a set of CLI commands that you run periodically, you can place them in a command file, copy that file to the storage router script directory and use the read script command to execute them when needed.
Each command should be on a separate line or contain a backslash ( \ ) as the line continuation character at the end of the line. At the end of a continuation sequence, add a blank line as a separator between the sequence and any following command. Any line beginning with an exclamation mark (!) or a number sign (#) is considered to be a comment and will not be executed.
When the command is issued without the force keyword, you are reminded that the action may change the configuration of the storage router and are then prompted to confirm your actions. When the command is issued with the force keyword, all warning prompts and messages are suppressed and the script is executed immediately.
You can also pass optional parameters to the script to control processing. Any parameter that includes spaces must be enclosed in quotation marks. Within the script, use the key character "@" to instruct the script execution function to substitute the value of the specified parameter. Whenever the execution function encounters @1, it substitutes the value of the first passed parameter. The value of the second parameter is substituted for @2, and so forth.
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for additional information about using scripts to automate tasks.
Examples
The following example reads and executes the CLI commands in the command file named myCommands.
[SN5428-2A]# read script myCommands*** Warning: this script may change your configuration.Do you want to continue? [yes/no (yes)] yesRelated Commands
reboot
To cause the storage router to shut down and then restart, issue the reboot command.
Note
reboot [force] [fast]
Syntax Description
fast
(Optional) Force a soft reboot of the storage router, bypassing hardware diagnostics.
force
(Optional) Force an immediate reboot of the storage router.
Defaults
If there are unsaved configuration changes when the command is issued, the default is to save all changes before rebooting. If the command is issued with the optional force keyword, any unsaved configuration changes are discarded.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
If the storage router is participating in a cluster, the reboot command will cause any SCSI routing instances running on this storage router to failover to another node in the cluster. At restart, the cluster determines any SCSI routing instances that should start on the storage router. If the node is identified as the preferred storage router for any SCSI routing instance (via the scsirouter primary command), that instance will start running on the node (assuming targets and critical resources are available).
If the reboot command is issued with no keywords and there are unsaved changes to the current configuration, you can choose to either save all changes or reboot without saving any changes.
Use the force keyword to cause an immediate reboot of the storage router, discarding any unsaved configuration changes. Append the optional fast keyword to bypass diagnostics during the reboot sequence.
Examples
The following prompt is received if you issue a reboot command (without the force keyword) when the storage router has unsaved configuration changes.
[SN5428-2A]# reboot*** Warning: This will reboot the system.Do you want to continue? [yes/no (no)] yesChanges have been made to the current configuration of the system whichhave not been saved.yes - all of the configuration data will be saved,no - modifications to the configuration data will not be saved.Save ALL configuration data? [yes/no (yes)] yesHalting system.........The following example reboots the storage router (after prompting you to save any unsaved configuration changes) but bypasses diagnostics during the reboot process:
[SN5428-2A]# reboot fast
Related Commands
Prepare the storage router to be powered down.
Specify the version of software to run when the storage router is restarted.
restore aaa
To cause the AAA authentication configuration to be copied from the specified configuration file into persistent memory, use the restore aaa command. The configuration file must exist in the savedconfig directory. To display the contents of the savedconfig directory, issue the show savedconfig command.
Note
restore aaa from filename
Syntax Description
from filename
The name of the configuration file containing the information to be restored. This file must exist in the savedconfig directory.
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
The restore command overwrites all existing AAA configuration information, including any user name and passwords in the local username database, RADIUS and TACACS+ configuration information, and the AAA authentication lists used for iSCSI, Enable, and Login authentication.
Note
Examples
The following example restores the AAA authentication configuration from the saved configuration file named aaa_backup:
[SN5428-2A]# restore aaa from aaa_backupRelated Commands
restore accesslist
To cause the named access list or all access lists to be copied from the specified configuration file into persistent memory, use the restore accesslist command. The configuration file must exist in the savedconfig directory. To display the contents of the savedconfig directory, issue the show savedconfig command.
Note
restore accesslist {name | all} from filename
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
If the access list currently exists in some form, the restore command does not delete existing information. The restore command adds missing entries, or overwrites existing entries of the same name, but never purges or deletes existing access list entries. If necessary, you can delete an access list and all its entries and then restore it from a saved configuration file.
There is a maximum of 100 access lists per storage router or per storage router cluster. There is a maximum of 200 access list identification entries across all access lists in the storage router or storage router cluster.
Note
Examples
The following example restores the access list named fooList from the saved configuration file named accessList_backup:
[SN5428-2A]# restore accesslist fooList from accessList_backupRelated Commands
restore all
To cause all the previously saved configuration information to be copied from the specified configuration file into persistent memory, use the restore all command. The configuration file must exist in the savedconfig directory. Use the show savedconfig command to display the contents of the savedconfig directory.
Note
restore all from filename
Syntax Description
from filename
The name of the configuration file containing the information to be restored. This file must exist in the savedconfig directory.
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
The restore all command restores all information from the named configuration file. Depending on the information that is restored, the running configuration of the storage router may be changed.
A restore command may overwrite or delete existing items. However, the restore command will not purge or delete existing items from access lists, but will add missing items or overwrite existing items of the same name. If necessary, you may delete access lists, or any other item to be restored, before restoring from a saved configuration file.
The restore all command will not restore the route table and RIP settings, the Fibre Channel (FC) zoning database, or the logging table. Use the restore system ip-route command to restore a saved route table and RIP settings, and the restore fcswitch zones command to restore the FC zoning database. Use the restore system logging command to restore the logging table.
SCSI routing instances and FCIP instances must be stopped before they can be restored. Use the no scsirouter enable command to stop active SCSI routing instances. Use the no fcip enable command to stop an active FCIP instance. After the restore is complete, use the scsirouter enable command to start the restored SCSI routing instances. Restored FCIP instances are automatically restarted.
Note
Examples
The following example restores all configuration data contained in the configuration file named foo_backup into persistent memory:
[SN5428-2A]# restore all from foo_backupRelated Commands
restore fcip
To cause the previously saved configuration information related to the named FCIP instance to be copied from the specified configuration file into the bootable configuration, use the restore fcip command. The configuration file must exist in the savedconfig directory. Use the show savedconfig command to display the contents of the savedconfig directory.
Note
restore fcip {name | all} from filename
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
The FCIP instance should be inactive before it is restored. Use the no fcip enable command to stop an active FCIP instance so it can be restored. After the specified FCIP instance is restored, it is automatically enabled and the running configuration of the storage router is updated.
A restore command never deletes existing FCIP instances. The restore command will add missing instances and will overwrite configuration information for existing instances of the same name. If necessary, you can delete the FCIP instance and then restore it from a saved configuration file.
Examples
The following example restores the FCIP instance fcip1 from the configuration file named fcip_backup001:
[SN5428-2A]# restore fcip fcip1 from fcip_backup001Related Commands
restore fcswitch
To cause the previously saved configuration information associated with the storage router Fibre Channel (FC) interfaces to be copied from the specified configuration file into the bootable configuration, use the restore fcswitch command. The configuration file must exist in the savedconfig directory. Use the show savedconfig command to display the contents of the savedconfig directory.
restore fcswitch {all | config | interface | zones} from filename
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
The restore fcswitch command overwrites the specified FC configuration information.
Use the config keyword to restore global FC configuration information, including:
•
•
•
•
•
•
•
Use the interface keyword to restore configuration information for each FC port, including:
•
•
•
•
•
•
Use the zones keyword to restore the internal zoning database, including:
•
•
•
•
Caution
Examples
The following example restores the configuration information for all FC interface from the configuration file named fc_config_08152002:
[SN5428-2A]# restore fcswitch interface from fc_config_08152002The following example restore all global and interface-specific FC configuration information from the configuration file named SN5428-2A_L2:
[SN5428-2A]# restore fcswitch all from SN5428-2A_L2Related Commands
restore scsirouter
To cause the previously saved configuration information related to the named SCSI routing instance to be copied from the specified configuration file into the bootable configuration, use the restore scsirouter command. The configuration file must exist in the savedconfig directory. Use the show savedconfig command to display the contents of the savedconfig directory.
Note
restore scsirouter {name | all} from filename
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
A SCSI routing instance must be inactive before it can be restored. Use the no scsirouter enable command to stop an active SCSI routing instance so it can be restored. After the specified SCSI routing instance is restored, issue the scsirouter enable command to start the instance and update the running configuration of the storage router.
A restore command never deletes existing SCSI routing instances. The restore command will add missing instances and will overwrite configuration information for existing instances of the same name. If necessary, you can delete a SCSI routing instance and then restore it from a saved configuration file.
Examples
The following example restores the SCSI routing instance foo from the configuration file named scsi_backup001:
[SN5428-2A]# restore scsirouter foo from scsi_backup001Related Commands
restore system
To cause previously saved system configuration information to be copied from the specified configuration file into persistent memory, use the restore system command. The configuration file must exist in the savedconfig directory. Use the show savedconfig command to display the contents of the savedconfig directory.
restore system {name | all} from filename
Syntax Description
name
The named system information to be restored. See Table 13-1 in the Usage Guidelines section for a list of valid names that can be used for the name argument.
all
Restore all restorable system information (except the route table and RIP settings, and the logging table) from the saved configuration file. Restorable system information includes CDP configuration, administrator contact data, DNS and NTP information, restrict configuration, remote logging data, SNMP configuration, Telnet and Secure Shell (SSH) settings, and the default download location for updated storage router software.
Note
from filename
The name of the configuration file containing the information to be restored. This file must exist in the savedconfig directory.
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
Table 13-1 describes the named system information that can be restored.
Some system information that is saved when the save system command is issued is not available for restoration from a saved configuration file. Use the show savedconfig command to display the contents of the specified configuration file. The following configuration information is available for display but cannot be restored:
•
•
•
•
Examples
The following example restores all restorable system configuration information (except the route table and the logging table) from the saved configuration file system_backup:
[SN5428-2A]# restore system all from system_backupThe following example restores the route table and RIP settings from the saved configuration file system_backup:
[SN5428-2A]# restore system ip-route from system_backup[SN5428-2A]# restore system rip from system_backupThe following example restores the logging table from the saved configuration file system_backup:
[SN5428-2A]# restore system logging from system_backupThe following example restores the SNMP configuration information from the saved configuration file sys_SN5428-2A:
[SN5428-2A]# restore system snmp from sys_SN5428-2ARelated Commands
restore vlan
To cause the specified VLAN to be copied from the named configuration file into persistent memory, use the restore vlan command. The configuration file must exist in the savedconfig directory. To display the contents of the savedconfig directory, issue the show savedconfig command.
Note
restore vlan {vid | all} from filename
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
If the VLAN currently exists, the restore vlan command overwrites existing configuration information with the information from the named configuration file. The restore vlan command also restores the VTP configuration information.
Note
Examples
The following example restores VLAN 100 from the vlanBackup file:
[SN5428-2A]# restore vlan 100 from vlanBackupRelated Commands
restrict
To close access to the specified interface via the named service, use the restrict command. To allow access via the named service, use the no form of this command.
restrict all [service]
restrict interface {service | all}
no restrict all [service]
no restrict interface {service | all}
Syntax Description
interface
Restrict access to the specified interface. See Table 13-2 in the Usage Guidelines section for a list of interface names.
service
Restrict access via the specified service or protocol. See Table 13-3 in the Usage Guidelines section for a list of service names.
all
Restrict all interfaces or all services.
Defaults
The following are factory default settings:
•
•
•
•
•
•
•
Command Modes
Administrator.
Command History
Usage Guidelines
Use the restrict command to restrict unauthorized access to storage router interfaces. Use the show restrict command to display the current interface and service restrictions.
You can restrict access on the interfaces listed in Table 13-2.
You can restrict access to the storage router interfaces by the services or protocols, shown in Table 13-3.
To access the GUI using an SSL connection, enable SSL on the appropriate interface and change the URL to use "https" instead of "http."
To completely disable the GUI, restrict HTTP access to all interfaces.
Examples
The following example restricts HTTP access to the management interface, preventing access to the web-based GUI from this interface:
[SN5428-2A]# restrict mgmt httpThe following example restricts Telnet access to the HA interface:
[SN5428-2A]# restrict ha telnetThe following example restricts access to all interfaces via FTP.
[SN5428-2A]# restrict all ftpThe following example enables SSL on the management interface.
[SN5428-2A]# no restrict mgmt sslThe following example enables SSH on the Gigabit Ethernet interface, ge1:
[SN5428-2A]# no restrict ge1 sshRelated Commands
restrict console
To enable password checking on the storage router console interface, use the restrict console command. The Administrator mode and Monitor mode passwords will be required when accessing the storage router via a console connected to the EIA/TIA-232 port. To disable password checking on the console interface, use the no form of this command.
restrict console
no restrict console
Syntax Description
This command has no arguments or keywords.
Defaults
Passwords are disabled on the console interface.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command if you need to restrict access to the console interface.
Examples
The following example enables password checking on the console interface:
[SN5428-2A]# restrict consoleRelated Commands
Secure access to storage router interfaces by communications protocols and services.
Display configurable security settings for the storage router interfaces.
