- 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
- ldap search-map
- ldap-search-map
- ldap-server deadtime
- ldap-server host
- ldap-server port
- ldap-server timeout
- lifetime seconds
- line com1
- line console
- line vty
- link (SDV virtual device configuration submode)
- link-state-trap
- link-state-trap (SME)
- load-balancing (Cisco IOA cluster Configuration submode)
- load-balancing
- locator-led
- logging abort
- logging commit
- logging console
- logging distribute
- logging level
- logging logfile
- logging module
- logging monitor
- logging server
- logging timestamp
L 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.
ldap search-map
To configure a search map, use the ldap search-map command. To disable this feature, use the no form of the command.
Syntax Description
Specifies the name of the search map. The maximum length is 128 characters. |
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
Related Commands
|
|
---|---|
ldap-search-map
To attach the configured LDAP search map to the group, use the ldap search-map command. To disable this feature, use the no form of the command.
Syntax Description
Specifies the name of the search map. The maximum length is 128 characters. |
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
Related Commands
|
|
---|---|
ldap-server deadtime
To configure global LDAP server deadtime period in seconds, use the ldap-server deadtime command To disable this feature, use the no form of the command.
no ldap-server deadtime minutes
Syntax Description
Specifies LDAP server deadtime period in minutes. The range is from 1 to 60 minutes. Default is 5 minutes. |
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
The following example shows how to configure global LDAP server deadtime period in seconds:
Related Commands
|
|
---|---|
ldap-server host
To configure global LDAP server IP address, use the ldap-server host command in configuration mode. To disable this feature, use the no form of the command.
ldap-server host {server-name | ip-address} enable-ssl | [port port number] [timeout timeout in seconds] | rootDN rootDN password [7 password | password ] [port port number] [timeout timeout in seconds] | test rootDN DN string [username user-name] [password [ 7 password | password]] [idle-time n]
no ldap-server host {server-name | ip-address} enable-ssl | [port port number] [timeout timeout in seconds] | rootDN rootDN password [7 password | password ] [port port number] [timeout timeout in seconds] | test rootDN DN string [username user-name] [password [ 7 password | password]] [idle-time n]
Syntax Description
Defaults
Port -Globally configured value (“ldap-server port <>”), in absence of which a value of 389.
Timeout- Globally configured value (“ldap-server timeout <>”), in absence of which a value of 5 seconds.
testrootDN-Default value dc=test, dc=com.
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
The following example shows how to configure LDAP server port:
Related Commands
|
|
---|---|
ldap-server port
To configure global LDAP server port, use the ldap-server port command in configuration mode. To disable this feature, use the no form of the command.
Syntax Description
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
The following example shows how to configure global LDAP server port:
Related Commands
|
|
---|---|
ldap-server timeout
To configure global timeout period in seconds, use the ldap-server timeout command in configuration mode. To disable this feature, use the no form of the command.
ldap-server timeout timeout in second
no ldap-server timeout timeout in second
Syntax Description
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
The following example shows how to configure global LDAP server timeout in seconds:
Related Commands
|
|
---|---|
lifetime seconds
To configure the security association (SA) lifetime duration for an IKE protocol policy, use the lifetime seconds command in IKE policy configuration submode. To revert to the default, use the no form of the command.
Syntax Description
Specifies the lifetime duration in seconds. The range is 600 to 86400. |
Defaults
Command Modes
IKE policy configuration submode.
Command History
|
|
Usage Guidelines
To use this command, the IKE protocol must be enabled using the crypto ike enable command.
Examples
The following example shows how to configure the SA lifetime duration for the IKE protocol:
Related Commands
|
|
---|---|
line com1
To configure auxiliary COM 1 port, use the line com1 command. To negate the previously issued command or to revert to factory defaults, use the no form of the command.
line com1 --> databits number | flowcontrol hardware | modem { in | init-string { default | user-input } | set-string user-input string } | parity { even | none | odd } | speed speed | stopbits { 1 | 2 }
no line com1 --> databits number | flowcontrol hardware | modem { in | init-string | set-string user-input } | parity { even | none | odd } | speed speed | stopbits { 1 | 2 }
Syntax Description
Defaults
Command Modes
Command History
|
|
Added an example to show the user-input initialization string for the Supervisor-2 module. |
Usage Guidelines
The line com1 command available in config t command mode. The line com1 configuration commands are available in config-com1
submode.
You can perform the configuration specified in this section only if you are connected to the console port or the COM1 port.
We recommend you use the default initialization string. If the required options are not provided in the user-input string, the initialization string is not processed.
You must first set the user-input string before initializing the string.
Examples
The following example configures a line console and sets the options for that terminal line:
The following example disables the current modem from executing its functions:
The following example enables (default) the COM1 port to only connect to a modem:
The following example writes the initialization string to the modem. This is the default.
The following example assigns the user-specified initialization string for a Supervisor-1 module to its corresponding profile:
The following example assigns the user-specified initialization string for a Supervisor-2 module to its corresponding profile:
The following example deletes the configured initialization string:
The following example writes the user-specified initialization string to the modem:
Related Commands
|
|
---|---|
line console
To configure a terminal line, use the line console command. To negate the previously issued command or to revert to factory defaults, use the no form of the command.
line console --> databits number | exec-timeout minutes | modem { in | init-string | set-string user-input string } | parity { even | none | odd } | speed speed | stopbits { 1 | 2 }
no line console --> databits number | exec-timeout minutes | modem { in | init-string { default | user-input } | set-string user-input string } | parity { even | none | odd } | speed speed | stopbits { 1 | 2 }
Syntax Description
Defaults
Command Modes
Command History
|
|
Modified the speed option by specifying speeds for the Supervisor-1 module and Supervisor-2 module. |
Usage Guidelines
The line console command available in config t command mode. The line console configuration commands are available in config-console
submode.
When setting the speed option, be sure to specify one of the exact values.
Examples
The following example configures a line console and sets the options for that terminal line:
flowcontrol software
The following example disables the current modem from executing its functions:
The following example enables (default) the COM1 port to only connect to a modem:
The following example writes the initialization string to the modem. This is the default.
The following example assigns the user-specified initialization string to its corresponding profile:
The following example deletes the configured initialization string:
The following example writes the user-specified initialization string to the modem:
Related Commands
|
|
---|---|
line vty
To configure a virtual terminal line, use the line vty command. To negate the previously issued command or to revert to factory defaults, use the no form of the command.
line vty --> exec-timeout minutes | session-limit number
no line vty --> exec-timeout | session-limit number
Syntax Description
Configures timeout in minutes. The range is 0 to 525600. To disable, set to 0 minutes. |
|
Configures the number of VSH sessions. The range is 1 to 64. |
Defaults
Command Modes
Command History
|
|
Usage Guidelines
The line vty command is available in config t command mode. The line vty configuration commands are available in config-line submode.
Examples
The following example configures a virtual terminal line and sets the timeout for that line:
Related Commands
|
|
---|---|
link (SDV virtual device configuration submode)
To link a virtual device to a real device, use the link command in SDV virtual device configuration submode. To remove a link, use the no form of the command.
link {device-alias device-name | pwwn pwwn-name }
no link {device-alias device-name | pwwn pwwn-name }
Syntax Description
Links a virtual device to a pWWN. The format is hh : hh : hh : hh : hh : hh : hh : hh, where h is a hexadecimal number. |
Defaults
Command Modes
SDV virtual device configuration submode.
Command History
|
|
Usage Guidelines
Examples
The following example shows how to link a virtual device to a device alias:
The following example shows how to link a virtual device to a pWWN:
Related Commands
|
|
---|---|
link-state-trap
To enable an SNMP link state trap on an interface, use the link-state-trap command in interface configuration submode. To disable an SNMP link state trap, use the no form of the command.
Syntax Description
Defaults
Command Modes
Interface configuration submode.
Command History
|
|
Usage Guidelines
Examples
The following example shows how to enable an SNMP link state trap on interface bay2:
The following example shows how to disable an SNMP link state trap on interface bay2:
Related Commands
|
|
---|---|
link-state-trap (SME)
To enable an Simple Network Management Protocol (SNMP) link state trap on an interface, use the link-state-trap command. To disable this feature, use the no form of the command.
Syntax Description
Defaults
Command Modes
Interface configuration submode.
Command History
|
|
Usage Guidelines
Examples
The following example shows how to enable the link-state-trap on the Fibre Channel interface:
The following example shows how to disable the link-state-trap on the Fibre Channel interface:
Related Commands
|
|
---|---|
load-balancing (Cisco IOA cluster Configuration submode)
To enable cluster reload balancing of all flows in an IOA cluster, use the load-balancing command.
load-balancing {enable | target wwn}
no load-balancing {enable | target wwn}
Syntax Description
Defaults
Command Modes
Cisco IOA cluster Configuration submode.
Command History
|
|
---|---|
Usage Guidelines
Examples
The following example shows how to enable cluster reload balancing of all targets:
Related Commands
|
|
---|---|
load-balancing
To enable cluster reload balancing for all targets or specific targets, use the load-balancing command. To disable this command, use the no form of the command.
load-balancing {enable | target wwn}
no load-balancing {enable | target wwn}
Syntax Description
Defaults
Command Modes
Cisco SME cluster configuration submode.
Command History
|
|
Usage Guidelines
The reload balancing operation is performed by the Cisco SME administrator for all or specific target ports. This operation first unbinds all the targets from the Cisco SME interfaces. The targets are then associated, one at a time, based on the load-balancing algorithm.
The reload balancing operation can be triggered if the targets remain unconnected due to errors in the prior load balancing opertions in the backend.
Examples
The following example enables reload balancing in Cisco SME:
The following example adds the host to the Cisco SME interface based on the load-balancing policy:
Related Commands
|
|
---|---|
locator-led
To blink an LED on the system, use the locator-led command. To restore the default LED state, use the no form of this command.
locator-led { chassis | fan f-number | module slot | powersupply ps-number | xbar x-number }
no locator-led { chassis | fan f-number | module slot | powersupply ps-number | xbar x-number }
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Use the locator-led command to flash the LED on a component in the system. You can use this blinking LED to identify the component to an administrator in the data center.
This command is available only on modular Cisco MDS switches.
Examples
Related Commands
|
|
---|---|
logging abort
|
|
To discard the logging Cisco Fabric Services (CFS) distribution session in progress, use the logging abort command in configuration mode.
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
The following example shows how to discard logging CFS distribution session in progress:
Related Commands
|
|
---|---|
logging commit
To apply the pending configuration pertaining to the logging Cisco Fabric Services (CFS) distribution session in progress in the fabric, use the logging commit command in configuration mode.
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines

