FeedbackTable Of Contents
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. Please see the Command Mode section to determine the appropriate mode for each command. For more information, see the Cisco MDS 9000 Family Configuration Guide.
•
tail
•
•
•
•
•
tail
To display the last lines (tail end) of a specified file, use the tail command.
tail filename [number of lines]
Syntax Description
Defaults
None
Command Modes
EXEC
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. In the second terminal, 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. Refer to the example below.
Examples
The tail command displays the last lines (tail end) of a specified file.
The syntax for this command is:
tail file name [number of lines]You have to enter Ctrl-c to exit this command.
You can use two separate CLI terminals to monitor the tail of a file as it gets updated. In one CLI terminal, execute the run-script or any other desired command.
switch# run-script slot0:test mylogIn another terminal, issue the tail command for the mylog file.
switch# tail mylogconfig tIn the second CLI terminal, 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.
telnet
To log in to a host that supports Telnet, use the telnet command.
telnet [hostname | ip-address]
Syntax Description
Defaults
None
Command Modes
EXEC
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#telnet server enable
To enable the Telnet server if you wish to return a Telnet connection from a secure SSH connection, use the telnet server enable command. Use the no form of this command to disable the Telnet server.
telnet server enable
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Usage Guidelines
None.
Examples
switch(config)# telnet server enableupdatedswitch(config)# no telnet server enableupdatedterminal
To configure terminal attributes, use the terminal command. Use the no form of the terminal monitor command to stop the display of syslog output.
terminal [length | monitor | terminal-type | unlock | width]
Syntax Description
Defaults
None
Command Modes
EXEC
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 and width are different than 80 and 24, then you will 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 monitorswitch# Aug 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 insertedAug 8 10:38:45 sup48 % LOG_MODULE-5-MOD_REG_OK: LCM - Registration succeeded for module 1Aug 8 10:43:10 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_CFG_PWRDN: Module 1 powered downAug 8 10:43:10 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_PWRDN: Module 1 powered downAug 8 10:43:10 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_INSERT: Module 1 has been insertedAug 8 10:43:40 sup48 % LOG_PLATFORM-5-PLATFORM_MOD_PWRON: Module 1 powered upAug 8 10:43:42 sup48 % LOG_MODULE-5-MOD_REG_OK: LCM - Registration succeeded for module 1......The following example stops the current terminal moitoring session:
switch# terminal no monitorswitch#switch# terminal monitor
traceroute
To print the route packets take to network host specified by hostname/IP Address., use the traceroute command.
traceroute [hostname | ip-address]
Syntax Description
host name
The host name must be specified or the IP address.
ip-address
The host IP address or name must be specified.
Defaults
None
Command Modes
Exec
Usage Guidelines
This program attempts to trace the route an IP packet would follow to some internet host by launching UDP probe packets with a small TTL (time to live) then listening for an ICMP "time exceeded" reply from a gateway.
Note
Examples
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 mstrunk protocol enable
To configure the trunk protocol, use the trunk protocol enable command.
trunk protocol enable
no trunk protocol enable
Syntax Descriptionconfig Configuration commands
Syntax Description debug Debug commandss
Syntax Description show Show commandsfcdomainfcdomainfcdomainfcdomain
trunk protocol
Configure Switch wide trunk protocol
enable
Enable trunk protocol
no
Disables the trunking protocol.
Defaults
Enabled
Command Modes
Configuration mode
Usage Guidelines
If trunking protocol is disabled on a switch, no port on that switch can apply new trunk configurations. Existing trunk configurations will not be affected—the TE port will continue to function in trunking mode, but will only support traffic in VSANs that it negotiated previously (when the trunking protocol was enabled). Also, other switches that are directly connected to this switch will be 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 trunk protocol.
Examples
switch# config tswitch(config)# trunk protocol enableswitch(config)#switch(config)# no trunk protocol enableswitch(config)#
