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 Cisco NX-OS system management commands that begin with the letter L.
To configure the amount of time that a receiving device should hold the information sent by your device before discarding it, use the lldp holdtime command. To remove the hold time configuration, use the no form of this command.
Global configuration mode (config)
network-admin
network-operator
vdc-admin
vdc-operator
|
|
Make sure that you are in the correct virtual device context (VDC). To switch VDCs, use the switchto vdc command.
This example shows how to configure the Link Layer Discovery Protocol (LLDP) hold time:
switch(config)#
lldp holdtime 180
switch(config)#
switch(config)#
no lldp holdtime 180
switch(config)#
To enable the reception of Link Layer Discovery Protocol (LLDP) packets on an interface, use the lldp receive command. To disable the reception of LLDP packets, use the no form of this command.
network-admin
network-operator
vdc-admin
vdc-operator
|
|
Make sure that you are in the correct virtual device context (VDC). To switch VDCs, use the switchto vdc command.
Make sure that you have globally enabled LLDP on the device.
This example shows how to enable the reception of LLDP packets on an interface:
switch(config)#
interface ethernet 6/3
switch(config-if)#
lldp receive
switch(config-if)#
exit
switch(config)#
This example shows how to disable the reception of LLDP packets on an interface:
switch(config)#
interface ethernet 6/3
switch(config-if)#
no
lldp receive
switch(config-if)#
exit
switch(config)#
|
|
---|---|
To configure the delay time for the Link Layer Discovery Protocol (LLDP) to initialize on any interface, use the lldp reinit command. To remove the LLDP initialization configuration, use the no form of this command.
Global configuration mode (config)
network-admin
network-operator
vdc-admin
vdc-operator
|
|
Make sure that you are in the correct virtual device context (VDC). To switch VDCs, use the switchto vdc command.
This example shows how to configure the delay time for LLDP initialization:
switch(config)#
lldp reinit 6
switch(config)#
switch(config)#
no lldp reinit 6
switch(config)#
To configure the transmission frequency of Link Layer Discovery Protocol (LLDP) updates, use the lldp timer command. To remove the transmission frequency configuration for LLDP updates, use the no form of this command.
Transmission frequency in seconds. The range is from 5 to 254. |
Global configuration mode (config)
network-admin
network-operator
vdc-admin
vdc-operator
|
|
Make sure that you are in the correct virtual device context (VDC). To switch VDCs, use the switchto vdc command.
This example shows how to configure the transmission frequency for LLDP updates:
switch(config)#
lldp timer 45
switch(config)#
switch(config)#
no lldp timer 45
switch(config)#
To configure the type, length, and value (TLV) descriptions to send and receive in Link Layer Discovery Protocol (LLDP) packets, use the lldp tlv-select command. To remove the TLV configuration, use the no form of this command.
lldp tlv-select [ dcbxp | management-address | port-description | port-vlan | system-capabilities | system-description | system-name ]
no lldp tlv-select [ dcbxp | management-address | port-description | port-vlan | system-capabilities | system-description | system-name ]
Global configuration mode (config)
network-admin
network-operator
vdc-admin
vdc-operator
|
|
Make sure that you are in the correct virtual device context (VDC). To switch VDCs, use the switchto vdc command.
This example shows how to enable the system capabilities TLV:
switch(config)#
lldp tlv-select system-capabilities
switch(config)#
switch(config)#
no
lldp tlv-select system-capabilities
switch(config)#
|
|
---|---|
To enable the transmission of Link Layer Discovery Protocol (LLDP) packets on an interface, use the lldp transmit command. To disable the transmission of LLDP packets, use the no form of this command.
|
|
Make sure that you are in the correct virtual device context (VDC). To switch VDCs, use the switchto vdc command.
Make sure that you have globally enabled the LLDP on the device.
This example shows how to enable the transmission of LLDP packets on an interface:
switch(config)#
interface ethernet 7/1
switch(config-if)#
lldp transmit
switch(config-if)#
exit
switch(config)#
This example shows how to disable the transmission of LLDP packets on an interface:
switch(config)#
interface ethernet 7/1
switch(config-if)#
no
lldp transmit
switch(config-if)#
exit
switch(config)#
|
|
---|---|
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 }
network-admin
network-operator
vdc-admin
vdc-operator
|
|
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 example shows how to blink the LED for module 4:
|
|
---|---|
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 log interface events, use the logging event command.
logging event {link-status | trunk-status} {enable | default}
no logging event {link-status | trunk-status} {enable | default}
Specifies that the default logging configuration is used by interfaces not explicitly configured. |
|
Specifies to enable logging to override the port level configuration. |
|
|
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 command does not require a license.
Do not configure the cache threshold to a non-default value. Configure the cache interval to a lower value so that the syslog is generated from the cache entry expiry.
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 detailed logging, use the logging ip access-list detailed command in global configuration mode. To return to default, use the no form of this command.
logging ip access-list detailed
no logging ip access-list detailed
|
|
Access list logging information can be displayed to audit the data collected from the logged access-list entry. When detailed logging is enabled by using the logging ip access-list detailed command, the following a dditional parameters are collected along with the currently collected ACL-LOG fields:
When detailed logging is enabled, the following additional parameters will be displayed in ACL-LOG cache entry along with the currently collected ACL-LOG fields:
This example shows how to configure detailed access list logging:
|
|
---|---|
Displays information about the IP access list logging cache. |
To enable logging messages from the defined facility that have the specified severity level or higher, use the logging level command. To disable logging messages from the defined facility, use the no form of this command.
logging level facility severity-level
no logging level facility severity-level
Appropriate facility. The facilities are listed in the “System Message Logging Facilities” section. 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:
|
|
|
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 add the description for physical Ethernet interfaces and subinterfaces in the system message log, use the logging message interface type ethernet description command. To disable the printing of the interface description for physical Ethernet interfaces in the system message log, use the no form of this command.
logging message interface type ethernet description
no logging message interface type ethernet description
|
|
Make sure that you are in the correct VDC. To change the VDC, use the switchto vdc command.
This example shows how to add the description for physical Ethernet interfaces and subinterfaces in the system message log:
This example shows how to disable the printing of the interface description for physical Ethernet interfaces in the system message log:
|
|
---|---|
Enables the device to log messages to the monitor based on a specified severity level or higher. |
|
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 log messages to the monitor (terminal line), use the logging monitor command to enable the device.
To disable monitor log messages, use the no form of this command.
logging monitor [ severity-level ]
|
|
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 [use-vrf VRF_name [facility {auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp}]]]
(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 VPN routing and forwarding (VRF) instance. In Cisco NX-OS Release 4.2 or later releases, the default VRF is default. |
|
(Optional) Specifies the outgoing facility. The facilities are listed in the “System Message Logging Facilities” section. The default outgoing facility is local7. |
|
|
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 enable a source interface whose IP address is displayed in all the log messages, use the logging source-interface command.
To disable the source interface, use the no form of this command.
logging source-interface interface
no logging source-interface interface
The interface whose IP address is displayed in all the log messages. |
|
|
This command was modified to ensure that the same IP address appears in all messages sent from an individual Cisco NX-OS device. |
This example shows how to specify that the IP address of the loopback 5 interface should be used for all log messages:
To set the logging time stamp units, use the logging timestamp command. To reset the logging timestamp units to the default, use the no form of this command.
logging timestamp {microseconds | milliseconds | seconds}
no logging timestamp {microseconds | milliseconds | seconds}
Specifies the time stamp unit in microseconds. The default units are seconds. |
|
|
|
This example shows how to set the logging time stamp units to microseconds:
|
|
---|---|