Note Once the "logging commit" is done the running configuration has been modified on all switches participating in logging distribution. You can then use the "copy running-config startup-config fabric" command to save the running-config to the startup-config on all the switches in the fabric.
Examples
The following example shows how to commit changes to the active logging configuration:
Related Commands
|
|
---|---|
logging console
To set console logging, use the logging console command. To negate the previously issued command or to revert to factory defaults, use the no form of the command.
logging console [ severity-level ]
no logging console [ severity-level ]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
The switch logs messages at or above the configured severity level.
Examples
The following example reverts console logging to the factory set default severity level of 2 (critical). Logging messages with a severity level of 2 or above will be displayed on the console.
Related Commands
|
|
---|---|
logging distribute
To enable Cisco Fabric Services (CFS) distribution for logging, use the logging distribute command. To disable this feature, use the no form of the command.
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Before distributing the Fibre Channel timer changes to the fabric, the temporary changes to the configuration must be committed to the active configuration using the logging commit command.
Examples
The following example shows how to change the distribute logging configuration changes:
Related Commands
|
|
---|---|
Commits the logging configuration changes to the active configuration. |
|
logging level
To modify message logging facilities, use the logging level command. To negate the previously issued command or to revert to factory defaults, use the no form of the command.
logging level facility-name severity-level
no logging level facility-name severity-level
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
The switch logs messages at or above the configured severity level.
Examples
Configures Telnet or SSH logging for the kernel facility at level 4 (warning). As a result, logging messages with a severity level of 4 or above will be displayed:
Related Commands
|
|
---|---|
logging logfile
To set message logging for logfile, use the logging logfile command.To negate the previously issued command or to revert to factory defaults, use the no form of the command.
logging logfile filename severity-level [ size filesize ]
no logging logfile filename severity-level [ size filesize ]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
The switch logs messages at or above the configured severity level.
Examples
The following example configures logging information for errors or events above a severity level of 3 (errors) to be logged in a file named ManagerLogFile. By configuring this limit, the file size is restricted to 3,000,000 bytes:
Related Commands
|
|
---|---|
logging module
To set message logging for linecards, use the logging module command. To negate the previously issued command or to revert to factory defaults, use the no form of the command.
logging module [ severity-level ]
no logging module [ severity-level ]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
The following example sets message logging for modules at level 7:
Related Commands
|
|
---|---|
logging monitor
To set monitor message logging, use the logging monitor command. To negate the previously issued command or to revert to factory defaults, use the no form of the command.
logging monitor severity level
Syntax Description
Specifies the maximum severity of messages logged. The range is 0 to 7, where 0 is emergency, 1 is alert, 2 is critical, 3 is error, 4 is warning, 5 is notify, 6 is informational, and 7 is debugging. |
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
The following example sets terminal line (monitor) message logging at level 2:
Related Commands
|
|
---|---|
logging server
To set message logging for the remote server, use the logging server command.
logging server [ hostname | ip address severity_level | facility auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
Enable message logging to the specified remote server for level 7 messages:
Related Commands
|
|
---|---|
logging timestamp
To set the time increment for the message logging time stamp, use the logging timestamp command. To negate the previously issued command or to revert to factory defaults, use the no form of the command.
logging timestamp { microseconds | milliseconds | seconds}
no logging timestamp { microseconds | milliseconds | seconds}
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
The following example sets the logging time stamp to milliseconds:
Related Commands
|
|
---|---|