Published On: August 6ᵗʰ, 2019 02:07
Cisco Enterprise Network Function Virtualization Infrastructure Software Command Reference
System Log Commands
system set-log
To set the log level and log type of messages, use the system set-log command in privileged EXEC mode.
system set-log level { debug | info | warning | error | critical } logtype { configuration | operational | all }
Syntax Description
level |
Specifies the log level. |
debug |
Logs all messages. |
info |
Logs all messages that have info and higher severity level. |
warning |
Logs all messages that have warning and higher severity level. |
error |
Logs all messages that have error and higher severity level. |
critical |
Logs all messages that have critical severity level. |
logtype |
Specifies the log type. |
configuration |
Configuration log messages are recorded. |
operational |
Operational log messages are recorded. |
all |
All types of log messages are recorded. |
Command Default
For the configuration log, info is the default level. For the operational log, warning is the default level.
Command History
show system logging-level
To view the log level and log type settings, use the show system logging-level command in privileged EXEC mode.
Syntax Description
configuration |
(Optional) Log level for the configuration log type is displayed. |
operational |
(Optional) Log level for the operational log type is displayed. |
Command Modes
Privileged EXEC (#)
Command History
Release | Modification |
---|---|
3.5.1 |
This command was introduced. |
Examples
The following is a sample output of the show system logging-level command with the default log level settings:
nfvis# show system logging-level system logging-level configuration info system logging-level operational warning
show log
To display a list of available log files or content of a specific log file, use the show log command in privileged EXEC mode.
Syntax Description
log-name |
Specifies the log file name. The log file name should be same as shown in the output of the show log command. |
Command History
Release | Modification |
---|---|
3.7.1 |
The log-name parameter is an optional parameter. When this parameter is not specified, a listing of all available log files is displayed. In addition, you can provide a partial or complete log file name (as shown in the show log output) in the log-name parameter. |
3.6.1 |
The log-name is a required parameter. |
3.5.1 |
This command was introduced. |
Usage Guidelines
In Release 3.6.1 and earlier releases, the exact directory path (/var/log) and exact filename is required to run this command.
Starting with Release 3.7.1, this command is modified for the following:
-
Display a list of all available log files (using show log).
-
Display a list of log files that match the partial filename provided in the log-name parameter.
-
Display the content of the specified log file if the filename matches exactly as shown in show log output.
To filter the content of a log file, you can use the show log log-name | ? command.
Examples
The following example displays the available log files.
nfvis# show log File Name Last Modified Size backups.log Mon Nov 13 10:30:01 2017 10758 boot.log Mon Nov 13 10:51:25 2017 13893 btmp Mon Nov 13 10:26:21 2017 768 confd_audit.log Mon Nov 13 11:05:35 2017 10423 confd_confd.log Mon Nov 13 10:49:54 2017 20977 confd_devel.log Mon Nov 13 10:49:54 2017 18969 confd.log Mon Nov 13 10:48:58 2017 582 confd_netconf.log Mon Nov 13 10:51:25 2017 1613 cron Mon Nov 13 11:01:01 2017 24762 ...
Examples
The following examples display all available log files matching a partial name.
nfvis# show log nfvis File Name Last Modified Size nfvis_config.log Mon Nov 13 10:51:25 2017 311395 nfvis_setup.log Mon Nov 13 10:49:59 2017 3170 nfvis_syslog.log Mon Nov 13 10:51:25 2017 1483 nfvis# show log esc File Name Last Modified Size esc/debug_yangesc.log Mon Nov 13 10:49:53 2017 276748 esc/error_escmanager.log Mon Nov 13 10:50:06 2017 11825 esc/esc_confd.log Mon Nov 13 10:28:42 2017 588 esc/escmanager.log Mon Nov 13 10:50:19 2017 44597 esc/esc_postinit.log Mon Nov 13 10:50:25 2017 74940 esc/event_escmanager.log Mon Nov 13 10:50:19 2017 4791 esc/forever.log Mon Nov 13 10:49:07 2017 6892 esc/yangesc.log Mon Nov 13 10:49:53 2017 23982
Examples
The following examples show the content of a particular log file.
nfvis# show log nfvis_syslog.log Nov 13 09:50:35 nfvisto6 %SYS-6-NFVIS_UP: System started by Power Switch. Up 1 minute, 42 seconds Nov 13 09:51:35 nfvisto6 %SYS-6-UPGRADE_APPLY: Upgrade Process: In Progress Nov 13 09:51:36 nfvisto6 %SYS-6-UPGRADE_APPLY: Upgrade Process: Restoring VMs
Examples
The following example filters the content of a log file.
nfvis# show log esc/escmanager.log | ? Possible completions: append Append output text to a file begin Begin with the line that matches count Count the number of lines in the output exclude Exclude lines that match include Include lines that match linnum Enumerate lines in the output more Paginate output nomore Suppress pagination save Save output text to a file until End with the line that matches nfvis# show log esc/escmanager.log | include ERROR | more 02-Mar-2017 01:46:27,613 INFO [LogContextService.java:outputDecoratedLog():185] [tid=] [cl=SM ] [tags=threadName:VM_STATE_MACHINE-SystemAdminTena_demo7_0_8adb7f6a-ca5e-454d-9c14-fd9d5d21054f,stateMachineType:VM_STATE_MACHINE, stateMachineContextId: SystemAdminTena_demo7_0_8adb7f6a-ca5e-454d-9c14-fd9d5d21054f] VM_STATE_MACHINE- SystemAdminTena_demo7_0_8adb7f6a-ca5e-454d-9c14-fd9d5d21054f Transition: VM_INERT_STATE ---- VM_ACTION_FAILED_EVENT ---- > VM_ERROR_STATE 02-Mar-2017 01:46:27,613 INFO [ManagedObject.java:update():66] [tid=] [cl=DB ] [tags=] DB TRANSACTION(477010616) - UPDATE VMStateMachineDao with values stateMachineContextId:SystemAdminTena_demo7_0_8adb7f6a-ca5e-454d-9c14-fd9d5d21054f; stateMachineType:VM_STATE_MACHINE; serviceStateMachineContextId:1a037a82-b248-4117-9156-aa26bc8e2ce1; deploymentDetailsId:15fa65be-0775-47c3-aa46-d6eb1e428a93; previousState:VM_INERT_STATE; currentState: VM_ERROR_STATE; monitorSet:true; serviceDefinition:0; vmInstance:demo7; vmIndex:0; classMetadata:SingleTableEntityPersister(com.cisco.esc.db.VMStateMachineDao); 02-Mar-2017 01:46:27,669 ERROR [StateMachineEngine.java:buildLogContext():75] [tid=] [cl=SM ] [tags=] Unable to set log context, null values found for RequestDetails 02-Mar-2017 01:46:27,673 INFO [LogContextService.java:outputDecoratedLog():185] [tid=] [cl=SM ] [tags=threadName:RECOVERY_WORKFLOW_STATE_MACHINE-93cfacf5-9ee8-4e0e-9438-722944b4da2d,stateMachineType: RECOVERY_WORKFLOW_STATE_MACHINE,stateMachineContextId: 93cfacf5-9ee8-4e0e-9438-722944b4da2d] RECOVERY_WORKFLOW_STATE_MACHINE-93cfacf5-9ee8-4e0e-9438-722--More-- ...