-
Cisco MDS 9000 Family Command Reference, Release 3.x
-
New and Changed Information
-
Preface
-
CLI Overview
-
A Commands
-
Advanced Services Modules Commands
-
B Commands
-
C Commands
-
Caching Services Module Commands
-
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
-
Feedback
Table Of Contents
tacacs-server directed-request
target (iSLB initiator configuration)
T 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 on page 1-3 to determine the appropriate mode for each command. For more information, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
tacacs+ abort
To discard a TACACS+ Cisco Fabric Services (CFS) distribution session in progress, use the tacacs+ abort command in configuration mode.
tacacs+ abort
Syntax Description
This command has no other arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command, TACACS+ must be enabled using the tacacs+ enable command.
Examples
The following example shows how to discard a TACACS+ CFS distribution session in progress.
switch# config terminalswitch(config)# tacacs+ abortRelated Commands
show tacacs+
Displays TACACS+ CFS distribution status and other details.
tacacs+ distribute
Enables CFS distribution for TACACS+.
tacacs+ enable
Enables TACACS+.
tacacs+ commit
To apply the pending configuration pertaining to the TACACS+ Cisco Fabric Services (CFS) distribution session in progress in the fabric, use the tacacs+ commit command in configuration mode.
tacacs+ commit
Syntax Description
This command has no other arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command, TACACS+ must be enabled using the tacacs+ enable command.
Examples
The following example shows how to apply a TACACS+ configuration to the switches in the fabric.
switch# config terminalswitch(config)# tacacs+ commitRelated Commands
show tacacs+
Displays TACACS+ CFS distribution status and other details.
tacacs+ enable
Enables TACACS+.
tacacs+ distribute
Enables CFS distribution for TACACS+.
tacacs+ distribute
To enable Cisco Fabric Services (CFS) distribution for TACACS+, use the tacacs+ distribute command. To disable this feature, use the no form of the command.
tacacs+ distribute
no tacacs+ distribute
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command, TACACS+ must be enabled using the tacacs+ enable command.
Examples
The following example shows how to enable TACACS+ fabric distribution.
switch# config terminalswitch(config)# tacacs+ distributeRelated Commands
show tacacs+
Displays TACACS+ CFS distribution status and other details.
tacacs+ commit
Commits TACACS+ database changes to the fabric.
tacacs+ enable
Enables TACACS+.
tacacs+ enable
To enable TACACS+ in a switch, use the tacacs+ enable command in configuration mode. The disable this feature, use the no form of the command.
tacacs+ enable
no tacacs+ enable
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Further TACACS+ commands are only available when the TACACS+ feature is enabled.
Using SHA-1 as the hash algorithm may prevent RADIUS or TACACS+ usage.
Examples
switch# config terminalswitch(config)# tacacs+ enableRelated Commands
tacacs-server deadtime
To set a periodic time interval where a nonreachable (nonresponsive) TACACS+ server is monitored for responsiveness, use the tacacs-server deadtime command. To disable the monitoring of the nonresponsive TACACS+ server, use the no form of the command.
tacacs-server deadtime time
no tacacs-server deadtime time
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Setting the time interval to zero disables the timer. If the dead time interval for an individual TACACS+ 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, TACACS+ server monitoring is not performed unless the TACACS+ 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.
switch# config terminalswitch(config)# tacacs-server deadtime 10Related Commands
deadtime
Sets a time interval for monitoring a nonresponsive TACACS+ server.
show tacacs-server
Displays all configured TACACS+ server parameters.
tacacs-server directed-request
To specify a TACACS+ server to send authentication requests to when logging in, use the tacacs-server directed-request command. To revert to sending the authentication request to the configured group, use the no form of the command.
tacacs-server directed-request
no tacacs-server directed-request
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
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 TACACS+ server to send authentication requests when logging in.
switch# config terminalswitch(config)# tacacs-server directed-requestRelated Commands
show tacacs-server
Displays all configured TACACS+ server parameters.
show tacacs-server directed request
Displays a directed request TACACS+ server configuration.
tacacs-server host
To configure TACACS+ server options on a switch, use the tacacs-server host command in configuration mode. Use the no form of the command to revert to factory defaults.
tacacs-server host {server-name | ipv4-address | ipv6-address}
[key [0|7] shared-secret] [port port-number]
[test {idle-time time | password password | username name}]
[timeout seconds]no tacacs-server host {server-name | ipv4-address | ipv6-address}
[key [0|7] shared-secret] [port port-number]
[test {idle-time time | password password | username name}]
[timeout seconds]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
Configuration mode.
Command History
1.3(1)
This command was introduced.
3.0(1)
Added the ipv6-address argument and the test option.
Usage Guidelines
This command is only available when the TACACS+ feature is enabled using the tacacs+ enable command.
When the idle time interval is 0 minutes, periodic TACACS+ server monitoring is not performed.
Examples
The following example configures TACACS+ authentication.
switch# config terminalswitch(config)# tacacs-server host 10.10.2.3 key HostKeyswitch(config)# tacacs-server host tacacs2 key 0 abcdswitch(config)# tacacs-server host tacacs3 key 7 1234switch(config)# tacacs-server host 10.10.2.3 test idle-time 10switch(config)# tacacs-server host 10.10.2.3 test username testerswitch(config)# tacacs-server host 10.10.2.3 test password 2B9ka5Related Commands
show tacacs-server
Displays TACACS+ server information.
tacacs+ enable
Enables TACACS+.
tacacs-server key
To configure a global TACACS+ shared secret, use the tacacs-server key command. Use the no form of this command to removed a configured shared secret.
tacacs-server key [0 | 7] shared-secret
no tacacs-server key [0 | 7] shared-secret
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
You need to configure the TACACS+ preshared key to authenticate the switch to the TACACS+ 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 TACACS+ server configurations on the switch. You can override this global key assignment by explicitly using the key option in the tacacs-server host command.
This command is only available when the TACACS+ feature is enabled using the tacacs+ enable command.
Examples
The following example configures TACACS+ server shared keys.
switch# config terminalswitch(config)# tacacs-server key AnyWordswitch(config)# tacacs-server key 0 AnyWordswitch(config)# tacacs-server key 7 publicRelated Commands
show tacacs-server
Displays TACACS+ server information.
tacacs+ enable
Enable TACACS+.
tacacs-server timeout
To specify the time between retransmissions to the TACACS+ servers, use the tacacs-server timeout command. You can revert the retransmission time to its default by issuing the no form of the command.
tacacs-server timeout seconds
notacacs-server timeout seconds
Syntax Description
seconds
Specifies the time (in seconds) between retransmissions to the RADIUS server. The default is one (1) second and the valid range is 1 to 60 seconds.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
This command is only available when the TACACS+ feature is enabled using the tacacs+ enable command.
Examples
The following example configures the TACACS+ server timeout value.
switch# config terminalswitch(config)# tacacs-server timeout 30Related Commands
show tacacs-server
Displays TACACS+ server information.
tacacs+ enable
Enable TACACS+.
tail
To display the last lines (tail end) of a specified file, use the tail command in EXEC mode.
tail filename [number-of-lines]
Syntax Description
filename
The name of the file for which you want to view the last lines.
number-of-lines
(Optional) The number of lines you want to view. The range is 0 to 80 lines.
Defaults
Displays the last 10 lines.
Command Modes
EXEC mode.
Command History
Usage Guidelines
You need two separate CLI terminals to use this command. In one terminal, execute the run-script or any other desired command. In the other, issue the tail command for the mylog file. On the second terminal session, you will see the last lines of the mylog file (as it grows) that is being saved in response to the command issued in the first terminal.
If you specify a long file and would like to exit in the middle, enter Ctrl-c to exit this command.
Examples
The following example displays the last lines (tail end) of a specified file.
switch# run-script slot0:test mylogIn another terminal, issue the tail command for the mylog file.
switch# tail mylogconfig terminalIn the second CLI terminal, you see the last lines of the mylog file (as it grows) that is being saved in response to the command issued in the first terminal.
tape-bkgrp
To configure a crypto tape backup group, use the tape-bkgrp command. Use the no form of this command to disable this feature.
tape-bkgrp groupname
no tape-bkgrp groupname
Syntax Description
Defaults
None.
Command Modes
Cisco SME cluster configuration mode submode.
Command History
Usage Guidelines
A tape volume group is a group of tapes that are categorized by function. For example, HR1 could be designated tape volume group for all Human Resources backup tapes.
Adding tape groups allows you to select VSANs, hosts, storage devices, and paths that Cisco SME will use for encrypted data. For example, adding a tape group for HR data sets the mapping for Cisco SME to transfer data from the HR hosts to the dedicated HR backup tapes.
Examples
The following example adds a backup tape group:
switch# config tswitch(config)# sme cluster c1switch(config-sme-cl)# tape-bkgrp group1switch(config-sme-cl-tape-bkgrp)#The following example removes a backup tape group:
switch# config tswitch(config)# sme cluster c1switch(config-sme-cl)# no tape-bkgrp group1switch(config-sme-cl-tape-bkgrp)#Related Commands
clear sme
Clears Cisco SME configuration.
show sme cluster
Displays information about the Cisco SME cluster
tape compression
To configure tape compression, use the tape-compression command. To disable this feature, use the no form of the command.
tape-compression
no tape-compression
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Cisco SME cluster configuration submode.
Command History
Usage Guidelines
Use this command to compress encrypted data.
Examples
The following example enables tape compression
switch#config tswitch(config)#sme cluster c1switch(config-sme-cl)#tape-compressionThe following example disables tape compression
switch#config tswitch(config)#sme cluster c1switch(config-sme-cl)#no tape-compressionRelated Commands
tape-device
To configure a crypto tape device, use the tape-device command. To disable this feature, use the no form of the command.
tape-device device name
no tape-device device name
Syntax Description
Defaults
None.
Command Modes
Cisco SME tape volume configuration submode.
Command History
Usage Guidelines
The tape device commands are available in the (config-sme-cl-tape-bkgrp-tapedevice) submode.
Examples
The following example configures a crypto tape device:
switch# config tswitch(config)# sme cluster c1switch(config-sme-cl)# tape-bkgrp group1switch(config-sme-cl-tape-bkgrp)# tape-device devicename1switch(config-sme-cl-tape-bkgrp-tapedevice)#The following example removes a crypto tape device:
switch# config tswitch(config)# sme cluster c1switch(config-sme-cl)# tape-bkgrp group1switch(config-sme-cl-tape-bkgrp)# no tape-device devicename1switch(config-sme-cl-tape-bkgrp-tapedevice)#Related Commands
tape-keyrecycle
To configure tape key recycle policy, use the tape-keyrecycle command. To disable this feature, use the no form of the command.
tape-keyrecycle
no tape-keyrecycle
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Cisco SME cluster configuration submode.
Command History
Usage Guidelines
Cisco SME allows you to recycle the tape keys. If you enable tape key recycling, all the previous instances of the tape key will be deleted. If you do not enable tape key recycle, all the previous instances and the current instance of the tape key is maintained, and the current instance is incremented by 1. (???)
Examples
The following example enables tape key recycling:
switch# config tswitch(config)#sme cluster c1switch(config-sme-cl)#tape-keyrecycleThe following example disables tape key recycling:
switch# config tswitch(config)#sme cluster c1switch(config-sme-cl)#no tape-keyrecycle
show sme cluster
Displays information about the Cisco SME cluster
clear sme
Clears Cisco SME configuration.
tape-read command-id
To configure a SCSI tape read command for a SAN tuner extension N port, use the tape-read command-id command.
tape-read command-id cmd-id target pwwn transfer-size bytes [continuous [filemark-frequency frequency] | num-transactions number [filemark-frequency frequency]]
Syntax Description
Defaults
Filemark frequency: 0.
Command Modes
SAN extension N port configuration submode.
Command History
Usage Guidelines
To stop a continuous SCSI tape read command in progress, use the stop command-id command.
Note
There can be just one outstanding I/O at a time to the virtual N port that emulates the tape behavior.
Examples
The following example configures a single SCSI tape read command.
switch# san-ext-tunerswitch(san-ext)# nWWN 10:00:00:00:00:00:00:00switch(san-ext)# nport pwwn 12:00:00:00:00:00:00:56 vsan 13 interface gigabitethernet 1/2switch(san-ext-nport)# tape-read command-id 100 target 22:22:22:22:22:22:22:22 transfer-size 512000 num-transactions 5000000 filemark-frequency 32The following example configures a continuous SCSI tape read command.
switch# san-ext-tunerswitch(san-ext)# nWWN 10:00:00:00:00:00:00:00switch(san-ext)# nport pwwn 12:00:00:00:00:00:00:56 vsan 13 interface gigabitethernet 1/2switch(san-ext-nport)# tape-read command-id 100 target 22:22:22:22:22:22:22:22 transfer-size 512000 continuous filemark-frequency 32Related Commands
tape-volgrp
To configure the crypto tape volume group, use the tape-volgrp command. To disable this command, use the no form of the command.
tape-volgrp group name
no tape-volgrp group name
Syntax Description
Defaults
None.
Command Modes
Cisco SME crypto backup tape group configuration submode.
Command History
Usage Guidelines
The tape volume group commands are available in the Cisco SME crypto tape volume group (config-sme-cl-tape-bkgrp-volgrp) submode.
Examples
The following example configures a crypto tape volume group:
switch# config tswitch(config))# sme cluster c1switch(config-sme-cl)# tape-bkgrp tbg1switch(config-sme-cl-tape-bkgrp)# tape-volgrp tv1switch(config-sme-cl-tape-bkgrp-volgrp)#The following example removes a crypto tape volume group.
switch# config tswitch(config)# sme cluster c1switch(config-sme-cl)# tape-bkgrp tbg1switch(config-sme-cl-tape-bkgrp)# no tape-volgrp tv1Related Commands
show sme cluster tape
Displays information about tapes
clear sme
Clears Cisco SME configuration.
tape-write command-id
To configure a SCSI tape write command for a SAN tuner extension N port, use the tape-write command-id command.
tape-write command-id cmd-id target pwwn transfer-size bytes [continuous [filemark-frequency frequency] | num-transactions number [filemark-frequency frequency]]
Syntax Description
Defaults
Filemark frequency: 0.
Command Modes
SAN extension N port configuration submode.
Command History
Usage Guidelines
To stop a continuous SCSI tape write command in progress, use the stop command-id command.
Note
Examples
The following example configures a single SCSI tape write command.
switch# san-ext-tunerswitch(san-ext)# nWWN 10:00:00:00:00:00:00:00switch(san-ext)# nport pwwn 12:00:00:00:00:00:00:56 vsan 13 interface gigabitethernet 1/2switch(san-ext-nport)# tape-write command-id 100 target 22:22:22:22:22:22:22:22 transfer-size 512000 num-transactions 5000000 filemark-frequency 32The following example configures a continuous SCSI tape write command.
switch# san-ext-tunerswitch(san-ext)# nWWN 10:00:00:00:00:00:00:00switch(san-ext)# nport pwwn 12:00:00:00:00:00:00:56 vsan 13 interface gigabitethernet 1/2switch(san-ext-nport)# tape-write command-id 100 target 22:22:22:22:22:22:22:22 transfer-size 512000 continuous filemark-frequency 32Related Commands
target (iSLB initiator configuration)
To configure an iSLB initiator target, use the target command in iSLB initiator configuration submode. To remove the target configuration, use the no form of the command.
target {device-alias device-alias | pwwn pWWN}
[vsan vsan-id]
[no-zone]
[trespass]
[revert-primary-port]
[fc-lun LUN iscsi-lun LUN]
[sec-device-alias device-alias | sec-pwwn pWWN]
[sec-vsan sec-vsan-id]
[sec-lun LUN]
[iqn-name target-name]no target {device-alias device-alias | pwwn pWWN}
[vsan vsan-id]
[no-zone]
[trespass]
[revert-primary-port]
[fc-lun LUN iscsi-lun LUN]
[sec-device-alias device-alias | sec-pwwn pWWN]
[sec-vsan sec-vsan-id]
[sec-lun LUN]
[iqn-name target-name]Syntax Description
Defaults
None.
Command Modes
iSLB initiator configuration submode.
Command History
Usage Guidelines
You can configure an iSLB initiator target using the device alias or the pWWN. You have the option of specifying one or more of the following optional parameters:
•
•
•
•
•
Note
If you configure an IQN for an initiator target, then that name is used to identify the initiator target. Otherwise, a unique IQN is generated for the initiator target.
Examples
The following example configures an iSLB initiator using an IP address and then enters iSLB initiator configuration submode.
switch# config tswitch(config)# islb initiator ip-address 100.10.10.10The following example grants iSLB initiator access to the target using a pWWN with auto zoning enabled (default).
switch (config-islb-init)# target pwwn 26:00:01:02:03:04:05:06The following example grants iSLB initiator access to the target using a pWWN with auto zoning disabled.
switch (config-islb-init)# target pwwn 26:00:01:02:03:04:05:06 no-zoneThe following example grants iSLB initiator access to the target using a device alias and optional LUN mapping.
switch(config-islb-init)# target device-alias SampleAlias fc-lun 0x1234 iscsi-lun 0x2345
The following example grants iSLB initiator access to the target using a device alias and an optional IQN.
switch(config-islb-init)# target device-alias SampleAlias iqn-name iqn.1987-01.com.cisco.initiator
The following example grants iSLB initiator access to the target using a device alias and a VSAN identifier.
switch(config-islb-init)# target device-alias SampleAlias vsan 10
Note
The following example disables the configured iSLB initiator target.
switch (config-islb-init)# no target pwwn 26:00:01:02:03:04:05:06Related Commands
tcp cwm
To configure congestion window monitoring (CWM) TCP parameters, use the tcp cwm command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp cwm [burstsize size]
no tcp cwm [burstsize size]
Syntax Description
Defaults
Enabled.
The default FCIP burst size is 10 KB.
The default iSCSI burst size is 50 KB
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
Use these TCP parameters to control TCP retransmission behavior in a switch.
Examples
The following example configures a FCIP profile and enables congestion monitoring.
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)# tcp cwmThe following example assigns the burstsize value at 20 KB:
switch(config-profile)# tcp cwm burstsize 20The following example disables congestion monitoring.
switch(config-profile)# no tcp cwmThe following example leaves the CWM feature in an enabled state but changes the burstsize to the default of 10 KB.
switch(config-profile)# no tcp cwm burstsize 25Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp keepalive-timeout
To configure the interval between which the TCP connection verifies if the FCIP link is functioning, use the tcp keepalive-timeout command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp keepalive-timeout seconds
no tcp keepalive-timeout seconds
Syntax Description
Defaults
60 seconds.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
This command can be used to detect FCIP link failures.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)#The following example specifies the keepalive timeout interval for the TCP connection:
switch(config-profile)# tcp keepalive-timeout 120Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp maximum-bandwidth-kbps
To manage the TCP window size in Kbps, use the tcp maximum-bandwidth-kbps command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp max-bandwidth-kbps bandwidth min-available-bandwidth-kbps threshold {round-trip-time-ms milliseconds | round-trip-time-us microseconds}
no tcp max-bandwidth-kbps bandwidth min-available-bandwidth-kbps threshold {round-trip-time-ms milliseconds | round-trip-time-us microseconds}
Syntax Description
Defaults
Enabled.
The FCIP defaults are max-bandwidth = 1G, min-available-bandwidth = 500 Mbps, and round-trip-time =1 ms.
The iSCSI defaults are max-bandwidth = 1G, min-available-bandwidth = 70 Kbps, and round-trip-time =1 ms.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
The maximum-bandwidth option and the round-trip-time option together determine the window size.
The minimum-available-bandwidth option and the round-trip-time option together determine the threshold below which TCP aggressively increases its size. After it reaches the threshold the software uses standard TCP rules to reach the maximum available bandwidth.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)#The following example configures the maximum available bandwidth at 900 Kbps, the minimum slow start threshold as 300 Kbps, and the round trip time as 10 milliseconds:
switch(config-profile)# tcp max-bandwidth-kbps 900 min-available-bandwidth-kbps 300 round-trip-time-ms 10The following example reverts to the factory defaults:
switch(config-profile)# no tcp max-bandwidth-kbps 900 min-available-bandwidth-kbps 300 round-trip-time-ms 10The following example configures the maximum available bandwidth at 2000 Kbps, the minimum slow start threshold as 2000 Kbps, and the round trip time as 200 microseconds:
switch(config-profile)# tcp max-bandwidth-kbps 2000 min-available-bandwidth-kbps 2000 round-trip-time-us 200Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp maximum-bandwidth-mbps
To manage the TCP window size in Mbps, use the tcp maximum-bandwidth-mbps command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp max-bandwidth-mbps bandwidth min-available-bandwidth-mbps threshold {round-trip-time-ms milliseconds | round-trip-time-us microseconds}
no tcp max-bandwidth-mbps bandwidth min-available-bandwidth-mbps threshold {round-trip-time-ms milliseconds | round-trip-time-us microseconds}
Syntax Description
Defaults
Enabled.
The FCIP defaults are max-bandwidth = 1G, min-available-bandwidth = 500 Mbps, and round-trip-time =1 ms.
The iSCSI defaults are max-bandwidth = 1G, min-available-bandwidth = 70 Kbps, and round-trip-time =1 ms.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
The maximum-bandwidth option and the round-trip-time option together determine the window size.
The minimum-available-bandwidth option and the round-trip-time option together determine the threshold below which TCP aggressively increases its size. After it reaches the threshold the software uses standard TCP rules to reach the maximum available bandwidth.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)#The following example configures the maximum available bandwidth at 900 Mbps, the minimum slow start threshold as 300 Mbps, and the round trip time as 10 milliseconds:
switch(config-profile)# tcp max-bandwidth-mbps 900 min-available-bandwidth-mbps 300 round-trip-time-ms 10The following example reverts to the factory defaults:
switch(config-profile)# no tcp max-bandwidth-mbps 900 min-available-bandwidth-mbps 300 round-trip-time-ms 10The following example configures the maximum available bandwidth at 2000 Mbps, the minimum slow start threshold as 2000 Mbps, and the round trip time as 200 microseconds:
switch(config-profile)# tcp max-bandwidth-mbps 2000 min-available-bandwidth-mbps 2000 round-trip-time-us 200Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp max-jitter
To estimate the maximum delay jitter experienced by the sender in microseconds, use the tcp max-jitter command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp max-jitter microseconds
no tcp max-jitter microseconds
Syntax Description
Defaults
Enabled.
The default value is 100 microseconds for FCIP and 500 microseconds for iSCSI interfaces.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
None.
Examples
The following example configures delay jitter time:
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# fcip profile 3switch(config-profile)# tcp max-jitter 600switch(config-profile)# do show fcip profile 3FCIP Profile 3Internet Address is 10.3.3.3 (interface GigabitEthernet2/3)Tunnels Using this Profile: fcip3Listen Port is 3225TCP parametersSACK is enabledPMTU discovery is enabled, reset timeout is 3600 secKeep alive is 60 secMinimum retransmission timeout is 200 msMaximum number of re-transmissions is 4Send buffer size is 0 KBMaximum allowed bandwidth is 1000000 kbpsMinimum available bandwidth is 500000 kbpsEstimated round trip time is 1000 usecCongestion window monitoring is enabled, burst size is 10 KBConfigured maximum jitter is 600 usRelated Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp max-retransmissions
To specify the maximum number of times a packet is retransmitted before TCP decides to close the connection, use the tcp max-retransmissions command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp max-retransmissions number
no tcp max-retransmissions number
Syntax Description
Defaults
Enabled.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
The default is 4 and the range is from 1 to 8 retransmissions.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5The following example specifies the maximum number of retransmissions :
switch(config-profile)# tcp max-retransmissions 6Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp min-retransmit-time
To control the minimum amount of time TCP waits before retransmitting, use the tcp min-retransmit-time command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp min-retransmit-time milliseconds
no tcp min-retransmit-time milliseconds
Syntax Description
Defaults
300 milliseconds.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
None.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)#The following example specifies the minimum TCP retransmit time for the TCP connection:
switch(config-profile)# tcp min-retransmit-time 500Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp pmtu-enable
To configure path MTU (PMTU) discovery, use the tcp pmtu-enable command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp pmtu-enable [reset-timeout seconds]
no tcp pmtu-enable [reset-timeout seconds]
Syntax Description
Defaults
Enabled.
3600 seconds.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
None.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)#The following example disables PMTU discovery:
switch(config-profile)# no tcp pmtu-enableThe following example enables PMTU discovery with a default of 3600 seconds:
switch(config-profile)# tcp pmtu-enableThe following example specifies the PMTU reset timeout to 90 seconds:
switch(config-profile)# tcp pmtu-enable reset-timeout 90The following example leaves the PMTU in an enabled state but changes the timeout to the default of 3600 seconds:
switch(config-profile)# no tcp pmtu-enable reset-timeout 600Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp qos
To specify the differentiated services code point (DSCP) value to mark all IP packets (type of service—TOS field in the IP header) on an ISCSI interface, use the tcp qos command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp qos value
no tcp qos value
Syntax Description
Defaults
0
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
Use these TCP parameters to control TCP retransmission behavior in a switch.
Examples
The following example configures the TCP QoS value on an iSCSI interface.
switch# config terminalswitch(config)# interface iscsi 1/2switch(config-if)# tcp qos 5Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp qos control
To specify the differentiated services code point (DSCP) value to mark all IP packets (type of service—TOS field in the IP header), use the tcp qos control command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp qos control value data value
no tcp qos control value data value
Syntax Description
value
Applies the control DSCP value to all FCIP frames in the control TCP connection.
data value
Applies the data DSCP value applies to all FCIP frames in the data connection.
Defaults
Enabled.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
Use these TCP parameters to control TCP retransmission behavior in a switch.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)#The following example configures the control TCP connection and data connection to mark all packets on that DSCP value:
switch(config-profile)# tcp qos control 3 data 5Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp sack-enable
To enable selective acknowledgment (SACK) to overcome the limitations of multiple lost packets during a TCP transmission, use the tcp sack-enable command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp sack-enable
no tcp sack-enable
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
The receiving TCP sends back SACK advertisements to the sender. The sender can then retransmit only the missing data segments.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)#The following example enables the SACK mechanism on the switch:
switch(config-profile)# tcp sack-enableRelated Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp send-buffer-size
To define the required additional buffering—beyond the normal send window size —that TCP allows before flow controlling the switch's egress path for the FCIP interface, use the tcp send-buffer-size command. Use the no form of this command to disable this feature or revert to its factory defaults.
tcp send-buffer-size size
no tcp send-buffer-size size
Syntax Description
Defaults
Enabled.
The default FCIP buffer size is 0 KB.
The default iSCSI buffer size is 4096 KB
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
None.
Examples
The following example configures a FCIP profile:
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)#The following example configure the advertised buffer size to 5000 KB :
switch(config-profile)# tcp send-buffer-size 5000Related Commands
fcip profile
Configures FCIP profile parameters.
show fcip profile
Displays FCIP profile information.
tcp-connection
To configure the number of TCP connections for the FCIP interface, use the tcp-connection command. To revert to the default, use the no form of the command.
tcp-connection number
no tcp-connection number
Syntax Description
Defaults
Two attempts.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
Access this command from the switch(config-if)# submode.
Use the tcp-connection option to specify the number of TCP connections from a FCIP link. By default, the switch tries two (2) TCP connections for each FCIP link.
Examples
The following example configures the TCP connections.
switch# config terminalswitch(config)# interface fcip 50switch(config-if)# tcp-connection 1switch(config-if)# no tcp-connection 1Related Commands
show interface fcip
Displays an interface configuration for a specified FCIP interface.
telnet
To log in to a host that supports Telnet, use the telnet command in EXEC mode.
telnet {hostname | ip-address} [port]
Syntax Description
hostname
Specifies a host name. Maximum length is 64 characters.
ip-address
Specifies an IP address.
port
(Optional) Specifies a port number. The range is 0 to 2147483647.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
None.
Examples
The following example establishes a Telnet session to the specified IP address.
switch# telnet 172.22.91.153Trying 172.22.91.153...Connected to 172.22.91.153.Login:xxxxxxxxPassword:xxxxxxxxxswitch#Related Commands
telnet server enable
To enable the Telnet server if you wish to return to a Telnet connection from a secure SSH connection, use the telnet server enable command. To disable the Telnet server, use the no form of this command
telnet server enable
no telnet server enable
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example enables the Telnet server.
switch(config)# telnet server enableupdatedThe following example disables the Telnet server.
switch(config)# no telnet server enableupdatedRelated Commands
terminal
To configure terminal attributes, use the terminal command in EXEC mode. To revert to the defaults, use the no form of the command.
terminal {length lines | monitor | session-timeout | terminal-type type | tree-update |
width integer}terminal no {length | monitor | session-timeout | terminal-type | width}
Syntax Description
Defaults
The default number of lines for the length is 24. The default width is 80 lines.
Command Modes
EXEC mode.
Command History
Usage Guidelines
Remember that all terminal parameter-setting commands are set locally and do not remain in effect after a session is ended. You must perform this task at the EXEC prompt at each session to see the debugging messages.
If the length is not 24 and the width is not 80, then you need to set a length and width.
Examples
The following example displays debug command output and error messages during the current terminal session.
switch# terminal monitorAug 8 10:32:42 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_CFG_PWRDN: Module 1 powered downAug 8 10:32:42 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_PWRDN: Module 1 powered downAug 8 10:32:42 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_INSERT: Module 1 has been insertedAug 8 10:33:12 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_PWRON: Module 1 powered upAug 8 10:33:13 sup48 % LOG_MODULE-5-MOD_REG_OK: LCM - Registration succeeded for module 1Aug 8 10:38:15 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_CFG_PWRDN: Module 1 powered downAug 8 10:38:15 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_INSERT: Module 1 has been inserted......The following example stops the current terminal monitoring session.
switch# terminal no monitorRelated Commands
time
To configure the time for the command schedule, use the time command. To disable this feature, use the no form of the command.
time {daily daily-schedule | monthly monthly-schedule | start {start-time | now} |
weekly weekly-schedule}no time
Syntax Description
Defaults
Disabled.
Command Modes
Scheduler job configuration submode.
Command History
Usage Guidelines
To use this command, the command scheduler must be enabled using the scheduler enable command.
Examples
The following example shows how to configure a command schedule job to run every Friday at 2200.
switch# config terminalswitch(config)# scheduler schedule name MyScheduleswitch(config-schedule)# time weekly 6:22:00The following example starts a command schedule job in two minutes and repeats every 24 hours.
switch(config-schedule)# time start now repeat 24:00Related Commands
scheduler enable
Enables the command scheduler.
scheduler schedule name
Configures a schedule for the command scheduler.
show scheduler
Displays schedule information.
time-stamp
To enable FCIP time stamps on a frame, use the time-stamp command. To disable this command for the selected interface, use the no form of the command.
time-stamp [acceptable-diff number]
no time-stamp [acceptable-diff number]
Syntax Description
acceptable-diff number
Configures the acceptable time difference for timestamps in milliseconds. The range is 500 to 10000.
Defaults
Disabled.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
Access this command from the switch(config-if)# submode.
The time-stamp option instructs the switch to discard frames that are older than a specified time.
Examples
The following example enables the timestamp for an FCIP interface.
switch# config terminalswitch(config)# interface fcip 50switch(config-if)# time-stampswitch(config-if)# time-stamp acceptable-diff 4000Related Commands
tlport alpa-cache
To manually configure entries in an ALPA cache, use the tlport alpa-cache command
tlport alpa-cache interface interface pwwn pwwn alpa alpa
no tlport alpa-cache interface interface pwwn pwwn
Syntax Description
interface interface
Specifies a Fibre Channel interface.
pwwn pwwn
Specifies the peer WWN ID for the ALPA cache entry.
alpa alpa
Specifies the ALPA cache to which this entry is to be added.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Generally, ALPA cache entries are automatically populated when an ALPA is assigned to a device. Use this command only if you wish to manually add further entries.
Examples
The following example configures the specified pWWN as a new entry in this cache
switch# config terminalswitch(config)# tlport alpa-cache interface fc1/2 pwwn 22:00:00:20:37:46:09:bd alpa 0x02Related Commands
traceroute
To print the route an IP packet takes to a network host, use the traceroute command in EXEC mode.
traceroute [ipv6] [hostname [size packet-size] | ip-address] | hostname | ip-address]
Syntax Description
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
This command traces the route an IP packet follows to an Internet host by launching UDP probe packets with a small TTL (time to live) and then listening for an ICMP (Internet Control Message Protocol) "time exceeded" reply from a gateway.
Note
Examples
The following example prints the route IP packets take to the network host www.cisco.com.
switch# traceroute www.cisco.comtraceroute to www.cisco.com (171.71.181.19), 30 hops max, 38 byte packets1 kingfisher1-92.cisco.com (172.22.92.2) 0.598 ms 0.470 ms 0.484 ms2 nubulab-gw1-bldg6.cisco.com (171.71.20.130) 0.698 ms 0.452 ms 0.481 ms3 172.24.109.185 (172.24.109.185) 0.478 ms 0.459 ms 0.484 ms4 sjc12-lab4-gw2.cisco.com (172.24.111.213) 0.529 ms 0.577 ms 0.480 ms5 sjc5-sbb4-gw1.cisco.com (171.71.241.174) 0.521 ms 0.495 ms 0.604 ms6 sjc12-dc2-gw2.cisco.com (171.71.241.230) 0.521 ms 0.614 ms 0.479 ms7 sjc12-dc2-cec-css1.cisco.com (171.71.181.5) 2.612 ms 2.093 ms 2.118 ms8 www.cisco.com (171.71.181.19) 2.496 ms * 2.135 mstransfer-ready-size
To configure the target transfer ready size for SCSI write commands on a SAN tuner extension N port, use the transfer-ready-size command.
transfer-ready-size bytes
Syntax Description
Defaults
None.
Command Modes
SAN extension N port configuration submode.
Command History
Usage Guidelines
For a SCSI write command-id command with a larger transfer size, the target performs multiple transfers based on the specified transfer size.
Examples
The following example configures the transfer ready size on a SAN extension tuner N port.
switch# san-ext-tunerswitch(san-ext)# nWWN 10:00:00:00:00:00:00:00switch(san-ext)# nport pwwn 12:00:00:00:00:00:00:56 vsan 13 interface gigabitethernet 1/2switch(san-ext-nport)# transfer-ready-size 512000Related Commands
transport email
To configure the customer ID with the Call Home function, use the transport email command in Call Home configuration submode. To disable this feature, use the no form of the command.
transport email {from email-address | reply-to email-address | smtp-server ip-address [port port-number]
no transport email {from email-address | reply-to email-address | smtp-server ip-address [port port-number]
Syntax Description
Defaults
None.
Command Modes
Call Home configuration submode.
Command History
Usage Guidelines
None.
Examples
The following example configures the from and reply-to e-mail addresses.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# callhomeswitch(config-callhome)# transport email from user@company1.comswitch(config-callhome)# transport email reply-to person@place.comThe following example configures the SMTP server and ports.
switch(config-callhome)# transport email smtp-server 192.168.1.1switch(config-callhome)# transport email smtp-server 192.168.1.1 port 30Related Commands
callhome
Configures the Call Home function.
callhome test
Sends a dummy test message to the configured destination(s).
show callhome
Displays configured Call Home information.
trunk protocol enable
To configure the trunking protocol, use the trunk protocol enable command in configuration mode. To disable this feature, use the no form of the command.
trunk protocol enable
no trunk protocol enable
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
If the trunking protocol is disabled on a switch, no port on that switch can apply new trunk configurations. Existing trunk configurations are not affected—the TE port continues to function in trunking mode, but only supports traffic in VSANs that it negotiated previously (when the trunking protocol was enabled). Also, other switches that are directly connected to this switch are similarly affected on the connected interfaces. In some cases, you may need to merge traffic from different port VSANs across a non-trunking ISL. If so, you need to disable the trunking protocol.
Examples
The following example shows how to disable the trunk protocol feature.
switch# config terminalswitch(config)# no trunk protocol enableThe following example shows how to enable the trunk protocol feature.
switch(config)# trunk protocol enableRelated Commands
tune-timer
To tune the Cisco SME timers, use the tune-timer command. To disable this command, use the no form of the command.
tune-timer {global_lb_timer global_lb_timer_value | rscn_suppression_timer rscn_suppresion_timer_value | tgt_lb_timer tgt_lb_timer_value}
no tune-timer {global_lb_timer global_lb_timer_value | rscn_suppression_timer rscn_suppresion_timer_value | tgt_lb_timer tgt_lb_timer_value}
Syntax Description
Defaults
None.
Command Modes
Cisco SME cluster configuration submode.
Command History
Usage Guidelines
The tune-timer command is used to tune various Cisco SME timers such as the RSCN suppression, global load balancing and target load balancing timers. These timers should be used only in large scaling setups. The timer values are synchronized throughout the cluster.
Examples
The following example configures a global load balancing timer value:
switch# config tswitch(config))# sme cluster c1switch(config-sme-cl)# tune-timer tgt_lb_timer 6switch(config-sme-cl)#The following example configures a Cisco SME RSCN suppression timer value:
switch# config tswitch(config))# sme cluster c1switch(config-sme-cl)# tune-timer rscn_suppression_timer 2switch(config-sme-cl)#The following example configures a target load balancing timer value:
switch# config tswitch(config))# sme cluster c1switch(config-sme-cl)# tune-timer rscn_suppression_timer 2switch(config-sme-cl)#
