- New and Changed Information
- Preface
- A Commands
- Advanced Services Modules Commands
- B Commands
- C Commands
- Caching Services Module Commands
- CLI Overview
- D Commands
- Debug Commands
- E Commands
- F Commands
- G Commands
- H Commands
- I Commands
- J Commands
- K Commands
- L Commands
- M Commands
- N Commands
- O Commands
- P Commands
- Q Commands
- R Commands
- S Commands
- Show Commands
- T Commands
- U Commands
- V Commands
- W Commands
- Z Commands
Cisco MDS 9000 Family Command Reference
Bias-Free Language
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.
- Updated:
- July 13, 2014
Chapter: R Commands
- radius abort
- radius commit
- radius distribute
- radius-server deadtime
- radius-server directed-request
- radius-server host
- radius-server key
- radius-server retransmit
- radius-server test
- radius-server timeout
- rate-mode bandwidth-fairness
- rate-mode oversubscription-limit
- reload
- read command-id
- read-only
- revocation-check
- rlir preferred-cond fcid
- rmdir
- rmon alarm
- rmon event
- rmon hcalarm
- role abort
- role commit
- role distribute
- role name
- rsakeypair
- rscn
- rscn abort vsan
- rscn coalesce swrscn vsan
- rscn commit vsan
- rscn distribute
- rscn event-tov
- rscn permit type nport event switch-config
- rule
- run-script
- rspan-tunnel
R Commands
The commands in this chapter apply to the Cisco MDS 9000 Family of multilayer directors and fabric switches. All commands are shown here in alphabetical order regardless of command mode. See “About the CLI Command Modes” section to determine the appropriate mode for each command.
radius abort
To discard a RADIUS Cisco Fabric Services (CFS) distribution session in progress, use the radius abort command in configuration mode.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example shows how to discard a RADIUS CFS distribution session in progress:
Related Commands
|
|
|
|---|---|
radius commit
To apply the pending configuration pertaining to the RADIUS Cisco Fabric Services (CFS) distribution session in progress in the fabric, use the radius commit command in configuration mode.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
After the "radius commit" is done the running configuration has been modified on all switches participating in radius distribution. You can then use the "copy running-config startup-config fabric" command to save the running-config to the startup-config on all the switches in the fabric.
Examples
The following example shows how to apply a RADIUS configuration to the switches in the fabric:
Related Commands
|
|
|
|---|---|
radius distribute
To enable Cisco Fabric Services (CFS) distribution for RADIUS, use the radius distribute command. To disable this feature, use the no form of the command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example shows how to enable RADIUS fabric distribution:
Related Commands
|
|
|
|---|---|
Commits temporary RADIUS configuration changes to the active configuration. |
|
radius-server deadtime
To set a periodic time interval where a nonreachable (nonresponsive) RADIUS server is monitored for responsiveness, use the radius-server deadtime command. To disable the monitoring of the nonresponsive RADIUS server, use the no form of the command.
no radius-server deadtime time
Syntax Description
Specifies the time interval in minutes. The range is 1 to 1440. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Setting the time interval to zero disables the timer. If the dead time interval for an individual RADIUS server is greater than zero (0), that value takes precedence over the value set for the server group.
When the dead time interval is 0 minutes, RADIUS server monitoring is not performed unless the RADIUS server is part of a server group and the dead time interval for the group is greater than 0 minutes.
Examples
The following example shows how to set a duration of 10 minutes:
Related Commands
|
|
|
|---|---|
Sets a time interval for monitoring a nonresponsive RADIUS server. |
|
radius-server directed-request
To specify a RADIUS server to send authentication requests to when logging in, use the radius-server directed-request command. To revert to sending the authentication request to the configured group, use the no form of the command.
radius-server directed-request
no radius-server directed-request
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
The user can specify the username@servername during login. The user name is sent to the server name for authentication.
Examples
The following example shows how to specify a RADIUS server to send authentication requests to when logging in:
Related Commands
|
|
|
|---|---|
radius-server host
To configure RADIUS server parameters, use the radius-server host command. Use the no form of this command to revert to the factory defaults.
radius-server host { server-name | ipv4-address | ipv6-address } [ key [ 0 | 7 ] shared-secret ] [ 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 { server-name | ipv4-address | ipv6-address } [ key [ 0 | 7 ] shared-secret ] [ accounting ] [ acct-port port-number ] [ auth-port port-number ] [ authentication ] [ retransmit count ] [ test { idle-time time | password password | username name }] [ timeout seconds [ retransmit count ]]
Syntax Description
Defaults
Idle-time is not set. Server monitoring is turned off.
Timeout is 1 second.
Username is test.
Password is test.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When the idle time interval is 0 minutes, periodic RADIUS server monitoring is not performed.
Examples
The following example configures RADIUS server authentication parameters:
Related Commands
|
|
|
|---|---|
radius-server key
To configure a global RADIUS shared secret, use the radius-server key command. Use the no form of this command to removed a configured shared secret.
radius-server key [0 | 7] shared-secret
no radius-server key [0 | 7] shared-secret
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You need to configure the RADIUS preshared key to authenticate the switch to the RADIUS server. The length of the key is restricted to 65 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 by explicitly using the key option in the radius-server host command. Global key configuration is exempted from CFS distribution.
Examples
The following examples provide various scenarios to configure RADIUS authentication:
Related Commands
|
|
|
|---|---|
radius-server retransmit
To globally specify the number of times the switch should try a request with a RADIUS server, use the radius-server retransmit command. To revert to default value, use the no form of the command.
radius-server retransmit count
no radius-server retransmit count
Syntax Description
Configures the number of times the switch tries to connect to a RADIUS server(s) before reverting to local authentication. The range is 1 to 5 times. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example configures the number of retransmissions to 3:
Related Commands
|
|
|
|---|---|
radius-server test
To configure the test parameter for an individual server, use the radius-server test command. To disable this feature, use the no form of the command.
radius-server test {{username {username} | {[password {password} [idle-time {time}]] | [idle-time {time}]} } | { password {password} [ idle-time {time} ] } | { idle-time {time} }}
no radius-server test {{username {username} | {[password {password} [idle-time {time}]] | [idle-time {time}]} } | {password {password} [idle-time {time} ] } | { idle-time {time} }}
Syntax Description
Specifies the user password. The maximun size is 32 characters. |
|
(Optional) Specifies the time interval for monitoring the server. |
|
Specifies the time period in minutes. The range is from 1 to 4440. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Defaults will be used for anything not provided by CLI. Also doing a "no" of any parameters will revert it back to default.
Examples
The following example shows how to display the username in test packets:
The following example shows how to display the time interval for monitoring the server:
The following example shows how to display the user password in test packets:
Related Commands
|
|
|
|---|---|
radius-server timeout
To specify the time between retransmissions to the RADIUS servers, use the radius-server timeout command. You can revert the retransmission time to its default by issuing the no form of the command.
no radius-server timeout seconds
Syntax Description
Specifies the time (in seconds) between retransmissions to the RADIUS server. The range is 1 to 60 seconds. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example configures the timeout value to 30 seconds:
Related Commands
|
|
|
|---|---|
rate-mode bandwidth-fairness
To enable or disable bandwidth fairness among ports in a port group, use the rate-mode bandwidth-fairness command in configuration mode. To disable bandwidth fairness, use the no form of the command.
rate-mode bandwidth-fairness module module-id
no rate-mode bandwidth-fairness module module-id
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Enter the command separately for each module you want to enable or disable bandwidth fairness.
Note
This feature is only supported on 48-port and 24-port 4-Gbps Fibre Channel switching modules.
Examples
The following example shows how to enable bandwidth fairness for a module:
The following example shows how to disable bandwidth fairness for a module:
Related Commands
|
|
|
|---|---|
rate-mode oversubscription-limit
To enable or disable restrictions on oversubscription ratios, use the rate-mode oversubscription-limit command.
rate-mode oversubscription-limit module module number
no rate-mode oversubscription-limit module module number
Syntax Description
Identifies the specific module on which oversubscription ratio restrictions will be enabled or disabled. |
Defaults
Oversubscription ratios are restricted for all 24-port and 48-port switching modules.
Command Modes
Command History
|
|
|
Usage Guidelines
When restrictions on oversubscription ratios are disabled, the bandwidth allocation among the shared ports is proportionate to the configured speed (if the configured speed is auto, then bandwidth is allocated assuming a speed of 4 Gbps).
You must explicitly shut down and take out of service shared ports before disabling oversubscription ratio restrictions on them.
The configuration is not saved to the startup configuration unless you explicitly enter the copy running-config startup-config command.
You must enable restrictions on oversubscription ratios before you can downgrade modules to a previous release.
Examples
The following example disables restrictions on oversubscription ratios for a module (there are only dedicated ports, so a shutdown is not necessary):
The following example shows how to view the status of a module’s oversubscription ratios:
Related Commands
|
|
|
|---|---|
Saves the new oversubscription ratio configuration to the startup configuration. |
|
reload
To reload the entire switch, an active supervisor module, a standby supervisor module, or a specific module, or to force a netboot on a given module, use the reload command in EXEC mode.
reload [ module module-number force-dnld ]
Syntax Description
(Optional) Reloads a specific module or active/standby supervisor module. |
|
(Optional) Reloads, initiates netboot, and forces the download of the latest module firmware version to a specific module. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Use the reload command to reboot the system, or to reboot a specific module, or to force a netboot on a specific module. The reload command used by itself, powers down all the modules and reboots the supervisor modules.
Use the reload module module-number command, if the given slot has a module or standby supervisor module, to power-cycle that module. If the given slot has an active supervisor module, then it causes the currently active supervisor module to reboot and the standby supervisor module becomes active.
The reload module module-number force-dnld command is similar to the previous command. This command forces netboot to be performed. If the slot contains a module, then the module netboots with the latest firmware and updates its corresponding flash with this image.
Examples
The following example uses reload to reboot the system:
The following example uses reload to initiate netboot on a specific module:
The following example uses reload to reboot a specific module:
The following example uses reload to reboot an active supervisor module:
Related Commands
|
|
|
|---|---|
read command-id
To configure a SCSI read command for a SAN tuner extension N port, use the read command-id command.
read command-id cmd-id target pwwn transfer-size bytes [ outstanding-ios value [ continuous | num-transactions number ]]
Syntax Description
Defaults
Command Modes
SAN extension N port configuration submode.
Command History
|
|
|
Usage Guidelines
To stop a SCSI read command in progress, use the stop command.
Examples
The following example configures a continuous SCSI read command:
Related Commands
|
|
|
|---|---|
Cancels a SCSI command in progress on a SAN extension tuner N port. |
read-only
To configure the read-only attribute in a zone attribute group, use the read-only command in zone attribute configuration submode. To revert to the default, use the no form of the command.
Syntax Description
Defaults
Command Modes
Zone attribute configuration submode.
Command History
|
|
|
Usage Guidelines
This command only configures the read-only attribute for enhanced zoning. To enable broadcast zoning for basic mode, use the attribute read-only subcommand after entering zone configuration mode using the zone name command.
Examples
The following example shows how to set the read-only attribute for a zone attribute group:
Related Commands
|
|
|
|---|---|
revocation-check
To configure trust point revocation check methods, use the revocation-check command in trust point configuration submode. To discard the revocation check configuration, use the no form of the command.
revocation-check {crl [none | ocsp [none]] | none | ocsp [crl [none] | none]}
no revocation-check {crl [none | ocsp [none]] | none | ocsp [crl [none] | none]}
Syntax Description
Defaults
By default, the revocation checking method for a trust point is CRL.
Command Modes
Trust point configuration submode.
Command History
|
|
|
|---|---|
Usage Guidelines
You must authenticate the CA and configure the OCSP URL before configuring OCSP as a revocation checking method.
The revocation checking configuration allows one or more of the methods to be specified as an ordered list for revocation checking. During peer certificate verification, each method is tried in the specified order until one method succeeds by providing the revocation status. When none is specified as the method, it means that there is no need to check the revocation status, which treats the peer certificate as not revoked. If none is the first method specified in the method list, subsequent methods are not allowed to be specified because checking is not required.
Examples
The following example shows how to check for revoked certificates using OCSP on a URL that must have been previously configured:
The following example shows how to check for revoked certificates in the locally stored CRL:
The following example shows how to check revocation status first using locally cached CRL and then, if needed, using OCSP. If CRL is not yet cached locally, only OCSP checking is attempted:
The following example shows how to do no checking for revoked certificates:
Related Commands
|
|
|
|---|---|
Configures a CRL or overwrites the existing one for the trust point CA. |
|
rlir preferred-cond fcid
To specify a preferred host to receive Registered Link Incident Report (RLIR) frames, use the rlir preferred-cond fcid command in configuration mode. To remove a preferred host, use the no form of the command.
rlir preferred-cond fcid fc-id vsan vsan-id
no rlir preferred-cond fcid fc-id vsan vsan-id
Syntax Description
Defaults
By default, the MDS switch sends RLIR frames to one of the hosts in the VSAN with the register function set to “conditionally receive” if no hosts have the register function set to “always receive.”
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The MDS switch sends RLIR frames to the preferred host only if it meets the following conditions:
- No host in the VSAN is registered for RLIR with the registration function set to “always receive.” If one or more hosts in the VSAN are registered as “always receive,” then RLIR sends only to these hosts and not to the configured preferred host.
- The preferred host is registered with the registration function set to “conditionally receive.”
Note If all registered hosts have the registration function set to “conditionally receive,” then the preferred host receives the RLIR frames.
Examples
The following example specifies FC ID 0x654321 as the RLIR preferred host for VSAN 2:
switch(config)# rlir preferred-cond fcid 0x654321 vsan 2
The following example removes FC ID 0x654321 as the RLIR preferred host for VSAN 2:
Related Commands
|
|
|
|---|---|
Displays information about RLIR, Link Incident Record Registration (LIRR), and Distribute Registered Link Incident Record (DRLIR) frames. |
|
rmdir
To delete an existing directory from the flash file system, use the rmdir command in EXEC mode.
rmdir [ bootflash: | slot0: | volatile: ] directory
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
This command is only valid on flash file systems.
The rmdir command deletes an existing directory at the current directory level or at a specified directory level. The directory must be empty to be deleted.
Examples
The following example deletes the directory called test in the slot0 directory:
The following example deletes the directory called test at the current directory level. If the current directory is slot0:mydir, this command deletes the slot0:mydir/test directory.
Related Commands
|
|
|
|---|---|
rmon alarm
To configure a 32 bit remote monitoring (RMON) alarm, use the rmon alarm command in configuration mode. To delete an RMON alarm, use the no form of the command.
rmon alarm alarm-number mib-object sample-interval { absolute | delta } rising-threshold value [ rising-event ] falling-threshold value [ falling-event ] [ owner alarm-owner ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Use the rmon event command to configure the events for alarms.
The maximum number of RMON alarms currently is only configurable through the device manager and threshold manager GUI. A CLI command is not available to change this maximum value.
Note We recommend setting alarm sample intervals to 30 seconds or higher to prevent excessive load on the system.
Examples
The following example configures a 32-bit alarm number 20 for ifInErrors (OID 1.3.6.1.2.1.2.2.1.14) on interface fc 1/1. The sample interval is 30 seconds and delta samples are tested. The rising threshold is 15 errors per sample window; reaching this level triggers event 1. The falling threshold is 0 errors in the sample window which triggers event 0 (no action). The owner is 'ifInErrors.fc1/1@test'.
Related Commands
|
|
|
|---|---|
rmon event
To configure a remote monitoring (RMON) event, use the rmon event command in configuration mode. To delete an RMON event, use the no form of the command.
rmon event event-number [description text [owner owner-name] | log [trap community-string] [description text] [owner owner-name] | trap community-string [description text] [owner owner-name] | owner owner-name]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You can trigger the events created by this command with alarms configured using the rmon alarm or rmon hcalarm commands
The log option logs the event to a local log file on the MDS switch. The trap option uses the onboard SNMP agent to send an SNMP trap to a remote NMS.
Note Events can be used by both rmon alarm (32-bit) and hcalarm (64-bit) commands.
Examples
The following example configures RMON event1 to log the onboard RMON log and send an SNMP trap to public community trap destinations. The description is public and is owned by switchname.
The following example configures RMON event3 to log the onboard RMON log and send an SNMP trap to public community trap destinations. The description is error and is owned by switchname:
The following example configures RMON event4 to log the onboard RMON log and send an SNMP trap to public community trap destinations. The description is warning and is owned by switchname:
The following example configures RMON event5 to log the onboard RMON log and send an SNMP trap to public community trap destinations. The description is information and is owned by switchname:
The following example configures RMON event 2 to log the onboard RMON log and send an SNMP trap to public community trap destinations. The description is CriticalErrors and is owned by test:
Related Commands
|
|
|
|---|---|
rmon hcalarm
To configure a 64-bit remote monitoring (RMON) high-capacity alarm (hcalarm), use the rmon hcalarm command in configuration mode. To delete an RMON hcalarm, use the no form of the command.
rmon hcalarm alarm-number mib-object sample-interval {absolute | delta} {rising-threshold-high value rising-threshold-low value [rising-event] [falling-threshold-high value falling-threshold-low value [falling-event]] | falling-threshold-high value falling-threshold-low value [falling-event]} [owner alarm-owner]
no rmon hcalarm alarm-number mib-object sample-interval {absolute | delta} {rising-threshold-high value rising-threshold-low value [rising-event] [falling-threshold-high value falling-threshold-low value [falling-event]] | falling-threshold-high value falling-threshold-low value [falling-event]} [owner alarm-owner]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Event number 0 is a predefined null (or no operation) event. When no event is specified by the user in an alarm this event is automatically used by the system. The event causes no action to be taken when triggered, however, the alarm is still reset. The event cannot be redefined by the user. It is a predefined event and you can only create events in the range from 1 to 65535.
To configure a high-capacity RMON alarm, use the CISCO-HC-ALARM-MIB.
The maximum number of RMON alarms is currently configurable through the device manager and threshold manager GUI. A CLI command is not available to change this maximum value.
Note We recommand setting alarm sample intervals to 30 seconds or higher to prevent excessive load on the system.
Examples
The following example configures 64-bit alarm number 2 for ifHCInOctets (OID 1.3.6.1.2.1.31.1.1.1.6) on interface fc 12/1. The sample interval is 30 seconds and delta samples are tested. The rising threshold is 240,000,000,000 bytes per sample window (an average of 8,000,000,000 bytes per second); reaching this level triggers event 4. The falling threshold is 180,000,000,000 bytes in the sample window (an average of 6,000,000,000 bytes per second) which triggers event 0 (no action) and resets the alarm. The owner is 'ifHCInOctets.fc12/1@test'.
Related Commands
|
|
|
|---|---|
role abort
To discard an authorization role Cisco Fabric Services (CFS) distribution session in progress, use the role abort command in configuration mode.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example shows how to discard an authorization role CFS distribution session in progress:
Related Commands
|
|
|
|---|---|
role commit
To apply the pending configuration pertaining to the authorization role Cisco Fabric Services (CFS) distribution session in progress in the fabric, use the role commit command in configuration mode.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Note Once the "role commit" is done the running configuration has been modified on all switches participating in the role distribution. You can then use the "copy running-config startup-config fabric" command to save the running-config to the startup-config on all the switches in the fabric.
Examples
The following example shows how to apply an authorization role configuration to the switches in the fabric:
Related Commands
|
|
|
|---|---|
role distribute
To enable Cisco Fabric Services (CFS) distribution for authorization roles, use the role distribute command. To disable this feature, use the no form of the command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example shows how to enable fabric distribution for authorization roles:
Related Commands
|
|
|
|---|---|
Commits temporary to the authorization role configuration changes to the active configuration. |
|
role name
To configure and assign users to a new role or to modify the profile for an existing role, use the role name command in configuration mode. Use the no form of this command to delete a configured role.
role name [ max-length 64 ] [ name ] [ description user description ] [rule number permit clear feature name | permit config feature name | permit debug feature name | permit show feature name ] [rule number deny clear feature name | deny config feature name | deny debug feature name | deny exec feature name | deny show feature name ]
no role name name [ description user description ] [rule number permit clear feature name | permit config feature name | permit debug feature name | permit show feature name ] [rule number deny clear feature name | deny config feature name | deny debug feature name | deny exec feature name | deny show feature name ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Users are assigned roles. Roles are assigned rules. Roles are a group of rules defining a user’s access to
certain commands. The rules within roles can be assigned to permit or deny access to the following commands:
- clear— Clear commands
- config— Configuration commands
- debug— Debug commands
- exec— EXEC commands
- show— Show commands
These commands can have permit or deny options within that command line.
Examples
The following example shows how to assign users to a new role:
Related Commands
|
|
|
|---|---|
Displays all roles configured on the switch including the rules based on each role. |
rsakeypair
To configure and associate the RSA key pair details to a trust point, use the rsakeypair command in trust point configuration submode. To disassociate the RSA key pair from the trust point, use the no form of the command.
rsakeypair key-pair-label [key-pair-size ]
no rsakeypair key-pair-label [key-pair-size ]
Syntax Description
Specifies a name for the RSA key pair. The maximum size is 64 characters. |
|
(Optional) Specifies a size for the RSA key pair. The size can range from 512 to 2048. |
Defaults
The default key pair size is 512 if the key pair is not already generated.
Command Modes
Trust point configuration submode.
Command History
|
|
|
|---|---|
Usage Guidelines
Only one RSA key pair can be associated with a trust point CA, even though the same key pair can be associated with many trust point CAs. This association must occur before enrolling with the CA to obtain an identity certificate. If the key pair had been generated previously (using the crypto key generate command), then the key pair size, if specified, should be the same as that was used during generation. If the specified key pair is not yet generated, it will be generated during enrollment using the crypto ca enroll command.
The no form of the rsakeypair command disassociates (but never destroys) the key pair from the trust point. Before issuing the no rsakeypair command, first remove the identity certificate, if present, from the trust point CA. Doing so ensures the consistency of the association between the identity certificate and the key pair for a trust point
Examples
The following example shows how to associate an RSA key pair to a trust point:
The following example shows how to disassociate an RSA key pair from a trust point:
Related Commands
|
|
|
|---|---|
Requests certificates for the switch’s RSA key pair created for the trust point CA. |
|
rscn
To configure a registered state change notification (RSCN), a Fibre Channel service that informs Nx ports about changes in the fabric, use the rscn command in configuration mode.
rscn {multi-pid | suppress domain-swrscn } vsan vsan-id
Syntax Description
Configures VSAN information or membership. The ID of the VSAN is from 1 to 4093. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example configures RSCNs in multi-PID format:
Related Commands
|
|
|
|---|---|
rscn abort vsan
To cancel a Registered State Change Notification (RSCN) configuration on a VSAN, use the rscn abort vsan command in configuration mode. To reverse the cancellation, use the no form of the command.
Syntax Description
Specifies a VSAN where the RSCN configuration should be cancelled. The ID of the VSAN is from 1 to 4093. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example cancels an RSCN configuration on VSAN 1:
Related Commands
|
|
|
|---|---|
rscn coalesce swrscn vsan
To enable coalescing of Switch Registered State Change Notification (SWRSCN) before sending, use the rscn coalesce swrscn vsan command in configuration mode. To disable coalesce SWRSCN, use the no form of the command.
rscn coalesce swrscn vsan vsan-id [delay milliseconds]
no rscn coalesce swrscn vsan vsan-id
Syntax Description
Specifies the delay in milliseconds to achieve swrscn coalesce. |
|
Specifies the Swrscn coalesce delay in milliseconds (default 500ms). The range is from 100 to 2000. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This feature can be enabled in a fabric where all the switches are MDS and are running 6.2(7) and above.
Examples
The following example shows how to enable coalesce SWRSCN:
The following example shows how to configure 100 milliseconds delay for coalesce SWRSCN:
rscn commit vsan
To apply a pending Registered State Change Notification (RSCN) configuration, use the rscn commit vsan command in configuration mode. To discard a pending RSCN configuration, use the no form of the command.
Syntax Description
Specifies a VSAN where the RSCN configuration should be committed. The ID of the VSAN is from 1 to 4093. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you commit the changes made to the active database, the configuration is committed to all the switches in the fabric. On a successful commit, the configuration change is applied throughout the fabric and the lock is released.
Note Once the "rscn commit" is done the running configuration has been modified on all switches participating in rscn distribution. You can then use the "copy running-config startup-config fabric" command to save the running-config to the startup-config on all the switches in the fabric.
Examples
The following example commits an RSCN configuration on VSAN 1:
Related Commands
|
|
|
|---|---|
rscn distribute
To enable distribution of a Registered State Change Notification (RSCN) configuration, use the rscn distribute command in configuration mode. To disable the distribution, use the no form of the command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The RSCN timer configuration must be the same on all switches in the VSAN; otherwise, the link will not come up. Cisco Fabric Service (CFS) automatically distributes the RSCN timer configuration to all switches in a fabric. Only the RSCN timer configuration distributed.
Note For the CFS distribution to operate correctly for the RSCN timer configuration, all switches in the fabric must be running Cisco SAN-OS Release 3.0(1) or later.
Examples
The following example enables the distribution of an RSCN configuration:
Related Commands
|
|
|
|---|---|
rscn event-tov
To configure an event timeout value for a Registered State Change Notification (RSCN) on a specified VSAN, use the rscn event-tov command in configuration mode. To cancel the event timeout value and restore the default value, use the no form of the command.
rscn event-tov timeout vsan vsan-id
no rscn event-tov timeout vsan vsan-id
Syntax Description
Specifies an event timeout value in milliseconds. The range is 0 to 2000. |
|
Specifies a VSAN where the RSCN event timer should be used. The ID of the VSAN is from 1 to 4093. |
Defaults
The default timeout values are 2000 milliseconds for Fibre Channel VSANs and 1000 milliseconds for FICON VSANs.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Before changing the timeout value, you must enable RSCN configuration distribution using the rscn distribute command.
The RSCN timer is registered with Cisco Fabric Services (CFS) during initialization and switchover. For high availability, if the RSCN timer distribution crashes and restarts or a switchover occurs, it resumes normal functionality from the state prior to the crash or switchover.
Note You can determine configuration compatibility when downgrading to an earlier Cisco MDS SAN-OS release using the show incompatibility system command. You must disable RSCN timer distribution support before downgrading to an earlier release.
Examples
The following example configures an RSCN event timeout value on VSAN 1:
Related Commands
|
|
|
|---|---|
rscn permit type nport event switch-config
To enable Registered State Change Notification (RSCN) on management port IP address changes or switch name changes, use the rscn permit type nport event switch-config command. To disable RSCN, use the no form of the command.
rscn permit type nport event switch-config vsan vsan-id
no rscn permit type nport event switch-config vsan vsan-id
Syntax Description
Defaults
RSCN will not be sent on management port IP address changes or switch name changes.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to enable RSCN on management port changes:
Related Commands
|
|
|
|---|---|
rule
To specify the tape volume group regular expression, use the rule command. To disable this feature, use the no form of the command.
rule {range range | regexp regular expression}
no rule {range range | regexp regular expression}
Syntax Description
Specifies the crypto tape volume barcode range. The maximum length is 32 characters. |
|
Specifies the volume group regular expression. The maximum length is 32 characters. |
Defaults
Command Modes
Cisco SME crypto tape volume group configuration submode.
Command History
|
|
|
Usage Guidelines
Examples
The following example specifies the volume group regular expression:
Related Commands
|
|
|
|---|---|
run-script
To execute the commands specified in a file, use the run-script command.
run-script [ bootflash: | slot0: | volatile: ] filename
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Updated the Usage Guidelines and Examples with information about user-defined variables. |
Usage Guidelines
To use this command, be sure to create the file and specify commands in the required order.
The run-script command accepts user-defined variables as parameters.
Examples
The following example executes the CLI commands specified in the testfile that resides in the slot0 directory:
In response to the run-script command, this is the file output:
The following example shows how you can pass user-defined variables to the run-script command:
rspan-tunnel
To associate and bind the SPAN tunnel (ST) port with the RSPAN tunnel, use the rspan-tunnel command.
rspan-tunnel interface fc-tunnel tunnel-id
rspan-tunnel interface fc-tunnel tunnel-id
Syntax Description
Defaults
Command Modes
Interface configuration submode.
Command History
|
|
|
Usage Guidelines
The interface is not operationally up until the Fibre Channel tunnel mapping is configured in the source and destination switches.
Examples
The following example configures an interface to associate and bind the ST port with the RSPAN tunnel and enables traffic flow trough this interface:
Feedback