L Commands
This chapter describes the Cisco Nexus 1000V commands that begin with the letter L.
line console
To enter console configuration mode, use the line console command. To exit console configuration mode, use the no form of this command.
line console
no line console
Syntax Description
This command has no arguments or keywords.
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Examples
This example shows how to enter console configuration mode:
n1000v#
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(
config)#
line console
Related Commands
show line console |
Displays console line configurations. |
line vty
To enter line configuration mode, use the line vty command. To exit line configuration mode, use the no form of this command.
line vty
no line vty
Syntax Description
This command has no arguments or keywords.
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Examples
This example shows how to enter line configuration mode:
n1000v#
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
logging console
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 ]
no logging console
Syntax Description
severity-level |
(Optional) Severity level at which you want messages to be logged. When you set a severity level, for example 4, all messages at that severity level and higher (0 through 4) are logged. Severity levels are as follows: |
|
|
|
0 |
Emergency |
System unusable *the highest level* |
1 |
Alert |
Immediate action needed |
2 |
Critical |
Critical condition—default level |
3 |
Error |
Error condition |
4 |
Warning |
Warning condition |
5 |
Notification |
Normal but significant condition |
6 |
Informational |
Informational message only |
7 |
Debugging |
Appears during debugging only |
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Examples
This example shows how to enable logging messages with a severity level of 4 (warning) or higher to the console session:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging console 4
Related Commands
|
|
show logging console |
Displays the console logging configuration. |
logging event
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 }
Syntax Description
link-status |
Logs all up/down and change status messages. |
trunk-status |
Logs all trunk status messages. |
default |
Specifies that the default logging configuration is used. |
enable |
Enables interface logging to override the port level logging configuration. |
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Examples
This example shows how to log interface events:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging event link-status default
Related Commands
|
|
show logging |
Displays the logging configuration and contents of a logfile. |
logging level
To enable the logging of messages from a named facility, such as license of accounting, authorization, and authentication (AAA), of a specified severity level or higher level, use the logging level command. To disable the logging of messages, use the no form of this command.
logging level facility severity-level
no logging level facility severity-level
Syntax Description
facility severity-level |
Facility name. The severity level at which you want messages to be logged. When you set a severity level, for example 4, all messages at that severity level and higher (0 through 4) are logged. Severity levels are as follows: |
|
|
|
0 |
Emergency |
System unusable *the highest level* |
1 |
Alert |
Immediate action needed |
2 |
Critical |
Critical condition—default level |
3 |
Error |
Error condition |
4 |
Warning |
Warning condition |
5 |
Notification |
Normal but significant condition |
6 |
Informational |
Informational message only |
7 |
Debugging |
Appears during debugging only |
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Usage Guidelines
To apply the same severity level to all facilities, use the following command:
- logging level all level_number
To list the available facilities for which messages can be logged, use the following command:
Examples
This example shows how to enable logging messages from the AAA facility with a severity level of 0 through 2:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging level aaa 2
This example shows how to enable logging messages from the license facility with a severity level of
0 through 4 and then display the license logging configuration:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging level license 4
n1000v(config)# show logging level license
Facility Default Severity Current Session Severity
-------- ---------------- ------------------------
0(emergencies) 1(alerts) 2(critical)
3(errors) 4(warnings) 5(notifications)
6(information) 7(debugging)
Related Commands
|
|
logging level ? |
Lists the available facilities for which messages can be logged. |
show logging level |
Displays the facility logging level configuration. |
logging logfile
To configure the log file used to store system messages, use the logging logfile command.
To remove a configuration, use the no form of this command.
logging logfile logfile-name severity-level [ size bytes ]
no logging logfile [ logfile-name severity-level [ size bytes ]]]
Syntax Description
logfile-name severity-level |
Name of the log file that stores system messages. Severity level at which you want messages to be logged. When you set a severity level, for example 4, all messages at that severity level and higher (0 through 4) are logged. Severity levels are as follows: |
|
|
|
0 |
Emergency |
System unusable *the highest level* |
1 |
Alert |
Immediate action needed |
2 |
Critical |
Critical condition—default level |
3 |
Error |
Error condition |
4 |
Warning |
Warning condition |
5 |
Notification |
Normal but significant condition |
6 |
Informational |
Informational message only |
7 |
Debugging |
Appears during debugging only |
size bytes |
(Optional) Specifies the log file size in bytes, from 4096 to 10485760 bytes. The default file size is 10485760 bytes. |
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Examples
This example shows how to configure a log file named LogFile to store system messages and set its severity level to 4:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging logfile LogFile 4
Related Commands
|
|
show logging logfile |
Displays the contents of the log file. |
logging module
To start logging of module messages to the log file, use the logging module command. To stop module log messages, use the no form of this command.
logging module [ severity-level ]
no logging module [ severity-level ]
Syntax Description
severity-level |
(Optional) Severity level at which you want messages to be logged. If you do not specify a severity level, the default is used. When you set a severity level, for example 4, all messages at that severity level and higher (0 through 4) are logged. Severity levels are as follows: |
|
|
|
0 |
Emergency |
System unusable *the highest level* |
1 |
Alert |
Immediate action needed |
2 |
Critical |
Critical condition—default level |
3 |
Error |
Error condition |
4 |
Warning |
Warning condition |
5 |
Notification |
Normal but significant condition (the default) |
6 |
Informational |
Informational message only |
7 |
Debugging |
Appears during debugging only |
Defaults
Disabled
If you start logging messages, and do not specify a severity, then the default is used, Notification (5).
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Examples
This example shows how to start logging of module messages to the log file at the default severity level (severity 4):
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging module
This example shows how to stop the logging of module messages to the log file:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(
config)#
no logging module
Related Commands
|
|
show logging module |
Displays the current configuration for logging module messages to the log file. |
logging monitor
to enable the logging of messages to the monitor (terminal line), use the logging monitor command.
To disable monitor logging, use the no form of this command.
logging monitor [ severity-level ]
no logging monitor
Syntax Description
severity-level |
(Optional) Severity level at which you want messages to be logged. If you do not specify a severity level, the default is used. When you set a severity level, for example 4, all messages at that severity level and higher (0 through 4) are logged. Severity levels are as follows: |
|
|
|
0 |
Emergency |
System unusable *the highest level* |
1 |
Alert |
Immediate action needed |
2 |
Critical |
Critical condition—default level |
3 |
Error |
Error condition |
4 |
Warning |
Warning condition |
5 |
Notification |
Normal but significant condition (the default) |
6 |
Informational |
Informational message only |
7 |
Debugging |
Appears during debugging only |
Command Modes
Global configuration (config)
Network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Usage Guidelines
This configuration applies to telnet and Secure Shell (SSH) sessions.
Examples
This example shows how to enable monitor log messages:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging monitor
Related Commands
|
|
show logging monitor |
Displays the monitor logging configuration. |
logging server
To designate and configure a remote server for logging system messages, use the logging server command. Use the no form of this command to remove or change the configuration,
logging server host0 [ i1 [ use-vrf s0 [ facility { auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp }]]]
no logging server host0 [ i1 [ use-vrf s0 [ facility { auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp }]]]
Syntax Description
host0 |
Hostname/IPv4/IPv6 address of the Remote Syslog Server. |
i1 |
(Optional) 0-emerg;1-alert;2-crit;3-err;4-warn;5-notif;6-inform;7-debug. |
use-vrf s0 |
(Optional) Specifies a virtual routing and forwarding (VRF) name VRF name. The default is management and the VRF name. |
facility |
(Optional) Specifies the facility to use when forwarding to server. |
auth |
Specifies the auth facility. |
authpriv |
Specifies the authpriv facility. |
cron |
Specifies the Cron/at facility. |
daemon |
Specifies the daemon facility. |
ftp |
Specifies the file transfer system facility. |
kernel |
Specifies the kernel facility. |
local0 |
Specifies the local0 facility. |
local1 |
Specifies the local1 facility. |
local2 |
Specifies the local2 facility. |
local3 |
Specifies the local3 facility. |
local4 |
Specifies the local4 facility. |
local5 |
Specifies the local5 facility. |
local6 |
Specifies the local6 facility. |
local7 |
Specifies the local7 facility. |
lpr |
Specifies the lpr facility. |
mail |
Specifies the mail facility. |
news |
Specifies the USENET news facility. |
syslog |
Specifies the syslog facility. |
user |
Specifies the user facility. |
uucp |
Specifies the Unix-to-Unix copy system facility. |
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Examples
This example shows how to configure a remote syslog server at a specified IPv4 address by using the default outgoing facility:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging server 172.28.254.253
This example shows how to configure a remote syslog server at a specified host name with the severity level 5 or higher:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging server syslogA 5
Related Commands
|
|
show logging server |
Displays the current server configuration for logging system messages. |
logging timestamp
To set the unit of measure for the system messages time stamp, use the logging timestamp command. To restore the default unit of measure, use the no form of this command.
logging timestamp { microseconds | milliseconds | seconds }
no logging timestamp { microseconds | milliseconds | seconds }
Syntax Description
microseconds |
Specifies the time stamp in micro-seconds. |
milliseconds |
Specifies the time stamp in milli-seconds. |
seconds |
Specifies the time stamp in seconds (Default). |
Command Modes
Global configuration (config)
network-admin
Command History
|
|
5.2(1)SK1(1.1) |
This command was introduced. |
Examples
This example shows how to set microseconds as the unit of measure for the system messages time stamp:
n1000v# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
n1000v(config)# logging timestamp microseconds
Related Commands
|
|
show logging timestamp |
Displays the logging time stamp configuration. |