L Commands
This chapter describes the Cisco Nexus 1000V commands that begin with the letter L.
limit-resource erspan-flow-id minimum
To configure the range of allowed ERSPAN flow IDs, use the limit-resource erspan-flow-id minimum command. To remove the configuration, use the no form of this command.
limit-resource erspan-flow-id minimum min-val maximum max-val
no limit-resource erspan-flow-id
Syntax Description
min-val |
Minimum ERSPAN flow ID number allowed. |
maximum |
Configures the maximum range value for ERSPAN flow IDs. |
max-val |
Maximum ERSPAN flow ID number allowed. |
Defaults
None
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(2) |
This command was introduced. |
Examples
This example shows how to restrice the range of allowed ERSPAN flow IDs to the range, 1-80:
n1000v(config)# limit-resource erspan-flow-id minimum 1 maximum 80
This example shows how to restore the default range of ERSPAN flow IDs:
n1000v(config)#no limit-resource erspan-flow-id
Related Commands
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.
Defaults
None
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(1) |
This command was introduced. |
Examples
This example shows how to enter console configuration mode:
n1000v# configure terminal
n1000v(config)#line console
n1000v(config-console)#
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.
Defaults
None
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(1) |
This command was introduced. |
Examples
This example shows how to enter line configuration mode:
n1000v# configure terminal
n1000v(config)#line vty
n1000v(config-line)#
logging console
Use the logging console command to enable logging messages to the console session.
To disable logging messages to the console session, use the no form of this command.
logging console [severity-level]
no logging console
Syntax Description
Defaults
None
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(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
n1000v(config)# logging console 4
n1000v(config)#
Related Commands
|
|
|
|---|---|
show logging console |
Displays the console logging configuration. |
logging event
Use the logging event command to log interface events.
logging event {link-status | trunk-status} {enable | default}
no logging event {link-status | trunk-status} {enable | default}
Syntax Description
Defaults
None
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(1) |
This command was introduced. |
Examples
This example shows how to log interface events:
n1000v# configure terminal
n1000v(config)# logging event link-status default
n1000v(config)#
Related Commands
|
|
|
|---|---|
show logging |
Displays the logging configuration and contents of logfile. |
logging level
Use the logging level command to enable the logging of messages as follows:
•
from a named facility (such as license or aaa)
•of a specified severity level or higher
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
Defaults
None
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(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:
•logging level ?
Examples
This example shows how to enable logging messages from the AAA facility that have a severity level of 0 through 2:
n1000v# configure terminal
n1000v(config)# logging level aaa 2
n1000v(config)#
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
n1000v(config)# logging level license 4
n1000v(config)# show logging level license
Facility Default Severity Current Session Severity
-------- ---------------- ------------------------
licmgr 6 4
0(emergencies) 1(alerts) 2(critical)
3(errors) 4(warnings) 5(notifications)
6(information) 7(debugging)
n1000v(config)#
Related Commands
|
|
|
|---|---|
show logging level |
Displays the facility logging level configuration. |
logging level ? |
Lists the available facilities for which messages can be logged. |
logging logfile
Use the logging logfile command to configure the log file used to store system messages.
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
Defaults
None
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(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# config t
n1000v(config)# logging logfile LogFile 4
n1000v(config)#
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]
no logging module [severity]
Syntax Description
Defaults
Disabled
If you start logging of module messages, and do not specify a severity, then the default is used, Notification (5).
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(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
n1000v(config)# logging module
n1000v(config)#
This example shows how to stop the logging of module messages to the log file:
n1000v# configure terminal
n1000v(config)#no logging module
n1000v#
Related Commands
|
|
|
|---|---|
show logging module |
Displays the current configuration for logging module messages to the log file. |
logging monitor
Use the logging monitor command to enable the logging of messages to the monitor (terminal line). This configuration applies to telnet and Secure Shell (SSH) sessions.
To disable monitor logging, use the no form of this command.
logging monitor [severity-level]
no logging monitor
Syntax Description
Defaults
None
Command Modes
Global configuration (config)
Network-admin
Command History
|
|
|
4.0(4)SV1(1) |
This command was introduced. |
Examples
This example shows how to enable monitor log messages:
n1000v# configure terminal
n1000v(config)# logging monitor
n1000v(config)#
Related Commands
|
|
|
|---|---|
show logging monitor |
Displays the monitor logging configuration. |
logging server
Use the logging server command to designate and configure a remote server for logging system messages. 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
Defaults
None
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(1) |
This command was introduced. |
Examples
This example shows how to configure a remote syslog server at a specified IPv4 address, using the default outgoing facility:
n1000v# configure terminal
n1000v(config)# logging server 172.28.254.253
n1000v(config)#
This example shows how to configure a remote syslog server at a specified host name, with severity level 5 or higher:
n1000v# configure terminal
n1000v(config)# logging server syslogA 5
n1000v(config)#
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 timestamp, 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 |
Timestamp in micro-seconds. |
milliseconds |
Timestamp in milli-seconds. |
seconds |
Timestamp in seconds (Default). |
Defaults
Seconds
Command Modes
Global configuration (config)
network-admin
Command History
|
|
|
4.0(4)SV1(1) |
This command was introduced. |
Examples
This example shows how to set microseconds as the unit of measure for the system messages timestamp:
n1000v# configure terminal
n1000v(config)# logging timestamp microseconds
n1000v(config)#
Related Commands
|
|
|
|---|---|
show logging timestamp |
Displays the logging timestamp configuration. |
Feedback