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 Nexus Cloud Services Platform commands that begin with the letter L.
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
This command has no arguments or keywords.
None
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
This example shows how to enter console configuration mode:
n1010#
configure terminal
n1010(
config)#
line console
n1010(
config-console)#
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
This command has no arguments or keywords.
None
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
This example shows how to enter line configuration mode:
n1010#
configure terminal
n1010(
config)#
line vty
n1010(
config-line)#
|
|
---|---|
exit |
Exits a configuration mode. |
line console |
Enters console configuration mode. |
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
Note Level 0 is the highest severity level.
None
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
This example shows how to enable logging messages with a severity level of 4 (warning) or higher to the console session:
n1010# configure terminal
n1010(config)# logging console 4
n1010(config)#
To log interface events, use the logging event command. To disable logging of events, use the no version of this command.
logging event {link-status | trunk-status} {enable | default}
no logging event {link-status | trunk-status} {enable | default}
None
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
This example shows how to log interface events:
n1010# configure terminal
n1010(config)# logging event link-status default
n1010(config)#
To enable the logging of messages from a named facility and for specified severity levels, 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
Note Level 0 is the highest severity level.
None
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
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 ?
This example shows how to enable logging messages from the AAA facility that have a severity level of 0 through 2:
n1010# configure terminal
n1010(config)# logging level aaa 2
n1010(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:
n1010# configure terminal
n1010(config)# logging level license 4
n1010(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)
n1010(config)#
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]]]
Note Level 0 is the highest severity level.
None
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
This example shows how to configure a log file named LogFile to store system messages and set its severity level to 4:
n1010# configure terminal
n1010(config)# logging logfile LogFile 4
n1010(config)#
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]
Note Level 0 is the highest severity level.
Disabled
If you start logging of module messages, and do not specify a severity, then the default, Notification (5), is used.
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
This example shows how to start logging module messages to the log file at the default severity level (severity 4):
n1010# configure terminal
n1010(config)# logging module
n1010(config)#
This example shows how to stop logging module messages to the log file:
n1010# configure terminal
n1010(
config)#
no logging module
n1010#
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 hostname [indicator [use-vrf name [facility {auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp}]]]
no logging server hostname [indicator [use-vrf name [facility {auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp}]]]
None
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
This example shows how to configure a remote syslog server at a specified IPv4 address using the default outgoing facility:
n1010# configure terminal
n1010(config)# logging server 172.28.254.253
n1010(config)#
This example shows how to configure a remote syslog server at a specified host name with severity level 5 or higher:
n1010# configure terminal
n1010(config)# logging server syslogA 5
n1010(config)#
To set the unit of measure for the system message 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}
microseconds |
Specifies the time stamp in microseconds. |
milliseconds |
Specifies the time stamp in milliseconds. |
seconds |
Specifies the time stamp in seconds (default). |
Seconds
Global configuration (config)
network-admin
|
|
4.0(4)SP1(1) |
This command was introduced. |
This example shows how to set microseconds as the unit of measure for the system message time stamp:
n1010# configure terminal
n1010(config)# logging timestamp microseconds
n1010(config)#
To log in to a Virtual Service Blade (VSB), use the login virtual-service-blade command.
login virtual-service-blade name [primary | secondary]
None
EXEC
network-admin
|
|
---|---|
4.2(1)SP1(2) |
The optional primary and secondary keywords were added. |
4.0(4)SP1(1) |
This command was introduced. |
This command gives serial command access to a virtual service blade.
This example shows how to log into the Cisco Nexus 1000V CLI for the VSB named VSB-1 which is on the primary Cisco Nexus 1010.
n1010# login virtual-service-blade VSB-1 primary
n1010#