- 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
- tacacs+ abort
- tacacs+ commit
- tacacs+ distribute
- tacacs+ enable
- tacacs-server deadtime
- tacacs-server directed-request
- tacacs-server host
- tacacs-server key
- tacacs-server test
- tacacs-server timeout
- tag
- tail
- tape-bkgrp
- tape compression
- tape-device
- tape-keyrecycle
- tape-read command-id
- tape-volgrp
- tape-write command-id
- target (iSLB initiator configuration)
- tclquit
- tcp cwm
- tcp keepalive-timeout
- tcp maximum-bandwidth-kbps
- tcp maximum-bandwidth-mbps
- tcp max-jitter
- tcp max-retransmissions
- tcp min-retransmit-time
- tcp pmtu-enable
- tcp sack-enable
- tcp send-buffer-size
- tcp-connections
- telnet
- telnet server enable
- terminal alias
- terminal ask-on-term
- terminal color
- terminal deep-help
- terminal dont-ask
- terminal edit-mode vi
- terminal event-manager bypass
- terminal exec prompt timestamp
- terminal history no-exec-in-config
- terminal home
- terminal length
- terminal monitor
- terminal output xml
- terminal password
- terminal redirection-mode
- terminal session-timeout
- terminal sticky-mode
- terminal terminal-type
- terminal time
- terminal verify-only
- terminal width
- test aaa authorization
- time
- time-stamp
- tlport alpa-cache
- traceroute
- tr ansceiver-frequency
- transfer-ready-size
- transport email
- transport email mail-server
- transport http proxy enable
- transport http proxy server
- terminal verify-user
- trunk protocol enable
- trustedcert
- tune
- tune-timer
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 to determine the appropriate mode for each command.
tacacs+ abort
To discard a TACACS+ Cisco Fabric Services (CFS) distribution session in progress, use the tacacs+ abort command in configuration mode.
Syntax Description
Defaults
Command Modes
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:
Related Commands
|
|
|
|---|---|
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.
Syntax Description
Defaults
Command Modes
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:
Related Commands
|
|
|
|---|---|
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.
Syntax Description
Defaults
Command Modes
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:
Related Commands
|
|
|
|---|---|
tacacs+ enable
To enable TACACS+ in a switch, use the tacacs+ enable command in configuration mode. To disable this feature, use the no form of the command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Additional 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
The following example shows how to enable TACACS+ in a switch:
Related 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.
no tacacs -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 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:
Related Commands
|
|
|
|---|---|
Sets a time interval for monitoring a nonresponsive TACACS+ server. |
|
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
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 TACACS+ server to send authentication requests when logging in:
Related Commands
|
|
|
|---|---|
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
Command History
|
|
|
|---|---|
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:
Related Commands
|
|
|
|---|---|
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
Command Modes
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:
Related Commands
|
|
|
|---|---|
tacacs-server test
To configure a parameter to send test packets, use the tacacs-server test command. To disable this feature, use the no form of the command.
tacacs-server test {{username {username} | {[password {password} [idle-time {time}]] | [idle-time {time}]} } | { password {password} [ idle-time {time} ] } | {idle-time {time} }}
no tacacs-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
|
|
|
|---|---|
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 using the no form of the command.
no tacacs-server timeout seconds
Syntax Description
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
Command Modes
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:
Related Commands
|
|
|
|---|---|
tag
To correlate multiple events in an event manager applet, use the tag command. To remove the correlation, use the no form of the command.
tag tagname1 { and | andnot | or } tagname2 [{and | andnot | or } tagname3 [{ and | andnot | or } tagname4 ]] happens occurs in seconds
no tag tagname1 { and | andnot | or} tagname2 [{ and | andnot | or} tagname3 [{ and | andnot | or } tagname4 ]] happens occurs in seconds
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
This command does not require a license.
Tag names have scope only within the policy they are defined in. Tag names must be already configured in event commands before they can be used in a tag command.The evaluation of tag logic operators is from left to right since all operators are of equal precedence, that is:
When a cli match event is tagged, the behavior changes compared to untagged cli match events. Commands matching a tagged cli match event are executed immediately. If this were not the case, there may be a delay while waiting for other tagged events to match before an event-default command in the applet action block is executed.
Examples
The following example shows how to use the tag command. The goal in this example is to save the latest core dump to bootflash (it could also be sent to an SFTP server etc). The first policy is triggered when a process crash is about to generate a core file. It sleeps for 60 seconds while the core file is generated and then increments a counter. The second policy monitors the counter as well as system switchover events. If the counter is greater than 0 and no switchovers have occurred in the last 60 seconds then the latest core file is copied to bootflash and the counter reset to 0. No exit-op is specified for the counter so that the second policy can be triggered multiple times at once.
|
|
|
|---|---|
Configures a command to be executed when an Embedded Event Manager (EEM) applet is triggered. |
|
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
The name of the file for which you want to view the last lines. |
|
(Optional) The number of lines you want to view. The range is 0 to 80 lines. |
Defaults
Command Modes
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, enter 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, press Ctrl-C to exit this command.
Examples
The following example displays the last lines (tail end) of a specified file:
In another terminal, enter the tail command for the mylog file:
In 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 entered 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.
Syntax Description
Defaults
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:
The following example removes a backup tape group:
Related Commands
|
|
|
|---|---|
tape compression
To configure tape compression, use the tape-compression command. To disable this feature, use the no form of the command.
Syntax Description
Defaults
Command Modes
Cisco SME cluster configuration submode.
Command History
|
|
|
Usage Guidelines
Examples
The following example enables tape compression:
The following example disables tape compression:
Related Commands
|
|
|
|---|---|
Displays information about all tape volume groups or a specific group. |
tape-device
To configure a crypto tape device, use the tape-device command. To disable this feature, use the no form of the command.
Syntax Description
Defaults
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:
The following example removes a crypto tape device:
Related Commands
|
|
|
|---|---|
Displays information about all tape volume groups or a specific group |
tape-keyrecycle
To configure tape key recycle policy, use the tape-keyrecycle command. To disable this feature, use the no form of the command.
Syntax Description
Defaults
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:
The following example disables tape key recycling:
Related Commands
|
|
|
|---|---|
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
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:
The following example configures a continuous SCSI tape read command.
Related Commands
|
|
|
|---|---|
Cancels a SCSI command in progress on a SAN extension tuner N port. |
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.
Syntax Description
Defaults
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:
The following example removes a crypto tape volume group:
Related Commands
|
|
|
|---|---|
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
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 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 write command:
The following example configures a continuous SCSI tape write command:
Related Commands
|
|
|
|---|---|
Cancels a SCSI command in progress on a SAN extension tuner N port. |
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
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 The VSAN identifier is optional if the target is online. If the target is not online, the VSAN identifier is required.
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:
The following example grants iSLB initiator access to the target using a pWWN with auto zoning enabled (default):
The following example grants iSLB initiator access to the target using a pWWN with auto zoning disabled:
The 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:
Note The VSAN identifier is optional if the target is online. If the target is not online, the VSAN identifier is required.
The following example disables the configured iSLB initiator target.
Related Commands
|
|
|
|---|---|
Assigns an iSLB name and IP address to the iSLB initiator and enters iSLB initiator configuration submode. |
|
tclquit
To exit Tcl, use the tclquit command.
Syntax Description
Defaults
Command Modes
Interactive Tcl shell and Tcl script.
Command History
|
|
|
Usage Guidelines
Terminates the current Tcl process. Synonym for the exit command.
Examples
The following example terminates the current interactive Tcl shell:
Related Commands
|
|
|
|---|---|
End the Tcl application (for a list of standard Tcl commands, see the Tcl documentation). |
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.
Syntax Description
(Optional) Specifies the burstsize ranging from 10 to 100 KB. |
Defaults
Command Modes
FCIP profile configuration submode
iSCSI interface 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:
The following example assigns the burstsize value at 20 KB:
The following example disables congestion monitoring:
The following example leaves the CWM feature in an enabled state but changes the burstsize to the default of 10 KB:
Related Commands
|
|
|
|---|---|
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.
no tcp keepalive-timeout seconds
Syntax Description
Defaults
Command Modes
FCIP profile configuration submode
iSCSI interface configuration submode
Command History
|
|
|
Usage Guidelines
Examples
The following example configures a FCIP profile:
The following example specifies the keepalive timeout interval for the TCP connection:
Related Commands
|
|
|
|---|---|
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
The FCIP defaults are max-bandwidth = 1G, min-available-bandwidth = 500 Mbps, and round-trip-time =1 ms.
The iSCSI defaults are max-bandwidth = 10000 Mbps (10Gbps), min-available-bandwidth = 8000 Mbps, and round-trip-time =1 ms.
Command Modes
FCIP profile configuration submode
iSCSI interface configuration submode
Command History
|
|
|
The IPStorage support was increased to 10G on the Cisco MDS 9250i Multiservice Fabric Switch. |
|
Usage Guidelines
The maximum-bandwidth option and the round-trip-time option together determine the window size. The maximum-bandwidth option limits only the IPStorage traffic and not the FCIP traffic or the iSCSI traffic.
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.
When configuring tcp bandwidth using the tcp maximum-bandwidth-kbps and tcp minimum-bandwidth-kbps commands, the value should not exceed the maximum speed of the physical IPStorage port.
The maximum and minimum tcp bandwidth of all the FCIP and iSCSI interfaces that are using a specific Gigabit Ethernet or IPStorage port should not exceed the maximum speed of the physical IPStorage port.
For optimal performance the minimum-bandwidth-kbps should be 80%-90% of the maximum-bandwidth-kbps.
Examples
The following example configures a FCIP 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:
The following example reverts to the factory defaults:
The 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:
The following example configures an iSCSI profile:
The following example configures the maximum available bandwidth at 9000000 Kbps, the minimum slow start threshold as 8000000 Kbps, and the round trip time as 20 milliseconds:
The following example configures the maximum available bandwidth at 5000000 Kbps, the minimum slow start threshold as 4000000 Kbps, and the round trip time as 200 microseconds:
Related Commands
|
|
|
|---|---|
Displays the iSCSI configuration for the port along with the tcp maximum and minimum bandwidth configuration. |
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
The FCIP defaults are max-bandwidth = 1G, min-available-bandwidth = 500 Mbps, and round-trip-time =1 ms.
The iSCSI defaults are max-bandwidth = 10000 Mbps (10Gbps), min-available-bandwidth = 8000 Mbps, and round-trip-time =1 ms.
Command Modes
FCIP profile configuration submode.
iSCSI interface configuration submode
Command History
|
|
|
The IPStorage support was increased to 10G on the Cisco MDS 9250i Multiservice Fabric Switch. |
|
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.
When configuring tcp bandwidth using the tcp maximum-bandwidth-mbps and tcp minimum-bandwidth-mbps commands, the value should not exceed the maximum speed of the physical IPStorage port.
The maximum and minimum tcp bandwidth of all the FCIP and iSCSI interfaces that are using a specific Gigabit Ethernet or IPStorage port should not exceed the maximum speed of the physical IPStorage port.
For optimal performance the minimum-bandwidth-mbps should be 80%-90% of the maximum-bandwidth-mbps.
Examples
The following example configures a FCIP 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:
The following example reverts to the factory defaults:
The 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:
The following example configures an iSCSI profile:
The following example configures the maximum available bandwidth at 9000 Mbps, the minimum slow start threshold as 8000 Mbps, and the round trip time as 20 milliseconds:
The following example reverts to the factory defaults:
The following example configures the maximum available bandwidth at 5000 Mbps, the minimum slow start threshold as 4000 Mbps, and the round trip time as 200 microseconds:
Related Commands
|
|
|
|---|---|
Displays the iSCSI configuration for the port along with the tcp maximum and minimum bandwidth configuration. |
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.
no tcp max-jitter microseconds
Syntax Description
Specifies the delay time in microseconds ranging from 0 to 10000. |
Defaults
The default value is 100 microseconds for FCIP and 500 microseconds for iSCSI interfaces.
Command Modes
FCIP profile configuration submode
iSCSI interface configuration submode
Command History
|
|
|
Usage Guidelines
Examples
The following example configures delay jitter time:
Related Commands
|
|
|
|---|---|
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
Command Modes
FCIP profile configuration submode
iSCSI interface 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:
The following example specifies the maximum number of retransmissions :
Related Commands
|
|
|
|---|---|
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
Specifies the time in milliseconds. The range is 200 to 5000. |
Defaults
Command Modes
FCIP profile configuration submode
iSCSI interface configuration submode
Command History
|
|
|
Usage Guidelines
Examples
The following example configures a FCIP profile:
The following example specifies the minimum TCP retransmit time for the TCP connection:
Related Commands
|
|
|
|---|---|
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
(Optional) Specifies the PMTU reset timeout. The range is 60 to 3600 seconds. |
Defaults
Command Modes
FCIP profile configuration submode
iSCSI interface configuration submode
Command History
|
|
|
Usage Guidelines
Examples
The following example configures a FCIP profile:
The following example disables PMTU discovery:
The following example enables PMTU discovery with a default of 3600 seconds:
The following example specifies the PMTU reset timeout to 90 seconds:
The following example leaves the PMTU in an enabled state but changes the timeout to the default of 3600 seconds:
Related Commands
|
|
|
|---|---|
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.
Syntax Description
Defaults
Command Modes
FCIP profile configuration submode
iSCSI interface 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:
The following example enables the SACK mechanism on the switch:
Related Commands
|
|
|
|---|---|
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.
Syntax Description
Defaults
Command Modes
FCIP profile configuration submode
iSCSI interface configuration submode
Command History
|
|
|
Usage Guidelines
Examples
The following example configures a FCIP profile:
The following example configure the advertised buffer size to 5000 KB:
Related Commands
|
|
|
|---|---|
tcp-connections
To configure the number of TCP connections for the FCIP interface, use the tcp-connections command. To revert to the default, use the no form of the command.
Syntax Description
Enters the number of connections. Accepted values are 2 and 5 (For Cisco MDS 9250i Switch only). |
Defaults
Command Modes
Interface configuration submode
iSCSI interface configuration submode
Command History
|
|
|
Usage Guidelines
Access this command from the switch(config-if)# submode.
Use the tcp-connections option to specify the number of TCP connections contained in an FCIP link.
Set the TCP connections to 2 when:
- Both ends or peers of the FCIP tunnel are on Cisco MDS 9222i Switches or Cisco MDS 9000 18/4-Port Multiprotocol Services Modules (MSM) or Cisco MDS 9000 16-Port Storage Services Nodes (SSN).
- One end of the FCIP tunnel is on Cisco MDS 9222i switch, Cisco MDS 9000 18/4-Port Multiprotocol Services Module (MSM), or Cisco MDS 9000 16-Port Storage Services Node (SSN) and the other end is on Cisco MDS 9250i Switch.
Set the TCP connections to 5 when:
Note When both ends of the FCIP tunnel are on Cisco MDS 9250i Switches, the TCP connections can be set to either 2 or 5, we recommend to set the TCP connections to 5 for higher bandwidth.
Examples
The following example configures the TCP connections:
Related Commands
|
|
|
|---|---|
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
(Optional) Specifies a port number. The range is 0 to 2147483647. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example establishes a Telnet session to the specified IP address:
Related Commands
|
|
|
|---|---|
telnet server enable
To enable the Telnet server if you want 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
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example enables the Telnet server:
The following example disables the Telnet server:
Related Commands
|
|
|
|---|---|
terminal alias
To display and define command aliases for a user session, use the terminal alias command. To remove the alias definition, use the no form of this command.
terminal alias [persist] [ alias-name alias-definition ]
no terminal alias [persist] [ alias-name alias-definition ]
Syntax Description
(Optional) Makes the setting persistent for the current and future sessions for the current user. |
|
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Aliases that you define with the terminal alias command are only available to the current user. Other users cannot use these command aliases. To create aliases that other users can access, use the cli alias name command.
The alias setting applies only to the current user session. Use the persist keyword to change the setting for the current and future session for the current user.
Examples
This example shows how to define a command alias only for the current user session:
This example shows how to define a command alias to persist across a session for the current user:
This example shows how to display the command aliases available to the current user session:
This example shows how to remove a temporary command alias for the user session:
Related Commands
|
|
|
|---|---|
terminal ask-on-term
To enable all confirmation questions on the terminal, use the terminal ask-on-term command. To disable all confirmation questions, use the no form of this command.
Syntax Description
Name of the session where you want to enable or disable the confirmation questions. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Confirmation questions are used in NX-OS to confirm actions that may cause traffic disruption. The no terminal ask-on-term command disables even the confirmation questions that are prompted during a reload operation.
Examples
This example shows how to enable all confirmation questions on terminal pts/0 only:
This example shows how to disable all confirmation questions on terminal pts/0 only:
Related Commands
|
|
|
|---|---|
Disables the terminal from asking you confirmation statements. |
terminal color
To change the colors that are used when displaying the commands and outputs on the CLI for a user session, use the terminal color command. To revert to the default color, use the no form of this command.
Syntax Description
(Optional) Makes the setting persistent for the current and future sessions for the current user. |
Defaults
All CLI prompts, commands, and command outputs display in colors that are defined by the terminal emulator.
Command Modes
Command History
|
|
|
Usage Guidelines
The terminal color command changes the CLI colors as follows:
- Displays the command prompt in green if the previous command was successful.
- Displays the command prompt in red if an error occurred in the previous command.
- Displays the command in blue.
- Displays output in the default color that is defined by the terminal emulator.
The terminal color setting applies only to the current user session. Use the persist keyword to change the setting for the current and future session for the current user.
Examples
This example shows how to enable the terminal display colors for the current user session:
This example shows how to enable the terminal display colors for the current and future sessions for the current user:
This example shows how to revert to the default for the current user session:
This example shows how to revert to the default for the current and future sessions for the current user:
terminal deep-help
To enable the display of syntax of all possible options of a given command, use the terminal deep-help command. To disable detailed help, use the no form of this command.
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
To invoke detailed help for a command, enter the command followed by simultaneously pressing the Alt and the ? keys (the Alt key is the option key on Mac).
Examples
This example shows the possible options of the zoneset command:
terminal dont-ask
To disable confirmation prompts on the CLI, use the terminal dont-ask command. To revert to the default, use the no form of this command.
no terminal dont-ask [ persist ]
Syntax Description
(Optional) Makes the setting persistent for the current and future sessions for the current user. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
The terminal confirmation prompt setting applies only to the current user session. Use the persist keyword to change the setting for the current and future session for the current user.
Examples
This example shows how to disable the CLI confirmation prompts for the current user session:
This example shows how to disable the CLI confirmation prompts for the current and future sessions for the current user:
This example shows how to enable the terminal to ask confirmation statements:
This example shows how to enable the CLI confirmation prompts for the current and future sessions for the current user:
Related Commands
|
|
|
|---|---|
terminal edit-mode vi
To enable VI style editing of CLI history commands, use the terminal edit-mode command. To revert to the default editing mode, use the no form of this command.
terminal edit-mode vi [ persist ]
no terminal edit-mode vi [ persist ]
Syntax Description
(Optional) Makes the setting persistent for the current and future sessions for the current user. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
The following table provides information about the difference between EMACS and VI mode editing commands:
| Note This command deletes a word when the cursor is placed at the beginning of the word. |
||
The edit mode setting applies only to the current user session. Use the persist keyword to change the setting for the current and future session for the current user.
Examples
This example shows how to change the edit mode for recalled commands to VI style for the current user session:
This example shows how to change the edit mode for recalled commands to VI style for the current and future session for the current user:
This example shows how to revert the edit mode for recalled command to EMACS style for the current user session:
This example shows how to revert the edit mode for recalled command to EMACS style for the current and future sessions for the current user:
terminal event-manager bypass
To bypass all EEM policies that use event cli match statements to trap specific CLI commands, use terminal event-manager bypass command. To revert, use the terminal no event-manager bypass command.
terminal no event-manager bypass
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
This command allows the user to run commands that may be blocked or redirected by EEM policies.
Examples
This example shows a simple event manger applet that matches a CLI command and how to the terminal event-manager bypass command allows the user to bypass the EEM policy completely.
This example shows how to restore matching of CLI commands by EEM policies:
Related Commands
|
|
|
|---|---|
terminal exec prompt timestamp
To configure printing timestamps before each CLI command is executed, use the terminal exec prompt timestamp command. To remove the configuration, use the no form of this command.
terminal exec prompt timestamp
no terminal exec prompt timestamp
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
This setting will automatically print CPU usage and timestamp information before each command is run. This can be helpful in debugging issues.
Examples
This example shows the extra information that is displayed when this command is enabled:
terminal history no-exec-in-config
To exclude EXEC commands from the command history in config mode, use the terminal history no-exec-in-config command. To revert to the default, use the no form of this command.
terminal history no-exec-in-config
no terminal history no-exec-in-config
Defaults
The CLI command history always includes EXEC commands in configuration mode.
Command Modes
Command History
|
|
|
Usage Guidelines
By default, the Cisco NX-OS CLI history recalls all commands from the current command mode and higher command modes. For example, if you are working in global configuration mode, the command recall keystroke shortcuts recall both EXEC mode and global configuration mode commands. Using the terminal history no-exec-in-config command, you can avoid recalling any higher mode commands when you are in a configuration mode.
terminal home
To move the cursor to the line 1 and column 1 of the screen without erasing the screen output, use the terminal home command.
Defaults
Command Modes
Command History
|
|
|
terminal length
To set the number of lines used by the screen output pager, use the terminal length command. To revert to the default number of lines, use the no form of this command.
Syntax Description
Number of lines to display. Range is from 0 to 512. Enter 0 to disable paging. |
Defaults
If the terminal emulator does not specify a screen length, then the default length is set to 24 lines. Most modern terminals propagate their window length to the switch so that the switch will automatically page output to match the number of lines of the user's window.
Command Modes
Command History
|
|
|
Usage Guidelines
If a command output exceeds the number of terminal lines, the session pauses after displaying the number of lines set in the terminal length. Press the space bar to display another screen of lines or press the Enter key to display another line. To return to the command prompt, press Ctrl-C.
The terminal length setting applies only to the current session.
Examples
This example shows how to set the number of lines of command output to display on the terminal before pausing:
This example shows how to revert to the default number of lines:
Related Commands
|
|
|
|---|---|
Sets the number of character columns for the current terminal session. |
terminal monitor
To automatically display new syslog messages to the current session, use the terminal monitor command.
Defaults
Logs are printed to the console session and no logs are printed to terminal sessions.
Command Modes
Command History
|
|
|
Usage Guidelines
This command is helpful for monitoring of unexpected events during changes or debug messages during debugging. Be careful if this command is used for monitoring debugging as the session or system may be overloaded by the number of messages printed.
Related Commands
|
|
|
|---|---|
terminal output xml
To set the command output formatting to XML, use the terminal output xml command. To set the default output formatting, use the no form of this command.
terminal output xml [ 1.0 | NX-OS-version ]
no terminal output xml [ 1.0 | NX-OS-version ]
Syntax Description
(Optional) Specifies the XML version depending on the Cisco NX-OS version that is installed on your switch. |
Defaults
Command outputs are in free form text for human consumption.
Command Modes
Command History
|
|
|
Usage Guidelines
This command is useful for scripts or other services that expect XML formatted output from CLI commands.
Examples
This example shows how to set the command output formatting to XML:
This example shows how to set the command output formatting to XML version 1.0:
This example shows how to set the command output formatting to XML version 8.1.1b:
This example shows how to set the command output formatting to default:
Related Commands
|
|
|
|---|---|
terminal password
To assign a password to be used in the copy { ftp | scp | sftp } commands, use the terminal password command. To remove the password, use the no form of this command.
Defaults
There is no password set for the copy { ftp | scp | sftp } commands.
Command Modes
Command History
|
|
|
Usage Guidelines
The password that is configured by this command is not restricted to the current username. It will be used for the user specified in any copy command, which allows another user other than the current user to be given.
This command has two modes: inline and interactive. In the inline mode, the password is echoed on the screen. In the interactive mode, the password is not echoed. To use interactive mode, type the help character ? instead of a password. When prompted, enter the desired password.
This command is not stored in the switch configuration and is not persistent between logins.
Examples
This example shows how to configure a password in inline mode:
This example shows how to configure a password to be used in the copy { scp | ftp | sftp } commands:
This example shows how to remove the password that is configured for the copy { scp | ftp | sftp } commands:
Related Commands
|
|
|
|---|---|
terminal redirection-mode
To configure the file format of the show command output that is redirected to a file, use the terminal redirection-mode command.
terminal redirection-mode { ascii | zipped }
Syntax Description
Defaults
The file format of redirected the show command output is set to ASCII by default.
Command Modes
Command History
|
|
|
Usage Guidelines
Some of the show commands have lengthy outputs, especially show commands for debugging such as the show tech-support command. You can use the terminal redirection-mode command to reduce the size of the file when you redirect the output from the command.
The terminal redirection mode setting applies only to the current session.
Examples
This example shows how automatic zipping of redirected output works. The mode is set to zip, a file is created and then unzipped. The size of each file is checked.
This example shows how to configure ASCII format for the terminal redirection mode:
terminal session-timeout
To set the terminal inactivity timeout period for the current session, use the terminal session-timeout command.
terminal session-timeout minutes
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
A value of 0 minutes disables the session timeout.
The terminal session inactivity timeout setting applies only to the current session.
Examples
This example shows how to configure the terminal session timeout period to 1 minute:
This example shows how to disable the terminal session timeout:
Related Commands
|
|
|
|---|---|
terminal sticky-mode
To search for a command match in the current mode only, use the terminal sticky-mode command.
Defaults
The current mode and all higher modes are searched for matching commands.
Command Modes
Command History
|
|
|
Examples
This example shows how commands are constrained to the current mode when this setting is enabled:
terminal terminal-type
To set the terminal type, use the terminal terminal-type command. To revert to the default type, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Examples
This example shows how to set the terminal type to xterm :
This example shows how to revert to the default terminal type:
Related Commands
|
|
|
|---|---|
terminal time
To save the current time to a variable, use the terminal time command.
terminal time [ variable ] [ delta ]
Syntax Description
(Optional) Displays the delta time to the currently saved time value. |
Defaults
Command Modes
Command History
|
|
|
Examples
This example shows how to save the current time to a variable:
This example shows how to display the delta time to the currently saved time:
terminal verify-only
To verify if a user is permitted to run given commands, use the terminal verify-only command.
terminal verify-only [ username name ]
terminal no verify-only [ username name ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
When configured, this command changes the CLI mode to verify if a given command is allowed to be executed but does not execute the command. The full command to be tested should be given. If a username is specified, the tests are for the specified user and not for the current user. Issue the no option to revert to normal command execution mode.
Examples
This example shows how to verify if the current user can execute the show clock command:
This example shows how to test which commands the user 'a123456' may execute:
Related Commands
|
|
|
|---|---|
terminal width
To set the number of character columns for the current terminal session, use the terminal width command. To revert to the default, use the no form of this command.
Syntax Description
Defaults
If the terminal emulator does not specify a screen width, then the default number of character columns is 80. Most modern terminals propagate their window width to the switch so that the switch will automatically page output to match the width of the users window.
Command Modes
Command History
|
|
|
Usage Guidelines
The terminal width setting applies only to the current session.
Examples
This example shows how to set the number of columns to display on the terminal:
This example shows how to revert to the default number of columns:
Related Commands
|
|
|
|---|---|
Sets the number of lines on a screen for the current terminal session. |
test aaa authorization
To verify if the authorization settings are correct or not, use the test aaa authorization command.
test aaa authorization command-type {commands | config-commands} user {username} command {cmd}
Syntax Description
Specifies the command type. You can use the keywords for the command type. |
|
Specifies the user to be authorized. The maximum size is 32. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
Related 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 }
Syntax Description
Defaults
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:
The following example starts a command schedule job in two minutes and repeats every 24 hours:
Related Commands
|
|
|
|---|---|
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
(Optional) Configures the acceptable time difference for timestamps in milliseconds. The range is 500 to 10000. |
Defaults
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:
Related Commands
|
|
|
|---|---|
tlport alpa-cache
To manually configure entries in an ALPA cache, use the tlport alpa-cache command. To disable the entries in an ALPA cache, use the no form of the command.
tlport alpa-cache interface interface pwwn pwwn alpa alpa
no tlport alpa-cache interface interface pwwn pwwn
Syntax Description
Specifies the ALPA cache to which this entry is to be added. |
Defaults
Command Modes
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 want to manually add additional entries.
Examples
The following example configures the specified pWWN as a new entry in this cache:
Related 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
(Optional) Specifies a host name. Maximum length is 64 characters. |
|
Defaults
Command Modes
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 Probes start with a TTL of one and increase by one until encountering an ICMP “port unreachable.” This means that the host was accessed or a maximum flag was found. A line is printed showing the TTL, address of the gateway, and round-trip time of each probe. If the probe answers come from different gateways, the address of each responding system is printed.
Examples
The following example prints the route IP packets take to the network host www.cisco.com:
transceiver-frequency
To set the interface clock to ethernet or Fibre Channel, use the transceiver-frequency command in interface configuration mode. To disable the ethernet clock for the port, use the no form of the command.
transceiver-frequency [ethernet] force
no transceiver-frequency [ethernet] force
Syntax Description
(Optional) Specifies the ethernet transceiver frequency for an interface. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to set the interface clock to ethernet or Fibre Channel:
transfer-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.
Syntax Description
Specifies the transfer ready size in bytes. The range is 0 to 2147483647. |
Defaults
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:
Related Commands
|
|
|
|---|---|
Configures a SCSI write command for a SAN extension tuner N port. |
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 [ port port-number ]
Syntax Description
Defaults
Command Modes
Call Home configuration submode.
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example configures the from and reply-to e-mail addresses:
The following example shows how to remove the callhome configuration for email smtp-server:
switch(config-callhome)# transport email smtp-server none
The following example configures the SMTP server and ports:
switch(config-callhome)# transport email smtp-server
Related Commands
|
|
|
|---|---|
Sends a dummy test message to the configured destination(s). |
|
transport email mail-server
To configure an SMTP server address, use the transport email mail-server command. To disable this feature, use the no form of the command.
transport email mail-server {ipv4 | ipv6 | hostname} [port port number] [priority priority number]
no transport email mail-server {ipv4 | ipv6 | hostname} [port port number] [priority priority number]
Syntax Description
(Optional) Specifies SMTP server port. The range is from 1 to 65535. |
|
(Optional) Specifies SMTP server priority. The range is from 1 to 100. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to configure an SMTP server port:
The following example shows how to configure an SMTP server priority:
Related Commands
|
|
|
|---|---|
transport http proxy enable
To enable Smart Call Home to send all HTTP messages through the HTTP proxy server, use the transport http proxy enable command. To disable this feature, use the no form of the command.
no transport http proxy enable
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Note You can execute this command only after the proxy server address has been configured.
Note The VRF used for transporting messages through the proxy server is the same as that configured using the transport http use-vrf command.
Examples
The following example shows how to enable Smart Call Home to send all HTTP messages through the HTTP proxy server:
Related Commands
|
|
|
|---|---|
transport http proxy server
To configure proxy server address and port, use the transport http proxy server command. To disable this feature, use the no form of the command.
transport http proxy server ip-address [port number]
no transport http proxy server ip-address [ port number]
Syntax Description
HTTP Proxy server name or IP address (DNS name or IPv4 or IPv6 address) |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to configure proxy server address and port:
Enter configuration commands, one per line. End with CNTL/Z.switch(config)# callhome
switch(config-callhome)# transport http proxy server 192.0.2.1 port 2
Related Commands
|
|
|
|---|---|
terminal verify-user
To verify the command and do not execute, use the terminal verify-user command.
terminal verify-user username {name}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can verify the authorizaion profile for different commands. When enabled, all the commands are directed to the Access Control Server (ACS) for verification. The verification details are displayed once the verification is completed.
Examples
Related Commands
|
|
|
|---|---|
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.
Note Trunk protocol is enabled by default from Cisco MDS NX-OS Release 6.2(7) and later.
Syntax Description
Defaults
Command Modes
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 terminal
The following example shows how to enable the trunk protocol feature:
Related Commands
|
|
|
|---|---|
trustedcert
To set the trustedcert, use the trustedcert command. To disable this feature, use the no form of the command.
trustedcert attribute-name attribute-name search-filter string base-DN string
no trustedcert attribute-name attribute-name search-filter string base-DN string
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
Related Commands
|
|
|
|---|---|
tune
To configure the tune IOA parameters, use the tune command. To delete the tune IOA parameter, use the no form of the command.
tune {lrtp-retx-timeout msec | round-trip-time ms | ta-buffer-size KB| timer load-balance {global | target seconds | rscn-suppression seconds | wa-buffer-size MB | wa-max-table-size KB}
no tune {lrtp-retx-timeout msec | round-trip-time ms | ta-buffer-size KB | timer load-balance {global | target seconds | rscn-suppression seconds | wa-buffer-size MB | wa-max-table-size KB}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to configure a IOA RSCN suppression timer value:
The following example shows how to configure an IOA target load-balance timer value:
The following example shows how to configure a global IOA target load-balance timer value:
The following example shows how to configure the round-trip time in milliseconds:
The following example shows how to configure the tape acceleration buffer size in KB:
The following example shows how to configure the write acceleration buffer size in MB:
The following example shows how to configure the write Max Table Size in KB:
The following example shows how to configure the LRTP retransmit timeout in milliseconds:
Related 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
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:
The following example configures a Cisco SME RSCN suppression timer value:
The following example configures a target load-balancing timer value:
Feedback