The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the system management commands that begin with L.
To turn on the locator LED of a Fabric Extender, use the locator-led command. To turn off the locator LED, use the no form of this command.
locator-led {chassis pattern {long | medium | short} | fex fex_number }
no locator-led {chassis pattern {long | medium | short} | fex fex_number }
|
|
---|---|
Use the locator-led command to toggle the locator LED of a Fabric Extender, which allows you to easily identify the machine in a busy data center.
This example shows how to turn on the locator LED for a specific Fabric Extender chassis:
This example shows how to turn off the locator beacon LED for a specific Fabric Extender chassis:
|
|
---|---|
Displays all configured Fabric Extender chassis connected to the switch. |
|
Displays the status of the locator LED in Fabric Extender modules. |
To discard the pending changes to the syslog server configuration, use the logging abort command.
|
|
---|---|
This example shows how to discard the changes made to the syslog server configuration:
|
|
---|---|
Enables the distribution of the syslog server configuration to network switches using the CFS infrastructure. |
|
Displays the pending changes to the syslog server configuration. |
|
To commit the pending changes to the syslog server configuration for distribution to the switches in the fabric, use the logging commit command.
|
|
---|---|
This example shows how to commit the distribution of the syslog server configuration:
|
|
---|---|
Enables the distribution of the syslog server configuration to network switches using the CFS infrastructure. |
|
To enable logging messages to the console session, use the logging console command. To disable logging messages to the console session, use the no form of this command.
logging console [ severity-level ]
|
|
This example shows how to enable logging messages with a severity level of 4 (warning) or higher to the console session:
|
|
---|---|
To enable the distribution of the syslog server configuration to network switches using the Cisco Fabric Services (CFS) infrastructure, use the logging distribute command. To disable the distribution, use the no form of this command.
|
|
---|---|
This example shows how to enable the distribution of the syslog server configuration:
This example shows how to disable the distribution of the syslog server configuration:
|
|
---|---|
Cancels the pending changes to the syslog server configuration. |
|
Commits the changes to the syslog server configuration for distribution to the switches in the fabric. |
|
To log interface events, use the logging event command. To disable logging of interface events, use the no form of this command.
logging event port { link-status | trunk-status } { default | enable }
no logging event port { link-status | trunk-status } { default | enable }
Specifies to the default logging configuration is used by interfaces not explicitly configured. |
|
Enables the logging to override the port level configuration. |
|
|
---|---|
This example shows how to log interface events:
|
|
---|---|
To log events on an interface, use the logging event port command. To disable logging of interface events, use the no form of this command.
logging event port { link-status | trunk-status } [ default ]
no logging event port { link-status | trunk-status }
(Optional) Specifies the default logging configuration that is used by interfaces not explicitly configured. |
|
|
---|---|
This example shows how to log interface events:
|
|
---|---|
To configure the Optimized ACL Logging (OAL) parameters, use the logging ip access-list cache command. To reset to the default settings, use the no form of this command.
logging ip access-list cache {{entries num_entries } | {interval seconds } | {threshold num_packets }}
no logging ip access-list cache {{entries num_entries } | {interval seconds } | {threshold num_packets }}
|
|
This example shows how to to specify the maximum number of log entries that are cached in the software:
This example shows how to specify the maximum time interval before an entry is sent to the system log:
This example shows how to specify the number of packet matches before an entry is sent to the system log:
|
|
---|---|
To enable logging messages from a defined facility that have the specified severity level or higher, use the logging level command. To disable logging messages from a defined facility, use the no form of this command.
logging level facility severity-level
no logging level facility severity-level
Facility. The facilities are listed in Table 1-1 of Appendix 1, “System Message Logging Facilities.” To apply the same severity level to all facilities, use the all facility. |
|
Number of the desired severity level at which messages should be logged. Messages at or numerically lower than the specified level are logged. Severity levels are as follows:
|
|
|
Support for multicast and unicast routing features was added. |
|
Support for Flex Links and Fibre Channel over Ethernet (FCoE) N-Port Virtualizer (NPV) was added. |
This example shows how to enable logging messages from the AAA facility that have a severity level of 2 or higher:
|
|
---|---|
To configure the name of the log file used to store system messages and the minimum severity level to log, use the logging logfile command. To disable logging to the log file, use the no form of this command.
logging logfile logfile-name severity-level [ size bytes ]
no logging logfile [ logfile-name severity-level [ size bytes ]]]
|
|
This example shows how to configure a log file called logfile to store system messages and set its severity level to 4:
|
|
---|---|
To enable module log messages, use the logging module command. To disable module log messages, use the no form of this command.
logging module [ severity-level ]
|
|
This example shows how to enable module log messages:
|
|
---|---|
To enable the device to log messages to the monitor (terminal line), use the logging monitor command. To disable monitor log messages, use the no form of this command.
logging monitor [ severity-level ]
|
|
This configuration applies to Telnet and Secure Shell (SSH) sessions.
This example shows how to enable monitor log messages:
|
|
---|---|
To configure a remote syslog server at the specified hostname or IPv4/IPv6 address, use the logging server command. To disable the remote syslog server, use the no form of this command.
logging server host [ severity-level ] [ facility { auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp }| use-vrf { vrf_name | management }]
no logging server host [ severity-level ] [ facility { auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp }| use-vrf { vrf_name | management }]
(Optional) Number of the desired severity level at which messages should be logged. Messages at or numerically lower than the specified level are logged. Severity levels are as follows:
|
|
(Optional) Specifies the outgoing facility. The facilities are listed in Table 1-1 of Appendix 1, “System Message Logging Facilities.” |
|
(Optional) Specifies the virtual routing and forwarding (VRF) to be used in the remote server. The name can be a maximum of 32 alphanumeric characters. |
|
The default outgoing facility is local7.
The default VRF is management.
|
|
---|---|
This example shows how to configure a remote syslog server at a specified IPv4 address, using the default outgoing facility:
This example shows how to configure a remote syslog server at a specified hostname with severity level 5 or higher:
|
|
---|---|
To set the logging time-stamp units, use the logging timestamp command. To reset the logging time-stamp units to the default, use the no form of this command.
logging timestamp { microseconds | milliseconds | seconds }
no logging timestamp { microseconds | milliseconds | seconds }
|
|
This example shows how to set the logging time-stamp units to microseconds:
|
|
---|---|